Originally Posted by
Gary02468 ...Thanks, that was it. I thought I'd checked previously, but Maps was indeed on the optimize-battery-usage list. I'm not sure how or when it got there, but turning that off solved the problem.
I've found Samsung to be very all or nothing when it comes to some things and putting apps to sleep is one of those things. Just like the way I found this out it probably happened to you the same way. For me I got some innocuous notification that X was running in the background and like everyone that has ever thought about their battery life ever, I said yes to putting the app to sleep. What I assumed at the time to be a one and done just for today turned out to be a one and done forever. Not that I would have read it probably but if the warning I got in that notification had said anything about "this is forever", "this may affect the way the app behaves in the future", "hey once you agree don't expect this app to work in the background ever again" or anything indicating the permanence of this choice I might not have suffered for those 3 days but obviously that's not how it works. It would also have been nice if it was like everything else and given the options "just this time" or "always", I mean it seems to give us those options all of the time. LOL
Anyway I'm glad that worked for you. Still can't get over it happening to Maps but in Samsung's defense navigation is probably something that more people use with the screen on or at least with Maps open somewhere on screen, PIP or full screen, AndroidAuto something.