ValveSoftware / ValveSoftware/SteamOS
[Safety] Travel Mode to prevent unintended wake, overheating, and potential thermal hazard inside the carrying case
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.6k
- Forks
- 83
- Avg merge
- 4m
- Merged PRs (30d)
- 3
Description
System Information
- Steam client version:
... - SteamOS version:
3.8.16 - SteamOS build:
20260716.1 - Kernel:
6.16.12-valve24.5-1-neptune-616-gb2f7cfe85e45 - BIOS version:
... - Opted into Steam client beta?: No
- Opted into SteamOS beta?: No
- Have you checked for updates in Settings > System?: Yes
Severity
Safety-critical / High priority
This is not only a battery-life or usability issue.
A Steam Deck that unexpectedly wakes or fails to remain suspended while stored inside a closed carrying case can continue operating under significant CPU/GPU load with severely restricted airflow.
Under these conditions, the device can become extremely hot while the user is unaware that it is running.
Because the Steam Deck contains a high-capacity lithium-ion battery and can reach very high internal temperatures under load, I believe this scenario should be treated as a potential thermal and fire safety hazard, not simply as an inconvenience.
I am not claiming that a Steam Deck fire has occurred in my case. The concern is that the current design allows a realistic failure sequence in which a high-power device can continue operating unattended inside an enclosed, insulating carrying case.
Problem
Steam Deck currently has no mechanism to detect that the device has been placed inside its carrying case.
Unlike tablets and laptops that can use a lid sensor, magnetic cover sensor, or similar hardware mechanism to enter a protected low-power state, placing a Steam Deck inside the official carrying case does not change the device's power or wake behavior.
This becomes particularly concerning because suspend/wake behavior is not always perfectly reliable.
There have already been SteamOS reports where Steam Deck devices unexpectedly wake from suspend, including cases where users found the device extremely hot after it had been stored in a bag or case.
Related examples include:
#2019— Steam Deck randomly wakes by itself#2645— Disable Bluetooth wake when not charging#1531— Fan stops working and device overheats#2475— Fan fails to resume after sleep, temperatures approaching 99°C
Valve has previously confirmed that some unintended wake events were caused by Bluetooth wake behavior and reproduced the issue internally.
However, Bluetooth is only one possible wake source.
The broader safety issue is that there is currently no "safe for transport" state that guarantees the Steam Deck will remain asleep once it has been placed inside a closed carrying case.
Potential failure scenario
A realistic sequence is:
- The user is playing a demanding game.
- CPU/GPU load and device temperature are already elevated.
- The user presses the power button to suspend the Steam Deck.
- The screen turns off and the user reasonably assumes the device is asleep.
- The user immediately places the Steam Deck inside the official carrying case and closes it.
- Suspend either fails, or the device later wakes unexpectedly due to Bluetooth, USB, controller, firmware, driver, or another wake source.
- The previous game remains active or the system resumes into a high-power state.
- The user has no visible or audible indication that the device has resumed.
- The Steam Deck continues operating inside the closed carrying case.
- Intake and exhaust airflow are severely restricted by the case.
- Heat accumulates while the device continues drawing significant battery power.
- The user may not discover the situation until the device is extremely hot or the battery has been substantially depleted.
This is very different from normal high-temperature operation during handheld gaming.
During normal use, the cooling system has access to ambient airflow and the user can hear the fan, feel the temperature, see the screen, or react to abnormal behavior.
Inside a closed carrying case, the device is effectively operating unattended in an enclosed thermal environment.
Why this should be treated as a safety issue
The concern is not merely:
"The battery drains too quickly while sleeping."
The more serious concern is:
A high-power handheld computer can unintentionally remain active or wake while fully enclosed inside a carrying case, with restricted airflow and no user awareness.
Steam Deck hardware can operate at high CPU/GPU temperatures under sustained load.
Related SteamOS reports have documented temperatures above 90°C, including cases approaching approximately 99°C when fan control fails after resume.
Those temperatures may be within or near hardware protection thresholds when the device is operating in open air, but the risk profile changes when the entire device is enclosed inside a carrying case.
The carrying case:
- restricts airflow around the intake and exhaust
- retains heat around the chassis
- prevents the user from noticing abnormal fan behavior
- prevents the user from feeling temperature rise immediately
- allows the device to continue consuming battery power unattended
The Steam Deck also contains a large lithium-ion battery.
Any scenario that combines:
- sustained high electrical power
- elevated internal temperatures
- restricted ventilation
- unattended operation
- and a lithium-ion battery
deserves additional safety protection.
Even if existing thermal throttling and shutdown protections prevent immediate hardware damage in most cases, relying exclusively on thermal shutdown should not be the primary safety mechanism for a device designed to be routinely transported inside an enclosed case.
A thermal shutdown is the last protection layer.
The system should prevent the unsafe operating state from occurring in the first place.
For this reason, I believe unintended wake while enclosed should be considered a potential thermal/fire safety hazard and treated with higher priority than a conventional suspend or battery-drain bug.
Current design gap
The official carrying case naturally creates an expectation that:
Once the Steam Deck has been suspended and placed inside the case, it is safe to transport.
At present, that assumption is not guaranteed by either hardware or software.
There is no equivalent of:
- laptop lid detection
- tablet magnetic cover detection
- transportation lock
- deep sleep lock
- all-wake-source disable mode
The user must simply trust that suspend succeeded and that nothing will wake the device later.
That is particularly problematic because unintended wake bugs have already occurred in SteamOS.
Suggested solution: Travel Mode / Carrying Mode
Please consider adding a dedicated: Travel Mode or Carrying Case Mode
When enabled, this mode should place the Steam Deck into a transport-safe suspend state.
Suggested behavior:
- Disable Bluetooth wake
- Disable controller wake
- Disable USB wake where possible
- Disable network wake
- Disable nonessential external wake sources
- Disable wake events that are not explicitly user initiated
- Prefer deeper suspend behavior while on battery
- Detect suspend failures
- Warn the user clearly if the system cannot safely enter suspend
- Automatically return to suspend if an unexpected unattended wake occurs
- Optionally require the physical power button to resume from Travel Mode
The UI could provide a clear confirmation such as:
Safe for travel — external wake sources disabled
This would give users confidence that the Steam Deck can safely be placed inside the carrying case.
Simpler software-only solution
If a full Travel Mode is not feasible, a simpler option would still significantly reduce the risk:
Disable all external wake sources while running on battery
with an optional user override.
For example:
-
On AC power / docked:
- Bluetooth controller wake can remain enabled.
-
On battery:
- Bluetooth wake
- USB wake
- controller wake
- other external wake sources
should default to disabled.
This is especially important because the primary reason to remotely wake a Steam Deck is usually when it is docked and connected to external power.
When operating on battery, unintended wake is much more likely to occur during transport.
Additional protection: unexpected wake detection
SteamOS could also detect suspicious wake behavior.
For example:
If the device:
- wakes while on battery,
- receives no physical user input,
- has no display interaction,
- is not connected to external power,
- and receives no meaningful activity for a short period,
SteamOS could automatically suspend again.
This would provide a second layer of protection even if a firmware or wake-source bug occurs.
Additional protection: suspend confirmation
The current interaction also makes it difficult for users to know whether suspend actually completed successfully.
The display turning black is not sufficient confirmation.
SteamOS could provide:
- a distinct suspend-complete sound
- LED behavior indicating successful deep suspend
- a "Safe to carry" indication before the screen turns off
- detection of failed suspend attempts
This would help prevent users from placing a still-running Steam Deck inside the carrying case.
Future hardware consideration
For future Steam Deck hardware revisions, Valve may also want to consider hardware-level carrying-state detection.
Possible implementations could include:
- magnetic case detection
- Hall-effect sensor
- lid/cover sensor
- proximity/contact sensor in the official carrying case
- another low-power physical transport-state mechanism
The principle would be similar to tablets with smart covers or laptops with lid sensors.
If the Deck detects that it is physically enclosed, the hardware/firmware could automatically disable external wake sources and enter a protected suspend state.
Expected behavior
Once a user intentionally suspends a Steam Deck for transport, the device should remain in a low-power, thermally safe state until the user explicitly resumes it.
Placing a suspended Steam Deck inside the official carrying case should never create a realistic possibility of the device silently resuming and continuing to run a demanding workload inside the closed case.
Actual behavior / Current risk
Today, the following is possible:
High-load game running
↓
User presses Sleep
↓
Screen turns off
↓
Steam Deck placed in carrying case
↓
Suspend fails or unexpected wake occurs
↓
Game / SteamOS continues running
↓
Device is enclosed with restricted airflow
↓
Temperature rises
↓
Battery drains rapidly
↓
User is unaware
This failure mode has already been partially demonstrated by existing unintended-wake reports where users found their Steam Deck unexpectedly running and very hot inside a bag or case.
The missing piece is a system-level protection that prevents this entire class of failure.
Request to Valve
Please consider treating this as a safety-related power-management issue rather than only a convenience feature.
Individual bugs such as Bluetooth wake can be fixed one at a time, but the underlying design problem remains:
There is no transport-safe state that prevents the Steam Deck from unexpectedly becoming fully operational while enclosed inside its carrying case.
A dedicated Travel Mode, or at minimum disabling external wake sources while on battery, would significantly reduce the possibility of:
- unintended battery drain
- severe heat accumulation
- thermal stress on the battery and components
- thermal throttling or emergency shutdown
- and, in the worst case, a potential thermal/fire safety event
For a portable device that is specifically designed to be carried inside a closed case, I believe there should be a stronger guarantee that once the user puts the device away, it cannot silently resume high-power operation without explicit user interaction.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or code entry points are named. Start by reviewing related issues #2019, #2645, #1531, and #2475, then clarify the scope of a transport-safe state and which wake sources it must cover. Done would mean a defined implementation that keeps the device safely suspended during transport and handles failed or unexpected wakes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100