yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] ElfinJNoty:
You are free to test yourself. Results and feedback are welcome, once you have results to share.

Without the IPTS modules built into the kernel at build time, it may not work. However, we have seen folks not read before just installing things, and they were able to boot a SP4 with non-IPTS builds, I can't recall their end results.

Results may vary, but give it a go. As you already noted(well done for reading ?), utilize the Surface device section in the OP

FYI No support will be provided for old Oreo build installs

---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------

You may test on Oreo build if you wish, but those builds are old and have not received any of the modern work done on Pie development. Those builds are considered deprecated and will receive no support from Team Bliss. We leave them available for those willing to test and troubleshoot on their own.

What USB audio device are you attempting to use? And does it work for you with a Linux distro installed/live booted?
[BLISS ROMS Development] KamaL:
Thanks

So I tried the latest 11.9 build

After struggling to load it due to BitLocker protection issues and having to insert the BitLocker code maybe 10 times (no idea why), I was able to load it as a live CD.

Obviously, screen touch, power button and volume buttons don't work, but the problem is that it's extremely laggy and I couldn't even install the ipts firmware.

Is it because I'm running it on a USB?

How should I access the root folders for copying the correct firmware?

Thanks
[BLISS ROMS Development] ElfinJNoty:
You don't "install" the firmware, you copy and place it in the appropiate directory. But that is intended to be done on a direct install, not as a Live boot bandaid.

When you install directly to onboard storage, you will be given an option to install with full read/write privilages of /system. You need this root access in order to place the firmware files.

Live Boot is our recomended way to ensure your device will boot the OS. Is not intended to be used beyond that in live boot. Performance will definitely be better on a direct install versus running off of a USB. But laggy? This could be due to running from USB, or various other possibilities. Best to do a direct install, grant full r/w, and then you'll be able to manually place the firmware files.
[BLISS ROMS Development] KamaL:
Ok. I understand.

I disabled BitLocker on the device and all other security issues, but BitLocker keeps asking the recovery code whenever I reboot to windows. Any idea why? I wanna be sure I can fix it before I install the build
[BLISS ROMS Development] ElfinJNoty:
You should have secure boot, bitlocker, and "faststartup" disabled in Windows/UEFI

Cannot advise about why bitlocker keeps asking for a password. I'd assume, because it isn't truely disabled. There may be something device specific between MS and your device's oem. We aren't Microsoft, or your particular device's manufacturer. That is who/where you should seek help with that. All I can say for sure is: it has nothing to do with BlissOS or our installation procedures.
[BLISS ROMS Development] electrikjesus:
:cool:

I remember having to start the process to disable bitlocker from within windows 10 on my old Surface Book. That may be the part you're missing there
[BLISS ROMS Development] beboxed:
I also had an issue where Windows 10 kept on asking for the recovery code. This was after I installed a Linux distribution on my SP6 which altered the EUFI boot menu/sequence. What I did to solve it was to boot into the recovery console (a recovery key needs to be entered) and disable (suspend) the encryption, I think the command was:

manage-bde -protectors -disable C:

I was then able to boot into Windows 10. Then in Windows I re-enabled Bitlocker again:

manage-bde -protectors -enable C:

From there on booting went totally fine without Bitlocker asking for the recovery code anymore.
[BLISS ROMS Development] Manxete:
Hi all...

I'm following this forum for some months and never need to ask a question until now. I have an issue with Bliss Os.

I downloaded this version Bliss-v11.9--OFFICIAL-20190525-2025_x86_64_k-k4.9.153_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org.iso (1.4 GB) and installed it on a MSI laptop. I installed this Os in a HDD partition with Windows 10 dual boot. All seems to work fine. The system starts well and I can use it without any problem. The BIG problem for me is when I try to play games. The games load correctly but the mouse dosn't works well. Some examples:

Game The Walking Dead No Man's Land. I can't click on messages ingame. I go to OK button with mouse and click it, but nothing happens.

Game Marvel Strike Force. I can click on menus, but when I click on screen and move to left or right to move the main game screen, nothing happens. I move the mouse but the screen doesn't move.

Game Rise Of Kingdoms. In this game, I can move the screen with no problems, but when I click on the buildings to interact with, nothing happens.

And i also can't use the zoom in games.

I tried 3 or 4 more games, and i have different issues but all of them related to the mouse. I think it could be a problem with mouse buttons mapping or something like that. But I look all the menus and I can't find any menu for change button mapping...

Someone with similar isuues? Any solution?

Tanks all!
[BLISS ROMS Development] ElfinJNoty:
Is because those games are designed to be played on a mobile device with touchscreen input. Not in a desktop environment with a physical mouse and keyboard. You should contact the game developers and ask them to include support for use of a mouse and keyboard as an alternative to touch only input.

This is a "games" issue, not an issue with Bliss OS.

There are many keymapping solutions available for download via the web, or from PlayStore. Some paid, some free, all with different levels of features and settings.

Some games are able to detect these types of instances running on a machine which has alternative input methods. We've heard of users being banned from PUBG Mobile, for example, for using keymapping to gain an advantage over other, normal, Mobile version players. <~~~is why we do not include a keymapping solution by default within the OS.

You can search this thread for "key mapping" or utilize a web search provider of your chosing "custom key mapping Android"

Should yield an abundance of results for you ?
[BLISS ROMS Development] Manxete:
Tanks for answer so quick...

I ask for any solution because before try Bliss OS I used anothers Android OS like Remix OS and Prime OS in the same laptop and I never had this kind of issues. All games works well. I changed from other Android OS to Bliss OS because it's Android 9 and it's more stable than others. I looked on google for solutions and i don't find nothing... I'll try to look for "custom key mapping Android" like you said...

Thanks All!
[BLISS ROMS Development] electrikjesus:
The other thing that might be going on here is mouse support in Android Pie has changed, so that also might affect games that seem to operate differently in older versions of Android. Since we don't alter the way AOSP uses mouse input yet, there's not much else we can do there.
[BLISS ROMS Development] electrikjesus:
docs.blissroms.com is live!!

We've been hard at work, preparing for quite a few changes within Bliss as an organization, and part of those changes started to roll out this week!! We've gone live with our documentation site, and as it is just starting, it already allows us to convey all the required information in a much nicer way than the instructions we provide on our thread templates. This should also open the door for contributors to add their knowledge to the mix too, as everything can be found on our GitHub (https://github.com/BlissRoms/Documentation), and our Gerrit page (review.blissroms.com) should also make adding things to it a bit easier too.

From this point forward, we will be shifting to using this site for the instructions for Bliss OS, as we have exceeded XDA's character limit (by a good 3000 chars) on that post, it is a good thing our own site doesn't have one.

BlissROMs Documentation Site - Bliss OS sectioned:

https://docs.blissroms.com/Bliss OS/installation-guide
[BLISS ROMS Development] Manxete:
Thanks for answer...

I didn't know that mouse support in Android Pie was changed... I think I will try to download the last version of Bliss OS based on Android Oreo to see if this one works well with games... It will be better than try to use a program for remaping buttons in Android...

Thanks All!
[BLISS ROMS Development] ElfinJNoty:
That is a backwards way of thinking, and may not yield the results you desire. Also, no support will be provided for non-Pie builds, as those do not include any of the development that has taken place in the past year. You may be seeking 1 resolution for gameplay experience, and introduce a whole new amount of compatibility issues or bugs that haven't been addressed in over a year(the last time we compiled Oreo).

Do as you wish, please just have a proper understanding of the route you chose. And please do not report your Oreo experience and findings here, as this forum is intended for development of Bliss Pie.

Thanks,

#StayBlissful
[BLISS ROMS Development] Manxete:
Thanks for answer.

I undertand and I'm agree with your answer. Maybe I don't explain myself well... I'm not english, and somtimes I have some problems to explain me. Now I have 3 Android OS installed in my laptop and I'm testing its to find the better for my use. The only reason for try Oreo is to see if gameplay works well or not. Of course I'll try to find a way for play games with Pie. In a previous post I say that Bliss Os Pie it's the most stable of all and I would like to keep it.

And of course I will not report any issues with Oreo in this forum. I know this is a Pie forum...

Thanks All!
[BLISS ROMS Development] electrikjesus:
Bliss OS (x86) has always been a spin-off from Bliss ROM, so the majority of the team works on the ROM for Android devices, and then I end up taking that, and adding all the needed commits from Android-x86 Project, Intel's Project Celadon (Android-IA), as well as a couple others, and do my best to make it work on as many PC's as possible. I do get a little help on the x86 side here and there, as well as help in this thread and the chats from a few more Bliss members. But every year get's harder and harder, and every year, there are less and less people working on doing the same thing we are for PCs.

I have to admit, this past year has been a ghost town for open-source work on "Android for PC" projects, Instead of having 4-5 people across the globe I can turn to and ask questions, that number is now down to 1-3... Making things much harder for me personally, because I'm still learning it all.

This project, as well as Android-x86 project are in dire need of community contributions. I know we can't be the only ones that sees the true potential of Android on PC hardware, and I refuse to just stop working on the projects too. I feel that potential is worth fighting for.

So I would like to ask you all to help our projects out by spreading the word. Introduce the geeks in your circles to Bliss OS as well as Android-x86, and show them why you think it's worth looking for people to help chip in a few hours of free time to improve these projects.

Just a couple commits here and there can mean the world for a guy like me. I'm not after $$ in this at all, I'm only seeking to help make a change for the better ;)
[BLISS ROMS Development] electrikjesus:
Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01

!! Please remember to not quote these update posts, or any of the OP's !!

OK, many of you have asked for Bliss OS - Pie to work with 32 bit bootloader, so I've revived the x86 builds for Bliss OS as an experiment to see how far we can get things going. Please do not expect this to be stable. And please do not complain if this is the case. This is a development thread, so if you choose to say anything, please let it be constructive in some form, and be accompanied with logs, device info, full build filename, and as much information about the steps you've taken to get this far.

Thank you for understanding ;)

Cases where these might be "the droids you've been looking for":

You have an Intel Atom device with a 32 bit bootloader

You have an older Intel Core 2 Duo device with a 32 bit bootloader

You have an older AMD Athlon device with a 32 bit bootloader

You have some other odd-ball CPU that the kernel might support, and it has a 32 bit bootloader

Builds being uploaded:

Generic Builds - !! for all non-IPTS devices !!

Bliss-v11.9--OFFICIAL-20190801-1319_x86_k-k4.9.153_m-18.3.5-pie-x86-llvm80_f-dev-kernel.org.iso

Known new issues:

Navbar issues still persist when using Taskbar. Please set a fallback Gesture method in the Blissify app first, then enable Taskbar.

Sleep states aren't working right on many machines. 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/Experimental%20-%2032%20bit%20%28x86%29%20builds%20-%20Pie/Changelog-Bliss-v11.9--OFFICIAL-20190801.txt/download

Thanks, and have a Blissfull time!!

Experimental 32 bit builds - Download Folder:

https://sourceforge.net/projects/bl...dge/Experimental - 32 bit (x86) builds - Pie/

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] Castle 1401:
Thank you Elec !
[BLISS ROMS Development] ElfinJNoty:
Thank you for remembering "not to quote these update posts or the OP's!"

:confused:

And yeah... We are well aware of how few developers/contributors are out there in the Android for x86 hardware landscape
[BLISS ROMS Development] RandomDelta:
Thanks a lot devs for reviving bliss os for 32 bit devices
[BLISS ROMS Development] GOOGLE_USER:
TROLLING?

And immediately... BAM! You do just that.

Then this...

So, to bring you up to speed, THOSE developers have abandoned their project to focus on industrial-grade lubricants & adhesives.

Why not SLIDE over there and STICK to their thread with inquiries not related to

Bliss OS

, if you question the veracity of my statement?

Clearly you know where it is located:
[BLISS ROMS Development] Castle 1401:
Im sorry . I was too exciting and annoyed there. Im really sorry. How can i delete these quote. I cant figure out the way

Once again. Im so sorry
[BLISS ROMS Development] GOOGLE_USER:
live & learn

You've erred and apologized. Certainly you can be forgiven.

To excise unneeded portions of text you are quoting you need only delete said portion.

This can be accomplished retroactively, too. So, no worries. Just click "Edit."

Be certain to leave the bracketed quote designators intact.

[*QUOTE=Member name xxxx, xxxxxxxx] <<--begins with... ... ends with-->> [*/QUOTE]

MINUS THE ASTERISKS - I had to include them to prevent it from actually posting as if it was a quote.

:good: :)

Also, I would advise all members to utilize the "Thanks" button located at the bottom of the individual's post where you wish to express gratitude.
[BLISS ROMS Development] electrikjesus:
And the 1-3 devs reference was for the number of people I am able to reach out to. That's the amount of people that make themselves accessible to the rest of us.
[BLISS ROMS Development] fritzcola:
Hey guys i have following question. I wasnt able to install Bliss on my Lenovo YOga 730IKB, so one of you suggested me to install an older 32bit version of Bliss. I used this version https://sourceforge.net/projects/bl...0171103-1727_k4.12_oto-installer.img/download . It worked an booted but i couldnt get past the setup and installation wasnt succesfull either, which was expected. Now i saw that you just published a new 32bit version. Could this version work on my laptop, cause the one above was the only one that booted?
[BLISS ROMS Development] vadim72:
after several hours of testing, the conclusion is this.

pros

full nine with all the features

Fast, 95 percent stable.

all android applications are fast, chrome is very smart, the feeling of stability is high

minuses

system.img is not unpacked

root does not pass, although all commands pass without errors

standard YouTube does not work, no video

IPTV not working, slide show

Through MX Player online movies normally go.

Thank you so much for the test build.

* fix please two problems IPTV and root
[BLISS ROMS Development] electrikjesus:
You forgot to read the part of the instructions that explain what you need to do to the system.sfs file after installing in order to get root.

And to help with your other issues, you also neglected to provide any of the requested info for build, device, install method, etc.
[BLISS ROMS Development] vadim72:
Tell me, where can I find your instructions for passing root?

I read all the instructions and found nothing but this

When the question appears whether you want to install the system as R / W, select YES.

and I always carry out this point, I have been testing all assemblies for three years

this item does not work in your assembly, the system folder does not exit

thank
[BLISS ROMS Development] ElfinJNoty:
You can achieve full root access by unpacking "system.img" from the system.sfs

.sfs is a read only compression, and the system.img is within the system.sfs

Extract system.img, then delete system.sfs

Then point your grub to the system.img instead of .sfs

Profit
[BLISS ROMS Development] vadim72:
you are joking ? I'm not a newbie.

I make android modifications myself

I always work only with system.img

I unpacked system.img with the command

cd / system

tar -cf - * | (cd / mnt / hdd / F / tv1 /; tar -xvpf -)

to exit the system folder from under the android. and set root.

I tried RemixRoot .zip to get root.

but I did not get root, there is no script for

root
[BLISS ROMS Development] electrikjesus:
It seems as though the last recovery I performed on the instructions template dropped that info, so I have pushed a new patchset with that info included into our docs.blissroms.com site. It should show up in tomorrows updates.

In brief, If you're using USB bootable install, select Yes to write System as R/W. if you installed using the Windows Installer, you need to manually extract the system.img from within the system.sfs file.

If you are trying to extract the system image into a folder on FAT32 or NTFS, this will not work as it does in Android-x86 installs, due to the fact that there are filesystem changes for sdcardfs, which Pie defaults to mounting unknown filesystems as... It's a headache so far.
[BLISS ROMS Development] vadim72:
I understand you, I respect your team, but you also understand me

I have a feeling that you assembled the assembly and did not check.

I now have five builds on android.

I myself help users with the android settings on different devices.

I will help them install root, sound on hdmi, drivers on Wi-Fi and other equipment

on the forum

https://w3bsit3-dns.com/forum/index.php?showtopic=128559&st=21020

I asked you for help, and wrote a problem, you were not convinced that there is a problem and gave me advice that everyone knows this and follows it.

I wrote there are two things that are critical, and they do not work.

This is the installation of root and IPTV.

Yes, I didn’t write what equipment I have, because I thought it didn’t matter,

K50ID ASUS Notebook

Experimental - 32 bit (x86) builds - Pie

once again, I respect you, but I need help installing root, it doesn’t work with standard methods, I believe that the file system in system.img is broken.

you will help everyone if you lay out the root .img files separately and I will replace them then and check.

I have been testing Bliss OS 7.x / 10.x / 11.x for three years and I always advised all users of your builds, they are the best of all and I have always helped everyone, but I can’t cope here.

therefore, I ask you to lay out a working system.img and .img files with root.

thanks and I'm not arrogant
[BLISS ROMS Development] vadim72:
I got a root

Experimental - 32 bit (x86) builds - Pie

along this way

/ sdcard / su / x86

you must put the x86 folder from the archive SR5-SuperSU-v2.82-SR5-20171001224502

this was not my problem, I can post a screenshot of the log.

we get root so, if someone does not understand what is needed and what files to put in advance, I can write detailed instructions.

experienced ones will understand by commands and will find and add preliminary files themselves

here are the commands, and they are all needed for root for systems and further systems

the only way I got the root

cd /system/xbin

chmod 4751 su

mv su su.orig

cd /system/xbin

mv su su.orig

cp /sdcard/su/x86/su.pie su

chmod 4751 su

su --install

su --daemon

exit

su -i

cd /system/xbin

chmod 4751 su

su --install

su --daemon

~~~~~~~

Now there is one problem

Help

the video does not work in IPTV, you need to fix fmpeg and the buffer

How can I do it

Experimental-MOD_ROOT - 32 bit (x86) builds - Pie

https://drive.google.com/file/d/1efh0qoKa-SvWvCoHGeMT9vFxuQs_st4o/view?usp=sharing
[BLISS ROMS Development] jjm06:
32 Bit experimental version, don't work for me.

Specs:

Intel C2D e6550

Amd Radeon hd 7470

2GB Ram
[BLISS ROMS Development] MadMax0067:
Successfully installed

But every app keeps crashing

Any Solution?
[BLISS ROMS Development] electrikjesus:
I would like to remind the Bliss OS public that we will not be able to answer any posts about our 32 bit builds or any builds that do not include logs, device info, and full install details.

This is the only way that we will be able to assist you.

Thanks for your help ;)
[BLISS ROMS Development] electrikjesus:
I will be uploading another 32 bit build here soon what is using kernel-4.4, and that might support the core 2 duo better
[BLISS ROMS Development] jjm06:
E

Thanks! The Graphics is more the Problem Screenshot soon.
[BLISS ROMS Development] ElfinJNoty:
https://opensource.com/article/19/7/create-pull-request-github
[BLISS ROMS Development] electrikjesus:
Actually, turns out that I will need to redo how I'm calling the SuperSU instructions from device/generic/common/device.mk, I used to separate it into 32bit & 64bit calls, but when we moved to 64bit only, I just added the 64bit instructions only.

As for ffmpeg, that is not working right at all, which is why I use the AOSP based codecs currently. Android-x86 project usually adds those, but it's pie-x86 branches are not there just yet.
[BLISS ROMS Development] DivideDroid:
Touchscreen Not Working

Having a OneMix 3, with touchscreen not working properly