Contribute
Register

Ignore Clamshell state changes - keep display On (MBP Retina 2012 a1398)

Status
Not open for further replies.
Joined
Dec 10, 2012
Messages
31
Motherboard
MSI P35 Neo2
CPU
Intel Xeon X5470 (socket 771-775 mod)
Graphics
Asus Gtx 760 DirectCu II 2GB
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Hi Users.

I've tried three different Mac forums for help (iFixit, Apple Users and Developers) but have yet to receive an answers that helps me fix the problem.

I just got a 2012 Retina Macbook Pro given to me which was a god-send because my early-2008 MBP really wasn't cutting it anymore.
Some liquid was spilled on it, causing the hall effect sensor (lid sensor) to think the lid is frequently (1-2 times per minute on average) being closed and opened again couple of seconds later. Otherwise the machine works just fine.

So I'm trying to find a way to make the OS ignore input from the sensor and/or bypass it in some way. I've confirmed the issue using "ioreg -r -k AppleClamshellState", it's "No" when screen is on and "Yes" when it turns dark. So I'm trying to find a way to have it constantly be set to "No". That command also outputs "AppleClamShellCausesSleep" which is set to "Yes", changing that to "No" might also be an option, IF I can find a way to do it.
Ioreg tells me these variables are in the IOPMrootDomain class, I've found the source code for it on Apple's Open Source website but that doesn't really help me at this time because even if I would change it and compile a new version, I don't know how to implement it.

Another option would be if there is some CLI tool like "pmset" that would allow me to set a variable that would solve this issue and have that run at startup using a script.

I would like to try to refrain from doing hardware modifications at this point in time because the machine works completely fine besides this single issue. If I don't find a way to fix this using software, I will try pulling the sensor (or at least one or two components on it) off the motherboard using a heat gun.
 
Just wanted to update, the problem seems to be fixed for now by removing a component from the sensor, see below.

 
Status
Not open for further replies.
Back
Top