yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] bethnesbitt:
This works, thanks. Noticed that it is giving me the corrected amount of internal storage, but, reading it odd. Says I am using 688gb of 0.91 tb. Hopefully apps will be supported soon, it has been how many years now?
[BLISS ROMS Development] wuhoatu:
I install Bliss 8.0 Alpha to Intel Compute Stick but it is rootless. Root update binary unsucessfully. Any help to get it rooted? Many THX.
[BLISS ROMS Development] electrikjesus:
I tried to post on the release post that you shouldn't try updating the surface binary for now...
[BLISS ROMS Development] electrikjesus:
If you read a few posts above yours, you'll find that we have moved to a private git server due to commercial projects abusing our work.

Also, If you gauge our past version of Bliss-x86 for nougat, you'll see that we add quite a bit once we are out of alpha/beta. So please be patient unless you are lending a hand in development ;)
[BLISS ROMS Development] doddos920:
how to install xposed on Bliss x86 base Android Nougat 7.1 kernel 4.9 64bit?
[BLISS ROMS Development] bethnesbitt:
HDMI

Have a Dell ST2220T touch, touch works fine, sound is acting up. I am receiving notification sounds, but in app sound does not work. Hooked the monitor up using VGA, sound works fine this way, only time the issue arises is when the Monitor is connected in the video card via HDMI.

Tested on both the monitor and my 32 inch screptre, so it is a HDMI issue, any ideas?
[BLISS ROMS Development] vel_tins:
Any chance to get a 32bit build? For some reasons, the 64bit builds won't boot on my Core 2 Duo T5200, even the laptop is capable to run Windows 64bit...
[BLISS ROMS Development] ElfinJNoty:
We will not be providing support for 32bit devices for non commercial purposes. It is too much work to maintain for something Google themselves has dropped support for.

The last stable 32bit release which would have been Nougat, can be found on our AndroidFileHost archive. But these previous builds as well are unsupported by Team Bliss
[BLISS ROMS Development] vel_tins:
Ok, never mind.

Nougat is good enough for a little bit "bedroom video-streaming".

Keep up the good work!
[BLISS ROMS Development] greg_mp:
Hello team,

Nice work here. I am trying to install android on my samsung galaxy book (12", core I5, 4gb ram, wifi but no lte) from USB stick or on SD card and all latest stable or bleeding edge version can start fine but the "first run" app that is getting time zone and google account is crash looping, and then we are never able to go farther.

The display is fine, and the touch is working. I have not seen orientation working from gyro, but it may be early in the first run step.

I have run a standard version of nougat here:

https://www.fosshub.com/Android-x86.html

It is not crashing at the same point. Actually first run is fine, but wifi is not working, it "never" switches on. BT is working, I don't think GPS is up, I have not succeed to get network access, as there is just usb type C port. I would need a wifi usb key.

If you have a fix that would be great.

I have the galaxy book 12 which is great as mobility laptop, but I sometimes need android apps and have them on galaxy book would spare me buying another tablet.
[BLISS ROMS Development] electrikjesus:
We have uploaded a couple more test builds to our bleeding-edge folder. Changes to gapps, kernel (added patches for some touchscreens, rotation, added support for Chromebooks, etc), install and init scripts, and many more.

Same issues for some PCs and Bluetooth. Check the previous release posts for details on installing and using old modprobe method.
[BLISS ROMS Development] calj17:
Easy Install For Bliss-x86 8 and 10 MBR 64bit

Could you please provide easy installer for bliss x86 versions 8 and 10 for MBR?

Thank you very much for your hard work
[BLISS ROMS Development] bfmetcalf:
what is the difference in the 2 downloads?
[BLISS ROMS Development] xfaethorx:
If I'm following it correctly the one with ts in the name before ax86 is touchscreen, might be wrong but I'm about to try that one on my Chuwi Hi10 Pro. Managed to get oreo to boot but the rotation detection was arse about face,the touchscreen didn't work , bluetooth crashed and sound didn't work. BUT that aside it booted, I could get onto youtube and stream a video perfectly and in full screen just without sound. I'm fully supporting anything that might bring these devices out of the Android 5.1 Jail they are stuck in at the minute.

For the record the *ts-ax86 variant didn't boot on my Chuwi HI10 Pro but the other variant did.

Results are:

I Still got screwed up rotation and in this variant the tablet doesn't appear to detect any rotation but portrait no matter what direction the tablet is turned in.

Wifi worked out of the box.

This time the bluetooth didn't crash, I could turn it on find my headphones and successfully stream a random you tube video plus audio!

Still no sound from the onboard audio device

Touchscreen is detected and one gesture appears to work where a diagonal swipe downward from a little to the right of the middle of the screen to the bottom right hand corner causes the application tray to be launched. After that though nothing else seems to work. I was unable to launch an app without a mouse and due to the screen rotation issue that was also arse about face when trying to move it.

All this aside the working bluetooth is good progress and a little bit of touchscreen action is a good start!
[BLISS ROMS Development] bfmetcalf:
I had to use the one without the ts to get it to boot. Running awesome so far, haven't tried out Bluetooth at all but everything else seems to work fine. I do have rotation working, but it is inverted. Anybody know a way to invert the rotation? I can lock it in a certain orientation, but that's it.
[BLISS ROMS Development] Rydzu033:
Hi, I have ASUS GL503VD and in almost every version of Android keyboard is not working(backlight and input). In Y50-70 all was it good. I do not know why this is not working maybe because specififc drivers or something else. Even in Phoenix os is the same situation. Only in one version of Bliss rom x86 the keyboard was working but i do not remember which one it was and the system was giving fc's.
[BLISS ROMS Development] tobad:
i experienced the same! so i think TS stand for Terminal Start ;)

the rotation is inverted with my machine:

DELL Venue 11 Pro 7130

CPU: Intel i5-4300Y

GPU: Intel(R) HD Graphics 4200

if you need more specs, tell me how and i will sum them up

greetings
[BLISS ROMS Development] bfmetcalf:
Oh yeah, mine is a Dell Inspiron 7348
[BLISS ROMS Development] tobad:
to invert the rotation we have to modify the init.sh (system.sfs\etc\init.sh)

something like this:

function init_hal_sensors()
{
...
set_property hal.sensors.iio.accel.matrix 1,0,0,0,-1,0,0,0,-1 (dont know which values)
...
}

but i dont know how to modify the init.sh within the system.sfs.

the only precedure that i know was with extracting the sytstem.img from the system.sfs. but in the beta release there is a other filesystem format.

EDIT:

i remember another procedure. mount the system.sfs in linux and modify the init.sh.

(https://xdaforums.com/showpost.php?p=74861706&postcount=1196)
[BLISS ROMS Development] bfmetcalf:
If you could let me know which line you edit and what you come up with. My daughter is just waking up from her nap so I'll have to stop messing with this for a while. Thanks for the updates though. I do know how to edit it on my Linux system already.
[BLISS ROMS Development] electrikjesus:
Check this post for help there: https://groups.google.com/forum/#!topic/android-x86/u5bbpB_TMqg
[BLISS ROMS Development] bfmetcalf:
Gotta say [MENTION=928479]electrikjesus[/MENTION], this is a very good build. Really runs nice and most of my apps are working well. Many thanks for the hard work
[BLISS ROMS Development] electrikjesus:
You are correct. ts stands for touchscreen, for this kernel, it was another attempt at getting IPTS functional.
[BLISS ROMS Development] avalanche99:
Hi.

I got a Asus T102ha tablet with a Intel Cherry Trail CPU.

I nearly installed all the rom builds on the tablet with the easy installer, but unfortunately I only get Sound on 2 Roms, Bliss v7.2 with 4.12 kernel and on the v8.0 built.

V10 with 4.9.54 doesn't start, it only starts on old modprobe (1844), no sound, no soind on jack, no screen rotation even with an app.

Bliss v10 (1718) only starts on nomodset.

But some apps I really love start on v10 and not on v7.2

Can I try something to get Sound an screen rotation working on bliss v10?

Could it be possible to get the 4.12 kernel functions in the 4.9.54 kernel of the v10 bliss rom.

I really want to get android on this tab.

Kind regards

avalanche99
[BLISS ROMS Development] xfaethorx:
Cool :D. I couldn't get that version to boot past the console. It didn't launch the loading screen or anything; it just sat at the console. I'd have been interested to see if that version made the touchscreen work on my target device.

Thanks for your efforts.
[BLISS ROMS Development] Shironomia:
Hello,

I'm following the guide "Custom Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit)", at the end it says I have to extract the system.img out of the system.sfs, but when I try to extract the system.img out of the system.sfs in the newest Bliss v10 .iso, there's no system.img inside. Instead I find all the files that are supposed to be inside of the system.img.. but right inside system.sfs.

Is it supposed to be this way and a mistake in the guide, or is there supposed to be a system.img inside?

Thanks for the help.
[BLISS ROMS Development] bfmetcalf:
That was for the older builds. For v8 and v10 there is no system.img inside. I just used the system.sfs as is and it is working fine.
[BLISS ROMS Development] greg_mp:
Hello,

I have tried this latest build, but they all have the same issues as previous ones: The wifi is not working on a galaxy book. The wifi card is an atheros and from the dmesg, it looks like the firmware load is not well accepted. Actually the wifi board is an Atheros QCA61x4a.

And btw the boot logo doesn't look really good. galaxy boot has core I5 and integrated graphics, and I didn't try the no-hw acceleration boot option.
[BLISS ROMS Development] avalanche99:
Hi.

Today I also tried the udoo builts on my asus t102ha.

Only

Bliss-v7.2-android_x86_64-OFFICIAL-20170907-0021_udoo-x86_01.img is booting but no sound!

Screen rotation control app is working, bluetoth is working an even the apps I need are working.

But no sound :crying:

Can someone help me to get one built working.
[BLISS ROMS Development] DigitalMD:
notification for any USB drives or SD cards

Thanks to the Bliss team for the hard work.

I am running the current Android 8 build (12-Jan) on my Acer Spin 1 and everything works very nicely. I run Bliss installed on a UBS 3 flash drive.

One anomaly I did notice that is different from Android 7 builds. I get a notification for any USB drives or SD cards that they are corrupt and if I click on it, it wants for reformat the drive regardless of whether I choose "portable storage" or the other option. I don't want to format the devices.

The Android 7 builds would allow access to SD cards and USB devices as portable storage without issue.

This may be a "feature" of Android 8 and not a problem with Bliss, I don't know.
[BLISS ROMS Development] electrikjesus:
No, I'll have to correct that then, it is now just a .sfs file. You should be able to extract that to a folder though
[BLISS ROMS Development] ubuntuh:
Hi every body . i have to admit that i'm a total noob in linux and commands but i want to run android 8 on my 64bit pc. I wrote the stick with rufus but when i chose the usb in bootmenu there is just a black screen with un underline cursor. I deduced that my efi has problems to start the grub. Anybody who can help me please?
[BLISS ROMS Development] calj17:
what is the difference between the 2 bliss os android x86 10 betas?

what is the diferrence between these 2 versions?

Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1718android_x86_64_k4.9.54-ga-px-ts-ax86.iso

Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1844android_x86_64_k4.9.54-ga-px-ax86.iso
[BLISS ROMS Development] DigitalMD:
Honestly dude .... this is answered not 8 post back from yours.....

https://xdaforums.com/showpost.php?p=75199104&postcount=1303
[BLISS ROMS Development] rjbad1100:
Looks clean. Gonna install tonight on my Surface pro 3. Just to make sure: Does the OS support OTA updates for fixes or no?
[BLISS ROMS Development] Miustone:
No, and avoid the "ts" Version of the latest Builds. It isn't booting on My Surface Pro 3 and the other Version has no Touch... Just saying :cowboy:
[BLISS ROMS Development] primus33:
Hi all, the build "Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1718android_x86_64_k4.9.54-ga-px-ts-ax86.iso" works very well on my Asus UX360CAK including touchscreen, sound, touchpad, etc.... The only thing i didn't tested is accelerometer for rotating screen & touchpanel on tablet mod.

Specs of Asus UX360CAK = CPU i5-7Y54 (Kaby Lake Low Voltage passive cooling), CFX Intel HD 615, RAM 4Go, SSD M2 for storage & Touchscreen Panel and 13,3 Full HD LCD. Thanks again electrikjesus & Bliss Team for your work :).
[BLISS ROMS Development] thebestofall007:
Just downloaded "Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1718android_x86_64_k4.9.54-ga-px-ts-ax86.iso", made a bootable USB with Multisystem under Ubuntu 16.04, booted it up on my Panasonic Toughbook CF-74, and the boot stops at a "root@x86-64: / #" console prompt or something like that. This has been the issue with every attempt to boot Android-x86 Oreo, or anything based on it, on this laptop.

A possible issue is that Android Oreo has a driver issue (or lack of drivers) with certain processors or something like that. Am I correct, and is there a workaround to this? Could someone fill me in on this, please?
[BLISS ROMS Development] ElfinJNoty:
Have you made necessary changes to grub entry for 8.x builds? Which have been explained in previous posts by [MENTION=928479]electrikjesus[/MENTION] with the links for recent builds
[BLISS ROMS Development] thebestofall007:
No, but I've also had this same issue with Phoenix OS, Remix OS, as well as vanilla Android x86 Oreo.
[BLISS ROMS Development] bfmetcalf:
The -ts build did that for me as well. I flashed the other build and it booted fine. I'm on a Dell 7348 2 in 1 laptop.
[BLISS ROMS Development] rjbad1100:
Hey everyone! So I originally got this working on my SP3 for about 2 hours, and removed it so I can also try Phoenix OS to do a comparison. I liked this build better in regards to performance (Fans keep running when PhoenixOS is installed) so I wanted to reinstall this as my main x86 ROM.

I'm doing the stable version currently since I plan to make a hard switch to it. However, this time when I try to install it, I keep getting a mounting error. It reads:

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

Error Executing C:\Windows\System32\Mountvol.exe with Args: Error output:

"The System cannot find the file specified"

To note again: I've had this installed before but removed it using Windows 10. Now I'm trying to install it again on the C:\ drive using Windows again. Does anyone know what's going on? Would love to get this back up and running.
[BLISS ROMS Development] snok:
Hi, i got a SurfacePro 3 and I got some issues with audio.

Youtube sounds good, system notifications sounds good. I got a problem with Roseta Stone app, all app sounds are working ok but audio exaples (talking people) are like super slow. It's like the app uses another hardware to reproduce it and then it sounds bad.
[BLISS ROMS Development] trycatch:
Hi there, i insttalled latest oreo beta to lenovo yoga convertable (x86, i7) and i can say that this build is fastest bliss on this machine.... thanks for developers firstly...

but i have a strange issue here, auto rotation strart to work with this build; bu it works +180 degree. i installed rotation control app and disabled auto rotale, it almost works but some online tv apps show video +180 degree...

is there any quick solution for disable auto rotation or correct it ?
[BLISS ROMS Development] thebestofall007:
I'm having the same issue with either build, sadly. What's weird is that my laptop has worked fine with nougat and marshmallow based ROMs.
[BLISS ROMS Development] avalanche99:
Hi I tried all the bulits now in the download section and the only one which is working on my Asus T102ha ist his one:

Bliss-v7.2-android_x86_64-OFFICIAL-20171024-1354_k4.12_cb_ipts.iso 28.10.2017 04:02747.6 MB

Screen rotation is working with rotation control app and this is ok for me, but i have 3 issues:

- no sound on headphone

- sd card is not detected, not in FAT nor in NTFS file format in the sd slot, but no problem in an USB card reader.

- Need to update SU-binary but I even with SuperSu I don't have the right to copy files into /system/xbin

I really need some help to fix the su-binary and to get my sd card detected.

Kind regards

avalanche99
[BLISS ROMS Development] calj17:
installation failed using Easy Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit)

I have tried install Bliss-v10.0-PC_Beta--OFFICIAL-20180112-1844android_x86_64_k4.9.54-ga-px-ax86 using Easy Install For Bliss-x86 8.x/10.x UEFI/ESP (64bit) selected the iso and during install process it shows me the error message and told me to report the error to developer. I had no issues installing the previous beta version of bliss 10.0 with the easy installer, but with this last build it gave me error during the install process in my Razer Blade 2016 1060gtx touchscreen. Should the easy installer for Bliss-x86 8.x/10.x UEFI/ESP (64bit) be updated or fixed?
[BLISS ROMS Development] electrikjesus:
make sure that you are not using the installer for MBR on a UEFI machine, otherwise you might damage your ability to boot into Windows correctly
[BLISS ROMS Development] electrikjesus:
no, you likely just didn't hit the clean up button. you will need to do that if you use the easy installer back to back, otherwise, please check the update/upgrade instructions on the second post to save yourself some headaches.
[BLISS ROMS Development] electrikjesus:
we will not be doing any further development to Bliss 7. whatever. Since we are such a small team all of our development has been moved to Oreo.
[BLISS ROMS Development] electrikjesus:
Please search the Android-x86 Google groups for what you need to add to the init.rc for your device, then submit a pull request to our GitHub
[BLISS ROMS Development] avalanche99:
Ok, thank you.

But on any Oreo built I have more big issues (no sound on Speakers an on headphone jack, no screen rotation even with rotation control app and also no sdcrad)

Which one is best for my asus T102HA with Atom z8350 CPU,

Intel STT Audio device; Realtek I2S Audio Codec, Intel SD-Hostcontroller, HID Sensor collection.

And how can I solve this issues?

Kind regards

avalanche99
[BLISS ROMS Development] electrikjesus:
we are still in beta, so start with lowering your expectations...
[BLISS ROMS Development] calj17:
I Was able to install the last bliss 10.0 beta in my razer blade. Got 2 issues. First everytime I start the os google play services crash and stop working. Second When I push power off button at the laptop it does not turn off the notebook, it goes to sleep mode and I have to press and hold turn off button in order to shut down the notebook. Sound works wifi works and razer blade touchscreen works. Thanks for your great work

Enviado do meu iPad usando Tapatalk
[BLISS ROMS Development] electrikjesus:
This has been mentioned at least 20+ times in this thread, but Google Play store will crash as long as there is no data or wifi connection. establish that first, then you can use play store fine for now.
[BLISS ROMS Development] calj17:
Ok sorry. So the olny problem to be solved for my razer blade is that it does not shut down when I press the button. I have to press and hold until notebook shuts down

Enviado do meu iPhone usando Tapatalk
[BLISS ROMS Development] thoryuuka:
Tried to install today -- but couldn't get passed the screen for partitioning as it doesn't seem to recognize logitech wireless keyboards in the installer.

It looks like this is because the logitech hpp driver moved to its own kernel driver a while ago.

Would it be possible to (instead of having it as a module) have the logitech drivers compiled into the kernel?

It looks like the installer is not loading modules :(
[BLISS ROMS Development] urby66:
Partition scheme for Dell Venue 5130 standalone install

Hello Colleagues,

I would like to install the "Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9" version to my Dell Venue 5130.

The live mode seems working well, so I would like to install to the HDD. The disk is blank.

My question would be how can I set the partitions to make is bootable standalone?

Thanks.
[BLISS ROMS Development] linusdan:
About download: So slow...
[BLISS ROMS Development] pauliusval99:
I tried to boot this on my Lenovo Yoga 720, i5-7300HQ. After selecting an option in grub (live or install), it gets stuck with a black screen and a blinking cursor. The activity LED on my flash drive doesn't even light up after that. Could this be a problem with rufus? Should I provide logs or something? (dunno where they're located)
[BLISS ROMS Development] mikekoz:
I have tried installing this on two different laptops, a Dell and a Sony 2 in 1, and the installer quits after about 30 seconds on both with the same error. It will start putting files in the AndroidOS folder it creates, then deletes them after it quits. I cannot tell you all the exact error message or upload a log file right now as I am at work, but thought this would be easy! I use Remix OS on a few laptops at home and it installs and runs almost flawlessly on both! I am doing the "easy" install for UEFI. Will post more info this eve.

Edit: I tried all three ISO files that were posted in the folder labelled "stable", just FYI.
[BLISS ROMS Development] namitutonka:
Bliss - X86 Support....this thread or telegram?

I'm both subscribed to this thread, and am the 98th person to have joined Bliss - x 86 Support on Telegram.

It seems like Telegram is primarily intended for developer to developer communication. This is my thought on what Blissx86 Telegram is supposed to be. Although there are tons of posts there (mine included) which obviously come from non-developers. [MENTION=928479]electrikjesus[/MENTION], Jon, your patience and forebearance on Telegram towards non-developers like myself, is phenomenal. Thank you again. But, given a preference, would it lessen your inconvenience (and other serious Bliss86 developers) to relegate all non-developer's input to this XDA thread? Wouldn't it be better to reserve Bliss86 Telegram use to developers only? That way you serious guys wouldn't repeatedly be spending a lot of time on Telegram responding to posts that I think should rather be on this thread. Many here are end users, wanting to implement the results of your hard work and knowledge with a simple install. Likewise, the many who like it simple, tend toward instant 'customer' gratification; so the many don't read the entire thread, and a bunch of them don't search before posting a question. I would think its a bit tiresome to deal with as a developer. Wouldn't you rather have Telegram uncluttered, and keeping it so by directing non-developer posts to this XDA thread?

Non-developers could be advised just to listen and watch Telegram. But post only on XDA.
[BLISS ROMS Development] electrikjesus:
You've got to understand the Bliss x86 telegram group is mostly 4 question and answers. yes the only ones that come to there are the technically inclined users, asking technical questions and the others we usually turn to this thread. On top of that I also have to deal with about 20 other threads for Bliss and development
[BLISS ROMS Development] electrikjesus:
You should expect the same amount of work to go into the answers we provide you here then. Also, We are just a small few developers doing this in our free time, and not on the payroll for a large company like Jide. so you should consider lowering your expectations there as well.