Successful clean install of /e/OS-T e-1.16-t-20231027-UNOFFICIAL-dreamlte by ronnz98 based on Stock Android 9.0 (Pie), One UI, but four apps do not work as they did here:
Fingerprint also does not work (timeout).
The app ‘Display’ does not work for me, neither the dark theme nor the font size etc. can be changed. I had to do this ‘font + display size’ and via the developer options. This is necessary for me because the default settings show very small icons and fonts - due to the default display resolution (1440 x 2960 pixels).
Very advantageous for future@ronnz98’s updates:
Updating can be done without a PC, as the e-Recovery allows ‘adb sideload’ from the microSD card.
Yeah, yeah @roonz98,
with your updated build e-1.16.1-t-20231028-UNOFFICIAL-dreamlte.zip the above mentioned bugs are fixed, that means the System Apps Battery + Display + Notifications + Sound & vibration as well as as well as Fingerprint are now fully functional
e-recovery
However, I have noticed inconsistencies when updating with the e-recovery via adb sideload - by the way, exactly the same problems that occur with the official e-recovery and the official /e/OS (Android 11) 'e-1.16-r-20231017342509-STABLE-dreamlte.zip. Details will follow.
Vendor Name: Samsung
Device name: Galaxy S8 SM-G950F
Device CodeName: dreamlte
Version of /e/OS which existed previously: e-1.20-t-20240224-UNOFFICIAL-dreamlte by @ronnz98
Version of /e/ Recovery which existed previously: recovery-e-1.20-t-20240224-UNOFFICIAL-dreamlte by @ronnz98
The device is Not rooted
I performed a Local Update (imported) from internal storage of SM-G950F which was installed lightning fast without any problems.
After the very easy manual update, the following are installed:
recovery-e-2.0-t-20240518-UNOFFICIAL-dreamlte by @ronnz98
Installed MicroG version 0.3.1.240913-10
BlissLauncher 3.0.1-beta
The new BlissLauncher with the colorful preset wallpaper suits the S8 very well. Thanks for ROM building, @ronnz98
Dear @ronnz98, my clique and I really appreciate your work and take our hats off to your commitment. But the voices are getting louder and louder against public test keys instead of personal or release keys, especially with AOSP 14 builds, because Google LLC is pushing more or less restrictively.