After x Close app the (empty) /e/ standard wallpaper is displayed without any characters.
After the system is set up, I installed the OpenLauncher activated it as Home app (Yes). This quiets the BlissLauncher for the time being, but the message “BlissLauncher keeps stopping” pops up again and again at regular intervals, so I deactivated it completely via adb shell pm disable foundation.e.blisslauncher
I’ve now customized the OpenLauncher a tiny bit (screenshot): Murena
The OpenLauncher is not a BlissLauncher, but the overall result is much better than with system startup and I can get comfortable with it.
Ok, could do it now, one need to swipe to times from top to button to go to the settings. There one can install f-droid and the open launcher app.
However if I run
adb shell pm disable foundation.e.blisslauncher
Exception occurred while executing ‘disable’:
java.lang.SecurityException: Shell cannot change component state for foundation.e.blisslauncher/null to 2
at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:24283)
at com.android.server.pm.PackageManagerService.setApplicationEnabledSetting(PackageManagerService.java:24079)
at com.android.server.pm.PackageManagerShellCommand.runSetEnabledSetting(PackageManagerShellCommand.java:2194)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:240)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:24948)
at android.os.Binder.shellCommand(Binder.java:950)
at android.os.Binder.onTransact(Binder.java:834)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4818)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:8937)
at android.os.Binder.execTransactInternal(Binder.java:1184)
at android.os.Binder.execTransact(Binder.java:1143)
(base) ronnz@ronnz-mint:~/Downloads$
Hello i’m bringing good news !
The update below works for the S3 LTE version, however the Bliss Launcher still doesn’t work.
I tried alternative like Fossify Launcher but the aesthetic is really bad.
Step 0 : Sideload another Home app (like what did Xxpsilon on the post of Aug 2024), it’s necessary because without that you are stuck in the settings menu.
Step 1 : Completely uninstall the Bliss Launcher (not disabled but entirely removed)
To do this you can use De-Bloater an app that requires root access provided by magisk.
(idk if it’s possible to do it via adb, i just found the commands to disable apps not uninstall…)
Step 2 : Install the apk of the Bliss Launcher and setup it as home launcher in the settings.
Note :
The F-droid version of Bliss Launcher is outdated, the widget menu doesn’t work for example. However i found this fork where the widget work
Installing Magisk (or Delta Magisk) After verification it’s the build who seems to make the recovery unaccessible (recovery loading and black screen), you will need to reflash it with Odin
If you don’t trust the bliss launcher fork you can also use Lawnchair, it’s a pretty good alternative i think
I have a few question, is there a way to get a newer apk version of the Bliss Launcher ? (Like extracting it from newer version of e/os)
And do you apply new security patchs on your /e/OS update ?
If it’s the case than it’s really cool, your build is the last rom compatible with LTE with updated security patch (if i’m not wrong).
After flashing this build, TWRP (any version by Awesometic) can’t be accessed anymore after rebooting the device without flashing it again (“Recovery Booting” message and black screen), and you’re stuck in this bootloop when you try to hard reboot, until you flash the recovery again.
The problem doesn’t exist with the LineageOS 19.1 or others roms.
The recents button don’t work, it doesn’t show the recent apps switch, the problems doesn’t seems to come from launchers, i tried with Launchair and Fossy Launcher and it doesn’t change anything.
→ To be more precise the recent button work, it’s the recent apps switch (who is bind in the recent button) who doesn’t work.