WhereYouGo not running in background on Android 8.0

[kur...@gmail.com]

Hi every one

Recently I wanted to play the cartridge “Bergsteigen” (3d1080c3-c3f3-4df7-b96c-0f4f2aebe343) but it didn’t work as expected in the WhereYouGo player.

Future analyses showed two problems occurring if the WhereYouGo player is running on Android 8.0.

1. If the phone gets locked, the app only gets only randomly some CPU time. So it can happen that the cartridge only gets called every few minutes what for some cartridge might not be enough. Here it would help if the WhereYouGo player offers an option to make a WakeLock (https://developer.android.com/reference/android/os/PowerManager.WakeLock) call to the android API.

2. After installing a Wake Lock app on my phone the WhereYouGo player was working even if the phone was locked. But the mentioned cartridge still didn’t behave the way it should. I recognised that if the phone was locked the WhereYouGo player signalled several times an hour a GPS fix. This brought me to the following URL: https://developer.android.com/about/versions/oreo/background-location-limits. Means that the WhereYouGo app is considered as a background app if the phone gets locked and only can get a few location updates an hour. It would be good if one of the mentioned functionality would be implemented to make the app even if the phone is locked recognised as a foreground app.

 

I think, those two issues could get to a real issue for the app as soon as Android 8.0 is more widely used.

 

Thanks Chris

[kur...@gmail.com]

Hi Michal (biylda)

I'ts nearly a year sins your last activity on this group and the github of WhereYouGo. Are you still going to maintain this app or are there any other planes?

I know that maintaining such a app is a big effort and you not always might have the time for it. But it would be great if you could share your future planes for this app in this group or on github and also provide information there if any help is required and how the community can help you whit this app.

I already created a fix for the second problem mentioned about which could be adapted to the main branche and the fix for the first one should be finished soon.

I hope to hear from you soon.

Regards, Chris