Live tracking login is not possible with restrict background data

Falco shared this problem 2 weeks ago
Closed

If I restrict background Data for the whole system on Android 5 I can't start live tracking. I need to enable background data to connect and then I could disable it will still work which means only the starting process get interrupted by android. I did test with the public room.


How to reporuce:

  1. Settings -> Data Usage, tap on the menu button in the top right corner, then tap Restrict background data.
  2. open browser to check internet is still available
  3. start locus pro (need to be in foreground to bypass restriction)
  4. start live tracking
  5. you will get a repeating connection error

I wasn't sure about bug or connection issue because I did experience alot of livetracking service login errors during usage of bad mobile service. But now I have a usecase which did work 0 of 10 times.


Workarround:

  1. disable Restrict background data
  2. start live tracking
  3. wait untill it got connected (until stats 0/0 do appear)
  4. enable Restrict background data

Confirmed on Android 5 Sony Z3C

Planed tests:

  • restrict background data only on locus
  • Android 7 restrict background data

Comments (3)

photo
1

Android 7 results:

- restrict background data got replaced with a similar feature but changed UI and changed label: No issue with the new data saving mode

- restrict background data only on locus: no issue


I guess this is a android 5 bug and not worth to fix.


Are you still interested in logs and screenshots? I would suggest to skip android 5 bugs despite my suggestion to use this old OS because of the excelent power usage.

photo
1

Hello Falco,

thanks for the report. Restricted background data seem to also work normally also on my Android 6 phone so it is thankfully not such a big issue at the moment. Live tracking could possibly detect this and inform the user about restricted background data access after starting the LT though since it limits normal function of the LT if the device is sleeping.

I will discuss this with Menion next week and see if/how to solve this issue.

Best Regards

Milan

photo
1

Hello Falco,

this is really a very specific use case and it is probably not worth fixing and testing if Android 6+ devices behave correctly. I will not be fixing this for this reason, unless more people need this fixed. I hope this issue is not too limiting for you and thank you for informing me about this, every quirk is good to know :)

Best Regards

Milan