- Nov 24, 2012
- HP Probook 6470b
- Intel Core i5-3320M
- Intel HD 4000, 1600x900
- Classic Mac
- Mobile Phone
AppleBacklightAtBoot is a reading taken early in the boot process. Its value will depend on the backlight level initialized via BIOS and/or the previous OS you ran depending on whether your BIOS sets the backlight level or leaves it alone.Yeah I could imagine that. But hey, take a look at AppleBacklightAtBoot and AppleMaxBrightness. They used to be 4648 and 1808 respectively. Now they are the same, but instead of increasing AppleMaxBrightness, it decreased AppleBacklightAtBoot. I believed I should have changed 1808 to 4648, you see? Am I wrong? Also, the max brightness value I got in Windows was 122A (4650), which is very near to 4648... But 1808 is too low...
Is the brightness changing as you move the slider? Is it the same before and after display sleep?Hmm ok... So what is your final conclusion? My laptop is not compatible with this method, or the user didn't follow it correctly?
I replaced it but nothing changed, my max brightness is still similar to the Windows' min...
That is just the compiler changing things for you. In the context that the reference is in, they refer to the same thing (^ is "parent of this")In DSDT brightness patch, for my PC I think it should say \_SB.PCI0.IGPU instead of ^PCI0.IGPU
You didn't answer my question. I will try to be more clear. Is the brightness slider prior to sleep working? Is the range of brightness experienced the same before and after sleep with the DSDT patch here and the backlight injector?Brightness slider and brightness after sleep always worked fine, the only problem is the max brightness.
Also, maybe I should say that this only happens when AppleIntelSNBGraphics.kext is loaded. If I remove that kext, then I have max brightness, but everything else is crap (video memory, resolution, all wrong...)
The fixes on this thread, as far as I could notice, only changed AppleBacklightAtBoot value to be the same as AppleMaxBrightness (1808). The whole behavior is intact...
I'll look at it here. Actually working on my Envy/HD4600 right now, but I don't see why it would be any different.Nope, doesn't help... the data refreshes fast if I set the brightness with the keys, but nothing changes after it gets dimmed before turning off. It does it for you?
Just tested... and yes... I see that value does not update. It is probably because the value is temporary and not "committed".I'll look at it here. Actually working on my Envy/HD4600 right now, but I don't see why it would be any different.
Make sure you have your current brightness set relatively high.
\rmdt.p5("brit", \_sb.pnlf.lev2, \_sb.pnlf.levl, \_sb.pnlf.levw, \_sb.pnlf.levx)
It shouldn't, but it would depend on how you set the data using ACPIBacklight.Is it my eyes playing tricks on me, or does this allow the screen to go brighter than the original method?