• 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

.:Addicted:.

Senior Member
Aug 22, 2014
388
88
Cuttack
addicted.tk
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

Recognized Contributor
Apr 10, 2008
2,946
5,004
Grand Rapids, MI
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
 
  • Like
Reactions: .:Addicted:.

.:Addicted:.

Senior Member
Aug 22, 2014
388
88
Cuttack
addicted.tk
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
 
Last edited:

vladone97

Member
Mar 21, 2015
47
5
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:.

Senior Member
Aug 22, 2014
388
88
Cuttack
addicted.tk
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
 
Last edited:

electrikjesus

Recognized Contributor
Apr 10, 2008
2,946
5,004
Grand Rapids, MI
@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:.

Senior Member
Aug 22, 2014
388
88
Cuttack
addicted.tk
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
 
Last edited:
Nov 4, 2017
15
1
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.
 
Feb 4, 2020
13
1
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
 
Last edited:

electrikjesus

Recognized Contributor
Apr 10, 2008
2,946
5,004
Grand Rapids, MI
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)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    The 14.3 (Android 11) version looks very fast and promising. But with too many bugs at the moment. Only Firefox and DuckDuckGo work when it comes to Web Browsers. Chrome and Opera crash on start-up. All the apps install in the "phone" mode. So the device feels like a very big phone. That's clearly visible with Google Calendar. It has a cool tablet layout on Bliss OS 11.4 (Android 9). Graphics performance is 40% lower compared to Android 9 (measured with 3DMark) but most of the games don't run anyways.
    I will come back to Bliss OS 11.4 and watch this promising Android 11 Development.
    Thank you Guys! Exciting stuff!
    1
    Havng the same problem. It started after installing the new kiwi browser update ( with chromium 93), all other browsers (brave, bloket, opera...) Started behaving the same. Could it be related to android webview?
    It worked fine for me in this specific iso <https://sourceforge.net/projects/bl...ernel-5.8-si-next-fs_r_egapps_libndk_wv_m.iso>
    Try disabling hardware acceleration, problem is when scaling, when video isnt scaled it works properly.
    1
    Click on the 3 dot menu and update google play services.
    Wasn't aware that Google Play can update Google apps without an ID, Google Play working fine now.

    Another question, is there a way to gain ROOT permission? I got an app need run with ROOT permission...
    1
    Try disabling keyboard from gearlock > system tweaks
    Thanks for all your help. I may switch back to android x86 or try out Bliss OS 11. I really like 14 as it addresses a lot of issues in my YogaBook 2, especially the sleep. 14 makes my tablet like a real android tablet. But it brings some new issues, like the translation is not completed, WeChat does run etc.

    I will definitely follow the thread and try out the new version if there is one.
    1
    nobody ever faced the problem mentioned before? still no luck...
    I resolved this problem successfully by going to Settings => Apps, finding the Google Play Services app and restoring it to the original version. And then going to Google Play Store and turning auto updates off.
    Had the same problem, Google Play Services crashing every 30 seconds. Restoring the default version of the app resolved this completely.

    Thank you!
  • 53
    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 ;)