Quote:
Originally Posted by dishe
I'd like to see ONE PLACE that confirms anything of the sort. You seem to be so sure of yourself... yet, I can assure that this is NOT an OS problem.
This is a Sprint Radio issue. None of my GSM Windows Mobile phones EVER had a problem like this. WinMo is actually very good, but I've seen this happen on Sprint's devices before (some people claimed it happened on the 6700 as well, however I personally never owned one).
I used to experience the random device-wake-up on my mogul in my office, where the device seemed to have trouble figuring out which tower to connect to (weak sprint signal, strong roaming VZ signal). This was very frustrating to me since the last 4 HTC devices I owned never gave me a problem (Tornado, T-mo SDA, Dash, Wizard).
I found that if I were to force the phone into roaming in that weak area, the device would stay off as intended. This is indeed very annoying, but its a good temporary fix. When I leave the office I put the phone back into automatic as intended.
I wrote a little MortScript and posted it on XDA-developers that will switch between roaming and automatic for you.
Just to clarify again: Its a SPRINT issue, and not a Windows Mobile one!!
|
Im not understanding, if this is a radio issue, why does it occur when im not switching networks, there are no updates my phone is receiving, no net connection, im not even moving, i have a full bar signal with sprint (they are the best in my area), and yet i get the
backlight cutting on
wm6 is buggy already, its my assumption (from a none technical standpoint) that this is not related to tower feeds, i'll play around with this later on today tho, being wrong doesnt bother me, but from what ive seen, it doesnt look like a radio issue
*edit* Any alltel wm6 users get this problem?