This object is in archive!
On widget v3.14 the add waypoint button does nothing
Solved
I just upgraded to v3.14 Pro and now when clicking on the "Add waypoint" button on the widget (even while recording a track) there is no popup dialog which asks for a name. Basically it does nothing.
Also, I noticed that you added the "Stop recording" action on the notifications, can you also add the "Pause"/"Resume" action? It could be very useful.
Thanks!
The same problem 
Hm here it works. (see attachment)
So i think, we need more details about your steps, hw and sw.
About your ideas. feel free to open a new topic
Hm here it works. (see attachment)
So i think, we need more details about your steps, hw and sw.
About your ideas. feel free to open a new topic
I'm also not possible to simulate this problem.
Is "add waypoint" button change it's color from "disabled" (light grey) to "enabled" (dark grey, almost black) state? Also if you start track record from Locus and then minimize it, is button on widget working or still not?
I'm also not possible to simulate this problem.
Is "add waypoint" button change it's color from "disabled" (light grey) to "enabled" (dark grey, almost black) state? Also if you start track record from Locus and then minimize it, is button on widget working or still not?
@gynta
I was out for a walking yesterday and posted immediately after I found the bug.
When you replied, I retried and the second time and it worked (dialog appeared, as in your video).
When I posted, I was recording a track (I still have the track on my DB) and the button was Enabled; I cannot record a video because I'm on KK and I'm not rooted, but I captured a screenshot at that time:
As you see, I was recording and the button was enabled. Pressing the + button didn't do anything. I had to click the Locus icon and add the waypoint from there.
I also tried to click the + button a few other times after minimizing Locus, but it never worked.
It worked only after stopping (and saving) the track and starting a new one, but I wasn't able to simulate the problem (and I wanted to add the waypoints to my previous track, of course).
Additionally, after it worked the second time, I saw another "quirk". After stopping the track recording with the right button (STOP) and saving, the widget remained in a "stalemate" state, see the screenshot below.
You can see that the GPS/Position icon has disappeared (because I stopped the track recording and saved, thus disabling the GPS) but the widget still though to be in recording mode (see the two button states).
I know that this may not help you to troubleshoot a lot, but something is not working 100% well here.
I'll do more tests when I'll go out another time, but how can I help you to debug this situation without taking a video?
@gynta
I was out for a walking yesterday and posted immediately after I found the bug.
When you replied, I retried and the second time and it worked (dialog appeared, as in your video).
When I posted, I was recording a track (I still have the track on my DB) and the button was Enabled; I cannot record a video because I'm on KK and I'm not rooted, but I captured a screenshot at that time:
As you see, I was recording and the button was enabled. Pressing the + button didn't do anything. I had to click the Locus icon and add the waypoint from there.
I also tried to click the + button a few other times after minimizing Locus, but it never worked.
It worked only after stopping (and saving) the track and starting a new one, but I wasn't able to simulate the problem (and I wanted to add the waypoints to my previous track, of course).
Additionally, after it worked the second time, I saw another "quirk". After stopping the track recording with the right button (STOP) and saving, the widget remained in a "stalemate" state, see the screenshot below.
You can see that the GPS/Position icon has disappeared (because I stopped the track recording and saved, thus disabling the GPS) but the widget still though to be in recording mode (see the two button states).
I know that this may not help you to troubleshoot a lot, but something is not working 100% well here.
I'll do more tests when I'll go out another time, but how can I help you to debug this situation without taking a video?
Hello,
thanks for a precise report. There were such problems few months ago, but I hoped they are already solved. Damn.
Anyway nor video, nor some logs won't help here. I have to test it on own device and try to simulate. Fortunately such troubles aren't end of work, because in worst case you may stop using it and control track record over Locus. Anyway I'll try to check it more precisely and let you know if I'll be able to simulate it and fix it. Thanks for now.
Hello,
thanks for a precise report. There were such problems few months ago, but I hoped they are already solved. Damn.
Anyway nor video, nor some logs won't help here. I have to test it on own device and try to simulate. Fortunately such troubles aren't end of work, because in worst case you may stop using it and control track record over Locus. Anyway I'll try to check it more precisely and let you know if I'll be able to simulate it and fix it. Thanks for now.
What I can say is that, if I remember well, Locus was NOT running the first time I started recording (so when I experienced the issue). I clicked the record button from the widget.
The path was recorded correctly, though. It's just the waypoint feature that didn't work.
Obviously I opened the app to add the waypoint manually, after it didn't work from the widget. But still it didn't work from the widget after minimizing the app again, only a stop recording worked.
I agree with you that it might be a problem of communication between the widget and the main app.
What I can say is that, if I remember well, Locus was NOT running the first time I started recording (so when I experienced the issue). I clicked the record button from the widget.
The path was recorded correctly, though. It's just the waypoint feature that didn't work.
Obviously I opened the app to add the waypoint manually, after it didn't work from the widget. But still it didn't work from the widget after minimizing the app again, only a stop recording worked.
I agree with you that it might be a problem of communication between the widget and the main app.
bad news
today occurs the same problem here...
bad news
today occurs the same problem here...
1.
steps after fresh device rebooot:
start record with widged
add poi on widged works
2.
steps after fresh device rebooot:
start locus first
record track
minimize
add poi on widged doesn't work
1.
steps after fresh device rebooot:
start record with widged
add poi on widged works
2.
steps after fresh device rebooot:
start locus first
record track
minimize
add poi on widged doesn't work
Quite interesting. Thanks gynta for very precise description, unfortunately it works for me :/. May you try to create for me a log, right after you press "Add waypoint" button on widget and nothing happen?
Quite interesting. Thanks gynta for very precise description, unfortunately it works for me :/. May you try to create for me a log, right after you press "Add waypoint" button on widget and nothing happen?
I don't know if I had done things correctly, however I connected my phone to the PC using ADB and then used Android Log Viewer because it allowed to filter messages by app name: menion.android.locus.pro.
The results of gynta's method 1 (working) are in log1.txt, while method 2 (non working which implies launching Locus) are in log2.txt.
In method 2, every time I tapped the "Add waypoint" button this line appeared:
but no dialog box asking for a name.
I hope it helps you somehow, but to me it doesn't seem an application debug log. Maybe because the app is not debuggable? I don't know.
I don't know if I had done things correctly, however I connected my phone to the PC using ADB and then used Android Log Viewer because it allowed to filter messages by app name: menion.android.locus.pro.
The results of gynta's method 1 (working) are in log1.txt, while method 2 (non working which implies launching Locus) are in log2.txt.
In method 2, every time I tapped the "Add waypoint" button this line appeared:
but no dialog box asking for a name.
I hope it helps you somehow, but to me it doesn't seem an application debug log. Maybe because the app is not debuggable? I don't know.
Ah sorry, I've forget to answer yesterday. Gynta already send me a log with short video and I think I've found a source of problem. Anyway not sure how to solve it correctly, so I did a small "hack" let's say. When you add waypoint from widget, it will always display just a small popup dialog where you define it's name, nothing more.
Hope this will work a lot better = always.
Ah sorry, I've forget to answer yesterday. Gynta already send me a log with short video and I think I've found a source of problem. Anyway not sure how to solve it correctly, so I did a small "hack" let's say. When you add waypoint from widget, it will always display just a small popup dialog where you define it's name, nothing more.
Hope this will work a lot better = always.
Now it works here with 3.14.2
Anyway - why Locus comes in front after tapping "Add point" from widged? (in case i startet record inside Locus and minimize)
Now it works here with 3.14.2
Anyway - why Locus comes in front after tapping "Add point" from widged? (in case i startet record inside Locus and minimize)
Uff this was tough. I was finally able to simulate this problem on my tablet. It looks like some problem in Android itself, fortunately seems that one hack solved it. So in next version, another attempt. Thanks guys!
Uff this was tough. I was finally able to simulate this problem on my tablet. It looks like some problem in Android itself, fortunately seems that one hack solved it. So in next version, another attempt. Thanks guys!
Replies have been locked on this page!