hey guys, i'm still having random reboots despite updating my firmware to 2.36 already. anyone having the same issues?
This is a discussion on random reboots within the Motorola Milestone forums, part of the Android Smart Phones category; hey guys, i'm still having random reboots despite updating my firmware to 2.36 already. anyone having the same issues?...
hey guys, i'm still having random reboots despite updating my firmware to 2.36 already. anyone having the same issues?
Do you know what trigger that? I'm getting pissed off with the random reboots..
Sent from my Milestone using Tapatalk
Well, ive been thinking about this recently - after a couple of especially glitchy days... must be the heat![]()
I dont remember suffering random reboots before (and ive been on 2.1 update1 since day 1). But two things had changed:
installed auto task killer
randomly fiddled with vsel settings for 1000/ 900/ 800 mhz overclocks
So - i have found a relatively stable vsel value of 56@900. And i have stopped using automatic task killers. Now i simply hit up control panel and hold.
What do you know... no more random reboots, just like before
To conclude - they are not happening by faulty design on my milestone. Please, correct me if im wrong to assume so...
Edit: i should say i noticed 0 benefit from auto task killer.
Last edited by ftgg99; 07-13-2010 at 03:19 PM.
So you saying about heat, but how do I reduce the heat? I'm not rooted and the random reboots are killing me.
Just to add, mine is a soft reboot, which means when reboot, it straightaway goes to the android screen and not the telco brand.
Last edited by bryant_16; 07-13-2010 at 08:51 PM.
Telus Milestone, stock 2.1-update1, rooted, lightly themed, but not overclocked... And no random reboots.
I did have a magnet-free case that would kill the battery in under 2 hours, and leave the battery cover uncomfortably warm. I determined it would only happen if the phone was "on" inside the case-- I'm guessing some button was being pressed.
Other than that, the phone's been solid. No auto-task killer (well, outside of the native OS), but I do have advanced task killer which I use on occasion.
... just another data point if anyone cares.
bryant_16 - are you using a taskkiller? my guess is that it is responsible. For example, android os may be dealing with a background overflow at the moment when you put the phone to sleep. If at this point a auto task killer simply removes the cache for the affected app from memory, the system would likely crash.
Hi there,
I'm not using any task-killers or any similar related applications. I'm using stock firmware.