yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] hgblob:
Great!

I did some testing and at boot time all the alsa mixers are set to 100% percent. I checked some audio recording tools and the signal level is way too big, that's why it's so distorted. If I lower the level to around 50 using alsa_amixer -c 1 .... then the sound level is much better, less distorsions.

Now I'm not sure how it's done in Android, we could of course have a shell script that runs at boot time to do this.
[BLISS ROMS Development] electrikjesus:
Starting at line 386 is where we would modify the initial alsa settings I think: https://github.com/BlissRoms-x86/device_generic_common/blob/n7.1-x86/init.sh#L386 Mic input on my other devices is also a bit higher than it needs to be I think, so setting that to 50%-70% might help more than just the SP3's
[BLISS ROMS Development] youling257:
you need care	f=/system/etc/alsa/$(cat /proc/asound/card$c/id).state

if [ -e $f ]; then

alsa_ctl -f $f restore $c

use /system/etc/alsa/chtrt5645.state for Cherry trail surface 3 .

i use my perfect /system/etc/alsa/bytcrrt5640.state for z3735f ，everything work well .

---------- Post added at 01:07 PM ---------- Previous post was at 12:56 PM ----------

it must 0db . such as

}

control.166 {

iface MIXER

name 'IN Capture Volume'

value.0 23

value.1 23

comment {

access 'read write'

type INTEGER

count 2

range '0 - 31'

dbmin -3450

dbmax 1200

dbvalue.0 0

dbvalue.1 0

}

}

}

control.168 {

iface MIXER

name 'ADC Capture Volume'

value.0 47

value.1 47

comment {

access 'read write'

type INTEGER

count 2

range '0 - 127'

dbmin -17625

dbmax 30000

dbvalue.0 0

dbvalue.1 0

}

}
[BLISS ROMS Development] wilbar:
[MENTION=2670513]rajnallan[/MENTION],

could you please describe the way to use the remix installer. The method explained on page 20 does not function for me, same to the "Easy way" described in the OP.

THX in advance.
[BLISS ROMS Development] franzli:
On the latest bleeding edge version, backlight control does not work on Dell Venue 8 Pro (cherry trail), but it does work on versions from 3.3.17 and 18.4.17.

I suspect maybe you forgot to apply some patches for the Surface 3 (non pro) to the kernel, since I recently found out that a special patched kernel for the surface 3 makes Linux work really well on the DV8P (including backlight).

Ps: ok, things seem to be even more confusing. Is was able to control the backlight on the 1804 build booting from USB, but when I install it I cannot control brightness anymore. Any ideas why that might be?
[BLISS ROMS Development] andythegreat:
Any builds that would support wifi, sound and touchscreen for cherrytrail devices ?
[BLISS ROMS Development] electrikjesus:
UPDATE - 01.13.17 - I have started working on adding kernel-4.10 as well as mesa 13.10 to the builds. The first one available is the 32bit. Running nice on my machine, so it can now be found in the AFH folder. 64bit is building still, so I will update later with links.
[BLISS ROMS Development] youling257:
[MENTION=928479]electrikjesus[/MENTION] ，do you know 0001-DO-NOT-MERGE-temporary-workaround-for-Fds-whitelist-.patch https://groups.google.com/d/msg/android-x86/BZZhufU_e6o/rnGszNjUDwAJ ?
[BLISS ROMS Development] youling257:
[MENTION=928479]electrikjesus[/MENTION] ，7.1.1 must add 0001-DO-NOT-MERGE-temporary-workaround-for-Fds-whitelist-.patch ，then can boot on debug mode .
[BLISS ROMS Development] lollyjay:
I installed bliss-x86_64_n7.1.1_01.11.17_r12_02_ej.iso on a Lenovo ThinkPad Twist 33476WU from USB. Very impressive! Smooth and quick. A few deficiencies are:

1. WiFi does not reconnect after sleep or boot; must be reconnected manually

2. Microphone is not functioning EDIT: IT DOES WORK

3. Screen rotation is not functioning natively; can be forced using an app

Thanks for your work. I'm looking forward to testing future alpha builds
[BLISS ROMS Development] mediawiz:
I tried installing Bliss for X86 on my Intel tablet. Seems to work pretty well, though the display/graphics driver could be improved to better support Intel HD/Iris graphics.

One thing... It says the SU binary needs to be updated. How do I update the Super SU binary on Android-x86?
[BLISS ROMS Development] lollyjay:
SuperSU is in Settings
[BLISS ROMS Development] harkaman:
[MENTION=2426389]mediawiz[/MENTION] . To update the Super SU binary, juct clickt su and update as normal And reboot
[BLISS ROMS Development] mediawiz:
Yes. I know where the Super SU settings are… the SU binary update won't work. It fails.

---------- Post added at 11:39 PM ---------- Previous post was at 11:39 PM ----------

It fails.
[BLISS ROMS Development] harkaman:
[MENTION=2426389]mediawiz[/MENTION] How did you install n7.1.1?
[BLISS ROMS Development] mediawiz:
I did the following:

- copied all of the files from the ISO to a "Bliss" folder on my hard drive (the same drive Win10 is installed on)

- created a blank/formatted "data.img" file, and put it in the "Bliss" folder

- then configured Grub to load the Android from the "Bliss" folder (with the appropriate params)

- rebooted the system to load Bliss via Grub

This seems to work fine with all the other Android-x86 based ROMs that I have tried (including: RemixOS, PhoenixOS, Cyanogen-x86).
[BLISS ROMS Development] electrikjesus:
I would love it if you could post your grub config for us to see what you're loading there
[BLISS ROMS Development] danieljenkin:
Looks great, thanks for posting
[BLISS ROMS Development] jrk190:
This is probably one of the best working builds posted yet.

The 4.0 kernel build wouldn't boot on my Asus Vivotab Note. The included pen works.

Suspend is VERY close to working. The screen is still lit, but black. It's SO close.

Wifi cuts out. Weird.

Brightness can't change.

But it's definitely progress.
[BLISS ROMS Development] electrikjesus:
The next releases will be a two branch release. [Stable] release will include kernel-4.4 & mesa-13.03, and will roll along all the usual Bliss updates with it. The stable branch will also include most of the updates that Android-x86 project pushes, once they've been tested in the [Unstable] branch of releases, which will include the newer kernel-4.10 variants and newer mesa variants (13.10-17.0 so far) as well, much of my testing will be on this branch, so there are good chances you will get previews of what's to come, and what's not to come ;)

So, why do it this way? Cause we seem to have a loving community of x86 users here who know their stuff pretty well, and I want to share this experience with as many as possible. Letting the veteran users test on the unstable branch will allow our stable branch to be that much more ;) So who all's with me?
[BLISS ROMS Development] jrk190:
What can we do to help you guys get things that are broke working?

My running list of bugs:

Sound

Cameras

Suspend

Wi-Fi spotty

The suspend issue was fixed for baytrail tablets on Ubuntu, as well as sound. They weren't ideal, but worked.

The camera has been a consistent issue with all tablet devices so far.

I think it's awesome to have a ROM team on the case. Seems toe that they typically get a lot of work done, though I won't discount the Android X86 team at all for their work. I just don't see windows working well for a tablet, and would actually get a lot of use outta it with Android on it, but without suspend and sound, that's kind of a deal breaker. I can maybe deal with no cameras.
[BLISS ROMS Development] electrikjesus:
Suspend, sound, rotation, video, etc are all going to be different on a per-PC basis. For instance, on one of my test machines, everything works but video. On another everything but rotation works. So its going to vary per machine. We do try and find as many drivers and firmware as possible, but its not gonna hit all at once ;)
[BLISS ROMS Development] lollyjay:
I installed bliss-x86_64_n7.1.1_01.11.17_r12_02_ej.iso on one of my test laptops. It boots up fine but does not detect WiFi. Most likely it is not friendly with the hardware BCM43228

(the notorious Broadcom chip)

---------- Post added at 07:35 PM ---------- Previous post was at 07:25 PM ----------

So far for my test laptops the bliss-x86_64_n7.1.1_01.11.17_r12_02_ej.iso build is fully functional with the minor exception of required manual reconnect to WiFi after sleep or boot. Once connected, WiFi is stable and stays connected. I'm treating this build as a beta :o
[BLISS ROMS Development] electrikjesus:
UPDATES!!

I am uploading a couple [Unstable] builds for you all now. Info on them can be found below:

bliss-x86_64_n7.1.1r12_01.16.17_k-4.10rc4_OMS.iso Is a 64bit build, using kernel-4.10rc4 w/ a few additions, and it is also using mesa-13.03 for stability. Touchscreen issues are almost gone on my tests, trackpad isn't functioning on my SP3 though. Wifi also cuts out and doesn't reconnect right sometimes. All a work in progress.

bliss-x86_n7.1.1r12_kernel-4.10_mesa-17.0.dev.iso is a 32bit build, also using kernel4.10rc4 w/ a few additions, and paired up with the very green mesa-17.0. This build does have a few issues, but hardware support is getting there for many 32bit machines. Worth a try if everything else doesn't work. This will likely have the same issues as the 64 bit build above.

Both of these builds also include some changes for houdini(app compatibility), so there should be less FC's on them both.
[BLISS ROMS Development] youling257:
do you add 0001-DO-NOT-MERGE-temporary-workaround-for-Fds-whitelist-.patch ?
[BLISS ROMS Development] electrikjesus:
Yes, I think I added that and maurossi's zygote patch as well.
[BLISS ROMS Development] franzli:
WiFi and touchscreen have been working on any bleeding edge build I've tried on the above mentioned Dell Venue 8 Pro (may also work on stable builds, just haven't tried). Only issues I found here are audio and backlight control as described in the post above (and physical buttons not working, but that seems to be a general issue).

Don't know if WiFi will work as easily in other cherrytrail devices though, as this one has an Intel card that is generally well supported by the kernel (as opposed to the realtek card used in most cherry trail devices).
[BLISS ROMS Development] electrikjesus:
UPDATE - 05/042017 - BLEEDING EDGE

Good morning everyone! I have a couple bleeding edge updates for you all today!! Both 32 & 64 bit :)

Updates include:

Redesign of About Phone with added About Bliss tab

Updated kernel to release version of linux kernel-4.11

Updates to both Taskbar app and Substratum/OMS

even more WiFi & Bluetooth issues fixed for many devices

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

Known Bugs:

- Changeling from AboutBliss not working

- reverse or 90° orientation on some touchscreens

Enjoy!!

https://downloads.blissroms.com/Bliss/Official/x86/
[BLISS ROMS Development] franzli:
Thanks a lot again!

Unfortunately, I still have the problem on the Dell Venue 8 Pro (cherry trail) that backlight control works if I run the live version from USB, but when I install to disk (using the easy method from op), the backlight is stuck on maximum. This happens with the latest version, but also the previous two (0424 and 0418) and an older version with the 4.10 kernel.

Any idea, why this night happen or is there any information I could provide that might help fixing?

I think a similar problem occurs on the Cube i7 book (with skylake 6y30 CPU), although I haven't tested that as extensively.

Apart from that, there get no audio output on the DV8P or the cube i7 book, even though at least the latter has audio output on Linux. Would logcats or sth like that be helpful?
[BLISS ROMS Development] FiendFyre:
Hey man, haven't heard much about the Surface Pro 4 lately, but I definitely appreciate all the work you've put in already. Here's a link I found for getting Debian working on the SP4 with the touchscreen drivers and everything, hopefully its useful.
[BLISS ROMS Development] ElfinJNoty:
Yes, of course...... Logs would be helpful
[BLISS ROMS Development] fastguy:
Hi [MENTION=928479]electrikjesus[/MENTION], I've installed the latest 64 bit and tried to install Crossover Android onto it to try to run Office 2010.

Installation is fine, but launching any installer does not work, I can get some logs if you like, or maybe you could give a try by downloading latest version from apkmirror and trying to run a simple installer like 7zip 9.2 .
[BLISS ROMS Development] youling257:
Fw :

Josh DuBois promotions@crossover.codeweavers.com

On 2017-04-05 at 23:06, youling 257 wrote:

> https://osdn.net/projects/android-x86/scm/git/manifest/ ，Android x86

> 7.1，crossover not working .

>

Ah, yes! This is correct. Unfortunately, we cannot support Android 7.x at this time.

We are working to be able to run on the version of Android 7 which is included in certain Chromebooks which have the Google Play Store (at this time, we don't run on those, either). Unfortunately, the work we are doing there will not carry over to other Android 7 machines.

The problem is that in Android N, Google implemented a new policy which restricted access to libraries up on which we rely (and which we had been able to use in prior versions of Android). It seems that starting in Android O, there will be a new public API which will allow us to do the same thing. That will leave Android N (7) as a gap where we lack the features we need.

So, I'm sorry about that - Android 7 won't work (unless you can convince the Android-x86 developers to give you a flag which will allow us to dlopen() libhardware.so). We simply don't have access to a key library which we need to run
[BLISS ROMS Development] fastguy:
Thanks a lot for this info. It's a pity indeed.
[BLISS ROMS Development] electrikjesus:
I've been working with their test program for a while trying to get crossover working correctly. It's related to KVM or one of the other virtual machine services I think, so I might test a couple kernels without it running. Since I have a limited amount of time to work on that specific application, it would be helpful if you could at least get some logs. I'm trying to help get a couple developers caught up to WTF we had to do to make this project tick.
[BLISS ROMS Development] fastguy:
Thanks. Actually two posts above, [MENTION=5550662]youling257[/MENTION] explained that Crossover not working is due to something Google has disabled in Nougat.

So I guess nothing you could do here unless you'd want to make a final marshmallow build ;) (I'll try your latest unsupported one)

On KVM, I'll be looking forward to having a kvm enabled kernel again. Thanks a lot!
[BLISS ROMS Development] electrikjesus:
That was what I'm talking about. They need to include a few things and the new sepolicy and restrictions within nougat make it hard. What we did with Substratum, is include ThemeInterfacer to handle the system level calls, but at first, even that had issues getting aapt & aopt to function. I could include the libraries they need for it to work on nougat, like I initially did for aapt, but they haven't really let us know what...
[BLISS ROMS Development] franzli:
In case anyone else runs into a similar issue, I've got a solution that works at least on my Venue 8 Pro (haven't tested the other device yet).

Instead of the east option from OP, I used the installation option from the USB stick in order to install to hard disk and formated the target partition as ext4. Now backlight control works just as well as it does on the live USB! Audio unfortunately still not working on the cherry trail Venue 8 Pro 5855, but this is probably a kernel issue (incidentally, sound works ok on the bay trail Venue 8 Pro 5830, even though the system seems awfully slow otherwise on the bay trail).

Maybe it might be helpful to put a hint in the OP that certain issues may be solved when using the USB installation method.
[BLISS ROMS Development] NotKaoDoro:
Does this have root access? I don't want root access as I am going through a plethora of android-x86 OSes to find one that works with F/GO out of the box. I'm aware of RemixOS, but I am looking for alternatives.
[BLISS ROMS Development] lollyjay:
The EDU versions do not have root
[BLISS ROMS Development] kobiandy:
Hello guys. I'm buying a dell venue 11 with intel atom z3770 2gb ram and 64gb emmc. I'd like to keep windows 10 on the emmc and install bliss x86 on an sd card. Will i be able to get a boot menu and smoothly choose an os without keyboard and is there any major issues with this tablet I'm about to purchase. Thank you in advance
[BLISS ROMS Development] electrikjesus:
You're going to have to wait till someone else chimes in. I personally have not tested Bliss-x86 with that device.
[BLISS ROMS Development] franzli:
Most baytrail devices I've heard about (and the few ones I tried to get Linux on) seem to be unable to boot from sd card, which is why people would normally have to install /boot into emmc when working with Linux (/and other party's of the filesystem can then go onto the sd card).

I haven't found a way to be able to split the android filesystem in a similar way - tried a bit to get the data partition to go on the SD card, but haven't found a way to make that work.

So what I ended up doing on the bay trail and cherry trail devices i'm trying was to set aside a couple gb on emmc for Bliss.

It's not running very smoothly on the baytrail Venue 8 Pro unfortunately, but i'd be curious to hear how the 11 is doing!

One thing I actually failed to test in my overview above was whether sd cards can be accessed on the devices. Might add that when I get a chance.
[BLISS ROMS Development] Stickypinkyfinger:
Hi

Don't know if I gone blind but in 7.1 for 64 bit pc, I was able to control sound through the settings but on the latest stable I don't have the option and most importantly, this rom don't have any sound.

Has it been missed out or am I going blind?
[BLISS ROMS Development] diaayousef:
Hi

I tried the latest bleeding edge (Bliss-v7.2-android_x86_64-OFFICIAL-20170504-0012) on my surface 3. The volume buttons and the power button do not work. The battery is always shown as charged to 100% and charging. It also does not rotate and the camera does not work.

for the latest stable version ( Bliss-v7.1-android_x86_64-OFFICIAL-20170402-1108_k4.4_01.iso ), the touch screen does not work

the only working version I found was ( Bliss-v7.1-android_x86_64-OFFICIAL-20170331-1607_k4.09_01.iso)

in this version, every thing worked except the camera and the microphone.

is that normal for surface 3 or did I do something wrong?
[BLISS ROMS Development] franzli:
I've mostly got the same issues (no buttons, no auto rotation, no camera) on bleeding edge on my venue 8 pro which also has a cherry trail platform (battery display seems a bit better there, I think it's not such on 100%though I don't know how accurate it is). I also don't have sound - do you get audio on the surface 3?

Thanks for the reference to the earlier version, might give that a try in the future!
[BLISS ROMS Development] diaayousef:
I fixed the sound issue by copying those files to /system/etc/alsa/

https:// drive .google .com/open?id=0B-le8_l90WMcWExnTURGTlc5bEdCZWs5cmxVeUZzTmdJampZ

https:// drive .google. com/open?id=0B-le8_l90WMcZEJDUTNKVWNJbk5DRmd4TUtZQ1VOX0FlZk0w

https:// drive .google. com/open?id=0B-le8_l90WMcZ3pnc3JoODJlWXRYY3BDTHc2VC1wcFEteDBV

I also found that the wifi keeps turning off in this version and does not turn on until I restart the surface

This version is also very slow compared to other versions and keeps restarting without any reason
[BLISS ROMS Development] franzli:
Thanks a lot, hope to find a moment this weekend to try this! Getting sound would be great and possibly make this fully usable for me!

I've also noticed the WiFi issue, seems to happen when you don't user the connection for a bit, so it seems like it goes to sleep and cannot wake up anymore.

Which version do you mean is very slow? The latest bleeding edge is surprisingly smooth for me on the cherry trail venue 8 pro - much smoother than on my other tablet with core m3 6y30!
[BLISS ROMS Development] youling257:
.state files from 7.1-rc0 https://www.fosshub.com/Android-x86.html by cwhuang，cwhuang has bay trail t100ta and Cherry trail surface 3
[BLISS ROMS Development] diaayousef:
I actually meant this version

Bliss-v7.1-android_x86_64-OFFICIAL-20170331-1607_k4.09_01.iso

Not the latest one

---------- Post added at 07:13 PM ---------- Previous post was at 07:10 PM ----------

Yes, I took those files from his build

His build is smooth but does not have the driver for rotating
[BLISS ROMS Development] franzli:
Interesting, I tried that build on the venue 8 pro cherry trail and it dies indeed seem to be running much slower (although I only ran geekbench from the live USB the multicore performance was horrible even for that, less than single core performance and below 1000 points). I also didn't get auto rotation, BUT this version had Bluetooth working in contrast to the current bleeding edge build! Would be great to get that back (and maybe a but more stable than on the 4.9 build), since this also allows at least a workaround for the audio not working - Bluetooth speaker worked alright! I've added a short note on this observation to my earlier overview post.

I tried getting the speakers to work on latest bleeding edge by copying the files mentioned above, but unfortunately audio still didn't work for me. Not sure if it would work on the older version with 4.9 kernel, since I didn't install that one.
[BLISS ROMS Development] will4958:
I apologize in advance if this has already been asked, but has anyone tried to install this ROM on a Chuwi tablet of any variety? I believe they're all x86 Baytrail-based running at least a quad-core Intel Atom. Mine is actually the Hi10 Plus dual boot running Windows 10 and Android, and I believe this ROM could be installed, but I thought I'd run by you folks here first. Thanks in advance.
[BLISS ROMS Development] rajnallan:
Need Help. I installed the latest Bliss version on my surface pro 3 using USB drive. After installation on a HDD partition I tried to boot back to windows I get this error as below:

setparams 'windows'

Search --file --no-floppy --set=root /EFI/Microsoft/Boot/bootmgfw.efi

chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi

I am not able to boot back to windows. When I try use the recover USB drive it does not boot through windows recovery but straight goes to the Grub screen where windwos is an option and when I select windows I get the above error. I looked in to the BIOS set up and it is correctly selected as USB-SSD. Please help.

Thanks
[BLISS ROMS Development] sk8223:
Seems like a good project, but I can't use the x86 EDU ROM because I can't disable Developer Options on it. I tried it as a Live USB and it keeps turning dev options back on after I toggle it off. Don't know why or if it's related to my USB (it's a super old Kingston 2 GB). Also, no power off or restart options for some reason. Don't know if this is normal behaviour or not. Running it on a Core M.

I guess I'll stick to rootless Remix OS for now even though it runs hot because I can run my games on it. The games I play check for root and dev options. I have to disable both. That's also why I'm looking into gaming on my old laptop rather than my phone. Though it seems like Bliss runs just as hot and uses the same amount of CPU when idle on 7.1 as Remix does on 6.0.1 (26%). Clocks are running at full 2.0GHz for some reason (they run from 0.8 to 1 Ghz on Windows 10). Wish there was a way to underclock without rooting.

Despite the high clock speed and heat issues, everything runs smoothly. As smoothly as Remix OS. I also get better brightness options with Bliss compared to Remix. But I don't know if it's worth running Android on this thing if it's going to be at the highest clock speeds possible even when idle. Wish there was more support for fanless computers. You'd think they'd be just fine on Android but Intel...

Anyway, thanks for adding to the Android x86 movement. Keep it up!
[BLISS ROMS Development] electrikjesus:
I would use a USB Linux variant to mount your uefi partition and check to see if the location is correct for your setup. The second post in this thread has a link to the Android-x86​ Projects documents for advanced assistance. We're using their installer ;)