yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] grayhaze:
I've gone one better and donated before they've sorted them out.
[BLISS ROMS Development] xfaethorx:
I donated just on the off change they get the CHUWI Hi10 pro working !

Everyone should try and donate a little.
[BLISS ROMS Development] noobstyle1337:
okeee i donated for surface pro 4 .....surface please for Chuwi ??
[BLISS ROMS Development] kypor:
Just tried latest bleeding edge with my Dell Venue Pro 8, and it works good! Thank you!

Used

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

Quirks:

Bluetooth - Is there a way to deactivate this? I keep getting a pop up "Bluetooth stopped working", even though Bluetooth doesn't appear to be activated.

Rotation does work, but it goes the opposite direction. Anyone know how to resolve?
[BLISS ROMS Development] algarues:
I am using the rom with a laptop with integrated Intel graphics and dedicated amd.

How can I use vgaswitcheroo kernel module to switch graphics card?

While on the integrated graphics I can use the command for the module to switch completely off the unused one.

In linux after giving the command to switch graphics card it is required to log out and then log back in. This causes a restart of the x-server with the other graphics card.

How can that be done in android?
[BLISS ROMS Development] franzli:
Could you specify which version of the DV8P you have, the older version with Baytrail Atom SOC (e.g. Z3740D) or the newer Cherrytrail with Z8500 Atom SOC? And could you verify if sound is working for you?

I have both the older and the newer version, but no sound on either of them - whereas the older Baytrail model used to have sound in older versions of Bliss x86, still on nougat.

I also noticed the Bluetooth note coming up on the older Baytrail model, but interestingly only after I had a look at the Bluetooth menu. So it maybe of you don't even go into the menu, you won't be bothered with the notifications.

Another quirk I noticed on three larger tablets (Cube i7 Book with Intel 6y30 CPU, Lenovo Yoga 3 11 with Intel m3-5y10 and Thinkpad Tablet 10 1st Gen with Baytrail SOC) was that screen orientation behaves a bit unpredictably. It starts out fine, but after the Setupwizard is finished, it switches to portrait mode. Not a big issue as one can control orientation with one of the Rotation apps on the play store, but annoyingly, some apps turn around the screen on their own again. Happens in slither.io when ads are displayed and in BombSquad from the beginning.

Autorotate is not so crucial, but does anyone know a way to properly fix screen orientation to avoid apps screwing up orientation? It's especially annoying if you want to play with the keyboard and you get everything upside down.
[BLISS ROMS Development] GogoAkira:
When i try to setup as new device, or even with account, it says Setup wizzard keeps stopping, and it just gives option to close it. Using Virtualbox and a stable release (Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1552_k4.4) , is there anything I can do to get it running. Mouse doesn't integrate, i can only use the keyboard
[BLISS ROMS Development] 4r44444:
Anybody already got the newest bleeding edge working on Chuwi Hi12 Tablet?

If you did install it, on which partition you did it coz there are like 5 Partitions.

And if you succesfully installed i what is not working and whats working?

Since Liveboot doesn't work I would be happy if anyone could answer :P
[BLISS ROMS Development] kypor:
Sorry its a Dell Venue 8 Pro 5830

Also you are correct, there is no sound available.

I didn't go into any settings either, from startup I always get an error "Process system isn't responding" and also "Bluetooth keeps stopping". The Bluetooth error is continuous, never going away even tapping Close app.
[BLISS ROMS Development] aatif69:
Not detecting partition

I tried almost everything but it's not detecting any partition apart from removable disk from which i am booting...

Plzzz help meee....
[BLISS ROMS Development] yusufadhi:
working touchscreen surface pro 4

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] grayhaze:
Did you just copy and paste [MENTION=7206464]maheshkondraju[/MENTION]'s post from two pages back after [MENTION=928479]electrikjesus[/MENTION] already replied and said it wasn't going to happen...?
[BLISS ROMS Development] electrikjesus:
And you guys wonder why I'm reluctant to answer all the repeat questions in here...
[BLISS ROMS Development] rymate1234:
Hi, I'm having an issue booting the latest oreo beta's on my x86 tablet. It's one of the many cheapo Atom tablets with an x5-Z8300

With the 4.15 kernel, the device doesn't even boot - it stops at the _ for a second or two and just reboots.

With the 4.9 kernel, the device does start booting, but appears to stop at the shell. Booting in debug mode, there appears to be some issues with initialising surfaceflinger https://gist.github.com/anonymous/d7ece7155a2af98ea5de85f49a588d9e (best attempt at extracting dmesg logs)

Booting the device with nomodeset allows it to boot, but obviously without h/w acceleration the experience is a bit rubbish. I'ver also tried using AUTO_LOAD=old to boot the tablet with no luck. Additionally, the latest releases of android x86 works on my tablet

If you need any more information, I'll be happy to provide it
[BLISS ROMS Development] digital0:
I have the same problem. Don't know how to debug it. Just compiled Android-x86 oreo myself, and it boots successfully. So it seems some of the Bliss kernel config options is faulty for our hardware?
[BLISS ROMS Development] TOSanthony:
How to download the 32bits Bliss Oreo?

Can you past download link please ?
[BLISS ROMS Development] Ealge0110:
32 bits ROM are not supported now, as stated in earlier posts.
[BLISS ROMS Development] sgn15:
What I meant (in my previous post) was running Android while still in Windows with access to all my windows-installed software, start menu, and running android (in a single window) at the same time. Nox App Player is actually what I was looking for, except that it has no version higher than lollipop. I needed Nougat/Oreo for the multi-screen/Picture in Picture features. It's not for gaming, it's actually for something I would (wish to) integrate into my own work.

With that said, is Virtual Machine method my only choice?

**Edit: I meant above for multitasking at work.
[BLISS ROMS Development] bfmetcalf:
If you want to run windows programs at the same time as android, then yes, VM is your only choice. This is an actual operating system, not an emulator or application running, it needs to run like an OS.

You could try the ARC welder addon for chrome browser, I think it will run android apps, haven't tried it though.
[BLISS ROMS Development] Infinity123:
I have been having issues with the latest Bliss builds. They won't boot anymore on my Dell Latitude 13 7350.

System specs:

CPU: core m-5Y71 with 8gb ram

wifi / BT: intel 7265

audio: Realtek I2S

The latest built that works for me is: (Bliss-v7.2-android_x86_64-OFFICIAL-20171103-0937_k4.12_oto-installer.iso)

I have attached picture where the boot seems to get stuck (20180218-1613android_x86_64_k4.15.x-b-s-rt-jwd4-ys_m18.0.1). It also gets stuck at the same point with the 4.9.8 kernel.

I am not sure how to provide other boot logs from the live usb stick...
[BLISS ROMS Development] noobstyle1337:
no Surface Pro 4 Touch support :(
[BLISS ROMS Development] electrikjesus:
I see nothing here that will help me diagnose the root problem :( Sorry
[BLISS ROMS Development] Eagle0110:
Can you please write a complete, structured guideline, for what kind of information and tests one should do to help the dev the most with the beta builds, and post onto the first page?

No just a list of things could be interesting doesn't help when there are OS noobs who don't even know how to read logs.

If it is indeed within your interest to expend your user base as well as the number of beta testers, a constructive instruction from the dev himself can be helpful for both you and your users!

Just my two cents :)
[BLISS ROMS Development] electrikjesus:
I do thank you for any donations you may have made to our project, but I still have yet to get anywhere on IPTS devices like the Surface Pro 4. It'll happen eventually, but I am not able to test anything for IPTS still, so please be patient.
[BLISS ROMS Development] electrikjesus:
I will take that into consideration
[BLISS ROMS Development] noobstyle1337:
I can Test for you no Prob

I've tried a little and no desire to install windows
[BLISS ROMS Development] Palm Trees:
Perhaps with everyone's help a list of devices or device database, could be created.

Of course, not flooding this thread, but maybe in a seperate thread.

"Device: [name]

What's working/not working

Bluetooth:

Tourchscreen:

Etc. etc.".

Something like that. I wouldn't mind helping :)
[BLISS ROMS Development] electrikjesus:
We've started gathering some statistics from working devices that we will be making available soon enough. This should help make a good starting point to eventually create such a list of what doesn't work.
[BLISS ROMS Development] ubuntuh:
I need bliss x86 so badly but i am stuck with a jumper ezbook pro v4 so an intel apollo lake device. We cant boot the grub and has to use rEFInd. Is there any way possible to wether configure the boot command to use refind or to use an iso which don't needs grub to boot? Help is much appreciated!
[BLISS ROMS Development] grayhaze:
As always I'm happy to test any builds on the SP4 and feed back results. I know that's not as helpful as having a device in your own hands though, so maybe we can get enough donations together to make that a reality. :)
[BLISS ROMS Development] DigitalMD:
The problem with Chuwi ( i have two Hi12 s ) is that Chuwi uses several non-standard drivers or older versions of drivers they have hacked, for example touch screen and audio and a proprietary power controller. SO, when you try to boot with common drivers bad things happen and it either won't boot or it does but several devices don't work.

WHY? Because Chuwi bought the leftover stock of a nice display (Microsoft surface 2) then put the cheapest components they could find around it meaning a complete kludge design with non-standard hardware, non-standard BIOS and non-standard drivers.

The Chuwi devices do not have a lot of customers so it's rare to see full support for the devices, even on Windows and support from the Chuwi factory is non-existent.

For me the Chuwi Hi12 runs very well on the latest WIndows 10 insider preview, as long as I make sure the correct drivers are installed. No complaints there and the factory Android 5.1 while dated performs nicely. I doubt you will ever see a fully functional non-factory Android ROM since CHuwi teamed with Remix OS which is now pretty much abandoned, for a hacked special version. And you will never see an update from Chuwi.
[BLISS ROMS Development] bsorli:
Yes and what I've experienced, but reading on other forums people have found some support for Bliss x86 builds and would live to see more support even if it comes from Hi8 and Hi10 devices that have been around longer and more popular.

Many builds on Hi8 have been tweaked to work on Hi12 and why I suspect Lineage OS has originally made progress with their efforts. Big problem for most relates to keeping Windows 10 that I use only once or twice per month. If dropping this will help, so be it and move on to native tablet support.

Either way, thanks for the quick reply! Sorli...]

Update - that's a great point and maybe just need to hunt down native drivers or hacked updates and extend Bliss efforts with a custom ROM.
[BLISS ROMS Development] WoltreX:
How can people use this OS on PC without keymapper? Good work but Fail..
[BLISS ROMS Development] electrikjesus:
Why should we include something that would just add to the bloatware? Especially since apps like Tincore Keymapper or Octopus ( http://www.phoenixos.com/en_US/octopus/intro ) fill that gap... That's not what Bliss is about ;)
[BLISS ROMS Development] aatif69:
stuck @ android x86#

stuck @ android x86#

booting from uefi usb , amd phenom x2 processor, win 7 64 bit, GPU: NVIDIA GeForce 7025 / NVIDIA nForce 630a..,Mother board -M4N68T-M-LE-V2, , Windows Security: Access NVRAM Privilege ... Not All Set

iso booted through rufus then i had gone to boot menu selectted usb run without installation then some text and then stucked @ android x86 #

phoenix os is running fine excep the pointer but the bliss is stucked @ android x86#

help me and ask any info which is needed

when i try install to hdd it wont show any partition there except usb tried creating one ntfs partiotion and one 400mb fat 32 partiotion for grub still it wont show any partition...
[BLISS ROMS Development] electrikjesus:
First off, what build did you try, and second, if it doesn't boot in live mode for you, it won't boot if you install it either
[BLISS ROMS Development] aatif69:
i tried

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

and

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

i just want andro on my pc u may suggest me any version which is more likely to boot on my system

Thanks for reply
[BLISS ROMS Development] electrikjesus:
Oh gosh... We're developing for Oreo now, so the Bliss v10.x versions. Those would be your best bet for compatibility
[BLISS ROMS Development] aatif69:
okay will try

your android pc installer gives an error

nstaller Version:2.6.0.0

Secure Boot ... Not Supported

Manufacturer: System manufacturer

Model: System Product Name

Product: M4N68T-M-LE-V2

BIOS info:

DELL - 20110705

BIOS Date: 07/05/11 19:20:42 Ver: 08.00.14

BIOS Date: 07/05/11 19:20:42 Ver: 08.00.14

Available GPU(s):

GPU: NVIDIA GeForce 7025 / NVIDIA nForce 630a

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

Administrator privilege ... ok

CPU Architecture: 9

CPU Name: AMD Phenom(tm) II X2 550 Processor

OSVer: Microsoft Windows NT 6.1.7601 Service Pack 1

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

System Firmware: Other

==========================================
[BLISS ROMS Development] aatif69:
tried the Bliss v10.x versions

its still the same

stucked @ x86_64#

Any hopes now?
[BLISS ROMS Development] kkellogg378:
Which version would I use to make a portable version with a bootable USB?

Which version would I use to make a portable version with a bootable USB?
[BLISS ROMS Development] digital0:
Any version you want.
[BLISS ROMS Development] DigitalMD:
All versions can be used for that.

Use the rufus tool to create a bootable USB from the ISO file
[BLISS ROMS Development] Infinity123:
Yes, I know that there isn't enough information to work with. But I have no idea how to get something like "last_kmsg" for live usb? I tired googling, but found pretty much nothing on how to debug and take logs for live usb...

A guide for "noobs" and normal people alike on how to take logs from live usb would be great.
[BLISS ROMS Development] RomLand:
Can not setup a device whenever I use VBox. It says "Setup Wizard has stopped" and then same error over and over!
[BLISS ROMS Development] electrikjesus:
There's always hope, just not this past round. Let me finish testing with Android-x86's 4.9 kernel and I'll be able to upload that build soon.
[BLISS ROMS Development] electrikjesus:
Delete me. Duplicate
[BLISS ROMS Development] electrikjesus:
Do you guys even read the release posts?

Add "SETUPWIZARD=0" to the grub config. Hit "e" when grub shows up
[BLISS ROMS Development] ghembuls:
Tested this on low setting within Oracle Virtual Box 5.2.6 using Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso, on grub selected no setup wizard and all works fine. Based on what I have tried compared to original android_x86 original project, this version is better on my end. Some expected lag due to low setup vbox is acceptable, in my own opinion, the lag and stutter is not so much different with other available android emulator.

Compared to BS Player (any version), with the same setting, in fact and again my own opinion, even on Android_N, Bliss is better. Other users experiences maybe different with what I have got, but on my end, I prefer Bliss.

My VBox Setting:

2 cpus

hpet on

cpuhotplug on

pagefusion on

memory 1800

vram 128

default virtualization

standard set on others

Thanks to [MENTION=928479]electrikjesus[/MENTION]​
[BLISS ROMS Development] NaNo79:
i install v.10.0 on USB surface pro 2017 and i face some problem

1- touchscreen not working

2- auto rotation not working

3- soft power button not working

4- volume button not working

how i can fix all that??
[BLISS ROMS Development] Infinity123:
I tried to boot the (20180218-1613android_x86_64_k4.15.x-b-s-rt-) build and managed to get a dmesg from my Dell Latitude 7350. I hope this will help.
[BLISS ROMS Development] HotDogfinba11:
The website won't load?
[BLISS ROMS Development] electrikjesus:
Our servers are currently down for maintenance. Once they are back up the website and downloads server should be available. Until then, we always have the fork of our site at https://blissroms.github.io and a mirror for our archived builds on Sourceforge: https://sourceforge.net/projects/blissos-x86/files/Official/Bleeding_edge/
[BLISS ROMS Development] 4r44444:
I addet it to boot command list in Grub and hit F10... still tablet reboots and ends in grub again.

Chuwi Hi12
[BLISS ROMS Development] electrikjesus:
You must have missed something, because if you got to the SetupWizard the first time, it should just boot and skip it this round when adding that command.
[BLISS ROMS Development] HotDogfinba11:
Thank you!
[BLISS ROMS Development] 4r44444:
Ok... I boot from USB Stick... Grub shows up, I go to Install Bliss option, press E, add the line "SETUPWIZARD=0" and press F10...

What am I doing wrong? :/
[BLISS ROMS Development] electrikjesus:
Add that bit to the kernel line, right before the word "quiet"
[BLISS ROMS Development] HotDogfinba11:
I get to the section where I select boot without installation but after that and it says it is about to start android and beneath x86_64:/ # and just flashes on that without getting anywhere

---------- Post added at 01:01 AM ---------- Previous post was at 12:42 AM ----------

[
[BLISS ROMS Development] 4r44444:
Tried it.

'Live' SETUPWIZARD=0 'quiet'

than I tried

'Live' 'SETUPWIZARD=0' 'quiet'

also tried

'Live' 'SETUPWIZARD=0 quiet'

Tablet still retarts instead of boot to live system :3
[BLISS ROMS Development] electrikjesus:
please paste the full grub entry here please. also, did it choose to not boot on the second boot?
[BLISS ROMS Development] maskes:
Chuwi Surbook - Goodix touch driver

Hi guys,

I have a Chuwi Surbook and I really like Bliss-x86 which I use for the last 8 month or so.

The problem is that I can only use it with my mouse as my Goodix touchscreen is not working.

Everything else is great.

Could you please add the Goodix touch driver to your next build?

I don't know if this will be of some help to you https://github.com/goodix

Thank you for your efforts and time to make Bliss-x86 even greater.
[BLISS ROMS Development] ghembuls:
Bliss 7.2 On VMWare

As I have written on few pages back, I put BlissOS on virtual environment. Compared to some of available android emulators, BlissOS N Series is much better. I tried the emulator which is using Android N as their latest build, but it cant match BlissOS even with the same Android N. I know, BlissOS is different from emulator, but since I put it as a virtual machine, then it is the same as emulators (they are all using virtualization).

I have also mentioned about using VBox to install BlissOS, and I got lags and stutters. So, I tried using VMWare for BlissOS. The result is totally different, with the same setting I used on VBox, VMWare is able to reduce significant lags and stutters. Had I put more power to the VMWare setting, I believe it will give much better result compare to VBox. Im not saying that VBox is lower than VMWare, but on this matter, the result is obvious. The same N-Series OS from the original Android-X86 project itself, feels rather slow compare to Bliss, both on VBox or VMWare environment.

Environment

- VMWare Workstation Pro 14

- Memory 1900 MB

- 128 GB VMDK (SCSI)

- 128 MB VRAM

- 2 CPUS & 2 CORES

- Network NAT

- Intel Virtex

- CPU Virtualization

- IOMMU

Bliss Image

- Bliss 7.2 Android X_86 20170703 Ax86.iso

(I tried to install X86_64 version, but cant install Xposed because, it was detected as 64 bit and Xposed framework from installer failed to install)

Addons Apps

- RAM Expander (SWAP) - 4GB SWAP + 100% Swap usage

- Xposed Official Build Sdk-25 X_86 (Installed direcly from Xposed Installer)

- LSpeed

- Busybox 1.28.1

- Gravitybox (N) 7.0.8 - Expose module

- Viper4Android (Nougat IO Fix)

- ADB On Ethernet

- Adaway

Extras

- Nova Launcher 5.5.3

- IYTB YouTube 49.55 No Root Black Theme Vanced

- MicroG for iytb

- Solid Explorer X_86

P.S

All 3rd party apps, are installed using ADB

Because this is only for testing and fun, my VMWare setting is based only on minimum requirement. If you plan making it as heavy duty android emulator, I strongly suggest to increase the virtual environment setting.

NOTE:

If OP or Mods believe this post is repeatitive and already discussed on previous page/s, feel free to delete it.
[BLISS ROMS Development] electrikjesus:
Actually, if you'd like to make a detailed post about how you got it up and running so others can repeat your steps, I would like to include it in the instructions.

let me know ;)
[BLISS ROMS Development] ghembuls:
If you feel it can assist others, I will gladly share. To reduce clutter and long reading, I will send you PM at the soonest. You can edit or moderate it, as you see fit.

I will write down and send you later.

P.S

Please check your PM

Thanks.
[BLISS ROMS Development] jthomas1987:
Are the current releases offline?

Tried the last couple days to DL the current 10.0 Oreo-based release, but the download site is offline from what I can see.

Just checking that it isn't something on my end, not trying to be a nag or anything like that.

I have 7.2 installed on my Lenovo Flex 14" in a triple boot setup (Win10, Voyager Linux, and Bliss 7.2), and everything on the 7.2 build works great. Get about 5 hours run time with it on a full battery. Was just thinking about trying out the 10.0 build is all.

Keep up the great work on this OS and hope it stays around for a long time. I could see it on x86 systems as a direct competitor to Chrome OS on Chrome books.
[BLISS ROMS Development] 4r44444:
setparams 'BlissOS 10.1 Live' 'Live' 'quiet'

shift 2
savedefault
set root=$android
linux $kdir/kernel root=/dev/ram0 androidboot.selinux=permi\
ssive $src $@
initrd $kdir/initrd.img

---------- Post added at 14:29 ---------- Previous post was at 14:15 ----------

After add in the 'SETUPWIZARD=0' command and pressing F10 screen turns black, for 0,01 seconds white and than tablet restarts and it returns to GRUB with the boot options. After restart pressing Live Boot or Installation the same happens again. It also does not save the "SETUPWIZARD=0" command and I have to type it again.
[BLISS ROMS Development] greg_mp:
Hello guys, thanks again for your good work. I didn't test the latest build on my galaxy book, as I get a "connection refused" on the blissroms website. Any idea?