So, I recently upgraded a Samsung S10 from iode 4 to iode 6.
The phone runs fine after reboot, but gets sluggish after opening and closing multiple apps.
Could it be that Android 15 is too high an upgrade for the S10? Considering that Samsung stopped upgrading the device at Android 12 or 11.
I must say my S10e doesn’t feel that responsive either.
This and a bunch of other frustations make me think that upgrading to 6.x was not the best decision I made…
Related:
I am checking with the devs on that one
I might be wrong because I don’t know how to further investigate this issue, but I have the feeling it’s a graphics issue:
Display rendering get slow. To the point I can sometimes see app windows refreshing when switching from one to another.
I also get frequent app crashes when watching streamed videos (from my media server) with vlc or mpv. It barely happened with iodé 4.x (except with corrupt video files, but that’s not relevant)
Online videos sometimes slightly freeze, even with a good connection.
I would guess these symptoms point to a video driver issue, or something like that.
Again, I might be wrong.
I haven’t debugged issues like this on Android before, but have been interested in either a debug mode from developer options or a 3rd party (trustworthy) app to give live “system monitoring” (RAM, CPU, GPU, maybe framerates, etc). Not sure if you want to poke around for one, I’ll try to put it on my “to do” to evaluate some options.
I have no debugging experience with android, but I could try to help if you give me pointers.
Hi,
still no improvements. Daily use is really awkward with this phone.
Should I consider rolling back to 4.x? Any news about how long 4.x is to be supported?
Thanks.
I’m running Iode 6.8 on several s10es and s10+ and it’s fine for daily use. Still love the phone for it’s compactness but yes, Iode 4 felt more responsive over all.
6.8 is utter crap. At best it should be considered as beta and labeled as such. Alas, no warning whatsoever
I strongly advise users not to upgrade.
It’s the worst upgrade ever for me: many usability regressions (latest android), laggy as hell with a few apps opened, many networking issues (power management?), bad touchscreen responsiveness and detection… not to mention many apps broke because Google Safetynet being deprecated.
→ a new install to downgrade to 4.5. Yet again many hours lost reinstalling and configuring everything… and I still don’t know if it’s worth it because no one seems to be able to tell me how long 4.x branch will be supported… and the Safetynet issue, which probably will be forever.
I’m so pissed
Eventually I downgraded to 4.25. Now everything is just fine and smooth. Even my banking app works again (I suppose the registration process is a bit more permissive on older androids).
Hopefully I’ll be able to use this phone a few more years.
Honestly I think this is your best bet. Pushing this device up to an Android 15 may just be too much. Surprised (but glad to hear) the banking app works again, maybe you are right the app itself has less security restrictions for older Android bases.
This smartphone seems decent to me in terms of raw power and memory. IMHO, the fact that it lags and bugs on android 15 comes from software issues (buggy drivers?), not hardware limitations.
I agree. I don’t see how a six-year-old flagship from a major OEM is too weak to run Android 15.
There are budget phones which run A15 just fine.
There must be some software issues (maybe in the Lineage base), and I hope they can be resolved. For me it’s okay as daily driver if I reboot at night, but there is a noticable difference to iode 4.
I’m not saying the hardware itself isn’t capable, you are right the chip itself is still better than a lot of budget phones.
But my experience is when the Lineage / iodé build gets too far beyond the newest manufacturer Android version that it can cause these headaches. The hardware drivers, etc. are all stuck behind closed source blobs targeted at the version the manufacturer supported (I believe A12 was the newest Samsung release?) ![]()
Yes, it was A12. So yo wouldn’t recommend to update any further? That’s bad securitywise but performancewise maybe conisderable. Maybe Iode can also cause some problems? I think I’ll switch to L4M, which is more streamlined and gets updates faster. Can report on how LOS 23 is working in November.
I would think a performance comparison between L4M 22.x and iodé 6.x should be very similar, but a cross-check would be a good confirmation (or not). They both get built in a very similar way with similar sources (for the lineage / vendor hardware bits).
Do you know how to make a reliable cross-check of both systems? Really interested in seeing the results.
No I don’t have a good handle on how to best do this besides the “eye test” which is frankly not worth much
There is Geekbench 6 from Aurora which seems like a common go-to for benchmarking, but what I suspect is that it won’t really uncover any OS optimization / issue (meaning it may be somewhat “system agnostic”).
To prove (or refute) this theory, I am building an unofficial v4-staging build for a Pixel 3a XL, as I also have the newest v6.8 build for that same device, and I have 2 of those devices on hand for testing.
So starting tomorrow I can run some tests on both devices (one with v4 and another with v6), But again I suspect that the Geekbench 6 results may be somewhat identical. I’ll report back after I get those tests done.
Maybe in the meantime someone has a better suggestion for measuring system performance?
Well it was a bit of a hassle, as the Lineage sources for Lineage 20.x aren’t as easily obtainable these days, so making an iodé 4.x build isn’t as easy. In the end for a quick test, I installed a Lineage 20 build I found, but that just confirmed my guess: a benchmarking tool like Geekbench 6 gave identical results for Lineage 20.0 (no GAPPS or microG) and iodé 6.8 on identical hardware (Pixel 3a XL).
The search for a better way to benchmark performance differences between different ROMs or different ROM versions (on identical hardware) continues.
Maybe DevCheck gets the job done? But only with the pro version and maybe will present same results as geekbench. That’s all I know. Thanks for your effort though @rik!