Hacker News new | ask | show | jobs
by y4mi 1615 days ago
my acer chromebook from 2015 got support.

i dont think the fault is entirely with google here, asus shouldn't have marketed it as that, considering your chromebook had an arm processor - great for battery life, but google really only implemented the docker/shell and android support for intel cpus.

really unfortunate though

1 comments

Ironically, most Android apps are built for arm processors.
I think the Chromebooks Android support is more like the virtual devices that Android studio creates then actual native installs.

It's been quiet long since I've last I checked it out, but at least at that time the locale was different inside the android apps vs chromeos (including keyboard layout etc) and there was a separate settings app like on any Android devices with dummy values in hardware etc.

It was funny because it let me install Firefox on the Chromebook but it felt more like gimmick then an actually useful feature as a lot of apps just outright didn't work

Most android apps are java. They should be built for jvms. The fact that we have java jars that fail because of hardware architecture invalidates java as an idea to me.
I don't think Android uses a JVM. Android apps are AOT compiled from DEX bytecode.