yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] KKJdrunkenmonkey:
Yes, unfortunately. Can you provide some suggestions on where to go from here?

I could use an older build of Bliss, but I've been hesitant due to a post on reddit regarding touchscreen stability. Per your comment there it seems that the newer kernels are not very stable with IPTS, something to do with driver error handling. The latest version of Bliss with GApps, IPTS, and a 4.9 kernal seems to be Bliss-v10.0-Beta-android_x86_64-OFFICIAL-20180303-2244_k4.9.83-ax86-ipts-gal_m17.3.6dev_fw.iso, should I be trying something like that?

Alternatively, how "no way" are we talking? Because I can edit the system.img manually if you can provide some expertise on what to copy in. I tried it once, going through the install script to see if there was anything special I needed to do, and copied in everything from an Android 9.0 Nano of GApps. This resulted in a Google configuration utility acting as home which kept crashing continuously, to the point that I couldn't even reach the Android settings to disable it. Apparently I have just enough knowledge to be dangerous, but not quite enough to get anywhere useful on my own. I made sure to take good notes, I can provide the steps I used if it would help you or someone else.
[BLISS ROMS Development] electrikjesus:
If you are willing to install all the right apps, libs and access permissions in the system, then it is feasible. For the average person though, this would take an entire days time
[BLISS ROMS Development] electrikjesus:
You're on the right path. But it almost seems as this route could be converted to all be an on-device script to download and copy the files. It looks like you're doing this from a Linux term though, so you might not need to even think about some of these. But you do go the on-device script route, you might hit a few bumps. what you've done might have at least shown you all the needed steps, but there might be some differences when doing those with the alt-f1 console. Some commands might need to be altered a little.

Some notes below:

# Skipping Google Assistant commands

This is a good move for now

# Skipping "Google Play Services as error reporting service" commands

You will want to replace the gmscore we add for fdroid/microG. Many of those apps will need to go in order to be replaced with OpenGapps prebuilts and libs.

# What the heck is pittpatt? Doesn't exist in my system/vendor.

I don't know on this.

# Unmount file system so it can be repacked into sfs

the system will be mounted with the ability to use r/w from alt-f1 term as long as you extract the system.img from within the system.sfs. If you are just repacking all this in order to rebuild the .iso, then you will need to repack the .sfs then.
[BLISS ROMS Development] ziomek00:
Yes, it only works on MX Player + x86 Codec.:)

How can I turn on HDMI 2.0 audio in Bliss OS and analog jack green?

I can only get sound via the USB Soundbar.
[BLISS ROMS Development] b00dymoon:
How to make mouse work camera and fire in pubg game please
[BLISS ROMS Development] CupangTerbang:
libhoudini does not support old CPU

tried test all app with arm librry, but always force close.

logcat show :

expected cpu feature AES >> is not supported

expected cpu feature SSE4.1 >> is not supported

expected cpu feature SSE4.2 >> is not supported

im using intel pentium P6300, bliss os 32bit Pie
[BLISS ROMS Development] electrikjesus:
I'll be uploading a kernel-4.18 version soon that may have a different outcome
[BLISS ROMS Development] ayaj007:
after installation I got display glitch like this
[BLISS ROMS Development] electrikjesus:
Means no hardware accelerated support. Use some of the kernel command line options from Grub to diagnose
[BLISS ROMS Development] electrikjesus:
Could also do that on some hardrive controllers too
[BLISS ROMS Development] lp894:
The newest IPTS version gets stuck in a boot loop on the SP4. Granted I know you tested it on the original surface book, but don't they both use the same touch screen? That is a complete guesstimation based on the fact they were released on the same day. I know that means diddaly squat in the grand scheme and the drivers could very well be different, I legit don't know lol
[BLISS ROMS Development] electrikjesus:
You may need to try and see if reformatting data allows you to boot. I've come across that issue once or twice this round
[BLISS ROMS Development] mahir555:
Thank you for this work.

Just a general question .. Can we run google ARcore on this rom ? Thanks
[BLISS ROMS Development] Deepak03:
Stuck at boot and showing "console: /#"

Bliss os 11.1v is stuck at booting and showing console for type commands console: /#

I tried to type commands like start/run nothing work but when i typed reboot it got rebooted to windows 10 os .

What should i type there to run bliss os. It's my first time:p to install dual os can you please help me to run it on my Lenovo Yoga 510.[IMG="screenshot"]https://drive.google.com/file/d/1ru5UnOZHpDaZ3zCKC9Ju-6MQjWVKN_uC/view?usp=drivesdk[/IMG]
[BLISS ROMS Development] soenggam:
It doesn't support your discrete graphics card.please disable it.
[BLISS ROMS Development] Deepak03:
But I'm using AMD A9 Radeon R5
[BLISS ROMS Development] soenggam:
Yes,you should disable it.

---------- Post added at 10:32 AM ---------- Previous post was at 10:28 AM ----------

You mean the cpu is amd a9 and GPU is radeon r5?
[BLISS ROMS Development] Deepak03:
And how can i disable it?

Can you help me to install bliss os??? Please, it's my first time to run dual boot OS?

---------- Post added at 10:35 AM ---------- Previous post was at 10:34 AM ----------

Yes
[BLISS ROMS Development] lp894:
Does this one also have the touch screen drop out issue on your surfacebook, or will that pretty much always be an issue to deal with?

---------- Post added at 02:02 PM ---------- Previous post was at 01:21 PM ----------

Doesnt work in live mode on the SP4. Well, it boots, but no touchscreen. Again I know you tested on the surfacebook but i tried lol
[BLISS ROMS Development] electrikjesus:
I haven't tested that yet. So if you have time, please let us know
[BLISS ROMS Development] electrikjesus:
you have to replace the firmware with the proper firmware for the sp4 before any touch screen will work for you. And unfortunately yes, touchscreen does drop eventually but stays on far longer
[BLISS ROMS Development] xhitm3n:
Im testing the latest build on my SP4 do i need to Rebuild ROM with the SP4 Firmware or can i ROOT explorer and change files directly?
[BLISS ROMS Development] electrikjesus:
Root explorer should do it once you've extracted the system.img from the system.sfs and renamed the system.sfs or deleted it.
[BLISS ROMS Development] Deepak03:
After booting stable version bliss os v7.2 on my Lenovo Yoga 510. It's got successfully boot and successfully started but showing nothing but screen glitches how can i fix it? May anyone help me please? It's showing that os is booting up but with screen glitches. It's showing mouse cursor it's showing colors but not readable not understandable. Whole screen have too many line. Whenever i move mouse it's showing that something is moving. Can anyone help me please?:)
[BLISS ROMS Development] ElfinJNoty:
"Stable" only signifies that the build is using the more generic kernel version 4.9. There is not a magic fix.(otherwise we would have likely included it in the build!)

As mentioned previously, your GPU is not fully supported. Please attempt to live boot a Linux distro from USB and see if your GPU is supported. If so, tell us what kernel ships with that distribution of Linux

You are now going backwards in Bliss versions to achieve better compatibility.... This will not yield improved results for you.

Please consider that Pie based builds are currently in Beta Preview status and are a work in progress. Thank you for reporting your usage. Do not expect full functionality or compatibility at this time.
[BLISS ROMS Development] lllboredlll:
Pm me an address and I'll get one headed your way. To clearify, I have 32 and 64 gb RT's, is that OK?

---------- Post added at 03:23 PM ---------- Previous post was at 03:20 PM ----------

I have one or two RT's I could donate. I ask nothing but a ty
[BLISS ROMS Development] KKJdrunkenmonkey:
Your logcat messages are correct. Per this Wikipedia article, the P6300 does not support those instruction sets. If what you're trying to do requires them I do not know of a workaround; but I thought they were there for performance improvements rather than as a requirement for things to function. I'm not an expert though, so maybe someone else can add more.
[BLISS ROMS Development] electrikjesus:
Sounds like it may be defaulting to software decoding if you can only use mx player and the x86 codec. So, you're gonna have to do some research into what your sound chipset is and then help us help you by finding a Linux kernel module repo for it.
[BLISS ROMS Development] ziomek00:
I mean, what should I do?

For me it looks like this:

pcmC0D0 - jack green

pcmC0D3 - HDMI

pcmC0D7 - DVI
[BLISS ROMS Development] KKJdrunkenmonkey:
Without knowing the hardware (i.e. the chips inside the box), we can't tell you what drivers you need for that hardware to run the jacks you describe. As an example, if I were to have this question on my main PC's motherboard, I'd look at the website for it or a technical manual and find that it has a SupremeFX S1220 codec chip and an ESS® Sabre Hi-Fi ES9023P digital-to-analog converter chip. I don't know which of those is the one I need to address, so I'd research both of them and see if I could find information on how to use them in Linux (since Bliss is built on Android, and Android is built on Linux). Chances are when you find them you'll also find installation instructions; if you have trouble, come back here and someone might be able to help you further.
[BLISS ROMS Development] ziomek00:
Sorry.

7.1 CH HD Audio (kodek audio Realtek ALC892)
[BLISS ROMS Development] a1lfa:
I have a SurfaceBook and I have tried the latest IPTS build from March 2019. The touch screen works but there is no Play Store. On the latest build there is no IPTS touch support but it has google play store. Is there a version of this awesome os someone has built that supports IPTS and google services?

Thank you for the help

---------- Post added at 02:34 AM ---------- Previous post was at 02:32 AM ----------

I have a SurfaceBook and I have tried the latest IPTS build from March 2019. The touch screen works but there is no Play Store. On the latest build there is no IPTS touch support but it has google play store. Is there a version of this awesome os someone has built that supports IPTS and google services?

Thank you for the help
[BLISS ROMS Development] KKJdrunkenmonkey:
Good. So, per electrikjesus's comment, if you look on the internet there should be drivers available for Linux for that device. They'll probably have instructions with them too.

---------- Post added at 02:48 AM ---------- Previous post was at 02:43 AM ----------

I'm in the same boat as you with a Surface Pro 2017. A couple pages back in this thread you'll find a discussion between me and electrikjesus regarding adding Open GApps to the build with IPTS support. So far no luck, I've gotten all of the Open GApps packages in place but SystemUI continually crashes with a generic null object reference exception on anrdoi.app.Fragment.setNextAnim(int) so something isn't right. If I get the process down I plan to report back here. In the meantime, if you're good at this stuff give it a shot and let me know how it goes for you!
[BLISS ROMS Development] a1lfa:
Understood. Thanks for the hard work. Honestly I will be of no real help with this besides testing it on the surfacebook pro 2016 but I am open to learn.
[BLISS ROMS Development] amn1987:
I had intially tried the latest 11.10 Vulkan build (kernel 4.19) which would boot only in non-HW accelerated mode. But Wifi/BT worked. Next I tried one of the stable builds, 11.9, kernel 4.9. This booted fine but Wifi/BT don't seem to work. No devices are found.

System specs: Intel Ci5 8250U with HD620 iGPU and Nvidia MX150 dGPU. Qualcomm Atheros QCS61x4A Wifi chipset.

Edit: Wifi worked after booting in Legacy Modprobe mode.
[BLISS ROMS Development] patriciogac:
Hi. Thank you for all the hard work. Here is a link when I have found information about the Silead GSL 1680 touchscreen

https://linux-sunxi.org/GSL1680

https://xdaforums.com/windows-8-rt/general/silead-mssl-1680-t3116128

In the Bliss OS realeses with the 4.9 kernel, the touchscreen works, but the calibration is bad, and there is no calibration tool that seems to work. I read many tablet users has ths touchscreen and many that tried Bliss OS or other similar android to x86 linux kernel based tablet has described the same simtoms as I with my tablet. All other features works correctly (WIFI, BT, etc)

Please if someone with the knowledge that I dont have is so kind to take a look or can guide me to make it work, or if the masters of this project could include the correct driver on future realeases will be awesome!. Thakn you in advance

Best regards

P Gac
[BLISS ROMS Development] retro-78:
Hi

Is there a version of bliss os without google play services ?

If not, do you know another android x86 distribution without google play services preinstall ?

I plan to use a FOSS android x86 for a TV box.

Thank you
[BLISS ROMS Development] electrikjesus:
Yes, there are older versions without it, take a look at the update posts from post 3 to see what ones. Also, I will have a few new Pie releases uploaded hopefully later on today. One with FDroid/microG and one with Google Play.
[BLISS ROMS Development] M47Z:
Just tried the new build. Awesome!

Bliss-v11.10--OFFICIAL-20191214-1647_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-undefined_foss.iso

Running on Medion P2213T (older low budget aio tablet/laptop). Installed from USB with auto install option on internal flash memory.

Good stuff first!

- No gaps version again! Microg included. Wouldn't need that either but I don't care!

- Wifi working

- bluetooth working

- speakers working

- screen brightness slider working

- auto rotation (kinda) working

- all physical buttons besides "dolby" button (kinda expected) working. Windows logo acts as capacitive home button!

So, after all it seems like my hardware is mostly supported out of the box! It makes me happy to see this project grow into an actual full fledged os. Just amazing.

Anyways here are the issues I had so far:

- "Issue with SD card - Tap to fix" notification. When I click on it it asks me wether I want to use it as portable or internal memory. For both options, it will then try to format the "sd card". After that the system won't boot anymore. All good if I just ignore the notification.

- "SuperSU - The SU binary needs to be updatet" notification. When clicking through it will try to update for a few minutes, then just fail.

- volume buttons switched: volume down makes it louder, volume up less loud.

- Screen rotation is off by 90°. Let me explain: I got the tablet in the keyboard dock, so it is horizontal. Screen is in the right rotation to begin with. When I turn on auto rotation now, it will rotate the screen to portait mode, even though it is still horizontal. If I then rotate it so it is vertical, the screen orientation switches to horizontal. Short: rotation sensor works, but the actual screen orientation is always off by 90°.

- Keyboard dock: For now the HDD included in the keyboard dock is recognized by BlissOS. But the trackpad as well as the keyboard itself won't work. In settings -> language and input, I do see an entry "Physical keyboard - AT Raw Set 2 keyboard" but no keystroke is recognized. Keyboard and trackpad work in Windows and all Linux distros I tried so far. Keyboard works in GRUB (the one that was installed with bliss) and BIOS as well. So most likely a driver does exist but is not included yet or faulty.

As always: Can't thank you enough for your time and effort. Keep it up!
[BLISS ROMS Development] electrikjesus:
For the screen rotation, you will need to figure out the correct orientation by experimenting with the order like we do in init here: https://github.com/BlissRoms-x86/device_generic_common/blob/p9.0-11.12/init.sh#L330 You can edit the init.sh on device after mounting as r/w from the alt-f1 console to try things out. Then once you get the magic sauce figured out, we can add it via a pull request on GitHub.

For the keyboard input, I am almost thinking that there are conflicting modules. Can you try and boot using old modprobe mode and see if that finds the correct keyboard dock drivers?
[BLISS ROMS Development] M47Z:
Booted the same version from USB drive in modprobe mode. Still not reacting to anything, touchpad or keystrokes. (Does it make a difference if I try this from USB live vs installed os?)

Will do!
[BLISS ROMS Development] electrikjesus:
The only other thing I could think of is to try and use lsmod from alt-f1 console to see what modules load, then compare against what lsmod shows from your successful Linux distros
[BLISS ROMS Development] KKJdrunkenmonkey:
Any chance of an IPTS build with Google Play? I've been attempting to get Open GApps installed, but so far every attempt results in SystemUI crashing continuously upon startup. Thank you, sir.

EDIT: Nevermind! Due to the pain of dealing with BitLocker not liking grub being reinstalled, I had stopped reinstalling it as I went through iterations of testing to get Open GApps in place. On a side note, I now realize that not formatting the install partition and reinstalling grub may have been biting me in the behind for my testing. Complete newb mistake. When it came up without any real differences I re-installed 11.10 and see the Store now. After a couple of tries the touchscreen is working perfectly. I'm learning a lot, but I've got a long way to go until I'm competent with this stuff.
[BLISS ROMS Development] electrikjesus:
You do realize there's a new ipts release a couple posts back, with play store
[BLISS ROMS Development] cosmy032:
I tried to install Bliss OS 11.10 on my Q702 Fujitsu.

If i try to boot Live it's works without problems, if i tried to install on HDD same thing it's working.

But when i try to install alongside Windows 10... i can see in GRUB only Bliss OS

I tried with UEFI and Legacy...same thing.. I tried to install from Windows with " Androidx86-Installv26.0003.exe " and after install my device dosen't boot anymore.. ( Bootable device was not found or it's boot but only in Windows, i tried to make a Auto update from Bliss OS now i can se in GRUB both Windows and Bliss OS but when i tried to boot on Windows coming every time "Preparing Automatic Repair" and after i have oprion only to restart..)

I tried to:

1. Install Windows 10 ( 2 partition - 1 x 80 GB for Windows and 1 x 570 MB for System (this is automaticaly created) )

2. After Windows is installed and boot i go in Bliss GRUB

3. Bliss Install

4. I make a 35 GB partition (ntfs or ext4)

5. Click to install on this partition

6. Yes for format, Yes for install GRUB, Yes for read-write and after it's starting to install ( i don't have this option to choose where to install GRUB )

7. Reboot

8. It's boot automaticaly in Windows or i have GRUB but only with Bliss OS.. :(:(

Can someone help me with this dual boot step by step please ?
[BLISS ROMS Development] xV3rsus:
Hi electrikjesus, First of all I would like to thank you for everything you do for the community. I would like a great help from you.

Last year I tried to install a build for my Surface Pro 4 but unfortunately the touchscreen didn't work and I immediately abandoned the idea of ​​putting a dualboot.

Now I have returned to the office and read so many pages before looking for a possible solution.

I tried several builds in the "Surface IPTS builds - Pie" section exactly v11.10 and v11.6 but the touchscreen still doesn't work.

I have read the specific instructions for the Surface model in which it explains to manually install the firmware for the Surface Pro 4 but unfortunately, having bad English, I have not understood the paths in which to put the files, the command to give in the shell and in addition I don't see any request for superuser permissions when I start the shell (maybe because I started the Live version without installing it?)

Could you explain to me which build of any Android version works quite well on a Surface Pro 4 and maybe explain step by step the steps to install the additional firmware to make the drivers work?

I would be infinitely grateful if you answered me, you would give me a nice Christmas present! Thanks in advance!:laugh:
[BLISS ROMS Development] KKJdrunkenmonkey:
Yes, hence my edit which you quoted. :)
[BLISS ROMS Development] M47Z:
Ok I figured out the screen orientation thing, thanks for showing me the way! Created a pull request, was my first one ever, I hope I did everything correctly. Slightly ot: Where is the upstream for this / is there one? Because the same bug happens on all Linux distros I tried.

Now back to the keyboard dock: I have not solved the issues but got some more info that might be helpful.

First of all: I was wrong! It does NOT work on Ubuntu. It has been a while, I guess I remembered it wrong. But it DOES work with Fedora 31, both keyboard and touchpad.

It seems like keyboard and touchpad are integrated into one usb device: ITE Device(8910) by Elan (Vendor: 04f3 Device: 0400).

http://www.linux-hardware.org/index.php?id=usb:0b05-1869

Note: Mine has a different vendor/device id, but the same description.

This is how far I got. Can't figure out how to load the two correct drivers (hid-core and usbkbd?) for the subsystems (?) of this usb device. Really don't know anything about that stuff, just trying to learn on the way...

I attatched lsmod output from blissos, as well as lsmod output and lshw output from fedora. Does this maybe tell you something I can't figure out? Any hint on how to go on is welcome!
[BLISS ROMS Development] rech67:
"Bliss-v11.10-20191214" version can't be possible to rotate the screen, but "Bliss-v11.10-20190901" can.

Device：GPD win2

CPU：Intel m3-7Y30

GPU：Intel HD Graphics 615

Thanks !!
[BLISS ROMS Development] KKJdrunkenmonkey:
Someone else reported that rotations were off by 90° for them. What happens if you try changing the dropdown?
[BLISS ROMS Development] rech67:
I tried the auto-rotate button and the result is the same.

(My device does not have a G-sensor.)
[BLISS ROMS Development] M47Z:
The included app to rotate the screen is pretty old I think. So first I would try some other apps (like this one: https://play.google.com/store/apps/details?id=org.crape.rotationcontrol&hl=en_US but there are a few) to be sure it is an actual issue with the os.

EDIT: I just saw that the build it worked on is only three month older, same android version... this makes me think my suggestion won't help, but I'd try it out never the less.
[BLISS ROMS Development] electrikjesus:
I'll get your pull request merged once I'm back at my development machine later this week. As for the other things, I will have to take a look into it and get back to you.
[BLISS ROMS Development] electrikjesus:
There's a firmware update I pulled from Android-x86 project in the latest, so maybe that has something to do with it. Or use the included Set Orientation app and lock it to Landscape or Portrait mode with that
[BLISS ROMS Development] KKJdrunkenmonkey:
Not the auto-rotate button. The dropdown shown in your photograph. Even though it's sideways it's still a dropdown which may allow to select the rotation, what happens when you try to change it?
[BLISS ROMS Development] xV3rsus:
Is there a build that works pretty well on Surface Pro 4? (Without touchscreen problems)