Moto G5+; OsmAnd+ 2.75; offline downloaded map - California, Aug31 2017; safemode
I am just learning smart phone use and starting with OsmAnd - so I don't do things very efficiently and may not be using the app in expected ways. But. This morning after OsmAnd had been running for about 2 hours, when trying to define a route (not moving, before I started driving) I repeatedly got a loop where the screen changed orientation from vert to horz and back at about 2 Hz when I selected the Go at the bottom of the dashboard route entry dialog; or sometimes it started when I selected the "To" item on the dashboard routing menu. When this happened, each time the screen flipped it displayed a black/white time display in large numerals in the top or left half of the screen, depending on the new orientation, with a large white box below/right, for about 1/2 second; then the usual map display appeared for 1/2 second, then it flipped back and so on. Sometimes changing phone orientation (physically) stopped the loop while other times it did not. Screen touch control appeared to not work during the loop. Sometimes this happened after starting to drive and in that case routing announcements continued ever though the screen was going crazy, flipping back and forth. When I couldn't get control back by touch or changing phone orientation physically, I had to manually power off the phone and this took much longer than usual - as if a lot of cpu power was being used elsewhere. The fingerprint sensor on this phone which works also as a left-swipe/right-swipe/press control did not function while the screen was looping. So far I have not experienced this at any other time with the phone and trying it again later while stationary I can not repeat it. I have used the camera, a file mgr app, Chrome browser app, a photo app (rename, move, etc photos) w/out experiencing this problem at all - screen orientation changes as expected. I usually navigate app menues in portrait mode but do text entry in horz mode so I change orientation a lot. It may be hardware but since it has only happen with OsmAnd and then only when defining/activating a route it seems strongly possible that it relates to how OsmAnd interfaces with the screen orientation API from w/in the routing function(s). If it's not a direct hardware fault then presumably it's some kind of timing issue. Just throwing this out so there's a data point if anybody else runs into the problem. I will continue to try the routing when I drive and see if and how often this occurs. I just had a thought: What happens when upon arriving (maybe parking before one quite arrives and thus not ever hitting the final arrival point) one does _not_ dismiss the route but simply continues (shopping, parking, driving to next errand, etc) for a couple hours before getting back to OsmAnd and attempting to define another route? Does it continue to try to recalc and maybe fill up a queue or something? Rufus -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
