Version of /e/OS or Stock which existed previously: 3.1.3 a15 (Ron’s latest unofficial build)
Is the device Rooted / Not rooted: Not rooted
*In order to downgrade from the unofficial build 3.1.3 (thanks to Ron) → Official 3.1.1, I used TWRP (TWRP-3.7.1-mondrian-09-02-25) & adb sideload (after switching the slot & rebooting to TWRP)
It’s working great, so far I have not encountered with any problem… except that I haven’t used App Lounge for sometime due to its problem mentioned here (using Aurora & F-Droid most of the time)
Hi,
I got my device with e-os preinstalled about a month ago and ever since it got it I’ve had problem with seemingly random reboots. The system would just shut down and start back. I realized, that it keeps happening on long write operations over the internet – when I download something big. I tried to download the newest update via the updater (3.1.1-a15) and it took me a few tries because the device was rebooting. Synchronizing via syncthing, downloading with firefox, copying files around with file manager also causes reboots.
The issue persists even after the update and it makes my phone rather unusable. Is there a way to fix this without returning the entire phone?
It is very sad, that update with IMEI problem is still available.
In my understanding the 3.1.4 is coming very soon (I am expecting today, but no guarantee), which fixes the problem. There is many other smaller fixes as well.
thanks for the information and links.
these explains the challenge for /e/ to propose some relatively cheap phones, as CMF-phone1, Teracube2s or even Pixel-7 : how long can thses be folowed ?
I do not have v3.1.1, but 3.1.2. My feedback is regarding 3.1.2 (I did not find a better thread for this).
I have update to it around 3rd or 4th of September, and the current version is now 3.1.2-a15-20250903521531-official-FP6
Vendor name: Fairphone
Device name: FP6
Device CodeName: FP6
Version of /e/OS or Stock which existed previously: I am not sure but I think it was 3.0.4. It was something from mid June or Mid july, which came as default when I bought my FP6 via Murena on mid/end August
I didt not root the device
After the update, battery life halved: Before I would charge in the morning, use the phone as much as I wanted: Browse, watch bravePipe, use Tor, chat, jellyfin, etc, and the next day morning I would still have 65% battery. On the next morning it would be at around 35%. Thus, lasted 2.5 days
Immediately after installing the update I saw battey was used much more, and now if I charge in the morning, and using the phone much less than before, on next morning the battery will be 35%
This, consumption went to 35% per day to 65% per day, almost double.
Besides that, the Moments switch dont work anymore.
I do not see any other updates avaiable and I would like to rollback. How to do that, @manjoj?
3.1.4 is being rolled out right now as a staggered release (as usual).
To try to skip the line, you can hit the refresh button of the updater several times.
You do a new install, wiping your data. Android doesn’t like to be rolled back otherwise for security reasons.
Personally, I will continue with the gs290 for one year, with some quite basic usage as you describe, as long as /e/OS offers new official updates (I feel an A13 upgrade very hypothetic). The only application I have installed is Editor (local), as a replacement of the “clouded” Notes.
After that year, I will look for a new “murena” phone, with official /e/OS, and with a long time perpective. It depends on the phone-Vendor, on Android-Aosp, Lineage-OS, and e.foundation.
I will take the risk, as I have experimented a FirefoxOS-phone 4 years without any update nor patches.
The risks could come from hazardous browsings, from clicks on spams, or installation of weak applications. Direct attacks against the phone through internet, using leaks of the old-version of the OS, should have low probability. What else ?
I’m on 3.1.3 and battery life seems back to or better than before. But I have my location service turned off because of the bug in 3.1.3. Probably best to (im)patiently wait for 3.1.4
I never saw the 3.1.4 when insisting in the refresh button. I only saw it when I activated the “test channel” in developer options. Is it safe to install 3.1.4 (not the beta) from this channel or should I wait for it to show up in the regular channel? I’m anxious because I’m with no mobile network at all (only wifi works)…
Another question, if you could help me: the OTA update writes itself to the A/B inactive partition, right? I ask it because I saw the installation shell script writes in both partitions, and this would affect the way I can install or maintain root.
On reflection, of course there were requests for testers so I guess if you were to follow the testing guidelines you could ask there whether this particular testing is suitable for a phone in regular use, mentioning whether your bootloader is locked, is it going to be ok switch between testing and regular builds later. And / or perhaps you are ok with clean installs once or twice. FP6 testing seems to be in progress by private message within the Testing Telegram group.
I’ve been following this thread since the beginning, and I still haven’t upgraded my Fairphone 6 with 3.0.4-a15 with the new update (3.1.1, 3.1.2, 3.1.3). In fact, in “System Update”, I get erratic information sometimes, saying “there are no updates” or showing the update to 3.1.1. (I’m in Poland, and I bought the phone with Android and installed /e/os myself).
I’m pretty happy with 3.0.4. Everything that is important for me is working fine - i’ve installed all the apps I need and even my banking app works (camera zoom is not working, yes, but that’s not really an issue for me).
I’ve read that there are a lot of problems with the 3.1.1 update, and that there were two emergency updates after it. So my questions are:
Why am I getting, sometimes, the information about the 3.1.1 update and not the 3.1.3, which I think is the last one? Do I need first to update to 3.1.1 to get 3.1.2 and then 3.1.3?
When the 3.1.4 will come out will I be able to update directly from 3.0.4?
This simply reflects the release, withdraw, release, that has proved necessary with fp6.
You are in control, it has proved wise not to have installed in the first flush. Many users just do not update from a nicely running version until they see good reports.