yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] electrikjesus:
!!New Bliss OS for PCs - v10.0 Beta Release!! - 2/03/2018

We are making another release of Bliss OS for PCs!! This time in the form of two builds with Kernel 4.15 (with extras from maurossi, jwrdegoede, Android-x86, and a few more sources) and some more changes with Mesa 17.3.3 & Mesa 18.1.0 too. A few more additions and fixes are also included in these builds too, like a new Bliss branded version of the freeform mode launcher, Taskbar from [MENTION=4289533]farmerbb[/MENTION], integrated themes, and much much more.

Same boot process as the Beta, so the old Windows Installers will not work as expected. On the old boot process, you used

DATA=AndroidOS/

but in this one, you will need to keep it shortened to

DATA=

You will also need to add

SRC=AndroidOS

or wherever your source folder is.

New Windows Installer for Bliss seems to be working well, so I also updated that with the secondary modprobe boot option too. Newest build of that can be found here:

https://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows/tree/master/bin

Same rules apply as previous Beta release, I don't want to see anyone in here posting silly things like "it doesn't work" or "I installed and it shows a black screen" If you plan on using this build, I would appreciate a little on your part to also provide the info we need to help you, like install type, conditions, hardware, PC type, processor type, drive type, filesystem type, what steps you took so far, etc. Please and Thank You.

Updates / Additions:

Kernel 4.15.x - mostly stable on all devices, including nvidia chipsets

Added a few more boot options to the mix, one of which uses the secondary modprobe method, so hoping this helps where some aren't able to boot.

New boot animation

Rooted with SuperSU (Do not update binary, it might break things)

Integrated Google Themes (Substratum still works in rooted mode too)

Bluetooth is mostly working right, just not on all machines. (The bane of my existence)

Bugs / Issues:

Bluetooth issues still exist on many devices

you will get Play Store and process crashes until WiFi is connected. Just dismiss these for now. Once connected to WiFi, things should work properly.

Sound or keyboard might not work, try to boot using the secondary modprobe option (add AUTO_LOAD=old in grub)

Expect more. It's still a beta release. Report your issues, but make sure you SEARCH the thread first to make sure it hasn't been answered. And post logs too (I know, WTF are logs anyways??)

As always, check the Bliss download site for the newest builds. The rest are all on AFH as a backup archive. Hope you all enjoy this one :D

https://downloads.blissroms.com/Bliss/Official/x86/bleeding_edge/
[BLISS ROMS Development] Miustone:
Report from m18 on Surface Pro 3 i5/8GB/256GB.

-Booted fine

-Touch works

-Buttons are working

-Auto Rotation works

-Front Cam Works (Rear Missing)

-Setup Wizard Informs about Google Notifications but shows a Blank Page. Tapped Back twice and tried again. Play Service FC and forced to the last Setup Page. All fine)

-Still getting random Play Services FCs with Wifi Connected

-Wifi isn't showing the Strength in the Statusbar

-Still a Problem with waking up from Standby (Background Light turns on but stays Black)

-Bootanimation is still small and now rotated too

-Looks like the System is not rw after selecting it while installing

Thanks for the new Builds! Think they are pretty well usable right now (Except for the Blank Screen after Standby)
[BLISS ROMS Development] aiglesh:
Touch screen version of second last beta.
[BLISS ROMS Development] jamesoh:
Have flashed the latest two roms and my observations are below:

- Unable to connect to add Google Account to device Says "Please try again later"

- i2c accelerometer not working

This was when having a read-write file system.

When keeping the filesystem compressed these two issues did not appear and there was just

- Boot screen is portrait when screen is in landscape

- Touchpad not working as I have model GDIX1002 rather than standard GDIX1001 [ With the Kernel not being released on this I can't hack the .ko and then get the touch screen working. I believe more and more devices are using GDIX1002 and it works 100% correctly with the GDIX1001 driver]

Device is a Chuwi Hi13, GDIX1002 touchscreen, BOSC0200 accelerometer
[BLISS ROMS Development] tobad:
i also try to get RW access to system data.

running windows 10, ntfs.

extraced system.sfs in new subfolder system. (C:\BlissOS-v10\system)

deleted systems.sfs

changed the grub entry

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

but it will not boot:

is it possible to mount the folder C:\BlissOS-v10\system as a device? or am i completely wrong?

Update:

extraced system.sfs in new subfolder system. (C:\BlissOS-v10\system)

renamed systems.sfs to _system.sfs

changed the grub entry

menuentry 'Bliss-x86 v10 Beta' --class android {
search --file --no-floppy --set=root /BlissOS-v10/_system.sfs
linux /BlissOS-v10/kernel root=/dev/ram0 SRC=/BlissOS-v10 androidboot.selinux=permissive quiet DATA=
initrd /BlissOS-v10/initrd.img
}

now boot process gets further until

so i think it cant access the system folder directly
[BLISS ROMS Development] pauliusval99:
Nope, it's a 100% different issue. You went through the installer and ended up unable to boot. I can't even reach the installer.
[BLISS ROMS Development] greg_mp:
hello,

tried to use the latest M18 on my galaxy book 12, and still the same issue with wifi that is not working. Looking at the dmesg, ath driver is trying to load the firmware, but firmware is not responding....

here is the dmesg

https://imgur.com/qjLva5h

I'm trying to update driver into the sfs file as it sounds like there is an updated version here: https://github.com/kvalo/ath10k-firmware

but actually didn't know that was so complicated to edit an sfs file. I have no linux machine and thought it was possible under windows...
[BLISS ROMS Development] electrikjesus:
Are you using an nvme drive by chance?
[BLISS ROMS Development] electrikjesus:
I will see if I can include this in the next beta release
[BLISS ROMS Development] electrikjesus:
This build I did try something a little different with the installer and it uses its own kernel 4.9 separate from the kernel built into the system. So you may be having issues with that
[BLISS ROMS Development] noobstyle1337:
on Surface Pro 4 many Works Fine:) but nooooooo Touchscreen :crying: plz Fix Thanx for this awesome rom
[BLISS ROMS Development] greg_mp:
Thanks a lot. If you can point me some place where it shows how to rebuild the sfs, I can give it a try before you start some unneeded work may be...

I am struggling to edit the sfs file under w10 and virtualbox refuse to open my USB3 key...
[BLISS ROMS Development] Guimenez:
I'm trying the 8 version but i can't make it boot, it stop on the line "Starting Android".

The 7 version worked fine.

What i done(the same i've done it with 7.0):

- Build my USB with Rufus using UEFI mode.

- Install it using the installer on my second partition (ext4) with write permissions.

- Edited my old grub2 menu and replace put only DATA= and not DATA=AndroidOS

My grub:

menuentry 'Android' --class android {

search --file --no-floppy --set=root /AndroidOS

linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive quiet DATA=

initrd /AndroidIOS/initrd.img

Thank you
[BLISS ROMS Development] I'mRonBurgandy?:
I have a Dell inspiron 13 2 in 1. I-5 kabylake. I tried both of the latest betas and they both live boot and seem to work fine, but the installer doesn't respond at all.
[BLISS ROMS Development] Canneloni:
Hey guys, sorry for the probably redundant question, but a quick search didn't really offer a solution:

I want to try Bliss OS on my Medion Akoya E1234T Windows Tablet. I downloaded several BlissOS ISOs, latest being "Bliss-v10.0-PC_Beta--OFFICIAL-20180201-2214_android_x86_64_k4.15.x-b-s-rt-jwd4-ys_m18.1.0-dev_w05" , but when i tried to boot, I had a black screen.

I also tried other ISOs and i always loaded them as live image from USB created by RUFUS. Onetime I was able to boot, but the wifi signal did not work at all. Since I want to test it first before I install it, I would love to have a working test image. How can I get there or what can I do?

This are the main specs of the Akoya:

Intel® Atom™ Z3735F Prozessor

64 GB Internal Storage

2 GB of RAM

Realtek RTL8723BS Wireless LAN 802.11n Network adapter

Would love for someone to point me to the right direction where to look.

Thanks :)
[BLISS ROMS Development] noobstyle1337:
CPU Fan is Not running on Surface Pro 4 its get pretty warm :(.
[BLISS ROMS Development] tobad:
I don't think so... here are some specs:

[ SanDisk SD6SP1M128G1012 ]

[ Standardmäßiger SATA AHCI- Controller ]
[BLISS ROMS Development] electrikjesus:
It's likely the ahci sata controller support here
[BLISS ROMS Development] electrikjesus:
I have no clue what build you tried, only your machine type
[BLISS ROMS Development] tinzzz007:
can i change the ethernet proxy configuration in this ROM ?
[BLISS ROMS Development] jamesoh:
[MENTION=928479]electrikjesus[/MENTION] any hope of getting the Goodix driver to also accept GDIX1002?
[BLISS ROMS Development] noobstyle1337:
I have the Surface Pro 4 i5 with 4 gb Ram ....... the build was Bliss v10 2031/2214 an all 7.1 releases with Kernel 4.12 and 4.13 with me it occurs while loading and surfing but the touchscreen would be more important to me

Thanx for this Awesome rom and Greetz from Germany
[BLISS ROMS Development] rea1l1:
Running a Fujitsu Q702 tablet w/ dock (i5,4gb ram, intel hd4000, usb3). BIOS is set in backward compatibility mode (which my win7 os install needs) though appears capable of booting UEFI.

I used rufus to prepare my usb 3.0 stick.

I am presently stuck at the Emergency remount reboot cycle.

Here are my experiences so far with x86:

1) generic android x86 installed smoothly and booted from USB stick

2) RemixOS x86 installed smoothly and booted from USB stick

3) Bliss Rom Live booted, but showed corrupt graphics and was unable to proceed through setup. This is the one time Live successfully booted - after that it repetitively failed.

3) Bliss Rom successfully installed to USB stick. At the end of installation I selected to load android (as opposed to "reboot") and Bliss Rom successfully loaded and fully ran. Upon rebooting, I was unable to boot into that installation.

4-8) I have tried numerous installations and research in order to get Bliss Rom to boot.

I have tried both:

Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9

Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4

Android_InstallerV12.exe

I noted the suggested requirement for logs if I am to receive good support, but don't know where to find such early boot logs. It appears to run very well on this system, if only I could get it to boot aside from immediate post-installation.

Thanks for all of the hard work you and your team are doing. It's an excellent operating system.

EDIT: I AM SILLY. Followed original instructions.. Used LiLi (as opposed to rufus) and live boot works fine. Going to see if an install works out better soon.
[BLISS ROMS Development] dataghost2014:
Does this have Apollo Lake CPU support? Thank you so much for this!
[BLISS ROMS Development] ubuntuh:
it doesn't work on my apollo lake because the grub didn't startup. You can try experimenting with rEFInd but in my case this didn't solve the issue either. There is an methode, where you respin the iso to use rEFInd instead of grub but i haven't already tried this and i think it is just for linux. Tell me if you find a solution
[BLISS ROMS Development] youling257:
refind.conf，a sample

timeout 20

scanfor manual

menuentry Androidx86 {

icon EFI/refind/icons/os_linux.png

volume UUI

loader 7.1/kernel

initrd 7.1/initrd.img

options "root=/dev/ram0 SRC=q DATA= androidboot.selinux=permissive buildvariant=userdebug DEBUG=1"

}

do you really know how to use refind ? do you success see these ?starting kernel，using load options "root=/dev/ram0 SRC=q DATA= androidboot.selinux=permissive buildvariant=userdebug DEBUG=1"

copy refind folder to esp partition，can you do it ? use easyuefi add refind option，can you do it ?

your C/D/E:drive ntfs partition，create Bliss-x86 folder，this is SRC，options "root=/dev/ram0 SRC=Bliss-x86 DATA= androidboot.selinux=permissive buildvariant=userdebug DEBUG="

/Bliss-x86/ramdisk.img，system.img，data.img

your fat32 partition，it can be your esp partition，or your U-disk，copy kernel and initrd.img to fat32 partition.

volume can be label，or guid.

volume UUI

loader 7.1/kernel

initrd 7.1/initrd.img
[BLISS ROMS Development] M1810:
Efi:requested map not found..

It says booting androod and then goes black.. any help?
[BLISS ROMS Development] Hardstylez92:
touchscreen not work chuwi hi10 plus

Hi. I installed this rom on a chuwi hi10 plus everything works correctly except the touchscreen how can I fix it?

im using Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4
[BLISS ROMS Development] Stickypinkyfinger:
When I tried to install this I couldn't see anything as the writing was so small I couldn't see it. Is it know for the writing to be small on the installation screen?
[BLISS ROMS Development] ubuntuh:
Sorry to say but i am quite a noob in computing so if you woud have the kindness to explain me the process more detailed? this would be really nice
[BLISS ROMS Development] xfaethorx:
There's no touch screen support that I'm aware of yet for this model. I've had no luck with the latest bleeding edge version on this device either . I'm waiting for them to get it working on this device as getting off of 5.1 would be brilliant.
[BLISS ROMS Development] andjohn:
Using this with a Surface 3 is SO CLOSE to perfect.

1. When selected power off, the tablet looks like it halts but it doesn't actually power off. It's like it gets all the way there and then just waits. You have to hold the power button for 20 seconds to force the power off and then press it again to get it to turn on again.

2. Always shows charging and that it's at 100% battery life

3. Wifi looks like it's not connected but is. Also, if you use the wifi heavily, it will disconnect and you have to reboot to get it back.

4. Tonnes in the logs about access denied to different things. I'll follow up with logs if I can

That's all I can remember right now.
[BLISS ROMS Development] ElfinJNoty:
Logs please, when you get a chance
[BLISS ROMS Development] vladnovski:
Can't run games

I have tried the two stable OS/roms but everytime I run games (any games) it closes right away. other utility apps such as file explorer runs perfectly.:(
[BLISS ROMS Development] sgn15:
Good day

I just found out about android emulators a few days ago and this is the 3rd one I have tried. I am no "techy" dude but I do understand how to follow instructions and basic computer stuff.

I used the video tutorial for Virtual Machine (Nougat) in the first post

Here are the steps from the video that didn't seem to appear in my own attempt (using Bliss Android 8 Alpha iso)

- screen where it asks me to choose "New" partition, then "Primary", then shows the size of partition "press enter"

^in relation to that above, it did say [Primary] partition despite missing the said screens

- screen where it asks for GRUB2 (i did see the screen where it asks me about GRUB though)

- after rebooting, instead of 4 choices, I have 6 choices

In the video:

Android-86 2017-12-11

Android-86 2017-12-11 (Debug mode)

Android-86 2017-12-11 (Debug nomodeset)

Android-86 2017-12-11 (Debug video=LVDS-1:d)

Mine: additional 2 options has asterisks

Android-86 2017-12-11

*Android-86 2017-12-11 (No SetupWizard)

Android-86 2017-12-11 (Debug mode)

*Android-86 2017-12-11 (Debug mode no hwaccel)

Android-86 2017-12-11 (Debug nomodeset)

Android-86 2017-12-11 (Debug video=LVDS-1:d)

I did choose the first one like in the video. But it gets stuck at the screen before "Android" comes up

The last line in the stuck screen is:

Detecting Android-x86... found at /dev/sda1

My laptop is i3-3120M CPU @2.50GHz

4GB RAM

Windows 10 Pro 64 bit

Questions:

1. Is this due to my hardware or I did some steps wrong? (like I said above, some steps from video were missing for me so I'm really not sure)

2. If due to hardware, what android version of bliss can work for my hardware for same VM method?

3. Assuming I can make this work (regardless of whatever android version) thru same VM method, is there a way to make this into a single .exe file that I can easily transfer to other PCs and use it there? like a portable app (and without needing vmbox manager)?
[BLISS ROMS Development] bfmetcalf:
I have it installed onto an SD Card so I can transfer it to any computer. This is not an emulator, it is actually Android running on your PC, you could completely remove Windows 10 and still run it on your computer. An exe file could intsall it (I believe there are some windows installers for it in the OP).
[BLISS ROMS Development] maheshkondraju:
Hey Guys,

Surface Pro 4 TouchScreen Finally working with Bliss x86 Rom but with an old custom build from raeckraeck.

I have the source code of that build, can someone find Surface Pro 4 TouchScreen drivers and merge it in newer build tree in github of bliss os, so that in future with every build our Surface Pro 4 TouchScreen works.

check this link for source code as well as image for usb to try out.
[BLISS ROMS Development] noobstyle1337:
coool many Thanx
[BLISS ROMS Development] dannieboiz:
I run this in VirtualBox on a 1080p monitor when in full screen it looks all messed up. Any way to have this scale properly?
[BLISS ROMS Development] electrikjesus:
As a rule of thumb we will only use sources that retain the correct developer attribution (commit history), so if your sources have that, I would love to take a look. If you aren't sure, look for a hidden .git folder, or pass it along in a PM and I will take a look ;)
[BLISS ROMS Development] electrikjesus:
Although Bliss may run well in a VM, I would prefer not to support it due to the lack of proper VM extensions for Android. Please try to run native if you want to experience what it was really meant to be.
[BLISS ROMS Development] sgn15:
I only want it to co-exist with windows so I have access to both windows and android. so my only option for bliss is the vm method.

sorry for asking again. You mean you have the .vdi file on your sd card?

I might buy a hig spec windows tablet when I have saved enough money and used the same vm method so I can access android too.

and so is it not working due to my hardware?

edit: op ignored my previous post
[BLISS ROMS Development] maheshkondraju:
i cant find any hidden .git folder but its a bliss x86 build with name Bliss-x86-m6.0.1-K4.9.20_USB.iso & Bliss-x86-m6.0.1-K4.9.20_src.zip

Can you just add the touch screen drivers from the working build to the development.

Secondly i am a newbie so i am not able to post the link of the build.

Shall i post the archive of the touch screen drivers, as i am not able to pick the surface pro 4 touch screen driver
[BLISS ROMS Development] grayhaze:
[MENTION=928479]electrikjesus[/MENTION]: I know you're probably sick to death of hearing about the Surface Pro 4 by now, but the work you've put into supporting our devices so far has really been appreciated. While the version of Bliss x86 mentioned by [MENTION=7206464]maheshkondraju[/MENTION] does indeed enable the touchscreen, it's extremely unstable and cuts out after any medium to heavy use. The wifi driver in that version is also pretty terrible and rarely keeps an internet connection for more than a few seconds at a time. Also I agree the lack of any sort of code change history isn't great for pulling in the required changes to the main builds.

A better option might be to look at jakeday's Surface Linux patches, which apparently provide both a stable touchscreen implementation and a more recent, stable driver for the Marvell wifi chip in modern Surface devices. He has patches available for both 4.14 and 4.15 kernels, the latter of which I see you've recently been working on with the bleeding edge Bliss x86 builds. You can find the repo here: https://github.com/jakeday/linux-surface

Thanks again for all your hard work and I totally understand if you'd rather focus on compatibility with more friendly hardware rather than Microsoft's complicated beasts.
[BLISS ROMS Development] maheshkondraju:
even i tried the latest bleeding edge bliss rom Bliss-v10.0-PC_Beta--OFFICIAL-20180201-2214_android_x86_64_k4.15.x-b-s-rt-jwd4-ys_m18.1.0-dev_w05.iso

everything works in this rom except for the touch screen on surface pro 4 that is the reason why i requested to pick the working touch screen driver and embed it into the latest bleeding edge version or even as sugested by GrayHaze lets include jakeday linux surface patches into bleeding edge images and i am happy to tell that i am here to test them on my surface pro 4 just like a alpha or a beta tester.

What works in bleeding edge bliss rom Bliss-v10.0-PC_Beta--OFFICIAL-20180201-2214_android_x86_64_k4.15.x-b-s-rt-jwd4-ys_m18.1.0-dev_w05.iso on Surface Pro 4 :

1. Graphics works fine with latest Mesa 18.1 drivers

2. Marvel Yukon Wifi Working fine without any packets drop.

3. Orientation Portrait Landscape works

4. Physical button Power button is allowing to go to sleep i think wake is not working on pressing again.

5. Audio &Volume rockers are working

6. Pen havent tested

7. Type Cover working with smooth scrolling

Whats not working:

1. Touchscreen
[BLISS ROMS Development] Guimenez:
When i start the live booting it stops in the message "starting android".

Does anyone know how to fix this?

I've one toshiba encore 2 wt8-b-102 with Atom z3735G.

The Nougat version boots fine.

Thank you
[BLISS ROMS Development] bfmetcalf:
You can also use a dual boot instead of using VM. In my experiences, VM is good for testing something out, but not a whole lot else (at least for me, I'm sure there are some real uses for others). You should be able to put an android folder on your c:/ drive and actually boot into android instead of using a VM session. In the second post on this thread there are instructions called "Custom Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit)" that show how to make it boot.

I do not have a .vdi file. I actually have it installed on the SD Card and boot straight off of it. I do not have Windows on my computer at all, Linux is on the HDD, but hasn't booted in a while except when I have updated Bliss-X86. I have had it installed on a USB drive as well and it works well too. The process is a little different with that process as you will need to install GRUB onto the USB/SDcard, but it does work fine.

You could also try this installer... https://xdaforums.com/android/software/winapp-android-x86-installer-uefi-t3222483
[BLISS ROMS Development] electrikjesus:
If it were that easy, it would have been included already ;)
[BLISS ROMS Development] electrikjesus:
No worries, many people miss the part where the windows installer installs Bliss side by side to Windows. Dual-boot method. and it requires no messing with partitions.! So no mess!

I should make an ad for it. "Bliss! Now with Windows installer! New and Improved formula leaves no streaks!"
[BLISS ROMS Development] Eagle0110:
Well, on blissroms.com there is still this claim that

"We are sorry :'(

but our Windows Installers are currently being updated",

maybe update that first before making your "ad" for the windows installer?
[BLISS ROMS Development] noobstyle1337:
Hey guys

i think it would be easier for the surface pro 4

to take the touch screen support from this kernel than from any Rom because the pen in the rom does not work

I say thank you very much if you can do it because I'm very excited about Surface Pro 4 support

Many Thanx and Greetz

://github.com/jakeday/linux-surface/blob/master/README.md
[BLISS ROMS Development] moelito:
If the bliss team manage to sort out the surface pro 4 IPTS (78) drivers for the touchscreen I promise I will put in a donation!