@kolkrabe
An update.
Earlier this week, I wanted to start backing up the settings for some apps on my GS290. The GS290 was on the charger. But when I picked up the phone, the screen remained black. And that is how it has been so far. No life left in the phone (purchased January 1, 2020).
So, an update to the new /e/OS 4.1.1 is no longer necessary for this phone. I have purchased a new device, a Fairphone 6+ via Murena.
Now for my wife’s phone, also a GS290.
Today, I exported the settings for apps she considers important and copied them to the PC. Tomorrow I will back up her files and then perform the update.
To be continued.
I observed also sync issues with my currently imported Google Calendar.
After removing both accounts (Murena, Google) and starting from scratch by creating fresh accounts all data could be synced.
As of today - Google still syncs. Murena has still the issue with authentification error. In addition I have an error in “Mail” with a funny error code which also indicates that something got messed up.
Vendor Name: OnePlus
Device name: 8T
Device CodeName: Kebab
Version of /e/OS Installed: v4.1.1 Android 16
Version of /e/OS or Stock which existed previously: e.OS v.4.1.1 Android 15
Is the device Rooted / Not root: Not rooted
The Issue: Android Auto is not working.
Android Auto was working fine on v4.1.1 A15, which was upgraded from v4.0 and v3.X prior to that. I completely wiped the phone and freshly installed /e/OS v4.1.1 based on Android 16. Android Auto is now not working from a fresh install with Android 16. So the issue lies either with a fresh install of v4.1.1 or with Android 16.
I can see in the list of system apps the Android Auto Stubs. It shows as version 1.0 with the package path com.google.android.projection.gearhead. Going into the App Lounge and bringing up Android Auto, it shows no option to upgrade. Only shows an option to “Open”.
Version of /e/OS or Stock which existed previously: not sure (always updated to the latest version, must have been your official version before 4.1.1-a16-20260717651034-official-FP6
Is the device Rooted / Not rooted: Not rooted
Problems that occur:
Apps sometimes not working properly: YouTube, Mastodon, Qobuz, Garmin Connect, etc. will start, but display empty boxes where content should be shown. Shutting the apps down won’t help. After a restart of the Fairphone, they will work again for some time.
Garmin Connect: Forgets my Garmin Forerunner 965 every few days and I have to add it again.
These problems occured with the upgrade to 4.1.1 did not happen on the previous versions.
Just to add to my previous post. I do not exaggerate when I say the battery readings became highly erratic and inaccurate, with jumps in battery usage going up and down even overnight when not in use. I’ve always made light use of the Fairphone 6 and yet maximum capacity, according to the app continued to go down to about 80%, which is obviously inconsistent with 30 charging cycles and there were quite a few random reboots. So I performed a Factory Reset and battery level appears to be back to normal; however, maximum capacity is now given at 83% when it should still be at or very near 100% as it was before the 4.1.1 Android upgrade.
Vendor Name: OnePlus
Device name: 8T
Device CodeName: Kebab
Version of /e/OS Installed: v4.1.1 Android 16
Version of /e/OS or Stock which existed previously: e.OS v.4.1.1 Android 15
Is the device Rooted / Not root: Not rooted
The Issue: Android Auto is not working.
Android Auto was working fine on v4.1.1 A15, which was upgraded from v4.0 and v3.X prior to that. I completely wiped the phone and freshly installed /e/OS v4.1.1 based on Android 16. Android Auto is now not working from a fresh install with Android 16. So the issue lies either with a fresh install of v4.1.1 or with Android 16.
I can see in the list of system apps the Android Auto Stubs. It shows as version 1.0 with the package path com.google.android.projection.gearhead. Going into the App Lounge and bringing up Android Auto, it shows no option to upgrade. Only shows an option to “Open”.
[Update]
I have found the workaround. The key is getting the real Android Auto package installed. The App Lounge is just broken for recognizing that the package can and should up updated.
I got the Aurora store, searched for Android Auto and used its “force download” option to get the package downloaded, then executed to update the system package. You could also go to online package stores to get the latest APK to download and install to update it as well.
Once Android Auto was updated, it then operated as expected in both of my vehicles.
All was good on my Fairphone 6 too until the update to 4.1.1., which caused persistent authentication failures and incorrect, erratic battery indicators, which have come back even after a Factory Reset when I again had to reset my password, remove and restore my Account to get the device to sync. And the battery information shown is still incorrect. For example: “27% Not Charging” even though I’d charged it up fully. And the bar chart for battery usage has also gone haywire again after the reset. Since the battery status level given is so low, I will leave the phone charging while updating as a precaution against another random reboot occurring during the update. So I’m now waiting for the 4.2 update to appear in the OTA Updater with baited breath. I see it is already available on the API server here. I’m tempted to download it immediately and not wait any longer; however, I will bide my time …
Shortly after posting, I noticed that the 4.2 update has finally appeared in my OTA Updater App. And I see it’s appeared as the latest at /e/OS builds. What a relief! But I’ll report again in Feedback for v4.2., but I trust it’ll fix the issues, or rather, squash the bugs in 4.1.1 for good.
There was some problem with native camera app in 4.0 but it still happens on 4.1.1 - when using video recording every now and then there is a problem with filming, the app stops working, the error says: ‘server died’ and then ‘serious camera error’ and the blue dot for camera working stays on after closing the app. I find it very annoying, and what any server has got to do with the off line app? Anything we don’t know about?…
Adding to the Passwords app issue, automatic Dark Mode doesn’t work with the sundown / sunrise timer, nor when it’s set with the specific time. On my Pixel with 4.0.0 it worked just fine (I had Dark Mode set to enable at sundown / sunrise, and Night Light at a specific time). Interestingly, Night Light does work with a set time but Dark Mode doesn’t.
Answering myself just in case anyone else is having similar Dark Mode issues: deleting my alarms, disabling automatic Dark Mode & Nightlight, restarting the phone and re-enabling all the above seems to have fixed automatic (sunset/sunrise) Dark Mode for me.
I forgot to mention something weird in my first post (FP3+):
Upon boot, I am prompted for my SIM’s PIN, as usual. But if I am not reactive enough and let the screen turn off by itself after the allotted period of inactivity, the PIN dial-keyboard thingy will never be displayed again. Basically, the phone ends up stuck in the “Locked SIM” status until I reboot. Even turning aeroplane mode on and off does not bring the dial back. So now when I boot I remain focused on the phone and avoid doing unrelated things.
All good on my Gigaset GS6 Pro with /e/ 4.1.1.
.