Android G1: the Java bastard

how-to
Dec 18, 20082 mins

Posting this one from my brand new Android G1. I was looking for a wifi capable phone for quite sometime to ditch my aged Nokia N70 for. Certainly it had to run Linux, Java being a plus. So, G1 choice was pretty obvious. Unfortunately it appeared that there was no chance for G1 to replace N70. G1 is lacking: – Obex/SyncML – you can’t send anything to it via bluetooth – Video calls – no second camera – Navigation s/w that would not require Internet connection – Voip functionality But what it does have (with firmware versions https://www.dusystems.com/g1.jpg And of course everyone is waiting for Android community to produce miracle applications that would put G1 next to aged phones like N70. There is a good reason for that to become true sometime very soon, as there are lots of Java developers around. And Android platform provides unseen opportunities to them. Any Java developer if free to write a piece of Java code, compile and self-sign it with Android tools and put it on the Market. If he gets lucky he can even make some bucks on that. So, Android should greatly benefit from Java. Java is supposed to turn a toy for developers into a top-grade product in notime… But then I’m asking myself – why doesn’t it have any Java(tm) compatible labels anywhere? In my understanding Android doesn’t have anything that would legally tie it to Java. It doesn’t certify its Dalvik Vm against any tests, it doesn’t provide bytecode compatibility, it only states that sources are compatible. Did anyone certify this source compatibility? Guess not. So, technically, Android could be called a Java bastard, as his parent technology is not legally related to him. I will post more on my adventures with G1 soon.