11–20 of 21 posts
Anbox is a great idea but it needs a lot of work to become a usable project. Currently, it's only available on a few distros, and app installation instructions are nowhere to be found.
> and app installation instructions are nowhere to be found https://github.com/anbox/anbox/blob/master/docs/install.md ?? Or do you mean for installing Android apps?
Earlier quoted context omitted.
Most Android apps are just JVM bytecode and work on any architecture. Apps using the NDK (native development kit) are architecture-specific and often lack x86 binaries but ecommerce apps are highly unlikely to use the NDK.
Huh, I feel like I used to get tons of "app X wants to load binary Y.so" notifications with XPrivacy for quite a few apps... is it really that rare?
I have an x86 Android tablet and it does emulate ARM binaries but the performance is bad enough that it is pretty obvious when you are running ARM binaries. I'm not sure how hard it would be to integrate libhoudini (Intel's ARM emulator) into this, if they ever even released the code.
Earlier quoted context omitted.
Huh, I feel like I used to get tons of "app X wants to load binary Y.so" notifications with XPrivacy for quite a few apps... is it really that rare?
I wouldn't call it rare in general, but it seems pretty rare within the specific genre of ecommerce apps. Unless they use React Native, that requires the NDK. I have an x86 Android tablet and it does emulate ARM binaries but the performance is bad enough that it is pretty obvious when you are running ARM binaries. I'm not sure how hard it would be to integrate libhoudini (Intel's ARM emulator) into this, if they ever…
I'd love it if I could have both handset and server Android devices and they could talk to each other. Imagine running the server-side part of apps (e.g. always on, attached storage) on a bit of cloud that you own yourself.
I'd love it if I could have both handset and server Android devices and they could talk to each other. Imagine running the server-side part of apps (e.g. always on, attached storage) on a bit of cloud that you own yourself.
Why does it matter what the backend OS is? Why does it need to be Android?
For this to work out, the devices really need to be either capable of running the same native code; or at least need to all be running an abstract bytecode VM with its durable state synchronized between them.
Anbox is a great idea but it needs a lot of work to become a usable project. Currently, it's only available on a few distros, and app installation instructions are nowhere to be found.
> and app installation instructions are nowhere to be found https://github.com/anbox/anbox/blob/master/docs/install.md ?? Or do you mean for installing Android apps?
[0]: https://github.com/anbox/anbox#install-and-run-android-appli...
Earlier quoted context omitted.
Huh, I feel like I used to get tons of "app X wants to load binary Y.so" notifications with XPrivacy for quite a few apps... is it really that rare?
I wouldn't call it rare in general, but it seems pretty rare within the specific genre of ecommerce apps. Unless they use React Native, that requires the NDK. I have an x86 Android tablet and it does emulate ARM binaries but the performance is bad enough that it is pretty obvious when you are running ARM binaries. I'm not sure how hard it would be to integrate libhoudini (Intel's ARM emulator) into this, if they ever…