Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

im gonna justtry and not worry about it..I have insurance too and the only thing that would really bug me is having to replace my invisible skin. My phone still functions 100 percent and is perfect compaired to the loose slider i had to deal with on multiple Palm Pre's

Re: Dent in my TP2!!
 

yup thats a dent...sucks, i dont have that thank God! Sorry bro.

Re: Dent in my TP2!!
 

I think we will all have this in time, I am starting to see on mine what looks like a simular dent. not as deep though.

Re: Dent in my TP2!!
 

I looked at my Verizon TP2. At first glance, you can't see anything, it looks and feels perfectly smooth, but when I reflect the light off it a certain way, I can see a very slight depression that looks similar to the one on your Sprint one at the exact same spot.

Might be a manufacturing thing?

Re: Dent in my TP2!!
 

I checked my Telus TP2 and no dents at all.

Re: Dent in my TP2!!
 

I see what you guys are talking about on my VZW TP2 bought day 1. Veeeeery slightly it feels pushed in. In the right light I can slightly see it. But it's there.

Sure it would seem just cosmetic, but if it comes about like that in 2 weeks, what about a year and a half from now - still cosmetic? Time will tell. Anyone hears anything let us know?

Re: Dent in my TP2!!
 

Mine looks like what you're describing as well. I think it's a manufacturing impression from assembly. The OP's looks like poor quality assurance. Where it is located seems like if it was caused by removing the battery cover it would have caused damage to the keyboard as well.

Re: Dent in my TP2!!
 

I have the same thing on mine (I just got my TP2 an HOUR ago). Like other users are reporting, you can't see it at first, but when held at an angle, you see a very slight dent.

Re: Dent in my TP2!!
 

My week old TP2 has the dent. My dead pixel replacement that is a day old doesn't. I believe normal wear against that rubber bumper there is causing it.

Possibly a fault in design?