If you have problems with the headphone jack, take it to the store. Don't use the Insurance/Assurion, because they will charge you $50 for a replacement, and you only get to use that 3 times a year. (Sometimes they make exceptions, like if there is not an Authorized Repair Center nearby).
Take the phone to an Authorized Repair Center (Not every store is), and tell them the problem. They will either repair or swap out the device with a new one since you have what's called ESRP. (Extended service and repair). It's a subset of your Insurance package, Total Equipment Protection, or TEP. From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Robertson Sent: Wednesday, May 28, 2008 11:07 AM To: [email protected] Subject: [Treo] Sprint Treo 755p update at Palm.com website May 28, 2008 I continued to have problems with my sound going out on my 755p. Blowing air into the headphone jack helped on occasion, but not always. Sound would return on occasion out of the clear blue. Device was undependable. I called Sprint tech support at *2. I have the Sprint device insurance. I do not know if that was required for the tech to speak with me. Anyway, the tech based in Fort Worth, Texas, was very helpful and suggested I first try the Palm.com software update for the device. In case the updated software did not work, he give me an Eticket number and Sprint repair store location near my location to use in case I needed to take the device in and use my "insurance," which I pay for on each month's statement. I had version 1.04 on my 755p. The latest at Palm.com is 1.07. You can check your version by opening the phone dial up screen and going to Options and then scrolling down to Phone Info. That will tell you your software version. The download takes over 45 minutes. The web site has instructions. So far my 755p is functioning well after installing 1.07. I am keeping my fingers crossed. Here is the URL for the 755p update: http://www.palm.com/us/support/treo/treo755psprint/<http://www.palm.com/ us/support/treo/treo755psprint/> Not whining or complaining, but for the curious, the 1.07 update did not fix the dreaded Error 3000 message. Robert, Austin, Texas [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
