Hello, I know this is a known bug (e/backlog#8871) but I thought I should add my voice just to let everyone know that it is still a problem. Location tracking/GPS has a very erratic behaviour, ranging from not finding me at all (rare), to getting the wrong position (extremely common), to working properly (sometimes).
Vendor: Fairphone
Device: FP3
CodeName: FP3
Version of /e/OS or Stock which existed previously: not sure, I suppose it’s 3.1.3
Is the device Rooted / Not rooted: not sure, the only thing I did after flashing the /e/OS ROM from the website was locking the bootloader.
Happy to provide any other info, and thanks to the /e/OS team for all the work they’re doing.
Vendor Name: FairPhone
Device name: FP4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 2.9-a14-20250321478214-official-FP4 (always normal OTA updates for me)
Is the device Rooted / Not rooted: not rooted
I just updated /e/OS and after that I also updated all the apps from the App Lounge.
So far, so good (with my limited knowledge it would take quite some time to notice eventual issues).
Thank you very much to all the Team for the good work!
I just got a new Fairphone 6 with /e/os 2 days ago, updated the phone and installed some apps. It reboots randomly even when i am not doing anything. I turned off the location services as some suggested and it hasn’t rebooted by itself for 24 hours. Is there any way i can provide logs for the devs to help? Or should i just return the phone and get something stable?
I have not been able to catch a reboot while on adb debug.
It’s difficult to leave the phone connected to USB-C when it’s your daily driver.
It had not rebooted for 4 days and it just rebooted this morning as I was about to use the phone (and therefore stopped the adb usb connection). I had been stationary for at least 10 hours.
I am currently in labrador city, canada.
I am crossing over to quebec today and there is a 1h time difference between here and there. I will launch adb and see if the revoot occurs as we change time zone.
I have one physical SIM with TELUS and one eSIM with Kodoo. But the reboot problem existed already when I only had one physical SIM with TELUS.
I just attached the intentional manual reboot adb logcat to the issue.
Today I’ll be changing timezone while driving, I will launch the capture before I leave and stop it when I arrive or event leave it until it hopefully reboots.
Yet sometimes it does not happen for 4 or 5 days. Hopefully it will have rebooted unexpectedly soon.
Since turning off location services on my brand new Fairphone 6 there has been no reboot so it seems like it might have something to do with it.
Since i see people talking about traveling causing the reboot, in my case it just happens randomly when i am at home. I just got the fairphone 6 two days ago and it runs the latest version of /e/os i haven’t been anywhere else then home with this phone.
EDIT: Maybe i “have” been somewhere else because i used the fake location
Hi!
I also have a Samsung S10e currently on 3.1.4-15-community. I have recently updated from a very old version (1.19 / Android 12) and now I have issues with Play Integrity, maybe causing issues with my banking apps. Do Play Integrity checks succeed for you?
Still not being offered 3.1.4, only 3.1.1. I know FP3 official always comes at the end of the release cycle, but it seems well beyond that now.
I’ve tried the refresh button numerous times, clearing cache & storage of the Updater app, rebooting and still only 3.1.1 offered. An earlier post here says there’s no need to update to 3.1.1 first.
Not wanting to wait any longer for v3.1.4 to be offered OTA I updated from v3.0.4 to v3.1.1. Immediately after the update I was offered v3.1.4, which I’ve now installed and am testing.
@manoj please could you clarify about missing a version when updating OTA. In both 3.1.1 and 3.1.4 feedback I think you’d said that update from 3.0.4 direct to 3.1.4 would be possible. I’m sure I’ve missed a version before and had a later version offered in the updater. On this occasion that clearly didn’t happen.
Edit: I’ve just noticed in Updater ‘Preferences’ that 'See all available updates’was turned off, presumably as I’d cleared storage. But I only cleared storage yesterday so I don’t think that can be the reason I’d not been offered 3.1.4 before that.
Fairphone 3+
FP3
Update from v3.1.1-t-official to v3.1.4-t-official
Not rooted
Update completed in 47 minutes with no issue other than one break in downloading, 10 minutes longer than usual.
Initial testing of basic functions & apps shows these appearing to be working fine: wi-fi, mobile data, bluetooth, phone, message, mail, browser, App Lounge (common apps, except install not yet tested), and various other apps.
GPS obtained an accurate fix in 3-4 minutes, but haven’t had chance yet to test any further.
Missing a version or two before an update does not matter as each update has all the previous code.
The only exception is when we are releasing an OTA OS upgrade build. That is say, upgrading a device from A13 to A14. Then it will be mentioned in the release notes or on this forum that you need to install v 3.x of A13 to get the next build which would be on A14.
Thanks for this useful clarification @manoj. My main concern was that while on 3.0.4 I was not being offered 3.1.4, only 3.1.1, and so I was unable to miss a version. However, as soon as I updated to 3.1.1 then 3.1.4 was offered.
Perhaps ‘See all available updates’ in Updater preferences was turned off even before I cleared storage, although I can’t remember ever turning that off and I have skipped a version once before, albeit quite some time ago, so presumably it must have been on then.
I’m on this build since a few weeks and most things work well EXCEPT for, yes, AGAIN, the anonymous mode on the app lounge has broken. I can’t display ‘common apps’ anymore…
Hello, thank you very much for e/os ! Here is my details :
Vendor Name : Fairphone
Device : FP3
CodeName : FP3
Previous e/OS version : Unknown, I install back up as soon as it is available in the manager though
Not rooted
I know it was already mentioned, but I experience trouble with GPS location. App like GPStest or GPSstatus cannot find satellites at all and when I use a navigation app, location jumps from fixed point to fixed point.
However, I want to mention that, although this problem seems present since 3.0.4, I was able to use location perfectly the 2025-09-20 evening. I find this strange, since my version at this moment was probably 3.1.1, that is, a version experiencing location bug on FP3 as far as I understand it.
Anyway, I made the update some day after this evening, and I cannot expect normal behavior since.
Hello,
only now I had the time to upgrade my FP4 root from 3.1.1 to 3.1.4, but I see that in the USB Debug USB settings there is no longer a USB Debug ROOT switch.
What can I do to get it?
