If no major issues emerge for those who installed the community builds I would guess either thursday/friday or after the weekend. Just my guess, I have no insight into development.
2 Likes
I have successfully updated my unlocked not rooted
- e-3.1.1-a15-20250830521751-community-FP3.zip
To
- e-3.2-a15-20251025540112-community-FP3.zip
through the updater, It was very fast !
(refresh 5 times to see the update)
- nomore cursor control from the keyboard panel but i found that swiping the space button do the job
minor issues i found :
-
In Advanced Privacy i cannot anymore change the country when the āchange my IPā feature is enabled
-
cannot figure how to see witch leak was authorized
1 Like
On my pixel 4a not rooted from :
- e-3.0.4-a15-20250711508346-community-sunfish
To
- e-3.2-a15-20251023539040-community-sunfish
No issue for the moment (I used the update directly on the phone)
1 Like
Fairphone 3
A15 3.1.2 ā A15 3.2
Update went smoothly. Phone is working after the update. However, Iām still experiencing Android Auto crash (error 22), which occurred first after I updated to A15 (did a dirty upgrade between A14 and A15).
[EDIT] Apparently, a fix is in the works for AA to work with Android versions above A14: Android auto "communication 22" - #8 by Segment
Fairphone
Fairphone 3
FP3
Previous version: 3.1.1 A15 community
Not rooted
Super smooth speedy update. All done in about 20 minutes I think.
So far so good! Iāve disabled the advanced privacy notifications 
Huge thanks to the team again!
1 Like
- Vendor Name: Oneplus
- Device name: 9 pro
- Device CodeName: lemonadep
- Version of /e/OS or Stock which existed previously: 3.1.4 A14
- Is the device Rooted / Not rooted: not rooted
All good so far! Only problem is that the Advanced Privacy keep all the time pushing notifications that its runing.
2 Likes
-
Vendor Name: Sony
-
Device name: Xperia 1 III
-
Device CodeName: PDX215
-
Version of /e/OS or Stock which existed previously 3.1.4-a14 then 3.2-a14 then 3.2-a15
-
Is the device Rooted / Not rooted: Not rooted
Upgrading from 3.1.4-a14 to 3.2-a14 to 3.2-a15 on PDX215 (Xperia 1 III)
Followed the upgrade instructions for PDX215 on the LineageOS wiki: Upgrade LineageOS on pdx215 | LineageOS Wiki
I installed 3.2-a14 first, and its timestamp was greater than the one for 3.2-a15 so I was asked if I wanted to downgrade, I selected yes.
Upgrade successful, all apps and data intact!
1 Like
Youāre right @elrond, the commands listed in my post are the official install guide without the unecessary steps. Donāt need to unlock the bootloader because itās already unlocked, no need to format because I want to keep my data.
1 Like
everything OK without any issue. Just the frequent notification of advanced privacy running is a bit strange.
1 Like
-
Xiaomi
-
Redmi Note 10 Pro (M2101K6G)
-
Sweet
-
3.1.4
-
Not rooted
The OTA update went very quickly and smoothly. Everything that was already functioning correctly continues to work without any problems. However, the issues I reported earlier on this forum and on GitLab still persist:
-
Find My Device still doesnāt work (the app wasnāt working in the previous 3.1.1 version either. After updating to 3.1.4 there was a visible change in the appās behavior, but the underlying problem wasnāt solved; now, after updating to 3.2, nothing has changedāthe FMD behaves exactly as it did in 3.1.4).
-
Only one of the four rear cameras works, and even that one captures images at 12 megapixels instead of the advertised 108 megapixels.
-
Minor bug in the weather module inside the Maps app: it displays the local time incorrectly.
User @cwasiey has the same device with the same problems. Iām curious whether the update helped them.
I would be very grateful if someone could give a substantive response to the issues Iāve raised, because although Iāve posted several times on the forum, I havenāt received any assistance so far.
Vendor Name: Xiaomi
Device Name: Redmi K20 / Mi 9T
Code Name: davinci
Version of /e/OS which existed previously: e-3.1.4-a14-20250919527684-community-davinci
Device Not rooted
OTA Update Installation without errors
after the error-free update to e-3.2-a14ā¦ clean installation on A15.
clean installation from the first e-3.2-a15ā¦ again without any problems. 
Compared to a14, a15 is much smoother. 
Everything works the same way as with a14.
no mistakes so far, perfect work
a big thanks to the developer team, Everything works as it should be.
Did you really report the issues to the developers or did you ājustā post in the forum? ā¦ Report an issue ā¦ Issues Ā· e / Backlog Ā· GitLab
Iām still new to GitLab, thank you for bringing this to my attention. And thanks to @manoj for supplementing my post.
Error
Fairphone 3 - community build
Updated last night from 3.1.1 (A15) to 3.2 (A15).
Updating went smoothly. This morning however, i got a bricked Phone. The screen is only displaying tiny pixels in every colour. Issue is persistent after taking out the battery and rebooting. I cannot confirm if itās a issues related to the update, or coincidentally happening at the same time and linked to flawed hardware. Curiously, i already experienced a short period of screen flickering and weird colours after updating to 3.x in Septemberā¦ How should i proceed?
Edit. After one reboot, the normal Fairphone boot display appeared on screen but was soon afterwards again covered with tiny pixelsā¦
Update: After wriggling and pushing the phone gently, the pixelated screen disappeared. Itās possible the error was caused by old hardware or a faulty connector. I will update, if the problem reoccurs.
2 Likes
If the phone donāt boot, try to switch to other slot using fastboot, to launch previous e-3.1.1 version.
(boot the phone in bootloader mode, plug it to the PC)
fastboot set_active other
2 Likes
Google Pixel 3 XL crosshatch from e/OS/ 3.0.4 A15 not rooted.
Updated through OTA without any problem.
- Vendor Name : Fairphone
- Device Name : Fairphone 6
- Version of /e/OS which existed previously: e-3.2-a15-20251022539040-community-FP6
Impossible to create a passcode to unlock the device so impossible to unlock with fingerprint.
Impossible to install app from F-droid like Droid-ify or APK from browser because āCanāt install packages while in secure FRPā
EDIT : back to 3.1.4
Samsung
Tab S5e (SM-T725)
gts4lv
before: 3.1.1-a15-20250830521751-community-gts4lv
now: 3.2-a15-20251025540112-community-gts4lv
not rooted
no issues from what I can tell so farā¦ many thanks!
Pixel 4a
sunfish
before: 3.0.4-a15-20250711508346-community-sunfish
now: 3.2-a15-20251022539040-community-sunfish
not rooted
all well, many thanks!
(and the āthe navigation bar cannot be invertedā-issue is solved obviouslyā¦)
@Hase As far as I know, your device has three rear cameras:
- 48 MP, f/1.8, 26 mm (wide), 1/2.0", 0.8 Āµm, PDAF
- 8 MP, f/2.4, 53 mm (telephoto), 1/4.0", 1.12 Āµm, PDAF, 2Ć optical zoom
- 13 MP, f/2.4, 12 mm (ultrawide), 1/3.1", 1.12 Āµm
Iām very curious to know whether all three workāthat is, if you can take telephoto and ultrawide photos as well, and whether photos taken with the main camera retain the full 48 MP resolution.
- Motorola
- Edge 30 Dubai
- Not rooted
- 3.1.4 A14
Everything works so far. THX