Well, being a converted Google Android fan boy. I am way not too excited. Don’t get me wrong, I will still be there and hanging around.
Why ? Here you go.
From : Here
Conclusion
In summary, Android is compiled for ARMv5, Neo 1937 is ARMv4. These instruction sets are not compatible. Therefore Android will not run on the Neo 1937. Solutions to this problem would be either:
* FIC releasing a version of the Neo based around an ARM926 core.
* Google compiling for ARMv4 and making that available.
* Google releasing the source and someone else compiling for ARMv4.
My guess is none of those three things is going to happen any time soon (although I’ll be really happy to be disproved!), so it is better to focus on trying to get this running on an actual ARMv5 based chipset. (E.g: PXA270, i.MX21).
May the force be with you.
After few sleepless night, “full” porting of Ruby over to Android finally works. Porting Ruby over to ARM platform is pretty much tricky but it is very cool project.
To make sure most of the RoR stuff work, my target is to get Metasploit 3 runs on Android. Running a full Metasploit is pretty much at Android emulator. But I guess at least I am reaching some where.
So for people who loves Ruby, doing RoR on Android will be a cool stuff. I At this stage, I’m not sure what type of benefits it will bring to the RoR developers. But i guess this is pretty much a good alternative for RoR loves, alternative for Java :)
Well, I did not code anything on RoR (UI design is alwats a hardjob) , but I do code alot on Ruby. Again, Rails not Ruby.
Screen Shot for metasplot on Android :
Read more…
Finally, I got Android running HTC TyTN II (Kaiser).
Thanx to XDA-Developers forum and lgorris. Things are pretty much unstable. It might be due to the original ROM is not too workable.
According to lgorris,
Google Android:
*make sms work
*make phone calls more stable (if the other side hangs up, dialer is frozen and connection kept up)
*get more overall stability (get rid of the random hangs; data connections always cause hang after some time)
*wait for sourcecode/better working binary blobs
==> ask dzo for his reverse engineer’D rilphone library code (that’s what provides the AT communication and so) and go improve it; dzo is the same person who put together android.bin
I guess still pretty much long way to go.
At this moment, Go and get a HTC Dream from T-Mobile :)
Screen shots,
Read more…
Update : 16th September 2009
Ruby and Busy manage to run peacefully in Google Android. Tested with some tools from ortegaalfredo. ortegaalfredo manage to compile strace gdb and bash to run in Android.
Some Small ScreenShot from Android :
bash-3.2# cd /data/opt/bin/
bash-3.2# ln -s ./busybox uname
bash-3.2# ./uname -a
Linux localhost 2.6.25-00350-g40fff9a #1 Wed Jul 23 18:10:44 PDT 2008 armv5tejl unknown
bash-3.2# /data/usr/bin/irb
irb(main):001:0> 1+1
=> 2
irb(main):002:0> exit
bash-3.2#
How can can we move on with Iphone ? or I am too poor to buy OpenMoko.
What’s Next for Android ? :) Stay Tune.
Small little task for my and myself. I manage to run Ruby within Android. It took me sometime to figure out how this work.
Now i got this on my Android.
ruby 1.8.7 (2008-08-11 patchlevel 72) [arm-linux]
Its not too hard to make this work in Android.
At least, something work in Android. Next will be some little Ruby apps runs in Android.
Night with Bad Flu.
This is a long story.
As a Apple freak, I always wanted an Iphone. The reason is … … Apple provided the SDK. Well, due to some funny and lame reasons, i still have not get to own any Iphone until today. Again, due too all the rules that set by Apple towards the coding environment in Iphone, I decided to hold my idea.
Along the way, My mind switched. I looked in to Openmoko and it seems to be cool. Of cause, the other alternative is Android.
Comparing Openmoko and Android, I strongly believe Android got a better future. At least at this point of time Google is planing for Google Apps Store. Software support for Openmoko seems to be way too far.
Well, after all these crappy story. I decided to go for Android and wait for Google and HTC to do something about this.
Good Night.