Few questions (hardware acceleration, changing device model, VMware tools)

[null.z...@gmail.com]

First, I want to congratulate you on the continuous support for this project.
You did a great job with a bit of problems here and there.
The one that has the most importance for me is the hardware acceleration on VMware Workstation Player 15.
It works fine on Nougat r2 (both stock and Lineage) but it doesn't work on Oreo.
Also, even with the hardware support, I simply can't run any games on it.
The Antutu 3D test crashes and games like "Temple run" or "Subway surfer" just start but then become unresponsive - no detection of any input whatsoever (but they don't seem to be frozen).
Any way to fix this?

The second problem is changing the device model.
Is it necessary to modify the ramdisk as suggested here: https://groups.google.com/forum/#!msg/android-x86/roivdWZHHEE/oUKBzWcxCQAJ ?
If so, do I have to modify the ramdisk every time I want to change the model? Is there maybe some easier way?
Since I'm running the VMware Workstation Player 15 I know how to extract the ramdisk, but I don't know how to put it back in again (Google is not really helpful or I don't know what to search).

Third problem is installing VMware tools.
From everything I've read, there's no support for the Android x86 from the company.
I've noticed that mouse integration is solved in Oreo, but as I've said previously, I don't have hardware support there so it's not of much use.
I can install all the dependencies trough Termux, but the installation fails when it searches for /var/log/vmware-install.log. Did anyone tried to install it like this or is there another way?

I'm grateful for all the suggestions.
Thx in advance!

[null.z...@gmail.com]

I was hoping for some answers, but nothing so far. Let's hope some more details will help.
I'm posting some log files.
After starting "Subway Surfers":
<code>
02-21 04:46:48.815  7807  7839 E CRASH   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000003
02-21 04:46:48.815  7807  7839 E CRASH   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-21 04:46:48.815  7807  7839 E CRASH   : Build fingerprint: 'google/marlin/marlin:7.1/NDE63L/3273814:user/release-keys'
02-21 04:46:48.815  7807  7839 E CRASH   : Revision: '0'
02-21 04:46:48.815  7807  7839 E CRASH   : pid: 7807, tid: 7839, name: UnityGfxDeviceW  >>> com.kiloo.subwaysurf <<<
02-21 04:46:48.815  7807  7839 E CRASH   :     eax 00000004  ebx cf88c688  ecx ca7fef00  edx 00000000
02-21 04:46:48.815  7807  7839 E CRASH   :     esi c0a93d60  edi cf88c688
02-21 04:46:48.815  7807  7839 E CRASH   :     xcs 00000023  xds 0000002b  xes 0000002b  xfs 0000006b  xss 0000002b
02-21 04:46:48.815  7807  7839 E CRASH   :     eip cf3a9205  ebp ca7feec8  esp ca7feebc  flags 00010296
02-21 04:46:48.815  7807  7839 E CRASH   :
02-21 04:46:48.815  7807  7839 E CRASH   : backtrace:
02-21 04:46:49.001  7807  7839 E CRASH   :     #00  pc 00401205  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #01  pc 003fea11  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #02  pc 0048c37a  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #03  pc 0042234b  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #04  pc 004897b9  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #05  pc 0048ba68  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #06  pc 0040eb04  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #07  pc 00412715  /system/lib/dri/gallium_dri.so
02-21 04:46:49.001  7807  7839 E CRASH   :     #08  pc 00b8b36b  /data/app/com.kiloo.subwaysurf-1/lib/x86/libunity.so
02-21 04:46:49.001  7807  7839 F mono    : * Assertion: should not be reached at mini.c:2215
02-21 04:46:49.041  1926  1987 W InputDispatcher: channel '7827f8e com.kiloo.subwaysurf/com.kiloo.unityutilities.UnityPluginActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
02-21 04:46:49.041  1926  1987 E InputDispatcher: channel '7827f8e com.kiloo.subwaysurf/com.kiloo.unityutilities.UnityPluginActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
02-21 04:46:49.043  1926  2243 I WindowManager: WIN DEATH: Window{4ab069a u0 SurfaceView - com.kiloo.subwaysurf/com.kiloo.unityutilities.UnityPluginActivity}
02-21 04:46:49.044  1926  3194 D GraphicsStats: Buffer count: 5
02-21 04:46:49.044  1926  2294 D KbdSensor: poll_batch: dev=0x7f45ba616100 sensor_handle=0 flags=0 sampling_period_ns=66667000 max_report_latency_ns=100000000
02-21 04:46:49.044  1926  2294 D KbdSensor: poll_setDelay: dev=0x7f45ba616100 handle=0 ns=66667000
02-21 04:46:49.045  1926  4814 I ActivityManager: Process com.kiloo.subwaysurf (pid 7807) has died
</code>

After startng "Antutu 3D"
<code>
02-21 20:16:22.937  6249  6249 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-21 20:16:22.937  6249  6249 F DEBUG   : LineageOS Version: '14.1.0-android_x86_64'
02-21 20:16:22.937  6249  6249 F DEBUG   : Build fingerprint: 'google/marlin/marlin:7.1/NDE63L/3273814:user/release-keys'
02-21 20:16:22.937  6249  6249 F DEBUG   : Revision: '0'
02-21 20:16:22.937  6249  6249 F DEBUG   : ABI: 'x86'
02-21 20:16:22.937  6249  6249 F DEBUG   : pid: 6205, tid: 6237, name: UnityGfxDeviceW  >>> com.antutu.benchmark.full <<<
02-21 20:16:22.937  6249  6249 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
02-21 20:16:22.937  6249  6249 F DEBUG   :     eax d2126688  ebx d2126688  ecx cccfed38  edx 00000000
02-21 20:16:22.937  6249  6249 F DEBUG   :     esi d2126688  edi cccfed38
02-21 20:16:22.937  6249  6249 F DEBUG   :     xcs 00000023  xds 0000002b  xes 0000002b  xfs 0000006b  xss 0000002b
02-21 20:16:22.937  6249  6249 F DEBUG   :     eip d1c43380  ebp cccfecd8  esp cccfec90  flags 00010286
02-21 20:16:22.944  6249  6249 F DEBUG   :
02-21 20:16:22.944  6249  6249 F DEBUG   : backtrace:
02-21 20:16:22.944  6249  6249 F DEBUG   :     #00 pc 0041a380  /system/lib/dri/gallium_dri.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #01 pc 00417d1c  /system/lib/dri/gallium_dri.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #02 pc 004a53ab  /system/lib/dri/gallium_dri.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #03 pc 0043b34a  /system/lib/dri/gallium_dri.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #04 pc 004a27b8  /system/lib/dri/gallium_dri.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #05 pc 0042b87f  /system/lib/dri/gallium_dri.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #06 pc 0042c01c  /system/lib/dri/gallium_dri.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #07 pc 004d201e  /data/app/com.antutu.benchmark.full-1/lib/x86/libunity.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #08 pc 004dddc4  /data/app/com.antutu.benchmark.full-1/lib/x86/libunity.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #09 pc 004de334  /data/app/com.antutu.benchmark.full-1/lib/x86/libunity.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #10 pc 004c7346  /data/app/com.antutu.benchmark.full-1/lib/x86/libunity.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #11 pc 004cb691  /data/app/com.antutu.benchmark.full-1/lib/x86/libunity.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #12 pc 004c46a3  /data/app/com.antutu.benchmark.full-1/lib/x86/libunity.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #13 pc 0042a96d  /data/app/com.antutu.benchmark.full-1/lib/x86/libunity.so
02-21 20:16:22.944  6249  6249 F DEBUG   :     #14 pc 00088daf  /system/lib/libc.so (_ZL15__pthread_startPv+190)
02-21 20:16:22.944  6249  6249 F DEBUG   :     #15 pc 00022f80  /system/lib/libc.so (__start_thread+25)
02-21 20:16:22.944  6249  6249 F DEBUG   :     #16 pc 000207e6  /system/lib/libc.so (__bionic_clone+70)
02-21 20:16:22.998  6249  6249 I debuggerd: type=1400 audit(0.0:1557): avc: denied { write } for name="logdr" dev="tmpfs" ino=3953 scontext=u:r:init:s0 tcontext=u:object_r:logdr_socket:s0 tclass=sock_file permissive=1
02-21 20:16:23.124  1569  1569 W         : debuggerd: resuming target 6205
02-21 20:16:23.126  1950  1950 I FileObserver: type=1400 audit(0.0:1558): avc: denied { sendto } for path="/dev/socket/logdw" scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=1
02-21 20:16:23.128  1950  1974 I BootReceiver: Copying /data/tombstones/tombstone_03 to DropBox (SYSTEM_TOMBSTONE)
</code>

Is this just a driver problem or something else?
I've seen topics about updating Mesa drivers so I might be able to follow the steps, but I'm far from a Linux expert.

[Chih-Wei Huang]

<null.z...@gmail.com> 於 2019年2月16日 週六 上午6:02寫道：

>
> First, I want to congratulate you on the continuous support for this project.
> You did a great job with a bit of problems here and there.
> The one that has the most importance for me is the hardware acceleration on VMware Workstation Player 15.
> It works fine on Nougat r2 (both stock and Lineage) but it doesn't work on Oreo.
> Also, even with the hardware support, I simply can't run any games on it.
> The Antutu 3D test crashes and games like "Temple run" or "Subway surfer" just start but then become unresponsive - no detection of any input whatsoever (but they don't seem to be frozen).
> Any way to fix this?

VMware 3D support was broken due to the vmwgfx driver
in newer kernel (since 4.14).
It still works if build oreo-x86 with kernel 4.9.

I've uploaded an 8.1-r1 iso with kernel 4.9 that
you can try. It works with VMware workstation 14.
(haven't try 15 yet)

https://www.fosshub.com/Android-x86.html

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

[null.z...@gmail.com]

VMware 3D support was broken due to the vmwgfx driver
in newer kernel (since 4.14).
It still works if build oreo-x86 with kernel 4.9.

I've uploaded an 8.1-r1 iso with kernel 4.9 that
you can try. It works with VMware workstation 14.
(haven't try 15 yet)

https://www.fosshub.com/Android-x86.html

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

Thx for the reply!

I've tried the version you've suggested and I can confirm that hardware acceleration works.

However, Antutu 3D crashes the player, and there are also problems with rendering (see the screenshot)

Also, I would prefer to stay on Lineage, I prefer it much more than stock Android.

Can you tell me how to compile this kernel for it?

Once kernel is compiled is it enough to just mount the .vmdk and replace the kernel file?

Thx in advance!

[Chih-Wei Huang]

<null.z...@gmail.com> 於 2019年2月24日 週日 上午4:13寫道：

> Thx for the reply!
> I've tried the version you've suggested and I can confirm that hardware acceleration works.
> However, Antutu 3D crashes the player, and there are also problems with rendering (see the screenshot)
>

> Also, I would prefer to stay on Lineage, I prefer it much more than stock Android.
>
> Can you tell me how to compile this kernel for it?
>
> Once kernel is compiled is it enough to just mount the .vmdk and replace the kernel file?

You don't need to compile it.
Just copy the kernel and all files in /lib/modules.

[null.z...@gmail.com]

On Monday, February 25, 2019 at 9:06:59 AM UTC+1, Chih-Wei Huang wrote:

You don't need to compile it.
Just copy the kernel and all files in /lib/modules.


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

Here's the thing - the Lineage r2 actually has a newer kernel (4.9.95) compared to this build (4.9.152).

Did you merge the mesa drivers in the kernel when you compiled it or not?

What I've tried is this https://groups.google.com/forum/#!topic/android-x86/oKV4qok3aDk, taking all the libraries from the Oreo and putting it into Lineage but it doesn't work :'(.

Do you think that this is because I took it from Oreo, because it's Lineage instead of stock Nougat or something else?

[Chih-Wei Huang]

<null.z...@gmail.com> 於 2019年2月26日 週二 下午12:05寫道：

>
> Here's the thing - the Lineage r2 actually has a newer kernel (4.9.95) compared to this build (4.9.152).

Why? 152 > 95 explicitly.

> Did you merge the mesa drivers in the kernel when you compiled it or not?

mesa is a userspace library, nothing to do with kernel.

> What I've tried is this https://groups.google.com/forum/#!topic/android-x86/oKV4qok3aDk, taking all the libraries from the Oreo and putting it into Lineage but it doesn't work :'(.
> Do you think that this is because I took it from Oreo, because it's Lineage instead of stock Nougat or something else?

Not sure what you did.
You just need to replace the kernel & modules.

[null.z...@gmail.com]

On Tuesday, February 26, 2019 at 7:10:08 AM UTC+1, Chih-Wei Huang wrote:

<null.z...@gmail.com> 於 2019年2月26日 週二 下午12:05寫道：
>
> Here's the thing - the Lineage r2 actually has a newer kernel (4.9.95) compared to this build (4.9.152).

Why? 152 > 95 explicitly.

True.

> Did you merge the mesa drivers in the kernel when you compiled it or not?

mesa is a userspace library, nothing to do with kernel.

That was my question. I guess it means that replacing the kernel won't update mesa drivers.

> What I've tried is this https://groups.google.com/forum/#!topic/android-x86/oKV4qok3aDk, taking all the libraries from the Oreo and putting it into Lineage but it doesn't work :'(.
> Do you think that this is because I took it from Oreo, because it's Lineage instead of stock Nougat or something else?

Not sure what you did.
You just need to replace the kernel & modules.

I did what Mauro suggested - took mesa libraries from vendor/lib and lib64 Oreo build (in the script, see attachment) and copied them to /system/lib and lib64

But the system fails to boot. When I put everything back it boots again.

In order to run any games I need to update mesa drivers

[null.z...@gmail.com]

 Any chance that I'll get some new instructions on what to do, or that we might get a Lineage 14.1 build with updated MESA drivers? (with an appropriate kernel > 4.14)