Comment on Why doesn’t the steamdeck hibernate by default?
Gnugit@aussie.zone 10 months ago
Linux has typically been buggy when it comes to hibernation. I wouldn’t bother, it’s not worth the risk in my opinion.
It’s not really a risk- it stays plugged in all the time…except on the rare occasion when it doesn’t. ;-)
I’m surprised there isn’t some kind of fail-safe that starts a graceful shutdown at 10-20% if it’s been in sleep for >x hours. Taking a LiPo to 0% is terrible for the pack; most devices have some sort of fail safe against this kind of battery stress.
There’s an option to automatically shutdown when battery drops to X%
Where, if I might ask? I looked under every setting in the UI and couldn’t find it. Is it somewhere in the bowels if desktop mode? I only use the deck as an appliance, like a switch. Maybe it would be better to wipe and install windows?
Just got to the KDE plasma settings and search for it.
There’s an option to automatically shutdown when battery drops to X%
Where do I find it? I’ve gone all through the settings and the developer settings, is it in desktop mode?
Yes, it’s one of KDE Plasma’s settings.
Isn't keeping it plugged in all the time really bad for the battery? It should stay between 30 and 80% iirc.
Iirc the SD does discharge from full battery a bit when plugged in for a while to preserve battery health.
It lets the battery discharge to 90% while plugged in. If you’re not using it for a few days you should still unplug.
It will still keep it above 90% all the time which is bad according to most comments I just found by googling about it, it's just the nature of lithium batteries. Steam deck allegedly has a feature to use direct power from outlet if in use while charging and if at max, but it still keeps battery at high %.
It’s worse than storing it in the ideal zone - between 3.6 and 4.0 volts (% means nothing if we’re getting technical as there is an interpretation later in software). Constantly at 4.2 is bad, dropping below 3.0 is very very bad, and going to ~2.7(iirc) is simply murder. I have a telemetry module in a rocket which doors not have a low voltage cut off and every time I’ve left it on at least one cell in the lipo is permanently damaged.
In the telemetry case, it’s designed to run absolutely a long s as possible because the cost of a (interchangeable) battery is small compared to the cost of the rocket and telemetry payload.
I’m not a battery expert, but I’ve left lipos in computers and phones on chargers for years without substantial/excessive deterioration relative to their number of charge/discharge cycles; my experience with the telemetry makes me more wary of full discharge as a cell damage condition (not a direct analog as the deck certainly shuts down before lipo cell death)
—-I should point out that I’m not terribly worried about battery damage - that’s a red herring. I’m just pissed when I grab my deck and its battery is dead and I was hoping to squeeze in a quick game. :-)
Below the 3.0 volt limit will reduce usable cycle count by 30-80% Everytime the cell drops that low. Charging over 4.1 will reduce usable cycle count as well.
Example # of usable cycles if you stop discharge at 3.2 and stop charging at 4.0 for modern lipos can be 5000-10000 cycles.
Charging to 4.3 every cycle (phone batteries are rated to 4.3 not 4.2… it’s why they have the larger than expected wh capacity numbers) will reduce that to 500.
Discharge it to 2.5 and you will get 10-50 cycles.
For those who are just looking at the SD or their phones… Most devices report 0% at 3 or 3.1v and 100% at 4.3 or 4.2 volts… So basically discharging to 0% doesn’t matter… It’s the charging to 100% that matters to most people.
If you charge to 100% you will get about 500 charges (it doesn’t matter what the % is you start at is… 90% -> 100% is the same one cycle as 20% -> 100%). That’s about two years of use for most people before your battery starts to suffer and you will see noticable decrease in battery life.
If you charge to 70% you will get about 10 years before you will see a drop in battery life. 80% will get you about 6-8 years.
woelkchen@lemmy.world 10 months ago
What’s broken is specific drivers and BIOS. Both are in the hands on Valve with their own device. Using 16GB for a copy of the RAM ob the 64GB model when a good chunk of capacity is already used for SteamOS, would mean that there is basically nothing left to install any games.
ErwinLottemann@feddit.de 10 months ago
it could be made optional and unavailable if there is not enough space