Jump to content


Photo

[Solved] Non-responsive, black screen during call, hard buttons cause no screen response


  • Please log in to reply
5 replies to this topic

#1 jw0914

jw0914

    All it takes for evil to triumph, is for good men to do nothing

  • Members
  • PipPip
  • 275 posts
  • LocationMadison
  • Current Device(s):Nexus 6 [XT1103]

Posted 26 May 2015 - 03:53 PM

Immediately upon pressing send, the screen immediately turn offs, is unresponsive to touch, hard buttons do not result in any screen response (they perform normally in every other aspect: volume lowers and raises with the screen off, holding the power button for 3 seconds or so cause the phone to vibrate, indicating the "Power Off" menu has popped up, hard reset combination works).  In order to end call, if other party is unable to do so (say a customer call center), phone must be hard reset.  I've had random success at fast, sequential pushes of the power button bringing the screen on for a few milliseconds, then it shuts right back off again, all responsiveness along with it.  

 

Has anyone come across a fix for this, as while this may be an issue with the proximity sensor (something I doubt) and screen protectors, hard buttons should always function as they don't rely on the proximity sensor for functionality... something many answers other thread results from Google seem to either ignore or blatantly overlook.  

 

Sequence of events:

 

Had 5.01 installed since January, screen operates fine, hard buttons always function

Flashed  5.1 about a week ago, problem began immediately on first phone call.

I do have a Zagg HD Glass screen protector, however if the proximity sensor was affected (which is highly unlikely), hard buttons should still function normally.

 

This appears to be a software bug in 5.1 that Google is under the impression is due to the proximity sensor and is not interested in fixing until further updates are pushed out (...yet the  hard buttons have no ability to bring the screen back on... not sure about their reasoning on that one.)  I'm probably going to have to flash back to a previous version of 5.1 or go back to 5.01, as this obviously isn't a bug that's feasible to live with, however I was hoping there might be something else that could be tried first since resyncing my OneNote data is a 2 day affair due to the bug within OneNote that prevents large sections from syncing properly



#2 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 26 May 2015 - 04:57 PM

not sure exactly, but definitely many people reported various proximity issues. I dont have a screen protector on.

 

The dev for MeanPop worked out a fix you can flash

http://forum.xda-dev...-1-rom-t3069031


  • rickw and jw0914 like this

#3 jw0914

jw0914

    All it takes for evil to triumph, is for good men to do nothing

  • Members
  • PipPip
  • 275 posts
  • LocationMadison
  • Current Device(s):Nexus 6 [XT1103]

Posted 26 May 2015 - 06:23 PM

There's definitely proximity issues, but this specific issue affecting the Nexus 6 on LM47I (possibly on the two previous iterations, but I'm not sure as I'm in the process of flashing E) aren't proximity sensor related, as the hard buttons will not turn the screen back on, essentially rendering the device useless.  It reminds me of the reports of malware apps that make you believe your phone is off while it's actually on.  Hard buttons (to my knowledge) have never been reliant on a proximity sensor, as it's one of the oldest cell phone input technologies.

 

Thank you for the link, I appreciate it and will try it as soon as the flash to LM47E finalizes



#4 jw0914

jw0914

    All it takes for evil to triumph, is for good men to do nothing

  • Members
  • PipPip
  • 275 posts
  • LocationMadison
  • Current Device(s):Nexus 6 [XT1103]

Posted 26 May 2015 - 06:47 PM

Perhaps I'm an idiot... because that fix worked.  I'm really perplexed how a proximity sensor coding error could prevent the hard buttons from being recognized by the firmware.


  • rickw likes this

#5 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 26 May 2015 - 08:54 PM

cant answer but glad the fix worked for you



#6 jw0914

jw0914

    All it takes for evil to triumph, is for good men to do nothing

  • Members
  • PipPip
  • 275 posts
  • LocationMadison
  • Current Device(s):Nexus 6 [XT1103]

Posted 26 May 2015 - 10:27 PM

Thanks again =]






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users