{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
team bliss is pleased to present to you
bliss rom based on Android 9 Pie
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 ROMs 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.
Notice
- READ: 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.
- Please do not ask for ETA's;
- 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;
- We encourage users to contribute towards this project, and we're openly accepting applications for others to join Team Bliss
First, a little bit about this project...
Starting in Android Pie, Bliss OS will be taking a different approach to building Android for PC's. Taking inspiration from @phhusson 's Treble methods, and Intel's Project Celadon, we have reworked a good majority of the commits from Android-x86 Project and Bliss OS's Oreo release, and packaged it up so that it can work a bit more dynamically. The result was something we could integrate into a single source, along side normal device builds. This is much like our Treble builds that use PHH's Treble methods, and Intel's Project Celadon's EFI builds. Both of which are also buildable directly from the BlissRoms-x86 source: https://github.com/BlissRoms-x86/manifest
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. For now though, you can stay tuned to this thread for updates on all that.
ROM Porting Details:
Like we mentioned already, things this round will be done a bit differently using the patching system to build for x86 devices, making updating and maintaining far easier than before, and even lowers the bar for understanding how it all works. But things were still complicated enough for us to see room for improvement. So we have also packaged up all the x86 bits we add to Bliss OS, minus a few goodies and are making them available to the entire community to add to their ROM projects. You can find the basics on GitHub already, https://github.com/Android-PC and for those interested in adding x86 support to your own ROM, I was able to squash things down to a single commit in build/make in order to help get the ball rolling. This will also be the source we are helping out Android-x86 Project with, so don't be surprised if things change a bit to reflect that projects branding more.
https://github.com/Android-PC/platform_build/commit/eda2e16b0018c5554f98acaa708f8200a171f206
I'm always open to suggestions on how we can improve upon things too, so don't be afraid to speak up, just remember to be considerate upon doing so
We will be updating our website also over the next few weeks to feature a new downloads section, as well as further information about using our source for commercial projects.
AIO Thread
Bliss Source
https://github.com/BlissRoms
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
BlissRoms Kernel Source
https://github.com/BlissRoms-Kernels
BlissRoms Vendor Source
https://github.com/BlissRoms-Vendor
BlissRoms-x86
https://github.com/BlissRoms-x86
Bliss' Android-PC Project
https://github.com/Android-PC
Open Gapps Project
!!CONSIDER THESE AS DEVELOPMENT BUILDS FOR NOW!!
These are not to be considered stable in any way shape or form. Please continue at your own risk. Developers and experienced users suggested
This release is a work in progress, and will take community effort in order to iron out all the bugs.
There are no IPTS builds for the Surface devices yet, and there won't be until I am able to fix my SurfaceBook. Sorry :'(
Read the documentation first:
https://docs.blissos.org
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with available installation options before attempting to install the OS.
Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Download the ISO file
Use Rufus or similar to burn to USB drive
Disable Secure Boot, Bitlocker, and any other boot security
Boot into the USB drive.
Run Bliss OS in Live mode to test things out, if all is well, continue to next step
Boot into the USB drive, and choose Bliss OS Install
Pick your poison, but please do this with caution, making sure to fully understand what you are doing.
These are beta builds, so please take that into consideration when reporting issues. We want all the info possible
Packages Manager sometimes crashes the system. This will require you to wait, then open a terminal and use $ su && svc wifi disable , and when it comes back, $ su && svc wifi enable
Screenshots aren't working yet
Video playback does not work right as of yet
Sound issues on many machines still
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.
-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.
-You can also open trouble tickets on our website for bugs.
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!
If someone takes it upon themselves to donate to us, of course it will be appreciated, and all funds will be used to pay our server and upkeep fees.
If someone wants to donate, our PayPal link is below.
PayPal Link
Very Important Information
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 team
when 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.
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.
Thank you for using Bliss! And have as always: #StayBlissful
XDA:DevDB Information
Bliss OS - Pie for PCs (development Beta Preview), ROM for the ROM Central
Contributors
electrikjesus, ElfinJNoty
Source Code: https://github.com/BlissRoms
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: x86 Arch
Version Information
Status: Beta
Current Beta Version: 20181018
Beta Release Date: 2018-10-18
Created 2018-10-19
Last Updated 2019-07-23
The Instructions
We have moved the instructions to be a part of our docs site
For the main instructions to get going with Bliss OS, you can check out our Installation Guide
If you get into a bind with your install, you should see our Troubleshooting section
For the few addons and other info we have for Bliss OS installs, you can check out our Extras section
And if you're ready to start building and testing new things, you can check out the Bliss OS Build Guide.
Thanks, and keep scrolling for FAQ & Updates
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-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso
It can be broken into 3-4 parts.
Build ID: "Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457"
Kernel Branch: "_kernel-4.9"
Mesa Branch: "_m18.3.0-devel_w40_LLVM70"
Firmware Branch: "_dev-kernel.org"
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)
-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.
Q: OK, So I have a BlahBlah 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:
Kernel-4.9 These are considered the most "Stable" builds, they will work across most older and recent devices.
Kernel-4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
Kernel 4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
Kernel 4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
kernel 4.19+ Intended for newer devices. Even more touchscreen support and ACPI support
Kernel 4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
Kernel 5.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.
For all other FAQ's, please check the Wiki or our Telegram Chat
Recent Update Posts:
Updates, Round 1 - 2018.10.28
https://forum.xda-developers.com/showpost.php?p=77999419&postcount=55
Updates, Round 2 - 2018.11.07
https://forum.xda-developers.com/showpost.php?p=78092995&postcount=112
Forgotten Kernel-4.18 build - 2018.11.01
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=175
Christmas Build - 2018.12.25
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=238
Fist Release of 2019!! - 2019.01.16
https://forum.xda-developers.com/showpost.php?p=78691527&postcount=337
Second Release of 2019!! - 2019.01.21
https://forum.xda-developers.com/showpost.php?p=78730287&postcount=363
Updates to kernel-4.20 - 2019.01.26
https://forum.xda-developers.com/showpost.php?p=78768409&postcount=378
Surface IPTS build updates - 2019.01.30
https://forum.xda-developers.com/showpost.php?p=78796749&postcount=396
Update for Bliss OS - 2019.02.05
https://forum.xda-developers.com/showpost.php?p=78841065&postcount=412
Bliss OS Updates - 2019.02.23
https://forum.xda-developers.com/showpost.php?p=78973810&postcount=500
Bliss OS Updates - 2019.03.10
https://forum.xda-developers.com/showpost.php?p=79083283&postcount=549
Bliss OS 11.6 Updates - 2019.03.24
https://forum.xda-developers.com/showpost.php?p=79188758&postcount=576
Bliss OS 11.7 Updates - 2019.04.03
https://forum.xda-developers.com/showpost.php?p=79265706&postcount=616
Bliss OS 11.8 Updates (with GMS) - 2019.04.23
https://forum.xda-developers.com/showpost.php?p=79397531&postcount=676
Bliss OS 11.9 Release (with GMS) - 2019.05.26
https://forum.xda-developers.com/showpost.php?p=79607423&postcount=827
Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01
https://forum.xda-developers.com/showpost.php?p=80044597&postcount=1039
Bliss OS 11.10 x86_64 Generic Vulkan Build - EXPERIMENTAL - Build Date 2019-09-01
https://forum.xda-developers.com/showpost.php?p=80172193&postcount=1130
Announcement - Community Builds
https://forum.xda-developers.com/showpost.php?p=80672909&postcount=1268
Bliss OS 11.10 x86_64 Generic & IPTS Builds - With Vulkan - Build Date 2019-12-14/15
https://forum.xda-developers.com/showpost.php?p=81209911&postcount=1396
Bliss OS 11.10 x86_64 Generic - With Vulkan - Build Date 2020-04-11
https://forum.xda-developers.com/showpost.php?p=82275141&postcount=1675
Bliss OS 11.11 x86_64 Generic - With Vulkan and other graphics options - Build Date 2020-06-24
https://forum.xda-developers.com/showpost.php?p=82967929&postcount=1796
Bliss OS 11.11 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-08-03
https://forum.xda-developers.com/showpost.php?p=83214267&postcount=1841
Bliss OS 11.12 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-09-25
https://forum.xda-developers.com/showpost.php?p=83661769&postcount=1916
Bliss OS 11.12/13 x86_64 Generic - Kernel 4.19.122/5.8 - Mesa-19.3.5/20.1.0 - Release Date 2020-11-14
https://forum.xda-developers.com/showpost.php?p=83919621&postcount=1947
Bliss OS 11.14 x86_64 Generic - Kernel 4.19.122/5.10 - Mesa-19.3.5/20.1.10 - Release Date 2021-05-09
Bliss OS - Pie for PCs (LTS)
team bliss is pleased to present to you bliss rom based on Android 9 Pie 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...
forum.xda-developers.com
Downloads
Downloads has been moved for now. Please use the latest link from our website:
http://blissos.org
or
http://blissroms-x86.github.io
Contributing to the project
Bliss OS is in need of contributors. People to help squash some bugs, forward port features and support, and others to help with answering the common questions here in the XDA threads, or on our Telegram chat.
Pull requests are going to be spread out a little. All the commits for the build script will go through http://review.blissroms.com While everything else will have to be in the form of pull requests from https://github.com/BlissRoms-x86 or https://github.com/Android-PC
For anyone interested in joining our team, please visit the Bliss Family page of our site for more information on how to do that
https://blissroms.com/bfor.html
For those with even a little experience, but a lot of drive to learn more, we also offer our services to help people learn the ropes. https://t.me/Team_Bliss_Build_Support
Or for those a little more committed, look into the Bliss Family page of our site and join from there.
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
AllanJacques said:
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
Click to expand...
Click to collapse
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Does not work on Asus t101ha (cherrytrail)
wenna.speedy said:
Does not work on Asus t101ha (cherrytrail)
Click to expand...
Click to collapse
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
vEEGAZ said:
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Click to expand...
Click to collapse
Also for your case, can you try booting up with the old modprobe method mentioned in the second post? It may handle that wifi chipset a bit differently.
Another thing to try is to disable and then re-enable wifi service:
$ su
$ svc wifi disable && svc wifi enable
electrikjesus said:
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Click to expand...
Click to collapse
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
AllanJacques said:
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Instead, how about I tell you about this update Microsoft pushed to the surface book that made it to where I can't test my IPTS, or any kernel currently...
So to help with quality assurance, I would rather wait until I can test a build to make sure it works as expected before passing it off to the public.
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
mickey36736 said:
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
Click to expand...
Click to collapse
You got that result when using the easy installer? Did you try using the bootable USB install?
electrikjesus said:
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
Click to expand...
Click to collapse
I tried all boot options - stucked on boot everytime.
electrikjesus said:
You got that result when using the easy installer? Did you try using the bootable USB install?
Click to expand...
Click to collapse
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
mickey36736 said:
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
Click to expand...
Click to collapse
The symptoms suggest that some of your hardware isn't being detected right on install
Surface pro 2017 touch screen
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
I'm just gonna ignore this and ask you to read the OP again, but slower
Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
You shall wait until we release a build that supports your ipts display, and then rejoice!
Pie is "beta preview" and we build BlissOS to run on 1000's of potential HW configurations. Then we test with the devices we possess. When deemed ready, we share. A build which supports your device specific issue: not ready yet.
The info you requested to do this manually can be found using the search function of XDA(visit the website instead of app and look in a thread for "search this thread" then type: manual driver
.....or just read the OP ?