Those with the official ota need some feedback

For those with random REBOOT issues on Thunderbolt after the OTA latest update: Remove/delete the app that switches between 4G & 3G, & manually reboot. This should address the issue.

The app is the same as the key combo to get to the settings page, right? At any rate, I have switched mine back from the CDMA auto (PRL) to the stock setting (CDMA LTE). I will see if that makes any difference.

I have had terrible performance since upgrade. As in a few reboots and from 100% battery at 7am to 20% at 11am. I had one reboot today that dropped me 12% battery life!!
Another site said that some of this is dependent on your local towers and I hear Indianapolis (where I am) is doing a lot with their towers as 4G is about to be unleashed. I have read of others with lots of reboots here.

I will report back.
 
Can anyone point me to how to roll back the software to previous. At this point I would much rather roll back and root than keep this software.

AFAIK there is no way to roll it back.
 
Can anyone point me to how to roll back the software to previous. At this point I would much rather roll back and root than keep this software.

AFAIK there is no way to roll it back.


If you are stock no, if you are rooted and s-off you can but you will be bugged to update so at that point the best bet is to install a stable rom. But as I said in the other reboot thread, you should not have to root for phone functionality. They knew that there would be random reboots and they pushed it anyway. Email vzw:

those having random reboots email vzw:

https://www.verizonwireless.com/b2c/contact/email.jsp


Email actually works better than calling because they HAVE to respond to it via email or email and call.
Explain how testers reported the software would cause random reboots because they were experiencing the same exact issue. Testers expected vzw/htc to fix that issue. Testers explain that the ots is the exact same build they tested and expected people to complain of random reboots.
 
Ok . .. so yesterday I switched the 3g/lte setting back to stock, then rebooted the phone with a battery pull.
Initial results of last night and this morning were better battery life - back to what it used to be, maybe better.
Then maybe 1 hour ago it rebooted. And used 12% of the battery doing so. ugh.
 
Email sent to Verizon. We'll see what they say...
They will say the same...

Actually if they get enough emails on that issue and people did a factory reset it should get handled. It's no.coincidence that people complained of random reboots with the leak ota and now customers are having issues. Right now it's not looking good for vzw first lte device to struggle with lte because of the network being new and to have random reboot issues because of an update they put out.

sent from droidforums app
 
Email sent to Verizon. We'll see what they say...
They will say the same...

Actually if they get enough emails on that issue and people did a factory reset it should get handled. It's no.coincidence that people complained of random reboots with the leak ota and now customers are having issues. Right now it's not looking good for vzw first lte device to struggle with lte because of the network being new and to have random reboot issues because of an update they put out.

sent from droidforums app

Maybe, but they are not going to roll him back to the version before the update.
 
For those with random REBOOT issues on Thunderbolt after the OTA latest update: Remove/delete the app that switches between 4G & 3G, & manually reboot. This should address the issue.

I have never had that installed and thus won't solve my problems with reboot since the update. Can anyone point me to how to roll back the software to previous. At this point I would much rather roll back and root than keep this software.

Sent from my Thunderbolt
this isn't walmart, there are no "rollbacks"
 
They will say the same...

Actually if they get enough emails on that issue and people did a factory reset it should get handled. It's no.coincidence that people complained of random reboots with the leak ota and now customers are having issues. Right now it's not looking good for vzw first lte device to struggle with lte because of the network being new and to have random reboot issues because of an update they put out.

sent from droidforums app

Maybe, but they are not going to roll him back to the version before the update.


You right they are not going to roll back, but hopefully they push a fix for the issue. I believe its a kernel issue because das bamf is built off the leak and I am not having any reboots.
 
Actually if they get enough emails on that issue and people did a factory reset it should get handled. It's no.coincidence that people complained of random reboots with the leak ota and now customers are having issues. Right now it's not looking good for vzw first lte device to struggle with lte because of the network being new and to have random reboot issues because of an update they put out.

sent from droidforums app

Maybe, but they are not going to roll him back to the version before the update.


You right they are not going to roll back, but hopefully they push a fix for the issue. I believe its a kernel issue because das bamf is built off the leak and I am not having any reboots.
Its interesting that some are having the issue, but not all. I had 2 reboots over the weekend, but I was at VaTech's Grad School graduation in a very hot, rather humid, non air conditioned basketball stadium where they crammed in an additional 25% more people when it was made because they use skinnier seats. Other than that, the OTA has been working like a champ. My battery issues are all but eliminated (though, interestingly, it seems to be eating up more battery in Wifi than before... but considering with mid to heavy use it still only has 50% at the end of the day, I'm not complaining).
 
I've not installed my update for this very reason... but I did have another goof and wanted to start fresh on my phone. I did a hard reset and now everything is different than my previous stock unrooted Thunderbolt. I got mine the day they came out...

When I go to updates, it says there is one around 34MB. I declined it. Should I continue to decline it? Not too happy with this... the phone operates great at home and when I'm out and about but in my office I barely receive any kind of signal and it constantly switches between 3G and 1x. I bought the larger battery, it will last me 36 hours or so with usage at home and with WIFI turned on. I go to work and it lasts about 24 hours or so. I think I will keep declining the update until I hear more. I don't want to regret buying my first droid/smartphone! It looks cool, operates great outside my office but man o man I long for the days of not having to charge my phone but once or twice a week. ;)
 
So now it has been 3 days since I did the factory reset and no reboots, whereas after the update my phone was rebooting itself once every few hours or so. I have not noticed any noticeable improvement while in 4G (at work where the building itself eats cell signals for breakfast and my phone regularly switches between 4G, 3G, and 1x). However, it has been a HUGE improvement when I am home and only have 3G. Worked from home yesterday and unplugged phone at 7 am. Made a few conference calls, and used it for email like I normally do. By midnight when I went to bed, the battery was still at around 30% where before the update the battery would have been at 30% around 6-7 pm.
 
I unrooted my thunderbolt and flashed back to stock. The took the update the day it was released, and have had no reboots. Also my performance of my signal and gps a lot better and 3g and 4g handout is much improved. I don't know if I am not having problems with the update because of the clean install of the stock Rom.

Sent from my ADR6400L using DroidForums
 
did they stop pushing the update?

I was rooted and went with the rooted update when it came out. Like a lot of others, i started having a lot of reboots and could not get my gps to work.

I just unrooted earlier today, and went back to the version before the update. It was slow to lock onto my gps position, but it did after a couple of minutes.

The odd thing is that I have not been prompted to update yet. I have rebooted a couple of times and checked for an update, but it isn't there. Is it possible that they stopped pushing the update?
 
Back
Top