30 June Update Doubtful

[jjcampnr]

VZW has a post on their twitter saying HTC is still working on the release, so it's probably doubtful it'll be out today (that is assuming the people answering tweets have any clue).

No Update Scheduled

HTC Still Developing

 

[z71kris]

ugg the update possibilities are why I chose the bolt...oh well, I still a great phone, and my battery has been lasting all day since I installed juice defender....

 

[Mike_is_Mike]

ugg the update possibilities are why I chose the bolt...oh well, I still a great phone, and my battery has been lasting all day since I installed juice defender....

That's the main problem - the TB is FULL of POSSIBILITIES........but EMPTY on REALITIES.

 

[VCL]

Just to give you all an update, the rumored Gingerbread update likely will not hit June 30th. I do not know when it is really planned, if at all, however I checked the approved software list (when Verizon approves a software update for any device, it goes on that list immediately), there was no new software approved for the Thunderbolt.

Usually there is an obvious lag time between a software approval and the actual push data, so even if they approved it tomorrow, it would likely be as little as a few days up to a week or more before it hits your phone. It is usually announced publicly shortly after approval.

Example: The MR1 for the Thunderbolt was approved 04/29/11. Pushed to phones 05/20/11.

So sad to say I doubt the rumor of a June 30th or the official statement of a "second half of June" fix will likely not happen, but do not fret! It will be out soon!

Don't fret, that is crap. This phone hasn't worked right out of the box but Verizon can push updates to other devices and leave their supposed LTE phone hung out to dry. Unacceptable, this is just ridiculous for the countries leading carrier to act like this.It sucks when a company gets so big they have you by the short hairs. It would be great if everyone got together who had a Thunderbolt and refused to pay their monthly bill until the phone was updated. See how fast the update hits the airwaves then.

 

[Mortiel]

June 30 is here, and no update.

And this comes as no surprise to me, as my original post stated. Lol

 

[drstrange462]

I stopped holding my breath for this update long ago.

 

[inthruoutdoor]

VZW has a post on their twitter saying HTC is still working on the release, so it's probably doubtful it'll be out today (that is assuming the people answering tweets have any clue).

No Update Scheduled

HTC Still Developing

Verizon says it is HTC, while HTC says it is Verizon. I wonder where the update really is....Check out this email I got from HTC today regarding the anticipated update (I sent the question to them yesterday, which is why they say "tomorrow" obviously referring to today:

"Dear [Customer],

I understand that your HTC Thunderbolt has been restarting all by itself since you performed the latest update.

This issue is known to us at HTC and Verizon. Verizon has pulled the update to fix this restarting issue within the update.

We are not releasing any update tomorrow. Verizon will release the correct update once they have resolved this issue.

I do apologize, for any inconvenience this has caused for you.

To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number XXXXXXXXXXXXX.

Sincerely,

Terri
HTC"

 

[JediJesus95]

So if HTC is still working on a fix then it will be another 3-4 weeks before Verizon gets done testing it.

 

[premise]

Here is the email I received yesterday from htc, This was after speaking to a verizon tech telling me gb is being pushed to my phone taday.



Dear [Customer]

We apologize for the issues you have experienced since the last update to your HTC Thunderbolt. HTC has been diligently working with Verizon since the rebooting issue was first recognized to try to resolve the concern. An update is being working on but we do not have an estimated time as to when this update will be released.

Also, HTC is only able to repair the device under our coverage because we do not perform direct device sales. We apologize for the inconvenience you have experienced and will document your concerns; however, we have no further information regarding the issue at this time beyond what has already been provided.

Feel free to contact us again should you have any further questions. If you feel more comfortable discussing issues by phone, you can contact Technical Support at 1-866-449-8358, 6 am to 1 am EST, 7 days a week.

To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number xxxxxxxxxxxxxxxxx.

Sincerely,

Dayton

HTC

 

[YourMobileGuru]

Here is the email I received yesterday from htc, This was after speaking to a verizon tech telling me gb is being pushed to my phone taday.



Dear [Customer]

We apologize for the issues you have experienced since the last update to your HTC Thunderbolt. HTC has been diligently working with Verizon since the rebooting issue was first recognized to try to resolve the concern. An update is being working on but we do not have an estimated time as to when this update will be released.

Also, HTC is only able to repair the device under our coverage because we do not perform direct device sales. We apologize for the inconvenience you have experienced and will document your concerns; however, we have no further information regarding the issue at this time beyond what has already been provided.

Feel free to contact us again should you have any further questions. If you feel more comfortable discussing issues by phone, you can contact Technical Support at 1-866-449-8358, 6 am to 1 am EST, 7 days a week.

To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number xxxxxxxxxxxxxxxxx.

Sincerely,

Dayton

HTC

What part of this is a surprise? We've known it for weeks. HTC was hard at work prepping Gingerbread for us when the issues with MR1 became known to them. They stopped work in that and wrote an updated firmware (known to us as MR2)) and gave it to Verizon. It was expected to push on or around the 15th IF it passed Verizon's Technical Acceptance testing. For some reason it didn't. The exact reason has never been revealed to us but us likely one of the following or a combination of both

1. It simply didn't COMPLETELY fix the reboot issue for enough of their testers to consider it worth pushing (probable)

OR

2. There is one or more other major bugs in the software that we are not aware of.

Either way HTC is back an square one and probably pissed about it but that's just how software development works.

Mortiel said that no other APPROVED software builds are listed in the system but that does not necessarily mean that TA is not testing something else as we speak but I personally doubt it, If it were then we probably would have had it leaked by now (most software leaks come out of the carriers not the OEM's).

 

[inthruoutdoor]

This is why I resorted today to calling Verizon and escalating to some level of tech support management, which gave me a free month of service ($60 credit on my account). I think this will be a weekly phone call for me until the issue is fixed because it is ridiculous to have paid for the phone and to be paying for the service when the device is too unreliable to even remain powered on.

 

[YourMobileGuru]

This is why I resorted today to calling Verizon and escalating to some level of tech support management, which gave me a free month of service ($60 credit on my account). I think this will be a weekly phone call for me until the issue is fixed because it is ridiculous to have paid for the phone and to be paying for the service when the device is too unreliable to even remain powered on.

That's prerogative if course, but I don't think they really need any more pushing they know there are issues with the software and want it fixed ASAP (as I said earlier i the thread it is costing them a fortune), but it takes a long as it takes and we know that the disaster that was MR1 *DID* pass technical acceptance and they are no doubt heavily motivated to make sure that does not happen again.

It's easy to blame Verizon and just as easy to blame HTC but they are BOTH to blame for this mess.

 

[skyjjc]

That's prerogative if course, but I don't think they really need any more pushing they know there are issues with the software and want it fixed ASAP (as I said earlier i the thread it is costing them a fortune), but it takes a long as it takes and we know that the disaster that was MR1 *DID* pass technical acceptance and they are no doubt heavily motivated to make sure that does not happen again.

It's easy to blame Verizon and just as easy to blame HTC but they are BOTH to blame for this mess.

Understand you point and you could be right. However, most users have no contractual arrangement with HTC while they do with Verizon. Even if you have a warrenty issue, you take the phone to Verizon, not HTC. If the problem is caused by both Verizon and HTC, the more pressure put on Verizon, the more pressure they will likely put on HTC. Of course any complaints should be polite, reasonable and accurate if you expect the best results.

 

[YourMobileGuru]

Understand you point and you could be right. However, most users have no contractual arrangement with HTC while they do with Verizon. Even if you have a warrenty issue, you take the phone to Verizon, not HTC. If the problem is caused by both Verizon and HTC, the more pressure put on Verizon, the more pressure they will likely put on HTC. Of course any complaints should be polite, reasonable and accurate if you expect the best results.

Of course, I just meant that by now they are well aware of the issue, putting plenty of pressure on HTC and the reps are no doubt as tired of hearing about the issue as we are of talking about it. I taljed to soneone I know at one of our local stores and she told me they wre doing warranty replacements ont hese about two a day, assuming this is average: 2 a day x however many corporate stores x 7 days a week for say 3 weeks after the update came out.... that's a LOT of phones...

 

[Mike_is_Mike]

Would be nice if Verizon would let us know what's going on.

 

[wgragg]

Ok, I know this isn't the case, but if you will allow me to cross over into the realm of fantasy for a moment....

Wouldn't it be a hoot if after all the blame of both companies, it turned out that one of VZW's many pieces of bloatware was causing the problems of rebooting?

One of the most staggering things I have seen since I came out of the IOS world is how market pressure causes all these carriers to constantly come out with new phones and trying to outdo each other. While having the latest and greatest is nice, the downside is that you dilute your market so much and have so many irons in the fire that you cannot do one thing well. The manufacturers, by necessity and pressure from the carriers have to develop so many new products that they cannot invest the proper resources to make an excellent phone. After a new phone is released, a majority of their resources go into the next great phone for another carrier, leaving few to fix bugs and update existing lines.

As much as I despise Steve Jobs and did not like the closed nature of the Iphone/Ipad, he at least (with a few exceptions), came out with very good hardware and a fairly stable software platform. Not that I would ever go back mind you...

 

[EricWiz]

Ok, I know this isn't the case, but if you will allow me to cross over into the realm of fantasy for a moment....

Wouldn't it be a hoot if after all the blame of both companies, it turned out that one of VZW's many pieces of bloatware was causing the problems of rebooting?

One of the most staggering things I have seen since I came out of the IOS world is how market pressure causes all these carriers to constantly come out with new phones and trying to outdo each other. While having the latest and greatest is nice, the downside is that you dilute your market so much and have so many irons in the fire that you cannot do one thing well. The manufacturers, by necessity and pressure from the carriers have to develop so many new products that they cannot invest the proper resources to make an excellent phone. After a new phone is released, a majority of their resources go into the next great phone for another carrier, leaving few to fix bugs and update existing lines.

As much as I despise Steve Jobs and did not like the closed nature of the Iphone/Ipad, he at least (with a few exceptions), came out with very good hardware and a fairly stable software platform. Not that I would ever go back mind you...

Other than the fact that Apple is the evil empire and Jobs is Emperor Palpataine, why wouldn't you go back? I ask because I have been considering the reverse, that maybe it is time to join the dark side.

 

[wgragg]

Other than the fact that Apple is the evil empire and Jobs is Emperor Palpataine, why wouldn't you go back? I ask because I have been considering the reverse, that maybe it is time to join the dark side.

Honestly, I have been tempted at times since I got my TBolt. In fact, my wife has a Fascinate and has gotten to really hate Android. To her, it is non-intuitive and kludgy. It certainly has not been as reliable as her Iphone was. Then again, she is not a techie and has little patience for learning curves, so the fact that Apple packages everything up for you in a nice little box is appealing.

I, on the other hand, have spent almost 40 years in IT and new tech doesn't scare me. I'm getting to an age where I don't like a lot of learning curve either, but I can adjust. There are a number of reasons I don't want to go back into the IOS world. Some people will understand and some I could get flamed over (may not go into those as they are moral/religious issues).

1. The closed nature of IOS. If the innovation does not come from Apple, they don't want it.
2. Jobs has way too much say in what apps are available. Flash is the most visible of them, but there are other decisions he has made and apps he has banned that have told me that if you don't agree with his world view and you submit an app that he disagrees with on a philosophical level, it will get banned. The same is true if your app happens to offend some special group of people, it will be banned. I believe in the open exchange of ideas, even if I happen to disagree with them. To me, the only apps that should be banned are those that contain malicious code or help people break laws.
3. The Iphone screen is just way too small. I need the extra real estate my Tbolt gives due to some eye issues.
4. I HATE Itunes with a passion. It is way too restrictive. Did I say I HATE Itunes?

Those are the primary reasons I don't want to go back. Others may well have additional reasons (rooting, etc), but these are mine.

 

[EricWiz]

I appreciate your candor. I too have spent a great number of years in IT (20 professionally, but I started coding with the original BASIC when I was 8)

Tech doesnt scare me, but I do like a layer of polish. i.e. I run windows and not ubuntu, though I did 'play' with it and some other linux desktop flavors.

I guess that I just have some frustration due to the fact that this phone has so much potential and yet has some serious issues, battery problems and it lacks some key apps.

 

[tcorkum]

I have to tell you I am thoroughly disappointed at the attention VZW is giving its Flagship 4G device. By the time they figure out all the issues we would have been better off waiting and picking up another manufactures device. I would be interested in hearing your thoughts, but it seems that Moto's working relationship with VZW is better than any other manufacture at this point.

I just wish I had not purchased all the accessories so that I could just return the phone and get something that works properly. I previously had the HTC Incred and was very happy. Now my wife and kids get Netflix and I can not?. My kids have Moto x and droid with out any issues for well over a year.

I thought that I was over the early adopter must have.....just another lesson to learn.:'(