Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
With the non-dev preview branch now updated to 3.5, you may run into a permissions issue when trying to change this setting in Konsole:
sudo echo 80 > /sys/class/hwmon/hwmon4/max_battery_charge_level
bash: /sys/class/hwmon/hwmon4/max_battery_charge_level: Permission denied
Apparently the ">" operator attempts to run before sudo, meaning that you technically aren't running this command as root and it fails.
To fix this, use this command instead:
echo 80 | sudo tee /sys/class/hwmon/hwmon4/max_battery_charge_level
You can verify this is set with the following command:
cat /sys/class/hwmon/hwmon4/max_battery_charge_level
Happy charge limiting!
EDIT: One more update here because this is REALLY interesting - It looks like PowerTools recognises if you're on SteamOS 3.5 and alters this setting directly! So previously where PowerTools charge limit would not work with the Deck turned off, now it DOES!
I'll keep an eye on things incase I'm wrong but that's a HUGE W for PowerTools if this is true.
sudo bash -c "echo 80 > /sys/class/hwmon/hwmon4/max_battery_charge_level"
What I want, is: Steamdeck stops using battery when it is in PSU Mode. And I can set a Threshold to not charge the battery while being in PSU Mode. Like.. Max charge 80%. And only start charging when below 75%. And when in PSU Mode, Battery wont be used, AND wont be charged either and just stays at.. lets say 78% (according to the set threshold)
I'd also love to have this in vanilla SteamOS, since there's obviously demand for it based on the amount of people who have asked me (the PowerTools dev) about the setting. I'm pretty hesitant about recommending this to the average user though, since the default battery charge behaviour is quite good and prevents some issues that can come up if you never let the battery fully charge & discharge.
This was added in PowerTools v1.4.0, but it's got a sort of dumb bug: it doesn't disable the charge limit when you turn it off in the PowerTools UI. Should be fixed in next PowerTools update.
For older kernels, PowerTools will fallback to the old slightly sketchy way of setting the battery limit by directly talking to the battery management chip. For people who like the vanilla experience, this is technically possible to do without PowerTools but it's a bit complicated so I don't want encourage regular users to do it. If you're an advanced user, the implementation is the last part of this file https://git.ngni.us/NG-SD-Plugins/PowerTools/src/branch/main/backend/src/settings/steam_deck/util.rs#L104
(e.g. call set(Setting::ChargeMode, ChargeMode::Idle as u8) to do passthrough charging, set(Setting::ChargeMode, ChargeMode::Normal as u8) for regular charging).
By default, the Steam Deck does this at 90%, though it will charge up to 100% when it goes below 90%. Generally, you don't need to change this since that's a quite reasonable limit. It's commonly called passthrough mode, since the power from the charger is passed directly through to the Steam Deck hardware, bypassing the battery.
The thing is, it is now stuck at 84%. It did not charge to 88%. Is there some kind of buffer zone, like, it has to be 5%-10% below the max value, so it will start charging?
And I read, that currently there is a bug, prevent you from turning off the charge limit. You need to do it manually via commands. I know how to do this. But just to confirm: to reset everything to default again, the value of the command-start must be "echo 100" right? not "echo 90"?
By the way, did 3.5.5 implement this natively?