Android/Linux for CDMA Touch Pro 2 Rhodium Updated 5-20-2010

[cflynt]

Originally Posted by Technix2002

Did anyone besides me with a Rhod500 (Verizon) use Zimage Build: htc-msm-android@20100324_120347? I tried it before anyone commented on it and now it's too late, I've lost wake up control (the top and reset buttons do nothing in Windows Mobile now) and notification lights don't light up either. Has anyone figured out how to fix this?

Nothing has fixed this issue of mine yet: re-done HardSPL, Radio, Hard Reset, and the next zimage htc-msm-android@20100324_160209

I'd have to say that it's upsetting because another user commented that it overwrote a chip... I don't know how I even beging to solve that and I didn't get the extra insurance on my device. <crap>

I am using it on a Rhod 400 and not experiencing any issues. Not sure if it helps you or not, I am running the new Stock 6.5 Sprint ROM and Radio. I am unlocked though. No issues. Sorry to hear your woes.

[clifftrue]

Originally Posted by 00_MACKIE_00

Is the all in one package working for everybody? I did not test it on a clean card.

Yep, it worked great for me to test a script for the US Cellular data issue. I wanted to verify that data still was not working before I posted a revised fix for it.

Anyone with data issues from USCC, and possible others, can find my revised steps to fix data here...

http://forum.ppcgeeks.com/showthread...40#post1656340

Please use the thanks button if this helps you. Also, thank eval- since that is source of my information to make the script.

[cflynt]

Originally Posted by clifftrue

Anyone with data issues from USCC, and possible others, can find my revised steps to fix data here...

http://forum.ppcgeeks.com/showthread...40#post1656340

Please use the thanks button if this helps you. Also, thank eval- since that is source of my information to make the script.

Updated FAQ with latest link. Thanks

[cxh9055]

Originally Posted by Technix2002

Did anyone besides me with a Rhod500 (Verizon) use Zimage Build: htc-msm-android@20100324_120347? I tried it before anyone commented on it and now it's too late, I've lost wake up control (the top and reset buttons do nothing in Windows Mobile now) and notification lights don't light up either. Has anyone figured out how to fix this?

Nothing has fixed this issue of mine yet: re-done HardSPL, Radio, Hard Reset, and the next zimage htc-msm-android@20100324_160209

I'd have to say that it's upsetting because another user commented that it overwrote a chip... I don't know how I even beging to solve that and I didn't get the extra insurance on my device. <crap>

I have the rhod500 and was running the htc-msm-android@20100324_120347 image all day today since it came out practically. I just rebooted into WM and I am able to use the top button perfectly fine. Also the LED seems to be working just fine. I am using the most up to date files other than that.

[cflynt]

It might very well be ROM related. Maybe something in the ROM caused an issue when Android was ran. I run the new Stock Sprint 6.5 ROM. I know that doesn't help you on Verizon. But maybe the ROM you were using before is coincidental?

[00_MACKIE_00]

Not sure how Android could mess up WM.......

[dem0n2001]

my question is ..i always hear how people say haret knocks WM out of memory ..if thats true then why do you have to do the backlight "hack" or how come in the early days you had to call in WM and then run haret.. if its knocking it out none of those things should matter ..no?

[EGOvoruhk]

Originally Posted by 00_MACKIE_00

Not sure how Android could mess up WM.......

It's not messing with WinMo, it's messing with the hardware itself. Meaning it doesn't work in Android or WinMo

Originally Posted by dem0n2001

my question is ..i always hear how people say haret knocks WM out of memory ..if thats true then why do you have to do the backlight "hack" or how come in the early days you had to call in WM and then run haret.. if its knocking it out none of those things should matter ..no?

Because WinMo is currently using the hardware, so it looks different then when things are disabled/enabled. Kind of like how in the earlier builds, you needed to make a phone call before booting, or else the ear piece wouldn't work. It was a cheap trick so that Android could realize some hardware was there

[dishe]

Originally Posted by dem0n2001

my question is ..i always hear how people say haret knocks WM out of memory ..if thats true then why do you have to do the backlight "hack" or how come in the early days you had to call in WM and then run haret.. if its knocking it out none of those things should matter ..no?

Yes and no- I'm not sure if I can explain this correctly, but there are certain non-volatile parts of memory (memory registers, I believe) which supersede the OS and control things like the current state of hardware. For example, when you activate a phone on Sprint for the first time, you need to enter the QPST menu and enter your MDN, etc... (if you've ever swapped phones, you might remember having someone tell you enter some numbers like this). Then allow data to be provisioned, update the PRL, etc... Many of these registers will survive a hard reset. They exist outside of the OS.

If Android is expecting the hardware to be in a certain state and the registers report otherwise, it can cause unexpected behavior.

Not sure if I made it clearer or more complicated, but yes HAret really does knock WM out of RAM.

[mpguy84]

Originally Posted by kitts

I am able to run at 842. It runs lot faster.. feels much smoother..

crazy... what xdanrdoid are u running. I have a RHOD500 and I cant seem to get that high! Whats in your startup.txt? thanks