Seems like PRl 15011 is a cause of this madness after the OTA update. What is your PRL?
No that's not it. I have 15011 and I'm one that has no issues
Sent from my Thunderbolt
Hm. If its not the the PRL then what could be the problem? What exactly is up with this new radio? Do we have any developers in the operating room yet?
No that's not it. I have 15011 and I'm one that has no issues
Sent from my Thunderbolt
The reason that doesn't make sense is because of the other phones that aren't even smartphones that are having issues as well. If it was just the Thunderbolt then maybe, but as FrankXS' link showed, the Charge is having connection issues as well. Then you have the fact that mine doesn't reboot at all unless I'm in a basement. So I know I don't have corrupt firmware because mine hasn't rebooted minus my 2 basement reboots.
People really need to pay attention to the conversations as I am even getting annoyed with myself because I feel like I'm saying the same stuff over and over and over and over and over and over again. I think the handling of the weak/dropped data signal issue is close to the mark. It's the only thing that makes sense.
Sent from my Thunderbolt
Chrisy?
And I'm sure you do it well.Oh, I have been paying close attention. I also have extremely in depth knowledge into how the towers communicate with devices. Its my job.
And what's the most common denominator? The Verizon towers that combine old and new technology and protocols.Honestly, considering the amount of power cycling issues I hear about on a wide variety of devices, I suspect it is likely a protocol corruption that has been severely overlooked for a long time now, or a new technology update that does not mesh well with older technology still in use.
I don't think it's necessarily a signal strength issue but a handshake issue. Obviously, signal strenghth can be a big part of this, as a low signal will initiate more attempted handshakes. But handshakes take place on a regular basis, regardless of strength of signal, right? (That's a genuine question.) And perhaps your network extenders at work create additional handshake issues.[/quote]Think of it as if your computer's TCP/IP protocol, or a wireless card driver even, caused your computer to crash, not the strength of the connection to a router or modem.
Don't give up looking for the cause. There are no confirmed sightings of gremlins.This seems to have no rhyme or reason based upon time of day or day of week, either.
This could explain my relatively infrequent problems as I am constantly pulling my batteries to replace them with spares from my wall chargers. But my n=1 doesn't say much. Are there others who cycle their spare batteries frequently but still have more severe reboot problems.Another baffling issue is that I notice performing a hard reset (pulling the battery and discharging the capacitors) minimizes reboots whereas a factory data reset seems to do nothing also points to an issue with firmware, not software.
Verizon's contract with Apple does not allow for, even require, sharing of code and engineering design parameters? Surely some people at Verizon have access to this. If so, maybe it's just an issue of corporate priorities.The iPhone is about the only device that appears immune, which irks me since Apple is so secretive about everything.
I had not heard that. Does this occur frequently?Yet another issue is that people have reboots even connected to WiFi.
While I admire the intellectual rigor of William of Occam, I don't think there is a single solitary cause of every phone problem ever experienced by anyone anywhere. Again, n=1, may not be related or generalizable.... but I think I read that someone here had a reboot while on Airplane Mode+WiFi, which means 2G was not active.
One time, after I experienced two reboots, one right after the other, I placed a call and it was a very poor quality call. Again, n=1, but interesting.However, I still do think something in the 2G firmware protocol is not meshing with newer EV-DO (eHRPD) and LTE protocols.
I'm happy to test any theories on a test phone, but if HTC does indeed send me one, I will follow their instructions, of course. But, again, I do not consider myself a very good test subject because this is not a significant problem for me.If anyone wishes to test this, and can go a period without calls or SMS, change the radio settings to EV-DO Only (which *should* disable 1xRTT connections) and see if reboots still occur.
The only way to confirm or deny the network connection protocol and/or firmware being the suspect is to run on pure Airplane Mode for a full day. This would only help if the test device experienced a consistent multiple reboots per day. Robrecht would make a perfect candidate if he got that test phone from HTC, and if it experiences multiple reboots per day, since his communication would not be affected by having that test device on Airplane Mode for a long period of time.
Both on the device end. Both on the device end. But some people at Verizon are also looking at the towers' role in this problem. Maybe they will have more luck.And just to let everyone know, I and several other associates of mine have been keeping a careful eye on this issue, and testing it intensely. We have been theorizing everything from the eHRPD firmware protocol to possible 2G radio feedback loops (both on device end), but have not had any definitive results in testing.
My pleasure. Two of Chrisy's links were about Moto reboots. Mortiel says the iPhone seems to be immune but does not know why.Thank you for the expansion sir. I would suspect motorolas and iphones to be rebooting as well?
Absolutely. That's why I'm thinking of it as some kind of last resort or stopgap measure. It certainly would not be designed to do this frequently and maybe it's not by design at all.I think it's possible, but I suspect the software has been designed to deal with connection errors without rebooting itself.
Not waves. Not like us. Personally, I think the ThunderBolt may be particularly prone to this issue because of the need for additional handshakes and transitions with newer tech & protocols insofar as we have 4G and eHRPD 3G on our phones.I don't know either, and I wonder if it is just a 4g snafu, and if charge owners are experiencing this in waves?
It is so infrequent for me that I will tolerate it as long as there is hope that HTC and Verizon can resolve the issue.I won't tolerate rebooting phones now that I have had years without.
Thanks for the detailed information. Good to hear from someone in the loop. Keep us posted of your findings would you?Oh, I have been paying close attention. I also have extremely in depth knowledge into how the towers communicate with devices. Its my job.
When I say corrupted radio firmware, I did not say it was *just* the Thunderbolt's radio firmware. I also did not mean the firmware was corrupted upon installation. Honestly, considering the amount of power cycling issues I hear about on a wide variety of devices, I suspect it is likely a protocol corruption that has been severely overlooked for a long time now, or a new technology update that does not mesh well with older technology still in use. It is highly unlikely that a Preferred Roaming List would affect device functionality. Firstly almost all LTE phone users should be on identical PRLs. Secondly all a PRL does is give the phone a list of towers, what their connection types are, and whether it is a Verizon tower or not.
Think of it as if your computer's TCP/IP protocol, or a wireless card driver even, caused your computer to crash, not the strength of the connection to a router or modem. The parameters for reboots, however, seem too random to calculate. I have a constant full bars of 4G at home, and have gotten reboots. I have full bars of 3G inside my work building (due to multiple network extenders since the building is a radio nightmare), and have gotten reboots at work. This seems to have no rhyme or reason based upon time of day or day of week, either.
Another baffling issue is that I notice performing a hard reset (pulling the battery and discharging the capacitors) minimizes reboots whereas a factory data reset seems to do nothing also points to an issue with firmware, not software. This I have tested on about 10 different Verizon devices, between basic and smart phones over a period of the last month. The iPhone is about the only device that appears immune, which irks me since Apple is so secretive about everything.
Yet another issue is that people have reboots even connected to WiFi. This would point to likely one source: 1xRTT (2G). Even when connected to WiFi, the 2G connection remains active, but I think I read that someone here had a reboot while on Airplane Mode+WiFi, which means 2G was not active. However, I still do think something in the 2G firmware protocol is not meshing with newer EV-DO (eHRPD) and LTE protocols. If anyone wishes to test this, and can go a period without calls or SMS, change the radio settings to EV-DO Only (which *should* disable 1xRTT connections) and see if reboots still occur.
The only way to confirm or deny the network connection protocol and/or firmware being the suspect is to run on pure Airplane Mode for a full day. This would only help if the test device experienced a consistent multiple reboots per day. Robrecht would make a perfect candidate if he got that test phone from HTC, and if it experiences multiple reboots per day, since his communication would not be affected by having that test device on Airplane Mode for a long period of time.
And just to let everyone know, I and several other associates of mine have been keeping a careful eye on this issue, and testing it intensely. We have been theorizing everything from the eHRPD firmware protocol to possible 2G radio feedback loops (both on device end), but have not had any definitive results in testing. Welcome to the Rubic's Cube of telecommunications.
Thanks Chrisy, but I read this thread through including the links you posted first as well. I have never owned a BB that doesn't reboot. While all my motors have reboots, it is once every 1/2 year or so. I iphones do not have random reboots. I bet firmware.PRL: 15008.
Also, it isn't just 4G phones experiencing reboots. I'm going to gather my links again.
Recent Random Reboots on not Thunderbolt Devices
http://forum.androidcentral.com/htc-droid-incredible-2/81588-random-reboots.html
http://forum.androidcentral.com/motorola-droid-x2/86310-random-rebooting.html
http://forum.androidcentral.com/motorola-droid-2/66365-d2g-keeps-rebooting.html?highlight=rebooting
http://forum.androidcentral.com/motorola-droid-x2/86310-random-rebooting.html
Random Reboots on BlackBerry Tour
Storm 2 Rebooting twice a day
The reason I first thought it was network related is when non smart phone VZW folks at my moms work are having reboots too. I don't think non smart phone owners post on forums though.
Some days I don't have any reboots at all. Those days I'm usually at home. I have had the reboots while using Google Navigation and always in a certain part of town. I have not paid attention to the exact location. I will today.
Interesting. I wonder when Verizon started rolling out their ePHRD-capable 3G network equipment in preparation for 4G. Or, when they upgrade one area with ePHRD in preparation for 4G, do they reuse the old equipment in other areas that don't have any 3G yet? Or, what percentage of the 3G network is ePHRD 3G?But it may be worth noting that 3G in that area, as well as native coverage, is relatively new. VZW acquired that area from Alltel, and I can remember it being strictly CDMA and not even 1x as recently as Christmas 2008 when I took a VZW work phone over there. Back then, Cellular South was still preferred there, so you'd only switch over to the former Alltel network if you had nothing else to connect to. Now, that network has been upgraded to 3G, and it's the preferred network in the area. What I'm wondering is if, due to its later upgrade to 3G than many areas, if it has different equipment (newer models) at the base stations. Could that account for my lack of reboots while there? In contrast, Tuscaloosa got 3G in the fall of 2006, and I get reboots here.
For you and your wife and many people. But so many other people also have the new firmware and either don't have a problem at all or have it very infrequently. So there must be another, additional contributor to the problem, be it phone or network or something else (personally, I don't think it's software, 'though the problem might be exaccerbated by GPS interference).All I know is the update caused it. Been my wife and I we have had 7 Thunderbolts. We know gladly have 2 on the old software that work great.
I can go over the extensive reviews/comparisons that I did if you would like, but what it comes down to is the old firmware doesn't reboot and the new firmware does.
Does anyone else remember this? I wonder if this was referring to a new, intended behavior or was it more likely just referring to the reboot performed during the update procedure?thorthunderblt said:Friggin OTA. I do remember that when it was updating that one of the pop ups before it actually downloads was that the update will cause the phone to reboot without warning.
Just read this in another thread:
Does anyone else remember this? I wonder if this was referring to a new, intended behavior or was it more likely just referring to the reboot performed during the update procedure?
And I'm sure you do it well.
And what's the most common denominator? The Verizon towers that combine old and new technology and protocols.
I don't think it's necessarily a signal strength issue but a handshake issue. Obviously, signal strenghth can be a big part of this, as a low signal will initiate more attempted handshakes. But handshakes take place on a regular basis, regardless of strength of signal, right? (That's a genuine question.) And perhaps your network extenders at work create additional handshake issues.
Don't give up looking for the cause. There are no confirmed sightings of gremlins.
This could explain my relatively infrequent problems as I am constantly pulling my batteries to replace them with spares from my wall chargers. But my n=1 doesn't say much. Are there others who cycle their spare batteries frequently but still have more severe reboot problems.
Verizon's contract with Apple does not allow for, even require, sharing of code and engineering design parameters? Surely some people at Verizon have access to this. If so, maybe it's just an issue of corporate priorities.
I had not heard that. Does this occur frequently?
While I admire the intellectual rigor of William of Occam, I don't think there is a single solitary cause of every phone problem ever experienced by anyone anywhere. Again, n=1, may not be related or generalizable.
One time, after I experienced two reboots, one right after the other, I placed a call and it was a very poor quality call. Again, n=1, but interesting.
I'm happy to test any theories on a test phone, but if HTC does indeed send me one, I will follow their instructions, of course. But, again, I do not consider myself a very good test subject because this is not a significant problem for me.
Both on the device end. Both on the device end. But some people at Verizon are also looking at the towers' role in this problem. Maybe they will have more luck.