General: Show Auto Connect compatibility notice only when relevant#512
Merged
Conversation
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.
What changed
The Auto Connect setting description no longer includes the vague "May not work on newer Android versions" caveat. Instead, a dedicated info box appears below the setting when it is enabled on Android 12 or newer, explaining the restriction more clearly.
Technical Context
BluetoothHeadset.connect()API, which Android 12+ (API 31) blocks with aSecurityExceptiondue toMODIFY_PHONE_STATEenforcementSettingsInfoBoxcomposable (same pattern as the ear detection and popup info boxes on the same screen)reactions.autoConnect && Build.VERSION.SDK_INT >= Build.VERSION_CODES.S— a static SDK check rather than the runtimeisNudgeAvailableflag, so users see the warning before their first failed attempt