Feedback for v3.0

[Jets]

Feedback for v3.0

very complicated for non geeks! won’t be able to do that. We need a SIMPLE solution!

This is how it always been. Not sure how you got eOS on you phone in the first place.

[swarfendor437]

FP3+ updated to 3.0.1-t-20250606498724-official-FP3 a couple of days ago. Only annoyance I get when using keyboard on another forum that uses Discourse is the voice input feature (voice to text). Any way to turn this off?

I think it happens when I am going for the space bar and catch the globe symbol to the left.

[aibd]

I expect it to be activated / deactivated by the keyboard symbol far left.

[irrlicht]

@AnotherElk

@irrlicht

FP3 (good), FP3+ (not good) I said

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.

The second device got it now. It updated OTA directly from 2.9-t to 3.0.1-t. But I had to ask for the update for about 40 times distributed over 5 days.

[bauduen]

@obacht

Samsung
Galaxy S7 (SM-G930F)
herolte
before: 2.9-s-20250321478216-official-herolte
for a short while: 3.0-s-20250528496287-official-herolte
now: 3.0.1-s-20250609498926-official-herolte
not Rooted

Only thing is that Parental Control still cannot be activated, issue 8625 persists for the time being. Not a showstopper for me as I do not need it anyways.

Thanks a lot for keeping that hardware alive!

Haven’t tested Parential Control, for the rest: same again!

[Konga66]

Same here. Just let us know if this is an issue or if we just have to wait a bit longer.
Thanks!

[piero]

Hello @Konga66, Welcome to the /e/ forum.

e-3.0 was removed because problematic on some devices,
but e-3.0.1-a14 for tangorpro has been already released (last week)…
/e/OS official tangorpro download

[harpo_bzh]

Hello everyone,

I just updated my S7 and it seems to be OKay.

Vendor Name : Samsung
Device name: Galaxy S7 bought refurbished from /e/foundation in 2019
Device CodeName: herolte (SM-G930F)
Version of /e/OS or Stock which existed previously: 2.9-s
Version installed : 3.0.1-s-2025060949989226-official-herolte

Thanks a lot to the developers team for your efforts !

[hakunamatata]

Don’t know if this feedback is even necessary, but:

Google
Pixel 5
redfin
3.0-t
Not rooted

Everything is fine as it was with v3.0.

[sophimae]

I hope, I’m in the right place with this feedback.

Vendor Name: Fairphone
Device name: FP5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 3.0.1-t-20250606498724-official-FP5
Is the device not rooted
Version installed: 3.0.1-a14-20250607498722-official-FP5

I can install almost no app from Google Play via App Lounge (or Aurora for that matter). App Lounge just does not install and immediately change the install button to “retry”. The app pages do not load at all.
Aurora Store states that the app is not compatible with my device, for example for apps like Firefox - which is known to work on 3.0.1-t official and on original Fairphone OS.

Factory Reset did not help. Reflashing a14 did not help. Clearing Cache and Data of App Lounge and or Aurora Store did not help. Any ideas?

EDIT: It works now! See Post 403 below.

[Delesamien]

• Vendor Name: OnePlus
• Device name: OnePlus 9 Pro
• Device CodeName: lemonadep
• Version of /e/OS or Stock which existed previously: 2.9-a14-20250321478411-community-lemondep
• Is the device Rooted / Not rooted: not rooted

Updated 3 day ago, without any problems observed.

[Konga66]

Thank you, piero. Interestingly, this morning I had “no updates available” in the settings. Now, the update is available…
Thanks anyway!

[WikiTang]

I believe I correctly followed all the steps to sideload the following update:
e-3.0.1-t-20250606498724-official-FP3.zip
(using the method described in Post #203).

Unfortunately, it doesn’t work. No matter what I do, the phone doesn’t boot properly, regardless of whether I’m on slot A or B.

Here’s a clear summary of my situation:

• My FP3 originally had an official build, with the bootloader locked.
• I updated to version 3.0 official via OTA, and that’s when things broke badly →
  when restarting, I would land on the lock screen, enter my pattern, and then the phone would immediately reboot again and again.
• I tried to get myself out of this on my own, using what I knew and with help from some posts here on the forum.
• I probably made things worse (I’m sure I did) by flashing the 3.0 community version afterwards,
  but that still had the same unlock → reboot loop issue.
• I then tried sideloading the 3.0.1 official version, following the recommended process —
  and now I’m stuck in an even worse bootloop, even after switching slots.
• I still have access to both fastboot and recovery mode, but I cannot boot into a working system.

If anyone has a clear and concrete way to help me recover from this without losing my data, I would deeply appreciate it.
Thanks for your help

[JBF]

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

I waited patiently for my phone to notify me of the update. The update went smoothly and everything seems to be working normally.

[aibd]

@WikiTang

by flashing the 3.0 community version

I think you are correct in thinking that this was the killer. Not only does community have the difference Different Build Types but current builds are different Android version; official is AOSP 13( T) community is a14.

I cannot suggest any way to recover the data except “expert paid for help” where they might probably take the phone apart (??)

To recover the phone I think you will have no choice but to carry out a fresh install Install /e/OS on a Fairphone FP3/3+ - “FP3” including unlocking the phone which will Format data.

[dave]

Fairphone 3+
FP3
Update from v2.9-t-official to v3.0.1-t-official
Not rooted

Update completed in 40 minutes with no issues.

GPS was not working after the update. Satellites found in GPSTest but no location fix. Coarse location only (1 km away) displayed in Magic Earth, no location in Memory Map for All. Rebooting didn’t help.

A search found the following post

No GPS at all on Pixel 7 Pro with e/OS 2.7, 2.8 or 2.9

I dont get the GPS to work in 2.7, 2.8 or 2.9. Reinstalled original Android 14 and 15 and the GPS works fine in both… Any special tricks needed for GPS in e/OS? Other than the GPS, e/OS works like a charm. The GPS works fine in my Galaxy S9 with e/OS 2.9 Fake location off. GPSTest app show no sattelites at all. Attached photo with Galaxy S9 to the left and Pixel 7 Pro to the right. [IMG_20250610_102922_900] Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services[phone]

so I turned off ‘Use assisted GPS’ in Settings, and an accurate location fix was found within 1 minute. Initially, GPS was still working properly after turning Assisted GPS back on again, but after turning location off and back on location was about 50 metres off. After repeating the Assisted GPS off/ on process again it’s now working well again. Will see how it goes.

Apart from this, my 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), and various other apps.

[Blu_chips]

@sophimae

I hope, I’m in the right place with this feedback.

Vendor Name: Fairphone
Device name: FP5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 3.0.1-t-20250606498724-official-FP5
Is the device not rooted
Version installed: 3.0.1-a14-20250607498722-official-FP5

I can install almost no app from Google Play via App Lounge (or Aurora for that matter). App Lounge just does not install and immediately change the install button to “retry”. The app pages do not load at all.
Aurora Store states that the app is not compatible with my device, for example for apps like Firefox - which is known to work on 3.0.1-t official and on original Fairphone OS.

Factory Reset did not help. Reflashing a14 did not help. Clearing Cache and Data of App Lounge and or Aurora Store did not help. Any ideas?

I have the same problem with the same version!

Also see this thread, where this has been discussed (but not solved) App Lounge hangs on many “common” apps

[Domi]

@Marsupilami

the App Lounge stopped working

Try it without Tor or VPN.

[Marsupilami]

@Domi

Try it without Tor or VPN.

I’m not using neither Tor nor VPN.

[WikiTang]

Thanks for the clarification — it makes sense now that the system crashed after mixing builds of different types and Android versions (official AOSP 13 and community AOSP 14). That said, I’m really trying to avoid formatting the device if there’s any other possibility.

Is there any chance to recover the system (or at least access it) by using a recent community build?
Even if it’s not fully stable — I still have access to both fastboot and recovery, so I’m wondering if a sideload of a proper AOSP 14-based community build could potentially work or unlock something?

I’m aware I took risks by switching build types, but maybe someone here has tested a workaround before going full wipe?

Any suggestion is welcome