On a 3-day tour in Thuringia last week, it happened to me several times that the MRA navigation jumped to the background for no apparent reason, i.e. suddenly only the start screen was visible. The navigation including voice instructions continued, but the screen display was gone and had to be brought back using the navigation buttons on the smartphone.
Is this a known problem?
This has never happened to me with other navigation apps (TomTom GoRide, Waze, TomTomGo, Kurviger). I therefore think a smartphone problem is rather unlikely.
I am using a relatively new Gigaset GX4 with Android 12.
Greetings hawebo
@hawebo honestly, that sounds more like an issue with the phone.
2010 GL1800 Goldwing using Samsung Galaxy S20 5G Android 13.
@RetiredWingMan I also initially suspected a hardware problem and therefore tried the navigation with other apps. I wasn't able to provoke the error even once.
Before I send the smartphone for a repair check, I wanted to ask here in the forum whether this error has already occurred?
@hawebo I say the issue seems the phone because it sounds like a screen sensitivity issue. Like a drop of water hit the screen or the phone holder caused a reaction. I suggest cleaning the screen and perhaps reducing the screen sensitivity in the phone settings if it continues to happen.
2010 GL1800 Goldwing using Samsung Galaxy S20 5G Android 13.
@RetiredWingMan Thank you for your help. It wasn't raining during my tour, so there wasn't a drop of rain on the display. The display has a screen protector, anti-reflective and anti-fingerprint. That's why the screen sensitivity is set to high and is in "glove mode". If this is the cause of the error, which doesn't sound implausible at first, I wonder why the error didn't occur with other navigation apps? Specifically, I tried TomTom GoRide and Waze during the tour.
@RetiredWingMan This week I will definitely go on another tour and switch off the "glove mode". I'll get back to you afterwards.
@RetiredWingMan The error (nav-screen suddenly jumps to the background) has now also occurred with another sat nav app. In the meantime, a defect in the display has been identified and the matter has therefore been resolved.
Greetings hawebo
@hawebo, thanks for getting back.
@hawebo thanks for the update. Glad to hear the issue is resolved.
@RetiredWingMan Thank you for your help. It wasn't raining during my tour, so there wasn't a drop of rain on the display. The display has a screen protector, anti-reflective and anti-fingerprint. That's why the screen sensitivity is set to high and is in "glove mode". If this is the cause of the error, which doesn't sound implausible at first, I wonder why the error didn't occur with other navigation apps? Specifically, I tried TomTom GoRide and Waze during the tour.
