Skip to content
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

Add allow input device toggle to bluetooth pairing dialog #214

Open
wants to merge 98 commits into
base: 14
Choose a base branch
from

Conversation

gmillz
Copy link

@gmillz gmillz commented Jan 14, 2024

Screenshot_20240120-113115

Evan Chen and others added 30 commits November 16, 2023 18:45
Fix: 282934003
Test: Run test app in work profile
(cherry picked from commit 81893c2)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:72f8ea55d38ab81524f54b666f8eebf3d4413f55)
Merged-In: I7fed6d1baa1a40e9126493d37e33d63236bb4b3c
Change-Id: I7fed6d1baa1a40e9126493d37e33d63236bb4b3c
 Add checks URIs for content from other users.
 Fail for users that are not profiles of the current user.

Test: atest DefaultRingtonePreferenceTest
Bug: 299614635
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:1876c449915c764242976280918758585689c82d)
Merged-In: Ib266b285a3a1c6c5265ae2321159e61e08e349f6
Change-Id: Ib266b285a3a1c6c5265ae2321159e61e08e349f6
…08425', 'googleplex-android-review.googlesource.com/24969251'] into udc-qpr1-release.

Change-Id: Ic2873946e9a04d9b0724162980df20cb91ed3e71
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 <lazerl0rd@thezest.dev>
Change-Id: I86af721fde33226d314d8a44525f310828299a72
add Sandboxed Google Play link for the work profile

The link is now dynamic and becomes hidden if GMS Core is uninstalled or
disabled.
Change-Id: Ia09dfd67bcfb8334439bfb9dab419235b182e297
Copy link

@DemiMarie DemiMarie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if success is false in onDialogDismissed? Should the default be CONNECTION_POLICY_FORBIDDEN, with the dialog being responsible for setting it to CONNECTION_POLICY_ALLOWED? In other words, should this be combined with GrapheneOS/platform_packages_modules_Bluetooth#20?

res/values/strings_ext.xml Outdated Show resolved Hide resolved
@gmillz
Copy link
Author

gmillz commented Jan 20, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet