Is there or will there be an OTA upgrade from Q to R/S on FP3 dev? If not, what is the safest way to get there?
I’m now on 1.5-q-dev-FP3. I was thinking I could flash the stable build to get the OTA, but there is no 1.5-q-stable-FP3 build available. I’m assuming that the 1.4-q-dev-FP3 boot is still on my phone in the alternate A/B slot. What if I use fastboot to switch back to that one, and then flash the 1.4-q-stable-FP3 build, followed by an OTA upgrade. Would that work?
Android rollback protection.
/e/OS 1.5 has a more recent security patch level than /e/OS 1.4, so even if you could switch the slot, booting the older OS version would prompt you for a factory reset for security reasons to continue booting.
Switching the build type from dev to stable should also require a data wipe from what I understood so far.
Oh dear. Well, I hope I’m not trapped again, like with the P to Q upgrade I did a while ago.
Thanks for the OTA update to 1.51 on my Murena Fairphone 4! Android 12 looks very good and runs so far without any problem. However, I have reset my FP4 and set up completely new.
I have had the Murena FP4 for 10 months now and am still very happy. To be exact: I have not had a single problem with the numerous updates and upgrades. The Fairphone hardware and /e/OS are a great match.
Thanks again to the whole development team!
Hi,
It s my first post here ! Just to confirm that the upgrade from 1.4-q to 1.5-r of the stable branch was done perfectly smoothly on my FP3 !
Thanks to the all e/ murena team. Your job is great and goes beyond my expectations !!
It is my understanding that you plan to make an upgrade to android 12 on FP3/FP3+. Is there.any ETA yet ?
I m not impatient (well maybe a little 
!), cause 1.5-r is really great and i m impressed by all the good work you are doing, but just for my knowledge…
Keep it that way, thanks again !
Hi.
On my Murena FairPhone 4, after upgrading 1.4 to 1.5-20221018, I got HTTP 404 errors when sync ecloud shared Caldav calendars (not my personal calendar).
Next I installed /e/ OS version 1.5.1-s20221102231514-stable-FP4.
I always have the sync error and now, the fingerprint reader does not work and I can’t add or delete any fingerprint (trash does nothing and add button disabled).
The device Not rooted.
Fingerprint issue was the same on my FP4. During I tried to delete saved fingerprints settings app freezed. So a restart was necessary. After that deletion was possible and I could save new fingerprints. Now all is working perfect.
My wife had the same issue just after the upgrade, but a simple reboot fixed this…
A part from that, the visual effects when closing applications are strange (uniform color frame around the application instead of the Bliss launcher). But this is a purely cosmetic effect.
Everything works perfectly well! Great work from the dev team! Very happy to run /e/ OS Android 12 on my FP4! 
What a pleasant surprise to have an OTA upgrade to 1.5-s on FP4! Just did the upgrade and everything went smoothly. I didn’t even get the fingerprint problem other users seem to have. Great job to the team and a big thanks!
I updated my OnePlus 6 to /e/OS R and then to /e/OS S. Everything seems to have gone smoothly! However, I have a problem with the EN version of microG: I cannot open the app. Instead, it crashes. I can revert to the non-EN version by going to the App Info, selecting the three dots above and then the menu entry “Deinstall updates”. However, you then lose all your GCM-registered apps.
@Manoj Are any bugs known for the microG version with Exposure Notification? I can try to capture a logcat.
EDIT: The logcat has the following exception:
--------- beginning of crash
11-12 14:42:44.889 5346 5346 E AndroidRuntime: FATAL EXCEPTION: main
11-12 14:42:44.889 5346 5346 E AndroidRuntime: Process: com.google.android.gms:ui, PID: 5346
11-12 14:42:44.889 5346 5346 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/org.microg.gms.ui.SettingsActivity}: java.lang.UnsupportedOperationException: Can't convert value at index 1 to color: type=0x1
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3707)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3864)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2253)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7870)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: Caused by: java.lang.UnsupportedOperationException: Can't convert value at index 1 to color: type=0x1
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.content.res.TypedArray.getColor(TypedArray.java:534)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.Activity.onApplyThemeResource(Activity.java:5181)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.view.ContextThemeWrapper.initializeTheme(ContextThemeWrapper.java:216)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.view.ContextThemeWrapper.setTheme(ContextThemeWrapper.java:147)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.Activity.setTheme(Activity.java:5159)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at androidx.appcompat.app.AppCompatActivity.setTheme(AppCompatActivity.java:144)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3671)
11-12 14:42:44.889 5346 5346 E AndroidRuntime: ... 12 more
11-12 14:42:44.892 1266 5378 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
11-12 14:42:44.892 1266 2169 W ActivityTaskManager: Force finishing activity com.google.android.gms/org.microg.gms.ui.SettingsActivity
EDIT 2:
Same for me.
And still looking for Izly app, disappeared with 1.3 update
I have a similar issue, that’s why I am replying to your post, even if my reply does not answer it:
I just updated my FP3+ to latest /e/ OS update (EN language settings). With that update the microG exposure notification seemed to stop working and could not be activated again anymore with the German CoronaWarn App from the app store.
According to the linked docs for Exposure notification, I tried to manually download the latest (stable) version microG APK and install it manually w/o success: The latest version (which I already had installed) could not be downloaded => http “404 ressource not found”. For unknown reason I tried to install the previous version which did exist but (luckily?!?) could not be installed => Message “App not installed”.
Referring to Tentos’ post, I also tried to switch language settings but in my case it does not matter whether language is EN or DE, the exposure notification framework does not work anymore.
Q: Is this a (known) bug?
Q: Any ideas how to deal with that?
Thanks!
/e/ update: 1.5-20221028230215
microG version: 0.2.24.223616-96 (f87cb98)-noen
Corona Warn-App: 2.28.3
manual download microG: Releases · e / os / GmsCore · GitLab =>
https://gitlab.e.foundation/api/v4/projects/149/jobs/artifacts/e-v0.2.24.223616/raw/play-services-core/build/outputs/apk/withMapboxWithNearby/releaseStable/play-services-core-withMapbox-withNearby-releaseStable.apk?job=build-release
Have you try here ?
Fairphone 4, I’ve found a bug (1.5.1-s).
Since latest Android 12 upgrade, I’m unable to rotate a picture. If I rotate a picture (up-side-down) in the gallery, as soon as I click on “Save”, gallery app crashed and the image is not saved.
Same behaviour on my spouse’s FP4 (identical config), so I guess it’s a general bug.
I’ve opened an issue here:
Cheers.
FP4 running 1.6-beta-s-20221109233613-stable-FP4.
I can successfully rotate and then save a picture in gallery app.
FP4 picture rotating and saving ok here too.
(1.5.1 s)
In my FP4 1.5.1-s-20221102231514-stable, picture rotating and saving ok too, just like with @ff2u and @winkman
Thank you. Nice to hear.
From what I’ve just tested, it seems that pics in the internal phone memory can be modified, but not those on the SD card. (almost all my pictures, and those from my wife are stored in the SD card folder). Maybe a lead?
Anyway, I changed the title of the issue to: " Unable to rotate a picture on Fairphone 4 SD card folder"
Workaround: Same task works well without any issue with “Simple gallery” app.
I have updated my
I newly installed 1.5 S on
with the following findings:
I have updated my FP3 2 weeks ago.
It worked fine apparently since I did not needed to go in the parameter section of my phone until now.
When I open the parameters on my FP3 and select for instance the account section. After 2 seconds, I have a black screen. This black screen can be closed by closing all the app in once. But to what I can see by now, I can not access to my parameters anymore.