Vendor Name: Xiaomi
Device name : Poco X3 Pro
Device CodeName : wayu
Version of /e/OS or Stock which existed previously : v1.18
Is the device Rooted / Not rooted : not rooted
I noticed that notifications has intermittent issues.
Case 1. Phone rings sometime it does not display anything weather the phone is sleeping or not. This is happening for regular calls and also whatsapp voice calls.
Case 2. Alarm also has the same intermittent issue as above. Normally when the alarm went off the phone wakes up and display the alarm, intermittently the phone does not display the alarm when it went off, but I can hear the alarm sound.
Vendor Name: Xiaomi
Device name: Mi 10T Lite 5G
Device CodeName: gauguin
Previous Version of /e/OS: 1.19.1-s
Rooted: No
I had several problems:
After manually updating, I could not reboot without formatting the data. It gave a message indicating that the data was corrupted. I had to reinstall all the apps, reconfigure emails, etc etc.
As for the data, photos, etc e-drive worked perfectly and all documents, photos,… were recovered.
Subsequently more problems:
The GPS placed me about 30 km away from the real place. I had to use the assisted GPS. In this way, at startup it does not locate me correctly but immediately jumps to my location.
F-Droid gave error when updating repositories: I had to reinstall.
My weather app (AEMET) was not connecting to the server either: I had to reinstall.
AppLounge does not connect (no error), stays with blank screen: waiting for update.
This is expected behaviour. The jump on your device from 1.19.1 -s to 1.20 -t was not a simple update, but included an upgrade of the underlying Android version, from Android 12 (S) to Android 13 (T).
Sometimes this may even work without wiping data, which is always welcome then, but wiping data in this case is the default, as long as a so-called OTA upgrade via the updater is not provided (which takes serious development and testing effort per device and per upgrade step, you can follow proceedings in the weekly posts here … https://community.e.foundation/tag/development-updates … currently in section “OS OTA Related information”).
Well, that’s not my experience.
I’ve done this several times before with LineageOS and others ROM. And this is the only time I’ve had to completely format the data when I’ve upgraded. For example, I just upgraded from Android 13 to Android 14 on an a52sxq with iode and everything was set up like a regular ota upgrade. Everything perfect and no problems, as usual.
Yes, I had to format in the downgrade.
That’s why I think it’s appropriate to point it out.
Hmmm … I personally had upgrades work without wiping data myself sometimes, so you certainly have a point in trying, and you seem to have been lucky so far. I had other upgrades which didn’t work out this way, though, but I was prepared for that.
I would never take this for granted, OTA upgrades need to be meticulously prepared for reasons.
But I believe manual upgrading S → T is a “special case” unlike any we saw with previous upgrade due to the enormous amount of work done by devs both /e/OS and LineageOS
In trying to confirm my understanding, very similar to @pealfa I think, I asked
Working great ! No major issues. As usual, the only color available in the appearance settings is the blue…
I would really like to know if some other “jumps” from an android to another will be made in the future for Samsung devices, particularly the S7 (which I own).
Haptic feedback works fine, but vibrate-on-ringing seems to fail. This behavior seems to happen when I use the traditional on-screen mode changer, and also when I use the side switch. A reboot seems to bring it back for a time, but the likelihood of vibration ceasing increases with uptime. This wasn’t an issue in 1.19.
Not the end of the world, as I just reboot in the morning and I’m good for most of the day, but worth the look if at all possible.
Vendor Name: Xiaomi
Device name: Mi10T
Device CodeName: apollon
Version of /e/OS: 1.19.1 s → 1.20 t (dirty upgrade)
Is the device Rooted / Not rooted: tested stock and rooted (magisk 27.0)
Upgrade itself went smooth.
Apps that stopped working (root / no root):
‘DAK’ App, now recognises custom ROM, worked previously in 1.19.1 with hidden root
‘mobiles Bezahlen’ (mobile payment app). App stopped working initially, works after deleting its app data)
App licensing implementation still does not seem to work,
when there’s a licensing app involved (e.g. PowerAmp, TitaniumBackup)
or not (e.g. DroidCamX, MacroDroid, SpritMonitor mentions a billing service not available on boot)
Google Fit can not login “problem with google-play services”, never worked since I switched to e/os.
Dear all,
I just wanted to keep you informed of the status for me after the update hard bricked my Fairphone 5.
I sent it back and got it repaired luckily without anything to pay.
Now this is anyway time for me to say goodbye to /e/OS for at least some years, this was a too bad experience for me.
I will stay with Fairphone OS and try to get rid of the Google Play Store (replacing it by microG if I manage to) because what I would like to avoid most is the Google spying on my apps usage.
I just wish other using /e/OS have better experience than me.
Bye all.
I doubt you could replace Google Play Services with Micro-G without rooting the device (and therefore unlocking obligatory the bootloader).
I don’t know what went wrong with your installation, but I assume you performed the Fairphone OS updates just before installing /e/, which may have forced the “anti roll back feature” system to block your Fairphone 5…?
Version of /e/OS or Stock which existed previously: /e/OS 1.19-s-stable
Is the device Rooted / Not rooted: I don’t know
I found a problem, i have since a long time ago System profile automatically chooses secondary SIM for cellular data
But it’s a problem only recently when, the second SIM have got a little data (when, i start use a second SIM card, the second SIM card don’t have data).
For me, it’s not automacally. When FP3 quit Wifi, in two cases on 3, the second SIM card are chosen.
I upgraded my Fairphone 3 to Android 13 (T) successfully without formatting, but with Android version upgrades being what they are, even if such unofficial shortcuts were reported working by other users for my device, I’m always prepared to wipe my phone if the process fails for me, or if I encounter any trouble after an at first seemingly successful upgrade.
Facing an Android version upgrade, it’s just the clean approach to wipe, even if undesirable.
I wouldn’t know.
Generally speaking nowadays I wouldn’t use TWRP for installs when an OS provides its own recovery to do this. The /e/OS developers have control over what the /e/OS recovery does, while TWRP is an independent project and any compatibility with /e/OS is not guaranteed.
For future reference (this came a few days after your post) …
Which will of course not keep us from trying to get around wiping data (or hope for others to try before us) . But the recommended way is now clear, which should help manage expectations when deviating from this path.
That really is poor It should not be acceptable that upgrading to a new version of the same ROM involves re-installing stock ROM and / or losing all user-installed apps and data. Especially as there is now working backup and restore solution with /e/OS
It should not be acceptable that upgrading to a new version of the same ROM involves re-installing stock ROM and / or losing all user-installed apps and data. Especially as there is now working backup and restore solution with /e/OS