Samsung Active tab 2
-
@matt-flaming said in Samsung Active tab 2:
But to exit out of the application, you just use the back button (or gesture if you are on a newer version of Android). You don't have to kill the app in recents menu.
Yes, but then the program stays active in the background, it does not close that way. The theory here was that after a program-exit the routes would not be usable without internet connection. Keeping it live in the background does not simulate that.
This is such a convoluted matter that it’s little wonder there is confusion!
In my view, it shouldn’t be necessary to be discussing it at all, given that providing the ability to load routes onto devices to enable offline mode fully would be a complete cure…
However… With both iPhone and iPad, in relation to @Con-Hennekens’ last post, what I have found is the opposite. I know it seems illogical (to put it mildly!) but, IN OFFLINE MODE, I am unable to return to a route UNLESS I DO CLOSE THE APP COMPLETELY BY STOPPING IT RUNNING IN THE BACKGROUND! If I don’t do this, I can’t return to navigation from the “route overview” screen - I just get endless buffering.
My brain hurts.
