Short backstory: my FP2 was getting more unusable by the day (random reboots up to 20x a day, freezes, glitches - I thought the GPU was dying). With the latest Upgrade to Android 9 (FP Open OS + Open GApps) it runs mush smoother now. Almost no reboots. Every now and then a single app crashes, but that’s ok.
My problem now is the GPS function/hardware. I’m using SatStat, OSMand+ and GPS Logger (https://gpslogger.app/). With Android 5-7 I always was quite fond of the accuracy and battery performance of the FP2. I usually have location disabled. When I go for a bikeride, I usually activate location, start SatStat to get a fix (this still works pretty good) and start GPS Logger afterwards. When I’m lost, I open up OSMand+
On my last tour, I wanted to have a look at my position in OSMand+ and noticed that the back of the FP2 was very hot. The location indicator of OSMand+ also somewhere behind my real position, although blue in color, saying it had a fix. After riding on, the indicator stayed at the same place, so something was wrong. I also noticed that the total distance in GPS Logger was way too low. SatStat didn’t show any sign of a working location service. At home I was curious about the GPX file and saw that after around 35min the track just ended. I tested the GPS Logger on a car and train ride with the same result: FP2 gets hot, logging stops after between 35-40 minutes, every time.
At first, I thought UnifiedNlp could be the cause of the problem. I never used it and now it was preinstalled with FPOOS. Indeed, I got the error “UnifiedNlp has no last known location” so I tried The LocalGsmNlp and Mozilla Backend which just caused my FP2 to freeze when opening up GPS Logger or SatStat so I deactivated UnifiedNlp but my main problem with the loss of a GPS signal after 35-40mins persists.
When I have GPS Logger turned off and only look for my position in OSMand+, I get a fix real quick and have no problems even after hours. I imported my performance settings and I couldn’t find any related bugs on Github so I’m not sure if it is a GPS Logger problem, a problem with some background services or with my hardware.
It’s a pretty long post so thanks if you read this far
Does anybody has a common issue or a clue what the cause of this problem might be? I’d love to be able to track my rides and hikes again.