Hello,
With my S7 I’ve had this type of crash 3 times since switching to V1.20. I was wondering if it wasn’t due to my phone, which is getting a bit old. But if other people have the same problem, it could be due to version 1.20.
If the upgrade from /e/OS1.19-s-android12 to /e/OS1.20t-android13 was not done on a clean empty phone (all data erased), then I would try erasing everything (format+wipe in /e/OS recovery) then re-install the t - 1.20.
Another solution would be to go back to 1.19s
Thanks you for your input.
I already anticipated that someone will tell me to wipe and install again. You are right with the assumption that I performed a dirty flash from Android 12 to 13 without installing Stock Android 13 on that device. I did that when upgrading from Android 11 to 12 and had not problems of any kind. But with all the backup processes come in place when wiping the phone I was to comfortable to do it this time. So it may be my fault.
@piero Thank you, too. Maybe that is something I will try to get rid off the misbehavior. Otherwise I will wait for 1.21 and hope for the best.
Is it possible to use the Error report (from developer options) menu tab to get a hint where the issue could come from or even identify the root cause of it? Browsing the logs after a crash would fit me more than re-configuring my phone including format+wipe in /e/OS recovery.
- Vendor Name : GOOGLE
- Device name : Pixel 7
- Device CodeName : panther
- Version of /e/OS or Stock which existed previously : 1.19 -T- dev
- Is the device Rooted / Not rooted : not rooted
Everything works fine.
- Vendor Name : Samsung
- Device name : S10e
- Device CodeName : beyond0lte
- Version of /e/OS or Stock which existed previously : 1.19-s-dev
Update following this tip.
Everything works fine.
3 Likes
I have uncovered a new bug: if I load a webpage containing any embedded media (video/sound) in the default browser while playing something via the PodcastAddict app, the sound temporarily drops to half volume for about 3-5 seconds. this happens, even if none of the media in the new webpage is set to auto-play - just by being in the page, it affects the sound volume for the playing app.
Phone: Samsung Galaxy S10+
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.
Hi!
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”).
1 Like
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.
1 Like
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
*Vendor name: Samsung
*Device Name: Galaxy S7
*Device CodeName: herolte
*Previous version: 1.17-q
*Rooted: No
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).
1 Like
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…?
- Vendor Name: Fairphone
- Device name: FP3
- Device CodeName: FP3
- 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.