I am back on the official FP3 2.9-t release. When I got the Fairphones many moons ago I made sure to immediately apply for the OEM unlock codes. I applied them to both phones just in case. From what I remember, the unlock codes are asked for when you try to use OEM_unlocking in the Developer Menu. Once the codes are installed it appears you can unlock the bootloader any time with the command line tools and the telephone in fastboot mode.
I was in a hurry to get the phones back up and running so I did NOT look into recovery options and missed the option of switching slots.But I have also seen feedback on the net which suggests that switching slots might not have worked. Suffices to say that even if I had found the option to switch slots, the crash seemed so severe and far-reaching that I would still have done what I did. In situations like this I am a big fan of not asking questions and finding the most elegant solution to get back up. Instead I typically roll over a broken OS with a known, sufficiently well working OS. And the phones had factory reset anyway, so that data damage was already done. Nothing to lose.
If you ever plan to lock the bootloader, be aware that data will be erased and a backup is needed (just stating it all the time for others who donât know)
Everything is working well except the two new features:
Find my devices does not send back any SMS on my phone (works well on the two other phones that I have access to). Could it be because I have two SIMs ? Has anybody else reported this issue as well ? I have created a git issue.
Murena voice to text has a small bug with keyboards that use several languages and a earth icon to switch from one language to another. After using the voice to text function once, the language selection icon (earth) activates the murena voice to text function as well instead of switching the language. A workaround to still change the keyboard language is to long press on the earth icon, when doing so the voice to text does not trigger. Do you know if this bug has been reported ?
Vendor Name : Gigaset
Device name : GS290
previously : /e/OS 2.9-s
rooted ? as delivered by e.solution (2021)
The update to /e/-OS-3.01-s succeeded;
no problem at this time.
Thanks for the struggle of âthe /e/-OS-Teamâ
brieucs.
PS, now for 3.xx :
âSadly AOSP 12 (/e/-OS-s) no longer have Android-security-patchesâ.
(( I have used a firefox-OS-2.2-ZTE-phone for 5 years without any update, nor accident apart short battery ))
PS2: ota-community for GS290 is still 2.9.
Update for Teracube 2e emerald. 3.0.1 official sideloaded successfully! Typed this message from my phone. I donât appear to have battery level issues like some others seem to be having. So far so goodâŚ
I never got the message, âInstall completed with status 0.â nor the prompt to reboot. After about an hour of being stuck at at line, âStep 2/2,â I took a chance on tapping the back button and then I got the prompt to reboot. After that, appears to be good as new!
For me, FindMyDevice puts my phone (Fairphone 4, /e/OS 3.0.1) two blocks (maybe 500 meters) away from its actual location. Thatâs not going to be terribly useful if I lose it or it is stolen.
Is this a configuration issue?
I always run Proton VPN. âUse precise locationâ is activated in the FindMyDevice settings. Under App Permissions, Location permission is set to âAllow all the time.â Nearby devices permission is set to âAllow.â Location services in general are set to Wi-Fi scanning âOnâ and Bluetooth scanning âOn.â
At the e/OS level, âFake geolocationâ and âHide IP Addressâ are both turned off.
Anyone have ideas about other settings that may be messing with the accuracy of my FindMyDevice results?
Vendor Name : Oneplus
Device name : 11 (CPH2451)
Device CodeName : salami
Version of /e/OS or Stock which existed previously : e/OS 2.9-a14
Is the device Rooted / Not rooted: Not
Upgraded directly from 2.9 to 3.0.1 and everything seems to be okay except a bank app that no longer works (could be the app, as two other bank apps work okay). I get the error âWe are unable to display your information at this time. Please try again later.â
Did get 3.0.1-s xxxxxx official, last night.
Did a test and gps seems to be working in airplane mode.
Have to mention, the S7 has not the fastest GPS, can take a long time, 20-30 min, to get an decent GPS fix, when running after an update.
Can use the app GPStest to see.
Fairphone
FP5
FP5
/e/OS 2.9-t-20250321478215-offical-FP5
Not rooted
Still on 2.9, 3.0 was never offered to me via the Settingsâ Updater, now I am waiting for 3.0.1 while I note that other FP5 owners have received both the one and the other update.
Anyone else experiencing this? Am I missing something?
A much simpler solution is to download an appropriate 3.0.1 image from your phone and use âLocal updateâ option under Settings / System Update / 3 dots menu.
No ?
