yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] electrikjesus:
That is normal for running in Live mode. Installed, debug mode should be able to toggle
[BLISS ROMS Development] Depau:
Hi,

I just tried your build and it works veeeery well on my Lenovo Thinkpad X1 Yoga.

A few questions that came to my mind:

Screen rotation doesn't work. Is there already any work in progress to get IIO sensors to work or should I try to fix it myself?

You got the ROM to build just fine, while Lineage x86 / Android-x86 don't build on nougat branch. Are you going to contribute the changes you made back upstream to Android-x86?

Thank you very much!

And good job, I'm really impressed!
[BLISS ROMS Development] rajnallan:
Thanks. Back in action..Appreciate your help as always
[BLISS ROMS Development] electrikjesus:
1) We have been messing a little with the IIO sensor matrices, but nothing promising yet.

2) We try and update GitHub on a daily basis, and there have been a few things we and Android-x86 project have chatted over. I will let them pick whatever they like from us. Sharing is caring ;)
[BLISS ROMS Development] sk8223:
I just installed it to my HDD and I still can't turn dev options off for good. It keeps turning back on. I installed the x86_64 EDU ROM.
[BLISS ROMS Development] electrikjesus:
How odd... I will have a look at it in the next few days then
[BLISS ROMS Development] naknul:
Does this Rom have Google Assistant support on pc?
[BLISS ROMS Development] electrikjesus:
if you are lucky enough to have a device with a working microphone, yes. I think I was able to enable everything for that.
[BLISS ROMS Development] diaayousef:
Can you please make a stable build for kernel 4.9 ??

Because the other kernels are missing most of the drivers for surface 3
[BLISS ROMS Development] electrikjesus:
on my tests, kernel 4.9 had the same wifi issues 4.10/11/12 are, so hardly stable IMO. But I'll see if I can kick something out in the next few days
[BLISS ROMS Development] diaayousef:
Thank you so much for working on this build

The problem with kernel 4.9 is not only the wifi

First, it is much slower than other builds. I did a benchmark using Geekbench 4 and found that the multi-core score is even lower than the single-core score

Sencond, it keeps restarting without any reason, especially when I try to wake it up
[BLISS ROMS Development] Depau:
1) well actually my computer is one of the few featuring an accelerometer mounted in the right direction XD

The problem is that it doesn't work at all. But maybe it's just that it's not enabled somehow. I'll try to debug that later today, I didn't have time yesterday.

2) That's great. I can't hear the andex devs over all this FOSS freedom lol
[BLISS ROMS Development] naknul:
Is it possible to make this function on a raspberry PI 3? i have tried but my PI dosne't want to boot. Any idea?
[BLISS ROMS Development] electrikjesus:
Shhh, don't get you're hopes up too soon, but we have plans for the RPi ;) It's not ready yet though. We will let everyone know

https://github.com/BlissRoms-RPi
[BLISS ROMS Development] franzli:
The rpi doesn't have an x86 but an ARM chipset, so this here cannot work. But interesting to hear that there's an rpi version in the works!
[BLISS ROMS Development] ikostas_1:
Can u make a remix os like installer??

Στάλθηκε από το SM-N920C μου χρησιμοποιώντας Tapatalk
[BLISS ROMS Development] lollyjay:
There is one for download in Post #2
[BLISS ROMS Development] ikostas_1:
And what about legacy BIOS??? :/
[BLISS ROMS Development] lollyjay:
Oh, sorry.
[BLISS ROMS Development] electrikjesus:
There are a number of installation methods to be found on the Android-x86 Google groups. Look here

https://groups.google.com/forum/#!searchin/android-x86/Legacy$20bios$20guide%7Csort:relevance
[BLISS ROMS Development] electrikjesus:
I looked into the remix installer source, but never got far due to lack of supporting documentation. I started to follow the Unetbootin documentation to try and build it, but ran into errors.
[BLISS ROMS Development] loveyoulovemetn:
Can we use this with macos+bootcamp? Many thanks
[BLISS ROMS Development] Depau:
How are you building this? I tried multiple times with up to date source and I'm getting issue on kernel configuration reading. I can build once more to get the logs.

I also tried to menuconfig, save .config, copy it to the right path, but it still doesn't build and I don't understand the error.
[BLISS ROMS Development] electrikjesus:
UPDATE - 05/23/2017 - BLEEDING EDGE

Hello again peeps :) I am updating a few things today, starting with my custom UEFI bootloader. I updated a couple of the efi versions, bootia32.efi now works on more legacy devices, and also added a few extra boot options for easy testing. ( https://www.androidfilehost.com/?w=files&flid=143191 ) Second up is a new 64bit bleeding_edge build, using kernel-4.11, with merges from Ubuntu's kernel work, as well as Maurossi, & Tovalds repos. The firmware in this build is also a hybrid of the three sources as well. Anyhoo, check our github for details on changes.

As always, uploading the new builds to Bliss server, and the old builds to AFH.

Updates include:

New switch in Buttons settings of Blissify to disable/enable the navbar on-the-fly (allowing us to use [MENTION=4289533]farmerbb[/MENTION] 's Taskbar as the Navbar without reboot)

Updated kernel-4.11 & firmware

Removed ARISE Audio. It was bugging out on a few things.

New power manager that's more fir for our devices.

and as usual, there's likely more, but I forgot...

Known Bugs:

- Changelog from AboutBliss STILL not working ( I am still working on it)

- reverse or 90° orientation on some touchscreens

- Some wifi reconnect issues still

Enjoy!!

https://downloads.blissroms.com/Bliss/Official/x86/
[BLISS ROMS Development] electrikjesus:
I have to update the stable branch of the manifest. The current working branch is Bleeding_edge

EDIT: It looks like I have already updated it. Let's double check to make sure you have all the required dependencies:

$ sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip squashfs-tools python-mako libssl-dev ninja-build lunzip syslinux syslinux-utils gettext

And if you already do, please PM me a log or hastebin and we will see if we can help. You can also check out our Build Support chat on hangouts: https://hangouts.google.com/group/3TtAHiGMN4zgEdlw2
[BLISS ROMS Development] scabs:
I EJ, i've been trying to test this, however the setup wizard keeps crashing so unable to setup the device.

Not sure if you are aware of this or if it has already been reported.

Thanks!
[BLISS ROMS Development] franzli:
Noticed the same issue. May be to do with gapps, had that on a different arm device that i wanted to set up yesterday, too - after flashing gapps!
[BLISS ROMS Development] electrikjesus:
Yes, it does appear to be gapps related. Add this to your grub entry, right before "quiet":

SETUPWIZARD=0
[BLISS ROMS Development] tobitege:
[MENTION=928479]electrikjesus[/MENTION] Hey bud, hope you're doing great! Just found this by chance, looks so interesting and I'll give this a try on the weekend!

Thanks for your work and making this available! :)
[BLISS ROMS Development] franzli:
Thanks, this allowed me to boot, bypassing the wizard! Strangely, everything seemed much more sluggish than what I experienced on previous versions running in my Venue 8 Pro Cherrytrail. Don't know I'd the faulty gapps introduce some extra problems. In fact, WiFi didn't connect either (it detects APs, but won't connect), so I couldn't install geekbench to check for much slower it is objectively, but it is very noticeable in simple ui usage.
[BLISS ROMS Development] electrikjesus:
What kernel was that build using g again?

And we have made good progress at fixing the setupwizard issues this week, so hopefully soon we will have another stable release
[BLISS ROMS Development] franzli:
I suspect the final 4.11 kernel? I was using the latest bleeding edge you uploaded a few days ago. You mentioned something about using stuff from three different sources though.

Great, would be glad to test another build! Also would be eager to test something with a 4.12rc kernel, heard good things about that for cherry trail (although the vanilla rc2 I built for arch Linux was missing touch support).
[BLISS ROMS Development] electrikjesus:
We do have a booting kernel-4.12rc2, but no WiFi at all on my tests :'( But as soon as it get at least that, we will get a bleeding edge tester out to you all
[BLISS ROMS Development] youling257:
it isn't only no WIFI，should to say wlan0 no Internet at all，eth0 no Internet at all also .
[BLISS ROMS Development] ElfinJNoty:
[MENTION=928479]electrikjesus[/MENTION] doesn't have a device with an Ethernet port for testing as far as I know.....

Thanks for pointing this out. Will make sure it is looked into. Hoping for some upstream fixes for 4.12 to help with compatibility right now. But progress being made daily.

Please feel free to spread the word and gather some attention from some developers.

I know Jon and all of the Bliss Family members would appreciate some contributions to debugging and development :good:
[BLISS ROMS Development] bethnesbitt:
Stuck on splash screen

I'm trying to run Bliss-x86 on a dell inspiron 2305 all in one desktop with:

4gb ram, 1.6ghz, AMD Athlon(tm) II X2 250u Processor, it has two processors

I ordered a 245e processor, and 80gb sata II ssd hard drive online, but that isn't going to be in until sometime next week.

The 250u is 64 bit, but none of the android-x86 64bit work on it. For now, until the parts come in, trying to run the 32bit version.

The 32bit of Phoenix, Android-x86 and RemixOS work with the following added to my menuentry:

menuentry 'Android-x86 6.0-r2 Live' --class android-x86 {
set root='(hd0,5)'
linux /kernel root=/dev/ram0 quiet DATA=
initrd /initrd.img
}

except for Bliss so far. I'm using xubuntu 17.04 and adding the grub.cfg into the menuentry, but it still sticks, even when I dd the ISO to a usb stick, it just stays on the splash screen, showing bliss with the animated flower logo. When trying the above code for bliss, get an emergency system r/o error and the pc reboots.

I have a newer desktop, Bliss boots up fine on that, when I saw how slick it looked on the newer desktop, I nearly cried with excitement :).

Am really wanting to get it working on the dell all in one, my ambition is to have it run basically as a great big 23 inch tablet.
[BLISS ROMS Development] electrikjesus:
I would try adding the permissive boot option. Here is an example:

menuentry 'Windows' --class windows {
search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}

menuentry 'Bliss-x86' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry '[GPU]Bliss-x86 xforcevesa' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet xforcevesa DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry '[GPU]Bliss-x86 nomodeset' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet i915.modeset=0 nomodeset DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry '[GPU]Bliss-x86 xforcevesa nomodeset' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet xforcevesa nomodeset i915.modeset=0 DATA=/RemixOS
initrd /RemixOS/initrd.img
}

menuentry 'Bliss-x86 DEBUG mode' --class bliss {
search --file --no-floppy --set=root /RemixOS/system.img
linux /RemixOS/kernel root=/dev/ram0 androidboot.selinux=permissive DATA=/RemixOS DEBUG=2
initrd /RemixOS/initrd.img
}
[BLISS ROMS Development] youling257:
DATA=/RemixOS，needn't .will create /mnt/$SRC/RemixOS as second data.

i understand your means，https://groups.google.com/d/msg/android-x86/0xVvHnQsbsQ/0rHH74UYCQAJ

https://groups.google.com/d/msg/android-x86/NKuKSs7Awoc/pAYoGqmABwAJ

"DATA=/AndroidOS" is a wrong syntax (and no effect) before (include) 6.0-r1.

In 6.0-r2, it means the data subdirectory is "AndroidOS".

The feature allows the users to specify the data subdirectory if they want.

If you want to use data.img as before, you have to remove "DATA=/AndroidOS"

from your cmdline as I have explained

The "old way" is always supported, of course.

Indeed I think you misunderstood (misuse) the meaning of DATA=.

If you want to say "my android-x86 installation dir is /AndroidOS",

it should be "SRC=/AndroidOS" instead of "DATA=/AndroidOS".
[BLISS ROMS Development] franzli:
Btw. the 4.12rc3 kernel is out. Tried it on one device in Linux so far (the Cube i7 book with skylake cpu) and it seems better than the rc2, at least I didn't have a regression with the touchscreen which is working fine now. WiFi is also OK, although I didn't check whether it was broken for me on rc2. Might be worth a try though.
[BLISS ROMS Development] bethnesbitt:
I tried all those settings, believe it has something do do with being an older cpu. When the PC boots to bliss, there is an ACPI error with bliss. Disabled the HDD and booted bliss live from the usb stick, it gives the same ACPI error. Tomorrow the more up to date CPU will be coming in the mail, hopefully that fixes the issue.

Don't think it is a menuentry error but a PC hardware error that doesn't like the

androidboot.selinux=permissive

for some reason. The only way androidx86 will seem to boot on this PC is if

androidboot.selinux=permissive

is removed. The only issue is that with Bliss, as I stated, it gives a system r/o error and boots back to the main ubuntu boot menu when

androidboot.selinux=permissive

is removed.
[BLISS ROMS Development] NMBNMB:
Wow, this Ax86 is fantastic, fast and far much updated.

Thanks for your efforts!
[BLISS ROMS Development] electrikjesus:
I can't figure out for the life of me why your machine would require selinux enabled... Very odd. Something else to look into I guess
[BLISS ROMS Development] electrikjesus:
Finally got around to modding the Android-x86 MBR/GPT installer to work with newer Bliss-x86 & Android-x86 builds. I have already added this to the second post also

Easy Install For Bliss-x86 6.4/7.x MBR (32bit or 64bit)

** This method is the easiest install method for MBR/GPT boot setups, but it does require Windows to install. **

For the overall instructions on using this method, please refer to the tools original thread: https://xdaforums.com/showthread.php?t=2142563

I have taken some time to update the tool for easy install on MBR/GPT machines. The builds I modified can be found here: https://www.androidfilehost.com/?w=files&flid=185778

Part 1 - Using the Installer

The installer has been modified, and will read and install any 32bit or 64bit Bliss-x86 build onto a GPT/MBR type setup. Just run the installer, pick the Bliss-x86 .iso file, and select your size data.img. If you require a size data.img larger than what is available, please use the RMXtools v1.7 mentioned in this post elsewhere.

AND.. I also have new 32bit and 64bit Bleeding Edge builds, using kernel-4.4.40 uploaded to https://downloads.blissroms.com/Bliss/Official/x86/bleeding_edge/ for testing.

The plan is to also push out a couple builds tonight and into tomorrow using kernel-4.12rc3 too, so keep your eyes peeled.
[BLISS ROMS Development] rajnallan:
I used the installer Android_InstallerV12_mod as suggested and installation of Bliss X86 rom went as a breeze on my surface Pro 3. When I restarted i got the boot screen as below.

1 Windows

2 Android

When I go to control panel/programs/ I don't find Android listed. So I am not able to uninstall and try again. When I go to commandprompt as admin and command bededit.exe I can see android as well as the file \android\boot\grldr.mbr but I still get the error message.

Any help please. I really appreciate the nice work done on the installer.

Thanks
[BLISS ROMS Development] electrikjesus:
This method is not intended for use on UEFI setups, like the SurfacePro3. For that, please use the UEFI install instructions. You will manually have to use the uninstall.bat in the Android folder to remove the install. (should work)
[BLISS ROMS Development] TerenceWSK:
It has been a long time since my last feedback (Lenovo tablet issues). I want to know how's the support on CherryTrail platform going on now? THX
[BLISS ROMS Development] electrikjesus:
Wait for this next bleeding edge release using kernel-4.12rc3
[BLISS ROMS Development] TerenceWSK:
I'm looking forward to your good news. Thanks for your effort.
[BLISS ROMS Development] wizmart:
still no success with wifi, ethernet working sometimes on edge 24-05, been trying on hp elitebook 8470p, i5, 8g. i don't have these problems with remix or phoenix.
[BLISS ROMS Development] Ichijou Raku:
Good night sir,honestly i'm newbie on android x86..

i have question,

- is the root access included on bleeding edge build?

- is the substratum interfacer included on bleeding edge build?

- and bleeding edge is stable enought for daily activity like browsing,etc??

thanks sir..
[BLISS ROMS Development] georgekav33:
Thanks for your efforts. Indeed the 4.12 kernel has some interesting stability commits for Bay trail as well.

Unfortunately, I tried the 4.11 of your and I get Wizard force closure just before I get the options for WiFi. 4.4 works fine.
[BLISS ROMS Development] franzli:
Have a look a bit earlier in the thread, previous page or two, there was an issue with the setupwizard which you could get around be adding the boot option SETUPWIZARD=0 (i.e. on the grub menu on startup press e for the first entry and add the boot option after "quiet").

You should be able to start then (note that I still faced issues with that build, slightly older ones ran much better for me on a cherry trail device).

Looking forward to the 4.12 kernel (in fact rc4 is out now ;) )
[BLISS ROMS Development] georgekav33:
You nailed it! That was it :)
[BLISS ROMS Development] electrikjesus:
Yes

Yes

And, Yes

Time got away from me this past weekend, but we got the WiFi on Setupwizard issues squared away, and I brought the kernel up to 4.12rc4. I'll run a test build tonight so that should be ready for you all tomorrow
[BLISS ROMS Development] fastguy:
Great news! Waiting for the new build. Btw, on the x32 version with kernel 4.11, bluetooth was not working properly. Hope you can nail it as well :) (and please, BT audio and input device-mouse support!)
[BLISS ROMS Development] georgekav33:
Yes, I can confirm that at least for the T100TA model. Sound is muted as well for me (I did properly shutdown from windows but still the issue remains)
[BLISS ROMS Development] ElfinJNoty:
Electrikjesus has been working tirelessly on bleeding edge builds which Bliss Team members have been testing and contributions are coming in from lots of places.

We appreciate your testing and reporting, and a new group of test builds will be released soon to include 4.12r4 kernel and perhaps some backports.

Please keep in mind the amount of effort that goes into making Bliss-x86 compatible with your device(among thousands of hardware configurations)

Donations to Bliss are always appreciated and go a long way towards our plans to file for non-profit status, as well as continue to maintain costs associated with hosting, build servers, and test devices. :good:
[BLISS ROMS Development] georgekav33:
Indeed I/we appreciate that effort. To be honest that rom is THE best X86 one I have encountered, and I have been in the scene for quite a while. I do appreciate his effort in porting and Bliss team for such a great rom for any device. I am just giving some feedback on verified bugs to help him improve it as I know well that porting a rom to a device is a feat, let alone doing in for a whole family of devices! Thanks Electrikjesus!:good:
[BLISS ROMS Development] electrikjesus:
Thanks for the shout out, but there is a reason I haven't even asked for donations. If we are doing the right thing here, the universe will find a way for it to continue. Even though I don't have a device of my own to test it on, I have been fortunate enough to be able to test it on my wife and kids computers when needed, along with all the Bliss team members who also test the builds. I'm not going to give up :)

BTW... Happy Birthday [MENTION=1857544]ElfinJNoty[/MENTION] ;) Enjoy your day!!!
[BLISS ROMS Development] Blac_Jak:
So, I was trying to install the 7.2 x86_64 Bleeding Edge build on my Toshiba Satellite C655, but every time I try to boot Bliss, it goes through the initial startup process with the black screen and text. Though, it never makes to the "Android x86_64" bit, instead it quickly displays an Emergency Reboot error and restarts every time. I've tested and installed both Phoenix OS and Remix OS and they both work perfectly fine but for some reason I can not get Bliss to work. Even when I edit the grub commands at the selection screen, the farthest point I can get the boot up to, is the "Android" point. it doesn't even display "x86_64" after it.

Laptop Specs

CPU: Intel Core i3 380M (2.53GHz Dual Core)

Ram: 4GB

Graphics: Intel HD Graphics

Model Laptop: Toshiba Satellite C655-S5128

*Edit*

So, it would seem that editing the GRUB commands and changing the second line actually managed to get it to boot Bliss. The next issue is that apparently, the Setup Wizard crashes every time I select a method of either retrieving data from a Google Account, or starting from scratch...

*Edit Edit*

Okay, so, I found out that the "Easy Installation" method for MBR and GPT does not provide a proper GRUB.cfg file upon installing, leaving no other way to change the GRUB commands except in the GRUB itself. EVERY. TIME. YOU. RESTART... Anyways, I don;t know if it's just me, but the Bleeding Edge build has an issue where the Setup Wizard crashes during the setup leaving you unable to use it. So, I just decided to use the latest official build. Again, the MBR and GPT instructions fail to mention that that method doesn't actually work. Once again, this method leaves no proper .cfg for the GRUB, and the GRUB commands it creates for the bootloader do not work. Using this method and rebooting to start up Bliss only ends in an Emergency reboot each time. To fix this, I just copied down the GRUB setup for Remix and used that as a basis and it worked!
[BLISS ROMS Development] franzli:
The setup wizard problem was discussed previously, must recently at the top of this page. See there for a workaround, until the next release which appears to have that gapps issue fixed.

I don't know what problem you mean with grub? Obviously it's a generic file, but works on most of my setups. On my baytrail tablet I need to modify the grub.cfg which admittedly is a bit complicated on windows (not so much on Linux). You need to mount the efi/efs partition and find the correct grub there, which you can then edit to your heart's content (I had to try you which over was the correct one, since I had two grub.cfgs, probably from done previous install attempt).

I have made the experience that installation using the method from the boot menu gives me better results (didn't have backlight control using the other method on my cherry trail tablet for example).
[BLISS ROMS Development] Blac_Jak:
What I was talking about had to do with one of the installation methods at the beginning of the thread. Installing Bliss on MBR/GPT systems using the tool listed and linked gives you no GRUB config to edit. It makes a boot folder with only a MBR file in it, and the essential core img files. Also, this method appears to have ruined my Remix install and plastered GRUB4DOS in its place...