yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] DellKyle:
Installs on Dell Inspiron 5559

Build used: Stable Version 7.12

Kernel: 4.9

Minor Issues:

1. Bluetooth just turns off by itself.

2. Some applications and games do not run.

3. Applications are not forced to run in landscape mode and run in portrait mode even if Rotation is locked.

4. SuperSU cannot be updated. Tried updating it but always update failed. And can't flash ZIP as this laptop does not have any android recovery, it relies on the windows UEFI to start. But i could be wrong.

5. Also, this laptop has 2 graphics chip, running some hardware info app shows that only the weaker of the 2 graphics chip is used, Intel Graphics (for Normal use) vs AMD Radeon R5 (usually used for Gaming). Driver for the better chip is absent?

Questions:

1. Important - I think the stable version 7.12 with Kernel 4.9 is a good ROM for my laptop to START with. I have installed a lot of games and have enjoyed using a very big screen and keyboard to use. However, If I would want to TEST other builds of this ROM, like Nightlies or the Bleeding Edge, what do I do?

a. Do I repeat the install procedure? Effectively losing all the apps and settings I have done with the current ROM? Or can I save it by saving Data.IMG in another folder in Windows?

b. Different ROMS and VERSIONS will have different files placed in the UEFI partition right? or do they differ only in the AndroidOS folder?

c. If I encounter problems with the new ROM and want to get back to the old one, will reinstalling the OLD ROM then copying back its SAVED DATA IMAGE bring back everything? Including all APKs that have already been installed? To save time.

2. Can someone help me with Mobile Legends? it is stuck at Name Entry screen, would have been so cool playing Mobile Legends with keyboard and mouse.
[BLISS ROMS Development] mumer012001:
BlissOS x86 32Bit Latest Version

Hi [MENTION=928479]electrikjesus[/MENTION] ! Please give me the link to download the BlissOS x86 32 Bit Latest Version.Thanks
[BLISS ROMS Development] mumer012001:
Error While Installing

Hi [MENTION=928479]electrikjesus[/MENTION] ! When i tried to open the UEFI installer it gave me error :

Not all system requirements are met Please check installer log.

The log file says :

================Installer Info================

Installer Directory:C:\Users\Mansoor Laptop\AppData\Local\Temp\RarSFX0

Installer Version:2.6.0.0

Secure Boot ... Not Supported

Manufacturer: Hewlett-Packard

Model: HP EliteBook 8440p

Product: 172B

BIOS info:

HPQOEM - f

Available GPU(s):

GPU: NVIDIA NVS 3100M

=============[REQUIREMENTS CHECK]============

Administrator privilege ... ok

CPU Architecture: 9

CPU Name: Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz

OSVer: Microsoft Windows NT 6.1.7601 Service Pack 1

Windows Security: Access NVRAM Privilege ... Not All Set

System Firmware: Other

==========================================

What is solution to this???
[BLISS ROMS Development] mweitzel2005:
IPTS update and Surface Pro 4 (pre-2017)

OK, so here is what I did in order to get touch to work on my Surface Pro 4 using the following ISO file (am sure there are more efficient ways of doing it [if you know one, share it please]):

Files used (may differ for your hardware, only tested this on a pre-2017 Surface Pro 4):

- ISO file: Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180803-1436_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_dev-kernel.org

- IPTS update files: ipts_firmware_v78.zip

Steps:

1. Boot into Windows

2. Mount the ISO file

3. Launch the install BlissOS using the Android installer

4. After successfully installing, verify that BlissOS is working (without touch at this point)

5. Copy (or download) the IPTS update file from Github into the Download folder

6. Install an Android file manager with Root support of choice (e.g. FX which I used)

7. Extract the IPTS update files into a new folder in your Download folder on Android

8. Boot into Windows

9. Mount the ISO again

10. Open the system.sfs file from the root of the ISO folder with 7zip

11. Copy the system.img file from 7zip onto your desktop

12. Move the system.img file from the desktop into the C:\AndroidOS folder (this is the folder you selected to install BlissOS into)

13. Rename the system.sfs file in the C:\AndroidOS folder to something like system.sfs.old

14. Boot into BlissOS (still working without touch)

15. Using your file manager, copy (or move) the file from the IPTS update file into the folder /system/lib/firmware/intel/ipts (take note of the exact file names)

16. Start the Android Terminal Emulator (came pre-installed with BlissOS)

17. Issue the command su - to elevate your user privileges to root

18. CD into the folder /system/lib/firmware/intel/ipts

19. For each file copied from the IPTS update archive issue the following command: chmod 644 <filename> (maybe you get away with issuing something like chmod 644 * in that folder but that is not what I did)

20. Reboot and confirm that touch is now working.

I know nothing about SquashFS, so there is probably a way to package this update again as a (much) smaller system.sfs file. If you know how please add the instructions below.

I hope this will help somebody else to get it working on their Surface.

Update:

In the spirit of full-disclosure... I do experience that touch does stop working after some use. Reboot 'fixes' this again. So maybe somebody else has got a more permanent solution or version of this 'recipe' they care to share.
[BLISS ROMS Development] ElfinJNoty:
Disable secure boot in uefi

---------- Post added at 09:01 PM ---------- Previous post was at 08:57 PM ----------

Disable "Secure Boot" in your machines UEFI/Bios

While you are at it, make sure from within Windows that you have Bitlocker disabled, and Fast Startup disabled
[BLISS ROMS Development] mweitzel2005:
Full disclosure

I do experience that touch does stop working after a while which is fixed by reboot. So not sure whether there is an improved 'recipe' that does not suffer from this.
[BLISS ROMS Development] XRed_CubeX:
Hi, when bliss os PIE will be released？
[BLISS ROMS Development] ElfinJNoty:
There's a Pie in the oven.

Until it's done, there will be no further development on Oreo or any further Oreo releases.

There are now several users who have offered suggestions on how to resolve. Read through the last 20 or so pages of posts if you wish to find them

---------- Post added at 09:14 PM ---------- Previous post was at 09:02 PM ----------

When it's ready

You are breaking an XDA rule by asking for an ETA. Stop breaking rules.

Is it really that difficult to believe we would share an announcement once it is ready?

Please don't reply to this. You are already annoying our team.

In the meantime, anybody who is able and willing....

Our Team's lead developer's laptop died and we as a team and hopefully via some contributions from users, are trying to raise funds to help him purchase a replacement. Of course, donations are not required at all and will not guarantee anything. All we can do is request. That said, development has slowed until we can get him a device to dev on. Other teammates are still dev'ing and working towards BlissROMs & BlissOS release. But, progress has slowed.

Contributions are always welcome. Patience is expected.
[BLISS ROMS Development] PaulXDA2Orig:
Device: Dell Inspiron 5559

Android Version: Nougat 7.12 x86_64 Stable Version

Kernel: 4.9

Just trying to help:

1. When using the very easy windows installer method, sometimes it fails, or install fails. Reason being: 'Mountvol z: /s", windows cannot mount your UEFI partition.

Solution:

a. Rinse and repeat - Run the installer again, Clean or Remove the failed install, then Run the installer again. It worked for me twice in different laptops, I cannot explain what happened but somehow in the 5th or 6th try, Mountvol can now mount the UEFI partition, maybe Saturn is aligned with Jupiter on that time so it mounted.

b. Disable Secure Boot - then Run the installer again. This sometimes is needed only when you cannot see the boot choices during startup and the machine boots immediately to windows.

c. Disable UEFI - or turn it off, making your laptop boot like an older version which SEEKS bootable materials from floppy, cd rom, usb, etc. Then Run the installer again.

2. Know how to manipulate your BIOS, before undertaking a possibly laptop breaking endeavor like installing an Android OS, if you even dont know how to manipulate your BIOS or even access it, dont proceed. Even though installing Android OS wont actually destroy your laptop, the boot sequence or some random error could happen in the UEFI partition which will result in your laptop not starting anything at all and if you knew what you were doing, it could be as simple as pressing F2 or DEL button to fix that, but since you had no idea what you were getting into in the first place, you would develop headache first before knowing the solution, sometimes a painful learning experience. So learn to ride a bike first before zooming on that Honda 750CBR.
[BLISS ROMS Development] XRed_CubeX:
Sorry for violating the rules, I thought it was allowed.
[BLISS ROMS Development] ElfinJNoty:
1:

a. this step should not be needed on a first time install. An error related to Mountvol = error mounting the EFI partition. This is usually caused by a previous install being present. So, if you have previously installed Remix or Phoenix or a build of BlissOS... then yes, you will need to "Cleanup Android" first to remove anything present in the EFI related to Android. The installer is designed to not be able to damage anything. So if it detects an existing install, it will abort installation and revert any changes it has made up to that point

b. it is a requirement for the installer to work and for your machine to be able to boot Bliss OS that Secure Boot be disabled. Also required: disable Bitlocker in Windows if enabled and turn off Fast Startup

c. the windows installer is for UEFI devices only. disabling or removing? followed by a reboot will not result in success with the Windows installer

2:

yeah... pretty much. UEFI is not a partition though(I think you mean EFI, which is where bootloaders live on your machine) Grub, for example, is written to the EFI. That is the process of "Mountvol Z: /S" where Z: is your EFI partition and /s is the volume label Windows is attempting to give it temporarily so it can be manipulated from within Windows. Z: or the EFI is not accessible by default from within the Windows File Manager specifically so user interaction cannot damage the Windows installation being able to boot.

The rest you got pretty much perfect. Should not be doing any of this if you don't even know how to get to your Bios/UEFI. In fact, depending on the machine, you often need to go into your Bios/UEFI and change the "boot order" so that AndroidOS is set to be first, which will launch the Grub Bootloader when you restart the machine, instead of the default which will be the Windows Boot Manager. And if you experience a failure to boot to BlissOS: go back into Bios/UEFI and put Windows Boot Manager back into the 1st spot, save changes and exit. Then when you reboot you will go directly into Windows again.

Much/all of this info can be found by reading the OP and it's following posts. We expect people to read, and to be familiar with their machines and the basics of a Bios/UEFI, and are confident any questions about the basics can be discovered via simple search methods(Google is everybody's friend). But we understand for various reasons, it is a struggle to get people to make sure they are educated on what they are doing before they do it. Therefore...... thank you for your post as a reminder :good:

We definitely appreciate users helping users. That is the way a forum, especially an XDA forum, is intended to work:good:

---------- Post added at 12:59 AM ---------- Previous post was at 12:50 AM ----------

I dont mean to pick on you, trust me you are not the first to ask for an ETA. But this serves as yet ANOTHER example of why it is important to READ THE OP AND IT'S FOLLOWING POSTS

it is 1 of the very first things we say in the OP
[BLISS ROMS Development] mweitzel2005:
Loss of touch functionality on SP4

I've tried this and run it under "su -" in the bundled Terminal Emulator.

The first command does not echo anything back (no error or other feedback), the second command returns "SELinux: Loaded file_contexts" but does not restore touch functionality for me.
[BLISS ROMS Development] Eljay227:
Touch not working on surface pro 2017

Surface pro 2017 i5 4gb ram. How do i update the firmware manually for the bliss os? It works now with mouse and keyboard only. Please advice if possible with links to recommended android rom or the version number and link to firmware and instructions on how to manually update. Thanks a bunch in advance.:cowboy::D
[BLISS ROMS Development] xhamadeex:
How did you type the commands exactly? Because it worked for me. First, make sure that the android version you installed is rooted. Then type:

Su

(Hit enter)

Command one

(Hit enter)

Command two

(Hit enter)

Try a different emulator if it didn't work.
[BLISS ROMS Development] unicav:
I have been trying to get this working on a Dell Venue 8 Pro 5830 (Yea, sorry ...Baytrail...constantly trying to get some better use out of it)

Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180803-1436_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_dev-kernel.org - Won't start Android

Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified - This one booted live and seemed to work OK other than the expected fails at startup and no sound.

So I went through the install process, wiped my entire C drive to ext4 and installed. Now when I boot it says hard disk not found???

I went through the install again, using GParted to redo the drive and format ext4 then not allowing the install to format. Again seemed to install completely but on reboot I get the same error.
[BLISS ROMS Development] AllanJacques:
I'm wondering if we could build this commands as a script and map volume button long press to execute it so we would have touck screen back in a pinch...

I don't know how to create scripts but I would love to try this out...
[BLISS ROMS Development] xhamadeex:
I thought of the same thing. But I dont know how it can be done. Maybe someone can post the script for us.
[BLISS ROMS Development] bfmetcalf:
I would think Tasker could be used for something like this
[BLISS ROMS Development] PaulXDA2Orig:
Im trying to install ADFREE. But it needs to flash a zip to easily create symlinks for hosts. Is there a way to flash a zip file in Androidx86? I dont believe we have a TWRP recovery for flashing zips. Suggestions please?
[BLISS ROMS Development] ezzony:
Hi soz for noob questions.

I have just installed 7.0 x86 on my old PC dual core connected to my TV and running very well. Just one problem, some apps rotate the screen. I have played with the rotate settings in the quick settings and in Settings>Display but I can't seem to lock the rotate and I have to reboot to get it back to normal view. What's the best way to fix this. And one other thing - is normal view Landscape or Portrait for use on TV screen?

And while I'm here, although my CPU is 64bit latest Oreo build won't boot. PhonixOS 64bit won't either and I believe this is because my CPU is missing some instruction sets. Would this more likely be the reason Bliss 64bit won't work for me either.

Oh, and is there a way to boot to my TV instead of to my dual monitor instead of having to plug the cable out of the graphics card to my monitor?
[BLISS ROMS Development] unicav:
Still trying to get this to work on my DV8Pro. After recovering the drive with a Win10 installer I was able to reboot with Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified and run as before. Did the install directly over the Windows partition and it boots and begins the startup wizard. After the expected errors with Google Play service stopping it finally came up to the Wifi. Connected to my network and immediately reboots. Tried skipping that step and does the same thing. Also getting android.process.acore has stopped repeatedly.

Any help or suggestions?
[BLISS ROMS Development] electrikjesus:
It's happening...

https://xdaforums.com/bliss-roms/bliss-roms-development/bliss-os-pie-beta-preview-t3855917
[BLISS ROMS Development] XRed_CubeX:
Hi, I installed this android Pie beta in dualboot with Windows and when I restart after installation it automatically starts Windows without asking whether to start windows or bliss os.My bios is legacy.
[BLISS ROMS Development] liskam:
Does the ipts 10.1 version support the New Surface Pro(2017)?
[BLISS ROMS Development] TeamPrimeOS:
Hi

I think you should try this link

https://xdaforums.com/bliss-roms/bliss-roms-qa/guide-how-to-setup-dual-boot-legacy-pc-t3802027
[BLISS ROMS Development] wenna.speedy:
Beta pie stuck on boot on asus t101ha
[BLISS ROMS Development] ElfinJNoty:
Go into bios and select AndroidOS as your first boot option to launch the Grub bootloader on reboot

---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------

For compatibility with ipts devices, the new Pie beta build with ipts kernel will be available soon

---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------

We have discussed this before

You are using a Windows installer .exe that says clearly UEFI ONLY

Legacy boot will introduce further variables to your boot process that will likely not be compatible.

If you must run legacy bios, follow the instructions in OP for a manual install.

And please do not post here about Pie releases.

There is a new separate thread for a reason
[BLISS ROMS Development] XRed_CubeX:
I burned the iso on a usb stick,and i installed bliss os,i know the differences legacy and efi.Sorry for my english,i am italian.
[BLISS ROMS Development] electrikjesus:
Please use the Pie thread for all questions regarding that build
[BLISS ROMS Development] XRed_CubeX:
okay
[BLISS ROMS Development] maysider:
Hi, I haven't found it so how to update to a new version without losing all my android settings in VirtualBox? thx
[BLISS ROMS Development] electrikjesus:
Simply by replacing all the .img files with those from the updated .iso
[BLISS ROMS Development] trev10232077:
Just installed 11.1 on surface pro 4 and touch is not working at all. please help as i was under the impression that touch works with the newest builds.. thanks
[BLISS ROMS Development] electrikjesus:
For the third or fourth time (between a few platforms), these are NOT for surface devices, and there will be no surface releases until I am able to test them. Thank you for using the Pie thread too
[BLISS ROMS Development] electrikjesus:
All Bliss OS 11.1+ Pie related talk should go here: https://xdaforums.com/bliss-roms/bliss-roms-development/bliss-os-pie-beta-preview-t3855917
[BLISS ROMS Development] maysider:
And install again like from the beginning? Will it optimize all the already installed apps to the latest version of Android like a common Android update does through OTA?

thx
[BLISS ROMS Development] ElfinJNoty:
No

Data.img from one Android version will not work with an install of another Android version. Can't mix and match.

You can however, retain your data.img between different installs of the same Android version, no problem. Just replace system, kernel, ramdisk, initrd

We have been working a way to integrate an OTA update process, but nothing at this time. One of many ideas/plans we have piled up
[BLISS ROMS Development] wenna.speedy:
I just tried last android x86_x64 version (new oreo rc2) and I can say to all cherrytrail/bay trail users (asus t101,t102 etc...): old problems were solved - sound,brightness, but touchscreen doesnt work. does anyone know how it repair?
[BLISS ROMS Development] ElfinJNoty:
https://xdaforums.com/bliss-roms/bliss-roms-development/bliss-os-pie-beta-preview-t3855917

This is latest build, and a preview of Pie which will be only version of Bliss being developed moving forward. Please give that a try for compatibility test. Touch should also be working
[BLISS ROMS Development] wenna.speedy:
Just tried.Stuck on boot screen on asus transformer... :/
[BLISS ROMS Development] Ciscke:
Did someone managed to install Netflix?

I have a Surface Pro 3, of course due to the root the app is not available on the Playstore, but I can't find a working apk.

The app gets installed but when I try to open it, it crashes.

Is there a particular procedure that I can follow?

I searched on Google but didn't find anything.

Android version 7.1. 2

Kernel version 4.9.31-android-x86_x64
[BLISS ROMS Development] liskam:
is there any possible to update the touch screen driver manually for surface devices?(i mean bliss 10.1
[BLISS ROMS Development] AltracasysHC:
Tried the Bliss-v10.1-Beta-android_x86_64-OFFICIAL-20180803-1436_k4.16.8-ipts-blissified-ath_18.1.0-devel_w14_dev-kernel.org.iso on my surface pro 4 , touch doesn't work:(
[BLISS ROMS Development] liskam:
and hi,is there anyone tried to install it on ext4 drive?

i would like to create a bootable usb stick and able to take it everywhere

but grub cannot be installed on the ext4 drive (i dont know much about linux

fat32+uefi installer is great but only 4g data.img:(

how could i make seperate data.img or uefi-bootable ext4 usb drive?

thx
[BLISS ROMS Development] bfmetcalf:
You need a fat partition for grub. Like 512 Mb for grub and the rest ext4 for Bliss
[BLISS ROMS Development] vladnovski:
which one has pre installed octopus and will work on intel laptop? thank you.
[BLISS ROMS Development] AllanJacques:
What does octopus do?
[BLISS ROMS Development] ElfinJNoty:
Pie beta preview. Installed by default.

Yes, an "Intel laptop" should work :rolleyes:

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

Button mapping

---------- Post added at 02:42 AM ---------- Previous post was at 02:35 AM ----------

A Reminder:

This thread is for Oreo builds.

A new thread has been opened for Pie:

https://xdaforums.com/bliss-roms/bliss-roms-development/bliss-os-pie-beta-preview-t3855917

Oreo development is done. No further builds or updates and/or fixes will be provided for Oreo. All dev efforts have moved on to Pie. Please move onto and follow the Pie thread in order to #StayBlissful
[BLISS ROMS Development] liskam:
Thank you!

Does this method support UEFI Boot on surface?
[BLISS ROMS Development] bfmetcalf:
I should be fine. I use it on my Dell laptop with UEFI.
[BLISS ROMS Development] elcidroyale:
How do I get my volume and brightness hotkeys to trigger volume and brightness in Bliss OS on my laptop?
[BLISS ROMS Development] mike2587:
I created an USB Bliss image (BlissOS 7.2 stable) and installed successfully on my hd (on a new partition formatted as ext4), I created then the entry with EasyBCD as suggested in this thread, changing the hd number, but when I choose the Bliss entry in the boot menu i got the "Error 13, invalid or unsupported executable format” message. Can anybody help me?
[BLISS ROMS Development] brokenworm:
how can you call the "stable" roms stable when not even wifi works without fraking op on heavy load and a reboot is needed to get it working again ?

i havent seen ONE stable rom for years .. and the roms u have is all from android-x86.org u just add some non working things in it "useless task manager for example" ! and now u throw away a UNFINISHED project to start over with android 9 to do an unfinished job on that one to ? ? i dont get this ! not even the mouse can press the buttons directly on the new builds .. thats just nogo :D hahaa
[BLISS ROMS Development] liskam:
Thanks for ur solution！

Sadly i dont know how to install grub to ESP partition in Windows 10...Could u explain it？thx！
[BLISS ROMS Development] bfmetcalf:
I can't help you there. I don't run Windows at all and don't really know anything about how Windows does things. I run Linux on everything.
[BLISS ROMS Development] electrikjesus:
Kindly try using hardware that actually works right on Linux before blaming your problems on someone else's project.