Porting Andoid on A1200 MING

[sabrod]

No need to thanks.

i posted the latest binary i built of phonetools here in the dev. forum: http://www.motorolafans.com/forums/d...tml#post186607

note that you'll may have to unzip it achyudhram.... :/ :/

Well anyway, even if i had fun with phonetools gmzhuo always considered it as a development tool rathr than any user flashing utils, etc... So it may not work for something else than sending genblob and a kernel.

Muromec buid also a ( i gues similar, but in python) tool, named putusb, Index of /muromec/putusb also a win version is avalaible, and there is also a test qtopia fw to flash with it, at Index of /qtopia/firmwares/ ( test1.tar.gz ) .

I can't tell you much about these tools, except what you can see: they are new, and not widely tested, so i would stay with the old working method.... Especially flashing could be dangerous, i suppose, so be aware...

Please post any issues and feel free to pm me about the matter, and in separate threads if they aren't related to android port...

[achyudhram]

ok. tryting

[achyudhram]

Sorry sabrod,,,,,,,,,,,,,,,,,
but both are not working. Both Report "Not Found"

iam using vista and ubutu. any thing needed to get these to work?

It is detected by RSD Lite and Os too.

[pry]

How to Run Google's Android OS on Your Windows PC - In just a few easy steps - Softpedia



port android on ew pc

[skynet.boy]

Hi,
I follow the instruction on "Porting Android to A1200" PDF file.
when i isuse the make command, the compiling process started
but after 10-15min the compilation process stopped with flowing error messages:

make[2]: warning: Clock skew detected. Your build may be incomplete.
LD .tmp_vmlinux1
kernel/built-in.o: In function `getnstimeofday':
utsname_sysctl.c: (.text+0x22b90): undefined reference to `__aeabi_uldivmod'
kernel/built-in.o: In function `do_gettimeofday':
utsname_sysctl.c: (.text+0x22c3c): undefined reference to `__aeabi_uldivmod'
utsname_sysctl.c: (.text+0x22c5c): undefined reference to `__aeabi_uldivmod'
kernel/built-in.o: In function `timekeeping_resume':
utsname_sysctl.c: (.text+0x22e00): undefined reference to `__aeabi_uldivmod'
utsname_sysctl.c: (.text+0x22e1c): undefined reference to `__aeabi_uldivmod'
kernel/built-in.o:utsname_sysctl.c: (.text+0x2349: more undefined references to `__aeabi_uldivmod' follow
make[1]: *** [.tmp_vmlinux1] Error 1
make[1]: Leaving directory `/home/neo/android/linux-2.6.24'
make: *** [zImage-a1200] Error 2

what is wrong?
i want to port Android to my A1200 Cellphone, but i can't
please help me!!!
thanks.

[sabrod]

these steps should at least work. That guides worked for me, at least, very well, even if i don't have the skills for doing such job, the compile time was quite calm, following the guide....
Try to understand more what you are doing, i mean if you want to "port" the opensource software, you will have to understand how to write a driver, anyway, so better to begin by reading them... I mean in the patches and openezx code... Actual or ancient.
(openezx continued its travel after that "GUIDE TO PORTING ANDROID" you also might want to read the openezx.org wiki...)

That said android would still be a nice stuff to have, maybe... I would like some release to work on our ezx too... and i think it will be done, one day, lets hope someone continue the good androidezx work!! ... (if you ask me, i am more placing "hope" ( and efforts) in FSO2 or SHR to have a powerfull distro, because there is already some testers, and devleoppers around this, and it actually already work more or less, and the opensource thing is much more clear it is GNU! but anything to compare would be nice... ( so) )

[novinsab]

Can any one provide the compiled ARM-EABI compatible openEZX patched kernel for the android for Hainan-a1200?
I am not very used to compiling stuff under linux especially ubuntu!!!

Thank you.

[novinsab]

Can anyone atleast provide me the android_nfs/lib files? I successfully compiled the kernel zimage but the android nfs modules fail

[sabrod]

nfs is not in module, double check if you have it on the zImage.
It must be compiled "in-kernel", because if not, the kernel will never be able to find the rootfs, wich is on an nfs export.
And if you wants to devel from a rootfs on sd card, then you don't need nfs at all...
I suggest you to try a little more with nfs, as you maybe have the tuto from android-ezx, (at first post) but please read the thread entirely if you can , ( i think there are some nice posts from pages 7- 10. AT LEAST go from 1 to 12! iirc it there are some traps you will be able to "manage" if you read this thread, will save you time, trust me!)
Nfs is good, because it is fast to erase, and rewrite, etc... For modifiing things, etc. Also if the kenrel hang, sometime it create data corruption on the sd, so you will have to re-format it. wich maybe nfs-root can prevent.

[novinsab]

Thanks sabrod... I just finished reading the whole thread from page 1 to this... and I am a bit confused but I think it helped me to overall understand what I am doing here...
Since the init memory is freed by kernel i am guessing that the problem is with the kernel I am using... I just downloaded muromecs android image from his openezx file deposit... its zImage-android
I tried compiling the zimage but since I could not patch the android patches because of the same extra operand error I just stopped the procedure...
The problem might be that I am using 2.6.30 openezx+android kernel but the android file system is for 2.6.24...

BTW, NFS never worked for me because kernel kept saying that /dev/nfs cannot be found!!!!

Do you have a compiled zImage for android rootfs of 2.6.24?