Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
- Thread starter electrikjesus
- Start date
hey... stumbled across BlissOS just a few minutes ago and find the project absolutely amazing... did anyone have success with running BlissOS on a Sony Vaio Flip 15 laptop? I'm mainly interested in Wifi and the touch screen - the rest of the features are less important... thx....
As a user of Bliss OS, I would like to request the addition of support for Ericsson F3507g mobile broadband hardware. This would allow me to use my Ericsson F3507g mobile broadband device with Bliss OS, giving me the ability to connect to the internet while on the go.
The Ericsson F3507g is a widely used mobile broadband device that is compatible with many different operating systems. However, it is currently not supported by Bliss OS. Adding support for this hardware would make Bliss OS more accessible and useful to a larger number of users.
I understand that adding support for new hardware can be a time-consuming and resource-intensive task. However, I believe that the benefits of supporting the Ericsson F3507g mobile broadband device far outweigh the costs. I strongly urge the Bliss OS team to consider adding support for this hardware in a future release.
Thank you for your consideration.
The Ericsson F3507g is a widely used mobile broadband device that is compatible with many different operating systems. However, it is currently not supported by Bliss OS. Adding support for this hardware would make Bliss OS more accessible and useful to a larger number of users.
I understand that adding support for new hardware can be a time-consuming and resource-intensive task. However, I believe that the benefits of supporting the Ericsson F3507g mobile broadband device far outweigh the costs. I strongly urge the Bliss OS team to consider adding support for this hardware in a future release.
Thank you for your consideration.
i have installed the build couple of questions,is this resolution normal the startdock taking all the screen also how do you go back ? no button appears is this a bug? EDIT:i just find out most of the problems are caused by the stardock if you use quickstep launcher or computer launcher everything seems to be working fine.
Hello, got a 5-6 year old chinese tablet (onda obook 20 plus, 2 in 1, windows and android) tested your rom, works great, but I need to solve three problems:
- sound (not working)
- turn off screen (if I press the power button, the screen turns black, not off)
- accelerometer calibration (inverted in landscape, good in portrait mode)...
Still can't believe it that most of the hardware is working...
How can I integrate sound drivers and solve accelerometer problem (tried all settings from orientation and no resolution).
- sound (not working)
- turn off screen (if I press the power button, the screen turns black, not off)
- accelerometer calibration (inverted in landscape, good in portrait mode)...
Still can't believe it that most of the hardware is working...
How can I integrate sound drivers and solve accelerometer problem (tried all settings from orientation and no resolution).
I used bliss os Android 9 on surface go 1.
i want use sim card
echo 16383 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan/cdc_ncm/rx_max
echo 16383 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan0/cdc_ncm/tx_max
echo 16384 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan0/cdc_ncm/rx_max
echo 16384 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan0/cdc_ncm/tx_max
ifconfig wwan0 up
But wwan0 only have inet6 local ipv6 address
help
how to config apn or display carrier GUI
i want use sim card
echo 16383 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan/cdc_ncm/rx_max
echo 16383 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan0/cdc_ncm/tx_max
echo 16384 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan0/cdc_ncm/rx_max
echo 16384 | tee /sys/bus/usb/devices/2-3/2-3:1.0/net/wwan0/cdc_ncm/tx_max
ifconfig wwan0 up
But wwan0 only have inet6 local ipv6 address
help
how to config apn or display carrier GUI
Okay, so with my old laptop, I struggled to get pretty much any rom working 100% that was also compatible with many games (Samsung NP365E5C). And that's with Prime OS, plain old Androidx86, and Bliss Os.
I started looking around with buying a cheap newer laptop and found this Asus BR1100CKA-YS02 11.6" for $30 as an open box purchase from my local Microcenter. It was so cheap as an open box that it was worth buying period. I spent like $50 total and walked out with the laptop (brand new condition with charger), two 16GB flash drives, and a wireless mouse.
I spent freaking forever trying to get it to install any version of Androidx86 and I had the same issue every single time: when selecting "install" from the boot options or "auto install to specified hard disk", it always went to a black screen and did nothing after. Secure boot off. No VMD options in BIOS. Tried from older to newer releases of each flavor of Androidx86 and the same issue. Eventually I discovered Advanced Android Installer. I tried that with many different versions as well. Latest builds 14.10 and 15.8.4 failed after copying system.sfs but older builds would finish. They would boot but with errors and then I'd get a distorted display or it would just freeze at the boot logo. Tried setting different debugging options but no difference.
Eventually I found someone on advanced Android installer forums who said they had success by formatting the partition with the advanced installer disk tool, mounting the disk, extracting the files from the iso of your choice to the root of the ext4 partition, creating a new folder in the root of the ext4 partition called "data", adding a grub bootloader option for Android and clicking the kernal button and pointing it to the kernal file in the root of the ext4 partition, and then reboot and select the Android OS option from the grub bootloader. I did exactly that and I finally got something to work. I went straight to trying 15.8.4 and it's working beautifully.
Here's the link to the original post I found that helped me:
aopc.dev
Bluetooth, wifi, PS4 gamepad, wireless mouse, Play store, keyboard shortcuts for screen brightness and volume, etc. I need to play around more with understanding the differences/configuring of taskbar/quick home/smart dock because it's kind of throwing me off. Seems redundant in some ways but I'm sure I'm just not setting it up correctly. I don't want to tinker to much more because I have a larger SSD on the way now so I'm waiting to upgrade first and reinstall everything.
I can tell you that Google Play works and I've played Dead Trigger 2 flawlessly with a PS4 controller, PubG but I didn't tinker much because I found it doesn't support a gamepad and I didn't feel like mapping anything, and I've also used Dolphin Emulator to play Super Mario Sunshine with the mapped PS4 controller and that worked absolutely beautifully.
Thank you devs for all your hard work and continued support.
Here's a video of me playing Super Mario Sunshine on Dolphin Emulator:
I started looking around with buying a cheap newer laptop and found this Asus BR1100CKA-YS02 11.6" for $30 as an open box purchase from my local Microcenter. It was so cheap as an open box that it was worth buying period. I spent like $50 total and walked out with the laptop (brand new condition with charger), two 16GB flash drives, and a wireless mouse.
I spent freaking forever trying to get it to install any version of Androidx86 and I had the same issue every single time: when selecting "install" from the boot options or "auto install to specified hard disk", it always went to a black screen and did nothing after. Secure boot off. No VMD options in BIOS. Tried from older to newer releases of each flavor of Androidx86 and the same issue. Eventually I discovered Advanced Android Installer. I tried that with many different versions as well. Latest builds 14.10 and 15.8.4 failed after copying system.sfs but older builds would finish. They would boot but with errors and then I'd get a distorted display or it would just freeze at the boot logo. Tried setting different debugging options but no difference.
Eventually I found someone on advanced Android installer forums who said they had success by formatting the partition with the advanced installer disk tool, mounting the disk, extracting the files from the iso of your choice to the root of the ext4 partition, creating a new folder in the root of the ext4 partition called "data", adding a grub bootloader option for Android and clicking the kernal button and pointing it to the kernal file in the root of the ext4 partition, and then reboot and select the Android OS option from the grub bootloader. I did exactly that and I finally got something to work. I went straight to trying 15.8.4 and it's working beautifully.
Here's the link to the original post I found that helped me:
Distro - Bliss OS 14/15
I also have the same issue as "madlonewolf" (11th gen i7), disabling Secure Boot will not fix loading into installation, instead I have to extract all files from the Blissos iso onto an ext4 partition and use grub2win bootloader in order to get a boot. After testing many android x86 iso's on...
aopc.dev
Bluetooth, wifi, PS4 gamepad, wireless mouse, Play store, keyboard shortcuts for screen brightness and volume, etc. I need to play around more with understanding the differences/configuring of taskbar/quick home/smart dock because it's kind of throwing me off. Seems redundant in some ways but I'm sure I'm just not setting it up correctly. I don't want to tinker to much more because I have a larger SSD on the way now so I'm waiting to upgrade first and reinstall everything.
I can tell you that Google Play works and I've played Dead Trigger 2 flawlessly with a PS4 controller, PubG but I didn't tinker much because I found it doesn't support a gamepad and I didn't feel like mapping anything, and I've also used Dolphin Emulator to play Super Mario Sunshine with the mapped PS4 controller and that worked absolutely beautifully.
Thank you devs for all your hard work and continued support.
Here's a video of me playing Super Mario Sunshine on Dolphin Emulator:
Attachments
Last edited:
Have HP pro 608 tablet trying to get sound to work.
ls -al /proc/asound
the above command returns card0 found as bytchtcx2072cx
looking in folder /system/etc/alsa/ there is a file called chtcx2072cx.state but there is no file called bytchtcx2072cx.state. I am assuming if i can find a copy the correct file into that system folder then sound might start working.
Any help is appreciated.
ls -al /proc/asound
the above command returns card0 found as bytchtcx2072cx
looking in folder /system/etc/alsa/ there is a file called chtcx2072cx.state but there is no file called bytchtcx2072cx.state. I am assuming if i can find a copy the correct file into that system folder then sound might start working.
Any help is appreciated.
Hi,
Looong thread so haven't read through all of it (sorry).
Used Bliss a couple of years ago on my Surface pro 4 but the battery died so now I'm looking into trying to install Bliss on my surface pro 7 plus. Is the surface pro 7 plus supported? Does it exist working multi touch drivers? Any step by step guide available? Any support with links etc highly appreciated. yes, tried to search without any luck
. Only found old post stating that it doesn't work... Latest surface Linux kernel seem to have support but honestly no clue on how to get this up and running with Bliss.
Thanks.
Looong thread so haven't read through all of it (sorry).
Used Bliss a couple of years ago on my Surface pro 4 but the battery died so now I'm looking into trying to install Bliss on my surface pro 7 plus. Is the surface pro 7 plus supported? Does it exist working multi touch drivers? Any step by step guide available? Any support with links etc highly appreciated. yes, tried to search without any luck
. Only found old post stating that it doesn't work... Latest surface Linux kernel seem to have support but honestly no clue on how to get this up and running with Bliss.Thanks.
Last edited:
Go to our Telegram or Discord, we got builds for surfaceHi,
Looong thread so haven't read through all of it (sorry).
Used Bliss a couple of years ago on my Surface pro 4 but the battery died so now I'm looking into trying to install Bliss on my surface pro 7 plus. Is the surface pro 7 plus supported? Does it exist working multi touch drivers? Any step by step guide available? Any support with links etc highly appreciated. yes, tried to search without any luck
Thanks.
i have a problem . i try install version 15 or 14 on virtual box
i did all this https://docs.blissos.org/installation/install-in-a-virtual-machine/install-in-virtualbox/
and every time have this error
any help . what i did wrong ? thank you
i did all this https://docs.blissos.org/installation/install-in-a-virtual-machine/install-in-virtualbox/
and every time have this error
any help . what i did wrong ? thank you
Last edited:
Hello I have the same problem as sergor,
is it possible that BlissOS 15 cannot be installed with VirtualBox 7?
No matter how I do it I always get the error message.
is it possible that BlissOS 15 cannot be installed with VirtualBox 7?
No matter how I do it I always get the error message.
I have installed Bliss OS Bliss-v15.8.4-x86_64-OFFICIAL-foss-20230201.iso on my PC and would like to build a driver for it.
I could not find the kernel sources for this release. Can some one provide a link to the kernel source ?
I could not find the kernel sources for this release. Can some one provide a link to the kernel source ?
Kernel source is defined in manifest https://github.com/BlissRoms-x86/manifest/blob/arcadia-x86/android-x86/04-kernel.xml#L11
For kernel v5.15.x builds https://github.com/hmtheboy154/darkmatter-kernel/tree/umbral
For kernel v6.1.x builds https://github.com/hmtheboy154/darkmatter-kernel/tree/gloria
Kernel updates sometimes so building driver yourself every time might not be practical.
Do you know ?
How to install this version of bliss os (15.8.4) ?
Can you explain ?
I can't install
Installing time a message will show "it take to long to detect then reboot your pc and check your installation folder"
Device
Lenovo 80E5
RAM 8GB
MEMORY 1 TB
PROCESSOR I5 5th
I have a Ubuntu PC and my initial effort was to install on a USB drive and use it when I want to run Android. However the installation failed due to some grub failure. So I ended up doing a manual installation inside my Ubuntu installation. I just copied 3 files to a folder on my Ubuntu ext4 drive and added a custom.cfg to grub.
Which are the 3 files ?
I have the bliss os iso file
Can I copy files into windows ext4 drive ?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1You can unzip the iso to find the 3 files. Windows doesn't use an ext4 flle system. So I am not sure if this can be done with Windows. I have only done this with an existing Ubuntu installation.1
Good to know that you are up and running. Most probably this is a kernel issue.1
If I remember correctly about the Conexant mic, it is actually use mono instead of stereo. So what you should do is using alsa_mixer or alsa_amixer on terminal to mute one side of the mic (could be the right side) like this and then try to record. But you will have to do this in every boot
About the camera, idk. You can try again -
62
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
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
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
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
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
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.
@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 ARE A U.S. FEDERAL NON-PROFIT ORGANIZATION (501c3)
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.
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-0216FAQ & 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 (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you...
forum.xda-developers.com
Bliss OS 14.3 - Generic 5.4 Builds (32bit FOSS / 64bit Gapps) - 2021/06/18
Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you...
forum.xda-developers.com
Bliss OS 14.3 - Generic x86_64 - kernel-5.10.42 - 06.26.21
Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you...
forum.xda-developers.com
Bliss OS 14.3 FOSS - x86/x86_64 - kernel-5.10.50 - 07.24.21
Bliss OS (x86) for PC's - 12.x/14.x Development - Beta Builds
Team Bliss is pleased to present to you...
forum.xda-developers.com
10Bliss 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:
Thanks, and #stayblissful9Bliss 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:
Thanks, and #stayblissful9Bliss 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:
Thanks, and #stayblissful
