yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] Ashwin Prabhunerurkar:
i have the same problem with surface pro 4

the bleeding edge build has problems formatting nvme drives and detecting android(the system.img is been looked for)

i tried original android x86 build

it works perfectly

but no touch
[BLISS ROMS Development] Lovelyven:
Thanks for the reply, so you did not install bliss but used the principal android x86 build. What version of it did you get working?
[BLISS ROMS Development] Ashwin Prabhunerurkar:
latest 7.1.2 build from android x86 website

---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------

the latest 7.1.2 build from android x86 website
[BLISS ROMS Development] Lovelyven:
Is there anyway to get the touch to work? Kinda sucks without touch. Or any way to get bliss up and running?
[BLISS ROMS Development] Basrawi96:
Hi is the black screen when play videos with nVidia cards fixed ?

I didn't try to install this rom on my pc

I faced this problem on android x86
[BLISS ROMS Development] naifaharsy:
Link broken?
[BLISS ROMS Development] ElfinJNoty:
Please check link for current builds in the Downloads section of OP. Download links working fine here
[BLISS ROMS Development] robocopvn:
My Dell XPS 13 9350 Skylake

Installing process is normal. However, in the boot, after choosing Android OS. It keeps showing Detecting android X86 and the dots are adding up, forever. Any idea how to fix it?
[BLISS ROMS Development] ilker4fun:
Will be there any support for samsung galaxy book? I really want to use android with touchscreen on my galaxy book. Thanks in advance
[BLISS ROMS Development] ZeroZorro:
After screening all those 1069 posts and googling (i mean googling a lot;) i still can't find a solution to get this working with an Intel GMA500 videocard (Asus EEE 1101ha). Picture is very distorted and I don't think only because of the 1366x768 resolution.

Is there any possible fix for this?

I also would settle for install on my Asus EEE 900 or even the 7004G version but there i got those endless dots piling up forever like stated in previous post.

If there is no hope for GMA500 to be supported by any AndroidX68 32bit Build i am afraid i'll have to stay with Winslows... :((

Thanks for any advise where to go with this...

Verstuurd vanaf mijn Z1 PRO met Tapatalk
[BLISS ROMS Development] franzli:
You could just give it a try with the live USB and report back, so that other people with the device (or crucially also people without the device) know the answer to this question. This might even help to pinpoint any bugs that might show up.
[BLISS ROMS Development] ilker4fun:
I will do it anyway but the reason why I am asking is that when an error occurs, this is an user error or OS error?.
[BLISS ROMS Development] ilker4fun:
I have tried Bliss OS on my galaxy book 10.6 with Intel Core M3-7Y30 CPU . Here we go:

* Both stable and bleeding edge with their latest version don't let me go though setup. Setup Wizard FC in the adding account screen.

* The good news is touch is working on latest bleeding edge version. Which is a big plus because I tried all other android x86 OS and my touchscreen worked wrong.(something like inverted)

* Wifi is not working.

* Finally, not also Bliss but also other OS show my screen in portrait mode. I tried some apps to force landscape mode on other OS but it didn't work.

* Because of portrait screen,my touchpad didn't work as expected on Bliss OS.

I hope [MENTION=928479]electrikjesus[/MENTION] . you can solve these problems in your future builds. You guys did awesome job. I am looking forward to use this OS on my galaxy book perfectly.

If devs need any help in terms of finding correct drivers for galaxy book, I would be glad to provide them.

Have a nice day all :)
[BLISS ROMS Development] franzli:
Great, thanks! For the FC you can skip the setup wizard by pressing e on the initial grub boot screen (where you've got the choice to stay normally, debug mode or install), and then add "SETUPWIZARD=0" (without the quotes) after "quiet" (line 3 or 4 I think).

As for WiFi, can you find out which WiFi card the galaxy book is using?

I also finally managed to give this a quick spin again, albeit not yet in my cherry trail DV8P. I tried the bay trail variant, which I think [MENTION=928479]electrikjesus[/MENTION] also has(?), with the latest stable build with 4.9 kernel. This one boots fine, but screen resolution seems to be detected wrong for some reason (looks a but like it's confusing horizontal and vertical resolution).

WiFi seems to drop very quickly still, sound seems to be working fine still. Wasn't able to test performance, as geekbench needs internet and my WiFi access had collapsed right after downloading geekbench ;p

I also tried the 4.12 kernel bleeding edge (not the oto-version) as well, but that one seemed to boot loop on my bay trail.

I tried the 4.12 on a Chuwi Hibook Pro as well, booted fine, WiFi and Bluetooth seemed to work (sound via Bluetooth also worked, though it was a bit scratchy, maybe due to the WiFi issues). Especially WiFi was a bit wonky however (this one was able to reconnect however, in contrast to the stable 4.9 build on my bay trail DV8Pro where I could find any WiFi any more after it had dropped). Touch screen didn't work for me on that version.

I also wanted to try the latest oto version that someone had reported to have working touch on another Chuwi tablet - however, the iso file I downloaded was not an efi image, at least that's what rufus told me. I also couldn't find a bootia32.efi or any other efi file on that iso, so not too surprising it didn't work. Is there any trick I'm overlooking?
[BLISS ROMS Development] electrikjesus:
The oto-installer .img file is an EFI image, AND it has updates to the 4.12 kernel for IPTS and Chromebooks, so that might work best for you

On a side note, does anyone have any ideas how we could get Chuwi to "donate" a couple devices to help further development here?
[BLISS ROMS Development] robocopvn:
My Dell XPS 13 9350 Skylake

Installing process is normal. However, in the boot, after choosing Android OS. It keeps showing Detecting android X86 and the dots are adding up, forever. Any idea how to fix it?

Thank you guys! PLEASE HELP ME !
[BLISS ROMS Development] franzli:
Ah, so for that build I need the img, not the iso, good to know. Will check that version once I find the time again!

Good point re a test device - it should actually be in their interest to see some active development on their devices and they do send free devices to reviewers (although it might actually be gearbest in most cases who send the review devices to YouTube channels etc for advertisement purposes). Not sure who to contact about that, but I guess one could try either directly with chuwi -as it would help their brand- or some retailer like gearbest/banggood etc. In either case they should be able to see the benefit, although the problem with many of these Chinese companies seems to be that they don't seem to care about development benefits of that source, witness their flat refusal to abide by the gpl and release their kernel modifications for example (I think chuwi is one such company, afaik they haven't published the kernel sources for the hibook pro either, which is why sine community roms available for some chuwi devices aren't available for that device).

One problem might be that these companies are just interested in seeking new devices, not in extending the usability of their devices beyond the short support period of their ancient roms.

Btw, not sure if any of the development undertaken here might be helpful: http://konstakang.com/devices/chuwi_vi10plus/CM13/

One other option might be to partner up with some review channel and see if they could donate some devices after reviewing them (in case they get them for free). Problem is that all the cherry trail devices are probably already a long time through those channels, as they're already quite old. They don't seem to offer dual boot in the new generation devices anymore, only either windows devices with Apollo lake or mediatek with android. Of course, this might make them more susceptible to supporting additional effort in getting dual boot android on the Apollo lake devices at least. Sorry, starting to ramble.
[BLISS ROMS Development] ilker4fun:
Your method works for bleeding edge 17.10.24. Not for the latest build because they don't have 'quite' word in there. So like I said, touch and TouchPad are working but in a inverted way. Do you know how to force landscape the screen? I think all of this inverted things are because of portrait mode.

Btw what device are you using atm?

Ik it is too much of question :) But I really want to make this work. Thanks

---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------

Are you planning to add galaxy book in your supported device list, sir? It would be awesome if you are able to do it.
[BLISS ROMS Development] dedaol:
A patch went into linux-4.14.0 that makes the goodix touchscreen driver usable on my Teclast x80h. Previously it lost events, e.g. screen keyboard keys got stuck. It would be nice if you could add the patch to the kernels you build.

That is the patch: https://git.kernel.org/pub/scm/linu...4&id=9b5db7aab4d6b66f84f5e147c87eff4fe8b48651

Do not worry about the Oreo issues. It barely runs on anything yet. Just do it when you have time and you feel like it, and stop when you feel stressed.
[BLISS ROMS Development] franzli:
You can still add the setupwizard line even if the quiet option is missing (in fact I often remove it as well, just gives you more output when booting), it should just be the line that's booting the kernel, I don't remember how exactly that starts.

About landscape, I'm not sure, although I vaguely remember that there may have been a kernel option. Maybe someone else can help out here? By inverted you mean that if you tap in the bottom left corner of the screen, it registers a tap in the bottom right?

To be honest, I'm not using bliss productively at the moment, because where Linux just works better for productivity and for entertainment things like sound and battery life (and in some cases stability) aren't quite what I'd like (particularly battery life is something I'm a bit obsessed about).

But I love seeing the progress over here and trying it out on some devices when I get the chance. Mostly I'm tinkering with the cherry trail Dell Venue 8 Pro 5855 (really like that tablet), but I've also got a Cube i7 book, which has somewhat similar hardware to your galaxy book I think (at least the m3 chipset that is) - that one actually worked quite well last time I tried, although I think battery life and Bluetooth were a bit problematic. Also still got the older bay trail Dell Venue 8 Pro - would love to convert that to android and give it to relatives, but unfortunately it's just not stable enough (or long lasting) yet -although it's great that this one's on board sound working!

And currently I've also got access to the Chuwi Hibook Pro which is why I gave that a spin.
[BLISS ROMS Development] boomerxyz:
I have a Surface 3 and when using the stylus to write, small chunks of hand written text vanishes every 10 seconds or so. Is there a way to fix this?
[BLISS ROMS Development] 2D-Kun:
My live USB was always not detected and i can't boot from it, but in windows/ ubuntu it was detected

---------- Post added at 03:20 PM ---------- Previous post was at 02:27 PM ----------

so i decided to use manual install, but im stucked at part 4, what do you copy mean the rest rest? do you mean all of the files inside of the iso? And which exact place do i need to place data.img?
[BLISS ROMS Development] nbaj2k:
I have a Lenovo 720, need to use the 'Custom Install For Bliss-x86 6.4/7.x UEFI/ESP (32bit or 64bit)' method since the Easy install doesn't work for me with my Bios.

So when I try to boot into Bliss x86, I get the following error

error: no such device : /AndroidOS/system.img

error: file '/AndroidOS/kernel' not found

unaligned pointed 0x2ded0d0

I'm guessing I somehowhaven't pointed it correctly to the system.img file. Could someone possibly help me with which step i'm missing? I'm wondering if the data.img file didn't create properly with RMXTools. When using that app is there anything particular I should be setting it to or importing a file first?

I appreciate any help and apologize for the questions!

-J
[BLISS ROMS Development] 2D-Kun:
Google play services keeps using my internet wtf
[BLISS ROMS Development] Basrawi96:
Hi

My specs

Core 2 duo e7400

Ram 4GB

GeForce GT430 4GB

I installed it with rufus and i installed it in hdd but it gets stuck at

A N D R O I D x86_64:/ #

If you need a log can you teach me how to get it from my machine
[BLISS ROMS Development] marfin777:
Is there a way to Disabling hibernation mode or lockscreen?

I'm pretty satisfied with the actual build. Thanks to the Developer(s) :good:

There's only one insignificant problem. The Wifi doesen't autoconnect at system-startup and it is disconnecting after several minutes.

The WiFi icon in the pull-down-options-menu is greyed and marked with a questionmark-symbol when it's disonnected.

I'm not sure, wheather it's an energy-saving-option or something similar of android, or if it's a part of my hardware, but i didn't found matching options.

I deactivated every setting I found for Energy-Saving.

Edit: Well. ok. I found the origin of this failure. It was the internal WiFi. I exchanged it to an external USB -WiFi Stick and this issue broke up.

But..: Is there an option to deactivate the hibernation-mode completely? (Or maybe to stay always active or to prevent the lockscreen?)

I only found a max time of 60 minutes waiting period for hibernation-mode.

Does anyone else have similar problems or a tip for me?

My specs:

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

HP Thin Client t620 (the x86 Version, not the ARM)
[BLISS ROMS Development] ssurell:
Just command prompt.

Same here Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9 on a HP2000 AMD. Also same result with Android-x86 CM 14.1-rc1 (cm-14.1-x86) (2017/11/15). This was using rufus in windows to make live usb, maybe dd in linux would work?
[BLISS ROMS Development] Basrawi96:
I installed official cm 14.1 I downloaded it from android-x86.org and it worked
[BLISS ROMS Development] ssurell:
But was it 64 or 32 bit?
[BLISS ROMS Development] Basrawi96:
64 bit copy
[BLISS ROMS Development] ssurell:
HP 2000 will only run 32 bit Android x86

I've spent all day trying distros of Android x86 to finally come to the conclusion my system will only work with 32 bit versions.

System: Host: cat-HP-2000-Notebook-PC Kernel: 4.10.0-13-generic x86_64 (64 bit gcc: 5.4.0)

Machine: System: Hewlett-Packard (portable) product: HP 2000 Notebook PC v: 0888110003305910000620100

Mobo: Hewlett-Packard model: 188B v: KBC Version 69.17 Bios: Insyde v: F.34 date: 05/22/2013

CPU: Dual core AMD E-300 APU with Radeon HD Graphics (-MCP-) cache: 1024 KB

flags: (lm nx sse sse2 sse3 sse4a ssse3 svm) bmips: 5190

clock speeds: max: 1300 MHz 1: 1114 MHz 2: 1114 MHz

Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6310] bus-ID: 00:01.0

Display Server: X.Org 1.18.4 drivers: ati,vesa (unloaded: fbdev,radeon) Resolution: 1368x768@0.00hz

GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

GLX Version: 3.0 Mesa 12.0.6 Direct Rendering: Yes

Audio: Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller bus-ID: 00:14.2

Card-2 Advanced Micro Devices [AMD/ATI] Wrestler HDMI Audio bus-ID: 00:01.1

Network: Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller port: 3000 bus-ID: 03:00.0

IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A

Card-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter port: 2000 bus-ID: 07:00.0

IF: N/A state: N/A mac: N/A

Bliss-v7.2-android_x86-OFFICIAL-20170703-0932_k4.4-b_m17.0.2_01 installed fine, but bluetooth would turn off and on every time I tried to pair with keyboard (generic bluetooth adapter previously working fine with other distros). Have LVDS disabled forcing HDMI out, but would like sound and mic through laptop if possible.
[BLISS ROMS Development] beverlykho:
Xposed installation error

Hi,

Finally got Bliss running on my Surface Pro 3. But when I tried installing Xposed, it gives any error, namely - tmp-mksh: syntax error: ';&' unexpected.

What did I do wrong?

Thanks in advance.
[BLISS ROMS Development] electrikjesus:
You likely tried to install Xposed onto Nougat (Bliss 7.2) instead of marshmallow (Bliss 6.4)

Second post reads:

Bliss-x86 6.4 Xposed Install Instructions (32bit or 64bit):...
[BLISS ROMS Development] franzli:
Finally managed to try installing on the cherry trail Dell V8P.

The latest bleeding edge (1102 and 03) runs OK in live, but I haven't been able to install it, neither with the windows tool nor with the installer from the live USB. I was able to install the previous version (1024 I think) using the windows tool.

Working:

Touch (not that there was a problem with that before)

Backlight control

WiFi

Bluetooth (soso,see below)

Not working:

Speakers

Bluetooth keeps losing connection - can pair with Bluetooth headphones, sound I'd played, but connection breaks every 10 seconds or so and is reestablished shortly after - unfortunately, not quite usable that way...

The heavy usage on the CPU still seems to be there, making for bad battery life, but that seems to be a general issue of android on x68 machines?

Geekbench results are strangely quite good considering there's this constant CPU usage (got around 3000 points). Not sure how, but that's not much worse than on Linux (I get around 3400 there).

So performancewise this seems to be no big issue, but the 3-4 hours battery life is unfortunate. Don't know if a solution for this is to be expected though...
[BLISS ROMS Development] beverlykho:
Xposed

Oh, my bad. Thanks for setting me right, eletrikjesus.
[BLISS ROMS Development] digital0:
I have Onda obook 20 plus dualboot tablet. It has SileadTouch touchscreen (at least according to Windows driver). Tried Bliss stable and bleeding edge. With 4.9 and 4.12 kernels touchscreen responds a little when I press at the top right of the screen (edit: if I tap randomly and repetitively on the whole screen, "Vision settings" starts blinking). How can I make touch work? I hope 4.14 kernels will work better.

Edit: dmesg|grep silead shows:

silead_ts i2c-MSSL1680:00: i2c-MSSL1680:00 supply vddio not found, using dummy regulator

silead_ts i2c-MSSL1680:00: i2c-MSSL1680:00 supply avdd not found, using dummy regulator

silead_ts i2c-MSSL1680:00: Chip ID read error -121

silead_ts: probe of i2c-MSSL1680:00 failed with error -121

My original Android 5.1 dmesg:

<7>[ 4.264736] [gsl_tp][gsl_ts_init]come int gsl_ts_init

<7>[ 4.264917] ****************************************

<7>[ 4.264957] SCREEN_MAX_X =1200

<7>[ 4.265006] SCREEN_MAX_Y =1920

<7>[ 4.265057] ctp_cob_gslX680 =210

<7>[ 4.265109] fw_index =1

<7>[ 4.265161] ****************************************

<7>[ 4.265237] GSLX680 Enter gsl_ts_probe

<7>[ 4.265271] ==kzalloc success=

<7>[ 4.265321] === GSL I2C addr = 40 ===

<7>[ 4.265373] [GSLX680] Enter gslX680_ts_init

<6>[ 4.265997] input: GSL_TP as /devices/pci0000:00/808622C1:05/i2c-5/i2c-MSSL1680:00/input/input8

<7>[ 4.266496] [tp_gsl] IRQ_PORT =360

<7>[ 4.266583] [tp_gsl] RST_PORT =366

<7>[ 4.331378] I read reg 0xf0 is 0

<7>[ 4.334978] I write reg 0xf0 0x12

<7>[ 4.338635] I read reg 0xf0 is 0x12

<6>[ 4.407766] trigger_algo:Algo_status:2

<7>[ 4.449223] read 0xfc = 80 36 0 0

<7>[ 4.449261] =============gsl_load_fw start==============

<6>[ 4.506236] usb 1-1: new low-speed USB device number 2 using xhci_hcd

<6>[ 4.552178] trigger_algo:Algo_status:2

<6>[ 4.677628] usb 1-1: New USB device found, idVendor=0581, idProduct=0101

<6>[ 4.677669] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

<4>[ 4.678185] usb 1-1: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes

<6>[ 4.695948] input: HID 0581:0101 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:0581:0101.0001/input/input9

<6>[ 4.696654] hid-generic 0003:0581:0101.0001: input,hidraw0: USB HID v1.10 Mouse [HID 0581:0101] on usb-0000:00:14.0-1/input0

<6>[ 4.696961] snd_soc_sst_platform: sst_platform_probe is deferred

<6>[ 4.697008] platform sst-platform: Driver sst-platform requests probe deferral

<6>[ 4.770132] trigger_algo:Algo_status:2

<7>[ 5.787264] =============gsl_load_fw end==============

<7>[ 5.857492] gsl pen test

<7>[ 7.267984] gsl_pen---I read real_time == 2efc

<7>[ 7.268017] gsl_pen---I read ret == f4e

<7>[ 7.361173] [GSLX680] End gsl_ts_probe

Edit2: Fedora 27 works when I copy mssl1680.fw to /lib/firmware/silead, but touchscreen is uncalibrated. Does anyone know how to calibrate it?
[BLISS ROMS Development] electrikjesus:
For Bliss, the Android-x86 docs do mention somewhere how to access the tscalibration app
[BLISS ROMS Development] DrBeaker:
Hello,

Sorry to bump thread, just came across via TechTablet Thread for Chuwi Hi12

Can anyone (possibly [MENTION=5945502]4r44444[/MENTION]) provide update status to Hi12. Does Touchscreen work fully? Graphics display? And finally, do we have sound matter resolved?

Great work to all contributors, I am getting the wallet out for a donation ;)
[BLISS ROMS Development] 4r44444:
Hi, in the newest Bleeding Edge Build I got Touch Screen, Wifi work. - Sound not work yet -Videos in Youtube for example are a grey shade.

Btw- You can just test it by yourself... when insert the USB Stick with the ISO Boot Live System so you can test without install the ROM.
[BLISS ROMS Development] hotwired34:
Has anyone had any success getting this to run properly on a Chuwi Hi10 Pro device? I used the bleeding edge live boot USB, and it got further than the stable release (which crashed the wizard due to missing WiFi), but it still seems like it's missing drivers or something.

For instance, it does not recognize touches on the touchscreen. YouTube videos do not work right - they look like they are decoded wrong. There's no rotation on the display and no sound.

This device came with Lollipop, and Chuwi only recommends updating it to Remix OS, but that hasn't been updated in a long while.

Any help would be appreciated.
[BLISS ROMS Development] kypor:
Using ASUS Transformer Mini T102HA

First of all I just want to say Bliss is awesome, and works the best for my device, thank you so much! :good:

I have an ASUS Transformer Mini T102HA and I've installed the latest K4.9 stable release (Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso) and so far everything works well. The only wish I would have is that the auto rotate would work, but I understand that the kernel may not have the drivers available for this system. The only thing that is not working so I can use it is that I use Kobo Reader to read books, but when I download a book in the reader, the app crashes. I'm not sure why, unless it has something to do with the virtual HDD using the easy install tool, creating the C:\AndroidOS folder in Windows. Any ideas or anything I can do to see what the issue could be?

Other that that, this is pretty amazing! Thank you so much!
[BLISS ROMS Development] digital0:
Please post the logs of the crash (logcat for example).
[BLISS ROMS Development] kypor:
Is this possible while the OS is running? Its a dual boot system currently, so if there is a way to monitor the crash while Android is running, that would be ideal. Android is new to me, and I'm not sure how to log the app crash
[BLISS ROMS Development] digital0:
adb logcat or the app catlog.
[BLISS ROMS Development] ubuntuh:
Hello there can someone explain how to get the 32 bit version..im a total noob but i loved bliss runing on my old laptop..thanks very much
[BLISS ROMS Development] harkaman:
https://androidfilehost.com/?w=files&flid=136638

https://androidfilehost.com/?w=files&flid=145774
[BLISS ROMS Development] electrikjesus:
Our EDU builds were only a few releases. If we ever get any more interest over them, we might pick them back up. But for now, you can find them on the AFH archives linked in the third post.