Feedback for v3.6

/e/OS Smartphone Operating System Build Feedback
47

I’m on FP5 too, but the Issue started ~2 days before i received the 3.6 update. I guess AA was broken by an regular app update.

48

Sharing details with developers

1 Like
49

Same here..

can I actually switch from the current V3.6 to stock Android or is the security patch too low then?

IMG_20260319_154832734
IMG_20260319_1548327341920×1080 329 KB

Screenshot_20260319-154723_Android Auto
Screenshot_20260319-154723_Android Auto1116×2484 126 KB

1 Like
50

Pixel 4a
sunfish
before: 3.5-a15-20260211580872-community-sunfish
now: 3.6-a15-20260313593773-community-sunfish
not rooted

all is well, thank you!

51

• Vendor Name: Xiaomi
• Device name: Redmi Note 10 Pro
• Device Codename: Sweet
• Previous version of /e/OS: e-3.5-a15-20260212581008-community-sweet
• Current version of /e/OS: e-3.6-a15-20260313593828-community-sweet
• Not rooted

The update took a few minutes to download, the installation went flawlessly, and everything works perfectly.
All my respect goes to the developers!

52

Vendor Name: Google

Device name: Pixel 8

Device CodeName: Shiba

Version of /e/OS or Stock which existed previously: 3.5

Is the device Rooted / Not rooted: not Rooted

Update smooth and fast (as the previous one 3.5). Everything ok so far. Thank you e-os dev!

Good job (as always :laughing:) !

53

FP5, not rooted, 3.5-a15 → 3.6-a15-official
All went well :+1:
Fast download, fast install - big improvement! Thanks eOS Devs!!
Small oddity: App Lounge and Aurora show for Google Play store different apps for update.

2 Likes
54

Vendor Name: Fairphone

Device name: FP4

Device CodeName: FP4

Version which existed previously: /e/OS 3.5 A14official

Device Not rooted

Smooth update, all seems to work well … except wireless screencasting (no workaround) and UnifiedPush for ElementX for which to work i have to install ntfy and switch once to and back to the eos preinstalled version then deinstall again.

Thanks and keep it up dear eos team !

55 
Vendor Name: FairPhone

Device name: FairPhone 6

Device CodeName: FP6

Version of /e/OS or Stock which existed previously: 3.5

Is the device Rooted / Not rooted: Official /e/OS version

The download went smoothly. Android Auto isn’t working for me anymore, though I’m not sure if it’s down to the e/OS update or an update to the Google app. Android Auto isn’t working anymore.

I’m also having trouble installing new apps from the App Store. This mainly affects Google Play apps. Updates install without any problems.

1 Like
56

2 Devices

  • Gigaset

  • Gigaset GS290

  • GS290

  • Version previously installed: 3.4-s (a12)-official

  • Not rooted

Update went smooth and fast. No issues so far.

Download at 10 am CET, within 15 minutes the download and install was done (per device), Wifi-connection with 20 Mbit/s at home.

Thanks a lot to the /e/OS-dev-Team, great job :flexed_biceps:

57

Vendor Name: FairPhone
Device name: FairPhone 5 5G
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: 3.5 Official
Is the device Rooted / Not rooted: Not rooted

Update went well and everything works fine, for the moment.

58

Vendor Name: Fairphone
Device name: Fairphone 6
Device CodeName: FP6
Version of /e/OS or Stock which existed previously: 3.5 Official
Is the device Rooted / Not rooted: Not rooted

Update was quickly done. Download speed is OK.

Updated without any trouble.

1/ Android Auto is not working anymore. It was properly working with 3.5 release.

2/ Schedulded dark theme during night is not working.

3/ When dark theme is defined in not disturb mode, it goes in dark when I activate ‘don’t disturb’. When I deactivate the mode, the phone sometimes remains in dark mode.

59

Device: Fairphone 6

Version of /e/0S: 3.6-a15-20260312593772-official-FP&

Banking and paying apps not working anymore, many websites are now inaccessible (banned IP messages, though different devices work smoothly on the same network). Quite a mess at the moment…

1 Like
60

Maybe due to GPS location falsification ? Or IP changer ?

Bank apps can check the IP which is trying to connect and if “you are” in Singapore (the phone) but your account usually connects frol France, it could be refused no ?

1 Like
61

Vendor Name: OnePlus

Device name: 9 pro

Device CodeName: lemonadep

Version of /e/OS or Stock which existed previously: 3.5

Is the device Rooted / Not rooted: Not rooted

The update was unbelievably quick, the 2GB download was finished in 57 seconds.

Everything works fine.

Also the usual troublemakers Revolut and Starling bank and American express (based in the UK) are opening just fine.

Big thanks to developers

62
  1. Vendor Name: FAIRPHONE
  2. Device name: Le Fairphone (Gen. 6)
  3. Device CodeName : FP6
  4. Version of /e/OS or Stock which existed previously: 3.5 a15 official
  5. Is the device Rooted / Not rooted: not rooted

Everything’s perfectly fine from my side. I’m not using Android Auto, so I can not comment the issue that several users have encounter.

Still on A15. According to urs-lesse (#43), Android 16 could be released next summer for the Fairphone 6.

Did not yet tested the “Bluetooth incoming calls in car”, but issue is still not fixed in e-Gitlab, so I guess no change at this point.

Thanks to all involved devs! :wink:

63

  1. Vendor Name: FAIRPHONE

  2. Device name: The Fairphone (Gen. 6)

  3. Device CodeName : FP6

  4. Version of /e/OS or Stock which existed previously: 3.5 a15 official

  5. Is the device Rooted / Not rooted: not rooted

After updating from 3.5 a15 to 3.6 a15, I encountered the “problem” / “bug” where the phone lost its connection to the mobile network provider. I didn’t notice it until the next day.

Restarting the phone and enabling Airplane Mode didn’t help. I had to deactivate and then reactivate the eSIM for the connection to the mobile network provider to work again.

64

Unfortunately, I killed my Fairphone 6, after the Android Auto update and 3.6 Android Auto didn’t work anymore. then wanted to install stock android again and I closed both bootloaders… Result: Fairphone 6 is just core junk and apparently has to be reflashed by the manufacturer because I can neither open the bootloader nor install it via sideload E/OS. Sorry but because I also had some problems with compatibility with Android Auto ect. I ordered another pixel without further ado, which fortunately came today, because without a mobile phone I could neither use 2FA for websites nor other communication channels. let alone my digital vehicle registration document.. I have definitely noticed how dependent one has become on digital services and will now stay because of the problems of E/OS. even if it was my own fault. but that’s just too risky when your whole life is suddenly totally blocked because of a cell phone.

66

- Fairphone
- Fairphone 4
- FP4
- Previous /e/OS: 3.5-a14-20260211580870-official-FP4
- Current /e/OS: 3.6-a14-20260312593433-official-FP4
- Not rooted, bootloader locked

Despite the FP4-specific bug fixes part of the release notes here v3.6-a14 · e / os / 🚀 Releases · GitLab saying “Fixed speaker volume being too low during phone calls”, I found no difference at all between 3.5 and 3.6: the speaker volume during calls (normal phone calls, WhatsApp calls, Teams calls…) is a tad low despite the call volume toggle being set to the max; volume on calls with speakerphone and wired earphones is OK, it’s the normal speaker (the one on the phone which I bring close to my ear) which has a low volume.

- Are there settings to try improve this situation?
- Is there already a proper “place” where to report this?

Other than this, all good with 3.6 so far. Thanks to the Team!

PS As I mentioned while I reported for 3.5: 3.5 brought an FP4 fix for a long standing issue which is mentioned in the release notes for 3.6; namely “Fixed poor audio quality in Teams and Skype calls”. Again a very big THX!!! to the Team for that fix.

3 Likes
67

Now that you mention it, yes FP4 normal on ear phone speaker volume could be tad louder on my phone too.

2 Likes