Manually keep backlight keyboard on Sony Vaio Z21

Actually, further to my note, there'a a much simpler way to do what you're suggesting:

Keep the P21KBDBacklihgtIlluminanceHigh to 0C always.

Then just use the Vaio Control Center (VCC) to select whether you want the backlight on or off (just by using the "turn backlight on when surroundings dark" checkbox). That way, it's ignoring whether it's light and dark, and just turning itself on or off depending on what is set in VCC.

 

Guess who feels pretty dumb just now. Thanks.

 

where are these files to modify located on the z21?

 

AFAIK most of those bounties never get paied on XDA. They are a good way of knowing what people really want though and good incentive for some to start looking at things. There is some amazing work being done here and it would be great to see some things here progress the way they have at XDA.

The past couple of project threads I started I had almost make 4 replies to reserve those first posts like is done on XDA.

It is great to see people paying attention to this. As it has been shown many times here if we want features like this, we have to figure it out ourselves. Nice job everyone.

I suggest looking at Process Monitor and setting the filter.

 

Back to the Sony gets 90% right thing?

 

The Z2 does not have the VESAutoDimmer key. It has a VESAutoDimmer2 key which seems to have more to do with the screen brightness rather than the keyboard.

In any event I added the P21... value to VESAutoDimmer2 with no effect and then created a VESAutoDimmer key with this value in it, and again, to no effect.

 

Difference here is that....



...and I make pictures that are oddly cropped too, apparently

Slow day at work thanks to Mr Columbus...

 

In my case, Mr. Columbus means there's no air conditioning. The temp in my office is almost 31°C.

 

So tweak the backlight and buy a a new compressor, on me

Open a window dude, you'll pass out.

 

If I could, I would.

A statement as applicable to passing out as opening a window.

 

Zoinks, would you mind posting a screenshot of your control center page?

 

Sorry for the large image, I'm in a 125% DPI mood today.



I haven't reassembled the Z1 from the WWAN transplant yesterday, so I don't have a pic for that.

Ideally, I'd like the exact KB settings from the Z1 for the Z2. I don't mind having to cycle a service to turn it on/off though. A simple batch file should make that livable if we can't somehow shoehorn the control center bits.

I think an always on or always off switcher would satisfy my needs and qualify for the bounty. Heck, you could even hit the batch file via the VAIO key, which might not be too shabby.

 

ZoinksS2k, just out of interest, where do you make that much money to give away such a bounty for a software mod? Are you in investment banking ?

 

I work in the interwebs

 

Anybody working this thingy?

 

I'm out of ideas at the "source" level. Unless someone's got a better (read simpler) idea, I suppose the next step is to decompile the app and see how the backlight is being triggered and how the time delay is being sent over.

 

If I can help test or whatever, let me know.

The $250 is earning me 1.6% interest

 

Unfortunately, neither the Vaio Control Center nor the KbdBacklightSetting event service are written in managed code. That eliminates all the "simple" tools at my disposal and it's not clear I want to work directly with assembly language.

I'll have to ruminate on this a bit.

Anyone else have a good idea here???

 

^^ Lol, I didn't post that, but I tried using .NET tools to intercept calls. Worked like a charm on AlienFX (Dell/Alienware light controll tool - it sends calls over USB on their setups), but no go on the SC/SA, and apaprently, no go on the Z2, either.

 

How about writing a script that runs at startup that presses a non-used key (i.e. the FN key) for a millisecond every 30 seconds. Or a script that triggers some other sort of other interrupt on the ps2 line?

Zoinks - I'll take half of the $250 for the idea, will help me pay for the JB4 I just installed (holy CRAP BTW)....

 

Is that meant in a good way or in a bad way?

Unused key idea is good, but avoid the Fn key - will cause unexpected results if this happens while you are typing. Unless your script checks for typing and only runs if the keyboard is idle. I recommend the scroll-lock key - haven't used that much.

 

Jb4 is car talk, sorry for the OT (but yes, definitely a good way). Good thoughts on the key, although 1ms out of 60 odds are pretty low you'd see an issue. Scroll lock would work, I have to imagine there are some unused keycodes as well for our US keyboards.

 

Fix denied

PS: I will be upgrading my ECU with the GIAC stg 1 kit once my exhaust comes in. With black thermal coat, of course.

 

^Envy the M3 exhaust big time, probably my favorite part of that car. But the torque of the N54 is pretty damn amazing. Down shifts are nearly pointless.

 

That's what the DCT is for. It'll blip the gas on downshift so you can stay in the powerband. Love riding the thing as close to the 8200rpm redline as possible. The Honda S2000 (the S2k in my name) redlined at 10K, but that was on a 4 Banger. The M3 is an 8

 

Where exactly on the Z2 do these go?

 

^The Z2 sits in the passenger seat doing datalogging duties!

 

Latest thinking:

This is indeed the place where the current setting is stored, but only for the purpose of the UI in the Control Center, as opposed to storing it in the Registry.

I still believe that the value being used is in the BIOS somewhere.

Here's why:

If you change the value in the file between 0 (10 seconds), 1 (30 seconds) and 2 (60 seconds) and then cover the sensor, the backlight only comes on for the time that was last set in the Control Center. i.e. if you last set 10 seconds in the Control Center and then change the file to 60 seconds, the backlight only comes on for 10 seconds.

If, however, you change the value to 60 seconds in the Control Center, then when you cover the sensor the keyboard lights up for the 60 seconds.

My guess is that the Control Center is storing the value in the BIOS for the system to use when the sensor is activated, and using the file just to initialize the current display in the its UI.

I have tried a value 3 for the timeout, but that seems to revert to 10 seconds. So, I still don't know if the CC is sending out an index (i.e. 0, 1 or 2), or an actual value (i.e. 10, 30 or 60). If it's just an index and there's no mapping for it in the BIOS then it's just not going to happen. If it's an actual value, then it's only a matter of time before someone finds this.

And so it goes...

 

Looking at the screen that ZoinksS2k sent, it looks like the Z2 much more closely reflects what the SA/SB/SC does than what the Z1 does (i.e. the ability to set different values for AC/battery).

rmcx, you do need to reboot (or otherwise restart the service) for the value to 'take' in the Z1 (in the Z1, when the service starts, it retrieves the value in the file and uses that). When you made change manually in the file, did you reboot before checking whether it has reflected the change or not?

Also, if someone with a Z2 could confirm that the system does definitely reflect the backlight timeout before windows starts (e.g. in the bios settings/ or windows 'F8' page). That would definitely confirm that the Z2 is using the BIOS to store these settings (unlike the Z1 which just uses the VaioEvent Service and is always 10 seconds before windows boots).

Other suggestions I have is for someone with a SA/B/C to post their 'CurrentSettingProfileData.xml' file with the backlight setting to always on, so we can see what value should be recorded there (or even better, do a comparison with the file when it's set to 10 seconds, so we can see exactly which entry is changing and what to). The other area of interest would be for someone with a Z2 or SA/B/C to post the contents of their:
HKLM\Software\Wow6432Node\Sony Corporation\Vaio Event Service\Settings\VESAutoDimmer2 registry settings, as that's the other relevant bit for the Z1.

But if it's bios based, it may just be that the Z2 bios does not support always on, which would explain why sony did not include the option for the Z2 but did include it for the SA. It could be fixed in one of their "regular" bios updates!

 

Re: Rebooting: That was my specific test - to see if rebooting was necessary or not.

1) I set the value of the timeout in the CC and then covered the sensor. Sure enough the backlight went off in that time frame.

2) I reset the value manually in the CurrentSettingsProfileData.xml file and covered the sensor. The backlight still turned off in the same time frame as in step 1.

3) I opened up the CC and noted that the UI now reflected what I had changed manually in step 2. I then changed the value via the CC and committed and then covered the sensor. The backlight now turned off in the time that I just specified in the CC.

i.e. I don't need to reboot for the new values to take effect IF they were set via the CC. If I do reboot, then yes, the values in the file are picked up and used.

To me, this indicates that the value that the system is using at any given moment is not being stored in the file. It may not be BIOS. It may well be main memory - but it's not in the file. Otherwise I would see the new timeout whenever I changed the file manually. And I'm not seeing that.

Now, a good argument that it's in main memory as opposed to BIOS is that when I actually go into the BIOS and cover the sensor, the timeout period always seems to be 10 seconds. I would think that if it's truly in the BIOS then it would use whatever value is set there. Which it's not.

etc.

 

It's clearly an acpi call, we just don't know how vaio event service is doing it. Beyone that, the value probably isn't even stored anywhere - the event service probably runs the on/off timer itself.

 

Not sure if this helps, but I installed the z1 bits on the z2 to see if he functionality carried over. The KB bl settings were not available in the control center.

 

I don't quite understand your second sentence here. Could you expand on that please.

 

So, it's taking the same approach as the Z1: the VAIO Event Service, when it starts, picks up the entry in the file and then sets the backlight timeout accordingly. So, there's a (small) possibility we can tweak it in windows. Back to my request for a comparison with Z2 and SA/B/C:

Could an owner of a Z2 post/attach their CurrentSettingProfileData.xml' file and separately, the entries in HKLM\Software\Wow6432Node\Sony Corporation\Vaio Event Service\Settings\VESAutoDimmer2 registry settings

Could an owner of the SA/B/C do the same (when the timeout has been set to "do not turn off")?, and if possible, attach an additional CurrentSettingProfileData.xml file after the timeout has been set to 10 seconds so we can compare?

file location is: C:\Users\{your user id}\App Data\Roaming\Sony Corporation\Vaio Control Center

Thanks!!

Also, ZoinksS2K, have you tried transplanting any of the files from the SA/B/C onto your Z2 rather than using old Z1 files, given that that the SA seems to much more closely match the approach the Z2 takes?

 

HKLM\SOFTWARE\Wow6432Node\Sony Corporation\VAIO Event Service\Settings\VESAutoDimmer2:

ExitACBrightLevel REG_DWORD 0x0000000f (15)
ExitDCBrightLevel REG_DWORD 0x00000005 (5)
NewACP1Nit REG_DWORD 0X000000b6 (182)
NewDCP1Nit REG_DWORD 0x000000b6 (182)
NewP1Lux REG_DWORD 0x0000007c (124)
ShowState REG_DWORD 0x00000000 (0)

C:\Program Data\Sony Corporation\VAIO Control Center\CurrentSettingProfileData.xml:

 

I went through a bit of trouble getting the SC (which has NO keep KB backlight on all all times option, BTW) to get the "keep backlit KB on at all times," functionality. I eventually installed the SA's Vaio CC with the help of several fellow SA/B/C/D owners and got the SC to have the "full control," over the backlit KB. Though after 2-3 standby/resume sessions, the backlit KB control normally returned to the default functionality... until a full reboot was initiated. Hope this helps.



I sold my SC, so this is my SA's readings:
OS is utterly stock. I'm not going to do anything to this, just swap it out for a SSD and a clean install afterwards.

 

I don't believe that the file in \Users...\Roaming\... does anything here.

Note that the samples presented above are identical.

I believe it's the file in \Program Data\Sony Corporation\... that holds the backlight values.

 

I'm no coder, but I'm speculating that the sony event service is looking at your setting for the backlight and perhaps running the "timer" itself and turning the backlight on and off via acpi - vs. just telling bios "hey the backlight timer is 30 seconds".

I'm away from my Z, but I would screw around with some software that allows you to play around with ACPI - perhaps Aida64. There are some good WIP tables around the internets that take a stab at the different ACPI functions Sony uses (primarily for linux).

 

So I watched a WMI performance counter on VESMgr, VESMgrSub1 and VESMgrSub2 while changing the timeout value in the CC. Sure enough there was a characteristic spike in one of the I/O values each time I hit the Apply or OK button. ==> the CC is transmitting something to the service right then and there.

Am hunting now for some sort of traffic monitoring app.

 

Many thanks for the info.
I don't think there's much more I can do with a Z1 - the SA and Z2 take quite a different approach. Either the parameters in the Z1 (such as P20KBDBacklihgtIlluminanceLow) are hiding somewhere else in the registry in the SA/Z2 or the event service no longer uses these values.

It's positive that by using the SA files on an SC, you were able to get the SC to have the "keep backlit keyboard on" functionality (which it didn't have before). Perhaps owners of the Z2 could take the same approach to get the functionality working on their Z2.

Sorry, you're right, rmcx: I was incorrect in the location of the file of interest. It should be:
C:\ProgramData\Sony Corporation\VAIO Control Center

 

Good call on that. I have changed the setting, and noticed it always edits:

C:\ProgramData\Sony Corporation\Vaio Control Center\CurrentSettingProfileData.xml

Specifically, this string:

PHP:

-<Class Classid='3F041FCE-B164-434C-A23E-3CBDD43FE0A6'> -<Item bEvent="0" bAllUser="1" Settingid='1'> <SettingData>0</SettingData></Item>-<Item bEvent="0" bAllUser="1" Settingid='2'> <SettingData>0</SettingData></Item>-<Item bEvent="0" bAllUser="1" Settingid='4'> <SettingData>3</SettingData></Item>-<Item bEvent="0" bAllUser="1" Settingid='3'> <SettingData>0</SettingData></Item></Class>

 

SettingID1 seems to be AC Power, Always on. When it's settingdata is "0," it's activated. When it's "1,' it's deactivated, and the 10sec option applies. "2," is Never turn on.

SattingID2 is the "on, but turn off after..." It's setting data:
0=off/10sec
1=30sec
2=60sec
3=Never off when dark

Setting3/4 corrospond for Battery Power

Note: Settings 1 and 3 override their respective 2/4 counterparts.

Also, if you have never used the option in Vaio CC before, it's specific setting will not exist until you do. I.e, if you haven't used the Battery Power "Turn on in low light conditions," option, then "settingID=4" will not exist until you do. Make sure to press apply each time.



The easiest way to find out which overall CLASSID is responsible? Just change the backlit KB options around, the XML file will change accordingly. For me, it was the last one.

 

I have tried a setting "3" in the Z2 file but as far as I can tell it is not interpreted and the timeout is defaulted to 10 seconds.

 

Haven't tried, but will after I put the Clear-Coat.com stuff on this morning.

Don't know if you still need the XML, but here's mine:

PHP:

<?xml version="1.0" encoding="UTF-8"?>
<CurrentSetting Machineid='18485'><Class Classid='F6C9FEA9-EAEB-492e-B2D0-6FB840C97866'>
        <Item Settingid='7' bAllUser="1" bEvent="0">
            <SettingData>514825</SettingData></Item><Item Settingid='1' bAllUser="1" bEvent="0">
            <SettingData>16</SettingData></Item><Item Settingid='3' bAllUser="1" bEvent="0">
            <SettingData>1</SettingData></Item></Class><Class Classid='E00CAA8C-52C2-41df-8046-F50FB4569563'>
        <Item Settingid='3' bAllUser="1" bEvent="0">
            <SettingData>0</SettingData></Item></Class><Class Classid='29A1BD33-9FC4-479a-8CBD-97747BDF49D0'>
        <Item Settingid='2' bAllUser="1" bEvent="0">
            <SettingData>0</SettingData></Item></Class><Class Classid='3F041FCE-B164-434C-A23E-3CBDD43FE0A6'>
        <Item Settingid='2' bAllUser="1" bEvent="0">
            <SettingData>2</SettingData></Item><Item Settingid='4' bAllUser="1" bEvent="0">
            <SettingData>2</SettingData></Item></Class><Class Classid='ADFA262A-9192-4637-9980-AD0FD523B22A'>
        <Item Settingid='1' bAllUser="1" bEvent="0">
            <SettingData>1</SettingData></Item></Class><Class Classid='48886F79-DE98-4475-845A-C638B6EB336B'>
    <Item Settingid='2' bAllUser="1" bEvent="0">
    <SettingData>0</SettingData></Item></Class><Class Classid='5CB31408-19EE-4fdf-B88A-2279A8D3C698'>
    <Item Settingid='1' bAllUser="1" bEvent="0">
    <SettingData>0</SettingData></Item></Class></CurrentSetting>

pyr0 and I played around a bit via IM. He had me try this which didn't do anything.

PHP:

<?xml version="1.0" encoding="UTF-8"?>
<CurrentSetting Machineid='18485'><Class Classid='F6C9FEA9-EAEB-492e-B2D0-6FB840C97866'>
        <Item Settingid='7' bAllUser="1" bEvent="0"><SettingData>514825</SettingData></Item>
        <Item Settingid='1' bAllUser="1" bEvent="0"><SettingData>16</SettingData></Item>
        <Item Settingid='3' bAllUser="1" bEvent="0"><SettingData>1</SettingData></Item>
    </Class>
    <Class Classid='E00CAA8C-52C2-41df-8046-F50FB4569563'>
        <Item Settingid='3' bAllUser="1" bEvent="0"><SettingData>0</SettingData></Item>
    </Class>
    <Class Classid='29A1BD33-9FC4-479a-8CBD-97747BDF49D0'>
        <Item Settingid='2' bAllUser="1" bEvent="0"><SettingData>0</SettingData></Item>
    </Class>
    <Class Classid='3F041FCE-B164-434C-A23E-3CBDD43FE0A6'>
        <Item Settingid='2' bAllUser="1" bEvent="0"><SettingData>3</SettingData></Item>
        <Item Settingid='4' bAllUser="1" bEvent="0"><SettingData>3</SettingData></Item>
    </Class>
    <Class Classid='ADFA262A-9192-4637-9980-AD0FD523B22A'>
        <Item Settingid='1' bAllUser="1" bEvent="0"><SettingData>1</SettingData></Item>
    </Class>
    <Class Classid='48886F79-DE98-4475-845A-C638B6EB336B'>
        <Item Settingid='2' bAllUser="1" bEvent="0"><SettingData>0</SettingData></Item>
    </Class>
    <Class Classid='5CB31408-19EE-4fdf-B88A-2279A8D3C698'>
        <Item Settingid='1' bAllUser="1" bEvent="0"><SettingData>0</SettingData></Item>
    </Class>
</CurrentSetting>

 

My feeling is that the Event Service only accepts an index since it reads the config file when it initializes and interprets what it finds there (i.e. an index). I've tried indexes other than 0, 1 and 2 with no success. Thus, without actually trying to patch the Service, I think that's a dead end.

Per someone's idea earlier in the thread, I'll see if I can rig a little app to pulse the sensor event periodically. I don't believe it's just a matter of simply sending keyboard strokes since I can cover the sensor and hit my external keyboard without turning the backlight on. It'll be a matter of emulating the sensor event and/or sending a pulse specifically emulating the built-in keyboard.

I've tried trapping several EMI events, but haven't found it yet.

 

I've noticed that the backlight seems to remember the setting when in the BIOS or in the Splashtop contrivance. Could be hallucinating the whole thing tho

 

It was a flat 10 seconds for me when in the BIOS.

And when I feed the service a bogus index, it defaults to 10 seconds.

 

glad I found this thread, I was looking in to it as well and ended up in the CurrentSettingProfileData.xml and the registry location.

Any updates on this, looks like the thread died out

 

It is still unresolved and the bounty stands

 

ZoinksS2k, I might have a solution for this. Wrote a simple program this morning which manage to control the backlit keyboard on my VPCZ12 rather well. (only initial testing so far)

Probably I would need to tweak some parameters in order for it to work on the Z21 (never used this model so don't know) so please post your email and i will contact you and see if we can fix a working program for that model too.

//Andreas