is power consumption dependent on offline map size/structure/location?
Hi - we will be going on a 2+ week bicycle trip in the desert and will be using Locus Pro on a Samsung Galaxy Tab Pro 8.4.
On some multi-day training rides, we've noticed some higher battery drain on some rides than on others. Typically we only use it for map checks at junctions - viewing the map with the current GPS location whenever we come to obscure junctions, to make sure we are where we think we are. Probably 15 seconds of usage, once every 15+ minutes. The rest of the time the screen is off and locked (but the Locus setting 'Disable Lock Screen' is on - very handy).
Anyway, as a programmer, my theory is that the battery drain rate is a function of the database size, i.e. how many total tiles exist in the map database that is being viewed.
For one trip, we downloaded all the tiles for the immediate area, but limited it to 31.50MB, zooms 11,12,13,14,15. Battery consumption seemed very low.
For a more recent trip, we used a much larger map, 3609.84MB, zooms 7,8,9,10,11,12,13,14,15; but only down to 14 in the area we were using.
Do you know, or have any guesses, as to how these things might affect battery consumption? It seems like searching a larger database would take more CPU power than searching through a smaller database.
So, one thought we had to reduce consumption for the long trip is to just fracture the entire database into geographically smaller regional maps, then specifically select the map that's needed day by day.
Could it be taking more CPU power to search for zoom 15 tiles, in an area where we only downloaded to 14, even though other parts of the same map database are 15?
Does the map database type (sql) matter for power consumption?
Also, would it make much difference if the map is on the internal memory versus the external sd card?