Timeline for Atrix will boot up but unlock screen is unresponsive
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2013 at 0:04 | history | edited | Izzy |
edited tags
|
|
| Oct 22, 2012 at 8:11 | answer | added | wkwaseem | timeline score: 2 | |
| Apr 27, 2012 at 1:29 | history | edited | Brian Mortenson | CC BY-SA 3.0 |
update
|
| Apr 25, 2012 at 17:10 | history | notice removed | CommunityBot | ||
| Apr 25, 2012 at 17:10 | history | bounty ended | CommunityBot | ||
| Apr 22, 2012 at 9:47 | answer | added | Arvanitis Christos | timeline score: 0 | |
| Apr 18, 2012 at 7:33 | answer | added | Sameer Sharma | timeline score: 0 | |
| Apr 17, 2012 at 15:50 | history | notice added | Brian Mortenson | Draw attention | |
| Apr 17, 2012 at 15:50 | history | bounty started | Brian Mortenson | ||
| Apr 17, 2012 at 2:33 | history | edited | Brian Mortenson | CC BY-SA 3.0 |
update
|
| Apr 17, 2012 at 2:15 | comment | added | Brian Mortenson | It's not a touchscreen failure. The first debugging message I listed there is happening in response to touching the screen. I have now confirmed my initial thought that it's just the home application -- I received a call and was able to unlock the screen to answer it. Once I answered it, I got a popup saying the Home application was not responding and forced closed it. During the call I could use the features specific to the call, but couldn't use the home button or the power button, as before. So I would like to remove and reinstall or repair the Home app over ADB. Is this possible? | |
| Apr 16, 2012 at 20:33 | comment | added | Matthew Read | Strange. The error makes it sound like you might be saved by a factory reset, but otherwise I would suspect the touchscreen has failed. | |
| Apr 16, 2012 at 17:12 | comment | added | Brandorf | Personally, I had pretty much the exact same thing happen to a Droid X. Phone would boot, but it was impossible to unlock the phone. I wiped the phone to no avail, took it back to Verizon, they re-flashed it, but ultimately it was decided that it was some sort of hardware fault, and I was given a replacement. | |
| Apr 16, 2012 at 2:06 | history | tweeted | twitter.com/#!/StackAndroid/status/191709188907483137 | ||
| Apr 15, 2012 at 22:43 | history | edited | Brian Mortenson | CC BY-SA 3.0 |
update
|
| Apr 15, 2012 at 7:17 | history | asked | Brian Mortenson | CC BY-SA 3.0 |