Page 24 of 42 FirstFirst ... 14192021222324252627282934 ... LastLast
Results 461 to 480 of 836
  1. timGSU's Avatar
    Posts
    167 Posts
    Global Posts
    210 Global Posts
    #461  
    I don't think 1 month is too much......if its a software change things like this take time.....and lots of it.....it probably has to pass both Palm's and Sprint's QE/QA departments before getting the green light to be released to consumers. I would expect something this month at the latest though......

    Either they are simply doing a small update to fix "just" this issue or they are trying to package it with another release that was already scheduled to be released to us......Right now I think it could be either situation, but of course I'm hoping we get the "fix" and an "update" all at the same time.

    Be patient, stuff like this takes time, and lots of it.
  2. #462  
    One month isnt too much? (careful everyone, Sprint or Palm has gotten to him!)
  3. #463  
    Quote Originally Posted by timGSU View Post
    Either they are simply doing a small update to fix "just" this issue or they are trying to package it with another release that was already scheduled to be released to us......Right now I think it could be either situation, but of course I'm hoping we get the "fix" and an "update" all at the same time
    That's what I'm thinking. There are rumors of the Treo 700w upgrade, which means Palm might have a working version of a later AKU plus any other patches. (it's been almost 7 months since the last Treo upgrade)

    This "fix" may require a hardreset (plausible) and maybe they're trying to roll it out all out once (if they're scheduled to do a ROM update say end of Nov or Dec, they may not want to have 2 releases so close: cost of approval by sprint, customer confusion and technical issues).

    Of course, this is all 100% pure speculation/hope on my part with nothing to back it up

    WMExperts: News, Reviews & Podcasts + Twitter
  4. #464  
    Quote Originally Posted by timGSU View Post
    I don't think 1 month is too much......if its a software change things like this take time.....and lots of it.....it probably has to pass both Palm's and Sprint's QE/QA departments before getting the green light to be released to consumers. I would expect something this month at the latest though......

    Either they are simply doing a small update to fix "just" this issue or they are trying to package it with another release that was already scheduled to be released to us......Right now I think it could be either situation, but of course I'm hoping we get the "fix" and an "update" all at the same time.

    Be patient, stuff like this takes time, and lots of it.
    You are on crack. To not have a fix for something as simple as text messaging is completely unacceptable.

    They can do a comprehensive firmware update later...and most likely we wouldn't see that for another year anyway the way they are going...bastards.
    <a href="http://www.wunderground.com/US/CA/Trabuco.html?bannertypeclick=miniDial">
    <img src="http://banners.wunderground.com/banner/ban/wxBanner?bannertype=miniDial&zip=92679" border=0
    </a>
  5. timGSU's Avatar
    Posts
    167 Posts
    Global Posts
    210 Global Posts
    #465  
    A) I'm not on crack.

    B) You obviously don't work in the software industry.
  6. #466  
    Quote Originally Posted by timGSU View Post
    B) You obviously don't work in the software industry.
    So, what's your point?
    <a href="http://www.wunderground.com/US/CA/Trabuco.html?bannertypeclick=miniDial">
    <img src="http://banners.wunderground.com/banner/ban/wxBanner?bannertype=miniDial&zip=92679" border=0
    </a>
  7. #467  
    Working in the software industry has NOTHINGto do with this issue. The issue is we are paying for a service that doesnt work!
  8. #468  
    Quote Originally Posted by rjmoose View Post
    You are on crack. To not have a fix for something as simple as text messaging is completely unacceptable.

    They can do a comprehensive firmware update later...and most likely we wouldn't see that for another year anyway the way they are going...bastards.
    Well, the whole "one month isn't too bad" is obviously completely relative, so no reason to jump on people. If you text 3,000 messages a month, it's evident that 1 day is too many. OTOH, if you do 50 a month (myself) then yeah, it's not that big of a deal.

    Re: new ROM updates, they did give the 700w one after 4 months and Palm in general has been good about updates. Considering they have so many deployed WM devices, they should be relatively on top of these upgrades (and MS does a lot of the grunt work with the AKUs).

    WMExperts: News, Reviews & Podcasts + Twitter
  9. #469  
    From a Customer Service standpoint, this whole mess is completely unacceptable. If they are having troubles, tell us. Be open. Don't bullsh*t us with conflicting answers. I am sick to death of the "Bush Administration" style secrecy. If it's going to take 2 months or you just don't know the problem yet, tell us FCS!!!
  10. #470  
    Bush Administration? WOW thats below the belt!
  11. timGSU's Avatar
    Posts
    167 Posts
    Global Posts
    210 Global Posts
    #471  
    The point is this:

    When a "bug" or "issue" turns up in production first it is verified. Knowing Sprint, this probably took at least 1 week.

    After the bug/issue is reported and verified it will be researched. In this case, both Sprint and Palm have done research trying to figure out whatís wrong, why its wrong, and possible solutions to the problem. At this point they also probably identified "workarounds" to the issue.

    Well guess what, there are workarounds for the issue (which is unfortunate in this case), and that is sending to the SMS e-mail gateways. Right there, the "pressure" level for both Sprint and Palm went down significantly. Should it, no, but guess what, it probably did.

    Sprint and Palm also probably realized that an update to Sprints servers caused the issue OR potentially Verizon and T-Mobile stopped accepting the messages since they didn't conform to the specs they were expecting. Meaning they may have accommodated the invalid encoding before and probably told Sprint that it was unacceptable and they would start dropping the messages. Sprint probably did nothing and they stopped being nice. I however think itís an update to Sprints servers that used to help re-encode our SMS messages that caused the issue. Obviously the update stopped that process from occurring.

    So now Sprint and Palm know that there is an issue, and they are developing a fix to it. Or at this point they are planning on rolling it into a full release to make rollout easier for them. I'm still not sold which route they are going since itís only reached 1 month on this issue, but I'm hoping they release the fix along with a major update to the software. I mean, letís face it, with the 6700 I can type over the 160 character limit and it will split the message up accordingly and send my message along, why the 700wx doesn't do this is beyond me.

    To me it seems that Sprint is forcing Palm to make a fix for the 700wx rather than Sprint rolling back whatever server update was done. Whatever gain was realized by the server update is apparently more important than the 700wx experiencing SMS send issues.

    Here is where it could get interesting:

    Itís probably pretty obvious that Palm has already been working on an update for the 700w/wx. The question is, was the improper encoding part of the update they were working on? Or is it fixed in the update they were working on?

    So thatís where I'm coming from, thatís why I'm not surprised we don't have a firmware update right now. As to why they won't say anything to us, I think itís more of a Sprint organizational issue overall. If they had the process in place to "notify" people of this issue, they would. But since they don't, we get all different answers from CS, etc.

    I'm definitely thinking we will get an update this month though, for sure.....the amount of time from the issue being realized to development to qe/qa to release should be getting close I would think. It just depends on how much testing each party is doing and how they are doing it. I would assume that Palm will not release the fix for Sprint to test until their QE/QA department finishes their testing and approves it. Then they will deliver the update to Sprint and they will have to send it through their QE/QA to approve it. Then palm will publish and release the update to the public.

    This all takes time and you have to understand that both companies already have items currently in their QE/QA departments currently in testing. Do I wish we could get an update in a week from 10/3, sure, but I know itís just not realistic to expect that from a major software developer unless itís a cosmetic type fix.

    Sorry guys, I just had to write all that out.....please don't flame me or anything....hopefully some of you will find it somewhat useful.
  12. timGSU's Avatar
    Posts
    167 Posts
    Global Posts
    210 Global Posts
    #472  
    Quote Originally Posted by SprintJunkie View Post
    Working in the software industry has NOTHINGto do with this issue. The issue is we are paying for a service that doesnt work!
    Sure does. You are paying for a service that doesn't work completely, right. However, there is a workaround for it. We should all be compensated for the issue, I agree.
  13. #473  
    Quote Originally Posted by timGSU View Post
    Sure does. You are paying for a service that doesn't work completely, right. However, there is a workaround for it. We should all be compensated for the issue, I agree.
    Thanks for your explanation of how it works. It was insightful but the whole thing still pisses me off. No slag against you. It's just so irritating that a $650 device can't do something that a $150 POS phone does. And then there's the runaround we get when trying to find out about it.....
  14. #474  
    Quote Originally Posted by SprintJunkie View Post
    Working in the software industry has NOTHINGto do with this issue. The issue is we are paying for a service that doesnt work!
    My point exactly!!!!
    <a href="http://www.wunderground.com/US/CA/Trabuco.html?bannertypeclick=miniDial">
    <img src="http://banners.wunderground.com/banner/ban/wxBanner?bannertype=miniDial&zip=92679" border=0
    </a>
  15. timGSU's Avatar
    Posts
    167 Posts
    Global Posts
    210 Global Posts
    #475  
    Quote Originally Posted by Brooose View Post
    Thanks for your explanation of how it works. It was insightful but the whole thing still pisses me off. No slag against you. It's just so irritating that a $650 device can't do something that a $150 POS phone does. And then there's the runaround we get when trying to find out about it.....
    oh trust me, it pisses the crap out of me, because I txt a few Verizon people almost every day at least a few times! (around 5 - 10) It also pisses me off that there wasn't enough communication done to realize that this would be a pontential issue when the servers were updated (or whatever the real reason is)......but I can't change any of that so I'll just get compensated and wait for the update....although I have thought about switching back to the 6700 until its fixed.

    Also its important to note it may not work exactly like that with Palm/Sprint, but I'm assuming most of it applies.
  16. #476  
    The REAL point is what Broose said:

    If there is a problem, have the nads to admit/acknowledge it and tell us they are working on a fix and apologize for the inconvenience and maybe offer a little perk. In other words, be PRO-ACTIVE, not in DENIAL!!!

    As of yesterday, I spoke to no less than 5 Sprint Reps who claimed there is no such problem nor were they aware of it.

    I may not be in the software industry, but I understand simple customer service:

    "Take care of your customers at all reasonable costs"

    End of rant....very very frustrated!!!!!!!!
    <a href="http://www.wunderground.com/US/CA/Trabuco.html?bannertypeclick=miniDial">
    <img src="http://banners.wunderground.com/banner/ban/wxBanner?bannertype=miniDial&zip=92679" border=0
    </a>
  17. #477  
    Quote Originally Posted by timGSU View Post
    Well guess what, there are workarounds for the issue (which is unfortunate in this case), and that is sending to the SMS e-mail gateways. Right there, the "pressure" level for both Sprint and Palm went down significantly. Should it, no, but guess what, it probably did.
    First time poster...sucks that my first post has to be a pissy one.

    The email gateway is not an acceptable workaround for me because I don't know the cell providers of over 3/4 of my cell phone contacts. So what do I do if I want to send a casual text to one person? I copy and paste their number to all the known email gateways and pray that it's one of them.

    Why is this not acceptable? Because I'm paying for every text message that goes out...so that's (at least) 5-7 text messages for one freakin' phone number.

    Happy One Month indeed. It's so frustrating calling Sprint, where the CS has either no clue or no empathy on the situation.
  18. #478  
    I just spoke to a Retention guy who checked the "known" issues. Guess what? This is now a known issue and a software patch is due out......drum roll please.... by the END OF NOVEMBER!!! Another month of this bs is possible. I appreciate at least getting this info but why oh why does it have to take so long? That BB 8703e is starting to call my name.....
  19. #479  
    I'm going to try to bring this to the public tv.. this is BS !

    I have a contact with CNN business section, wonder if its worth a story on ...
  20. #480  
    What about complaints to the better business bureau?

Posting Permissions