There is no answer there? isn’t it?
Question was how can we ask the Dev team. That’s how, but yes, I don’t see an answer up until now either.
Hi all,
I’m “happy” to see I’m not the only one to be affect by this issue. I’m experiencing this problem too and it is always way to long to get my location, to be useful in any ways.
Does you guys know if it is FP3 only related ?
Will remind the team members to check and assign a milestone to fix.
Fix for this issue would be coming as part of the next release - v3.3. Issue is to move under development. ETA 1 month 
Thanks a lot ! Hope so
No, I have a Sony smartphone, and have the same issue.
Hi @Manoj 
Do you have any news ?
Did you update to 3.3 ? And how it is ?
I checked it right now on my FP3 3.3-t. It’s not at all fast but it works. To get a position it took me about 2 minutes but then I had it. So it doesn’t generally not work. There are at least conditions for not working.
Probably it’s a good idea to update the satellite data (AGPS data) once on devices where it didn’t work for a long time. This update gets actual informations about the currently usable satellites from a network server.
And we cannot say it often enough: clear the cache of all apps (including all system apps and services) after each update.
The issue doesn’t seem resolved yet … https://gitlab.e.foundation/e/backlog/-/issues/8871 … I thought I also saw a forum post confirming this somewhere, but I didn’t find it quickly now.
That being said, location still works for me. Location fixes are not as fast as they once were for me behind windows (e.g. in cars or trains or indoors) but location will work eventually as expected, and out in the fresh air I can’t complain even if with paying closer attention I feel the count of used satellites is lower than in the past, but of course I didn’t take notes in the past to compare to.
There’s actually something interesting to try in the GitLab issue … https://gitlab.e.foundation/e/backlog/-/issues/8871#note_779194
And it mentions something which I encounter in Android since I use Android (which is since Android 5) … showing me old positions initially before establishing a new location fix. I always thought this was Android just being weird on purpose, but I will have to test the setup mentioned in the link.
Yes, finally for me, since I moved away from my city, the GPS doesn’t fix anymore whatever the tricks described here or in the gitlab.
Different device but following a move GPS was poor. I checked that I was using Settings > Assisted GPS. Turned it off. At the time I failed to check where to delete the stored data and only remembered to switch on again much later. Both changes helped.
e/OS 3.4 on FP3+ with SatStat app: outdoors, sat fix works after a few minutes and enough satellite strength indicators switch from red to blue. FP3+ is less sensitive than FP4 but location at least is available outside. Map apps position correctly.
It does not fix always. Being outdoors today I had a lot of SatStat satellite strength indicators (all networks GPS, Glonass, Beidou) staying red although they showed very suitable values and should have turned blue very soon. I requested AGPS data update - no improvement. It stays very unreliable.
Well, this is very weird. Back with 3.1.4 it would take a while to fix and sometimes the position would be a bit off (e.g. the other side of the road), but it would work. At least since 3.2 it would straight up not find me at all every time I tried (not often tbf). Now I’m on 3.4. I did test it right after the update and it was still unable to find me. Until… A couple days ago I was in a part of town I didn’t know and got frustrated. Fired up the GPS without really expecting anything. It immediately worked and in less than a minute it had an accurate fix. No idea how to explain this. Happy to carry out any tests which might help understand this.
Not working on 3.5 official either.
My FP3 is now running 3.5 Official and everything is ok. GPS Apps are working well. Magic Earth is ok. I have tried Waze, location is ok.