Change video resolution and disable mouse acceleration

[Luis Fernando]

Hello. Is there any way to disable mouse acceleration (not pointer speed)? Also, I try to change resolution using grub:

androidboot.selinux=permissive vmalloc=192M quiet nouveau.modeset=1 i915.modeset=0 video=1600x900@60

but only the ALT+F1 console resolution changes, if I add VULKAN=1, the OS resolution changes but the mouse pointer turns into a square with blurry stripes. Is there a proper way to change the OS resolution?

I'm using android-8.1-r2 32 bits, Intel core 2 duo E7500 with 4gb RAM and Nvidia GTX750 TI 1gb.

[Chih-Wei Huang]

Luis Fernando <arkady.grigor...@gmail.com> 於 2019年9月5日 週四 上午11:44寫道：

Am I correct that you disable Intel GPU and enable Nvidia (nouveau) GPU?

Anyway, the video= option should work.
If not, please collect logcat and dmesg for debugging.

I'm not sure what you meant "disable mouse acceleration".
We don't have that feature ("mouse acceleration").


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Luis Fernando]

>>Am I correct that you disable Intel GPU and enable Nvidia (nouveau) GPU?

Yes. That's what I'm doing. If I use "nomodeset" the resolution is set by "gfxmode" from gub.

>>Anyway, the video= option should work. If not, please collect logcat and dmesg for debugging.

After testing a little more, I notice that the resolution is set to 1600x900 (at least is what "wm size" returns) but the refresh rate is diferent, that's why when I press ALT+F1 / ALT+F7 the screen goes black to adjust to the new refresh rate. I did asume it was a diferent resolution because the image was blurry. The dmesg and logcat files are atatched. I also included when using VULKAN=1. When I was testing it crashed when pressing "Settings" button. I'm using this:

I couldn't take a screenshot when using VULKAN=1, but I can tell that is way more stable apart for the glitched mouse arrow.

>>I'm not sure what you meant "disable mouse acceleration". We don't have that feature ("mouse acceleration").

Nevermind. I already gave up.

[Chih-Wei Huang]

Luis Fernando <arkady.grigor...@gmail.com> 於 2019年9月5日 週四 下午10:39寫道：

>>Am I correct that you disable Intel GPU and enable Nvidia (nouveau) GPU?

Yes. That's what I'm doing. If I use "nomodeset" the resolution is set by "gfxmode" from gub.

>>Anyway, the video= option should work. If not, please collect logcat and dmesg for debugging.

After testing a little more, I notice that the resolution is set to 1600x900 (at least is what "wm size" returns) but the refresh rate is diferent, that's why when I press ALT+F1 / ALT+F7 the screen goes black to adjust to the new refresh rate. I did asume it was a diferent resolution because the image was blurry. The dmesg and logcat files are atatched. I also included when using VULKAN=1. When I was testing it crashed when pressing "Settings" button. I'm using this:

According to the logcat I think the resolution is set correct (1600x900).

Maybe you can remove @60 in video= option and let it decide the appropriate refresh rate.

 

I couldn't take a screenshot when using VULKAN=1, but I can tell that is way more stable apart for the glitched mouse arrow.

Right, another known issue of vulkan.

 

>>I'm not sure what you meant "disable mouse acceleration". We don't have that feature ("mouse acceleration").

Nevermind. I already gave up.

[Luis Fernando]

>>According to the logcat I think the resolution is set correct (1600x900).Maybe you can remove @60 in video= option and let it decide the appropriate refresh rate.

I already did it, it doesn't work. I think the OS (the console resolution is fine) is totally ignoring "video=1600x900" and using gfx_payload from grub wich is set to 1600x1200 by default with a different refresh rate. The same happens with "nomodeset" option. I had this problem once using Linux and was solved by installing Nvidia drivers properly so maybe there is something wrong with the way the driver detects the monitor (in my case at least).

Is there any way to get any sort of preview build? I'm willing to test alpha builds but I dont't want to compile it. Do you know what are the header files responsible for mouse input? I would like to take a look at it. Anyway, thanks for the reply.

[Amyhopps10]

Chih-wei, would you like to release Android-x86 go edition for pcs with 1GB RAM? I have a old PC with 1GB RAM & it runs slow on normal Android-x86 releases.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/92b96e56-fc4f-46dc-b921-62799b01ca67%40googlegroups.com.