forked from aosp-mirror/platform_frameworks_base
-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
NFC auto turn off #121
Open
mrxx0
wants to merge
414
commits into
GrapheneOS:15
Choose a base branch
from
mrxx0:nfc-auto-turn-off
base: 15
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
NFC auto turn off #121
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
…ystem_server side Don't require reboot or settings re-set for always on and lockdown to take effect on first vpn connection. The requirement for reboot, re-set at settings has been caused by a permission not granted or declared by VpnDialogs, which caused the unexpected behavior. Prevent this by checking the permission of local process instead.
In the general case, ContentProvider authorities can't be renamed because they aren't required to be based on the package name. Chromium always forms ContentProvider authorities by prefixing them with its package name, and relies on this invariant in code. When its package is renamed by original-package handling code, statements like String authority = context.getPackageName() + CONSTANT become invalid. Add a special-case for Vanadium to fix this.
This resolves the NPE crash when updating an application under the new package name that initially had the original package as package name.
This is needed for properly verifying updates of system packages.
13: 13fe843829ec
versionCode of many system packages, including privileged ones, is set to the current SDK version and is thus not incremented during non-major OS upgrades. This allowed to downgrade them to the older version that had the same versionCode.
Signed-off-by: June <[email protected]>
Signed-off-by: r3g_5z <[email protected]>
13: d93766fa56de Change-Id: I5ccc4d61e52ac11ef33f44618d0e610089885b87 Squashed with: Author: Daniel Micay <[email protected]> Date: Wed Mar 15 06:32:20 2023 -0400 simplify removal of SUPL IMSI / phone number This is not required for SUPL to work and the comment about Google is unnecessary.
13: 47eb7cbe1686
Adds a global data structure that is accessible by privileged installers and allows them to avoid installing the same package at the same time.
Applies to device PIN, SIM PIN and SIM PUK input screens.
This setting disables animations in keyguard PIN input UI.
This allows apps that have minor dependency on GSF/GmsCore (EuiccSupportPixel, Google Camera etc) to work without having any of GSF, GmsCore, Play Store installed. Gservices provider is currently hosted by GSF, soon to be hosted by GmsCore.
Depends on commit: "don't crash apps that depend on missing Gservices provider"
- isolate EuiccGoogle from all non-system package via AppsFilter, which stops it from sending data to Google through GmsCore. EuiccGoogle doesn't send data to Google directly - keep EuiccGoogle disabled by default, but do not disable it after each reboot - remove a misleading "device information will be sent to Google" message that appears before eSIM download
Google's LPA that is shipped on GrapheneOS handles requesting the Camera permission at runtime, which allows the user to give it a one-time grant. 13: 7bb7df2d2b13
Android Auto requires this broadcast to be sent to complete its initialization.
Build.getSerial() is protected with the very broad READ_PRIVILEGED_PHONE_STATE permission. Android Auto needs Build.getSerial() in some cases, but doesn't need most of the other privileges that READ_PRIVILEGED_PHONE_STATE grants.
It's better for this to be done in an explicit way.
OP_GET_ACCOUNTS wasn't spoofed unless the app had the WRITE_CONTACTS uses-permission.
This is needed for changing permission pre-grant type from regular to fixed, otherwise permission state won't be changed if permission was manually revoked by the user.
This is needed for apps that have a system-fixed notification permission pregrant, but didn't have it before. In that case, notification channel state for non-blockable channels will be frozen at its last value, i.e. such channels would be permanently blocked if they were blocked before app received the system-fixed notification permission.
Notification pregrant is now made by adding a permission pregrant XML in GmsCompat app repo.
See the corresponding change in GmsCompat repo.
When there's no added Google account, Play Store attempts to update GmsCore even if the google_play_store_system_component_update setting is disabled. Play Store always ignores GmsCore updates as of version 44.6 when GmsCore update owner is set to non-Play Store value.
It's used by the GmsCompat location service implementation.
462062c added an unconditional 10 second delay to ContentProvider change callbacks for all background apps as part of MediaProvider optimizations. This led to unexpected delays when changing SettingsProvider settings (android.provider.Settings) that are observed by background system packages.
e5c3caf
to
36e31c0
Compare
9d15b31
to
a3bc946
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.
NFC auto turn off feature, like for Bluetooth and Wifi
Not tested since NFC isn't available with emulator