This object is in archive! 

Freeze after changing point type, keyboard and dialog problem

R3gi shared this problem 6 years ago


I found a bug, which unfortunately occures only occasionally, but IMO it's good to know about it.

Steps to reproduce:

1. Open Route planner

2. Add new point

3. Tap that point and select "Change to via point" from the context menu

4. Observe the bug:

The virtual keyboard is displayed and the app freeze, eventually with ANR dialog. User might move the map, use buttons on map, add/remove new points, interact with the keyboard (without visible text, of course) – everything with opened keyboard. When user hides the keyboard, the app freezes.

After some time the "Change to via point" dialog may or may not comes up with option to rename the point. The keyboard may or may not be hidden in that time. Typed text is recorded in the text field.

After tapping Cancel in the dialog, the keyboard is not hidden together with the dialog.

As I said, this issue happens only in some cases, so it can be quite hard to catch it.

However I assume this isn't an expected behaviour, is it possible to fix this problem?


Sony Xperia Z3 Compact, Android 5.1.1, rooted (no critical system changes), Locus Map Pro 3.28.1

Replies (3)


Good day,

topic that starts with "occures only occasionally" is immediately moved to category "later", so sorry for a delay in response :).

Just trying to simulate this issue on own SGS7 and Z1C devices (also A 5.1), but unfortunately on none of this such problem happen.

I'm sorry, but without exact steps that leads to this problem or visible crash in app, it is almost impossible to fix this. Mainly it is interesting that I have no more reported similar problems, so maybe some issue in custom rom? Hard to say, really. I'll be watching this problem more carefully.



after more then half of the year, I personally never saw this problem on any of my devices (stock ROMs, mostly not-rooted) and also did not get any other bug report.

If same problem still happen, please try to create a bug report by this method: . It is possible that in log will be any useful information.

Anyway most probably I won't be able to solve such random unpredictable error, sorry.


Hi Menion,

since I'm no longer using Locus nowadays, I can't debug or tell if the bug is still present. As I wrote, this issue is hard to catch, so let's close this ticket until someone experience this again :-)

Thanks for your support!

Replies have been locked on this page!