yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] franzli:
Quick feedback regarding the bleeding edge release from 18/7 on the Dell Venue 8 Pro 5855 (cherrytrail):

youtube video working now

backlight control working again!

like in the previous build, buttons are now working thanks to the 4.12 kernel

bluetooth still not working

as on previous builds something seems to occupy the CPU more than expected, but now even more than on the early May build I have currently installed (I think 0405); CPU usage is not going below 29% even when completely idle (typically between 30 and 50%) and Geekbench 4 now gives 1088 (single core) and 1904 (multi core) - the single core result is as expected, but multicore is much worse than on the older build, where I got over 3000 points

probably as a consequence of the last point, battery life takes a heavy hit, battery life as projected by Android is now only about 2 hours when idle (on Linux I get projected battery life between 8 and 10 hours when doing simple text editing); on the May build I'm using it wasn't great either, but at least slightly above 3 hours

Could you clarify whether you included the patches for the Surface 3 (non-pro) that are used in the arch package here (https://aur.archlinux.org/packages/linux-surface3-git/)?

Although I think I get bluetooth connectivity even on the vanilla mainline kernel, so the lack of bluetooth may have to do with something outside the kernel or the kernel config? The extreme CPU usage pattern is also not restricted to this device, but I've noticed that on every device I've tried Bliss on so far (incidentally also for RemixOS), so that may be something in the Android-x86 code base?
[BLISS ROMS Development] electrikjesus:
Here is the patches pulled from there: https://github.com/BlissRoms-x86/kernel_common/commit/d14485f0c7f6768c36abe4e11b55e3c7eeef5f2a Also, with the help of a couple commits from Youling, we now have bluetooth working on the newer 4.12+ kernels, so I will get those updates built over the next few days for you all ;)

As for CPU handling, I do believe that there is something not right, with every kernel, so yes, it is likely how Android-x86 has been altered to use a pure Linux kernel currently. Not sure if it has worked correctly in the past...
[BLISS ROMS Development] franzli:
Great, that sounds exciting! If we get working Bluetooth, I'll probably update to that version!

Although I'm still wondering why the CPU usage issue got worse this time around. If I can observe anything else that may be related I'll point it out.
[BLISS ROMS Development] kanttii:
Software power button / power menu

There's a power menu in the taskbar, here's how to use and access it:

https://youtu.be/FBibeje3vR8
​

Directions:

1. Go to desktop

2. Open the menu

3. Click the 3 dots button on the bottom right of the menu

4. Click power menu and choose
[BLISS ROMS Development] ubuntuh:
Hi, sorry to repeat if it has already been posted, but is there any possibility to mount the system r/w while booting from an USB without installation?

Also i have no sound on my asus x205t, is there someone who can tell me how to fix this?
[BLISS ROMS Development] franzli:
I believe electrikjesus mentioned that system cannot be mounted r/w from USB a few pages ago.

The x205t has a cherry trail soc, right? My venue 8 pro with cherry trail doesn't have working speakers either. If you get working Bluetooth (I currently don't, see above), you may be able to connect speakers/headphones, otherwise you may have to wait.

My older baytrail venue 8 pro interestingly has working sound (and they used to be as bad as cherry trail), so maybe there's hope.
[BLISS ROMS Development] Mohamed Sallah:
everyday i check this topic like 10 times :"D

waiting for ipts support
[BLISS ROMS Development] pederado30381:
Me too. Waiting for Surface Pro 4 Touchscreen support^^
[BLISS ROMS Development] electrikjesus:
I'm actually trying to run off an ipts build with patches to our 4.9 kernel. Hoping this works ;)

Would you mind letting me know the install method you used for the older baytrail venue 8 pro? I seem to not be having much luck booting mine into Bliss, but Windows is working well on it.
[BLISS ROMS Development] franzli:
Sure, although I'm not sure I can reconstruct the exact details. I'm using the 32 bit version and the installer from the grub menu of the USB stick. There is also a problem with the graphics so that you'll have to pass the "nomodeset" parameter to the kernel, i.e. when booting from USB press e to edit and then edit the parameter before or after "quiet". The same needs to be done with the installed version, so you may want to modify the grub.cfg file on the efi partition after installation to avoid having to add the kernel parameter manually every time.

Let me know if this helps, otherwise I can try and remember if there was anything else I had to do.
[BLISS ROMS Development] daspex:
hi,

thanks for the nice rom but it does not work with my device mp man 815 it seems to have identical hardware like the chuwi 8 as i read somewehre.so here is the install log.

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

Installer Directory:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0

Installer Version:2.4.5800.0

Secure Boot ... Disabled

Manufacturer: MPMAN

Model: MPW815

Product: MPW815

BIOS info:

INSYDE - 3

MPMAN.F.W86C.JLBNRBA02

INSYDE Corp. - 54470054

Available GPU(s):

GPU: Intel(R) HD Graphics

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

Administrator privilege ... ok

OS Type: 32-bit!

CPU Architecture: 9

CPU Name: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz

OSVer: Microsoft Windows NT 10.0.14393.0

OperatingSystem Version ... ok

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

System Firmware: UEFI

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

====Install Started on 22.07.2017 14:59:33====

-ISO File: C:\Users\Otzenknecht 2\Downloads\Bliss-v7.2-android_x86-OFFICIAL-20170703-1529_k4.9-ax86_wf_01.iso

-TargetDrive: C

-UserData: 2097152

-Setup Directories...

-Folder Created: C:\AndroidOS

-Extract ISO

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\7z.exe x "C:\Users\Otzenknecht 2\Downloads\Bliss-v7.2-android_x86-OFFICIAL-20170703-1529_k4.9-ax86_wf_01.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oC:\AndroidOS

-Extract SFS

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\7z.exe e "C:\Users\Otzenknecht 2\Downloads\Bliss-v7.2-android_x86-OFFICIAL-20170703-1529_k4.9-ax86_wf_01.iso" "boot\grub\grub.cfg" -oC:\AndroidOS

-Create Data.img

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\dd.exeif=/dev/zero of=C:\AndroidOS\data.img count=2097152

-Initialize Data.img

#Launch:C:\Users\Otzenknecht 2\AppData\Local\Temp\RarSFX0\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"

===Installing Boot Objects===

-Mounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /S

-Setup Boot Directory...

-Boot Directory is Already Exist

==============Revert Installation==============

-Cleaning up Android Directory ... C:\AndroidOS

===Removing Boot Objects===

-Mounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /S

Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S

Error output:

Das Verzeichnis ist nicht leer.

-Remove Android UEFI Entry

-UEFI: -1

-Cleaning up Android Directory ... Z:\EFI\boot\

-UnMounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /D

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

====Uninstall Started on 22.07.2017 15:02:27====

Android Installation Not Found

===Removing Boot Objects===

-Mounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /S

-Remove Android UEFI Entry

-UEFI: -1

-Cleaning up Android Directory ... Z:\EFI\boot\

-UnMounting EFI Partition...

#Launch:C:\Windows\System32\mountvol.exe Z: /D

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

maybe someone can help....thanks in advance
[BLISS ROMS Development] franzli:
I'd advise to install Bliss on a separate partition in any case. I think I tried installing on the windows c: drive using the windows installer at some point and never got it to work, while installing on a separate position I was usually able to boot normally. Not sure where the problem is, since it's using IMG files anyway if installing on an ntfs or fat32 drive, so those would have to be mounted anyway, but when installing to a separate partition things normally worked for me.

I'm saying worked because I have noticed that I get the best results installing to an ext4 partition using the built-in installer, i.e. the one you can choose in the grub boot menu when booting from USB. When using the windows installer, I often didn't get backlight control on the installed version, even though it was working when booting from USB. Installing onto an ext4 partition typically solved that issue.
[BLISS ROMS Development] kharnm:
Hi,

I tried to install Bliss on my Surface Pro 3 with the easy installer (new version), all fine exepted on boot, I have this message : android/boot/grldr.mbr missing

Any idea ?
[BLISS ROMS Development] electrikjesus:
Yeah, you used the MBR installer on a UEFI machine. Please use the UEFI installer ;)
[BLISS ROMS Development] kharnm:
Well, I've use the Easy Install For Bliss-x86 6.4/7.x UEFI/ESP, this one : https://www.androidfilehost.com/?w=files&flid=140019

I try again, same problem. Secure boot disabled, of course.
[BLISS ROMS Development] dapo4friends:
Hello blissinians..

Please i just wanted to ask these q's.

1. I use an infinix Hot 2 device, please might people like me be blessed with the privilege of using the blissroms or is it for One plus alone... Wish it wudnt be.....

My phone uses ARM architecture , Is 16 gb internal storage, 2gb ram, mt6580 SoC... .

2. Please how do I install a proper triune-boot Of blissx86, remix os, and windows.. .Can i use the usb to hard drive install method.....

Cos i tried installing them on windows (normal way for remix os) even though to different partitions, both didn't work (unlike when I had only remix os into windows in the past )

3. Bliss x86 seems to have issues installing as layover on windows-the easy mbr installation method (normal popular remix os install mode)... The grub boots, gets to a point, writes sth like emergency bla bla.... And restarts system....REMIX OS doesn't have this problem!!!!
[BLISS ROMS Development] bg260:
Thanks man! I'm going to try this on my Nvidia machine right now.
[BLISS ROMS Development] electrikjesus:
Logs please, cause I still think you're trying to write it over a previous install attempt

Same for you as well. We need logs, not a vague description
[BLISS ROMS Development] kharnm:
Here is the log. Thanks for support
[BLISS ROMS Development] dapo4friends:
Hmmm...OK..

But please, any help for my first two questions

..I'm really itching to try blissrom if my device can take it....:(
[BLISS ROMS Development] franzli:
Re 1: this is for the x86 version, which won't work on arm. You might be better off asking on the forum for at least a similar arm device (except if elektricjesus happens to also maintain bliss versions for any arm device, which would be a coincidence)

Re 2: Since i think that both remix and bliss-x86 use grub as bootloader, there shouldn't be a problem in principle. You may have to manually add an entry to the grub.cfg file, I suspect (for that you need to Mount your efi partition).

Installation using the USB installer should work fine.
[BLISS ROMS Development] dapo4friends:
There are blissroms for the one plus phones...I'd u check the download.blissroms.com....
[BLISS ROMS Development] franzli:
Yes, I'm aware that Bliss ROMs typically/originally are for ARM hardware, I'm just saying that this particular thread is about the PC x86 version, so you may have more luck asking about ARM on a subforum for an arm device (ideally specifically for the phone you're interested in).
[BLISS ROMS Development] dapo4friends:
In trying to install bliss x86 it may be safer to format your hard disk destination as ext4 rather than NTFS for easy identification in the bliss install menu....but it'll cost a bit more space so u may want to add about 500mb extra to your 8gb partition size

This prevents u selecting a wrong partition and losing data....

---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------

---------- Post added at 12:03 PM ---------- Previous post was at 11:21 AM ----------

Oh OK....thanks a lot, I appreciate your help....
[BLISS ROMS Development] slim6y:
Firstly, I must say thank you, this is a wonderful install.

My issue isn't with the install as far as I am aware, my issue is that I can not get my tablet to reboot (though I have not tried this on the most recent install).

In previous versions (I used Nougat from Android x86 and another version of Bliss) I can install but when it comes to reboot I end up in an infinite loop of attempting to boot android, switching off, restarting, attempting to boot android.... and so on.
[BLISS ROMS Development] electrikjesus:
Can you help us by filling in the blank spaces in the story? What kind of device, what type of install? what other OS's are installed? what OS's have you had in the past that might still have boot entries in EFI or MBR? What is the terminal output while booting? Have you tried to boot in debug mode to further inspect what's going on?
[BLISS ROMS Development] slim6y:
Hey, thanks for getting back to me. Apologies, I had written a bigger description but I deleted, so I will fill in the blanks here.

Device = Toshiba WT8-A

Install = Bliss-v7.2-android_x86_64-OFFICIAL-20170712-1941_k4.12-SP3_m17.2.0_01

OS's = None - I used gparted to remove all traces of Windows

Previous EFI = Windows 8.1 and Windows 10, however, they do not appear in any drive list after gparted dealt with them

When using Bliss I get no terminal output at all. Grub does not seem to install in a separate partition so I just get No Bootable Device.

When I install the Android x86 version android-x86_64-7.1-rc1 I get this https://drive.google.com/open?id=0B5nf-g1bXqlub3lseFZEVDlnajg

I didn't try much from the Bliss install but I did notice that GPS was not working - but I did not play around a lot.

What would you suggest?
[BLISS ROMS Development] electrikjesus:
Hmm. So, do you still have an EFI (VFAT) partition, and then a second one for the OS? if so, I'd like you to try using the latest version we uploaded for the Udoo. That EFI installer might work better for you.
[BLISS ROMS Development] slim6y:
I made an EFI (vfat) partition with gparted and a second one for the OS. I made the EFI one large enough too (1080 MiB).

I will hunt for the version for the UDO and see what happens. Thanks again. Will let you know.

---------- Post added at 03:38 PM ---------- Previous post was at 03:05 PM ----------

Ok, I gparted, made a fat32 partition for the EFI I installed everything on the second partition (ext4) and everything is fine for installation. At this point I have not tried to reboot. What would you suggest I do to see if the tablet will reboot successfully?

---------- Post added at 03:47 PM ---------- Previous post was at 03:38 PM ----------

I also want to note that currently, WiFI works, rotation and GPS are not working.
[BLISS ROMS Development] slim6y:
Update: I risked a reboot and managed to get back into the system. GPS now works, but rotation still does not.
[BLISS ROMS Development] slim6y:
One more update. I did a reboot but this time GPS didn't work and nor did rotation. Do you have some fixes for this? I also notice you can enter two different boots, what is the difference between the two?

I have a lot to learn all I need to do is be pointed in the correct direction and I can experiment to fix the bugs. Looking forward to hearing more from this :) Thanks again.
[BLISS ROMS Development] kharnm:
I've tried the androidx86 version with the UEFI installer, same problem.
[BLISS ROMS Development] gujiangjiang:
Here are the support you can try to add into blissX86.

https://github.com/JideTechnology/remixos-kernel/commit/7b57e4cc3c1ad5860c44baad86148111fc104604

Add rt5651/es8316 audio codec driver support

1, codec driver support ACPI ID/normal I2C way register

default register is I2C way

2, rt6551 conflict with rt5645 iotcl_xx.c

3, if you want to compile this codec, need to enable macro
[BLISS ROMS Development] slim6y:
Did you try the Bliss version as per previous comment? Did it work?
[BLISS ROMS Development] kharnm:
Great news !

I've launche the UEFI installer and clean android, same with the MBR version. After a first failed try, the second works !
[BLISS ROMS Development] slim6y:
Which version did you install?
[BLISS ROMS Development] kharnm:
Finaly, I use the UEFI installer and Bliss.
[BLISS ROMS Development] pulsaris:
Forgot to tell that 32bit version will boot. The 64bit version does not.
[BLISS ROMS Development] slim6y:
You're all lucky, everything is failing one by one. WiFi now will not switch on. I am going to try to keep the boot loader that is with Bliss and try the Nougat Android x86 install which has worked in the past.
[BLISS ROMS Development] tritant:
Hi all,

Thank you for this very good work!!!

I use this rom on a lenovo yoga in multi boot android, ubuntu, windows 10.

I have not encountered a problem for now...

With launcher3 modified for launch app in freeform windows and taskbar(https://www.xda-developers.com/andr...what-it-is-and-how-developers-can-utilize-it/), this is my best experience with a touch screen for the momment.

But, no way for install xposed on nougat version ?
[BLISS ROMS Development] daspex:
Ok,

I'll try to put it on a ext4 partition,if i remember right the ext4 partition has to be placed after the win partitions,right?
[BLISS ROMS Development] franzli:
I guess not per se, but if you have windows partitions etc. that you are still using (or the uefi partition), then to avoid possible complications with booting it might make sense not to change the starting point of those partitions, but just to carve out a new one at the end.
[BLISS ROMS Development] dapo4friends:
Hello Admin,

Good evening.....

Thanks a lot lot for the work done so far, I know how gruesome such things can be, and then having to give it away for free... Waow!!!

Please I'd like your comment on this very disturbing issue I encountered!!! It leads me to think that a part of the installation instruction u gave on USB to hard drive installation on MBR drives might be wrong....

I created an 8.5 gb (to be safe) partition (and 400mb FAT32 grub partition) and I also personally decided to make the 8.5 gb an ext4 from the get go, to avoid confusion when selecting it later in the installation process...

I installed bliss on this partition, completed it and tried rebooting my system to windows after all said and done...windows couldn't boot...even after I tried to do startup repairs...

Long story short...what I noticed later (upon removing the drive from my pc later) was that there was no free space on the bliss 8.5 gb partition and THAT MY WINDOWS INSTALLATION HAD BEEN FORMATTED!!! And the windows partition had been converted from primary to extended partition and windows couldn't be installed into it again..in fact the entire partition structure is messed up right now

From my experience with Remix OS, the Data partition alone takes at least 8gb, and 'system' also takes extra space- about 2.* Gbs....

1. The question therefore is if data alone in bliss x86 takes at least 8gb and all I have is an 8gb partition, then where did the system components get installed into (since space wasn't made for them)? And why was my windows partition formatted

2.I also noticed that the installer contrary to the guide, doesn't ask u to select the partition u want to install GRUB into...it just does so and asks u if u want to add windows in the grub boot options!!! Why does this happen and did it likely tamper with my windows installation???

Still looking for another drive to move my data into so I can repair the drive....phewwph!!!!

3. I wouldn't be sure if the problem above is why Bliss x86 doesn't ever boot successfully after selecting it from grub menu...I downloaded the latest x86-x64 version of the stable build (I use a 2012_Intel atom 32BIT machine though) the moment it displays ANDROID_#,

NEXT I GET IS A BLANK SCREEN STARING AT ME FOR HOURS.....
[BLISS ROMS Development] ElfinJNoty:
I can't comment on your partition structure, or why your Windows install got messed up. Also not sure which installer you are using. Or which Bliss-x86 build you attempted to install. That info helps on narrowing down where your issues are coming from

If you get a blank screen after ANDROID_# you may need to add "nomodset" to your grub menu entry. This should alleviate any graphics conflicts and should boot. Assuming that is the cause of it not booting of course.

I'd like to add that I have a fully working tripple boot with Windows10(first os installed) as well as KDE Neon(Linux) and Bliss-x86_64 and have never experienced any loss of data or damage to another OS on a separate partition.

Just wanted to make that distinction, so that other readers do not believe this is a common issue at all.

We will try to help you out as best we can. Often when facing weird issues(on unfamiliar hardware) we advise people to try and start with the simplest methods of installation prior to more advanced options.

Are you able to boot to Bliss-x86 from a USB? If that doesn't work, than that would be the first place to start in troubleshooting.
[BLISS ROMS Development] dapo4friends:
THANKS A LOT FOR YOUR RESPONSE

I'd appreciate an itemised format of response though, where each question or concern is picked and dealt based on the question... So I know what has been answered and what was omitted, overlooked or forgotten......

1. I used Rufus 2.9 to prepare the USB.... I used the latest x86_x64 build under the stable branch released on 2017-07-03.....

2. Lucky u to have a tripple boot with no issues...

U omitted the part of my question about if the 8gb space created for blissx86 contains both data and system or data alone...if latter is true, where did 'system' install into, if we follow the installation guide to the letter??

Bcos as I said earlier, I created an 8.5 gb partition for bliss..just to be on the safe side in case more space was needed....How come there was no space left at the end of the install and my windows partition was reformatted to an extended partition.....is it possible that bliss needed more than 8gbs of space (so as to install system.sfs and the rest).......cos remix OS takes about 10.5 gb of space for an 8gb option!!!!

3. As to the issue of trying the simplest first...that shud have been to install bliss x86 into windows like an application (like remix os)....that route never worked.....bliss during boot starts looking for sda3 partition to load from, when it doesn't find, it simply reboots again....I doubt if it was properly configured to install using this mode!!!

4. Yes, I am able to boot from USB and even do the installation.....save only that Grub never gives option to choose which partition u want it installed into (contrary to what the installation guide says on pg. 1 of this thread)....sth I find disturbing and likely a reason my Windows OS was wiped....is it?
[BLISS ROMS Development] franzli:
Re your 4: So this sounds like you're using the installation from the USB medium right? I know that on the various installs I did (albeit about two months ago), I was always prompted where I want to install. The naming scheme of the partitions is not very transparently listed admittedly, so you need to make sure in advance you know the exact name of the partition you want to install to, best using some Linux installation (or live USB), e.g. /dev/sda5.

And yes, if a non-empty partition is chosen by accident there is a possibility that it will get formatted (I think if it's an ext4 partition it might prompt you whether you want to format, but don't remember exactly).
[BLISS ROMS Development] daspex:
Hi,

I managed to get it booting but no touchscreen is working i guess thats normal for pc-version....I'll try the tab-version next.

Edit:didn't had to make a extd-partition just increase the data-img size to 8,xx GB that worked for my device...:)