-
Notifications
You must be signed in to change notification settings - Fork 38
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
🐞 [iOS] High battery usage created by overhead #179
Comments
@JustinGanzer thanks for the bug report, the periodic network activity spikes look like our telemetry system sending batches of data but we don't expect the extra overhead that you're seeing.
How did you simulate this? Using the built-in simulation tracks or a gpx file? |
Hey @alfwatt, I'm currently testing using real devices as well as gpx files recorded using an iPhone, for the simulator doesn't support battery analysis as fas as I am aware. Now that I think about the simulation environment, our app is connected via Wifi. I'm not sure if there is a difference in time the radios stay on when compared to cellular data. If you find any of these factors could potentially yield different results, I'd be willing to go out and test it in a more natural environment. |
I'm seeing the same percentage of usage when using Mapbox and a cellular connection. Every 30 seconds the SDK is requesting a location and posting back to mapbox.com. |
Same issue here. Are you planning to fix this? |
Same issue happening with our app, overhead is constantly on 60%. |
Configuration
Steps to Reproduce
MGLMapboxMetricsEnabled
Userdefault at true/defaultExpected
I expected the SDK to be preservative of battery life by means of batch send telemetry and such, thus leaving radios to go idle every once in a while.
What Actually happens
Radios never ever go to idle, responsible for over 60% of the average component utilization.
Other findings
By only doing one thing, that is opting out of Mapbox telemetry (through the app settings of iPhone) almost immediately drops the overhead completely.
Logging
With telemetry enabled
With telemetry disabled
I'll update as soon as I have time to further investigate, but perhaps anyone can confirm this behaviour? That is a lot of energy consumed by telemetry if that is the case. Hopefully we can find a way to leave telemetry on all while lowering power consumption.
The text was updated successfully, but these errors were encountered: