Bliss OS (x86) for PC's - 14.x/15.x Development - Stable Builds

[electrikjesus]

HI Mr jesus - i have this machine and latest build won't boot. What is wrong ?

https://www.asus.com/Laptops/X553MA/overview/

Without any logs, cpu info, install info, etc, you might as well be calling me Mrrs Cleo

 

[Swehub]

Without any logs, cpu info, install info, etc, you might as well be calling me Mrrs Cleo

:laugh: I will provide more information.

Must try this first: Bliss-OS-Merkaba-v12.6-android_x86_64-OFFICIAL-202005041218_k-k4.19.110-ax86-ga-rmi_m-10.0.8-ax86_ld-2.4.100-ax86-ma_dg-_dh-_mg-_gms_cros-hd_cros-wv

 

[.:Addicted:.]

I just used lite version & found it's not compatible with normal Merkaba-v12.6 k5.6 data partition. So they kind of messed up.
Merkaba-v12.6 k5.6 -> many thiings not working(bliss related modification, even a hide status bar lead to system freeze)
Bliss lite -> Android x86 experience with extra bliss app bloat.(bliss paper, bliss about etc)+xda gesture(lol i even bought that)+Brave(idk, wouldn't bromite a better alternative). But everything seems working, no crashes.(Everything(AOSP related) was working in non lite version too)

So my question is, if i keep using bliss lite & another update arrives, would that be compatible with previous bliss lite data? Coz i can't keep reinstalling apps or backup etc.

 

[electrikjesus]

I just used lite version & found it's not compatible with normal Merkaba-v12.6 k5.6 data partition. So they kind of messed up.
Merkaba-v12.6 k5.6 -> many thiings not working(bliss related modification, even a hide status bar lead to system freeze)
Bliss lite -> Android x86 experience with extra bliss app bloat.(bliss paper, bliss about etc)+xda gesture(lol i even bought that)+Brave(idk, wouldn't bromite a better alternative). But everything seems working, no crashes.(Everything(AOSP related) was working in non lite version too)

So my question is, if i keep using bliss lite & another update arrives, would that be compatible with previous bliss lite data? Coz i can't keep reinstalling apps or backup etc.

No, it should be a given to completely wipe data before flashing Bliss OS Lite. But if you're flashing an update for Bliss OS Lite on top a previous Bliss OS Lite build, you should be good to go

 

[.:Addicted:.]

But if you're flashing an update for Bliss OS Lite on top a previous Bliss OS Lite build, you should be good to go

Ok, thanks for the info. I plan on to use bliss 12 lite since it seems lot faster than bliss 11 (even bliss 12 non lite is faster than bliss 11)

Hope we'll see more bliss mods on lite version too.


Anyway to disable display off after a short time of booting if screen lock is enabled? Coz i have to unlock immediately else display turns off & can't turn it on without force restart.(volume/power button didn't work)

Edit: fstab again in initrd.img instead of system.img

 

[vladone97]

I'm running Bliss-OS-Merkaba-v12.6-android_x86_64-OFFICIAL-202005041401_k-k5.6.2-si-yling-rmi_m-10.0.8-ax86_ld-2.4.100-ax86-ma_dg-_dh-_mg-_gms_cros-hd_cros-wv.iso on a One Mix 1S and I can't run any games. They all crash on startup. It seems like Bliss OS is acting as if the "Enable native bridge" setting was toggled off, even though I have it toggled on.
log: https://drive.google.com/file/d/1-a8-hSh_LR3kdSE68r64ZM4UYpi0nqV9/view?usp=drivesdk

 

[.:Addicted:.]

It seems like Bliss OS is acting as if the "Enable native bridge" setting was toggled off, even though I have it toggled on.
log: https://drive.google.com/file/d/1-a8-hSh_LR3kdSE68r64ZM4UYpi0nqV9/view?usp=drivesdk

Read release notes. Or best don't use it at all since you discovered a **new** bug.

 

[Swehub]

It works now. Immediately after installation use VULKAN mode. Otherwise it will be bootloop

 

[.:Addicted:.]

Anyway to disable display off after a short time of booting if screen lock is enabled? Coz i have to unlock immediately else display turns off & can't turn it on without force restart.(volume/power button didn't work)

@electrikjesus I noticed sleep works. Tablet goes to sleep if i press power button, display turns off completely & power button LED blinks as supposed to be in sleep state.
But my problem is i can't use it after sleep.
If i press power button, device wakes up. I can confirm that from solid power button LED & sound i hear from speaker (i get a notification sound when i start my device) But display stays off. I tried using tasker & binding vol long press to turn on display. But that doesn't work. So only way i got is restart
Any proper way to turn on display in such case?
Edit: sleep.state none doesn't help

 

[electrikjesus]

@electrikjesus I noticed sleep works. Tablet goes to sleep if i press power button, display turns off completely & power button LED blinks as supposed to be in sleep state.
But my problem is i can't use it after sleep.
If i press power button, device wakes up. I can confirm that from solid power button LED & sound i hear from speaker (i get a notification sound when i start my device) But display stays off. I tried using tasker & binding vol long press to turn on display. But that doesn't work. So only way i got is restart
Any proper way to turn on display in such case?
Edit: sleep.state none doesn't help

It should be tied to spacebar after power is pressed. Try tapping the space a couple times.
If that doesn't help, we add a flag in board.config for the fake deep sleep we have to use on PC hardware, so tht might be messing with some devices

 

[.:Addicted:.]

It should be tied to spacebar after power is pressed. Try tapping the space a couple times.
If that doesn't help, we add a flag in board.config for the fake deep sleep we have to use on PC hardware, so that might be messing with some devices

Nop, when i press spacebar, i can hear tap sound. But display not turning on.
Also i would prefer vol button or power button to wake up device since it has detachable keyboard & can be used as tablet independently.
@electrikjesus

 

[YellowSomething]

I'm curious; has anyone else had any issues installing this on an AMD C-50?
I can't seem to get it to work, but have seen others running android on these from inactive threads and forums, years ago.

 

[.:Addicted:.]

Nop, when i press spacebar, i can hear tap sound. But display not turning on.
Also i would prefer vol button or power button to wake up device since it has detachable keyboard & can be used as tablet independently.
@electrikjesus

Can anyone help me turning on display

 

[electrikjesus]

Can anyone help me turning on display

You may need some commits for i915 to resume from suspend, and that is a kernel commit. So it may have to wait for a new release. The other thought is to google some of the fbcon commands for your CPU/GPU and see if any of those can help with backlight/brightness issues

 

[khanhtranngoccva]

Can you make the freeform windows in Android behave exactly like on Chrome OS, especially the resizing part?

 

[electrikjesus]

Can you make the freeform windows in Android behave exactly like on Chrome OS, especially the resizing part?

Unfortunately, no we can't. Were focused on working with the methods that Google includes in AOSP, and making those work for our setup

 

[Swehub]

When will you post next version ? waiting with excitement

Can you add Magisk Manager to Android 10

 

[khanhtranngoccva]

Is this the correct configuration to boot Bliss OS? I am dualbooting with Linux Mint instead of using the default Windows bootloader. The boot splash appeared, but no linux shell sessions started and the OS did not proceed to launcher.
menuentry "Bliss OS" {
search --no-floppy --set=root --file /BlissOS/system.img
linux (hd0,msdos2)/BlissOS/kernel root=/dev/ram0 USE_SQUASHFS=0 quiet androidboot.selinux=permissive androidboot.hardware=android_x86_64 acpi_sleep=s3_bios,s3_mode mitigations=off SRC=/BlissOS
initrd (hd0,msdos2)/BlissOS/initrd.img
}
Directories available on (hd0,msdos2): /BlissOS/data.img
/BlissOS/system.img
/BlissOS/initrd.img
/BlissOS/kernel

 

[electrikjesus]

Is this the correct configuration to boot Bliss OS? I am dualbooting with Linux Mint instead of using the default Windows bootloader. The boot splash appeared, but no linux shell sessions started and the OS did not proceed to launcher.
menuentry "Bliss OS" {
search --no-floppy --set=root --file /BlissOS/system.img
linux (hd0,msdos2)/BlissOS/kernel root=/dev/ram0 USE_SQUASHFS=0 quiet androidboot.selinux=permissive androidboot.hardware=android_x86_64 acpi_sleep=s3_bios,s3_mode mitigations=off SRC=/BlissOS
initrd (hd0,msdos2)/BlissOS/initrd.img
}
Directories available on (hd0,msdos2): /BlissOS/data.img
/BlissOS/system.img
/BlissOS/initrd.img
/BlissOS/kernel

It looks correct. If you're on mint though, you should just be able to run "sudo update-grub" and it''ll add what it finds. You may also need to add "DATA=" so it looks in the root folder ov where you installed it for the data folder (assuming it's ext3/ext4)

 

[electrikjesus]

When will you post next version ? waiting with excitement

Can you add Magisk Manager to Android 10

This type of question is considered "bad manners" for development communities. Please think of this before asking for ETA's