yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] mikekoz:
Why the hostility? I did not intend my post to be rude or offensive, just looking for a little bit of help with the software. If you do not want to help me, that is fine, I will figure it out by myself. If I did come across as rude, I apologize, but there is no need to instantly assume that I am treating Bliss with any disdain. I was just comparing it to RemixOS because I have used it for a year or so, and this is new to me.
[BLISS ROMS Development] electrikjesus:
It was not my intention to be rude, but we get a minimum 10 users a week saying this or that doesn't work, and they we're too busy to provide the minimum we ask for to diagnose issues.
[BLISS ROMS Development] mikekoz:
Fair enough, but in no way was I even implying that I was expecting you to solve my problem with no information or that you were too busy. I clearly stated that I was not able to supply the log files for you, or anybody, to look at this morning because I was at work. I also said I would post the log files this evening. This is not that important to me, so I think I will just move on to something else. If I decide to to give it another go, I will post all the needed information at that time.
[BLISS ROMS Development] ubuntuh:
Hi everybody, is there any way to run the installer without grub because i have problems booting the iso with my apollo lake chip (Intel celeron N3450). Instead of booting it shows just a blank screen with one underline cursor. Thank you
[BLISS ROMS Development] ElfinJNoty:
That result doesn't have anything to do with the Grub being installed. You may need to utilize some of the boot menu entry variables in order to get Bliss booting on your device. For example, adding "nomodset" to the Bliss boot parameters
[BLISS ROMS Development] youling257:
use the refind ! the bios not support grub2 !
[BLISS ROMS Development] ubuntuh:
Yeah already installed. But still no result. Which bootcommands can I try to add?
[BLISS ROMS Development] youling257:
i only known this http://bbs.phoenixstudio.org/cn/read.php?tid=10384 ，chrome browser translate to English.

i don't know how to use refind at all.

if your Apollo lake bios like this http://www.cnx-software.com/2017/02...-04-on-chuwi-lapbook-14-1-apollo-lake-laptop/ ，you can use grub2.
[BLISS ROMS Development] akajazz:
I have exact same issue on a Lenovo x60. I've Googled this quite a bit, but mostly end up on Ubuntu forums that tell me to try holding shift to get grub boot menu - doesn't do anything in my case. I've gone through the install a half dozen times, trying different combinations of partitions, because I'm pretty sure I got something wrong in there, but no luck. The instructions at the beginning of the thread don't exactly match what I see during install - when asked if I want to install Grub, (and I hit yes) it does not ask me what partion to install it to. I do have a big partition (200gb) for the main OS and 300 mb partition for Grub, but no opportunity to tell installer which partition to use for Grub. I'm using ext4 format. Full disclosure, I'm a linux noob so I'm sure I'm making a mistake somewhere.

I'm working my way backwards through this thread in hopes of finding more updated instructions. If I find it, I'll post back here.

I'm trying Bliss-v7.2-android_x86-OFFICIAL-20170626-1555_k4.9-b_m17.1_pw_rc_01 fwiw.
[BLISS ROMS Development] jthomas1987:
Installed Bliss 7..2 on my new Lenovo Ideapad. It runs great, and i am triple booting between it, Voyager Linux 16.4, and Windows 10. Did it as an experiment and so far runs fine. Keep up the great work.
[BLISS ROMS Development] namitutonka:
Live-Bliss-X86-USB, smooth as silk

Everything, like using LastPass to log into XDA with this reply, watching videos on either chrome or youtube on the chrome browser (on another tab as I type). I don't see installing this if the live USB works this well.

Dell XPS 12-9250. :) Sleep problems like with any other x86 based android OS. My 2-in-1 touch enabled PC/tablet turned off while I went to the kitchen. May toy with extracting system.sfs, edit the sleep settings (sleep.earlysuspend=0, sleep.state=none, or poweroff.doubleclick=1 OR in terminal $ setprop sleepstate none) in recent Telegram messages within build.prop x8x, and zip the live. iso file back up. That shouldn't be too hard. Will report back on the change if any on my live Bliss -x86 USB.

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

the file build.prop was in the C:\Users\m\Documents\Bliss-x86\Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1718android_x86_64_k4.9.54-ga-px-ts-ax86\system folder. There wasn't any instance of the word sleep it the file. I left it unedited. Will use the live,iso as is and will end the session before leaving the PC.

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

Starting live from it's boot menu begins the animated Blissx86 logo which lasts for about a minute. I then have to alternately choose either 'Launcher3' or 'Pixel launcher' while exiting a 'Google Services' message which fails to start and avoiding the 'wait' button. Smooth sailing happens after logging onto my wifi from the network menu. Seems to install and run pretty much everything from the PlayStore, except sound does not work and the game "Deus Ex: The Fall" didn't function correctly. Also there is no way to exit or quit Bliss-x86, I have to bounce between chrome, the PlayStore, or an installed running app. The only way to exit (I tested and recreated this several times) was to physically open my PC/tablet and unplug the battery connection. However smoothly this Live version ran, this is a fatal flaw. Using the Androidx86-Installv24-5800.exe installer with this beta build, or Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso or Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4.iso on my Dell PC/tablet resulted in failed installs with similar logs as this one here.
[BLISS ROMS Development] tobad:
hi guys. i`m trying to fix rotation on my dell venue 11 pro 7130. currently rotation is top-down [180 degree reversed]

system identification:

do i have to modify hal.sensors.iio.accel.matrix?

which are the default values in hal.sensors.iio.accel.matrix?

because i have the writeprotected system.sfs i dont want to try&fail so i ask you before i take the chance.

if you give me a hint for the value i will add theme with these lines to the init.sh

thanks :good:
[BLISS ROMS Development] electrikjesus:
You are on the right track. Once you get a working configuration for rotation, please submit a pull request on our Github
[BLISS ROMS Development] electrikjesus:
The included Taskbar launcher has a shortcut to Power Menu in the three dots menu. If your power button hardware is supported, there is that option too. Otherwise, ctrl-alt-del also brings up the power menu ;)
[BLISS ROMS Development] electrikjesus:
Youling, we have a rEFInd theme that we edited for Bliss-x86, but I do not know enough about how to make it be included in the USB to run, and when I did figure something out, it never allowed me to edit entries like in Grub (hitting 'e')

Do you happen to have any examples I could go by in order to also use rEFInd as a baked in boot option?
[BLISS ROMS Development] namitutonka:
Our old DOS standby ctrl-alt-del didn't work. I used the taskbar as well as Launcher3 and the Pixel launcher, but did not notice the three dot power menu in the taskbar. Thanks. Just may take it for another spin.
[BLISS ROMS Development] electrikjesus:
You may have to enable search bar in Taskbar for it
[BLISS ROMS Development] ExaCrystal:
Where do i get the 32bit iso?

Edit: Never mind, i found it
[BLISS ROMS Development] assasukasse:
I've been trying to run this on my eeepc 900 with 1gb ram and 16gb hdd. Managed to get the archived 32 bit version but can't get it to boot. I reach the animated splash screen then it reboots... Tried to boot from SD, and from USB.

Any suggestion?

CPU atom 900
[BLISS ROMS Development] DigitalMD:
32 bit is no longer supported. Can only suggest you read the previous post in the forum for suggestions, like editing the grub file.

Some machines simply don't work.
[BLISS ROMS Development] namitutonka:
The three dots in the taskbar brought up the power menu, and My PC turns off using it. I made a bootable USB from Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1718android_x86_64_k4.9.54-ga-px-ts-ax86.iso. Live (without wizard) works fine, except for bluetooth. I also did a successful install into a 45Gb partition (sda7) on the same 2-in-1 PC, a Dell XPS12 9250. Touch works, wifi works, but bluetooth does not. Bluetooth has a naggingly constant popup that it has stopped. Trying to set it up using the Google app on my android phone was unsuccessful. No devices found while searching from my phone.
[BLISS ROMS Development] electrikjesus:
In order to avoid that, you will have to format the data partition or reinstall, and go through SetupWizard selecting the other option to restore. Otherwise, it's just going to keep trying to find a Bluetooth that isn't working on your machine
[BLISS ROMS Development] namitutonka:
I did an install of the Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso on this 45Gb partition, which includes a 20Gb formatted data.img. Bluetooth does not work. At least there isn't a bluetooth notification popping up all the time.

SuperSU did update its binaries. BusyBox Pro is installed. I can read books with Moon+ Reader Pro, transferred from my Win10 desktop's FileZilla through my Blissx86 PC running a PlayStore wifi transfer app. Words with Friends doesn't work. Fii Note works but doesn't sync. Denver Trash and Recycling app does not work. Chrome browser works nicely. Rooted ES File Explorer Pro works. Toca Boca game works. Netflix app keeps stopping before it can start. The Room from Fireproof games works. Super 2048 game works. The Denver Post app works. Wolfram Alpha doesn't work. YouTube app works. "OK Google" voice commands work.

Hmmm.... seems if you want to run Android on an x86 tablet , then you're better off getting a non-x86 pure Android tablet OR possibly an x86 Udoo. Linux is clearly multi-platform, maybe someday Android will be too. Linux Mint 18.3 works perfectly on my x86 tablet, including bluetooth and touch. I'm tempted to remove my Android boot option, and going from a triple back to a dual-boot x86. But I really like my Moon+ Reader Pro on a bigger screen than my phone without having to resort to Calibre in Windows. May keep Bliss-x86 solely for a book reader.
[BLISS ROMS Development] fddm:
Just want to report that I installed the stable nougat build on my Asus Chromebox CN60 flashed with coreboot/seabios. All the hardware support/features I am able to test work great. I'm using it as a TV box, and this has been a huge upgrade coming from Linux/Libreelec. Thank you!
[BLISS ROMS Development] HypoTurtle:
The Linux mainstream kernel should have the android patches added for a while, so it should be possible to use the same kernel & modules with mint as with android/bliss. But for the time being you could list the modules used/loadee on bliss and mint to see what's missing or if bliss is incorrectly favouring one module over another. Saying the best way to use android on a x86 tablet is to get a non-x86 tablet I take to be a slip of the tongue... That being said yea probably best (but likely poorly updated) is to use a device with a specific hardware build of android compiled for it
[BLISS ROMS Development] maravic:
Chuwi Hi10 report:

I have installed Bliss V10 (Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1718android_x86_64_k4.9.54-ga-px-ts-ax86.iso) with Android-x86 windows installer. System boots only with nomodeset parameter. Without this paramter it boots only to terminal prompt.

System is laggy and with screen artifacts - in comparision to nougat-rc2 build from android-x86

Wifi is working - (rtl8723bs), bluetooth not tested.

power ald volume keys and backlight control is also working.

Sound (es8316 ) - not working

Screen rotation - only manual using app instaled from google play

Touchscreen - not working

I found patches to kernel for touchscreen https://fedorapeople.org/~jwrdegoede/icn8505/ but kernel 4.12 is required. and I wasn't able to compile kernel 4.9 with this patches. Maybe someone could try to add this patches and build test kernel?
[BLISS ROMS Development] bfmetcalf:
did you try the other image without the -ts? That is the one that worked the best for me.
[BLISS ROMS Development] jamesoh:
I've got one of the new version Chuwi Hi13, the only OS i've managed to get the sensors working on so far is Phoenix OS and their 2.14 Kernel and then had to change the hal matrix to get it working 100% correctly.

When running the latest bliss (v10) I cant get connected to Play, which I believe may be serial number related, will try the latest build next time to see if it work.

Main reason of posting was to say that the Chuwi Hi13 has a GDIX1002 based touchscreen, goodix.ko currently only provides for GDIX1001 and for the android based images I've been having to rebuild the driver based on the kernel (cant do it for bliss v10 right now withe files going private).
[BLISS ROMS Development] HypoTurtle:
Is dumping the sfs from v10 into an img working for anyone?
[BLISS ROMS Development] electrikjesus:
That step is no longer needed for the 8.x/10.x versions (Post 2 updated now)
[BLISS ROMS Development] HypoTurtle:
I know its not needed but I'd rather run a rw system.img atm - I'm not seeing anything related to that on post 2.

Fairly sure the img I made should boot just not sure why it doesn't the system.img mounting is there in initrd.img...
[BLISS ROMS Development] electrikjesus:
Try extracting it to just a folder
[BLISS ROMS Development] HypoTurtle:
That would need to be on an ext4 partition. Not a big deal, just would prefer it on ntfs & not sure why its refusing to load the img.
[BLISS ROMS Development] bfmetcalf:
Are you copying on a Windows computer? If so, it could have something to do with permissions.
[BLISS ROMS Development] electrikjesus:
Extracting to a folder should work on ntfs also ;)
[BLISS ROMS Development] HypoTurtle:
Nope doing it on another androidx86 build. Creating a system.img mounting img & sfs, cp -rp ing it over.

You sure? I know NTFS has like pseudo Linux permission support,...
[BLISS ROMS Development] aiglesh:
I tried it on a Dell Inspiron 13 convertible, installed via the new installer. Works excellent. All hardware is working except rotation and track pad.

Even turn off hardware button and sleep function is working. Battery percentage, charging status etc, hot keys for brightness, volume buttons all work.

very nice.
[BLISS ROMS Development] electrikjesus:
Hey man. I'm not going to guarantee any things going to be fixed. But I'll try my best to do what I can. RemixOS is a corporate product, they make money off it. This is a personal project, so I dream of the the piles of $$ Jide's exec's are swimming in all Scrooge McDuck style, but then I wake back up to the real world and realize I do this for my fun. Not for anyone elses ;)
[BLISS ROMS Development] -->:
can i use xtrememusic instead of arise?
[BLISS ROMS Development] electrikjesus:
I am unfamiliar with Xtreme music, so I really couldn't tell you. Best bet is to try and see. If you fail, just replace the system.img with the one from the ISO.
[BLISS ROMS Development] bigr1979:
Thanks for your work. Am using latest bleeding edge build on a Surface pro 2 and works very well (apart from the odd wifi crash as others have stated).

Have even booted it on an old Toshiba Encore tablet which wasn't playing nice with android x86 before. The Encore has screen rotation and seems quick enough, no sound unfortunately and same with wifi, mostly ok but sometimes crashes.

I have noticed that 5ghz wifi doesnt work on the Surface pro 2 but on the Toshiba Encore it does.

Screen brightness slider works on Surface Pro 2 but not Encore.

Anyway main reason for the post was to thank you for your time and work, am enjoying your builds.
[BLISS ROMS Development] scabs:
This is awesome stuff [MENTION=928479]electrikjesus[/MENTION]. Thanks so much for your time on this.

I'm using "bliss-x86_64_n7.1.1r13_02.08.17_k4.10rc7-dev_01.iso" on an Alcatel Plus 10 (Cherry Trail x5-Z8350).

Here are my observations:

1) WiFi does not work. (RTL8723BS)

2) Bluetooth does not work

3) Sound does not work

4) Touchscreen and Auto Rotation are working

5) Very snappy

6) USB Ethernet adapter is working

7) Power and volume buttons are not working.

Thanks again!
[BLISS ROMS Development] bart2465:
Touch is not working on Surface pro 4. Are the correct IPTS firmware files loaded in the rom?
[BLISS ROMS Development] tafo:
thank you for the stunning work in porting Slim rom to x86 laptops, its really running very smoothly, Im using the latest bleeding edge rom( feb 9) I want to report my prelimanry feedback, kindly know that I installed it on SSD, Surface Pro 3- ( SP3)

-wifi: working

-Touch screen:working

-toych type keyboard: working-including light buttons and integrated mouse pad

-sounds : working

-bluetooth: not working

-autorotation: not working

-camera : front and rear cameras are working with the default camera app, however while snaping a photo, a gray photo is presented and its not saved.

This rom is near to perfect and i will use it as my daily driver, I love it:), keep up the good work bro, I will be watching your thread so closely for recommendations, news and updates
[BLISS ROMS Development] janosch2001:
Winpad 10 Bliss Install

Hey I have a Winpad 10 and tested Bliss X68 with it..

I booted it live and everything worked great expect of sound buttons.. Then i tried to install it, and grub didnt boot because of the bootia32.efi fike missing (since it has a 32 bit uefi bios) so i need to manually push that fike to the installation.. Also are there any fixes for my 2 other problems ?

Thanks
[BLISS ROMS Development] theOriginalSuperl2:
Please help.

I'm having huge problems on my SP3. It's stuck booting in the boot animation, and /data seems to be mounting read only. Even if I remount it with "mount -f -o rw,remount /data", "mount" still shows that it's read only (attached picture). Logcat output shows many "read-only filesystem" errors when writing in /data (also attached) I've tried setting chmod 7777 on every single file on the SD card that I'm booting from (but I've tried all of this with a USB drive, too) but that doesn't work. If I delete the "data" folder on my SD card android boots, but it's like a live CD because no data's saved. In that case, "tmpfs" gets mounted at /data, read-write. The strange thing is, if I create an empty /data folder on the SD card, and boot it, from the console, "ls /data" shows nothing, but when I plug the SD card in an SD reader, somehow, theres the usual files and folders you'd find in /data on android devices (this was a quick look - I think some stuff would be missing). It's weird, because as far as I can tell, /data's been read only the whole time, and even as root I can't write. Normal android x86 boots and runs fine.

N.B. The owner of the "data" folder on the SD card gets changed to "system" every the I boot.

TL;DR: Android gets stuck at the boot animation because /data gets mounted as read only.
[BLISS ROMS Development] rajnallan:
This has been replied in one of the earlier post. After installation you should delete the system.sfs file. If you miss that step then files will be read only.Afetr install if you open the filws you will find both system img file and system sfs file. Delete system.sfs
[BLISS ROMS Development] theOriginalSuperl2:
Sorry, where are these files located? I can only see a folder called "system".
[BLISS ROMS Development] theOriginalSuperl2:
Do I have to do this before booting? Are these files unpacked on the first boot?
[BLISS ROMS Development] rajnallan:
As soon as you install, before rebooting, open file explorer open the position where you have installed Bliss , there will be a folder called Android open that delete system.sfs and then reboot.
[BLISS ROMS Development] electrikjesus:
If you installed this to an EXT4 partition, there is currently a bug in Android-x86 that is not allowing installs to work after some time. we are looking into an answer still.
[BLISS ROMS Development] theOriginalSuperl2:
But I thought you had to install to an ext4 partition or android doesn't work properly?
[BLISS ROMS Development] lollyjay:
Only if you want entire partition used instead of fixed data size
[BLISS ROMS Development] electrikjesus:
I wanted to give you all a quick heads up that we will be also releasing a few unroofed builds geared towards the education sector. These builds will include all the customization options you have come to love, minus a select few options that required root. I will be posting these builds in the next couple days. and will also be posting the newer bleeding-edge builds too ;)
[BLISS ROMS Development] theOriginalSuperl2:
To avoid this, can I use ext3? or does it have the same bug
[BLISS ROMS Development] electrikjesus:
Didn't mean to skip your answer there. Yes, it will have the same bug for now. I have been completely happy side loading it to a folder on both my HDD and my sdcard (one for stable daily use and one for testing) or using the windows UEFI installer works too. Same method.
[BLISS ROMS Development] theOriginalSuperl2:
So fat32 will be fine?
[BLISS ROMS Development] I'mRonBurgandy?:
Which version did you use?
[BLISS ROMS Development] Miustone:
What is with this 20180201-2214 Build? Any Infos? Searched the Thread but found no Posts about it...

Thanks
[BLISS ROMS Development] bfmetcalf:
It was just uploaded, should have a bunch of fixes according to what was said in the etelegram group. Comes with kernel 4.15 I think
[BLISS ROMS Development] Miustone:
.

Looks like it's also smaller. I will give it a try on My Surface Pro 3! Thanks for the Info! :highfive:

Edit: Looks like it was still uploading. There is now another Version too. One says m17 and one m18. Diffrence?
[BLISS ROMS Development] bfmetcalf:
I think it's the different Mesa builds. Mesa 18.1 vs mesa 17.3.3