yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] ElfinJNoty:
Thank you for providing useful information regarding your issue. It makes it much easier for us to diagnose things with a fuller picture of what is going on.

Based on the names of the other builds you have tried, it appears you have a machine which is only capable of a 32bit OS. If this is the case, please do understand that our current 32bit release is labeled "experimental" for good reason, and you should expect to encounter bugs and/or issues.

Since you say you are receiving the same error on multiple installs of a variety of x86 Android offerings, we cannot/will not speculate about what is taking place on other OS's. But according to the pop up message: the app is detecting root access, and seems to be developed in a way that it shuts itself down if root is detected.

You have linked an installation method you used(the YouTube video) which is not one of our documented installation methods. Our USB installer method gives you the option to enable r/w(root) upon install. As does our UEFI only Windows .exe installer(writes /system as a read only .sfs by default). I would suggest installing Bliss OS with our suggested installation methods.

If that doesn't work, you must take the issue up with the app developer. Either use an older version of the app that didn't have this check for root access. Or ask the developer to write the app without this check in place. We have nothing to do with the development of that game, therefore it's intended behavior is out of our hands.

Please report back if doing a proper installation with our suggested install methods, alleviates this issue for you.
[BLISS ROMS Development] r0ckster05:
thx for the reply.

but how did you boot into the live mode?

on the ipts build the live mode hangs on detecting android-x86? like you mentions too earlier in this thread yourself.
[BLISS ROMS Development] bullet25:
The latest Generic build would boot to the live mode for me.

Alternatively, I'm sure if you can get it to boot to the live mode on anything you can do the same steps then run the install on the device.
[BLISS ROMS Development] plnewton:
Any Updates on getting Google Play Services in the Surface Book Version?
[BLISS ROMS Development] ElfinJNoty:
No

Our team no longer has a device with an IPTS display.

Not going to release at this time: something we cannot test and verify :svetius:
[BLISS ROMS Development] electrikjesus:
We are open to any Surface users that would like to learn how to maintain Unofficial Surface builds. Just a FYI ;)
[BLISS ROMS Development] plnewton:
Be happy to help if I can but I am no coder lol, what is involved?

I actually repair surface devices for a living so I have quite a range of them here to test with most of the time
[BLISS ROMS Development] electrikjesus:
Not much coding involved unless there's issues. For the most part, it's the same as building AOSP from source.
[BLISS ROMS Development] plnewton:
yeah no worries, happy to give it a crack mate..

let me know what you need done

cheers
[BLISS ROMS Development] electrikjesus:
Full details for how to get started on building Bliss OS are detailed on our docs site. https://docs.blissroms.com/Bliss OS/build-guide/

Let me know when you're able to get things going there or if you need any assistance, we have a build support chat on Telegram, https://t.me/Team_Bliss_Build_Support

Thanks again :D
[BLISS ROMS Development] electrikjesus:
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:

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.
[BLISS ROMS Development] hamdan198:
Complete and utter noob to all of this,

but could somebody link me to a surface LAPTOP build?

I don't mind if it is a bit outdated

Thank you and awesome job dude(s)!

:D
[BLISS ROMS Development] ElfinJNoty:
Please read the first three posts of this thread and familiarize yourself with the project.

You'll find a Surface device specific section @ docs.blissroms.com, as well as the link to our downloads @ Sourceforge

We aren't about giving hand outs here, but rather hand ups. Shouldn't be difficult to find the appropriate download link. The information is there already for you to help yourself ?
[BLISS ROMS Development] hamdan198:
Can't seem to find one for laptop though, there is pro, book but no laptop?

Also it would be helpful if you guys could 'hand me up' a guide to applying a custom kernel

more specifically https://github.com/jakeday/linux-surface

Thanks!

And the surface laptop keyboard is known to be a bit wierd, has it been reported to work on android?

Can patch the entire kernel to bliss os rather than just the firmware files?
[BLISS ROMS Development] electrikjesus:
Hey man, you'll want to start off with the latest IPTS version (which already includes jakeday's kernel patches) from Sourceforge. Then once you have that installed, head over to https://docs.blissroms.com/Bliss OS/installation-guide/#specific-surface-model-instructions

And read that a bit to gain an understanding of what you're about to do.

The Surface Laptop firmware is detailed on that page as well (v79 for the Surface Laptop), You can get the latest dump of that from jakeday's github here: https://github.com/jakeday/linux-surface/tree/master/firmware

Then all you need to do is follow the directions laid out for you already.

It's hard for us to make things any easier than it is already when there's so few of us working in this project, so I appreciate any patience you can spare.
[BLISS ROMS Development] hamdan198:
IPTS is touch right, with this firmware would the surface keyboard work as well?
[BLISS ROMS Development] ElfinJNoty:
The keyboard cover is supported in our builds when following instructions provided(linked above)
[BLISS ROMS Development] hamdan198:
Downlaoded latest ipts bliss rom and no keyboard (for surface laptop)?

what do i do now?

Sorry for being such a bother :)
[BLISS ROMS Development] harris123424:
How update bliss os x86 11.9 -> 11.10 ?
[BLISS ROMS Development] electrikjesus:
In this case, I don't know. My SurfaceBook I used to test those builds on never had the keyboard Not work. I would search around Jake-Day's github issues and see if any others have the same issue on the those two kernel branches. Otherwise, plug in a USB keyboard and mouse and use those to update the firmware files detailed in my previous post

Depending on install method,

EXE Install: You extract the new .img files from the .ISO on top of the old ones in the install folder on C:/

USB Install: Burn the .ISO to USB, and install like normal, it will detect as an update and act accordingly
[BLISS ROMS Development] hamdan198:
No i am typing this message on ubuntu on surface laptop, keyboard works fine. I think it is a .patch (check in the patches folder and then look for a ..hid thing)

Any idea on how to apply a patch
[BLISS ROMS Development] electrikjesus:
All the patches that apply to the kernel we use for that version are applied already. We might be missing configs though, and we can't use anything that requires python or a shell script to make work, so that might stop some hardware from functioning properly if it needed a script. The only way to patch the kernel for Bliss is to do it in the source and build the entire OS. It's not like Linux in that respect.

And just so you're aware, there are three IPTS builds that should work for that device. One with Kernel 4.9, and the other with Kernel 4.19 One with just the touchscreen patches (cali) and an older one with all the Jakeday patches (forward ported Jakeday's patches from Kernel 4.18)

Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k4.9.153-ipts_m-19.0.0_ax86-p_f-dev-kernel.org.iso	2019-03-25

Bliss-v11.6--OFFICIAL-20190323_x86_64_k-k4.19.24-ax86-cali_m-19.0.0_ax86-p_f-dev-kernel.org.iso	2019-03-25

Bliss-v11.5-PC_RC1--OFFICIAL-20190223-1446_x86_64_k-k4.19.24-ax86-ipts2_m-18.3.1_pie-x86_f-dev-kernel.org.iso	2019-02-24
[BLISS ROMS Development] hoshi411:
Install went great on surface pro 3.

Battery life is amazing.

1) What should i use for a camera app? I installed open camera all but it's really choppy and the rear camera doesn't show up.

2) What does everyone do for sleep?

I found a setting to doubletap on the navbar for sleep which works well but id like to know the other possible methods.

Thanks.
[BLISS ROMS Development] MaximalRoot:
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

2019-09-02

so this version seems to come on startup with the screen lock in swipe to unlock screen, which I was able to undo with the mouse, also the encrypt tablet option seems to freeze the dell laptop, also doesn't work under android x86 android-x86_64-8.1-r2 build not sure when it last worked if it ever worked under laptops or tablets, but for some reason the swipe up to unlock screen worked better under their image, not sure what went wrong with Official / bleeding_edge / Generic builds - Pie builds for 9-01 since even without a pinn or password or pattern it default on startup as being locked, also the stable and rc1 versions under grub2 would not install right keep getting an sector 2 error on thoese images, Bliss-v11.5-PC_RC1--OFFICIAL-20190223-0953_x86_64_k-k4.19.24-ax86_m-18.3.1_pie-x86_f-dev-kernel.org and the stable one before it, both during install failed but 11.10 grub2 install worked correctly on my old dell laptop used rufus-3.6 from windows with the iso images and partition scheme MBR and target system bios for my older dell laptop , please note I also have a desktop and laptop that uses GPT also, so I have two USB drives for each of these devices for them to bootup the android x86 images.
[BLISS ROMS Development] beacool:
Which version is compatible with surface book 2?
[BLISS ROMS Development] striplexterzo:
The last two realeses don t boot ?!?!

tablet HP X2 10-P020NL. No problema with Android x86 and previws realeses of blissos.
[BLISS ROMS Development] qjboyzcl:
Hope to add support for 144 monitor. This version of blissos adds video = 1920x1080@144 to the command line. It doesn't work, but it works well in Android x86 or primeos. I hope the next version works well. Thank you.
[BLISS ROMS Development] electrikjesus:
Is your device the Atom version of the X2 tablet? If so, the upcoming builds with Kernel-5.2+ should have better compatibility with those
[BLISS ROMS Development] Natus Chaos:
I installed the pie experimental build for x86 only from the website on a older computer and it runs really well, super user din't work but I used a xda guide to fix it, the problem I find mainly is that browsers and YouTube play videos only with a black screen, the sound is okay but no video. Is there any thing that me as neebie can do to fix this? If not is okay, thank you guys for this amazing project.
[BLISS ROMS Development] Ealge0110:
Wooow our kernel version has already bumped to 5.2 now?! Do you happen to know if the kernel 5.x's support for connected standby is working on Surface devices now?

---------- Post added at 10:46 PM ---------- Previous post was at 10:36 PM ----------

And hey! I saw you need someone to help maintain Surface builds? I was actually just about to look into building Bliss OS myself and I already have an Ubuntu build environment setup on a powerful machine. I'd be happy to lend a hand if you don't mind to give me a brief documentation for what patches you apply to the Surface brunch with each build and preferably also a list of the tools you used to apply them!
[BLISS ROMS Development] electrikjesus:
Possibly. How did you install it and what's the CPU & graphics card in there? If you can grab the OpenGL info I posted about in my last update post, that'll also tell us if things are getting loaded right.
[BLISS ROMS Development] electrikjesus:
Yeah, Looks like Mauro added the commits to fix fuse not working with sdcardfs, so I'm running a few test builds with that to make sure things are running right all around. https://github.com/maurossi/linux/tree/kernel-5.2_si_next

For the kernel development, my main tool is an old version of Gitkraken (2.2.0). That lets me visualize things enough to work with the kernel commits and patches and fix just about everything I need. Still have to use the terminal to apply the patches with the proper commit attribution intact, otherwise everything I have a merge conflict with ends up getting authored as me instead of the people that deserve the credit, but it's a lot better than using JUST a terminal for everything.

I typically use that to do my heavy lifting with the kernel, and just a terminal to apply all the patches. Jake-Day has a script, I just use one line in it to apply all the patches from his repo to my project folders kernel/ dir.

Our docs.blissroms.com should have mostly everything you need to get started building Bliss OS, and I can answer any questions you may have as well. Tagging me either in here or in our Telegram chat will get my attention. Just don't abuse it ;)

There are a couple others out there that have responded to the call to help as well, so I feel that the more people we can directly help here will end up becoming more people that we can help in the community on down the road.
[BLISS ROMS Development] Ealge0110:
Got it! Hopefully will have time on the weekend to take a look at it.

Since you mentioned there are a few others also interested helping with Surface builds, can we have a separate thread or a separate channel on Telegram where we can coordinate the effort?
[BLISS ROMS Development] electrikjesus:
Yes, if you PM me on Telegram, I can create a private dev chat for Bliss OS stuff to use.
[BLISS ROMS Development] Grumpy Cat:
Latest Vulcan version won't even boot on my laptop no matter what I do, even with GPU support disabled lol. Maybe it's just to old, it is a 2009 model Dell.
[BLISS ROMS Development] Magnesus:
On One Mix 3 Yoga it works flawlessy as far as I can test apart from - sadly - the goodix touchsreen. Tried doing modprobe goodix in terminal, the module loads but nothing changes.
[BLISS ROMS Development] electrikjesus:
You should try setting video= in Grub for your external display. You can use Google for more on that or we touch lightly on it in our docs

The squashfs errors tell me that something isn't right with your install. You might need to extract the system.img from within the system.sfs file for your install.
[BLISS ROMS Development] electrikjesus:
That might very well be the case. The Vulkan and gbm_gralloc drivers are mostly for newer hardware
[BLISS ROMS Development] electrikjesus:
If you can check around online for the Goodix touchscreen Linux drivers/kernel modules that work on that device, we may be able to add them to the mix without breaking things for other Goodix users.
[BLISS ROMS Development] Grumpy Cat:
Any version you recommend? It's still my Dell Studio 1747.
[BLISS ROMS Development] electrikjesus:
Does the latest experimental 32bit version we posted boot up OK on your PC?
[BLISS ROMS Development] Shubham Tople:
I have a canvas laptab 777w ? Any idea if bliss is will be comfortable with my system
[BLISS ROMS Development] ElfinJNoty:
No. We have no idea. We can only test on devices we own. We compile Bliss OS to be compatible with 1000's of potential hardware configurations. We rely on user feedback for what is and isn't working.

Suggest you install and test latest 11.10 release as a start, and go from there ?
[BLISS ROMS Development] talljosh:
Thanks! I solved the issue of not being able to see what I'm typing by using "video=1920x1200". With this option the device's display turns on in portrait mode (and is ungarbled!), and the external display shows the top half (or so) of what the device's display shows, but when I switch to the virtual terminal it restricts the resolution to the size of the external display so I can see what I'm typing.

When my external display is attached, using the video= option makes the device's display show correctly instead of being garbled. However, when I don't have the external display plugged in I can't seem to get the device's display to be ungarbled no matter what option I set for video=. I don't want to always need to connect an external display while booting, so I'd love to work out what's causing it to work with the external display. One thing I've observed is that, after I exit grub, I first get garbled text showing up on the device's display, then the (ungarbled) text shows up on the external display, then for just a second or two the external display shows the boot animation while the device's display shows nothing. After that, both displays are blank for a moment before they both show the boot animation. I wonder if this momentary flicker before the device screen works is something being reinitialised, causing it to work. Any pointers on where to look to figure out more about this?

I'm using the 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 image, and I verified the checksum. I tried installing the image on a different USB drive in case it was a dodgy drive, but I still get the errors. It's worth noting that sometimes it boots up properly and in that case I don't see any squashfs errors in dmesg. But often it gets stuck on the boot animation. (Also, when it does get to the lock screen, the lock screen seems to crash and restart periodically, but I'll worry about that issue later.)

I've extracted the system.img file from system.sfs, but I think I'm going to have to buy myself a bigger USB drive before I can test with that - my 4GB disk doesn't quite seem to fit everything with the extracted system.img. Do I just put system.img in the root folder alongside initrd.img, install.img and ramdisk.img?
[BLISS ROMS Development] :
I think it sounds like a install thing too but possibly a driver issue I wouldn't know how to help with that besides trying nomodeset editing grub.cfg(if you can find it).

I got froze at the black "-" at top screen few times before the logo but no garbles installing different ways. Don't use auto install, say no to gpt when it asks because it can bring up wrong cf/cgdisk. Create/Modify free space first as primary with a bootflag as well don't specify file type yet then write to disk, go back it should come up as unknown filesystem. Then proceed format the unknown filesystem to ext4, i used r/w. When it is done do not click run now make sure you reboot first.
[BLISS ROMS Development] electrikjesus:
Part of your issue is that you are running it all from a USB drive instead of installing to the HDD/SSD. You're going to run into some permissions and space issues when doing that. Live Mode is only meant to test compatibility, not run the system full steam ahead.
[BLISS ROMS Development] bensr20det:
First off I would like to say thank you to everyone involved in this project. It is clear that many very talented people have spent many hours on this and from what I have seen it is amazing. I was just introduced to Bliss OS today and have spent many hours reading up and attempting to educate myself. I have a Surface Pro 3 that has not been used much lately and I think Bliss OS could make me love it again. I wiped the device and downloaded 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. I did the auto install and got everything setup. Is that the best build for my device? and are there any recommendations for things I need to do after I install or suggested tweaks. Right now the keyboard crashes but that is not a big deal since I can side load one that works. and SuperSU will not update and I haven't figured that one out yet. Thanks for this awesome OS and I look forward to using it.
[BLISS ROMS Development] talljosh:
I kind of thought I was still testing compatibility, since it's still only booting up all the way roughly half the time. But since you say that installing it might help with some of the problems I'm seeing, I tried to give that a go. However, until I can do something about the garbled device display, I can't use the installer. Regardless of whether I have an external display attached, and use video= or nomodeset options, I get this kind of thing:

I notice that there's an auto install option on the advanced grub menu, but I'm a bit hesitant to use it. I don't want to wipe away my Windows install. Is there a way I can modify the grub command to tell it what partition to install to?