Contribute
Register

Native Brightness working without 'blinkscreen' using patched AppleBacklight.kext

Status
Not open for further replies.
Hi rehab, this method is good also for my hp not probook version?

I used last script version here http://www.tonymacx86.com/hp-proboo...-range-brightness-using-acpibacklight-16.html
with right command and right values but 2 things,
1) all brightness levels are good also without monitor sleep/wake, so for this works good
2) levels are not equal with windows, i mean there are all levels, from completely black screen to highest.

I am not interested to more vanilla, less vanila, honestly i would try to solve this also with this other method if possible, it's the only missing things on my HP.

Thanks
 
Hi rehab, this method is good also for my hp not probook version?

I think this technique applies to any HD3000/HD4000 laptop.

I used last script version here http://www.tonymacx86.com/hp-proboo...-range-brightness-using-acpibacklight-16.html
with right command and right values but 2 things,
1) all brightness levels are good also without monitor sleep/wake, so for this works good

Not sure what you mean by what you wrote for #1.

2) levels are not equal with windows, i mean there are all levels, from completely black screen to highest.

I don't think it is our goal to produce the same levels as Windows.
 
I think this technique applies to any HD3000/HD4000 laptop.

Ok , i try


Not sure what you mean by what you wrote for #1.

Sorry, i mean, the initial problem about not all levels available is now gone with that script and your kext.


I don't think it is our goal to produce the same levels as Windows.

Ok. But it's strange that completely all levels are available. I mean, the lowest on windows is not completely black screen like now on osx.
For exmple, there is a guide on "another forum" about the choice of right panel in an apple kext. For example if i set my panel to a similar macbook panel i have more or less more balanced brightness levels. I would to delete this last mod, i prefer solve with one of those methods.
 
@jona1
Why the obsession of making it look like windows? You have the tools to make it close to what you have to windows, but more importantly you can make it as you like it best... Try with that.
 
Sorry, i mean, the initial problem about not all levels available is now gone with that script and your kext.

Yes, both of these solutions are solving the same problem in different ways.

Ok. But it's strange that completely all levels are available. I mean, the lowest on windows is not completely black screen like now on osx.

By design. Like a real MacBook[Pro/Air]. Lowest level on real Macs is black (backlight off).

The goal is not to make OS X work like Windows, but rather to make OS X work on our laptops like it does on a real Mac.
 
@jona1
Why the obsession of making it look like windows? You have the tools to make it close to what you have to windows, but more importantly you can make it as you like it best... Try with that.

You are right, thanks for right words..
 
By design. Like a real MacBook[Pro/Air]. Lowest level on real Macs is black (backlight off).

Oh buddy, really i did not know this, completely.. I thought that lowest level had to be like in windows..

The goal is not to make OS X work like Windows, but rather to make OS X work on our laptops like it does on a real Mac.

Now it's clear rehab, honestly now i prefer to use your kext, i know it's less vanilla, but it works good and no problem with future update, plist or not plist.
Maybe i'll try also this.

Thanks
 
Updated the script to also make an AppleBacklightInjector.kext. Intended to be installed alongside vanilla AppleBacklight.kext.

Please try it and provide feedback. Thanks...
 
Updated the script to also make an AppleBacklightInjector.kext. Intended to be installed alongside vanilla AppleBacklight.kext.

Please try it and provide feedback. Thanks...
All seems fine here with the injector... how come you gave in? man, how will you sleep with all the system warnings you will be causing across the globe :p
 
All seems fine here with the injector... how come you gave in? man, how will you sleep with all the system warnings you will be causing across the globe :p

So far I don't see any. In this case there is no conflict as there aren't two separate definitions for the iokit match (unlike the AppleHDA case).

I think what is happening is the system is loading actually loading two different instances of the kext (that is allocating two separate AppleIntelPanelA objects), and going through the startup sequence for each one, up to the point of calling ::probe for both. But because the IOProbeScore is higher for the injector (2500 vs. 2000), it chooses to start (calling ::start... etc.) the injector one instead of the native.
 
Status
Not open for further replies.
Back
Top