-
-
Notifications
You must be signed in to change notification settings - Fork 75
add patch level warning settings #332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
inthewaves
wants to merge
128
commits into
GrapheneOS:15-qpr2
Choose a base branch
from
inthewaves:expiration-warning
base: 15-qpr2
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
1db09e3
to
8d379fa
Compare
This uses the standalone wallpaper picker class from WallpaperPicker2 as seen in the Pixel stock ROM.
The NFC preference in Settings -> Connected devices -> Connection preferences doesn't listen to changes from the NFC tile. (This wasn't an issue in Android 10, because there used to be a SwitchPreference that listened there.)
If no customization is needed, BoolSetting base class can be used directly from XML by adding settings:boolSettingField="<class name> <BoolSetting field name>" to the preference XML definition.
This preference controls the glove mode feature on Pixel devices for increased touch sensitivity without requiring a custom HAL or other device-side code. This is done by using the debug.touch_sensitivity_mode system property, which Settings has permission to change. The user-visible value is persisted in Settings.Secure, while the property is persisted in persist.vendor.touch_sensitivity_mode. Requires frameworks/base commit: "Add a config to state whether a device supports increased touch sensitivity." Requires device/google/* commit: "Express support for increased touch sensitivity." Closes: GrapheneOS#1 Co-authored-by: Diab Neiroukh <[email protected]> Change-Id: I86af721fde33226d314d8a44525f310828299a72
It's added to Private Space screen instead of the Apps screen (where regular and work profile links are) to avoid revealing whether the Private Space is present when the "Hide when locked" Private Space option is enabled.
Allow sorting applications by size in Settings->Apps just like in Settings->Storage/USB->Apps Change-Id: I9e022162110e1feff20f257992086e66735e0f5e
Signed-off-by: June <[email protected]> Co-authored-by: inthewaves <[email protected]> Co-authored-by: June <[email protected]>
"None" app picker option was invisible because this activity wasn't updated to support edge-to-edge.
There was a mismatch between checks in getContactSharingState() and setContactSharingState(), which led to contacts access being granted by default when the user accepted a background pairing request for a hands-free device, despite the contacts access toggle indicating that the contacts access will not be granted. Fix this check mismatch by removing the confusing setContactSharingState() method and switching code that depends on setContactSharingState() to use the value of getContactSharingState() instead.
Before this change, contacts access toggle was turned on by default in foreground pairing dialogs for hands-free devices.
There's a "Clear storage" button in App info > Storage & cache. When app implements a "manage storage space" activity, that button opens it instead of actually clearing the storage. "Manage space" activity might not provide an option to clear app storage or it might not work at all. This change adds a separate button to launch that activity and makes the "Clear storage" button ignore its presence.
It takes more than 5 seconds to load in many cases due to an upstream regression.
many carrier where 5G network options is available (in settings) doesn't really support standalone 5G and in that case setting it to 'NR/5G only' soft fails. it is disabled for NSA carrier, calling options will be broken on NSA (non standalone 5G).
…animation" This reverts commit cdfab94fdab8287e47e6a24bb1700a85ee250484.
8d379fa
to
6da3739
Compare
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.
Review and merge with GrapheneOS/platform_frameworks_base#126