|
||||
So let me get this straight, even when the phone is in 'zombie' mode, a soft reset with the stylus will not reboot the phone right?
You have concluded yourself that you putting the phone in flight mode (to keep your alarm but not notify you on anything else) is causing the issue and by NOT putting your phone in flight mode overnight you do not get this issue. My suggestion (coming short of telling you to reflash and start new) is to tell you to try a freeware app for alarms, stay out of flight mode, or go buy an alarm clock if you want to have something wake you up in the morning.
__________________
Loving my rooted Droid X
Last edited by weedahoe; 02-13-2008 at 02:59 PM. |
|
||||
OK ... So maybe I'm a bit abnormal in how I utilise my phone, but it's a tool that for the most part works for me and is quite solid - so work with me ...
In the posts I've read/found today, some folks seem to think this zombie issue may be tied to activesync... If that is the case, then perhaps because I'm in "flight mode" when there is a sync attempt to my exchange server, it locks up ... That'd be interesting to check ... As for my batteries, they all tested fine ... I have learned though that I may just need bi-focals now ... There were a + and - labeled on the battery ... Just really needed to adjust my view-point to see them ... |
|
||||
No, i use my phone as an alarm sometime as well and there is nothing wrong with doing that. What I am implying is that sometimes when we hack and mod our devices and load with 3rd party software, other minute side effects can occur. If you think AS is causing the issue then close it out by (in XP) going to your task manager and closing wcescomm.exe and leaving it in the cradle. Another way would be to not leave it connected to the PC but rather to a wall charger. If your phone no longer has those same issues with you still using it in the same manner then you know what your issues is/was.
|
|
||||
G-r-e-a-t ...
Had a night of no zombie .... System was on battery not plugged in ... Guess this means it's time to go back to the drawing board and try to figure out what program interactions may be causing this - a potential buffer overflow? Of course, I have tomorrow to look forward to; what with the mutiple reminders on each alarm (not just a WM6 feature) and all
Thanks for the thoughts ... I'll put up another post if I think I come across something. Cheers |
|
|
|