• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

cjeu100

Senior Member
Jan 26, 2020
214
107
I've got BlissOS 14.3 more or less working on an old Nextbook (Intel Clover Trail 32-bit only, UEFI only, tablet that can't run much else).

I have to do the following tweaks to get it working in this low memory environment:
  1. Boot into debug mode every time and manually do "swapon /dev/mmcblk1p3" to activate a much-need 4GB swap partition created at install time. Occasionally it's mmcblk2 instead of mmcblk1.

  2. In the boot debug (the only way I found to get root), I had to rename /android/system/bin/logcat to logcat.no to stop it from working. Otherwise, when lmkd would fail (see log below), logcat would absorb all CPU and memory and make the tablet lock up. A rather counterproductive result to the intent of lmkd!

This is what happens to lmkd, which in turn sends logcat nuts and locks up the tablet (I presume this'll get fixed in a later release):
Code:
11-03 21:15:28.592  1749  1749 E lowmemorykiller: /proc/zoneinfo parse error                            
11-03 21:15:28.592  1749  1749 E lowmemorykiller: Failed to get free memory!                            
11-03 21:15:28.602  1749  1749 E lowmemorykiller: /proc/zoneinfo parse error                            
11-03 21:15:28.602  1749  1749 E lowmemorykiller: Failed to get free memory!                            
11-03 21:15:28.613  1749  1749 E lowmemorykiller: /proc/zoneinfo parse error                            
11-03 21:15:28.613  1749  1749 E lowmemorykiller: Failed to get free memory!                            
11-03 21:15:28.623  1749  1749 E lowmemorykiller: /proc/zoneinfo parse error                            
11-03 21:15:28.623  1749  1749 E lowmemorykiller: Failed to get free memory!                            
11-03 21:15:28.635  1749  1749 E lowmemorykiller: /proc/zoneinfo parse error                            
11-03 21:15:28.635  1749  1749 E lowmemorykiller: Failed to get free memory!

Anyone got tips on how to get swap to mount on boot?
32 bit build is better for low ram devices. according to developer 14.x builds have all the lowmem configs added in so the init will trigger a better system config for low ram/low spec devices. To get root you have to extract system.img from system.sfs with 7-zip or gearlock will automatically do it with supercharge function. If ther build you downloaded has gearlock then you can use gearboot to execute scripts- https://wiki.supreme-gamers.com/gearlock/developer-guide/gearboot-documentation/
you can increase performance by editing /default.prop (with nano /default.prop if gearlock installed) and changing ro.debuggable=1 to ro.debuggable=0
if you cant change files in /system when android booted then mount -o remount,rw /
type su first before other commands to get root access
 

awnz

New member
Aug 18, 2019
3
0
Thanks. This is already a 32 bit build (it's a 32-bit only CPU - Intel Atom / Clover Trail, the platform Intel famously pushed for x86 tablets then just abandoned) and when I checked /default.prop, ro.debuggable=0 is already set for this build (14.3, 32bit FOSS).
 

pipperonni

New member
Nov 11, 2021
1
0
Hello friends. I am new to Bliss OS. I have tried 11 and now 14, but all the same. Installing ok, staring - OK, but 90 % of the apps just keep crushing, some of them are working minute or two, some are not even starting, G apps are the same, every few minutes there is an annoying pop up that tells me that Google Play stopped work, but the same time I am in the app and I am downloading apps. I am launching Youtube, it runs ok a few minutes and just disappears. None of the browsers didn't work for me, I was able to run only Opera Mini and when trying to watch online movies I see a black screen.

Thank you in advance
 

MCH_LNZ

Member
Nov 13, 2021
5
6
Hello. I usually lurk these forums, but registered to contribute a bit of useful knowledge for those trying to install Bliss OS on Chuwi Hi12 tablets with Atom Z8300 cpu.

1) If trying to install Bliss OS 14.3 you get a kernel panic and the tablet resets, first install Bliss OS 11.x
so it will partition eMMC storage correctly, then try again installing 14.3

2) A possible solution to touchscreen issues

Bliss OS 14.3 has a kernel recent enough to support natively Hi12 touchscreen controller, and
it works correctly when running from a live USB key,.
But once installed in the internal eMMC storage, usually either touchscreen does not work anymore or only intermittently.

I could not identify the exact cause, but by adding a "fake" Windows boot option in the EFI partition and changing an uefi/bios setting now it works even when booting from eMMC.

Connect an usb keyboard to the tablet
boot with a linux live distribution and from command line
mount the EFI partition
then change directory to it
create folder "Microsoft/Boot"
copy all the files in subfolder "Android" (in EFI partition) to "Microsoft/Boot"
then change directory to "Microsoft/Boot" and copy "grubx64.efi" to "bootmgfw.efi"
unmount the EFI partition and reboot
after this (with an USB keyboard still connected to the tablet)
reboot pressing esc to enter uefi/bios settings
in bios settings select "chipset" --> "south bridge" --> "LPSS & SCC Configuration"
then set "SCC SDIO Support" to "PCI Mode".
At this point when you reboot you will se both Android and (fake) Windows boot options
select the "Android" option and now touchscreen works correctly.

Remember to select the boot option with Vulkan support (VULKAN=1) or else you will have some issues with video playback and some slowdowns.

I don't know why it works, my guess is that there must be a timing issue while initializing the touchscreen controller and making the tablet spend extra time loading the "windows" bitmap and handling SDIO using PCI mode the controller gets properly initialized by UEFI.

UPDATE:
Selecting "Android" works when "Windows" is selected by default, but if at boot "Android" is already selected by default, you have to select "Windows" (using vol+ and vol- buttons) or else touchscreen won't be initialized correctly.
 
Last edited:

Michael62

Member
Aug 19, 2008
8
0
Sony Xperia X Compact
Please recommend build with gapps for this old PC:

CPU: Intel Celeron T1600 (Merom DC 1M, M0)
1666 MHz (10.00x166.7) @ 1662 MHz (10.00x166.2)
Chipset: Intel GL40 (Cantiga-GL) + ICH9M (Base)
Memory: 4Gb
Graphics: Intel GM45/47 Chipset - Integrated Graphics 0 [B3] [Fujitsu-Siemens Computers]
Intel GMA 4500(M)(HD), 1358138 KB
Graphics: Intel GM45/47 Chipset - Integrated Graphics 1 [B3] [Fujitsu-Siemens Computers]
Mobile Intel(R) 4 Series Express Chipset Family, 1358138 KB
Sound: Intel 82801IB ICH9 - High Definition Audio [A3]
Network: RealTek Semiconductor RTL8102E/8103E Fast Ethernet NIC
Network: Realtek RTL8187B Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter

Looks like I have problem with wireless driver.
Live USB debug boot screen before froze:
image.png

I can press ctrl-c here and get console
 
Last edited:

MCH_LNZ

Member
Nov 13, 2021
5
6
Please recommend build with gapps for this old PC:

CPU: Intel Celeron T1600 (Merom DC 1M, M0)
1666 MHz (10.00x166.7) @ 1662 MHz (10.00x166.2)
Chipset: Intel GL40 (Cantiga-GL) + ICH9M (Base)
Memory: 4Gb
Graphics: Intel GM45/47 Chipset - Integrated Graphics 0 [B3] [Fujitsu-Siemens Computers]
Intel GMA 4500(M)(HD), 1358138 KB
Graphics: Intel GM45/47 Chipset - Integrated Graphics 1 [B3] [Fujitsu-Siemens Computers]
Mobile Intel(R) 4 Series Express Chipset Family, 1358138 KB
Sound: Intel 82801IB ICH9 - High Definition Audio [A3]
Network: RealTek Semiconductor RTL8102E/8103E Fast Ethernet NIC
Network: Realtek RTL8187B Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter

Looks like I have problem with wireless driver.
Live USB debug boot screen before froze:
image.png

I can press ctrl-c here and get console
Have you tried 14.3 with gapps ? It has one of the most recent kernels and wider device support than earlier ones.
Besides this, rtl8187B is connected by way of USB (a "chip to chip" USB datalink if it's on the motherboard), try to give a look into USB configuration options in bios/uefi settings to check if everything is allright there.
As an alternative disable the wifi interface, install Bliss OS on an internal drive, then enable wifi back again and check if there are differences compared to live usb boot.
 
  • Like
Reactions: Michael62

indonesyann

New member
Sep 16, 2020
1
1
For old chinese tablets like chuwi hi8, teclast x98 or alldocube iwork8, iwork10 etc, I recommend to install android pie blissos 11.14 :
- install gearlock recovery environment 7.3.3
- install the latest kernel pledge 5.10.58 by AXON at supreme-gamers.com or github.

Even my crappy cameras are working, only screen rotation sensor isn't working, wifi is stable, bluetooth is stable, battery management is better than stock.

Use mitigation=off HWL=intel GRALLOC=intel according to your hardware in grub EFI bootloader params.

BLISSOS_2021-11-27_11-45-09.png
 
Last edited:
  • Like
Reactions: cjeu100
May 1, 2021
25
0
so Bliss OS 14 are (Android 11) beta Builds, my question is when will it get to releasing android 12 based builds for Pc desktops and laptops? just wondering if Bliss OS or Android Generic is working on releasing iso images of android 12 for pc's.

or android x86 project if they are working on any android 12 based builds for pc's even if its based on their linux builds were you have to built the image yourself from scratch like linux can with its ubuntu commands. I have yet to see any android 12 based images,

my current samsung galaxy A tablet 10.1 (2016) has some beta AOSP android 12 builds already on XDR page for it, in any case I got android 11 on my tablet and waiting for android 12 roms to be a bit more stable otherwise it seems to be an improvement over android 11.


but was wondering about Bliss OS if they are also working with android 12 yet? with gapps or not with gapps when the iso are released for android 12, I do prefer gapp with images since they include google play store and google play's ebooks app stuff like that in it.
 
Last edited:

MCH_LNZ

Member
Nov 13, 2021
5
6
but was wondering about Bliss OS if they are also working with android 12 yet? with gapps or not with gapps when the iso are released for android 12, I do prefer gapp with images since they include google play store and google play's ebooks app stuff like that in it.
I don't know, but on Bliss OS sorceforge download pages they uploaded two alphas of waydroid for x86-64 (a barebone Ubuntu that runs an android subsystem).
That should greatly simplify development of new releases (at least for x86-64, maybe for ARM, too).
 
  • Like
Reactions: GOOGLE_USER
May 1, 2021
25
0
I don't know, but on Bliss OS sorceforge download pages they uploaded two alphas of waydroid for x86-64 (a barebone Ubuntu that runs an android subsystem).
That should greatly simplify development of new releases (at least for x86-64, maybe for ARM, too).
can you point me to that download page for that, an ubuntu can it run google play store and install stuff like google play books on ubuntu, I plan on using the newest version of ubuntu on my desktop, was planing on playing with any android that can run on it, was going to research that soon, I would use ubuntu for access to my google play ebooks to read on linux without using the webbrowser to access them, but sometimes, I like to use my tablet for also listening to ebooks, I am not sure if ubuntu has a good text to speech engine or not for listening to ebooks, it matter to me if they sound like humans or robots reading the ebooks back to me, once and awhile I do like to listen to ebooks besides just read them. again I am not sure at this time how ubuntu linux text to speech engine, that would impact the quality of any text to speech options, I know of calibre and bookworm software for ubuntu already, just not sure about how well you can use android on linux yet,

also I found a way to use some of my epic games launcher titles on linux with lutris software, but I have not tested that software out yet, one of the reasons I still have to dualboot to windows, also linux and windows don't always done well with the system time, after dualbooting if I recall its messed up the built in time before between the OS systems if I recall theirs a problem with that. the website for the epic games launcher is https://lutris.net/ and I have yet to try it on ubuntu I was going to try for my games just have not, as its not offically supported from the epic games launcher website I think its like a linux wrapper software that runs some of the epic games stuff and allow access to installing the games with wine or something like that again I have yet to try it so I am just guessing how it works. also have have some cross platform xbox one games and can be played on windows with microsoft store, those games I would still have to boot to windows 11 or windows 10 to use them, so I still can't fully drop windows from my desktop computer yet for that reason only I have to dualboot them if I want to play those games on something other than my xbox one x system.
 
Last edited:

cjeu100

Senior Member
Jan 26, 2020
214
107
  • Like
Reactions: MCH_LNZ

ijinesh

Member
Nov 9, 2008
30
0
Hi,
I am new to this. Can someone pls suggest the kernel and build I should use for dual booting with Surface Pro 7?
Has anyone been successful in getting Bliss OS work with Surface Pro 7?
Thanks in advance.
 

gatarax

Senior Member
Sep 27, 2018
70
11
Hello, i am novice for this android emulator. I have a desktop PC with Windows 10 Pro, I7 4790 processor and GTX 1060 .
I'm only looking for an emulator without dual-boot. Can we install Bliss os 14 without dual-boot please?
 

electrikjesus

Recognized Contributor
Apr 10, 2008
2,951
5,012
Grand Rapids, MI
I don't know, but on Bliss OS sorceforge download pages they uploaded two alphas of waydroid for x86-64 (a barebone Ubuntu that runs an android subsystem).
That should greatly simplify development of new releases (at least for x86-64, maybe for ARM, too).
Yeah, those are a couple experiments so far at a lightweight Ubuntu base, with Waydroid able to run as the default session.
 

[email protected]

New member
Dec 13, 2010
3
1
I have BlissOS x64 14.3 running on Dell WYSE 5070 and WYSE 5470AIO devices surprising well, with caveats. It triple boots win11/ubuntu/android through grub.

I currently have it default to tablet style UI.

My main problem i am trying to solve right now is that when booted it automatically boots into my Admin account and i cant even figure out how to set a password to this Admin account.

Firstly i would like to have a password set in order to login to this admin account and ultimately i would like it to boot directly into a lock screen that allows me to choose from the 4 user accounts i have setup in the multiuser settings and require a password to successfully login to any of those desktops.

Has anyone figured out how to accomplish this so that it works in a logical manner?

Has anyone figured out how to replace the brightness slider in the top menu with a volume slider? why is it so difficult to change master volume?
 

kamazok

Member
Aug 22, 2015
12
6
The first impressions of Bliss OS 15 Alpha on Android12, I like. The speed of the system itself has noticeably increased. Everything works so fast that you think, "Did my N3450 (6W) change to some new 12th generation i7?" Waiting for the final release, thank you.
 

IamTheBRAVE

Senior Member
Successfully installed BlissOs 15 on my old hp machine. But don't have root or gearlock recovery. Magisk asks to patch img.
Any idea how to get it working?
So far it looks good. All apps start in window mode which is a pain. And top and bottom of app bar mixes with status and nav bar. If you press a link in the bottom center it activates home button (pic 1).
App permission and default app menus in settings are empty. (pic2)
Will update if i get these to work somehoe.
Thanks @electrikjesus for your continuous support 👍
 

Attachments

  • PXL_20211217_110338777.jpg
    PXL_20211217_110338777.jpg
    1.6 MB · Views: 23
  • PXL_20211217_110815664.jpg
    PXL_20211217_110815664.jpg
    980.7 KB · Views: 23

Top Liked Posts

  • There are no posts matching your filters.
  • 55
    pOad4eK.png

    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: https://github.com/BlissRoms-x86/manifest/tree/q and the new patching system and build script are all included in https://github.com/BlissRoms-x86/vendor_x86/tree/q
    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.

    !!UPDATE!! 07.01.2020
    These builds are now made with Android-Generic project

    Yep1l4L.png

    Made with Android-Generic v1.1 - Android for PCs & GSI devices

    AG For ROM developers
    Android-Generic means there is finally something out there that helps to bring all the PC commits/setup/etc to your current ROM's build environment, working towards making the process easier for everyone involved moving forward. We also added a few smart features to the vendor toolkit as well, like commit resolution resource sharing, easy methods to add your vendor, easy methods to create manifest backups, and the scripts do most of the work for you already, with the exception of fixing some patch conflicts (the toolkit is smart enough to find potential fixes on it's own based on all the devs that contribute their patch resolutions back to the main repo). We have also added the option for Customizations to be chosen/placed on top of your ROM for added customization/branding options. We're trying to change the game here and allow many more ideas for PC to arise than what Team Bliss would have been able to do on their own. All the info needed to get started can be found in the project README.md, including links to the development chats for each side of the project : https://github.com/android-generic/vendor_ag

    AG For users of Bliss OS, Android-x86, etc.
    This means there is going to soon be a lot more options out there to choose from for running Android on your PC. And every new ROM added to the main repo means more and more ROMs will have an easier time porting their work to PCs as well.

    Now, on to more info about Bliss

    A7JONTD.png



    Bliss Source
    https://github.com/BlissRoms

    BlissRoms Devices Source
    https://github.com/BlissRoms-Devices

    Bliss' Android-PC Project
    https://github.com/Android-PC

    Bliss OS Source
    https://github.com/BlissRoms-x86

    Bliss OS Kernel Source
    https://github.com/BlissRoms-x86/kernel_common



    M8leihh.png


    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:
    Bliss-OS-v11.10--OFFICIAL-20190901-1611_x86_64_k-k4.19.50-ax86-ga_m-18.3.5-pie-x86-llvm80_ld-2.4.99-ma-p_dg-pie-x86_dh-pie-x86-rt-vulkan.iso
    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: "_fwdev-kernel.org"
    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. (https://github.com/maurossi/linux)
    -ga/gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (https://github.com/GalliumOS/linux)
    -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 https://github.com/jwrdegoede/linux-sunxi

    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 https://blissos.org and the Bliss OS 12 alpha testers section is just below the Downloads section. When that section is in view, please type the secret code and the download button will show.

    Have fun reading, and hope to see some bug reports soon ;)




    Cz6L1rZ.png



    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.

    The Instructions

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

    Thanks, and keep scrolling for FAQ & Updates



    aWICthQ.png



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

    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.

    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:
    Code:
    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.





    myCEQmI.png


    @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:
    yMdcL5e.png


    PayPal Link

    WE ARE A U.S. FEDERAL NON-PROFIT ORGANIZATION (501c3)

    2rw5ves.png


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


    https://smile.amazon.com/ch/82-3580195https://smile.amazon.com/ch/82-3580195


    Notice


    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.

    [ul]
    [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]
    [/ul]

    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.



    wwdX3pH.png


    Websites
    https://blissroms.com
    https://blissos.org


    Official Platform Links

    https://www.facebook.com/BlissFamilyOfROMshttps://www.facebook.com/BlissFamilyOfROMs
    https://twitter.com/Bliss_ROMshttps://twitter.com/Bliss_ROMs
    https://www.instagram.com/blissroms
    https://t.me/blissx86https://t.me/blissx86



    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)

    Contributors
    electrikjesus, jackeagle
    Source Code: https://github.com/BlissRoms-x86

    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-07-02
    15
    FAQ & Questions:

    For all FAQ's, please check the Wiki or our Telegram Chat


    Recent Update Posts:

    Updates, Round 1 - 2019.11.19
    https://forum.xda-developers.com/showpost.php?p=80950983&postcount=15

    Second round of updates - 2019.12.16
    https://forum.xda-developers.com/showpost.php?p=81122057&postcount=80

    Bliss OS 12.2 Alpha Updates - 2019.12.28
    https://forum.xda-developers.com/showpost.php?p=81329287&postcount=160

    Bliss OS - Yantra - 12.2 Beta Release - 2020.02.05
    https://forum.xda-developers.com/showpost.php?p=81688893&postcount=229

    Bliss OS "Yantra" 12.3 Beta Release - 2020-02-23
    https://forum.xda-developers.com/showpost.php?p=81845175&postcount=296

    Bliss OS "Yantra" 12.4 Release Candidate 1 - 2020-02-27
    https://forum.xda-developers.com/showpost.php?p=81880187&postcount=309

    Bliss OS "Yantra" 12.5 Release Client 2.1 - 2020-03-26
    https://forum.xda-developers.com/showpost.php?p=82110111&postcount=389

    Bliss OS "Merkaba" 12.6 Release Client 2.2 - 2020-05-05
    https://forum.xda-developers.com/showpost.php?p=82490635&postcount=451

    Bliss OS "Merkaba" 12.6 Release Client 2.2 - AMD - 2020-04-23 & Bliss OS Lite Alpha Release - Vulkan - 2020-05-31
    https://forum.xda-developers.com/showpost.php?p=82731139&postcount=499

    Bliss OS "Sri" 12.8 - Introducing Android-Generic v1.1 Vulkan & Generic-Intel Builds - 2020-06-30
    https://forum.xda-developers.com/showpost.php?p=82968733&postcount=543

    AG-10 Bliss OS 12.12 - Generic Build - 2020-10-07
    https://forum.xda-developers.com/showpost.php?p=83661857&postcount=674

    AG-11 & Bliss OS 14.3 - Generic Build - 2021/06/17

    Bliss OS 14.3 - Generic 5.4 Builds (32bit FOSS / 64bit Gapps) - 2021/06/18


    Bliss OS 14.3 - Generic x86_64 - kernel-5.10.42 - 06.26.21

    Bliss OS 14.3 FOSS - x86/x86_64 - kernel-5.10.50 - 07.24.21
    10
    Bliss OS 12.2 Alpha Updates - 2019-12-28
    !! Please remember to not quote these update posts, or any of the OP's !!

    It's a little late for Christmas, but early for new years, so I have another update for all of you to test. Tons of updates that won't show up in the changelog, like a bunch for firmware and kernel drivers. As well as a bunch of silead touchscreen firmwares added to the mix. Thanks to a few upstream updates from Android-x86 project, we finally got Superuser added properly too (must be enabled from Developer Options in Settings), so that is also included, as well as a non-functioning switch in Settings for enabling Houdini (yeah, that's still broken). S3 sleep modes have also been tweaked a little to hopefully work better, just remember to use the Sleep option from the power menu now and not a third party app.

    Taskbar might need to be updated from Play Store for it to properly hide the nav bar, but things there are working great!!

    PLEASE NOTE I recommend everyone testing to also use this in Vulkan mode, as I am considering making it the default. This 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"

    Builds being uploaded:
    • Bliss-OS-v12.2-x86_64-OFFICIAL-201912272156_k-k4.19.80-ax86-ga-q_m-q-x86_ld-q-x86_dg-_dh-q-x86.iso

    General Updates List:
    • More fixes for sleep when using the power menu. Access it using Ctrl+Alt+Del or the three dot menu from Taskbar.
    • More updates to stagefright-plugins
    • Added more kernel modules for various wireless hardware
    • Some fixes for sound and volume on many devices
    • Some upstream updates from Android-x86 project's q-x86 branch
    • and much much more, check the changelog.

    Known new issues:
    • AOSP Gesture navbar might crash still
    • Sleep states aren't working right on a few machines. Some can cause SystemUI to restart
    • Power buttons still don't work on a most machines.
    • Volume buttons might not affect media volume, use 3rd party EQ or volume control.

    Download:

    You still have to go through our website to download. The default download link for the alphas has been updated.

    Changelog:

    Code:
    ====================
         12-27-2019
    ====================
    
    
       * bootable/newinstaller/
    20d3e2e Merge remote-tracking branch 'ax86/q-x86' into HEAD
    63c8e6b init: do not modify /default.prop
    
       * device/generic/common/
    4012579 Add optional native bridge and widevine
    0f4ea69 Merge remote-tracking branch 'ax86/q-x86' into q-x86-12.1
    6cf5d7f init: allow to disable SetupWizard
    f96a177 init: allow to set ro.sf.lcd_density by DPI in cmdline
    
       * vendor/blissos/
    580ea7cc Update to 12.2
    32d32840 Script updates for houdini and widevine inclusion
    701585df Remove NexusLauncher
    
    ====================
         12-26-2019
    ====================
    
    
       * device/generic/common/
    999e952 Update to track our own houdini
    dc379ac Insist that a few product inherits are found
    135c675 Add a couple more Superuser package variants
    
       * external/koush/Superuser/
    27b7d22 Make the icons more visible
    c61bc31 Fix pin dialog crashing
    
       * packages/apps/Settings/
    e565b279b0 Add Android-x86 dashboard
    ea248ebd65 Settings: Add Superuser entry
    
    ====================
         12-25-2019
    ====================
    
    
       * device/generic/common/
    574cda7 Reset superuser configs to ax86's q branch
    1eec22c Add another superuser package variant
    815bd7c Reset nativebridge to android-x86 sources
    
       * packages/apps/Settings/
    37f98643f4 Settings: Add developer setting for root access
    10fbbd75cb Add information about OpenGL driver version
    d6d04c55cc Add Manufacturer to device info
    
    ====================
         12-24-2019
    ====================
    
    
       * device/generic/common/
    cba4d81 Update Superuser calls
    a29e99a Staging houdin changes
    
    ====================
         12-23-2019
    ====================
    
    
       * external/koush/Superuser/
    2c2f827 Replace android.support.v4.app by AndroidX
    
       * external/koush/Widgets/
    642ab34 Fix crashing
    a3c5c1e Replace android.support.v4.app by AndroidX
    
    ====================
         12-22-2019
    ====================
    
    
    ====================
         12-21-2019
    ====================
    
    
       * external/stagefright-plugins/
    d32297d Port to q-x86
    
    ====================
         12-20-2019
    ====================
    
    
    ====================
         12-19-2019
    ====================
    
    
       * frameworks/base/
    5ad841cc802b Enabling suspend on IVI after clicking sleep from the power button menu.
    
       * system/core/
    ff43c53f5e libcutils: add probe_module
    
    ====================
         12-18-2019
    ====================
    
    
       * device/generic/common/
    73c011b Akoya P2213T: Fix orientation of auto rotation
    
       * frameworks/base/
    c29a214a9af1 Align the pageBlockOrder to the kerne 4.19 kernel
    
       * vendor/blissos/
    9378ffc0 Updates for q-12.1
    
    ====================
         12-17-2019
    ====================
    
    
       * vendor/blissos/
    182435d2 Use vendor/GMS for USE_GMS
    
    ====================
         12-16-2019
    ====================
    
    
    ====================
         12-15-2019
    ====================
    
    
    ====================
         12-14-2019
    ====================
    
    
    ====================
         12-13-2019
    ====================
    
    
       * bootable/newinstaller/
    5e88beb Merge remote-tracking branch 'ax86/pie-x86' into HEAD
    c8ead07 Update filename for new Bliss OS version name
    
       * external/ax86-nb-qemu/
    83784e3 Updates for q-x86
    
       * external/ax86-nb-qemu-guest/
    55b45ba Update patch for q
    eaa55f7 Updates for q-x86
    
       * vendor/google/chromeos-x86/
    abc8257 extract-files.sh: Update to 12499.66.0_atlas

    Thanks, and #stayblissful ;)
    9
    Bliss OS "Yantra" 12.2 Beta Release - 2020-02-05
    !! Please remember to not quote these update posts, or any of the OP's !!

    OK peeps, what we have here is a little departure from our last update. This update marks the start of Bliss OS - Yantra. What this will be is a separate version of Bliss OS with all the bells and whistles added. Where our last releases were mostly AOSP with a few Pixel related additions, the Yantra releases will include commits from many other Android ROM teams, like LOS, Paranoid Android, Omni, AICP, etc.
    These builds also remove some of the compatibility problems with non-x86 or universal apps we were seeing with the alphas. So for the time being, until ChromeOS updates to use Android 10 blobs, or there is an open-source solution for running Arm apps, you won't be able to run those types of apps. If you want your favorite game to work as intended on Bliss OS, then please complain to the game developer and ask them to release universal apks for their game.

    For troubleshooting, we also now have a way of specifying what hardware composer and gralloc source we want to use from Grub command line:
    HWC=xxx: Define DRM_HWComposer - options include drm, drm_minigbm, and intel.
    GRALLOC=xxx: Define DRM_Gralloc - options include gbm, minigbm, and intel.

    Difference between the builds:
    First one is using Android-x86's kernel-4.9 branch (based off kernel-4.19.95) without any changes. On this branch, some of my machines were having issues with the keyboard and touchpad, so for those devices that have troubles, we also have the second build, using the kernel branch, k4.19.80-ga-q, and this includes the removal of HID_RMI with the connections now defaulting to use HID_MULTITOUCH instead.

    UPDATE 02.07.20 - Two updated builds added to help get rid of ueventd issues.
    These builds have an updated kernel including all the commits to support chromebooks. The second build has the HID_RMI stuff added to the kernel so that some troublesome touchpads and synaptics touchscreens now work. These two builds also have some of the ARM compatibility libraries added back, so users can hopefully install a couple of the apps that were working fine before.

    PLEASE NOTE I recommend everyone testing to also use this in Vulkan mode, as I am considering making it the default. This 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"

    Builds being uploaded:
    • Bliss-OS-Yantra-v12.2-android_x86_64-OFFICIAL-202002051133_k-k4.19.80-ax86-ga-q_m-19.3.0-ax86-q_ld-2.4.100-ax86-ma_dg-_dh-q10.0-x86_mg-_gms_cros-wv.iso
    • Bliss-OS-Yantra-v12.2-android_x86_64-OFFICIAL-202002051304_k-kernel-4.19_m-19.3.0-ax86-q_ld-2.4.100-ax86-ma_dg-_dh-q10.0-x86_mg-_gms_cros-wv.iso
      Bliss-OS-Yantra-v12.2-android_x86_64-OFFICIAL-202002062215_k-k4.19.95-ax86-ga-rmi_m-19.3.0-ax86-q_ld-2.4.100-ax86-ma_dg-_dh-q10.0-x86_mg-_gms_cros-hd_cros-wv.iso
      Bliss-OS-Yantra-v12.2-android_x86_64-OFFICIAL-202002071251_k-k4.19.95-ax86-ga_m-19.3.0-ax86-q_ld-2.4.100-ax86-ma_dg-_dh-q10.0-x86_mg-_gms_cros-hd_cros-wv.iso

    General Updates List:
    • Added more fixes for sleep. Sleep from power menu is currently missing. Access it using Ctrl+Alt+Del or the three dot menu from Taskbar.
    • Added sleep options like double-tap to sleep from statusbar or lockscreen
    • Added Blissify app for customizations
    • Generic Kernel updates for the "kernel-4.19" build
    • Fixes for sound and volume on many devices
    • Some upstream updates from Android-x86 project's q-x86 branch
    • and much much more, check the changelogs.

    Known new issues:
    • AOSP Gesture navbar might crash still - Future builds will include XDA's Navigation Gestures app in order to provide a solution for Gestures. https://play.google.com/store/apps/details?id=com.xda.nobar
    • Sleep states aren't working right on a few machines. Some can cause SystemUI to restart
    • Power buttons still don't work on a most machines. You can now set Volume buttons to wake the device from Settings > Blissify. Sometimes Power button may work to wake the device.
    • Touch/Mouse interaction might stop sometimes upon screen on or boot. To fix this, set Swipe as your lock method in Settings
    • Sensor input is still not working, so rotation will have to be set manually
    • Some machines still have volume/sound issues, use 3rd party EQ or volume control.

    Download:

    You still have to go through our website to download. The download section for Bliss OS 12 Betas has been updated.

    Changelog:

    Code:
    Changelog too big to include. See full changelogs here:
    All changelogs - [url]https://sourceforge.net/projects/blissos-dev/files/Beta[/url]

    Thanks, and #stayblissful ;)
    9
    Bliss OS "Yantra" 12.3 Beta Release - 2020-02-23
    !! Please remember to not quote these update posts, or any of the OP's !!

    The Bliss devs have been working hard to bring you all some awesome updates, and I have also had some time to get quite a few things done for this project too, so we're bringing you another jam-packed update of Bliss OS 12.x. Some of the biggest highlights in this update are working mic, device admin, widevine video codecs, and we added a few titlebar buttons too (these will be submitted upstream to Android-x86 Project eventually). Make sure that you read the changelogs for all the juicy details, and hit the Thanks button if things are working better this round.

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

    Updates include:
    • New themes and theme updates
    • New fonts and font updates
    • Permissions updates for some Google apps
    • Look & Feel updates to Settings
    • Updates and fixes to dialer
    • Added Active Edge support for some devices
    • Added many new options to Blissify
    • Updates for a few LineageParts related features
    Added titlebar buttons for minimize and pip (picture in picture) mode
    • Much much more, see the changelogs

    Bugs fixed:
    • Microphone bugs are fixed
    • Sound bugs on many devices are fixed
    • Widevine is now working
    • native navbars and guesture navigation is now fixed
    • Flashlight notification fixes
    • Camera fixes (use Open-Camera)
    • Various fixes to SystemUI
    • Fixes for a few LineageParts related issues
    • Fixes in PerformanceManager

    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.

    Builds being uploaded:
    • Bliss-OS-Yantra-v12.3-android_x86_64-OFFICIAL-202002231104_k-k4.19.95-ax86-ga-rmi_m-19.3.3-ax86-q_ld-2.4.100-ax86-ma_dg-_dh-q10.0-x86_mg-_gms_cros-hd_cros-wv.iso
    • Will also be posting another build without the custom RMI fixes.

    Known new issues:
    • Sleep states aren't working right on a few machines. Some can cause SystemUI to restart
    • Power buttons still don't work on a most machines. You can now set Volume buttons to wake the device from Settings > Blissify. Sometimes Power button may work to wake the device.
    • Touch/Mouse interaction might stop sometimes upon screen on or boot. To fix this, set Swipe as your lock method in Settings
    • Sensor input is still not working, so rotation will have to be set manually
    • Some machines still have volume/sound issues, use 3rd party EQ or volume control.

    Download:

    You still have to go through our website to download. The download section for Bliss OS 12 Betas has been updated.

    Changelog:

    Code:
    Changelog too big to include. I have uploaded all the changelogs from my test builds though so you all can see the changes. See full changelogs list here:
    All changelogs - [url]https://sourceforge.net/projects/blissos-dev/files/Beta[/url]

    Thanks, and #stayblissful ;)