So as much as I'm loving my ppc6700, amazed by it's strengths and accepting it's weaknesses, it's obvious that the software is only 99% done at best. The miniSD card problems, the battery reporting issues, the camera's extra bits, WMP's odd behavior, etc. There's all sorts of crap that's tarnishing an otherwise impressive device.
So who's going to fix these issues? Can we even expect a fix? Will Sprint be releasing an update? Will Microsoft? Is this something that HTC will fix? Who's responsibility is it, or are we just going to have to live with it this way? From past experience, how has updates like this been addressed for similar phones? Anyone have any inside info, any insight?
Originally posted by SofaKing So as much as I'm loving my ppc6700, amazed by it's strengths and accepting it's weaknesses, it's obvious that the software is only 99% done at best. The miniSD card problems, the battery reporting issues, the camera's extra bits, WMP's odd behavior, etc. There's all sorts of crap that's tarnishing an otherwise impressive device.
So who's going to fix these issues? Can we even expect a fix? Will Sprint be releasing an update? Will Microsoft? Is this something that HTC will fix? Who's responsibility is it, or are we just going to have to live with it this way? From past experience, how has updates like this been addressed for similar phones? Anyone have any inside info, any insight?
One issue I see is three players here. Harder to get things done when too many cooks in the kitchen. Actually, maybe there are four players - Audiovox and HT are one company, but it may be two separate units internally, if you know what I mean.
Originally posted by winger One issue I see is three players here. Harder to get things done when too many cooks in the kitchen. Actually, maybe there are four players - Audiovox and HT are one company, but it may be two separate units internally, if you know what I mean.
Crossing my fingers...
Well, you've actually got FOUR players in the kitchen:
HTC makes your hardware, UTStarcom/Audiovox brands, sells, and (??) supports the (CDMA) hardware in the US, MS provides and (??) supports the OS (WM5), and the carriers (right now only SPCS but soon VZW) support the network and end-use applications. 3rd party developers minimally support the end user at this time.
So, yeah, don't hold your breath for major bug fixes.
Audiovox and SPCS will eventually roll out ROM updates to address the issues THEY find to be important. Those issues may well differ from the issues you find to be important.
This is one of the many joys of being on the bleeding edge of new technology.
Sad truth is that a power user of the 6700 today probably knows more about the ins and outs of the handset than 99% of those employed by the four corporations above.
You're on your own here aside from this forum. At least for a while.
im hoping for at least one Rom Update.... hell there was 3 for my Treo 600 and 2 for my Treo 650...
And you have to realize that the 6700 does exist on the GSM side as the qteq 9100/k-jam. More then likely, they are having similiar issues i am thinking. From browsing their forums, i have noticed battery problems as well as WMP problems...
the DSOD problem has been noticed as well on the Samsung i730 and that has WM2003SE.
Im actually hoping the SC card problem is a hardware problem, that way a can just get a replacement when they figure it out...
Originally posted by takmsdsm im hoping for at least one Rom Update.... hell there was 3 for my Treo 600 and 2 for my Treo 650...
And you have to realize that the 6700 does exist on the GSM side as the qteq 9100/k-jam. More then likely, they are having similiar issues i am thinking. From browsing their forums, i have noticed battery problems as well as WMP problems...
the DSOD problem has been noticed as well on the Samsung i730 and that has WM2003SE.
Im actually hoping the SC card problem is a hardware problem, that way a can just get a replacement when they figure it out...
Do we know if anyone with the Wizard is having this problem? I am not aware of it.
It did not occur on my PPC-6600 which was WM2003 (it had EVDO, but it wasn't turned on and I believe it was a different radio chip set than the one in the 6700). It seems that the i730 has this problem as well. The main thing that these two phones have in common is EVDO and the DSOD. Does anyone know if they have the same EV radio chip set? I am begining to think that this may have something to do with EVDO. After I get a DSOD, I ususaly cannot re-connect to data without a soft reset (even if taking out the SD card brings it back to life, the data radio seems to have crashed). It has never happened to me when I was connected to a computer via USB or BT. It has only happend when I was out and connected to EVDO data. Since I seem to always be in an EV area, I cannot know for sure if this would happen or not in a 1x area.
I am not convinced it has to do with the SD card since people without a card are having the problem as well. The reason why removing the card from the slot sometimes (and not all the time) brings it back to semi-life could just be that it causes the OS to do some re-initialization which brings the device back.
Originally posted by takmsdsm im hoping for at least one Rom Update.... hell there was 3 for my Treo 600 and 2 for my Treo 650...
And you have to realize that the 6700 does exist on the GSM side as the qteq 9100/k-jam. More then likely, they are having similiar issues i am thinking. From browsing their forums, i have noticed battery problems as well as WMP problems...
the DSOD problem has been noticed as well on the Samsung i730 and that has WM2003SE.
Im actually hoping the SC card problem is a hardware problem, that way a can just get a replacement when they figure it out...
Oh, you'll get your ROM updates. As for the "SC" (??DSOD??) card issue, who knows. This seems to be an almost random event from what I have read that may be triggered by a number of issues. Probably could be addressed in a ROM update if someone can get a handle on the root cause(s). It will be interesting to see what happens to the VZW handset when its finally released into the wild. Will it have similar problems or will VZW have done their homework and traced the issues down and eliminated them?
Remember the "BOD" on the SPCS 660X handsets? Maybe waiting a bit isn't so bad after all.
Originally posted by rduckwor1 Oh, you'll get your ROM updates. ...
Remember the "BOD" on the SPCS 660X handsets? Maybe waiting a bit isn't so bad after all.
Bob Duckworth
Whay re you certain of ROM updates? What is the BOD on the 660x ? Was that fixed in a timely manner?
Originally posted by winger Whay re you certain of ROM updates? What is the BOD on the 660x ? Was that fixed in a timely manner?
Well, we are talking about a WINDOZE device here. ROM updates typically follow to correct issues that manufacturers and carriers discover after they release devices.
THE "BOD" (Beep of Death) issue was a loud squeal that occurred at random during a phone call on the PPC660X devices SPCS released. Initially thought to be related to a dormant data connection, I can't say that this was conclusively proven. SPCS took 3 months to get the issue rectified. I fled to VZW and their XV6600 before my SPCS trial period was done. I was invloved with SPCS engineers and Audiovox (to a lesser extent) trying to troubleshoot the issue. To say they were less-than-responsive would be an understatement.
As much as I'd love to see an update, I think that it's time to be realistic. What possible financial incentive does Sprint or anyone else have to update our devices? We have already purchased the phone and we're tied in to 2 year contracts, they have no reason to do anything. It's easier for them to wait out the 18 month (or so) lifespan of the 6700 and fix the problems with the next generation device.
ETF's are slowly becoming a thing of the past with credits to cover them when changing carriers. ETF's are also much lower than they used to be. That's the nature of competition at work.
Originally posted by tonydiv As much as I'd love to see an update, I think that it's time to be realistic. What possible financial incentive does Sprint or anyone else have to update our devices? We have already purchased the phone and we're tied in to 2 year contracts, they have no reason to do anything. It's easier for them to wait out the 18 month (or so) lifespan of the 6700 and fix the problems with the next generation device.
Remember the old adage: It costs ten times as much to get a new customer as to keep an existing one.
SPCS will have a significant base of 6700's out there and it is their leading technology handset and a big part of their EVDO roll-out. If there are significant problems that can be addressed with ROM/Radio updates, they will likely be forthcoming.
What specific issues would you like to see addressed?
Originally posted by DREXLERMAC The locking up of the pc when you try to sync via usb cable .
This must get fixed asap .
I agree that this is a big issue for end users. It involves the handset, the handset OS, the PC and PC OS, and the software that handles the data synch. Potentially, this issue is software based and that means MS most likely will come up with the potential fix. That may be slightly better than hoping that the handset manufacturer will offer a fix. Since AS is the primary (only?) method that the handset data has to talk with the PC data, let's hope that MS finds a fix for you guys soon.
I said it before and I'll say it again. A firmware update will be released sometime in December. It should deal with a lot of the issues as found in the offical bug submit thread at my forum. If you have a problem that is not listed there, please post it at my site if you want it turned in for the next update.
Originally posted by Shadowmite I said it before and I'll say it again. A firmware update will be released sometime in December. It should deal with a lot of the issues as found in the offical bug submit thread at my forum. If you have a problem that is not listed there, please post it at my site if you want it turned in for the next update.
Well, I hope I can hold out untill December.
Unfortunately, the DSOD is not listed in your official bug list. To me, this is the most serious of all the bugs.
Same here, I use USB and it works great. Never had a problem. Remember a LOT of third party applications try to take control of USB and certain ports. Try to stop all the applications you have running in the background (taskbar) and see if that helps.
As for new bugs, I'll unlock that thread pretty soon here for new bugs to be added...
Login
Panel
