[KEYBOARD] Brightness adjustment key.
Tu
-
jeannets Posted messages 28331 Registration date Status Contributeur Last intervention -
jeannets Posted messages 28331 Registration date Status Contributeur Last intervention -
Hello, this is the first time I'm asking a question on a forum because I can't find the answer after hours of searching online. Several times.
So I have a problem with the brightness adjustment shortcut keys. I'm on Windows 10. Since I have a Thinkpad P15s, these keys are located on F5 and F6 and only work with Fn lock disabled.
These keys do nothing. When I press the decrease brightness button, no matter what brightness level I'm at, it just brings it back to 90/100. When I press the increase brightness button, it activates the brightness adjustment (I see the blue bar with the sun appear) but it doesn't change the brightness level.
I have no issues with any other Fn shortcut keys. I just replaced my keyboard with a new one (and retrieved my number pad keys, most of which weren't working due to a liquid spill on that specific area).
I've uninstalled and reinstalled the latest drivers for the keyboard and graphics card. Anyway, they were up to date.
I have all the Windows updates.
I've tried accessing the keyboard input settings but that didn't help.
I've installed Sharpkeys but it doesn't offer any brightness adjustment settings.
I use Lenovo's update software but it tells me there are no issues (and doesn't offer anything specific for the keyboard).
It doesn't seem to be a physical problem. My keyboard is new.
The keys do something and activate the screen brightness function.
So what's going on, the registry? I don't know anything about the registry if you can help me.
Oh yes, and often at startup the keys work normally. It can last 5 seconds or 5 minutes, always after startup.
Sorry for the long message, I prefer to give you all the information I've been able to gather myself.
And thank you in advance for your expertise.
So I have a problem with the brightness adjustment shortcut keys. I'm on Windows 10. Since I have a Thinkpad P15s, these keys are located on F5 and F6 and only work with Fn lock disabled.
These keys do nothing. When I press the decrease brightness button, no matter what brightness level I'm at, it just brings it back to 90/100. When I press the increase brightness button, it activates the brightness adjustment (I see the blue bar with the sun appear) but it doesn't change the brightness level.
I have no issues with any other Fn shortcut keys. I just replaced my keyboard with a new one (and retrieved my number pad keys, most of which weren't working due to a liquid spill on that specific area).
I've uninstalled and reinstalled the latest drivers for the keyboard and graphics card. Anyway, they were up to date.
I have all the Windows updates.
I've tried accessing the keyboard input settings but that didn't help.
I've installed Sharpkeys but it doesn't offer any brightness adjustment settings.
I use Lenovo's update software but it tells me there are no issues (and doesn't offer anything specific for the keyboard).
It doesn't seem to be a physical problem. My keyboard is new.
The keys do something and activate the screen brightness function.
So what's going on, the registry? I don't know anything about the registry if you can help me.
Oh yes, and often at startup the keys work normally. It can last 5 seconds or 5 minutes, always after startup.
Sorry for the long message, I prefer to give you all the information I've been able to gather myself.
And thank you in advance for your expertise.
6 réponses
Thank you for your responses which are not helping me at all.
-The brightness adjustment issue was present before the liquid spill.
-I spilled a few drops on the side of the numeric keypad, which is opposite the Fn keys (I don't know where the motherboard is).
-My computer is a Lenovo Thinkpad P15s, it is designed to withstand liquid spills, dust, and shocks; moreover, I just replaced the keyboard, it is separated in a watertight manner from the inside of the computer, there is not even a need to open the bottom of the computer to change it.
-I just tested the motherboard using Lenovo's Diagnostic tool and everything is fine on that front. (I also conducted other tests: keyboard, video card... and no malfunction was found).
-At the moment I am writing this, I just restarted my computer 5 minutes ago and the brightness adjustment keys are functioning normally. As I have already mentioned, they start to bug randomly after a few minutes.
THUS:
-The problem is clearly not hardware-related; otherwise it would NEVER work.
-So please stop insisting on the obsession with the motherboard and the water droplets.
-Could you perhaps, with your great knowledge, explain to me which driver the Fn keys depend on, since apparently it doesn't depend on the keyboard?
-Or help me narrow down the issue by eliminating or highlighting the areas that it could affect: the Windows 10 operating system, the Lenovo BIOS, the drivers (and if so, which one?), the registry?
THANK YOU.
-The brightness adjustment issue was present before the liquid spill.
-I spilled a few drops on the side of the numeric keypad, which is opposite the Fn keys (I don't know where the motherboard is).
-My computer is a Lenovo Thinkpad P15s, it is designed to withstand liquid spills, dust, and shocks; moreover, I just replaced the keyboard, it is separated in a watertight manner from the inside of the computer, there is not even a need to open the bottom of the computer to change it.
-I just tested the motherboard using Lenovo's Diagnostic tool and everything is fine on that front. (I also conducted other tests: keyboard, video card... and no malfunction was found).
-At the moment I am writing this, I just restarted my computer 5 minutes ago and the brightness adjustment keys are functioning normally. As I have already mentioned, they start to bug randomly after a few minutes.
THUS:
-The problem is clearly not hardware-related; otherwise it would NEVER work.
-So please stop insisting on the obsession with the motherboard and the water droplets.
-Could you perhaps, with your great knowledge, explain to me which driver the Fn keys depend on, since apparently it doesn't depend on the keyboard?
-Or help me narrow down the issue by eliminating or highlighting the areas that it could affect: the Windows 10 operating system, the Lenovo BIOS, the drivers (and if so, which one?), the registry?
THANK YOU.
When giving instructions, it must be done BEFORE. Our possible knowledge does not make us fortune tellers.
-The brightness adjustment issue was prior to the liquid spill.
This was not mentioned anywhere in your post.
-I spilled a few drops on the side of the numeric keypad, which is opposite the Fn keys (I don't know where the motherboard is).
The motherboard is located roughly "everywhere" in a laptop; it covers between 60 and 95% of the surface depending on the type of laptop.
-My computer is a Lenovo Thinkpad P15s, it is designed to withstand liquid spills, dust, and shocks; by the way, I just changed the keyboard, it is sealed off from the interior of the computer, and you don't even need to open the bottom of the computer to change it.
Likewise, you never indicated that. It's impossible to know the thousands of different models.
-At the moment I am writing these lines, I just restarted my computer 5 minutes ago, and the brightness adjustment keys are working normally. As I have already mentioned, they start to bug out randomly after a few minutes.
So it is probably not a software issue either because if that were the case, it would already be malfunctioning from the start.
THEREFORE:
-The problem is clearly not hardware-related; otherwise, it would NEVER work.
False! A hardware issue can very well be related to one or more components, which can react to various causes: heat, humidity, shock...
-So please stop insisting on the obsession with the motherboard and the drops of water.
It is your presentation of the facts and the lack of specific information that led to the most logical assumption. You are in front of the machine, not us.
-You could, for example, with your vast knowledge, explain to me which driver the Fn keys depend on, since apparently it does not depend on the keyboard.
The keys depend, like all other components, on both a hardware part AND a software part. The Fn keys are just keys like any others, no more no less; it's just a contact. Then the keyboard is connected via a connector to the motherboard.
But if you have changed the keyboard, we can eliminate the physical part of the keyboard and also eliminate the water since it occurred after this issue.
If your (brand) drivers are up to date, then logically the motherboard and/or its controller could very well be the culprits. Is the BIOS up to date? I had two HP series with keyboard issues, and updating the BIOS fixed the problem.
-Or help me narrow down the problem by eliminating or highlighting the areas it could touch: the Windows 10 operating system, the Lenovo BIOS, the drivers (and if yes, which one?), the registry?
The answer is partly given.
OS: no. (if up to date)
BIOS: yes
Drivers: yes (unless up to date)
Registry: no
Motherboard and specific controller: yes
Afterwards, we will never be as effective as a technician who has the PC in front of him. Thank you not to forget that.
-The brightness adjustment issue was prior to the liquid spill.
This was not mentioned anywhere in your post.
-I spilled a few drops on the side of the numeric keypad, which is opposite the Fn keys (I don't know where the motherboard is).
The motherboard is located roughly "everywhere" in a laptop; it covers between 60 and 95% of the surface depending on the type of laptop.
-My computer is a Lenovo Thinkpad P15s, it is designed to withstand liquid spills, dust, and shocks; by the way, I just changed the keyboard, it is sealed off from the interior of the computer, and you don't even need to open the bottom of the computer to change it.
Likewise, you never indicated that. It's impossible to know the thousands of different models.
-At the moment I am writing these lines, I just restarted my computer 5 minutes ago, and the brightness adjustment keys are working normally. As I have already mentioned, they start to bug out randomly after a few minutes.
So it is probably not a software issue either because if that were the case, it would already be malfunctioning from the start.
THEREFORE:
-The problem is clearly not hardware-related; otherwise, it would NEVER work.
False! A hardware issue can very well be related to one or more components, which can react to various causes: heat, humidity, shock...
-So please stop insisting on the obsession with the motherboard and the drops of water.
It is your presentation of the facts and the lack of specific information that led to the most logical assumption. You are in front of the machine, not us.
-You could, for example, with your vast knowledge, explain to me which driver the Fn keys depend on, since apparently it does not depend on the keyboard.
The keys depend, like all other components, on both a hardware part AND a software part. The Fn keys are just keys like any others, no more no less; it's just a contact. Then the keyboard is connected via a connector to the motherboard.
But if you have changed the keyboard, we can eliminate the physical part of the keyboard and also eliminate the water since it occurred after this issue.
If your (brand) drivers are up to date, then logically the motherboard and/or its controller could very well be the culprits. Is the BIOS up to date? I had two HP series with keyboard issues, and updating the BIOS fixed the problem.
-Or help me narrow down the problem by eliminating or highlighting the areas it could touch: the Windows 10 operating system, the Lenovo BIOS, the drivers (and if yes, which one?), the registry?
The answer is partly given.
OS: no. (if up to date)
BIOS: yes
Drivers: yes (unless up to date)
Registry: no
Motherboard and specific controller: yes
Afterwards, we will never be as effective as a technician who has the PC in front of him. Thank you not to forget that.
This time it held up well for an hour before starting to bug.
Thanks for the more constructive response.
So it probably won't be a software issue either, because if that were the case it should have malfunctioned +- from the start.
The + or - raises my eyebrows. If it's hardware, it's categorical, it works or it doesn't, right?
Whereas if it's software, it can, more or less, start malfunctioning later. It's strange too, I grant you, but given that I don't see a third solution, by elimination, I feel like it proves that the problem is software. Am I wrong?
Unless:
False! A hardware issue can very well be related to one or more components, each of which can react to various causes: heat, humidity, shock...
It would be surprising if the same external factor occurs every time between 1 minute and 1 hour after startup. My computer never overheats, doesn't get shocked... There's no possible correlation between a physical event and the functioning of the keys ceasing. Unless there could be a link between closing the lid and sleep mode AND the function keys? I just thought of this, I will run some tests, but it could be that it happens after closing and reopening the lid, or after sleeping in general.
FN keys are just like any other keys, no more no less, they're just contacts. Then the keyboard is connected via a connector to the motherboard.
Thanks for the explanation for the clueless. I was talking about the software, I was asking about the drivers. Because when you look in the keyboard settings, there's everything but the function keys. When you start a virtual keyboard for testing, there's everything but the function keys. When you download a specific software to change the key assignments (Sharpkeys), we have access to everything except a few Fn keys (we have the volume control keys, End, Insert, Home, Delete, but not microphone control, airplane mode, brightness, or hanging up a call for example).
So when I update the keyboard driver, I feel like it's not even touching the problem.
Internet searches rather make want to update the graphics card driver, but I don't quite understand why.
So:
OS: NO (up to date)
Bios: NO (up to date as of yesterday, updates every few days for this BIOS, it's crazy)
Drivers: NO (up to date)
Registry: NO
Motherboard and specific controller: YES.
Okay but which controller, how to check that, run tests?
I’m not going to pay and go see a "tech" to fix this. It's not a big deal, it just forces me to do an extra 3-second maneuver to adjust the brightness. It's just the fact that I don't understand where it's coming from that annoys me, and I was hoping to find the same kind of thinking here, with more knowledge. A desire to understand where it comes from, to solve the problem at the source.
Thanks for the more constructive response.
So it probably won't be a software issue either, because if that were the case it should have malfunctioned +- from the start.
The + or - raises my eyebrows. If it's hardware, it's categorical, it works or it doesn't, right?
Whereas if it's software, it can, more or less, start malfunctioning later. It's strange too, I grant you, but given that I don't see a third solution, by elimination, I feel like it proves that the problem is software. Am I wrong?
Unless:
False! A hardware issue can very well be related to one or more components, each of which can react to various causes: heat, humidity, shock...
It would be surprising if the same external factor occurs every time between 1 minute and 1 hour after startup. My computer never overheats, doesn't get shocked... There's no possible correlation between a physical event and the functioning of the keys ceasing. Unless there could be a link between closing the lid and sleep mode AND the function keys? I just thought of this, I will run some tests, but it could be that it happens after closing and reopening the lid, or after sleeping in general.
FN keys are just like any other keys, no more no less, they're just contacts. Then the keyboard is connected via a connector to the motherboard.
Thanks for the explanation for the clueless. I was talking about the software, I was asking about the drivers. Because when you look in the keyboard settings, there's everything but the function keys. When you start a virtual keyboard for testing, there's everything but the function keys. When you download a specific software to change the key assignments (Sharpkeys), we have access to everything except a few Fn keys (we have the volume control keys, End, Insert, Home, Delete, but not microphone control, airplane mode, brightness, or hanging up a call for example).
So when I update the keyboard driver, I feel like it's not even touching the problem.
Internet searches rather make want to update the graphics card driver, but I don't quite understand why.
So:
OS: NO (up to date)
Bios: NO (up to date as of yesterday, updates every few days for this BIOS, it's crazy)
Drivers: NO (up to date)
Registry: NO
Motherboard and specific controller: YES.
Okay but which controller, how to check that, run tests?
I’m not going to pay and go see a "tech" to fix this. It's not a big deal, it just forces me to do an extra 3-second maneuver to adjust the brightness. It's just the fact that I don't understand where it's coming from that annoys me, and I was hoping to find the same kind of thinking here, with more knowledge. A desire to understand where it comes from, to solve the problem at the source.
I understand the urge, but sometimes from a technical standpoint, it is not always possible to determine the cause of a problem. Unless you have a "lab" with all the tools and diverse knowledge (hardware/software that are different). This is my job (with hundreds of machines), I know what I'm talking about :-) Even we don't have a real lab, no economic interest.
Anyway, you partially reasoned this out yourself above and also partly concluded (namely that it's not always easily identifiable).
So I won't go over your entire post.
But for the controller, if all the BIOS and software updates are done, you must first identify it, it's integrated into the motherboard.
And even if you manage to do that, it's not "controllable" or testable by the average person.
In fact, in professional practice, for this type of problem, I call the manufacturer, we don't test too long, too expensive, and you need a lab; we change the motherboard, it's faster and cheaper.
Of course under warranty or support contract, it doesn't cost us anything.
An electronic component, contrary to popular belief, does "wear out"; usually it takes a long time, but manufacturing weaknesses, unusual constraints, and bam, it can malfunction, and no, it's not necessarily "on/off".
So I will close this here as far as I'm concerned; your issue is likely to remain "undetermined" given the symptoms.
Sometimes it's interesting to look at the drivers/updates that do not come directly from the manufacturer but from DriversCloud, which lists your components and provides updates from the component manufacturers themselves.
I don't think it comes from the software side, but in the end you have nothing to lose.
Have a good Sunday.
Anyway, you partially reasoned this out yourself above and also partly concluded (namely that it's not always easily identifiable).
So I won't go over your entire post.
But for the controller, if all the BIOS and software updates are done, you must first identify it, it's integrated into the motherboard.
And even if you manage to do that, it's not "controllable" or testable by the average person.
In fact, in professional practice, for this type of problem, I call the manufacturer, we don't test too long, too expensive, and you need a lab; we change the motherboard, it's faster and cheaper.
Of course under warranty or support contract, it doesn't cost us anything.
An electronic component, contrary to popular belief, does "wear out"; usually it takes a long time, but manufacturing weaknesses, unusual constraints, and bam, it can malfunction, and no, it's not necessarily "on/off".
So I will close this here as far as I'm concerned; your issue is likely to remain "undetermined" given the symptoms.
Sometimes it's interesting to look at the drivers/updates that do not come directly from the manufacturer but from DriversCloud, which lists your components and provides updates from the component manufacturers themselves.
I don't think it comes from the software side, but in the end you have nothing to lose.
Have a good Sunday.
Last bottle thrown into the sea, you never know.
I ran the tests and the problem actually occurs after it goes to sleep. Whether it's by closing the lid, clicking on sleep, or waiting.
Any magic ideas?
I ran the tests and the problem actually occurs after it goes to sleep. Whether it's by closing the lid, clicking on sleep, or waiting.
Any magic ideas?
touslesdrivers.com is no longer maintained for quite some time, driverscloud is actually the "suite".
Magical, right? This would confirm that it is not hardware if we are logical. So there’s a chance it's a software issue, but which one.... Let's see what the scan from https://www.driverscloud.com/ will show.
Magical, right? This would confirm that it is not hardware if we are logical. So there’s a chance it's a software issue, but which one.... Let's see what the scan from https://www.driverscloud.com/ will show.
Just to keep you updated, driverscloud just made me do a system restore after installing 3 new drivers. My computer was ventilating heavily non-stop, and it didn't fix the brightness issue.
It definitely comes from the sleep mode. Even after 3-4 hours, without sleep, there are no problems.
But oh well, nobody has any ideas, never mind.
It definitely comes from the sleep mode. Even after 3-4 hours, without sleep, there are no problems.
But oh well, nobody has any ideas, never mind.
jeannets
Posted messages
28331
Registration date
Status
Contributeur
Last intervention
Ambassadeur
6 597
Hello,
This might not be a keyboard issue...??
This liquid could have leaked onto the motherboard..??
This might not be a keyboard issue...??
This liquid could have leaked onto the motherboard..??
The motherboard being THE central part, of course it can.
And if so, why?
Because no computerized system likes liquids.
Best regards.