Repository navigation
Releases
Releases · rozx/DockSense
DockSense v0.3.3
DockSense now starts right at sign-in instead of up to a minute and a half later, so a PC that was docked or undocked while it was off no longer sits in the wrong mode's setup first.
Changed
- Start with Windows starts DockSense right at sign-in. Windows runs its startup apps late: on the Ally X, DockSense was started 36 seconds after sign-in when booting into the Xbox full screen experience, and 83 seconds after sign-in on the desktop. Start with Windows now also registers a sign-in task in Task Scheduler (
DockSense-<your user ID>, no admin rights needed) that starts DockSense about two seconds after sign-in, before the Windows shell is up. The power plan and the rest of the profile are in place that much sooner.- Existing installs get the task the next time DockSense runs. Turning Start with Windows off removes it.
- The startup entry stays, and Windows' own switches for it still decide: when the entry is switched off in Task Manager or Windows Settings, the task does not start DockSense either.
- If the task is missing or disabled, DockSense starts as before, and Settings says that it starts late.
- This early the taskbar does not exist yet, so the tray icon appears a few seconds after DockSense has started working. Programs that a profile starts together with DockSense, and notifications, wait until about 20 seconds after sign-in, when the desktop is there.
- The full screen experience setting is applied before Windows reads it. Windows decides once, when the shell starts, whether to boot into the full screen experience. If you shut down as a handheld and switched on docked to an eGPU, it booted into the full screen experience and DockSense left it again almost a minute later. DockSense now writes the current mode's setting as the very first thing it does at sign-in. If Windows was quicker anyway, DockSense switches about 20 seconds after sign-in, provided the mode's profile has switch immediately on.
- Restart for a mode also prepares the full screen experience. Restart for Handheld (or Docked, or eGPU) in the tray menu now stores that mode's sign-in setting along with its iGPU memory size, so Windows comes back up the way the mode wants it.
- When DockSense starts later than 20 seconds after sign-in, it no longer waits another 10 seconds before switching the full screen experience.
- The diagnostic report shows the sign-in task and the sign-in time.
What's Changed
Full Changelog: v0.3.2...v0.3.3
DockSense v0.3.2
Switching modes with a different iGPU memory size now takes one restart instead of "unplug, wait, then restart".
Added
- Restart for a mode, from the tray menu. When another mode's profile uses a different iGPU memory size than the one in effect, the tray menu offers Restart for Handheld (8 GB) (or Docked, or eGPU). After you confirm, DockSense stores that mode's size in the firmware and restarts Windows. Plug in or unplug the dock or eGPU while the PC restarts, and it comes up in the new mode with the right memory already in effect.
- The entry only appears when a restart is really needed. A mode whose size is already in effect is not listed.
- If the PC comes back up in the old mode after all, DockSense puts that mode's size back and tells you, as before.
- If Windows does not restart after all, because an app with unsaved work held it up or you cancelled there, a notification says that the new size is waiting for a restart.
- Restart now button on the iGPU memory notification. When you have already switched modes and a new size is waiting for a restart, you can restart straight from the notification instead of opening DockSense first.
Changed
- The iGPU memory notification disappears once no restart is pending any more, for example after the restart or when you go back to the mode the PC started in. A leftover notification's button never restarts the PC when there is nothing to apply.
What's Changed
Full Changelog: v0.3.1...v0.3.2
DockSense v0.3.1
Fixed
- USB drives and memory cards no longer trigger a mode re-check. Windows reports every drive that is plugged in, removed or formatted to all app windows, and DockSense took those reports for a monitor or graphics card change. The mode never changed because of it, but each one caused a needless re-check and a misleading "display adapter or monitor" line in the log. DockSense now reacts only to display adapters and monitors, and the log says which of the two arrived or left.
What's Changed
Full Changelog: v0.3...v0.3.1
DockSense v0.3
This is the first version that can update itself. If you are on 0.2.1 or older, install 0.3 by hand once: download the zip and replace DockSense.exe. Later versions arrive through DockSense.
Added
- Updates from inside DockSense. Once a day DockSense asks GitHub whether a newer release exists (Settings → Updates; it can be turned off). By default it tells you with a notification and a card on the Status page, and Install update downloads the release, checks it and restarts DockSense. With Install automatically, the release is downloaded in the background and installed the next time DockSense starts, never while it is running.
- The download is only taken from this repository's releases, and its size and SHA-256 must match what GitHub publishes for the release.
- Restarting for an update keeps the mode and power plan, and does not run profile programs or switch the full screen experience again.
- If DockSense is in a folder you cannot write to, such as Program Files, Windows asks for administrator approval for the file swap, and automatic updates wait for your click. The approved step checks the download against GitHub once more by itself.
- Updating while automatic switching is paused keeps it paused.
- New
updatessetting inconfig.json:Off,Notify(default) orAutomatic. - Start with Windows tells you when it won't work. The switch now shows what really happens at sign-in, and a note under it says why when DockSense will not start: Windows switched the entry off (Task Manager, or Windows Settings → Apps → Startup), the entry starts another copy of DockSense, or Windows holds DockSense back until you switch to the desktop when it boots into the full screen experience. Turning the switch on fixes the first two.
- The diagnostic report shows the startup state, the update setting and whether the install folder is writable.
Fixed
- On PCs without the Xbox full screen experience, 0.2.1 created its settings key when Start with Windows was on, and DockSense then treated the full screen experience as available. DockSense no longer creates the key, and removes it again when it holds nothing but what DockSense wrote.
What's Changed
Full Changelog: v0.2.1...v0.3
DockSense v0.2.1
Fixed
- Start with Windows now works when Windows boots into the Xbox full screen experience. Windows holds startup apps back until the first switch to the desktop, so DockSense was not running in Handheld mode after a restart. DockSense now marks its own startup entry as Start at log in (the per-app choice under Windows Settings → Apps → Startup). Existing installs are updated the next time DockSense runs.
What's Changed
Full Changelog: v0.2...v0.2.1
DockSense v0.2
Added
- Switch the Xbox full screen experience right away when the mode changes, not only at the next sign-in (Mode profiles → Switch immediately). It uses the Windows gaming experience API, so no keyboard shortcut is simulated. DockSense never enters the full screen experience live when Windows is set to restart the PC to do so. A separate Exit when leaving this mode option leaves the full screen experience when you switch away from a mode, unless the new mode's own setting decides otherwise.
- Power plans page. Create a plan from any existing plan, rename and delete plans, and edit the plugged-in and on-battery values of the settings that matter on a handheld: minimum and maximum processor state, energy performance preference, boost mode, maximum frequency, core preference on hybrid CPUs, and display and sleep timeouts. Each plan shows its type, whether it is active, which modes use it, and whether the Game Mode throttle affects it.
- Run programs on mode changes. Each mode profile can start programs, scripts or URLs when the mode begins or ends, or when DockSense starts in it. Arguments, a hidden window and administrator rights are supported, PowerShell scripts (
.ps1) run with Windows PowerShell, and Test starts an entry right away. A notification says which program started and why; you can turn it off under Settings → Notifications. - iGPU memory per mode on ASUS handhelds whose firmware offers it, such as the ROG Xbox Ally X. DockSense stores the size through the same ACPI interface Armoury Crate uses, and only writes sizes the firmware lists. It applies at the next restart: Status shows the pending size with a Restart now button, and a notification tells you. DockSense never restarts by itself.
- When you start DockSense yourself, a notification says it is running in the background, with the current mode and power plan. It doesn't appear when DockSense starts with Windows (the Run entry now passes
--autostart, and older entries are updated automatically) or when the window opens anyway. You can turn it off under Settings → Notifications. - Status shows whether the full screen experience is active right now and the current iGPU memory.
- The diagnostic report lists every power plan with its type, the live full screen experience state and the iGPU memory options.
Changed
- Mode profiles can use hidden High Performance-type plans too, including plans created on the Power plans page.
What's Changed
Full Changelog: v0.1...v0.2