Configure persistent Wi-Fi Direct PC identity - #11286
Open
alchemy wants to merge 2 commits into
Open
Conversation
alchemy
marked this pull request as ready for review
September 11, 2026 08:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Give Omarchy PCs an explicit, persistent Wi-Fi Direct device classification. Set
device_type=1-0050F204-1(computer / PC) in a P2P configuration loaded through wpa_supplicant's-moption, so the classification is restored when the service starts. This gives peers a consistent description of the source device across applications using that supplicant instance and across service restarts.The device type has a general role in Wi-Fi Direct discovery: upstream exposes the primary device type in discovered peer information, and its P2P discovery API supports requesting particular device types. Consequently, advertising the correct class can matter to peer classification and discovery filtered by device type, beyond screen sharing. Improvements for other receivers or applications are plausible implications of that mechanism, but have not been tested here.
LG Screen Share motivated the investigation and provides the confirmed use case: on an LG OLED55B9PLA, advertising the PC identity made Miracast sharing open full-screen automatically instead of in a window. The result was confirmed again after restarting wpa_supplicant.
Install the tested PC identity setting as
wifi-direct-pc.conf, loaded by the50-wifi-direct-pc.confsystemd drop-in. The generic filenames describe the Wi-Fi Direct PC identity independently of the application using it. Fresh hardware setup and an idempotent migration share one setup leaf. Only Arch's stock service is augmented: existing configuration, custom ExecStart flags (including an existing-m), replacement units, and masked services are preserved and receive manual integration guidance. Unrelated service settings remain intact.Activation is deferred until reboot so an update does not disconnect Wi-Fi. To activate immediately after installation, run
sudo systemctl daemon-reloadandsudo systemctl restart wpa_supplicant; the restart temporarily interrupts Wi-Fi and any active Wi-Fi Direct session.Validation:
git diff --checkpass. The focused Wi-Fi Direct tests were rerun successfully after renaming the configuration files and updating the-mpath../test/all: CLI suite passed; 230 of 237 shell test files passed, including the new Wi-Fi Direct suite. Failures outside this change:config-test.sh,snapper-test.sh, andunowned-system-paths-test.shrequire the missing siblingomarchy-pkgscheckout;locate-test.shfails with a UnicodeDecodeError;launch-about-test.shfails its roomy-window animation assertion;runtime-smoke-test.shreports duplicate widget IPC handlers;screenshot-sanity-test.shreports that omarchy-shell is not responding. These failures were not repaired as part of the network configuration change.