fix(bluetooth): refresh discoverable state after scan - #155
Closed
liuhao-1997 wants to merge 12 commits into
Closed
Conversation
Serialize background Wi-Fi callbacks with LVGL, avoid synthetic Shift lock hints, and make Settings/shortcuts share live PipeWire volume in rounded 10 percent steps.
Prefer packaged JetBrains Mono SemiBold and render both ZClaw text roles at 14px, retaining the existing fallback chain.
Add antialiased compact text layout, bounded settings navigation, persistent optional UISFX feedback, and glyph-height fixes without adding a service or resident process.
…erzero-20260811-volume-zclaw
…urn off after a few minutes of' Scan '
…erzero-20260811-volume-zclaw
Collaborator
Author
|
Closing this PR; the change will be resubmitted from a clean branch. |
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
1 participant
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.
Refresh the Bluetooth Discoverable state after leaving the Scan view. Stop discovery first, query the current BlueZ status, and rebuild the Bluetooth submenu. No scan lifecycle or Bluetooth API behavior is changed.