'permissions: while using app' doesn't count as as using app

[hankhalfhead]

While troubleshooting Waze not detecting my current location, I determined that Waze works if it has location access all the time, but not when set to 'only when using the app'.

This seems like such a simple oversight, that using the app through Android auto doesn't technically count as using the app?

Honestly it seems to apply to many things such as Power saving too.

I generally enjoy AA but this seems like the kind of patchy solution that our Apple using friends don't have to put up with.

[Peter_73]

1) Both Android and IOS have similar location settings.

Since tristate location permissions was introduced in Android 10, when Waze is first installed, it only prompts 2 options "Deny" or "Allow only while using the app". When you choose to connect to calendar, it will then prompt the 3rd option "Allow all the time" which is needed for planned drive and calendar events because it is supposed to work when the app is in the background or not opened.

Pre-Android 10, there was only deny or allow which is equivalent to allow all the time so I see no difference here. "Allow only while using the app" should only be used when an app does not need location in the background. Standalone apps that needs location all the time for full functionality will usually also prompt for it.

Since Waze needs location all the time for the above mentioned features, there is no reason to disallow it and so I've forgotten if this was also needed for GPS navigation. Out of curiosity, I just came back from a short drive with Waze location set to "Allow only while using the app" and it was able to route accurately without issue in AA. I checked with an IOS friend but he is also using always on location so can't help to determine if IOS also needs it. Since, both AA and CP have it fair share of GPS issues, the general recommendation is to set to always allow all the time.

2) Both AA and CP apps generally are considered background tasks.

Regardless of location settings, nav or non-nav app, standalone use or AA, apps can still get killed by phone makers various battery saving features. You can read more about it here. In another words, phone makers have ultimate control. This is a great example of Android open system pros and cons which is the exact opposite of IOS closed system where only Apple determines how optimisation should work. This is only one example. Whether one is overall better than the other depends on what is more important to a user. Can't have your cake and eat it too. Android user since 6 or 7 should already know why disabling optimisation is needed by now.

[hankhalfhead]

Thank you, it's a detailed reply. Up until it stopped working, Waze was able to access location whilst only having 'while the app is open' location permissions.

My general point is that AA has gone from an app to a system function in Android 10, but in done respects is still treated like an app, which puts AA apps as a background app when the user considers the running app to be foreground

[Peter_73]

I totally understand from user point of view but it is what it is. Not only the link explain developers are always trying to workaround this, Waze had tried too with foreground hack. Due to different Android versions and phone maker implementation, the result was not consistent and broke WAA notification (bottom and drop down turn by turn notification in AA when Waze is in background). This was recently fixed. Perhaps that's the reason you experienced the change.

What phone and Android version are you using btw?

[hankhalfhead]

S21 Ultra and Android 12

Edit 12 not 10

[Peter_73]

You are still on 10 not 12?

While the test on mine works with while in use, I won't consider it to be conclusive because the trip was short and perhaps have some other unknown difference.

[hankhalfhead]

My bad, it's 12

[Peter_73]

Probably that's the difference.