atl/android_translation_layer
0
0
Fork 0
mirror of https://gitlab.com/android_translation_layer/android_translation_layer.git synced 2025-10-27 11:48:10 -07:00
Code Issues Packages Projects Releases Wiki Activity

fix up / update README

Browse Source
This commit is contained in:
Mis012
2022-07-25 13:02:43 +02:00
parent 8fedbfb438
commit 456d5eb3d9
1 changed files with 18 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@@ -36,8 +36,7 @@ screenshot:
![angry birds 3.2.0, Worms 2 Armageddon, and gravity defied running side by side by side](https://gitlab.com/Mis012/android_translation_layer_PoC/-/raw/master/screenshot_2.png)
note: running two or more different apps at the same time needs a tiny bit of luck, since the data directory path is currently hardcoded to `./data/` no matter the app
note: the GLSurfaceView widgets currently start out with zero width, which is somewhat helpful for debugging so it wasn't fixed yet; to get the app to start rendering, enable hexpand on the Wrapper widget around the GtkGLArea using Gtk Inspector
note: running two or more different apps at the same time needs a tiny bit of luck (no conflicting files), since the data directory path is currently hardcoded to `./data/` no matter the app
##### FAQ:
@@ -76,6 +75,16 @@ A:
angry birds (old version) and worms 2 armageddon were chosen because they similarly don't use
compat layers, and basically the entire UI is custom drawn with OpenGL calls from native code.
Q:
why are only 32bit architectures supported?
A:
we are currently using good old dalvik vm (probably newer commit than ever shipped though), which
is so hopelessly hardcoded to assume 32bit ints and pointers that it probably made google's cost/benefit
analyses of writing art from scratch a lot easier.
Eventually, we should probably move to ART, but it's an open question whether that will bring issues for our
usecase (is there a way to use ART without zygote? is it straightforward to port the few modifications that we did to dalvik?)
##### Roadmap:
- fix issues mention above
@@ -86,4 +95,8 @@ A:
- implement more stuff (there is a lot of it, and it won't get done if nobody helps... ideally pick a simple-ish application and stub/implement stuff until it works)
- implement the alternatives to GLSurfaceView (using SurfaceView to get an EGL surface, native activity, not sure if there are others?)
- especially implement the alternatives to GLSurfaceView (using SurfaceView to get an EGL surface, native activity, not sure if there are others?) which would allow us to support a few more 99%-native applications with relative ease
- explore switching to ART in the interest of supporting 64bit architectures
- explore using apparmor to enforce the security policies that google helpfully forces apps to comply with (and our own security policies, like no internet access for apps which really shouldn't need it and are not scummy enough to refuse to launch without it)