OpenJDK on Android

Mario Torre neugens.limasoftware at
Wed Nov 14 12:22:56 UTC 2012

Eh, I wish we had some more developers than just myself :)

Daneel, the Dalvik-to-Java converter is basically done, though, it works
quite well (that was a different story than the rest of the project, it was
all quite fast and got lots of contributions).

For the rest I did quite some good things, but really, this is not a one
man job, the API is huge, and it requires lots of low level work,
especially for the Insets stuff.

It's fun thing to work on, though, perhaps when I either get some spare
time (or my manager manages to propose the new 48hours day ISO standard! :)
*or* we get more people interested, I could reboot it, I'm always
interested in this project.


2012/11/14 Fernando Cassia <fcassia at>

> On Wed, Nov 14, 2012 at 7:57 AM, Mario Torre <
> neugens.limasoftware at> wrote:
>> To be honest, the likely reason nobody tried those things *for real* is
>> that I don't think it really makes much sense to run desktop applications
>> on such small devices (even if they are actually capable of doing so).
> Android only on phones? Two years ago perhaps.
> Today, Android is increasingly on large-screen TVs...
> If you ask me, the right way to disrupt Google´s disruption of the Java
> ecosystem (pardon the redundancy) is to build the whole Android APIs atop
> the JVM...
> I wish this project had more momentum...
> ---
> IcedRobot is an attempt to bring the Android API on Linux Desktop.
> (...)
> 2. Avoid Dalvik and Harmony as much as possible and put the Android stack
> on top of the OpenJDK class library, and run the whole thing in Hotspot
> (this is cool, ins’t it?).
> ---
> But wtf do I know. ;-)
> FC

pgp key: PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF

Proud GNU Classpath developer:
Read About us at:

Please, support open standards:

More information about the discuss mailing list