Thanks very much @ronnz98 for continuing your great work for clover.
This build seems to contain several major issues that are present for users of other devices too, it looks like /e/OS 2.0 isn’t quite ready yet for wider usage:
The Bliss Launcher constantly crashing happened to me with a fresh install after formatting data and wiping system and caches and then setting it to use the traditional 3-button navigation layout instead of gestures. It looks like it might be more stable with gestures. But with that together with the screen offset bug I decided to format it again and install e-1.21-t-20240420-UNOFFICIAL-clover.zip.
Now I have completely reinstalled (clean install) e-2.1-t-20240609-UNOFFICIAL-clover by @ronnz98. This time not with e-Rcovery V2.1 but TWRP Recovery twrp-3.7.0_12-0, which seems more reliable to me.
The clover runs well as before, although the BlissLauncher 3.0.1-beta no longer automatically switches to landscape mode. A temporary remedy is provided by a rotation app, which can be used to manually adjust each app to landscape / portrait format, regardless of whether the app supports one or the other display format.
Interesting option, thanks for mentioning that. Are you still using twrp-3.7.0_12-0, and does this /e/OS local update method depend on a specific recovery?
Also, are you using Bliss launcher? I had to switch to a different launcher due to this screen offset bug in both the search/widgets page as well as the main app icons page:
Local Update is fully compatible with TWRP 3.7.0_12-0. During the update process, TWRP opens and displays the update. However, TWRP does not need to be operated, it closes automatically and the Mi Pad boots automatically.
Yes, I use the BlissLuncher 3.0.1 (with greatly enlarged icons) to my satisfaction. Additionally, I use the app ‘Rotation Control’ with which I can force the display of each application in portrait and landscape format.
I just updated to e-2.2-t-20240723-UNOFFICIAL-clover.zip and this major bug is still present with Bliss launcher, and it also causes the system UI to repeatedly crash. It works fine though with an alternative launcher. Thanks to @Xxpsilon for the good tip on local updates. And a huge thanks to @ronnz98 for supporting clover devices.
Now that I look closer at your screenshots, it looks like you’re using the swipe gesture navigation mode, whereas I’m using the traditional three buttons at the bottom. Maybe that’s where the problem is.
OK I just tried setting the screen size setting to one notch larger, and it does fix the alignment bug in Bliss launcher. But that screen resolution is way too small for me (everything looks huge), so I’m going to stick with Neo Launcher until Bliss launcher gets fixed.
@ronnz98: I wonder if this bug is due to a wrong or missing setting in the build.prop file? I’m not very familiar with it, but I know that build.prop controls some parameters like device form factor and default screen resolution.
Successful manual update V2.2 from V2.1 via ‘Local Update’