Android 13 - no recording details on lockscreen or pulldown

Hi Bob,

and are you sure the track recording is on and your active track recording profile parameters allow the recording of track points? E.g. check the TR panel and selected GPS accuracy in the profile. Values lower than 50m may result in no recording.

Hi Michal

The track is recording OK and I can see everything when I unlock the phone and look at the app. It's just the notifications that give zero's for everything.

I exported the settings from my Android 8 phone which shows the detail in the notifications and imported them to the Android 13 phone. I've double checked the recording profile on both phones and they are the same.

Both phones have the same version of Locus Map (4.13.1). The main difference is the Android version.

Cheers Bob

Hi Bob,

thank you for the additional information. Unfortunately, we can't simulate the problem on any A13 device so we have to wait for some more feedback from other users. So far you are the only one to report this. Thank you for understanding.

P.S. you can "unlock" the app in its settings so that you don't have to unlock your phone. Go to Locus settings > controlling > display > unlock screen > put it ON.

Thanks Michal

I already knew about the unlock feature but don't like to use it.

I'll keep playing around with settings (app and phone) and I'll let you know if I find anything.

Cheers

Bob

Hi Michal

I've done some playing around with settings, and it seems to me that the app is losing touch with the notification after it is made initially.

When I start recording, the notification displays zeros until I change a notification setting.

If I switch notifications off then on again, it displays the details of the recording for that point in time, and again doesn't change them.

Also Stop and Pause options in the notification do nothing.

I hope this further info may help diagnose the problem. If there's anything I can do to get more info please let me know.

Cheers

Bob

Hi Bob,

thanks for the testing. We've tried the same procedure on multiple A13 devices but to no avail - all worked correctly. We can't start fixing until we replicate the problem successfully.

Hi Michal

I'm pleased to let you know that the problem has resolved itself when the phone did an upgrade from One UI 5.0 to One UI 5.1.

Thanks

Bob

Thanks Bob for the update!