Cannot open opengl games in 7.1-rc2

237 views
Skip to first unread message

Philip Z

unread,
Oct 17, 2017, 1:25:22 PM10/17/17
to Android-x86
Hi Android-x86 experts,
I used to be able to open some opengl games with 7.1-rc1, but I can't open them successfully any more with 7.1-rc2 (game exits right after starting). I suspect if it's because we use SwiftShader as the software renderer. Am I able to switch to other software renderer to see if it fixes the issue? Let me know if you have any suggestions or need more details.

Thanks!

Philip

Chih-Wei Huang

unread,
Oct 17, 2017, 10:11:25 PM10/17/17
to Android-x86
What device and GPU did you use?
What games did you test?

It's possible. But you need to rebuild the source
to enable the old software renderer by mesa.


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

Philip Z

unread,
Oct 17, 2017, 10:28:08 PM10/17/17
to Android-x86
Hi Chih-Wei,
I used qemu kvm with no GPU. 
I tested 王者荣耀 and 穿越火线.
I actually compiled the source by myself. So, if you can point me to where I can enable the old software renderer, that will be great.

Thanks,
Philip

fguy

unread,
Oct 18, 2017, 4:47:47 AM10/18/17
to Android-x86
The same problem is with VMware. If you download the android x64 with 3D acceleration, the game "Defens Zone 3" starts with a black screen, and there is a sound and when you press the ESC, you exit the game. If you download android with the key "nomodeset" then this game starts fine. I also compiled android x64 from the MESA 17.2.2. In this assembly, the game starts normally when using 3D acceleration. In my opinion, the problem is in MESA 17.1.x.

Philip Z

unread,
Oct 18, 2017, 10:11:50 AM10/18/17
to Android-x86
Hi fguy,
How did you compile x64 with Mesa 17.2.2? Any guide to follow? Thanks!

Philip

fguy

unread,
Oct 18, 2017, 10:53:32 AM10/18/17
to Android-x86
How did you compile x64 with Mesa 17.2.2? Any guide to follow? Thanks!
 
I managed to download Mesa 17.2.2 when it was active in the repository of this project. A small patch fixes the build error. This version has a problem with 3d ATI / AMD adapters and so the authors returned to 17.1.10 for android 7.1.2.

Zhouheng Zhuang

unread,
Oct 18, 2017, 11:43:06 AM10/18/17
to andro...@googlegroups.com

I see. Could you tell me which version or the date of your Android x86 source code is? What is the small patch fix that fixes the build error?

Thanks,

Philip


On Oct 18, 2017 7:54 AM, "fguy" <fguy...@gmail.com> wrote:
How did you compile x64 with Mesa 17.2.2? Any guide to follow? Thanks!
 
I managed to download Mesa 17.2.2 when it was active in the repository of this project. A small patch fixes the build error. This version has a problem with 3d ATI / AMD adapters and so the authors returned to 17.1.10 for android 7.1.2.

--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/2lULttKG5xs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86+unsubscribe@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

fguy

unread,
Oct 18, 2017, 11:49:09 AM10/18/17
to Android-x86

I see. Could you tell me which version or the date of your Android x86 source code is? What is the small patch fix that fixes the build error?

 

Zhouheng Zhuang

unread,
Oct 18, 2017, 12:10:38 PM10/18/17
to andro...@googlegroups.com

Thanks, fguy!
I checked my external/mesa repo and it included the Oct 5 merge fix by Chih-wei. I didn't see anything about 17.2. Is the changeset removed?
Thanks,
Philip


On Oct 18, 2017 8:49 AM, "fguy" <fguy...@gmail.com> wrote:

I see. Could you tell me which version or the date of your Android x86 source code is? What is the small patch fix that fixes the build error?

 

--
IMG_20171018_090404.jpg

fguy

unread,
Oct 18, 2017, 1:50:18 PM10/18/17
to Android-x86

I checked my external/mesa repo and it included the Oct 5 merge fix by Chih-wei. I didn't see anything about 17.2. Is the changeset removed?

you need to ask this question Chih-Wei Huang 

Chih-Wei Huang

unread,
Oct 19, 2017, 5:38:33 AM10/19/17
to Android-x86
2017-10-18 10:28 GMT+08:00 Philip Z <zz...@cornell.edu>:
> Hi Chih-Wei,
> I used qemu kvm with no GPU.

In 7.1-rc2 QEMU supports two mode.
With -vga std it uses the software renderer.
With -vga virtio it uses the virtual GPU virgl
to provide much better 3D performance.
You can read the qemu-android script
to understand how to enable virgl exactly.

If your QEMU is built with virglrenderer
you should try virgl first.

> I tested 王者荣耀 and 穿越火线.

I downloaded the apps from qq.com.
I tested them with two QEMU modes,
as well as Intel GPU (i965, Skylake).
The app crashed in all cases with the log:

10-19 16:52:01.287 3821 3847 W libc : pthread_create
sched_setscheduler call failed: Operation not permitted
10-19 16:52:01.369 3821 3862 W art : Long monitor contention
with owner pool-6-thread-1 (3860) at void
com.tencent.beacon.a.h.g()(ProGuard:320) waiters=0 in void
com.tencent.beacon.a.h.a(long, long, boolean) for 426ms
10-19 16:52:01.553 1405 1465 I ActivityManager: Process
com.tencent.tmgp.sgame (pid 3821) has died

It looks like not an issue of the renderer.
Maybe it's updated and broken in android-x86.
If you have kept the old apk,
you may try it in 7.1-rc2.
Or, if you install the same apk to 7.1-rc1,
does it still work?

> I actually compiled the source by myself. So, if you can point me to where I
> can enable the old software renderer, that will be great.

You need to revert commit 2c04b2e and 658c992
in device/generic/common to go back to the old
mesa swrast. (maybe more, I didn't verify)

Chih-Wei Huang

unread,
Oct 19, 2017, 5:39:22 AM10/19/17
to Android-x86
The VMware (vmwgfx) issue is entirely different than
the issue of QEMU. Please don't mix them up.

I also tested the "Defense Zone 3 HD" on QEMU.
It works well with virgl and software renderer.

Chih-Wei Huang

unread,
Oct 19, 2017, 6:52:48 AM10/19/17
to Android-x86
2017-10-19 17:38 GMT+08:00 Chih-Wei Huang <cwh...@android-x86.org>:
> 2017-10-18 10:28 GMT+08:00 Philip Z <zz...@cornell.edu>:
>
> It looks like not an issue of the renderer.
> Maybe it's updated and broken in android-x86.
> If you have kept the old apk,
> you may try it in 7.1-rc2.
> Or, if you install the same apk to 7.1-rc1,
> does it still work?

After more testing, I surprisingly found it's
an issue of the new houdini 7.1.
The 64-bit 7.1-rc2 equips with new houdini libs
that seems to be incompatible with the two apps.
If I using the old houdini 6, it just works.
(with both virgl and swiftshader)
I didn't really play it (don't know how to play).
I just see the welcome screen so I guess it's OK.

The 32-bit 7.1-rc2 still uses old houdini 6.
You can just try it.

They are the first apps I found which can't
work with newer houdini. Interesting...
Reply all
Reply to author
Forward
0 new messages