30 June Update Doubtful

[wgragg]

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.

I agree with you. It does have some issues that are annoying, though I haven't been hit as hard as some. I can certainly understand the temptation to go back to an Iphone and as I have said, I have been tempted at times. I'm not one to discourage anyone from pursuing something they want and if you decided to make that switch, it would certainly be a valid choice. Hopefully it would work out for you.

On the other hand, I've learned (and am still learning) that if the grass looks greener on the other side of the fence, make sure someone didn't install astro-turf! IOS has its own share of problems and frustrations. I guess it all boils down to what someone wants and expects out of tech.

I do think that VZW and HTC will work out the phone issues. I also wish they would get it done already, but then again, it isn't as simple as changing a few lines of code and pushing it out the door. These things take time to get through the process. Of course it would have been a lot simpler if HTC and VZW decided to just go with a pure Android rather than their own tweaks....

 

[wgragg]

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

Early adopter = unofficial beta tester!

 

[inthruoutdoor]

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.

I disagree completely. They absolutely need more pressure, as it has been over a month since they pushed the last update that caused this issue. We the customers are giving them our money so shouldn't we expect a fully functional product in return? And if they cannot provide a functional product in a reasonable amount of time (6 weeks is way beyond reasonable to me when the phone randomly reboots 5-10 times per day) shouldn't they be obligated to compensate their paying customers? I think so. And to me, it does not matter how many warranty replacements they are issuing every day. Honestly, they shouldn't even be offering that because it does not fix the problem and it is just a hassle. I absolutely agree that both HTC and Verizon are responsible, but I think skyjjc is correct that the contractual agreement is with VZW so they are the ones who need to provide the solution. I am not going to stick up for corporations like this because allowing them to get away with issues like this only perpetuates the problem. They will realize that their customers don't care enough to take action, so they don't feel the impact of delivering a faulty product, therefore there is no motivation for them to focus on and fix not only the individual product, but their PROCESS in order to prevent future occurrences of similar situations.

I hardly think VZW needs your defense in this situation. They are responsible for this problem, they are taking way too long to solve it, while I am paying for and dealing with an unreliable product until they do, so I have and will continue to take action to put whatever amount of pressure on them that I can.

 

[wgragg]

All the pressure in the world cannot make the technical issues go away any faster. It still takes a certain amount of time to change code, test, recode, retest, beta test, get the myriad of approvals needed, send it to the carrier for their approval, set up a deliverable, test the delivery mechanism, field test the deliverable, schedule the update on the update servers, set up the management protocols, work with marketing to get the word out, etc. It is a very complicate process fraught with exposure to any number of errors along the way. I didn't even mention the amount of time it would take to isolate the modules causing the failure in the first place.

Granted, VZW and HTC should probably be more forthcoming with time frames, but on the other hand, any date they say, no matter how well they qualify it ("may be ready", "projected date", etc.) is subject to slippage and then all these people wanting the fix will claim they broke a promise and get even more upset.

I find it funny how people complain that a problem isn't fixed in a week (intentional hyperbole there) without having an inkling of the involved process of getting a phone update developed and pushed out. Where I do blame HTC/VZW though is that they should have more thoroughly tested the problematic update before pushing it out. Then again, they were under a lot of pressure from these same complainers (some of them anyway) to fix the original issues with the phone.

 

[inthruoutdoor]

All the pressure in the world cannot make the technical issues go away any faster. It still takes a certain amount of time to change code, test, recode, retest, beta test, get the myriad of approvals needed, send it to the carrier for their approval, set up a deliverable, test the delivery mechanism, field test the deliverable, schedule the update on the update servers, set up the management protocols, work with marketing to get the word out, etc. It is a very complicate process fraught with exposure to any number of errors along the way. I didn't even mention the amount of time it would take to isolate the modules causing the failure in the first place.

Granted, VZW and HTC should probably be more forthcoming with time frames, but on the other hand, any date they say, no matter how well they qualify it ("may be ready", "projected date", etc.) is subject to slippage and then all these people wanting the fix will claim they broke a promise and get even more upset.

I find it funny how people complain that a problem isn't fixed in a week (intentional hyperbole there) without having an inkling of the involved process of getting a phone update developed and pushed out. Where I do blame HTC/VZW though is that they should have more thoroughly tested the problematic update before pushing it out. Then again, they were under a lot of pressure from these same complainers (some of them anyway) to fix the original issues with the phone.

I find it funny how you assume you are the only person who knows anything about what you speak of! Who are you to say who does or does not have an "inkling" of the process involved in testing and developing software? As a matter of fact, I work for the government in software test and I do know that it is an intricate process and difficult to isolate problems. However, that does not change the fact that Verizon needs to resolve this issue and that since they delivered a faulty product, they need to inform their customers and compensate them accordingly. And you are right that more pressure will not lead to a solution to this problem being pushed any faster. However, enough pressure could cause them to examine their software development and test PROCESSES (as I mentioned in my previous post) in order to understand how to more efficiently deliver functional products to their customers in the future.

 

[Charmed Juan]

Does anyjuan have any knowledge as to why Verizon and HTC don't tell customers where they are in the development of Gingerbread and Skype?
Have they finished the coding? Is it in testing? How long do they expect it to be in testing? Are they waiting for the Flyer to come back from the printers?
Do they have a part-time intern in the basement doing the coding?

I want more than "It's coming soon"

 

[dannyb884]

An idea on why the update didn't come out yesterday:

My cousin has the EVO, which just received the Gingerbread update a couple of weeks ago. Since he has updated he has experienced the oh so wonderful reboot issue and also has been getting random text message notifications even when not receiving an actual text. The 2nd issue is something that happens all day every day.

With the first update for the Thunderbolt being so buggy, I'm guessing HTC is making sure that this update is absolutely perfect before they release it to us "patiently" waiting TB owners. No matter how badly I want this update, i would rather wait and have it work properly than get it within the next couple of days and have it cause more issues.

Just my 2 cents, obviously this is not proven info.

 

[Mike_is_Mike]

Does anyjuan have any knowledge as to why Verizon and HTC don't tell customers where they are in the development of Gingerbread and Skype?
Have they finished the coding? Is it in testing? How long do they expect it to be in testing? Are they waiting for the Flyer to come back from the printers?
Do they have a part-time intern in the basement doing the coding?

I want more than "It's coming soon"

It's coming real soon.

 

[wgragg]

I find it funny how you assume you are the only person who knows anything about what you speak of! Who are you to say who does or does not have an "inkling" of the process involved in testing and developing software? As a matter of fact, I work for the government in software test and I do know that it is an intricate process and difficult to isolate problems. However, that does not change the fact that Verizon needs to resolve this issue and that since they delivered a faulty product, they need to inform their customers and compensate them accordingly. And you are right that more pressure will not lead to a solution to this problem being pushed any faster. However, enough pressure could cause them to examine their software development and test PROCESSES (as I mentioned in my previous post) in order to understand how to more efficiently deliver functional products to their customers in the future.

The comment about people not knowing the process was aimed at you specifically, but more generally as I have seen so many of these comments from young, impatient people who really don't realize you can't fix these problems in such a short time. As an example of the mentality, I am a system administrator for a library system here in Texas, having been in IT since 1974 (yes, the old punch card days). We just received 34 brand new computers to replace the aging public computers in our computer lab and I am starting the process of getting them ready to deploy.

The problem is that the librarians I work with are constantly hounding me every day about why they aren't out on the floor yet (we've had them one week). No matter how hard I try to explain to them that I can't just unbox them and turn them on, but must set security, install a bunch of software, test the configuration, then sysprep one, image the hard drive, and replicate that image. Then I have to set them up physically, rename and readdress them, etc. The constant pressure from them is very frustrating, but I want to do it right so that I don't have to go in and redo everything a week after I deploy.

While the problems with the TB are also frustrating, I want them to get this update right and if it takes longer, then it takes longer. I do agree that some sort of compensation for the lack of function would be nice, I would seriously doubt that it will happen on a large scale. I also agree that they should learn a lesson from this, but frankly, this is not the first time around the block for them and I doubt they have learned a similar lesson from previous issues on other phones.

Honestly, I think they should have pulled the update as soon as the problems started to appear and possibly even reversed it, but they didn't, so we are stuck with things the way they are now.

 

[YourMobileGuru]

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.

AMEN Brother!

Add to that I don't want to be subjected to the labotomization/Cult of Mac initiation that Apple seems to love to do so much. It's not magical, it's not revolutionary, it's just polished. And frankly after a while it gets BORING!

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?

I'm pretty sure the next iPhone screen is gonna be bigger, of not this one then the next.

I hate iTunes as well (or at least I used to) but it has really grown on me, and I now view it as more of a necessary evil. The biggest thing I hate about it is how everything has to sync to the computer instead of the cloud and they are fixing that with iOS5.

 

[Mike_is_Mike]

I'm beginning to doubt the 6/30/11 release date.

 

[Mortiel]

I'm beginning to doubt the 6/30/11 release date.

I lol'd

 

[Chiefmcfuz]

I lol'd

I did too. Almost choked on my water LMAO!

 

[Mortiel]

I did too. Almost choked on my water LMAO!

I can most DEFINITELY assure you that the update WILL be released on 06/30/11.

 

[dvdillonla]

I can most DEFINITELY assure you that the update WILL be released on 06/30/11.

Think the last "1" should be a "2"?

 

[robrecht]

jcase confirmed that MR2 is now on its 5th revision 1.70.xx and is looking at a potential 7/6 release. That sounds pretty credible but of course not set in stone.

EDIT: This is MR2; GB will come later with MR3.

Thanks, Robrecht

 

[YourMobileGuru]

jcase confirmed that MR2 is now on its 5th revision 1.70.xx and is looking at a potential 7/6 release. That sounds pretty credible but of course not set in stone.

EDIT: This is MR2; GB will come later with MR3.

Thanks, Robrecht

Leak or it's all talk.....j/k.... LOL

 

[FrankXS]

jcase confirmed that MR2 is now on its 5th revision 1.70.xx and is looking at a potential 7/6 release. That sounds pretty credible but of course not set in stone.

EDIT: This is MR2; GB will come later with MR3.

Thanks, Robrecht

Okay. I change my prediction to 7/6/11. Shoot, now I'll have to get my PayPal accnt set up to receive my $20 payments before this date

Sent from my HTC ThunderBolt 4G/LTE using Tapatalk

 

[FireMedic559]

Well thats no fair! Is the prediction just for any update or for GB/reboot fix. We all know there will be an update on that date...you know the one to remove free tethering!!!

 

[GoldLeader]

I can most DEFINITELY assure you that the update WILL be released on 06/30/11.

You must have talked to a Verizon rep on the phone too, right?
That INSTANTLY gives the post complete credibility!