Feedback for v3.0

/e/OS Smartphone Operating System Build Feedback
349

Plesase excues my laziness to check in the posts before :see_no_evil::see_no_evil:

As @AnotherElk stated hit that button atleast 5 times :grin::grin:

The files for Official and Commumity are online.

350

First there was 3.0, which got retracted because of considerable trouble, which could have resulted in devices updated already, and devices still waiting.

Then 3.0.1 came, and official or community build type made a difference in the past few days, because 3.0.1 came for official first, then for community just recently. But now the FP3 update files are there for both build types.

@aibd’s hint still applies, if not done already …

351

Same as yours (Galaxy S7 “herolte”).
I rolled back to 2.9 (from 3.0), because of the GPS issue. Couldn’t use my navigation without Wi-Fi on Airplane Mode. Can you confirm if this is the case with 3.1 release? My problem was that on Airplane mode I wasn’t able to see the satellites, thus not able to use maps in offline mode.

352
  • Vendor Name: Fairphone
  • Device name: FP5
  • Device CodeName: FP5
  • Previous version of /e/OS: 2.5 T
  • Installed version: 3.0.1 T (OTA)
  • Not rooted

I’ve waited for a while to update to 3.0 as I depend too much on my device for breaking issues. With 3.0.1 I was able to OTA update from 2.5T to 3.0.1T and everything seems to be working.

353

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.

354

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)

1 Like
355 
  • Vendor Name: Fairphone

  • Device name: FP5

  • Device CodeName: FP5

  • Version of /e/OS which existed previously: 2.9U

  • Not rooted

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 ?
356
  • Vendor Name: Murena
  • Device name: Fairphone 4
  • Device CodeName: FP4
  • Version of /e/OS or Stock which existed previously: 2.9 official
  • Not rooted.

Downloaded v3.0.1 - quick download & reboot.
No issues sofar :star_struck:

Thanks to the development & testing team💐

UPDATE : MAIL APP keeps on closing without a reason :man_shrugging::man_shrugging::man_shrugging:

357 
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.

358

you were lucky, mine was dead after 18 months… in 2017

359

I still use it sometimes as radio-FM :wink:

2 Likes
360

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!

THANK YOU TO EVERYONE!!

361

no such issue on my 3.0.1-s-20250609498926-official-herolte
gps works flawlessly (no wifi + airplane-mode)

1 Like
362

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?

1 Like
363

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.”

364

Hi there.

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.

1 Like
365

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?

1 Like
366

did you try to hit the refresh button several times ?

367
  • Vendor Name: Fairphone
  • Device name: 4
  • Device CodeName: FP4
  • Version of /e/OS or Stock which existed previously: 2.9 A14 Official
  • Is the device rooted: Not rooted

All my usual apps works as expected on 3.0.1.

1 Like
368

I did, but thanks anyway. I will give it another try tomorrow, feedback following.

1 Like