Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

possible duplicate effort (android) #677

Open
Mis012 opened this issue Sep 15, 2024 · 0 comments
Open

possible duplicate effort (android) #677

Mis012 opened this issue Sep 15, 2024 · 0 comments

Comments

@Mis012
Copy link

Mis012 commented Sep 15, 2024

I guess it depends what your ultimate goal is, but I see that you have started implementing some android APIs (e.g Bitmap.java), which overlaps with our project: https://gitlab.com/android_translation_layer/android_translation_layer, though we don't currently support using arm libraries on non-arm systems.

Since this project is mostly focused on the problem of emulation, it might be beneficial for you to utilize our project for dealing with android APIs (both java and native).

For non-time-critical stuff one could just use (parts of) our project in an aarch64 alpine chroot with qemu-user, but we can also run full apps which would absolutely benefit from only emulating the parts that need to be emulated.

We simply use art (though we have some patches on top for various reasons), and it seems that it should be possible to utilize the "native bridge" functionality (mainly used by intel's houdini) to load arm libraries on non-arm systems. https://github.com/goffioul/ax86-nb-qemu is an open source implementation of a "native bridge", which supposedly works with AOSP (we have not tried to get it to work with our project yet), but I wonder if something like dynarmic would be easier to deal with since it's in-process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant