GPS in AppSupport works only once

REPRODUCIBILITY: Always
OS VERSION: 5.2.0.16
HARDWARE: JP2026 with stock AppSupport and preinstalled MicroG
UI LANGUAGE: GER
REGRESSION: (Yes)worked on my Xperia 10III

DESCRIPTION:

When using OSMand or Enroute Flight Navigation a GPS Fix i quickly found, but when moving the position is not updated any more.
Using Pure Maps or OSMScout it works flawlessly

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. Start Android Apo

  2. Wait for gps Fix

  3. Move around

EXPECTED RESULT:

Position should be updated

ACTUAL RESULT:

Position stays unchanged, even when moving. In Enroute the Position marker gets grayed out, meaning no GPS Connection.

MODIFICATIONS:

ADDITIONAL INFORMATION:

1 Like

Thia doesn’t affect all android apps. I think this is related to the GNU bug we are currently seeing in some apps, but just a guess

2 Likes

Ot definitely is. Just tried again with HereWeGo: if it hangs just tilt the phone into landscape mode and it refreshes, hangs again, tilt tbe phone back to portrait mode and it refreshes… It is THE bug.

BTW just tapping he screen has thr same effect.

In Enroute I get a fix once, GPS Signal is received on startup. When I watch the status page, for the next try I get no GPS available. Leaving the app towards the Panel View and maximizing it again gives another single fix.

Changing orientation does nothing for me.

Can somebody point me in a direction what logs to check? I found nothing primarily interesting in journalctl or lxc-attach logcat.

I’m having this bug too. For those gps android apps that actually work, I can use them only after a fresh restart of AppSupport. If I use them some time later, they get the correct location at startup, but no update, as said in the first post.

This an unrelated bug, in my opinion. I have it with Google Maps, and it is quite unusable for this reason.

I explored a litte further. When using OSMand, I get my location once and it is never updated.

Using GPSTest from FDroid I see that my location is aquired once, then after some time lost and than first a “coarse” location is aquired (I think by cell location) and then correct GPS Location. In logcat journal I didn’t see anything that caught my attention.

Can anybody give my a direction how to explore further?

I thought the GPS problems I had with my Jolla Phone 2 were sorted, as the GPS Info app now quickly gets a location fix (performing similarly to my Sony Xperia 10 III).

But I got a nasty surprise when I tried to use a GPS Android app. While GPS Info got a fix quickly (say 30 seconds), the Android app took ages (5-10 minutes?) before it thought it had a location… and then once I started walking around, it immediately lost the GPS fix, and mostly refused to get one again. It’s seemingly only able to occasionally briefly get a GPS fix if I am stationary for ages, and that’s extremely intermittently. Even though GPS Info still reports a great signal!

I am seeing the exact same problem with both Locus Map & CoPilot GPS. And probably other Android GPS apps (like HERE WeGo), but those two give detailed GPS data (esp. Locus Map), so they are easier to check. Locus Map shows it can see lots of GPS satellites, but they are virtually all red i.e. a very weak signal (unlike on my Sony). I’ve tried leaving Android GPS on for 0.5-1 hour, even outside, without any improvement.

What is really weird is that both Android apps work brilliantly on my Sony Xperia 10 III (and I do really need those apps). I had bought the Jolla Phone 2 with the expectation it would work just as well, so it’s really frustrating to discover that GPS basically doesn’t work at all on Android apps.

Has anyone else noticed this problem with their Jolla Phone 2? (I checked all GPS settings on SfOS, Android settings, and MicroG, without luck, so I doubt it’s a user configuration issue.)

I encountered the same problem

Yet I have no idea how to investigate further…

Same here also, used with magic earth, organic maps and blitzer.

I have the opposite experience. Here Maps e.g. works like it worked on the 10ii (only for GPS, the usability is much worse…), Blitzer.de Pro works like on the 10ii, but the AlpenvereinInteraktiv-App works much better. While on the 10ii I had to restart the app to get the exact point where I am, hopefully - while using the J2 actualize the location often enough to use it as a tool for hiking.

After 2 weeks of daily usage, I can say that it is not happening that often. It happened to me 5 or 6 times and it was solved after a restart of AppSupport. I couldn’t find what is causing this bug. It is completely unpredictable.

That’s weird, assuming you are talking about the Android version of HERE WeGo, rather than the ancient native SfOS version.

  • Are you running the latest version of SfOS on the Jolla Phone 2? i.e. 5.2.0.17 (Finlayson)?
  • Do you have MicroG installed? And if so, is it from the Jolla Store (as it’s done if you choose to install it during phone set-up), or from F-Droid?
  • Which version of MicroG do you have installed? (I have 0.3.15.250932 from F-Droid.)
  • What settings do you have in Settings > Location?
  • What settings do you have in MicroG > Location?
  • Do you have GPSInfo or other native GPS apps installed? (Maybe they somehow interfere with AAS GPS?)

I think that’s an entirely unrelated bug report, where they are talking about the whole app’s display freezing-up (not refreshing), rather than the GPS location itself not updating.

I disagree. The app stays reponsive, I can scroll the map but the blue (fix aquired) position dot in Osmand turns to a gray (last known position) dot. So I think its the same problem.

I have the latest 5.2.0.17 Release, Stock Micro G from Jolla during install without any changed settings. Other AAS GPS Apps show the same problem, but the problem persists with and without a native GPS App running

1 Like

Same issue I reported in the SFOS issue tracker on GitHub

1 Like

Thanks, I misunderstood that bug report, due to some people mentioning Google Maps (which suffers a seperate bug).

I would be happy for moderators to merge this thread into that one.

Of course I have the most recent version of SFOS. MicroG installed from Jolla-Store.

For Here We Go, it helped me to install an old version with aurora. I went back to 4.16.200 (8234030). Works flawless since then. I don’t accept updates - I tried different older ones but only from this one everything works as it should.

Yes, I had to install an old version of Here WeGo (v4.17.200) to solve the problem with it’s Settings screen freezing (not updating), which is probably related to the graphical freezing seen with Google Maps on the Jolla Phone 2. However that didn’t solve the GPS problem.