Vendor Name: Fairphone
Device name: Fairphone 2
Device CodeName: FP2
Version of /e/OS or Stock which existed previously: /e/OS 1.12.3-r-20230619301238-dev-FP2
Is the device Rooted / Not rooted: Not rooted
Settings - System - Advanced - microG - Self-Check: all ok, including location permissions
Settings - System - Advanced - microG - Location - Wi-Fi location - Request from Mozilla: enabled
Settings - System - Advanced - microG - Location - Wi-Fi location - Request from Hotspot: enabled
Settings - System - Advanced - microG - Location - Mobile network location - Request from Mozilla: enabled
Settings - Advanced Privacy - Location: Exposed
Settings - Advanced Privacy - Manage my location: Use my real location
Settings - Location - Wi-Fi and Bluetooth scanning - Wi-Fi scanning: enabled
Settings - Location - Wi-Fi and Bluetooth scanning - Bluetooth scanning: disabled
Settings - Location - App access to location - “Allowed only while in use”: Apps are listed
Compass
Screenshot
Main camera (Camera module 12 MP version 2) photo + video
Selfie camera (Top module version 2) photo + video
(Camera records completely black video from the moment surrounding light is too dark or changes into too dark when moving … years old issue I already had with Open Camera on LineageOS, can live with it.)
No issue with update from 1.12.3 Q to 1.3.0 Q (stable) on my S9+ ; GPS is still working fine in my daily driver app “Naturalist” :-).
Seems though that the battery consumption has been heavier since a handful of releases … I would say that I’ve progressively lost around 30% full charge duration. No new app in use since then.
Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: /e/OS [1.11
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on [1.13-s-20230727314102-dev-
The following things work for me:
Call / be called
Send SMS / receive SMS
Alarm
Internet via Wi-Fi
Internet via mobile network
Internet via ethernet cord (usb adapter)
Wi-Fi hotspot
Location
Screenshot
Main camera (original FP4) photo + video
Selfie camera (original FP4 ) photo + video
USB connection to PC / MTP
Bluetooth (music playback, data connection)
Everything went well in the OTA update and so far feels really quick and snappy, Thanks a lot to the whole e team and and every one involved for all the amazing work! <3
Vendor Name: Fairphone
Device name: FP3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously : 1.12.3 stable
Is the device Rooted / Not rooted: I don't know
Vendor Name: Teracube
Device name: 2e
Device CodeName: emerald
Version of /e/OS or Stock which existed previously:
1.12.5-r-20230705306756-dev-emerald
Is the device Rooted / Not rooted: rooted
OTA update failed to install. After a few attempts I exported the update to SD card and flashed from recovery. That went okay.
Alas, that meant I missed out on the Magisk OTA update also. No problem as I had the 1.13 fastboot files ready just in case updating totally failed.
With 1.12.5 I had downgraded microG. Figured I’d have to do the same with 1.13 but adb remount repeatedly failed with /system, /product, and /vendor. The mount command also failed to mount /system. Always reported as not mounted anywhere so can’t be remounted.
So after deleting some microG dalvik files under /data/ I booted into recovery and was able to do what I needed in /system from there (/mnt/system/system).
When I fastboot flashed 1.12.5 per the instructions (things had changed since the last time) it included logo-verified.bin. A problematic item responsible for dm-verity corruption boot message along with a poweroff countdown.
Ultimately I wound up dirty fastboot flashing 1.13 along with Magisk patched boot image, logo.bin, and using the --disable-verity --disable-verification flags when flashing vbmeta.
Now everything is as good as before 1.12.5.
Fun stuff.
Interestingly I was sure I replaced microG before fastboot flashing thus getting 0.2.28 again but 0.2.27 was present after boot. Mozilla and Nominatum backends were gone but the others were still present. Installed them.
After awhile a check with SatStat showed great location results. Tiny red GPS circle on my house and a small blue network circle covering my house and the building next door.
Everything else in the build seems good to go. App Lounge acts odd but then when hasn’t it.
EDIT: Regarding failure to mount /system I never thought to try mounting the root directory instead. From what I read somewhere that should work(?).
Fairphone 3+
FP3
Updated from v1.12.3-s stable
Not rooted
All went well with update - 40 minutes to complete.
No immediate issues noted, all seems to be running fine currently.
Previous issue with Seek app (now v2.15.0) where app crashed if I tried to view a saved observation with location enabled seems to be resolved and app appears to be working correctly now.
Phone still not reconnecting to a Proton VPN server when I try to change VPN server or on reboot (issue #6793 in Gitlab).
One issue has popped up on my FP4 since the 1.13 update: wifi connection gets lost sometimes after some time of inactivity.
I have to switch to airplane mode and back to reconnect to my network.
* Vendor Sony
* Device Xperia 10
* Device kirin
* Version of /e/OS before: 1.12.3-s
* The device is rooted
Since OTA-update to 1.13-s the battery drain rised.
The battery loses 5-6% per hour. Independantly if I use it or it or not. So I have to recharche the phone during the day, which was never necessary before. The battery usage shows a linear graph down and there is no app consuming all this.
Any ideas how to analyse this further? Could I roll back to 1.12.3-s somehow?
I first flashed the phone one year ago and had never trouble with the monthly updates.
Thank you @piero. I have only recovery-e available.
Using the recovery-e
go to -->settings -->system-updater, select the previous version 3 dot menu, and choose “export”
In settings->updater I have a “…” menu showing me “Preferences” and “Version information”. I’ve selected (I would assume it’s the default) to remove installed sources. So that’s maybe why I cannot find an “export” there?
Reboot into recovery mode, and “apply the update” from the location you choosed (internal or external storage)
I’ve done this and tried to sideload via adb the 1.12.3 eOS file. But it refuses install with the message “Denying OTA because it’s SPL downgrade”.
Humm… I was thinking come back to previous version was possible…
Not 100% sure that works because not tested, but installing TWRP in place of recovery-e, then install previous version and reinstall the recovery-e (for future update compatibility) could do the thing.
I have to test and come back here in about an hour to edit this post…
I have e-1.13 and TWRP already installed, so i tested this :
It worked for me. I come back to e-1.12.3
So, i redo the update (this time with recovery overwrite selected), i am now in your configuration. (e-1.13 and recovery-e)
I rebooted to the recovery-e and choose apply from internal storage (where i have stored the e-1.12.3.zip) and it worked too, i came back to e-1.12.3
So, i redo the update and i am one more time in your configuration. (e-1.13 and recovery-e)
I rebooted to the recovery-e and choose adb sideload (as you did), it also worked, i came back to e-1.12.3
So i redo the update, uncheck the recovery-overwite feature and reinstall TWRP to recover my original state
I don’t have the same device as you,
mine for the test is a Samsung Galaxy s4active using latest “R” /e/build on top of latest stock firmware based on android 5
Have a try using TWRP,
make a backup, and install previous /e/
If you still have a SPL relative error message, wipe /system (trying to avoid anti-SPL-rollback), eventually wipe /cache and wipe /davilk, before another install attemp.
