I have been a fan of Palm for many years starting back in 1996 with a US Robotics Palm 1000 and over the years have purchased many of their products. Through blind loyalty I even replaced a Treo 650 with a Centro despite being ridiculed by my mates who at the time were all buying iPhones. When the Pre was announced it was fantastic news as I finally had a device to counter some of the stick I was getting from the Apple fanboys. After the long wait between announcement and UK availability I signed up for an 18 month contract on o2 the morning they become available here in the UK (Nov 6th?).
So impressed was I, that when my wife’s Nokia came out of contract in Feb 2010 I immediately convinced her to go for a Pre on an 24 month contract on o2.
We were happy Palm Pre users for months.
Recently though the power switch on my wife’s Pre stopped functioning correctly. It responds if pressed with herculean effort but doesn’t work otherwise. My wife assured me that it just stopped working and she hadn’t dropped it or damaged it anyway.
A bit of googling found that others also reported similar problems:
Especially interesting is this post which claims Sprint acknowledge it is a known hardware problem:
“I am bumping this thread to report the same problem. I took the phone into Sprint on Saturday and they told me that this is a known hardware problem. They said Palm is aware of it as well and they are replacing the phone with no questions asked. ”
So I took the Pre to an o2 shop, explained that it was broken and required fixing under warranty.
A week later I get a call saying that the phone is damaged and that a repair will cost 117.5 GBP. When asked for an explanation of the damage there was a very vague explanation of “crack behind the screen”. The screen does not have a crack in it (although this is also a common problem with Pres – see http://forum.o2.co.uk/viewtopic.php?f=23&t=30038) so I do not understand the comment nor the relevance to the power button.
I asked for the phone to be returned so as to check its condition. The letter that came with it simply said the phone was damaged and would cost 117.5 to repair which I had declined. No details of damage were given. I (admittedly not a trained phone engineer) cannot see any problem with it.
It seems that many other Pre users have experienced similar problems with o2 refusing to accept liability for a phone repair under warranty due to cosmetic damage of the phones:
The fee is always the same – 117.5 GBP
The justifications are often vague.
It appears that o2 are hiding behind a blanket “It is damaged” response as a simple means of not having to cover the cost of repairs themselves and if so, this is unacceptable.
I do not have a problem with Palm – I still love it. I bought 2 Palm Pres from o2 and think they have a duty of service to provide me with a handset fit for purpose and free from manufacturing defects. If they believe my phone fault is as a result of damage then they should provide a detailed explanation in their rejection of the warranty claim. Are o2 simply giving up on Palm and unconcerned if they piss of handset owners? Are o2 hoping people will give up trying to get a problems fixed by o2 and go to Palm direct instead?
I have asked @o2 several times via Twitter for info about justification for repair estimates but have yet to receive a response. Thought you might be interested in this and possibly have some insight into the problem.
Next time, Mark, get her to buy an iPhone. Because as long as it’s in warranty, you can avoid all this tossing around. It’s simply too much hassle. That’s why Apple instructs and empowers their team members to take one look at the issue and — provided you’re in warranty — get you a new one from the back. It’s simply not worth winding up the customer. And the amount of to-and-fro just ends up costing everyone more and more money. I wish more organisations adopted a can-do approach.
In the United Kingdom, however, we don’t generally get this, do we? Instead we all arse about with weeks and weeks of back-and-forward.
But who’s at fault with this specific issue. What do readers recommend Mark does next?