Introducing the latest addition to the Bliss OS family: Bliss OS 16, codenamed typhoon-x86, based on Android 13 QPR2.

#FeelTheWind

You can try the new BlissOS 16 Beta here :
https://mega.nz/folder/ek4wnaQB#rzOD7TFJl59x2Im6rLvO6g

And remember, these are Beta builds so bugs are expected.

Like what we are doing on Bliss and want to help us go further? Consider joining the team and find out how easy it is to make a difference in the community ;)

https://goo.gl/forms/PdiaAj1PojosmehK2

BlissOS 16.8 is here with QPR3 & July Security Patch and Kernel 6.1

https://blog.blissos.org/bliss-168
#StayBlissful #FeelTheWind

16.8 is available to download here

https://mega.nz/folder/ek4wnaQB#rzOD7TFJl59x2Im6rLvO6g

#FeelTheWind

XDA thread for BlissOS 16 has been created :
https://forum.xda-developers.com/t/bliss-os-x86_64-v2-for-pcs-16-x-development-beta-builds.4608697/

Meanwhile, if you have any bugs encountered with the OS, we recommend you to report those on our Github

For BlissOS 14.x & 15.x :
https://github.com/BlissRoms-x86/support/issues

For BlissOS 16.x :
https://github.com/BlissOS/bug_reports/issues

Templates for reports will be available soon.

To those concerned about KernelSU's security:

Today's KernelSU has come a long way from the original KernelSU created by zx2c4 several years ago(kernel-assisted-superuser), and the issues back then have been addressed:

1. We now have authorization management, so we can control which apps can use Root instead of any app being able to use Root without user awareness like before.
2. We use signature verification for manager authentication instead of package name verification. Signatures can't be spoofed like package names.
3. We've also added features like App Profiles to restrict Root privileges.

Additionally, we welcome any security researchers to discuss KernelSU's potential attack surfaces with us. We will spare no effort to improve KernelSU's security.

They got our trust

We've successfully tested and verify that BlissOS can be able to boot on an exFAT partition. The test is done on a Windows 10 VM, we split the Windows disk and format it to exFAT directly on Disk Management. After that, we copy kernel, initrd.img, system.sfs from a BlissOS 15 iso and then create data.img by using dd & mkfs.ext4 provided by Cygwin. Then we install Grub2Win and make a simple option for it.

Compare to FAT32, exFAT provide a major advantage in which you can be able to create data.img larger than 4GB and the speed should be the same, or even better on exFAT side. When comparing to NTFS, while exFAT speed is considered slower than NTFS, we don't know exactly how slow because the performance when booting on NTFS is being taxed too. We are using NTFS-3G driver (https://github.com/tuxera/ntfs-3g) which is an userspace driver that use FUSE so the speed is not high comparing to NTFS driver on Windows.

If you want another file-system option for the BlissOS drive that Windows can still be able to read it beside FAT32 & NTFS, there's now exFAT. However, we still recommend using EXT4, as this is what Linux & Android usually use, and it's literally faster than both of these options.

Also, there is no plan for exFAT as an option for the bootable installer yet.