• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Did this bork my phone?

MizzouBrent

MizzouBrent

Android Expert
Last weekend I installed the kingdom GPS driver on my phone and it spiked my CPU to 100%. This was on a Friday afternoon and I didn't realize what was going on until Monday morning.

I had some reboots over the weekend so I installed a new GPS driver but I still have been seeing reboots. Most are when I'm doing something intensive on system resources like playing angry birds but I've had some reboots doing less intensive things as well.

I'm trying to convince myself its not a hardware issue and that it can be fixed but I'm not so sure. I'm running rooted stock now so it can't get any more stable than this.

I would like to think that I didn't do this to myself. Surely three days of a spiked CPU couldn't break my phone right?
 
what hw is your phone? mine was hw4 and about a few months ago, i would get random reboots. i also noticed that my phone would get warmer then normal. i tried different roms and the same thing. i then tried rooted stock, same thing. i even unooted and same thing. so i took it in and got a refurb evo. i then immediately rooted it. so not sure if the issue is the same or not for you. i do not think that it is the gps drivers that are cuasing the reboots.

if your phone reboots on the stock rom, i would contemplate unrooting and see. obviously do not accept the ota. but if it is still happening then maybe a sprint tech might help. however keep in mind that they may give you a new or refurb phone but they are starting to come in with 2.3.3. already installed.
 
I'm hw003 right now. So far no reboots on stock 2.3.3 rooted. I have been giving it quite a workout and just gave it to my son to play Angry Birds. I guess if it doesn't trigger a reboot, then that's a good thing. But it seems like my phone is definitely getting more sensitive to things it could handle in the past.

I'm using the exact steps you recommended so far. If I can reproduce on the stock root version, then I'll unroot and try to see if I can reproduce on stock without root, then take it in. It really stinks though. As I'm typing this, it just froze in the middle of Angry Birds and I had to do a battery pull. Ugh.
 
Ok after the battery pull, I let it set for a minute or two, tried to fire up Google Maps and it rebooted after like 15 seconds. My official non-expert opinion is that it's a CPU heat issue/failure. Guess I'll unroot and take it in tomorrow.
 
yeah if it keeps happening, i would might think about just waiting until an exploit is fond. cuz if they get you a new or refurb phone, you will be fubar until they do.
 
One of the first things the tech will probably ask/do is update the phone. They'll suggest that the update will fix the problem. I took my phone in (unrooted) to have the ear speaker replaced and I had to specifically ask them NOT to update the firmware to gingerbread. I told them I didn't want Gingerbread because I had a few apps that I used for work that didn't behave well with GB and updating would make my phone worthless for work. They bought that so they left it alone and didn't ask again.
 
I have been having the same issue...seems to occur any time I am doing multiple things, using nav, or when I am taking alot of video or pics

one thing you can try is to flash the rooted 4.22 software..basically full wipe and run stock and see if the issue remains.

I don't believe this is due to the updated gps drivers, as my phone was doing this prior to

Several late 003 and early 0004 phones had reboot/heat issues ..I am wondering if this is the case on ours?
 
isn't the reboot issue a precautionary measure of android when your memory gets maxed out and it can't run anything else, it reboots the phone to clear out?

my 002 used to do this a lot when we were on android 2.1, never really did it on 2.2. at least not frequent enough for it to matter.

my 004 (battery door date of april 2011) didn't really ever do it on 2.2 (though that was only for a couple of hours) I brought it home, rooted and flashed mikg. I know the sense 3.0 elements use more memory to run and I had a few random reboots while on mikg 1.xx

since flashing mikg 2.1 I haven't had my phone reboot on me.

I think this would make sense if your phone is pegging the cpu at max and then rebooting.

have you tried flashing a different radio? maybe try downgrading to pri 1.77

what recovery version are you using? I recommend using RA and doing a full wipe and reflash of the stock rooted 2.3.3 and see what happens.

you may want to start by trying to track down your cpu at max issue? do you have spare parts or the paid version of system panel?
 
Drew5150 said:
isn't the reboot issue a precautionary measure of android when your memory gets maxed out and it can't run anything else, it reboots the phone to clear out?

my 002 used to do this a lot when we were on android 2.1, never really did it on 2.2. at least not frequent enough for it to matter.

my 004 (battery door date of april 2011) didn't really ever do it on 2.2 (though that was only for a couple of hours) I brought it home, rooted and flashed mikg. I know the sense 3.0 elements use more memory to run and I had a few random reboots while on mikg 1.xx

since flashing mikg 2.1 I haven't had my phone reboot on me.

I think this would make sense if your phone is pegging the cpu at max and then rebooting.

have you tried flashing a different radio? maybe try downgrading to pri 1.77

what recovery version are you using? I recommend using RA and doing a full wipe and reflash of the stock rooted 2.3.3 and see what happens.

you may want to start by trying to track down your cpu at max issue? do you have spare parts or the paid version of system panel?
Click to expand...

Well if the reboots are just a memory issue, that makes me feel a little better. I'm not sure. I know there's a thread on XDA about reboots, but I haven't read much of it yet because my problem isn't unbearable yet.

I was actually running MikG on Saturday and Sunday. I had about 3 reboots while using it, so I switched over to the stock rooted rom. It performed better, but I got it to reboot after I played Angry Birds for about a half hour. Normally I wouldn't do this, but I was trying to see if I could get it to reboot and I did.

I'm not getting any more CPU pegging at least. I have been keeping a close eye on it, and I'm not using any of the GPS driver that were causing the spike, so so far, so good with that. But even without the CPU spikes, I have seen them. Usually when doing something with the GPS or playing a game for a long period of time, so definitely during the more intensive things. I'm not ever getting them when the phone just sits there.

I use Amon RA 2.3. I upgraded to the newest radios when they became available, then downgraded back to the November radios. I have since re-upgraded to the new radios/PRI. I'm pretty happy with the way my phone is behaving now.

I was actually getting really frustrated over the last couple of days, because while using AOSP roms, it seemed that the HTC Vision GPS driver had been draining my battery even without an apparent wakelock, but that issue seems to have gone away now. I'm not sure what I did to fix it.
 
You must log in or register to reply here.
Back
Top Bottom