Anyone tried Anbox-4-arm64 yet?

[FrankWu]

I've updated my Manjaro packages from my previous comment:
https://drive.google.com/open?id=1Hl8mWh...My9owzQ-E0
Notes:

1. Extract the archives -> the compiled packages are in there along with all the mess I've done to get it to run
   
2. Ignore anbox-image_experiment.tar.gz -> that's the standard one dug up from Anbox'es github page and doesn't work
   
3. anbox-image-working.tar.gz is using the Android image kindly provided by Sebastian Krzyszkowiak from his proof of concept on the Librem 5 Usually it's unwise to use images randomly posted on the internet and you can create your own if you have 100GB+ of free storage to build one
   
4. I don't know if it's necessary but I've created a version of the pinebookpro kernel with the same flags as from this merge request accompanying the photo of the Proof of Concept on the Librem 5. Link here: https://social.librem.one/@dos/103564403894744164  (I have no idea why the link doesn't show up properly )
   

Additional notes:

• run anbox-bridge before you start the container to get networking (running as root might be required)
  
• In my Plasma session, Anbox was... lets say heavy and did cause my system to hang at least once
  
• In XWayland mode on my Wayfire setup, Anbox doesn't show the cursor but didn't exhibit the instability I observed in Plasma (it works but you have to go blind and click the touchpad)
  

Yet more notes:

• I had no success with Vivaldi and Brave browsers
  
• I need to dig and find a game which doesn't require Google Play Services to test (or just use of my game projects as guinea pig during the weekend)
  
• Telegram works okey. It doesn't crash at first sight of a sticker and may be even usable (though we should try to bring telegram's developers attention to the crash on the aarch64 desktop one )
  

Well, we have something to begin working on

Hi PakoSt,
I downloaded your anbox-image-working.tar.gz, but there are 4 files, which one should be used for ARM64? (In fact I am using one ARM64 devices).
anbox-image-1:2018.07.19-3-aarch64.pkg.tar.zst  
android_1_arm64.img
anbox-image-1:2018.07.19-2-aarch64.pkg.tar.zst  
android.img

In fact I have used [u]android_1_arm64.img but when launching the app manager it shows starting then exit .[/u]
[u]And then I used your android.img, for this one when launching app manager it works fine. But when I installed some apks with "native-code: '' 'armeabi' 'armeabi-v7a", it failed with error "INSTALL_FAILED_NO_MATCHING_ABIS". Then I found this image file (android.img) 's abilist is [arm64-v8a] which makes [u][u]'armeabi' 'armeabi-v7a" apk failed.  Just want to confirm if android.img is built with [u][u]arm64-v8a only.[/u][/u][/u][/u][/u]

[u][u][u][u][u]Another problem I found is when launched WebView Browser, after I finishing typing a website, it shows blank window and then crashed.[/u][/u][/u][/u][/u]
[u][u][u][u][u]I found there is following error:[/u][/u][/u][/u][/u]

[u][u][u][u][u]02-27 15:09:44.678    30    30 E EGL_emulation: tid 30: eglCreateSyncKHR(1315): error 0x3004 (EGL_BAD_ATTRIBUTE)[/u][/u][/u][/u][/u]
[u][u][u][u][u]02-27 15:10:08.539   519   615 E libEGL  : validate_display:99 error 3008 (EGL_BAD_DISPLAY)[/u][/u][/u][/u][/u]


[u][u][u][u][u]Do you have this issue?[/u][/u][/u][/u][/u]