Recording/pausing incosistencies between app and notification

virtualdj shared this problem 4 months ago
Closed

Hi, during my last hiking with Locus Pro v3.28.1 (on a Samsung Note 4 with Android KitKat) I noticed some incosistencies on the recording/pausing state.

I captured two screenshots which I've merged here for your convenience.

46550fc8c6ff643b18d8b437d29e8415

As you can see, the app main view reports Paused while the notification (with the two action buttons of course that I forgot to capture) says "In registrazione" (i.e. Recording in English). You may notice the clock: the screenshots were taken one after another.

I usually start recording and pause/resume from the notification and the widget because it's faster and I discovered this issue because the icons on the widget weren't "correct" with what the notification said... So I opened the app and realized that the notification was wrong.

I didn't notice this behaviour in the past, so it has to be something from the recent versions; also, sometimes I still have the widget unsync issue with these Locus versions, but normally rebooting the phone solves the problem.

Maybe you can add an hidden "report issue" button/menu in the app settings, so when I/we have this issues you can create a dump of the app state and see where the real problem is? It's frustrating not to have the state propagated between the various locations (main app, notification, widget, Android Wear app, etc.). :-)

Comments (10)

photo
1

Hi,

as I can see from the "widget unsync issue", it's quite hard to replicate this problem - I've tested it a few times and haven't observed any such behavior. Both widget, notification and the main app recording panel display the same state. We'll try to test it on other devices and OS versions.

best regards

Michal

photo
1

Do you have both Free and Pro versions installed? If yes, remove one of them - that may be the cause of the issue.

photo
1

I have only Pro version installed (and the same was in the past for the widget unsync issue); this specific time widget was OK (it was "Paused") the problem was on the Notification text and action buttons.

I'm aware that's difficult to troubleshoot, hence I suggested to have a Debug command buried in the settings in case of problems. It doesn't happen frequently, but it's unpleasant when it does :-)

photo
1

Hello,

I currently can't imagine what information insert to log, that may help here. Locus for sure still send information about recording state to notitification system of status bar. Why it does not react correctly, don't know. It looks to me little like there are some problems with existence of Locus itself. May you check if all optimizations are disabled for Locus Map app? ( check this manual page: http://docs.locusmap.eu/doku.php?id=manual:faq:gps_lost_fix_android6 ).

I personally do not use widget or this notification too much, so seems I should start.

photo
1

> I personally do not use widget or this notification too much

:-( actually I use both widget and notfication a lot, because I need to start recording when walking and pause before entering inside a building (to avoid wrong point due to bad GPS reception) when visiting new cities/hiking.

> I currently can't imagine what information insert to log

For the widget it's not easy, I know, because you don't have an idea to what is currently displaying.

But for the notification you can log when the recording is started/paused and from which source (app, notification, widget, wear, etc.) and then when you call the Android code that displays/create/update the notification you log that too. The case of my screenshot displays that something went wrong there, i.e. when updating the existing notification.

photo
2

Thanks for a suggestions. Unfortunately problem here is caused by disconnecting of widget and app, or notification system and app. I really need to test and simulate it on own device. Will let you know if I discover something ...

@Michal, thanks, I'll take this task.

photo
1

Thanks, I suggest you to start recording and pausing/resuming from the widget and/or notification without opening Locus main UI. Try doing it several times and, if possible, go inside buildings to simulate a GPS loss.

This increases the changes to mimic my behaviour... of course it's not so easy, because neither my installation always shows the issue, but it happens.

Finally I forgot to answer to your optimization question: yes, they are disabled and as I'm running the app in Android KitKat (4.4) there are no battery optimization or Doze issues.

photo
photo
1

Good evening,

unfortunately, during last months, I was testing and using recording widget from time to time and never had any problem with it. Because I'm unable to simulate problem we talk here, it is almost impossible for me to fix it. Sorry, I'm closing this topic.

When you find some useful news that may help here in future, feel free to write here.

Thank you for understanding,

Menion

photo
1

OK, but is there something I can do to help if/when I see that problem again? Logs, dump, record a video or something else?

photo
1

Hard to say. Best should be to try to figure out steps that caused this problem. May you find out that something like the restart of the device, wait minute, start recording over widget without start of app etc etc ...

photo