Active Topics

 


Reply
Thread Tools
Posts: 8 | Thanked: 3 times | Joined on Jan 2012 @ Michigan, USA
#1
Hold off on calling me crazy for a bit. You might also remember me for damaging a tiny part (touchscreen ribbon cable) (http://talk.maemo.org/showthread.php?t=87274).

I'd just gotten my replacement N9, and it was going well for a few days, so it's time to swap the case to my sexy blue one!

After that, starting *either* phone with the old, non-responsive screen works. Starting either phone with the "working" screen results in a boot loop.

I understand that this isn't much to go on, but any ideas?
 
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#2
"Boot Loop -- Caused by end user, breaking his hardware when trying to swap the case." - sounds more like the correct topic.

You could of course try to disable watchdogs that reboot the device on hardware failure. (search the forum for flasher parameters).
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
 
Posts: 8 | Thanked: 3 times | Joined on Jan 2012 @ Michigan, USA
#3
Good news, everyone! (because you were all waiting with bated breath, right )

It seems that the boot loop was caused by an issue with the proximity sensor. Just by not attaching it the phone boots and runs just fine. I miss the standby screen and all, and doubletap to wake doesn't work... But it's a small price to pay (and proxy sensors are cheap!)

Maybe someday this will help a poor, clumsy soul like me.
 
Posts: 20 | Thanked: 0 times | Joined on Aug 2012
#4
can you please explain this a litle better? thanks
 
Reply


 
Forum Jump


All times are GMT. The time now is 10:48.