[CAB] GSM&CDMA Project Android Port and Startup Utility [01/23] FRX04 Reference!

[jerryyyyy]

Hello,

I am a bit new at this and just did my first ROM flash,but wanted to try Android also.

I downloaded ProjectAndroid2.2Froyo.121610 and installed it to my storage card. SIM card out and no overclocking. I believe I am a Rhod400 with Sprint.

I get the android flash screen and animation, but no more. Reinstalled once. Suggestions?

I appear to be rather dead in the water...

[demonlordoftheround]

Originally Posted by jerryyyyy

Hello,

I am a bit new at this and just did my first ROM flash,but wanted to try Android also.

I downloaded ProjectAndroid2.2Froyo.121610 and installed it to my storage card. SIM card out and no overclocking. I believe I am a Rhod400 with Sprint.

I get the android flash screen and animation, but no more. Reinstalled once. Suggestions?

I appear to be rather dead in the water...

Try backing up the entire card, reformat it, then reinstall Android. Double check your startup file for the correct entries. Yes, a Sprint TP2 is a rhod400.

Are you overclocking? Try booting Android without overclocking.

[jerryyyyy]

Originally Posted by demonlordoftheround

Try backing up the entire card, reformat it, then reinstall Android. Double check your startup file for the correct entries. Yes, a Sprint TP2 is a rhod400.

Are you overclocking? Try booting Android without overclocking.

Thanks. I read a bit and cut out the overclocking, so doubt that is the problem... initial screen just comes up and runs and runs and runs.... I have an old 4GB card from my 6800 days and can reformat it (FAT32 I believe) and try again. I believe all my overclocking stuff sits on the storage card, so if I take it out should be definite solution to avoiding that. I'll report back.

I want to see how Android runs since my next phone is likely to be Android unless they do major surgery on Windows Phone 7.

[darylrue]

Originally Posted by jerryyyyy

Thanks. I read a bit and cut out the overclocking, so doubt that is the problem... initial screen just comes up and runs and runs and runs.... I have an old 4GB card from my 6800 days and can reformat it (FAT32 I believe) and try again. I believe all my overclocking stuff sits on the storage card, so if I take it out should be definite solution to avoiding that. I'll report back.

I want to see how Android runs since my next phone is likely to be Android unless they do major surgery on Windows Phone 7.

Ok, here is what I did to get mine to finally work with a good amount of stability. Any other way I tried did not work and I tried several ways.

1. uninstall and remove all android file references from storage card (no class 10).
2. Install from this thread link.
3. Copy new zimage and module files from xda-forums for 12-25 under TP2.
4. Launch using haret.exe give it as much time as it needs to load or crash or whatever.
5. Reboot launch using startup utility, only check rhod400 and force cdma. give it a long time after startup before dinking with it.

you now have working android that is fairly stable. I tried other ways and recieved many errors, lockups, reboots, etc...

I think I might try the 3d drivers again but maybe not since everthing is working ok except exchange email from 1 account (calendar is syncing though) and I hate to have to reload everything. Good luck.

Feel free to email me and I can email you the 2 files right away. email darylrue@gmail.com . Good luck. Hope the above instructions work for you and it is not just me.

[jerryyyyy]

Originally Posted by darylrue

Ok, here is what I did to get mine to finally work with a good amount of stability. Any other way I tried did not work and I tried several ways.

1. uninstall and remove all android file references from storage card (no class 10).
2. Install from this thread link.
3. Copy new zimage and module files from xda-forums for 12-25 under TP2.
4. Launch using haret.exe give it as much time as it needs to load or crash or whatever.
5. Reboot launch using startup utility, only check rhod400 and force cdma. give it a long time after startup before dinking with it.

you now have working android that is fairly stable. I tried other ways and recieved many errors, lockups, reboots, etc...

I think I might try the 3d drivers again but maybe not since everthing is working ok except exchange email from 1 account (calendar is syncing though) and I hate to have to reload everything. Good luck.

Feel free to email me and I can email you the 2 files right away. email darylrue@gmail.com . Good luck. Hope the above instructions work for you and it is not just me.

I appreciate the offer of help, but I bagged the try from the .cab and am trying the .rar now. I hung for 5 minutes on a message that I needed the roofile system unzipped... then it took off again. But looks like it is hung.

I looked in the files and there is a rootfs.img. I'll see what that does.

[touch-this-pro]

question: can I install this android into an encrypted SD card?
thanks

[jlpatte2]

Just got around to trying to play with fxr03 and (also tiad's mods) and they both seem horribly nearly uselessly slow. I had previously had success using blazin2.2 from september as an basically usably quick system, any ideas what I should be looking at to understand the root of my slow speeds?

Update:
So it appears that the android startup utility had checked "HW3D" and that that was causing my insane slow issues; is this option not neccesary to make use of the newer 3d driver sets?

PS I don't intend to bash, I was just legitimately confused why it seemed like things had slowed down so much... This project is defintely doing great stuff, and it feels like I will have support on my "old" phone much past any life winmo was going to give it. Thanks All!

[jerryyyyy]

Originally Posted by jlpatte2

Just got around to trying to play with fxr03 and (also tiad's mods) and they both seem horribly nearly uselessly slow. I had previously had success using blazin2.2 from september as an basically usably quick system, and ideas what I should be looking at to understand the root of my slow speeds?

Have to say I agree with you with only 12h experience. I guess this proves the point you can get Android up and running on a TP2, but it is too slow to be useful. Maybe we are missing something. My build is in my signature. I did not OC the Android build. This is all a bit tricky interacting with the Windows Mobile OCing.

[manekineko]

Originally Posted by jlpatte2

Just got around to trying to play with fxr03 and (also tiad's mods) and they both seem horribly nearly uselessly slow. I had previously had success using blazin2.2 from september as an basically usably quick system, any ideas what I should be looking at to understand the root of my slow speeds?

Originally Posted by jerryyyyy

Have to say I agree with you with only 12h experience. I guess this proves the point you can get Android up and running on a TP2, but it is too slow to be useful. Maybe we are missing something. My build is in my signature. I did not OC the Android build. This is all a bit tricky interacting with the Windows Mobile OCing.

FYI, it sounds very much like you two are running into the system process choking the CPU bug that is very common these days. If your build is running significantly less smooth than tiad8's video, this is most likely what's going on:
http://forum.ppcgeeks.com/tp2-androi...x03-tiad8.html

There's a bug that's causing the system process to randomly consume all of the CPU on boot, slowing Android to a crawl. This only happens some of the time, and it's unclear what is causing it, but the devs are aware of the issue and looking into it. It can usually be fixed by making a call to any number, voicemail is an easy one. Alternatively, using Dev Tools => Bad Behavior => crash the system server also usually fixes it.

[khowe]

Originally Posted by manekineko

FYI, it sounds very much like you two are running into the system process choking the CPU bug that is very common these days. If your build is running significantly less smooth than tiad8's video, this is most likely what's going on:
http://forum.ppcgeeks.com/tp2-androi...x03-tiad8.html

There's a bug that's causing the system process to randomly consume all of the CPU on boot, slowing Android to a crawl. This only happens some of the time, and it's unclear what is causing it, but the devs are aware of the issue and looking into it. It can usually be fixed by making a call to any number, voicemail is an easy one. Alternatively, using Dev Tools => Bad Behavior => crash the system server also usually fixes it.

Opening and closing Google Maps seems to work, as well.