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

Bliss OS - Pie for PCs (LTS)

Search This thread

morganabels

Member
Oct 23, 2016
21
0
I skipped installing the included GRUB from the installer because I already have GRUB2 installed. How do I add a BlissOS entry there? I installed BlissOS on a new NTFS partition.
 

Moritz777

New member
Aug 23, 2021
1
0
I have a problem on my Surfage GO. Sometimes when I turn the screen off it will not turn back on again and I will have to force a reboot. But there ist a second problem, which ist the battery drain. It can not last a night on standby and is always flat the next day. I am using Bliss os 11.14 with extendet hardware support on the Surface GO 1.
 

Ictcreations

Member
Feb 29, 2012
25
2
in relation to the screen not turning on bug, i have exactly the same issue. the screen goes off, but when i press the power button it does nothing. I have a work around that i found by accident..

If you have the surface go type cover from microsoft, fold it up onto the screen as you would do when you have finished with the surface and then open it again. you should then find screen comes back on and at the lock scrren. :cool:

tried it several times and always works.

As for battery drain, i've noticed that. but tbh it doesnt really bother me. I'm never on it long enough for it to cause me issue, i can still get 3/4 hrs out of it, and lets not forget that its a bloody miracle that android even works on a surface!!!! my hats off to the mega talented developers.

There are a ouple of things that would be great to get fixed and working though... one would be the camera for sure, and the other would be GPS.
 

alex4998

New member
Aug 30, 2021
3
0
This question has been asked a few times already but I didn't find any answer. What about installing Bliss OS on XPS 13? The OS starts perfectly fine from the USB boot stick and the most important hardware items: display, keyboard, touchscreen, wifi, bluetooth, etc work fine however it looks like it cannot be installed. If a USB boot stick method is used it cannot find a partition to install to. It is impossible to create a partition as well. It always gives an error when even clicking on Create Partition. It sort of installs when the installer is started from Windows. It definitely creates AndroidOS folder and after reboot you can try to start Bliss OS but it doesn't go past detecting Android-x86.
I would say all that is related to the Android core unable to use that particular internal SSD installed on XPS. Is there a workaround for that? Maybe some changes in the configuration might help?
 

alex4998

New member
Aug 30, 2021
3
0
I have a Bluetooth GPS and I even can pair it with Bliss OS and read the NMEA stream. Now, I'd like to use this GPS feed for the Android Location. There are applications in the store which are supposed to do that but all of them want me to do this "Please go to the developer option, click "Select mock location app" and select this app as provider." I cannot find Developer Option or Mock Location in the Bliss OS. Is it possible to do that via configuration files or what not? Is there another way allowing to use external Bluetooth GPS for the location service?
 

alex4998

New member
Aug 30, 2021
3
0
There is one strange rendering behavior. That can be an application issue or can be Bliss OS issue. I lean toward the Bliss OS issue because an a multiple Android devices it looks fine. I'm talking about Garmin Pilot application. See two attached images. The one which has contrast black shadows of the terrain are from Bliss OS. The other with soft shadows is from an actual device. Do you think it can be related to how certain things are rendered on the low level? Is there a fix or workaround for that?
 

Attachments

  • FromADevice.png
    FromADevice.png
    203.2 KB · Views: 26
  • FromBlissOS.jpg
    FromBlissOS.jpg
    3.4 MB · Views: 27

selfi

Member
Sep 11, 2016
7
0
First install gearlock then install gapps via gearlock, second download googleplayservice.apk and googleplaystore.apk via apkmirror, third goto #>system>priv.app>com.android.vending>replace with googleplaystore.apk then rename to com.android.vending.apk and set permission to 0644
And put googleplayservice to #>system>priv.app>com.google.android.gms>replace and rename com.google.android.gms.apk and set 0644
Reboot
 

explorer470

New member
Sep 14, 2021
1
0
I'm having some issues installing this on my surface pro 5. I initially tried the android-x86 build (non-bliss) as it was my first result in trying to figure out how to do this. I created bootable usb, installed as dual boot by creating an extra partition on my drive. I was able to boot, format partition to ext4, install and boot properly but the touch screen did not work.

I since discovered the surface has some unique needs and have been pointed to Bliss as a solution but am struggling. I downloaded and installed the "Bliss OS 11.14 FOSS Experimental (x86_64)" and have it loaded on that same partition, formatted again to ext4, and it boots. Still no touch screen support though. I've read others commenting in this thread that they've successfully installed onto a Surface Pro 5, however, I can't figure out what i'm doing wrong. I know i've taken a bit off-nominal path before stumbling on this thread, but could use some help figuring this out or where i went wrong.

Thank you in advance!
 

yeahman45

Senior Member
Dec 26, 2010
1,683
108
I have installed the latest rom with kernel 4.20 on an Chuwi Hi8 (Intel Bay Trail Tablet)
The necessery driver was already in the system.img, but the wrong driver was choosen from the system.
So at the first boot it won't reconize touch-events correctly.

I wrote this little script for patching this after install the ROM. Could this help you with your problem? :)

Code:
#!/system/bin/sh

#Block Module and Disable Silead_Firmware
echo "blacklist gslx680_ts_acpi" | tee -a /etc/modules.blacklist
mv /lib/firmware/silead_ts.fw /lib/firmware/silead_ts.bak

#Enable Firmware for Device
cp /lib/firmware/silead/gsl1680-chuwi-hi8.fw /lib/firmware/silead/mssl1680.fw

#Create Calibration Folder
mkdir -p /data/misc/tscal
touch /data/misc/tscal/pointercal
chown 1000.1000 /data/misc/tscal /data/misc/tscal/*
chmod 775 /data/misc/tscal
chmod 664 /data/misc/tscal/pointercal

PS: At first I had problems with the Android UI (force closes), but after enabling Vulkan at Boot it seams fine..
At the moment I try to get the battery indicator to read the right values (which already been provided from the kernel in another folder) and
bluetooth still not works (but this was under ubuntu too).
how did you install it please?
did you overwrite the existing android that was on the device?
did you keep windows?
can you dual boot windows and bliss os?
 

yeahman45

Senior Member
Dec 26, 2010
1,683
108
I have installed the latest rom with kernel 4.20 on an Chuwi Hi8 (Intel Bay Trail Tablet)
The necessery driver was already in the system.img, but the wrong driver was choosen from the system.
So at the first boot it won't reconize touch-events correctly.

I wrote this little script for patching this after install the ROM. Could this help you with your problem? :)

Code:
#!/system/bin/sh

#Block Module and Disable Silead_Firmware
echo "blacklist gslx680_ts_acpi" | tee -a /etc/modules.blacklist
mv /lib/firmware/silead_ts.fw /lib/firmware/silead_ts.bak

#Enable Firmware for Device
cp /lib/firmware/silead/gsl1680-chuwi-hi8.fw /lib/firmware/silead/mssl1680.fw

#Create Calibration Folder
mkdir -p /data/misc/tscal
touch /data/misc/tscal/pointercal
chown 1000.1000 /data/misc/tscal /data/misc/tscal/*
chmod 775 /data/misc/tscal
chmod 664 /data/misc/tscal/pointercal

PS: At first I had problems with the Android UI (force closes), but after enabling Vulkan at Boot it seams fine..
At the moment I try to get the battery indicator to read the right values (which already been provided from the kernel in another folder) and
bluetooth still not works (but this was under ubuntu too).
can you tell me what build (iso) did you try? I have tried the latest one and it seems stuck on bliss bootanimation
 
@yeahman45:

I think the last version I installed was Bliss-v11.13--OFFICIAL-20201113-1525_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.0-llvm90_dgc-t3_gms_intelhd.iso. With this version I also had no more problems with the "sleeping" of the tablet (did not turn on after the device was longer in standby). And I think it was necessary to select vulkan as boot option to get the system running.

I had completely wiped the internal disk to install Bliss, but as i know a dual boot should be possible. But you won't be able to select any other boot option in Grub, as there is no support for touch or the buttons. You will have to use a usb adapter and a keyboard to change the selected system at boot.
 
  • Like
Reactions: yeahman45

yeahman45

Senior Member
Dec 26, 2010
1,683
108
@yeahman45:

I think the last version I installed was Bliss-v11.13--OFFICIAL-20201113-1525_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.0-llvm90_dgc-t3_gms_intelhd.iso. With this version I also had no more problems with the "sleeping" of the tablet (did not turn on after the device was longer in standby). And I think it was necessary to select vulkan as boot option to get the system running.

I had completely wiped the internal disk to install Bliss, but as i know a dual boot should be possible. But you won't be able to select any other boot option in Grub, as there is no support for touch or the buttons. You will have to use a usb adapter and a keyboard to change the selected system at boot.

ok thx man!
ah ok so you wiped the windows partition too? I would like to replace the old android 4.4 with bliss os but still keep windows
 

yeahman45

Senior Member
Dec 26, 2010
1,683
108
I have installed the latest rom with kernel 4.20 on an Chuwi Hi8 (Intel Bay Trail Tablet)
The necessery driver was already in the system.img, but the wrong driver was choosen from the system.
So at the first boot it won't reconize touch-events correctly.

I wrote this little script for patching this after install the ROM. Could this help you with your problem? :)

Code:
#!/system/bin/sh

#Block Module and Disable Silead_Firmware
echo "blacklist gslx680_ts_acpi" | tee -a /etc/modules.blacklist
mv /lib/firmware/silead_ts.fw /lib/firmware/silead_ts.bak

#Enable Firmware for Device
cp /lib/firmware/silead/gsl1680-chuwi-hi8.fw /lib/firmware/silead/mssl1680.fw

#Create Calibration Folder
mkdir -p /data/misc/tscal
touch /data/misc/tscal/pointercal
chown 1000.1000 /data/misc/tscal /data/misc/tscal/*
chmod 775 /data/misc/tscal
chmod 664 /data/misc/tscal/pointercal

PS: At first I had problems with the Android UI (force closes), but after enabling Vulkan at Boot it seams fine..
At the moment I try to get the battery indicator to read the right values (which already been provided from the kernel in another folder) and
bluetooth still not works (but this was under ubuntu too).
how do you apply the script after installing the rom? I mean where do you execute this? :) by adb?
 

KK28KK

Member
Oct 19, 2021
6
1
Turkey/Canada
I have another question incase if anyone wil see. Blustack android emulator is able to give ASTC support via software, not hardware. So, is it possible to have ASTC support by software in Bliss OS?
 

lionking037

New member
Apr 27, 2021
2
0
Thanks. I have installed "Bliss-v11.14--OFFICI" and it works perfectly fine in my Intel Celeron CPU N3450. Wifi works fine too. will update if there is any bug found.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 72
    Jc3gieK.png


    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.


    bDCQlHu.png


    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

    KorMlds.png


    Open Gapps Project

    FJaqYur.png


    !!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.
    CJQkPNY.png

    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.


    57yteuF.png

    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
    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
    19
    Bliss OS 11.8 Updates (with GMS) - 2019-04-23
    !! Please remember to not quote these update posts, or any of the OP's !!

    We finally have the green light to release builds with Play Store included. So I'm uploading a few generic builds with that included, but don't worry, other 11.8 releases with our FOSS apps are still planned. As for the changes, additions include updates to system stability, customization, and more. Finally got Lockscreen working properly too. Still working on getting sleep/resume to work right on x86 though. So we aren't planning on changing the release type to Stable until then.

    There's still a trick to getting Taskbar and our navbar options to play nicely, so please make sure you check the instructions on the 2nd post for that. The 4.19 build should also boot for most AMD GPUs too. VUlkan support is still spotty for some chipsets though. Consider that still experimental.

    Builds being uploaded:
    Bleeding-Edge Builds - !! for all non-IPTS devices !!
    • Bliss-v11.8--OFFICIAL-20190420-1316_x86_64_k-k4.9.153_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org_gms.iso
    • Bliss-v11.8--OFFICIAL-20190420-2101_x86_64_k-k4.9.153_m-19.0.0_ax86-p_f-dev-kernel.org_gms.iso
    • Bliss-v11.8--OFFICIAL-20190421-1341_x86_64_k-k4.19.32-ax86-ga_m-19.0.0_ax86-p_f-dev-kernel.org_gms.iso
    Bleeding-Edge IPTS Builds - !! for Surface * X1 devices !!
    • None

    General Updates List:
    • Notification actions are stable
    • Bluetooth updates & fixes
    • Power buttons working on many more devices (still no sleep state)
    • Some upstream updates from Project Celadon, Android-x86 & PHH-Treble
    • and much much more, check the changelog.

    Known new issues:
    • Navbar switch is not sticking through reboot. Need to turn off the navbar manually after reboot if you are using Taskbar as the navbar.
    • Sleep states aren't working right on many machines. Some can cause SystemUI to restart
    • Power buttons may still not work on a few machines.

    Changelog:

    Code:
    Changelog too large for posting here. Links: 
    
    https://sourceforge.net/projects/blissos-x86/files/Official/bleeding_edge/Generic%20builds%20-%20Pie/Changelog-Bliss-v11.8--OFFICIAL-20190421.txt/download
    
    https://sourceforge.net/projects/blissos-x86/files/Official/bleeding_edge/Generic%20builds%20-%20Pie/Changelog-Bliss-v11.8--OFFICIAL-20190420.txt/download

    Thanks, and have a Blissfull time!!

    Head on over to http://blissroms.com for the downloads. And while you're there, feel free to checkout more of what we're doing as a nonprofit. We're also always looking for developers, maintainers, designers and social media peeps to volunteer their time. If that's you, you can find the Join Team Bliss link on our nonprofit page.
    19
    Bliss OS 11.10 x86_64 Generic Vulkan Build - EXPERIMENTAL - Build Date 2019-09-01
    !! Please remember to not quote these update posts, or any of the OP's !!

    We've been running ourselves a bit thin lately, but we have gotten a lot done towards making this the best Android on PC experience yet. So we'll be going with another experimental build this round. This one is a generic build that contains a few updates and changes for Vulkan hardware (mostly all the Intel Integrated GPUs, but some amd & nvidia GPUs too).
    This build also contains a few bits forward ported to Pie from Android-x86 project, so you'll now be able to find OpenGL and Manufacturer info in Settings, with a little bit of work (see notes)

    Release Notes:
    - Sleep states are partially working using Vulkan & gralloc_gbm (forces switching from default of drm_gralloc to gbm_gralloc when using VULKAN=1 from grub). Need to use a third party tool for now to trigger sleep states if it's not showing up for you in the power menu (I found one called EasyOff). CPU will still be active during mock sleep states, but activity will drop to almost nothing.
    - For OpenGL and Manufacturer info to be shown, you will first need to enable Developer Options, then set the flag for About Phone v2 to Off. Then you can find it in the About Phone section of Settings.

    Notes on sleep states:
    - Throughout testing, sleep states weren't always working right though, so switching between old-modprobe mode and normal boot mode while using the VULKAN=1 grub command was able to get things to trigger right most of the time.

    Vulkan Build
    - Need to select Vulkan from advanced grub menu, or manually add "VULKAN=1" to Grub command line

    Builds being uploaded:
    • Bliss-OS-v11.10--OFFICIAL-20190901-2019_x86_64_k-k4.19.50-ax86-ga_m-p9.0-x86-11.10_ld-2.4.99-ma-p_dg-pie-x86_dh-pie-x86-rt-vulkan.iso

    Known new issues:
    • Navbar issues still persist when using Taskbar. Please set a fallback Gesture method in the Blissify app first, then switch navbar to SmartBar, then disable it and enable Taskbar. This can also be switched later using Quick Tiles from the statusbar.
    • Sleep states aren't working right by default on non Vulkan & IA-Hardware-Composer builds (coming soon). Some can cause SystemUI to restart (lockscreens won't be of any use due to this)
    • Power buttons may still not work on a few machines.

    Changelog:

    Code:
    Changelog too large for posting here. Links: 
    https://sourceforge.net/projects/blissos-x86/files/Official/bleeding_edge/Generic%20builds%20-%20Pie/Changelog-Bliss-OS-v11.10--OFFICIAL-20190901.txt/download

    Thanks, and have a Blissfull time!!

    Head on over to http://blissroms.com for info on Bliss. And while you're there, feel free to checkout more of what we're doing as a nonprofit. We're also always looking for developers, maintainers, designers and social media peeps to volunteer their time. If that's you, you can find the Join Team Bliss link on our nonprofit page.
    16
    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

    Downloads

    Downloads has been moved for now. Please use the latest link from our website:
    http://blissos.org
    or
    http://blissroms-x86.github.io