These builds represent huge changes to Bliss OS in the form of both updates and feature changes. Not all these features have been catered to PC users though so there are still a ton of mobile features and options throughout the OS.

!!PLEASE NOTE!! The builds that use Kernel-5.2+ are no longer compatible with the AUTO_LOAD=old kernel command line option. If you are using this option to boot, then you will not be able to. It will bootloop.

Hi,
I have a Huawei Matebook 13 (Core i7-8565U, Whiskey Lake, UHD 620/MX 150). I am able to boot the may release of Android x86_x64 14.1 r4 k4.19 image but when I try to boot BlissOS live usb the booting just stops after Android has been detected at /dev/sda1. I've tried all three ISOs/kernals, but they all give the same result and I've tried adding GRALLOC=gbm.

I also tried to replace the BlissOS kernal with the one from Android x86 and that actually made the booting go as far as the "plasma circle" loading screen.. but it never made it passed that.

Is my laptop unsupported? Android x86 works "out of the box" with touch screen and everything. They can't be THAT different?

Edit: I tried BlissOS 11 with 4.19 kernel and it didn't work with the BlissIS kernel.. but for that release it kind of worked to use the Android x86 kernel... Android did load but touchpad, touchscreen and keyboard does not work.

I have an Intel Atom notebook from 2016, which is unfortunately locked in 32 bit UEFI. Bliss 11 works, but unfortunately audio doesn't work. The BIOS doesn't even recognise Bliss 12 as a bootable USB device. Any workaround?

I ran into some issues with Bliss OS Yantra/Merkaba that I was not able to work around yet, so the first part of this release is a build of that (with the issues it has) but confirmed booting for AMD Ryzen CPU.
The second part of this update is the first release of Bliss OS Lite 1.2, which is a stripped down version of Bliss OS, adding minimal extras to not conflict with things on our PC's These Lite builds will let me focus on solidifying a strong base to work from moving forward and allow me to get things fixed faster without having to backtrack and revert things coming from the new features added weekly to BlissROM, I was having issues with lockscreen, security, updates, etc.. So I decided to roll the source all the way back to Bliss OS 12.2, when it was mostly AOSP, and started with only adding a few pixel additions for customization.

I will also be moving to a different plan for releasing these builds. As I have already started baking it into the build script. The plan is to now have a separate branch/build for Vulkan, AMD, Atom & Generic. Doing it this way will allow me to focus on giving each machine type the attention it needs to help make things as stable as possible on that machine type. Unfortunately, this is also a sign that I have given up on my dreams of a truly universal .iso for all devices...

!!PLEASE NOTE!! If you have a previous Bliss OS install and want to switch to Bliss OS Lite, you will need to wipe your data image/partition/folder as this is a different OS. Updating Bliss OS Lite to newer Bliss OS Lite will not require you to wipe data.

The builds that use Kernel-5.2+ are no longer compatible with the AUTO_LOAD=old kernel command line option. If you are using this option to boot, then you will not be able to. It will bootloop.

Here's a short list of some of those updates.

Updates and fixes included in Bliss OS Lite:
• Finished setting up Gralloc and HWC switches in init
• Fixes for random crashes on boot
• Used a ton of updates from @Fcuzzocrea and LOS-x86 (Still in development)
• Fixes for booting in Live Mode
• Fixes for power buttons and power dialog not showing
• Bunch more updates, too many to list. check the changes

PLEASE NOTE I recommend everyone testing to also use this in Vulkan mode or boot using gbm_gralloc, as I am considering making it the default. Vulkan mode can be done from the Advanced grub menu if you installed using the bootable installer, or if you used a different grub, you will want to add "VULKAN=1" to the grub entry before the word "quiet". If your device doesn't support Vulkan, you can add "GRALLOC=gbm" to the same place in your grub entry. Sleep states should work fine after that.
Other bootloop issues can also be solved by booting with GRALLOC=gbm command -line option.

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer? | Terms of Service