Hardware Controller: WunderLINQ Escape key no longer works.

Keith Conger shared this problem 3 months ago


I'm the developer who worked with Menion to add WunderLINQ support.


We had a mutual user report that the ESCAPE key code no longer launches the WunderLINQ app with "wunderlinq://".

I've confirmed I see the same thing when the hardware controller is set to WunderLINQ in LocusMaps 4 and Classic.

Replies (4)


Hello Keith,

interesting, I see no reason why it should not work as expected > no changes in the part of the app. All other buttons except "ESC" key work correctly?


Hi Menion,

I hope you have been doing well.

All other buttons do appear to work fine, it's just ESCAPE. I tested with hardware control and ADB commands. I believe it has something to do with launching our URL.

I see this message in logcat when Escape is pressed:
java.lang.UnsupportedOperationException: This isn't a hierarchical URI.
at android.net.Uri.getQueryParameter(Uri.java:1720)
at o.NR.IconCompatParcelizer(:78)
at o.NR.write(:48)
at o.vU.onStart(:72)
at o.SyncFailedException.onStart(:218)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1510)
at android.app.Activity.performStart(Activity.java:8315)
at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3701)
at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2308)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7898)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)


Hi Keith,

I'm fine, believe you as well :).

Uff, I was searching for some complicated problem and in the end, it was simple. New Android API disabled the option to search for other apps (packages). But there is an option to hardcode a list of visible packages for Locus Map, so I've added the Wunderlinq app to this list and it seems to work now! So in the next app version, it should work as expected.


Thanks for the quick response, I've passed this on to the user who reported it.

Leave a Comment
Attach a file