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

[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.