Sorry to answering a bit late, to buzzy this week!
yes @paulakreuzer i set location to high accuracy, but i’m turning off the wifi to test only the GPS capacity.
After what you said, I try again my GPS with SaSat in a middle of the downtown (Lyon, France), and in the middle of a hudge place: after 3 or 5min, it work!
Usualy i tried in my street and it’s perhaps to “narrow”?
But it wasn’t realy accurate (20 / 30m) and i lost the fix after 200m by ridding my bike.
The next day i tried in a bus : can’t get any fix at all.
Today i tried in a place next to my street, and i get a fix after 2 or 3min, with a 6/ 8m accuracy. After walking around, it keep the fix, but lost accuracy, uppon 20m.
I reboot the phone to test the new TTFF, and it was realy fast this time!
I’ll try again in the weekend with a bike or a faster vehicule, but is this the expected behavior?
Now i’m not so sure now if the regular OS was working better: i realize that it was just the Google’s unifiedNlp Backend witch is maybe more precise that the Mozilla one…
No, not at all. I sometimes experienced similar behavior for short phases without any apparent reason, but usually I get a fix within <1min and an error of <3m.
Maybe. I don’t remember anyone having GPS hardware issues that didn’t result in a totally non-working-GPS. But everything is possible! PS: On the other hand if it works well on FP OS then it’s not a hardware issue.
Hey guys! Nice to see there are some workarounds here.
I was wondering whether someone tried these with GAPPS already? I’d like to have a functioning Play Store (mostly for apps like Spotify and Netflix, but also some more niche / local ones), but so far it keeps crashing when GPS is active.
A very nice alternative for the Play Store is the Yalp Store from Fdroid. It is small app with very little overhead. If you are only planning to download free apps (and are not using any other play services), there is no need for the whole GAPPS package.
I was just reading an article@Roboe sent in another thread and this part made me think about all the work we have to do to get location working on FPopenOS:
At Google I/O 2013, Google revamped the Android location APIs and released them as part of Google Play Services. In other words, Android’s top-tier location services are now closed source. If the above history is any indication, the open source location stack will be left to rot. The added features include the Fused Location Provider, a “complete rewrite” of Android’s location algorithms, Geofencing (which lets you define locations on a map that will trigger events in an app when the user enters them), and Activity recognition, which uses accelerometer data and fancy algorithms to determine if the user is walking, biking, or driving—all without turning on the GPS.
It made complete sense to put the Maps API and Google Cloud Messaging into a proprietary app, as those services depend on Google servers to function. However, moving over the entire location stack feels like a massive power grab on Google’s part. There are now two methods to get location: the good, low power, closed source Google way, and the crappy, battery expensive, open source way. (emphasis mine)
Yeah, this whole work to use location services is just for that. But, on the contrary of some people, I think this is good for privacy. You know, before that change, AOSP (the open source version of Android) used Google Services for location, even when no GApps were installed, because these location services where integrated into the system, and there weren’t any method to change it. That was bad. Now we can choose, .
The article is referring to the network location (proprietary on phones with Google Services) and the pure GPS location (open source on every phone). microG or UnifiedNLP (which doesn’t need signature spoofing) fill the gap of network location left by Google Services (when no installed).
Of course microG/UnifiedNLP is less battery-consuming than the whole Google Mobile Services (spying) framework.
A question: is the GPS problem with FP OS affecting everybody or just a limited amount of users ? (to understand if it’s a failure or a known software limitation)
I’m having a few issues with GPS as well. I tried a few of the fixes in the wiki (Faster GPS and SatStat), but still the GPS experience is sub-optimal. Most of the times I get a fix in a few minutes, which IMHO is still not satisfying as if you enter your car it’s no fun to have to wait minutes before leaving. Just as a comparison, a couple of other phones I used (a Samsung and a Huawei) usually got fixes in 10 seconds.
My question is: is anybody having -really- fast fixes with the Fairphone 2, both stock and open OS ? Thanks
I’m using EFIDroid to have both FP Open OS and FP OS (with all Gapps disabled) and on both I usually get a fix before the app that uses GPS finished loading (e.g. OSMAnd on Open OS and Pokemon Go on FP OS).
I have to add that I almost always start using GPS when I’m outside. When I start using GPS before I’m out the door or while I’m in a vehicle it sometimes takes noticeably longer.
This is my first message around here.
I just got my Fairphone 2, and after not even a week, I decided to escape Google and moved to Fairphone Open OS. I have now the version 17.01… And unfortunately, my GPS doesn’t work at all. (It used to work perfectly when I was on Fairphone OS, it cannot be a hardware issue…)
I already read a lot of answers on this thread, but didn’t manage to make it work.
Should I install OpenGapps? Why, what is that for? (Actually I tried using the updater, but it failed) I even tried to download Google Maps, but it doesn’t help…
I changed the settings in gps.conf, still nothing. Maybe I don’t do it the good way.
If someone around could give me a few steps to follow, it would be really helpful!
Thanks.
Thanks for your fast reply. First of all, I didn’t check this #gpsguide, my bad. I will do it, try your tips, and I will write you back then.
We talk later, thank you!
Ohlala Paul, I tried to read more carefully the wiki of the forum to understand how to setup my FP open, and I realised I didn’t do much so far (basically I just installed the OS). From one article, there is always a link hiding another article, and another… I will write you back as soon as I am ready!
Cheers
So!
First thing first, I tried with my normal Fairphone Open 17.01 to open maps (with OSMand, and Swarm) but nothing worked: a pop-up with “waiting for location” appears on my screen. Then I tried to download Google maps. Same thing. However my location settings is turned on, and set up on “High accuracy”.
So I installed FasterGPS. Entered in the developper mode to make it work. I set up my location to Europe and Netherlands (where I live). Nothing changed. I changed the advanced settings INTERMEDIATE POS to 1.
Tadaaa! Swarm recognised where I am! Humm wait, no… OSMand and Google Maps don’t. I download Waze to check, same thing. “Waiting for location”. I reopened Swarm, “Waiting for location”… Arf!
With “GPS Status & Toolbox” nothing appears, except the compass.
It seems there is another problem.
What could it be?
EDIT: I just tried with SatSat. Left my phone for 2minutes next to the window and it worked. I just hope this will work also when I am moving… We will see!
Do you have wlan enabled? I learned that location mode works (at all/way better) with wlan enabled (as it seems to be used somehow )
(I’m using opengapps)
.