GO app disappears on smartphone after unlocking the screen — TomTom Discussions

GO app disappears on smartphone after unlocking the screen

kasperx80
kasperx80 Registered Users Posts: 10
Master Traveler
Hi

I used the app mid of this year on german highway and hoped the app would behave similar to googles app maps.
In tomtom go I disabled smartphone screen while navigation to ignore screening and just listening to audio. When I then unlocked my phone again the app disappeared (and closed?) and I got to home screen. At that point the app was useless because I would have had to stop my vehicle to use phone.
On google maps the app just reappears after unlocking and within 1 secs updates the screen to show actual infos.

os: Android 10

Thanks in advance
kasper
Tagged:

Best Answer

  • dezmo
    dezmo Registered Users Posts: 91
    Revered Navigator
    Accepted Answer
    I can confirm this behaviour. I do have the "run in background " selected, but the app automatically quit when I switched of the screen e.g. for a short break for toalett...
    I always have to restart TT. Fortunately it will continue where it was.

    I'm on the last (3.3.31) version with Samsung Note 10plus (android 11)
    But, TT worked for me like this since ages.
    Even with version 1.8xx.

Answers

  • lampard
    lampard Administrators Posts: 5,740
    Moderator
    edited December 2021
    Hi kasper,

    Do you have an option 'Run in the background' (Main Menu> Settings> Other> Run in background) enabled in the app? I've not seen any such reports so far.

    Best, lampard
  • kasperx80
    kasperx80 Registered Users Posts: 10
    Master Traveler
    Thanks for answer.
    Correct, didn't know that. I will try that.
  • kasperx80
    kasperx80 Registered Users Posts: 10
    Master Traveler
    Next try :)
    Same (test) program, other (older) smartphone with android 7.
    Background mode is activated from default. Program stays in background within lets say 10 seconds after smartphone lock. Within those 10 seconds on smartphone rewaking the program reappears again. But after those 10 seconds smartphone requires screen relock and then user sees home screen. So program might be crashed. Then on program opening last route was shown again. I dont know whether I needed to start navigation or the program started automatically.
    However the program disappeared after x seconds on smartphone lockscreen :(
  • dezmo
    dezmo Registered Users Posts: 91
    Revered Navigator
    Accepted Answer
    I can confirm this behaviour. I do have the "run in background " selected, but the app automatically quit when I switched of the screen e.g. for a short break for toalett...
    I always have to restart TT. Fortunately it will continue where it was.

    I'm on the last (3.3.31) version with Samsung Note 10plus (android 11)
    But, TT worked for me like this since ages.
    Even with version 1.8xx.
  • kasperx80
    kasperx80 Registered Users Posts: 10
    Master Traveler
    Is this "problem" worth a support ticket or is this already sort of a ticket? (Do I have a chance to contact anyone from tomtom otherways (developer)?) (Don't know the details of this forum)
  • szachowa
    szachowa Administrators, Staff Posts: 469 Staff
    Hi, this is expected behaviour. Application will be not closed from recents when you are driving.

    I can confirm following from @dezmo
    But, TT worked for me like this since ages.
    Even with version 1.8xx.
  • kasperx80
    kasperx80 Registered Users Posts: 10
    Master Traveler
    @szachowa seems like you did not read this website.

    szachowa wrote: »
    Hi, this is expected behaviour. Application will be not closed from recents when you are driving.

    I can confirm following from @dezmo
    But, TT worked for me like this since ages.
    Even with version 1.8xx.
    -> Expected behaviour is program ending after locking?

    The answers say that the program ends or even crashes (some seconds) after smartphone (screen) locking. @dezmo confirms that.
    So your comment is a contradiction.

    Or did I read wrong?