I think Verizon's network is causing the reboots

[Sparkyvett]

I'm getting bummed out about the reboots. My phone seems to reboot at work a lot. Never at home. This is killing my battery there.

Starting today, I've resorted to turning my phone off completely while at work. So at least it won't reboot. I only check it at lung anyway. But, cmon already.

I agree, These reboots also kill my battery while I'm at work. Its funny how my phone doesn't have any issues while its on wifi at my house. As soon as I turn off wifi, let the reboots begin!:'(

 

[Chrisy]

Yup. I don't have reboots at home at all. I'm on 3G here but must be connected to a different tower than when I'm at work.

 

[jlgraham]

I'm unbelievably frustrated by Verizon. Everytime I call customer service they are of no help and always have a different excuse for the reboot problem. I'm on my third Thunderbolt and it has the same issue! It's like my old Palm Pre again.

I've been calling Verizon every day and I made quite the scene in the Verizon store...I think more people need to be adamant about this because Verizon doesn't seem to be willing to acknowledge how bad it is, and of course they refuse to send me any other device as a replacement.

 

[PJnc284]

My advise is to take this fix with a large dose of salt. I have never seen a task killer *stop* reboots. I have seen it cause them. I have been in cellular Tech support long enough that it makes me HIGHLY skeptical.

However, if it works, it works. Can't argue with results.

If a task killer works then it's because of a poorly written app in which case you should probably be trying to figure out what it is so you don't get reboot hell if you actually decide to use the app. Task killers should NEVER be the answer.

 

[VideoEngineerAJS]

I'm unbelievably frustrated by Verizon. Everytime I call customer service they are of no help and always have a different excuse for the reboot problem. I'm on my third Thunderbolt and it has the same issue! It's like my old Palm Pre again.

I've been calling Verizon every day and I made quite the scene in the Verizon store...I think more people need to be adamant about this because Verizon doesn't seem to be willing to acknowledge how bad it is, and of course they refuse to send me any other device as a replacement.

I don't think we know how bad it is. I along with many others aren't having an rebooting issues at all. That's why this thread is here. I mean it's obviously not strictly the phone if you are on your third one and you're still having the same issue.

 

[jlgraham]

In any case, I was firm enough (after 2 1/2 hours on the phone, and 3 different supervisors) with customer service that they agreed to send me a Droid X2 instead of the usual replacement even though I've had my Thunderbolt for over a month. Bye bye HTC.

 

[brett328]

If a task killer works then it's because of a poorly written app in which case you should probably be trying to figure out what it is so you don't get reboot hell if you actually decide to use the app. Task killers should NEVER be the answer.

If a task killer works or not, I shouldnt have to track down the culprit no matter what. VERIZON and/or HTC needs to get on the stick, NOT ME!

The point is, this may provide some temporary relief until such time as a TRUE fix is discovered or GB takes us out of this purgatorious situation.


p.s. now 24 hours, heavy use, no reboot as of yet. task killer set to kill tasks every 30 minutes. Still at 55% battery 8 1/2 hours since off charger.

 

[FrankXS]

If a task killer works or not, I shouldnt have to track down the culprit no matter what.

Absolutely not true, IMHO. The whole point of having an Android phone rather than an iPhone, for example, is to allow 3rd party developers to create apps and distribute them without HTC/VZW/Google's/Apple's evaluation and permission. The price you pay for this flexibility is that it becomes your responsibility to "track down the culprit" when you load poorly behaving apps. It comes with the deal. Take it or leave it.

-Frank

 

[brett328]

The whole point of having an Android phone rather than an iPhone, for example, is to allow 3rd party developers to create apps and distribute them without HTC/VZW/Google's/Apple's evaluation and permission. The price you pay for this flexibility is that it becomes your responsibility to "track down the culprit" when you load poorly behaving apps. It comes with the deal. Take it or leave it.

-Frank

Uh, NO! the whole point for me is that I dont want an iphone! Plain and simple! No itunes syncing, no Apple sauce either! Not sure what your reason is, nor would I speculate.

But before we even go there, did I miss something? Now everyone has concluded that the culprit is an APP? Wanna bet? My phone started misbehaving after the OTA, not after a downloaded App. Dont have to be a rocket scientist here boys. Its in the firmware update for sure! that makes it Verizons and HTC's nut to crack!

Again, we are here to try and find help, and or workarounds. So far the task killer is still on the table for me, and my TB is not rebooting. right wrong, stupid, or not. I likey when phone doesnt reboot in the middle of some important task. I thought others might feel the same way.

 

[PJnc284]

But before we even go there, did I miss something? Now everyone has concluded that the culprit is an APP? Wanna bet? My phone started misbehaving after the OTA, not after a downloaded App. Dont have to be a rocket scientist here boys. Its in the firmware update for sure! that makes it Verizons and HTC's nut to crack!

Again, we are here to try and find help, and or workarounds. So far the task killer is still on the table for me, and my TB is not rebooting. right wrong, stupid, or not. I likey when phone doesnt reboot in the middle of some important task. I thought others might feel the same way.

uhmm...are you aware of what task killers do? They kill apps and background tasks. For a task killer to be the answer, it's almost 100% have to be app related. I'm guessing it's just a placebo though and there's something else going on. My guess, whether Verizon wants to admit it or not, is still that it's radio/signal/tower related. The only reboots I've had were at my parents house outside of wilmington, NC. While there, I could go all day without one or have 2-3 in one day. I've have yet to have one here in raleigh/garner where I live and work.

Things we know:
1. It isn't limited to only 3G or LTE areas.
2. It isn't Verizon bloatware related because the custom roms reboot also
3. MR1 based roms have the problem more than devices running release firmware
4. Adjusting the radio combination seems to get rid of the problem

You do the math.

 

[brett328]

uhmm...are you aware of what task killers do? They kill apps and background tasks. For a task killer to be the answer, it's almost 100% have to be app related. I'm guessing it's just a placebo though and there's something else going on. My guess, whether Verizon wants to admit it or not, is still that it's radio/signal/tower related. The only reboots I've had were at my parents house outside of wilmington, NC. While there, I could go all day without one or have 2-3 in one day. I've have yet to have one here in raleigh/garner where I live and work.

Things we know:
1. It isn't limited to only 3G or LTE areas.
2. It isn't Verizon bloatware related because the custom roms reboot also
3. MR1 based roms have the problem more than devices running release firmware
4. Adjusting the radio combination seems to get rid of the problem

You do the math.

So, lets see, there's no way the new firmware could be adversely affected by the amount of open app and or processes in the background? It absolutely has to be related to a single app, and not some weird reaction to the size or number of processes processing? WOW, you are quite the deducer! I suppose you designed the the new firmware too, since this would nearly have to be the case for such a deduction to be true.

 

[PJnc284]

Possible but unlikely. If it were related to an app or process limit, it would be more widespread, wouldn't happen in certain areas and not others and likely wouldn't happen on freshly reset devices that hadn't even had a google account set up on it yet.

 

[dms76]

My new replacement will not register that an update is available. I've manually check for an update several times today as to decline it. I keep receiving no updates and my current firmware dated 2-17-11
1.160.0223r and the WiFi connects to a hidden ssid. So I wonder if Verizon pulled the update?

Sent from my ADR6400L using Tapatalk

 

[Malibu02]

IMO it is becoming painfully obvious it is tower, network, or radio related.
I have 0 reboots at home but when i switch towers I get one.
I do wonder why , considering the hit Verizon is taking by replacing phones and bad PR, they havent come out with even a press release i.e. What process is in place to resolve? Is work being done to ensure the GB release will resolve these issues? Is this related to implementation of LTE?
At some point it will be picked up by the press i.e. MSNBC, CNN , ZD Net or others and by then they may have painted themselves into a corner by letting this fester regardless of how widespread the issue really is.

$.02

 

[Mortiel]

If a task killer works then it's because of a poorly written app in which case you should probably be trying to figure out what it is so you don't get reboot hell if you actually decide to use the app. Task killers should NEVER be the answer.

Actually, on the contrary... It the testing I have been doing on the Thunderbolt, I notice a few things:

1. The Thunderbolt crashes immediately upon booting up in safe mode. All safe mode does is disable all non-core Android services from auto-running at boot. (You may test this by powering off your Thunderbolt, then upon powering it back on, hold down the Volume Down key when you see the Quietly Brilliant splash screen. Keep holding it down until you see 'Safe Mode' in the bottom left of the screen.)

2. The Thunderbolt will power cycle about 10 minutes after the Mobile IM service is stopped with an 80% accuracy.

Further pointing to an issue possible with the Mobile IM service conflicting with another service or protocol is that when I first got the Thunderbolt I was blocked out of the Mobile IM service. When I'd try to sign in to, say, Windows Live on Mobile IM, I would be taken to a My VZW Single Sign On (SSO) page. This is common for some Verizon services, but you rarely see it. When I tried to sign in with my My VZW credentials, the SSO would freeze and force close. Since MR1 I can now log into Mobile IM and the subsequent SSO page.

All this is just likely coincidence and conjecture, but its a theory, and a different angle. Mobile IM conflicting with a core process or protocol possibly?

 

[DevTin23]

Idk if anyone has said this or noticed but it seems to be that it only restarts for me when i have a weak signal.

sent for my fantastic thunderbolt.

 

[dpham00]

Actually, on the contrary... It the testing I have been doing on the Thunderbolt, I notice a few things:

1. The Thunderbolt crashes immediately upon booting up in safe mode. All safe mode does is disable all non-core Android services from auto-running at boot. (You may test this by powering off your Thunderbolt, then upon powering it back on, hold down the Volume Down key when you see the Quietly Brilliant splash screen. Keep holding it down until you see 'Safe Mode' in the bottom left of the screen.))
2. The Thunderbolt will power cycle about 10 minutes after the Mobile IM service is stopped with an 80% accuracy.

Further pointing to an issue possible with the Mobile IM service conflicting with another service or protocol is that when I first got the Thunderbolt I was blocked out of the Mobile IM service. When I'd try to sign in to, say, Windows Live on Mobile IM, I would be taken to a My VZW Single Sign On (SSO) page. This is common for some Verizon services, but you rarely see it. When I tried to sign in with my My VZW credentials, the SSO would freeze and force close. Since MR1 I can now log into Mobile IM and the subsequent SSO page.

All this is just likely coincidence and conjecture, but its a theory, and a different angle. Mobile IM conflicting with a core process or protocol possibly?

Interesting, I don't use mobile IM and haven't had a reboot in a long time, over a week and only had a handful ever. Btw, the mobile IM app really should be a mobile text app since it uses your texts, not ims, fine for those who have a text plan, but those like me who don't have a text plan, this app is useless, i just use the yahoo messenger app, which isn't charged to your text allowance, and even allows international texts free.

 

[jeffjeter]

I watched mine reboot several times while charging.

Sent from my HTC Thunderbolt using Tapatalk.

 

[PJnc284]

Interesting, I don't use mobile IM and haven't had a reboot in a long time, over a week and only had a handful ever. Btw, the mobile IM app really should be a mobile text app since it uses your texts, not ims, fine for those who have a text plan, but those like me who don't have a text plan, this app is useless, i just use the yahoo messenger app, which isn't charged to your text allowance, and even allows international texts free.

I don't use the Mobile IM and even have it completely removed and have still had reboots along with a lot of others. Those reboots have only occurred in 1 area so I'm still sticking with radio/tower issues. Not to mention, blackmanx mentioned network related reboot issues when everyone was complaining about the Thunderbolt being delayed. Sounds like they got it fixed before launch but reintroduced the problem with the OTA.

 

[dms76]

Actually, on the contrary... It the testing I have been doing on the Thunderbolt, I notice a few things:

Further pointing to an issue possible with the Mobile IM service conflicting with another service or protocol is that when I first got the Thunderbolt I was blocked out of the Mobile IM service. When I'd try to sign in to, say, Windows Live on Mobile IM, I would be taken to a My VZW Single Sign On (SSO) page. This is common for some Verizon services, but you rarely see it. When I tried to sign in with my My VZW credentials, the SSO would freeze and force close. Since MR1 I can now log into Mobile IM and the subsequent SSO page.

I doubt it's mobile IM as I removed it as bloatware when I rooted the phone. Still possible that it is a problem since effects of removing bloatware is not always known.