hey this is an off topic

im on windows 10

I have this weird bug

dwm.exe(desktopwindowmanager) high cpu usage and freezing when i reattach keyboard

it returns back tonormal after deattaching keyboard

again same problem after reattaching keyboard

if i have to use pc normally with keyboard,i have to put pc to sleep and turn it on again

I am facing the same issue here as many of you regarding screen rotation and screen resolution. The easy fix here is just to do a "xrandr -o right". That way you get correct screen orientation (and actually the correct native resolution of 1920x1200 as well), but the problem is that the intel driver still thinks the monitor is operating in vertical mode, hence when you do "xrandr" from the terminal it only outputs vertical resolutions to choose from. The problem also remains when you start programs or games through Wine, you are left with only vertical resolutions to choose from..

I am running Debian 10.2 Buster 64 bit with Gnome3, and I am using the default Intel Driver.

I have tried the following to fix this problem without any luck so far:

1.) Edit the "/etc/default/grub" file to include "GRUB_CMDLINE_LINUX="fbcon=rotate:1". Then "Sudo update-grub" and rebooted. Nothing. Since this a macine that can only boot in EFI mode, some suggested trying: "video=efifb fbcon=rotate:1". Tried that too and updated the grub loader. Still would not rotate..

2.) I have also tried to add 1920x1200 as a new custom resolution with:

sudo xrandr --newmode "1920x1200_60.00"  193.25  1920 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync

or

sudo xrandr --newmode "1920x1200_59.88"  193.25  1920 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync

(since the refresh rate actually is 59.88)

and then:

sudo xrandr --addmode DSI1 "1920x1200_60.00"

With the last command I only get this error every time:

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  35
  Current serial number in output stream:  36

This problem with orientation and resolution is about to drive med mad. Any help with this is very much appreciated.

Hi drakxstar and Netready 

How did you get Android X86 booting?
I downloaded the ISO and wrote it to the USB stick using the Ubuntu USB Start Creator. I am able to boot from it on a normal PC, but the D330 fails to see the USB stick in the boot menu. Other images (PrimeOs and Linux) work fine, so its not a hardware problem.

Hi, did you use the dd method to write the ISO? If using Windows you need to use Balena Etcher (dd by default) or Rufus and select "Write using DD image mode" after clicking start.

Boots fine and straight off using either of the above methods for me.

agree with netready, if your are making the boot disk from windows then use rufus

if you are making the boot disk from linux, then use balena etcher

it is very easy to install etcher, trust me it is worth your time and bandwidth

btw the new version of android x86, android x86 9 RC1 is really awesome, no error with google play anymore

but did not try with games like PUBG or that kind, i just tried with simple game like candy crush saga

Hi drakxstar and Netready 

Thank you for your quick response!

I got it working now with Rufus (using dd mode)! It seems that the D330 is quite picky in relation to how the boot stick gets setup. I had to try with multiple settings (MBR/GPT, ...) until it detected it. Other systems like PrimeOS, Xubuntu and the Macrium Reflect Boot System (created on another PC, for a Partition backup) got detected with default settings without any issue.

Anyway, it runs and works quite ok.

How do you make Landscape working persistently? I use Force Landscape, but it has to run manually on every boot again.

Things I noticed:

• The screen stays on forever, althrough Sleep mode is (I think by default) set to 5 minutes.
• Pressing the Power Button and then "Sleep" works, but after switching it on again, it is quite laggy. And even worse, WIFi stays disabled until the next reboot.
• The physical keyboard is not automatically detected, but it can easily be switched with the Notification Bar Entry.
• GRUB2 can not be controlled by touch

Do you know solutions for any of those issues?

Do you know how GRUB2 can be updated, eg. after another OS is installed?

Are you able to have Windows beside Android x86? After I installed android (and GRUB2), WIndows failed to start with "Bad System Config Info". I guess GRUB2 damaged some settings.

Update:

• Wlan seems to get broken when ever the screen gets locked. Only a restart seems to help. :smileysad:
• I could fix windows with the recovery tools from Macrium Reflect Boot System. It seems to have been caused because I installed Android x86 to an NTFS partition. I reinstalled it again afterwards to an EXT partition and there windows did not get broken.

Hi Netready

No, I also have only the low-res variant (81H3). Do you have the latest BIOS? Maybe there is a fix for this issue. I had 8NCN34WW, but now updated to 8NCN37WW.