Why does my laptop screen dim after a few seconds on battery power?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
It isn't actually locking or going to sleep. After a few seconds, the screen just clicks to a slightly darker setting. I have looked through dconf editor and the settings menu, and can't find any. Someone on here asked a similar question about Fedora, but it was a system update that fixed it. I'm running Debian 9, so that won't work for me. Below I will include a screenshot of my dconf power menu:
To be clear, this issue doesn't plague me when the laptop is plugged in. But when it's unplugged, the computer gets noticeably darker after just a few seconds of idling.
Also, the screen brightens back up as soon as I touch the mouse or the keyboard.
Solved, kind of: While dealing with some other issues, I rebooted my computer a few times (something I hadn't done since messing with dconf) and the issues seems to have gone away. So perhaps it was just necessary to reboot after editing?
debian dconf
asked Nov 9 '17 at 20:40
Clayton McCray
283
add a comment |Â
up vote
0
down vote
favorite
It isn't actually locking or going to sleep. After a few seconds, the screen just clicks to a slightly darker setting. I have looked through dconf editor and the settings menu, and can't find any. Someone on here asked a similar question about Fedora, but it was a system update that fixed it. I'm running Debian 9, so that won't work for me. Below I will include a screenshot of my dconf power menu:
To be clear, this issue doesn't plague me when the laptop is plugged in. But when it's unplugged, the computer gets noticeably darker after just a few seconds of idling.
Also, the screen brightens back up as soon as I touch the mouse or the keyboard.
Solved, kind of: While dealing with some other issues, I rebooted my computer a few times (something I hadn't done since messing with dconf) and the issues seems to have gone away. So perhaps it was just necessary to reboot after editing?
debian dconf
asked Nov 9 '17 at 20:40
Clayton McCray
283
could be a bug in gnome?
– mattia.b89
Nov 9 '17 at 20:47
Maybe, that would be extremely irritating. I don’t know what to do if that’s the case.
– Clayton McCray
Nov 9 '17 at 20:48
open a bug in the gnome bugtracker: bugzilla.gnome.org
– mattia.b89
Nov 9 '17 at 20:51
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
It isn't actually locking or going to sleep. After a few seconds, the screen just clicks to a slightly darker setting. I have looked through dconf editor and the settings menu, and can't find any. Someone on here asked a similar question about Fedora, but it was a system update that fixed it. I'm running Debian 9, so that won't work for me. Below I will include a screenshot of my dconf power menu:
To be clear, this issue doesn't plague me when the laptop is plugged in. But when it's unplugged, the computer gets noticeably darker after just a few seconds of idling.
Also, the screen brightens back up as soon as I touch the mouse or the keyboard.
Solved, kind of: While dealing with some other issues, I rebooted my computer a few times (something I hadn't done since messing with dconf) and the issues seems to have gone away. So perhaps it was just necessary to reboot after editing?
debian dconf
asked Nov 9 '17 at 20:40
Clayton McCray
283
It isn't actually locking or going to sleep. After a few seconds, the screen just clicks to a slightly darker setting. I have looked through dconf editor and the settings menu, and can't find any. Someone on here asked a similar question about Fedora, but it was a system update that fixed it. I'm running Debian 9, so that won't work for me. Below I will include a screenshot of my dconf power menu:
To be clear, this issue doesn't plague me when the laptop is plugged in. But when it's unplugged, the computer gets noticeably darker after just a few seconds of idling.
Also, the screen brightens back up as soon as I touch the mouse or the keyboard.
Solved, kind of: While dealing with some other issues, I rebooted my computer a few times (something I hadn't done since messing with dconf) and the issues seems to have gone away. So perhaps it was just necessary to reboot after editing?
debian dconf
asked Nov 9 '17 at 20:40
Clayton McCray
283
edited Nov 17 '17 at 4:32
asked Nov 9 '17 at 20:40
Clayton McCray
283
asked Nov 9 '17 at 20:40
Clayton McCray
283
asked Nov 9 '17 at 20:40
Clayton McCray
283
283
could be a bug in gnome?
– mattia.b89
Nov 9 '17 at 20:47
Maybe, that would be extremely irritating. I don’t know what to do if that’s the case.
– Clayton McCray
Nov 9 '17 at 20:48
open a bug in the gnome bugtracker: bugzilla.gnome.org
– mattia.b89
Nov 9 '17 at 20:51
add a comment |Â
could be a bug in gnome?
– mattia.b89
Nov 9 '17 at 20:47
Maybe, that would be extremely irritating. I don’t know what to do if that’s the case.
– Clayton McCray
Nov 9 '17 at 20:48
open a bug in the gnome bugtracker: bugzilla.gnome.org
– mattia.b89
Nov 9 '17 at 20:51
could be a bug in gnome?
– mattia.b89
Nov 9 '17 at 20:47
could be a bug in gnome?
– mattia.b89
Nov 9 '17 at 20:47
Maybe, that would be extremely irritating. I don’t know what to do if that’s the case.
– Clayton McCray
Nov 9 '17 at 20:48
Maybe, that would be extremely irritating. I don’t know what to do if that’s the case.
– Clayton McCray
Nov 9 '17 at 20:48
open a bug in the gnome bugtracker: bugzilla.gnome.org
– mattia.b89
Nov 9 '17 at 20:51
open a bug in the gnome bugtracker: bugzilla.gnome.org
– mattia.b89
Nov 9 '17 at 20:51
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
Especially on Laptops, the embedded controller (EC) does a lot of things, including power management and controlling of the backlight.
Unfortunately, every vendor does this differently, and none of this is documented somewhere. For Windows, the pre-installed drivers reasonably support it; for Linux, the situation is difficult because of the diversity and lack of documentation.
So I very much suspect it is the EC that turns down your backlight after a few seconds of confirming that there's no power from the power supply. (My laptop does this instantly). If that is the case, looking at Gnome settings or filing a bug is not going to help.
On my laptop, I can turn the brightness up again manually. See if this works on your laptop. If you are lucky, the EC produces an ACPI event (or some sort of event) you can catch with a custom script, and then turn the backlight back up automatically, but how this works (if at all) will depend entirely on your laptop, so you need to do a bit of reading and sleuthing. E.g. try acpi_listen.
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
Okay, thanks. I'll look into that. I just edited the question to reflect this, but I don't have to manually turn up the brightness again in the sense of changing the setting; as soon as I touch the mousepad or the keyboard the screen brightens back up.
– Clayton McCray
Nov 10 '17 at 21:49
Then I'd suspect some kind of "display power saving mode if you are not using it" executed on the EC. And I bet you can turn it off somehow. Do you still have the Windows drivers for it? Any settings for that in those?
– dirkt
Nov 11 '17 at 6:26
My laptop is dual booting Windows 10 and Debian 9, so I would think I do still have windows drivers. Should I poke around in the settings of the Windows partition?
– Clayton McCray
Nov 14 '17 at 20:48
Yes, definitely look at the Windows drivers.
– dirkt
Nov 14 '17 at 20:51
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Especially on Laptops, the embedded controller (EC) does a lot of things, including power management and controlling of the backlight.
Unfortunately, every vendor does this differently, and none of this is documented somewhere. For Windows, the pre-installed drivers reasonably support it; for Linux, the situation is difficult because of the diversity and lack of documentation.
So I very much suspect it is the EC that turns down your backlight after a few seconds of confirming that there's no power from the power supply. (My laptop does this instantly). If that is the case, looking at Gnome settings or filing a bug is not going to help.
On my laptop, I can turn the brightness up again manually. See if this works on your laptop. If you are lucky, the EC produces an ACPI event (or some sort of event) you can catch with a custom script, and then turn the backlight back up automatically, but how this works (if at all) will depend entirely on your laptop, so you need to do a bit of reading and sleuthing. E.g. try acpi_listen.
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
Okay, thanks. I'll look into that. I just edited the question to reflect this, but I don't have to manually turn up the brightness again in the sense of changing the setting; as soon as I touch the mousepad or the keyboard the screen brightens back up.
– Clayton McCray
Nov 10 '17 at 21:49
Then I'd suspect some kind of "display power saving mode if you are not using it" executed on the EC. And I bet you can turn it off somehow. Do you still have the Windows drivers for it? Any settings for that in those?
– dirkt
Nov 11 '17 at 6:26
My laptop is dual booting Windows 10 and Debian 9, so I would think I do still have windows drivers. Should I poke around in the settings of the Windows partition?
– Clayton McCray
Nov 14 '17 at 20:48
Yes, definitely look at the Windows drivers.
– dirkt
Nov 14 '17 at 20:51
add a comment |Â
up vote
0
down vote
Especially on Laptops, the embedded controller (EC) does a lot of things, including power management and controlling of the backlight.
Unfortunately, every vendor does this differently, and none of this is documented somewhere. For Windows, the pre-installed drivers reasonably support it; for Linux, the situation is difficult because of the diversity and lack of documentation.
So I very much suspect it is the EC that turns down your backlight after a few seconds of confirming that there's no power from the power supply. (My laptop does this instantly). If that is the case, looking at Gnome settings or filing a bug is not going to help.
On my laptop, I can turn the brightness up again manually. See if this works on your laptop. If you are lucky, the EC produces an ACPI event (or some sort of event) you can catch with a custom script, and then turn the backlight back up automatically, but how this works (if at all) will depend entirely on your laptop, so you need to do a bit of reading and sleuthing. E.g. try acpi_listen.
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
Okay, thanks. I'll look into that. I just edited the question to reflect this, but I don't have to manually turn up the brightness again in the sense of changing the setting; as soon as I touch the mousepad or the keyboard the screen brightens back up.
– Clayton McCray
Nov 10 '17 at 21:49
Then I'd suspect some kind of "display power saving mode if you are not using it" executed on the EC. And I bet you can turn it off somehow. Do you still have the Windows drivers for it? Any settings for that in those?
– dirkt
Nov 11 '17 at 6:26
My laptop is dual booting Windows 10 and Debian 9, so I would think I do still have windows drivers. Should I poke around in the settings of the Windows partition?
– Clayton McCray
Nov 14 '17 at 20:48
Yes, definitely look at the Windows drivers.
– dirkt
Nov 14 '17 at 20:51
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Especially on Laptops, the embedded controller (EC) does a lot of things, including power management and controlling of the backlight.
Unfortunately, every vendor does this differently, and none of this is documented somewhere. For Windows, the pre-installed drivers reasonably support it; for Linux, the situation is difficult because of the diversity and lack of documentation.
So I very much suspect it is the EC that turns down your backlight after a few seconds of confirming that there's no power from the power supply. (My laptop does this instantly). If that is the case, looking at Gnome settings or filing a bug is not going to help.
On my laptop, I can turn the brightness up again manually. See if this works on your laptop. If you are lucky, the EC produces an ACPI event (or some sort of event) you can catch with a custom script, and then turn the backlight back up automatically, but how this works (if at all) will depend entirely on your laptop, so you need to do a bit of reading and sleuthing. E.g. try acpi_listen.
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
Especially on Laptops, the embedded controller (EC) does a lot of things, including power management and controlling of the backlight.
Unfortunately, every vendor does this differently, and none of this is documented somewhere. For Windows, the pre-installed drivers reasonably support it; for Linux, the situation is difficult because of the diversity and lack of documentation.
So I very much suspect it is the EC that turns down your backlight after a few seconds of confirming that there's no power from the power supply. (My laptop does this instantly). If that is the case, looking at Gnome settings or filing a bug is not going to help.
On my laptop, I can turn the brightness up again manually. See if this works on your laptop. If you are lucky, the EC produces an ACPI event (or some sort of event) you can catch with a custom script, and then turn the backlight back up automatically, but how this works (if at all) will depend entirely on your laptop, so you need to do a bit of reading and sleuthing. E.g. try acpi_listen.
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
answered Nov 10 '17 at 8:36
dirkt
14.2k2931
14.2k2931
Okay, thanks. I'll look into that. I just edited the question to reflect this, but I don't have to manually turn up the brightness again in the sense of changing the setting; as soon as I touch the mousepad or the keyboard the screen brightens back up.
– Clayton McCray
Nov 10 '17 at 21:49
Then I'd suspect some kind of "display power saving mode if you are not using it" executed on the EC. And I bet you can turn it off somehow. Do you still have the Windows drivers for it? Any settings for that in those?
– dirkt
Nov 11 '17 at 6:26
My laptop is dual booting Windows 10 and Debian 9, so I would think I do still have windows drivers. Should I poke around in the settings of the Windows partition?
– Clayton McCray
Nov 14 '17 at 20:48
Yes, definitely look at the Windows drivers.
– dirkt
Nov 14 '17 at 20:51
add a comment |Â
Okay, thanks. I'll look into that. I just edited the question to reflect this, but I don't have to manually turn up the brightness again in the sense of changing the setting; as soon as I touch the mousepad or the keyboard the screen brightens back up.
– Clayton McCray
Nov 10 '17 at 21:49
Then I'd suspect some kind of "display power saving mode if you are not using it" executed on the EC. And I bet you can turn it off somehow. Do you still have the Windows drivers for it? Any settings for that in those?
– dirkt
Nov 11 '17 at 6:26
My laptop is dual booting Windows 10 and Debian 9, so I would think I do still have windows drivers. Should I poke around in the settings of the Windows partition?
– Clayton McCray
Nov 14 '17 at 20:48
Yes, definitely look at the Windows drivers.
– dirkt
Nov 14 '17 at 20:51
Okay, thanks. I'll look into that. I just edited the question to reflect this, but I don't have to manually turn up the brightness again in the sense of changing the setting; as soon as I touch the mousepad or the keyboard the screen brightens back up.
– Clayton McCray
Nov 10 '17 at 21:49
Okay, thanks. I'll look into that. I just edited the question to reflect this, but I don't have to manually turn up the brightness again in the sense of changing the setting; as soon as I touch the mousepad or the keyboard the screen brightens back up.
– Clayton McCray
Nov 10 '17 at 21:49
Then I'd suspect some kind of "display power saving mode if you are not using it" executed on the EC. And I bet you can turn it off somehow. Do you still have the Windows drivers for it? Any settings for that in those?
– dirkt
Nov 11 '17 at 6:26
Then I'd suspect some kind of "display power saving mode if you are not using it" executed on the EC. And I bet you can turn it off somehow. Do you still have the Windows drivers for it? Any settings for that in those?
– dirkt
Nov 11 '17 at 6:26
My laptop is dual booting Windows 10 and Debian 9, so I would think I do still have windows drivers. Should I poke around in the settings of the Windows partition?
– Clayton McCray
Nov 14 '17 at 20:48
My laptop is dual booting Windows 10 and Debian 9, so I would think I do still have windows drivers. Should I poke around in the settings of the Windows partition?
– Clayton McCray
Nov 14 '17 at 20:48
Yes, definitely look at the Windows drivers.
– dirkt
Nov 14 '17 at 20:51
Yes, definitely look at the Windows drivers.
– dirkt
Nov 14 '17 at 20:51
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f403610%2fwhy-does-my-laptop-screen-dim-after-a-few-seconds-on-battery-power%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
could be a bug in gnome?
– mattia.b89
Nov 9 '17 at 20:47
Maybe, that would be extremely irritating. I don’t know what to do if that’s the case.
– Clayton McCray
Nov 9 '17 at 20:48
open a bug in the gnome bugtracker: bugzilla.gnome.org
– mattia.b89
Nov 9 '17 at 20:51