Bliss OS (x86) for PC's - 12.x Development - Beta Builds

2,701 posts
Thanks Meter: 4,836
Post Reply Email Thread
Announcement from electrikjesus: Team Bliss is rolling out with Alpha builds of Bliss OS 12.0, Android 10 for PC's

Team Bliss is pleased to present to you
Bliss-OS for PCs based on Android 10
An Open Source OS, based on Android, that incorporates many customizations options and added security features. And it is available for just about any Chromebook, Windows/Linux PC or tablet released in the last 4 years

Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.

Bliss-OS comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.

First, a little bit about this project...
Starting in Android Pie, Bliss OS took a different approach to building Android for PC's. Taking inspiration from @phhusson 's Treble methods, and Intel's Project Celadon, and Android-x86 Project, we have now adapted that method to be a bit more streamlined, and packaged it up so that it can work a bit more dynamically. The manifest can be found at:* and the new patching system and build script are all included in
These Bliss OS releases will be considered the Bleeding Edge of development for Android on x86, and we will be marking most of our additions to be sent down the ladder to our Android-PC project & hopefully Android-x86 Project as well.

ROM Porting Details:
As with Pie, things this round will be done a bit differently using a new adaptation of our patching system to build for x86 devices, making updating and maintaining far easier than before, and even lowers the bar for understanding how it all works. But things were still complicated enough for us to see room for improvement. So we have also packaged up all the x86 bits we add to Bliss OS, minus a few goodies and are making them available to the entire community to add to their ROM projects. You can find the basics on GitHub already, and for those interested in adding x86 support to your own ROM, I was able to squash things down to a single commit in build/make in order to help get the ball rolling. This will also be the source we are helping out Android-x86 Project with, so don't be surprised if things change a bit to reflect that projects branding more.
I'm always open to suggestions on how we can improve upon things too, so don't be afraid to speak up, just remember to be considerate upon doing so

We will be updating our website also over the next few weeks to feature a new downloads section, as well as further information about using our source for commercial projects.

XDA's Bliss AIO Thread

Bliss Source

BlissRoms Devices Source

Bliss' Android-PC Project

Bliss OS Source

Bliss OS Kernel Source

Bliss OS downloads can be a bit confusing to most users initially. We have tried to slim down the methods for which there can be differences by revamping our downloads section of the websites. For newbies, this will help a lot. For advanced users though, like all of you We have a little Q&A for what the filenames mean below:

Build Types Explained:

Q: Bliss builds come with funny names. Why?
A: Because we felt the need to include the various branches for Kernel, Mesa, & Firmware in the build name.
So, when you see a name like this:
It can be broken into 3-4 parts.
Build ID: "Bliss-OS-v11.10--OFFICIAL-20190901-1611_x86_64"
Kernel Branch: "_k-k4.19.50-ax86-ga"
Mesa Branch: "_m-18.3.5-pie-x86-llvm80_"
libdrm Branch: "_ld-2.4.99-ma-p"
drm_gralloc Branch: "_dg-pie-x86"

Some uncommon flags:

drm_hwcomposer: "_dhpie-x86"
Firmware Branch: ""
llvm Branch: "_lv18.0.3-llvm9.0"

Q: What do the parts of the kernel names mean?
A: When we add a batch of commits to the kernels, we like to save that version with an identifier. So the most common parts to the kernel names are as follows:
-ax86 : Means that this kernel started off from the Android-x86 repo, or has the majority of Chih Wei's commits for that kernel
-ma : Means this started out from Maurossi's repo. (
-ga/gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (
-ipts : Means that we are including some specific commits for the Intel IPTS touchscreens (mostly in the Surface line of devices) These builds likely won't run well on most other devices.
-yl : Means that kernel includes the latest Intel BayTrail/CherryTrail commits from @youling257
-jw/jwd/jd: Means that kernel includes the latest Intel BayTrail/CherryTrail commits from

Q: OK, So I have a Blah-Blah CPU, with a Such'n'such GPU, what builds are right for me?
A: Well, we have a method to all our madness there. We build Bliss OS with different kernels that work as a way to make it more compatible with different types of devices. Here is the breakdown on those:
k4.9 These are considered the most "Stable" builds, they will work across most older and some recent devices.
k4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
k4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
k4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
k4.19+ This is our current mainline kernel branch. Intended for newer devices. Even more touchscreen support and ACPI support
k4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
k5.0+ This is where things will start getting tricky. Even more touchscreen support, and added support for ARM/ARM64/ATOM etc, but also a ton of Android kernel commits start making their way into things.

Bliss OS 12.0 Alpha Downloads

These are to be considered "in development" and are in no way intended for general use. We will expect any bug reports or issues to be accompanied by a log of some sort. Whether it's in the form of an attached file, or a link to a hastebin or something. It just has to be a log. If you post a screenshot, saying "it no workie", you won't get very far. We tend to only help those who help themselves.*
With that being said, the downloads are a little hidden this round. We added a secret download button to the website for out Bliss OS 12 alpha builds, and the secret code to reveal it is hidden within this first post (somewhere)

Please visit or and the Bliss OS 12 alpha testers section is just below the Downloads section. We have removed the need for a code to be entered, so just use the link to head to the downloads for Bliss OS 12.x

Team Bliss is not responsible in any way for anything that happens to your device in the process of installing

Please familiarize yourself with the methods of install as well as what could go wrong before moving forward.* Please make sure you download the correct version of Bliss for your specific device.* The links are labeled clearly.

We have moved the instructions to be a part of our docs site

[li]For the main instructions to get going with Bliss OS, you can check out our Installation Guide[/li]
[li]If you get into a bind with your install, you should see our Troubleshooting section[/li]
[li]For the few addons and other info we have for Bliss OS installs, you can check out our Extras section[/li]
[li]And if you're ready to start building and testing new things, you can check out the Bliss OS Build Guide[/li]
[li]When you are ready to contribute back to the project, we also have a Git Started guide to help get things rolling with our Gerrit.[/li]

This is a development alpha release, so there will be bugs.

Before you even think about filing a bug or posting that something isn't working, we want you to scroll down to the second post of this thread and check out each of the update posts linked there. Those will mostly state where we are in development and what still stands to be updated/fixed as well as what is recently fixed. Once you have done that to verify your issue is not already identified, you should proceed further below.

Known Issues:

Sleep Issues on non-Vulkan machines. This is due to a bug in drm_gralloc/drm_hwcomposer. Haven't found a fix for it for Pie or Android 10. FIX: Run in Vulkan Mode if you can
Lockscreen shows, then the device crashes. Please see above issue as this is a direct result of said sleep issues
I can't install Magisk in this release, why? This is due to the lack of a ramdisk/boot image this round. Due to changes in Android 10, this was a change we needed to make.
My favorite game won't work on Bliss OS 12.x when it did on Bliss OS 11.x. What gives? In Android 10, many things changed, one of which was how Intel's Houdini worked in Android. Since we've used this library for ARM translation in the past (what your game uses to make it work) some apps that are released without x86/x86_64 compatibility or built as universal apk's will not work. This is not a problem we will be able to fix on our own. It is an issue with app developers not wanting to take the time to add Universal APK support. Pass them this if needed:

For All Other Issues:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us.* It will save you and our team quite some time.
Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
After downloading the Catlog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving.
As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.

Manual Logging:
Use the alt-f1 console, and in the console, type:
logcat > sdcard/log_name.txt
Then alt-f7 to get back to the Android UI, and replacate the issue. When done, use alt-f1 to go back to console and ctrl-c to stop the logging.
Copy and paste the entire log either to Hastebin or Pastebin

Save the log, and copy and paste the link into the forum with a brief description of the error.
Only issues with adequate info and logs attached will be taken seriously. Thank you.

Advance debugging options are also available through the parts we inherit from Android-x86 Project. You can read up on those here:

Once you are ready to report your bugs, you will need to head over to our GitHub's bug_reports repo, and then use one of the given templates to fill out your bug report or feature request:

@Jackeagle @electrikjesus @rwaterspf1 @Makaveli_da_dev @ElfinJNoty @BitOBSessiOn @customworx
@nilac @sixohtew @aclegg2011 @Roger.T @T.M.Wrath @kanttii @rev3nt3ch @techfreak243 @SuperDroidBond @USA_RedDragon @bcrichster

@deadmanxXD @krittin98 @BlackScorpion @techexhibeo @droidbot @siphonay @pacer456 @nitin1438 @theGeekyLad @kunalshah912 @regalstreak @lordarcadius

A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!

We really appreciate all your knowledge & hard work!

About Bliss Family of ROMs

Bliss Family of ROMs aims to develop and maintain various OS & software projects for educational and the Android community building purposes.*

Team membership consist of and provides:
Training, development opportunities, design opportunities, build servers when available, download servers, design & development software, as well as a stress free team oriented community of professionals and mentors in all fields revolving around Android development. To join our team, please visit either of our websites, and find the Join Team Bliss link.

If someone wants to donate, please do so via this PayPal link:

PayPal Link


We receive a small donation each time you make a purchase with “Amazon Smile”:


The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible.

We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.

[li]Please do not ask for ETA's[/li]
[li]We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts[/li]
[li]Team Bliss will allow some minor off-topic comments in our development threads. Please post in the general forums for off-topic comments and/or questions. Overall, please keep comments relevant to development, as this better helps you and our teamwhen trying to determine problems that users are having. We appreciate all levels of knowledge in our threads, and therefore we ask that the seasoned members be helpful to those with less knowledge. Most importantly, do NOT troll those with less knowledge than yourself.[/li]

Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts. We thank you for adhering to our thread rules.


Official Platform Links

Thank you for using Bliss!* And as always: #StayBlissful

XDA:DevDB Information
Bliss OS (x86) for PC's - 12.x Development - Android 10, ROM for all devices (see above for details)

electrikjesus, jackeagle
Source Code:

ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP, LOS, Android-x86

Version Information
Status: Testing

Created 2019-11-16
Last Updated 2020-02-05
The Following 39 Users Say Thank You to electrikjesus For This Useful Post: [ View ] Gift electrikjesus Ad-Free
16th November 2019, 06:00 PM |#2  
Recent Update Posts:

Updates, Round 1 - 2019.11.19

Second round of updates - 2019.12.16

Bliss OS 12.2 Alpha Updates - 2019.12.28

Bliss OS - Yantra - 12.2 Beta Release - 2020.02.05

Bliss OS "Yantra" 12.3 Beta Release - 2020-02-23

Bliss OS "Yantra" 12.4 Release Candidate 1 - 2020-02-27
The Following 10 Users Say Thank You to electrikjesus For This Useful Post: [ View ] Gift electrikjesus Ad-Free
16th November 2019, 09:19 PM |#4  
Junior Member
Flag Sivas
Thanks Meter: 0
working smoothly as always, keep it up! btw why is there windows logo on the pictures lol
16th November 2019, 09:26 PM |#5  
Originally Posted by kc4knc

working smoothly as always, keep it up! btw why is there windows logo on the pictures lol

It was a Windows tablet mockup I used for the image, in order to help signify our target device type
The Following 3 Users Say Thank You to electrikjesus For This Useful Post: [ View ] Gift electrikjesus Ad-Free
17th November 2019, 01:36 PM |#6  
Junior Member
Thanks Meter: 0
I really like the secret code idea
Although I copied the link instead of writing the code since It was easier at that point^^

Edit: nvm I just noticed that u hinted the code was hidden in ur post XD
17th November 2019, 09:11 PM |#7  
Update on known issues

Chrome not working correctly - Please go to recents, and click the chrome icon, then click freeform. This will allow chrome to not close. A better solution is to download Brave browser from Play Store. The next update will include LOS's Jelly browser instead, since that's a small browser source we can add to the manifest.
Play Store sign-in not showing anything - Please open this window in freeform and resize until you can see what is presented on screen.
The Following 2 Users Say Thank You to electrikjesus For This Useful Post: [ View ] Gift electrikjesus Ad-Free
18th November 2019, 11:47 AM |#8  
Senior Member
Thanks Meter: 41
where i can type the secret code? no space, it can't type.
I can't find the type the secret code space.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20191118-194411.png
Views:	5024
Size:	247.4 KB
ID:	4879711  
Attached Files
File Type: zip - [Click for QR Code] (5.10 MB, 2250 views)
18th November 2019, 01:05 PM |#9  
bfmetcalf's Avatar
Senior Member
Thanks Meter: 253
Donate to Me
Originally Posted by youling257

where i can type the secret code? no space, it can't type.
I can't find the type the secret code space.

Just click on that and start typing. It will change when you have finished typing.
18th November 2019, 01:17 PM |#10  
Senior Member
Thanks Meter: 41
Originally Posted by bfmetcalf

Just click on that and start typing. It will change when you have finished typing.

Android chrome, finger click that, no pop up android screen keyboard for type.
18th November 2019, 01:39 PM |#11  
bfmetcalf's Avatar
Senior Member
Thanks Meter: 253
Donate to Me
Originally Posted by youling257

Android chrome, finger click that, no pop up android screen keyboard for type.

Hmmm, interesting. Maybe do it on a computer and send the link to your phone.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread