[BLISS ROMS Development] franzli:
This is an overview of my current attempts to install a workable system on three different x86 tablets with brief bugreports and two logcats.

All of the devices have working Wifi, but as mentioned in other posts, the connection can get a bit wonky and if it gets lost (typically after not data were transferred for a bit), you may have to reboot to get Wifi back.

Cube i7 Book (Skylake 6y30, 4GB)

Runs fairly well on latest 64bit bleeding edge with some weird problems.

Working:

Wifi

Autorotation (but inverted! - my current fix is to turn device opposite of what I want and then lock rotation - fix welcome, but workable this way; same issue on Linux)

Audio (requires cold boot as pointed out for some other devices in the the thread)

Wacom pen (sensitivity and palm rejection seem fine too)

Microphone (quality not very good, but working at least in skype; in another sound recorder app I only got static, so there might be some limits)

Physical buttons (Power, volume)

Working only on Live USB:

backlight/brightness control - works perfectly when booting from USB, however on installation backlight is simply stuck (although it might not be on max brightness and at one point I noticed something that may have been a slight change in brightness?? may have imagined that one)

As I mentioned, I had a similar issue on Dell Venue 8 pro (Cherry Trail), which I could fix using the Android installer from USB and install to an ext4 partition rather than the easy install, but this doesn't seem to help on the Cube i7 Book

In the attached zip there's one logcat just after me trying to adjust brightness up and down on the quick settings slider

Not working:

Bluetooth - doesn't seem to work on either live USB nor installation (but works fine on Linux since at least kernel 4.9)

The attached zip contains another logcat after I tried to activate Bluetooth from settings menu

Camera

One further issue (also mentioned earlier and coming up on the other two devices as well) is that the CPU usage is fairly high, it seems like one of the four virtual cores is always almost 100% busy and all cores hardly ever go below 2GHz (and if so only to about 1900MHz), which leads to high temperatures, reduced performance (see Geekbench score below) and bad battery life.

Geekbench 4 scores: 2455 (single) 3444 (multi - this looks like it's reduced by the strange fulltime use of one core, since it's not much better than the z8500 in teh DV8P 5855 below)

Dell Venue 8 Pro 5855 (Cherry Trail x5-z8500, 4GB)

This works very nice and smoothly on the latest 64bit bleeding edge build and is almost perfect apart from one unfortunately rather big issue.

Working:

Wifi

Backlight control (on live USB and if installed onto ext4 partition from USB installer, not working when using easy installation from windows with img files)

Stylus Pen (pressure sensitivity, palm rejection etc. seem ok)

Not working:

Audio

Autorotation

Bluetooth (working fine on Linux though, kernels 4.10 and 4.11; ps after input from a surface 3 user I tried the Bliss-x86-64 build from 31 March with the 4.9 kernel and Bluetooth works there, albeit maybe not entirely stable and the build seems to have much worse multicore performance than the latest bleeding edge with 4.11 kernel, probably some background processes)

Camera

probably microphone

Physical buttons (power, volume)

There is an occasional issue where I can boot fine the first time, but when I shut down the device and want to boot into android the next time, I get a sort of boot loop, i.e. it boots up, the boot animation runs for a while and then the device reboots on its own. Sometimes it helps to repair the ext4 volume from a linux installation, so there may be something going on that corrupts the partition? It may have to do with the lack of a proper shutdown function as the buttons aren't working? I'm typically using a power menu app, but maybe that's not shutting down the ext4 partition properly either.

This is quite annoying because it disrupts the otherwise quite advanced usability on this device.

CPU scaling seems to work much better than on the other two devices - on idle three cores actually consistently scale down to below 1GHz and there's only one typically somewhere over 1GHz . There's still a constant CPU usage level of about 22%(haven't been able to test mic and camera yet) taking a toll on performance and battery life (which is predicted at about 2h at 60% atm, although I guess the predictions aren't that good), so it's not all golden, but it's at least not impacting general usability.

Geekbench 4: 1097 (single core) 3232 (multicore)

Due to the buttons not working, you cannot wake the device if it goes to sleep, so screen has to stay on all the time, which doesn't help battery life.

Dell Venue 8 Pro 5830 (Bay Trail , 2GB)

Working but relatively sluggishly on the latest 32bit stable build (requires nomodeset boot parameter in grub). Sometimes apps are prone to crashing and occasionally the whole device hangs and reboots on its own (or needs to be rebooted by force).

Still quite surprised at how much is working!

Working:

Wifi

Autorotation

Stylus Pen (pressure sensitivity, palm rejection etc. seem ok)

Audio (requires cold boot and is relatively wonky, I keep losing audio when trying to make a Skype test call, which also prevents me from testing the microphone)

Not working:

Backlight control

Bluetooth

Camera

Physical buttons (power, volume) - they may have worked on the live USB or the March stable build, I remember they worked at some point, but they don't now

CPU seems to be struggling at times but is not stuck at maximum speed like on the Cube i7 book. General CPU usage according to kernel auditor around 60-75% in idle, which probably accounts for the overall sluggishness. (Nonetheless, individual cores sometimes clock down to 500-600MHz)

Geekbench 4: 977 (single) 2720 (multicore)

Due to the buttons not working, you cannot wake the device if it goes to sleep, so screen has to stay on all the time, which doesn't help battery life. I remember that on some version, waking actually did work on this device, not sure which one though (possibly the previous stable build)

I hope this overview is somewhat helpful. If anyone's got any suggestions for any of the issues, that would be great.