ThaSurgeonGeneral
Member
Seriously? NOBODY else is having this problem?
Sent from my DROID RAZR using DroidForums
Sent from my DROID RAZR using DroidForums
Seriously? NOBODY else is having this problem?
Sent from my DROID RAZR using DroidForums
lol...maybe not alot of ppl are. Faulty phones, lemons do happen. Maybe the folks that are having this problem havent poosted yet, or dont post on online forums. Lots of possibilities..
The rzr's screen is crap, utter pixelated crap. I was playing with a demo unit yesterday and I agree with everyone who says so.
Likewise, yes it is fast and snappy. Heck I was playing flash games on kongregate and the phone could keep up with most of them (Jobs, R.I.P but eat your heart out). Couldn't tell you much about the user experience, honestly it seems the same as any other blurred out Moto unit. It certainly feels solidly built, but I want to refer you to the user who had a very hot unit which was MELTING THE ADHESIVES OUT OF THE PHONE. I, being a poweruser, will stay away from this one.
Seriously? NOBODY else is having this problem?
Sent from my DROID RAZR using DroidForums
Do you have it set to automatically detect that it's in your pocket? If so, change it and see if you're still getting the "random" screen timeouts.
I thought the same thing as I was driving home from that store last night. I'm going to try and capture a freeze on film and will also film the phone being off in the morning. Hopefully with that proof and going to another store I can get something accomplished.If you are still within the 14 day period then the store has to replace it once with a brand new Razr no matter what. That worry free guarantee means you can bring that phone back for any reason at all and swap it out for a different phone all together or return it, or get a replacement just because you say so. You need to either go to a different store or just go in there and tell them if they are refusing to give you a new one then return it.
Nope...no consistency. That was the first time it froze on the main screen. It's frozen on the:weird - has there by ANY consistency as to what you're doing when it happens?