Monday, March 17, 2008

What's with Palm Treo 755p and Sprint

HELP! I can't take it anymore! I had to write about it and at least get the frustration off my chest.

I'm on my fifth Treo 755p with no end in sight as to why it keeps bricking. By bricking, I mean that it freezes up and nothing can get it to reset or reboot past the white welcome "ACCESS powered" screen. OF COURSE I've done the 'hard reset' -- that's seems to be the extent of what anyone from Sprint or Palm can suggest.

I tried to figure out what was the cause, and for a while I was pretty sure it was adding a second bluetooth audio device. However, this last failure happened so soon, that I never had a chance to add the second device and it still froze.

My latest guess is that this failure is due to being on a fringe area when on a call. I believe I was in the same store when it failed at least once before. Maybe the software has a safety feature that shuts it down when putting out too strong a signal. Then, when rebooting, it notices the last stored signal level is too high, so it doesn't want to continue. Nice theory, huh? Who knows if it's at all even close to the truth.

One would think that Sprint, and especially Palm would be interested in my failures. After all, someone is paying to replace and repair the device. But no! Seems like no one cares.

Emailing Palm is like emailing a help desk in India that, perhaps speaks English, but doesn't really understand what I wrote. I told them I had a working device and was afraid it was going to fail. So they responded by telling me how to reboot the device, and lastly how to do a hard reset. They also told me to take off my third party apps, one at a time. Of course my email said I was running NO third party apps. After a little back and forth, they suggested that it was a hardware problem -- great thinking! Four devices in a row with the same problem?

At least Sprint has cheerfully (though no so much this last time) replaced the device, although I have to wait each time for about an hour for them to "test" my device and see that it really doesn't boot. I can't blaim them too much, other than the fact that they, too, should want to know what's going on.

Perhaps someone can suggest what to do, or someone from Palm would read this an take an interest. After all, it's their broken product!

Now, that I got it off my chest, I hope to make another phone call or two before it dies again.

4 comments:

Yaakov (Jeff) said...

Wow! In desperation, I tried emailing a top person at Palm and actually got a response. Unfortunately, since the failure I'm seeing is not a frequent occurrence, it doesn't get much attention. That makes sense, but awfully frustrating even if you are the 1 in a million.

Nonetheless, I got a call (?did I provide my phone number?) from Palm corporate offering some real support help. I need to set up a time to work with them. Hope it works.

While waiting around the Sprint store, I checked out the other phones. I think I'll pass on them. The Window's stuff is not really designed for a touch interface, though it works. My fingernails are not sharpened to a point to use as a stylus. The calendar app doesn't even allow compressing the days view, and shows much less that the Palm OS does. The only good thing I saw was that the memos allowed taking scribbled notes along with voice and typed text -- something I think is obvious, yet sorely missing from the Palm. That's was the first 3rd party app I tried to install --- long ago -- when I 'allowed' myself to have 3rd party apps.

Yaakov (Jeff) said...

I guess I'm not the only one:

http://discussion.treocentral.com/showthread.php?t=162474

John said...

Hi Jeff.

I have been tracking some of these issues at Palm and I wanted to know if you ever tried to install the 755p update on any of your devices before they were frozen? There was a least one fix in that update that prevents an Access Logo hang. You can find it here if get another device. http://www.palm.com/us/support/downloads/treo755pupdate/sprint.html

Yaakov (Jeff) said...

I did speak to tier 3 support at Palm, and at leat one person recognized this as a know, unsolved problem -- but -- he had a solution to prevent my palm from dying again -- reset the device, wipe out the 'backup' directory on the PC, and just do a transfer from PC to palm, not a real sync. That would prevent some *bad* settings from ruining the device.

Seemed to work!

I just saw the 1.07 Sprint software update, so I installed that now.

The other thing that happened is that I returned the leased car with the built-in bluetooth audio. (UConnect from Chrysler).

Either way, I seem to be infinitelty more stable now. Not a crash or reset since.