- Layout of notif shade is no longer custom, so need to handle
insetsIgnoringVisibility on client.
- Do not special case Keyguard anymore. Just treat it as regular
control target.
- No more special sauce to hide navigation bar on Keyguard.
- Treat it as BEHAVIOR_SHOW_TRANSIENT_BARS_ON_SWIPE but don't
actually do that in DisplayPolicy
Test: InsetsPolicyTest
Test: Lockscreen with PIN
Bug: 118118435
Change-Id: I1edce4fdb792fd97a181165a03957ba5d6d3e551
As part of statsd becoming a Mainline module in R, autogenerated
StatsLog.write() calls are going away and replaced by
*StatsLog.java
that is autogenerated for each module.
This CL replaces some usages of StatsLog with
FrameworkStatsLog.
Bug: 145952197
Test: m
Change-Id: I7d92b833937037e075c7e53401367061901b3a6e
Notification instance IDs are generated by NotificationManagerService
when the notification is first posted, and stored in the
StatusBarNotification so that they can be passed to the SystemUI
process.
Bug: 144022566
Test: atest NotificationManagerService BuzzBeepBlinkTest RoleObserverTest
Test: statsd_testdrive 244
Change-Id: I804786dfa165864257d8801d7e96f2ac0ead960f
The former method required us to load each individual DeviceConfig
constant at startup time. This could easily lead to an issue where
someone forgets to add that line in the startup path and the value
isn't loaded. Switching to have all DeviceConfig constants read and
processed by a generic loop so we don't run into this issue.
Bug: N/A
Test: flash device and confirm DeviceConfig constants are loaded
Change-Id: I981829722cf035e894415a11e214724b213c65fa
When an app requests the special access permission to be able to manage
external storage, and it is denied, we need to kill the app, in order to
lose the external_storage gid it may have that allows it access to
unreliable USB OTG volumes.
When the app op is granted, we don't kill the app to pickup the new
gid because it may result in bad UX especially since that gid is only
useful to access unreliable USB OTGs that are rarely present.
The next time the app is restarted, it will get the external_storage
gid and will be able to access any mounted USB OTG volumes.
Bug: 144914977
Test: Copy paste of I73c5ce56ee24e5c864d7c9280b83fc3854701a97
Change-Id: I5cb13dc9c51cb8b4e942e529b4a1c7dac180cace
1. Moving Seal (back) to commit call as we no longer need it to be async.
2. Current states:
Stream/Validate/Commit - for Streaming installation might be entered multiple times while waiting for DataLoader to finish.
Install - renamed from Commit to avoid confusion with mCommitted.
3. Install still has to be a separate state to allow
setPermissionsResult.
Test: atest PackageManagerShellCommandTest
Bug: b/136132412 b/133435829
Change-Id: I6afcfeafabbf7e26906fcf5697c44c5617c9c1b5
As part of statsd becoming a Mainline module in R, autogenerated
StatsLog.write() calls are going away and replaced by
*StatsLog.java
that is autogenerated for each module.
This CL replaces some usages of StatsLog with
FrameworkStatsLog.
Bug: 145952197
Test: m
Change-Id: Ib36d010ca962904bbc905be7e832346d2c08cb2e
As part of statsd becoming a Mainline module in R, autogenerated
StatsLog.write() calls are going away and replaced by
*StatsLog.java
that is autogenerated for each module.
This CL replaces some usages of StatsLog with
FrameworkStatsLog.
Bug: 145952197
Test: m
Change-Id: I74f9614fc8866dd1c5875ee1b240c808613b8625
As part of statsd becoming a Mainline module in R, autogenerated
StatsLog.write() calls are going away and replaced by *StatsLog.java
that is autogenerated for each module.
This CL replaces some usages of StatsLog with FrameworkStatsLog.
Bug: 145952197
Test: m
Change-Id: Id3e0900a050441b9aef3ee6244759f5098afdfb1
As part of statsd becoming a Mainline module in R, autogenerated
StatsLog.write() calls are going away and replaced by
*StatsLog.java
that is autogenerated for each module.
This CL replaces some usages of StatsLog with
FrameworkStatsLog.
Bug: 145952197
Test: m
Change-Id: Ied4cad6550c99697003948a2639c74fba31f1fde
Create a new helper to deal with application foreground state changes.
1) Rename various Helpers.
2) Move GnssManagerService into location dir.
3) Use new AppForegroundHelper everywhere.
4) Move sendNiRequest to internal API
5) Some refactoring of NetInitiatedActivity
Test: atest AppForegroundHelperTest
Change-Id: Ifffe0e6a34452a18d017c6b190547b904d77b430
Make sure to use the handler if the caller is the system server
Test: Build / treehugger / manual code inspection
Change-Id: I0c9998511280193d785ebcf7aa501ee02c0a8548
Fix: 148230239
Previously this could work regardless of target SDK version, so for
compatibility it should still work that way.
Bug: 146386279
Bug: 136503238
Test: presubmit
Change-Id: I57729f0d35679afaf3a43dfac5cd42f488d78baf
Adds a new flag to ShortcutInfo to mark it as cached. Also adds new
APIs in ShortcutManager to remove or retrieve a cached shortcut.
Bug: 148084870
Test: atest com.android.server.pm.ShortcutManagerTest1 \
com.android.server.pm.ShortcutManagerTest2 \
com.android.server.pm.ShortcutManagerTest3 \
com.android.server.pm.ShortcutManagerTest4 \
com.android.server.pm.ShortcutManagerTest5 \
com.android.server.pm.ShortcutManagerTest6 \
com.android.server.pm.ShortcutManagerTest7 \
com.android.server.pm.ShortcutManagerTest8 \
com.android.server.pm.ShortcutManagerTest9 \
com.android.server.pm.ShortcutManagerTest10
Change-Id: I859b416ccd4228eec10a436550ff98866a62af66
An app can now have legacy storage access in 3 mutually exclusive
ways:
1. Targeting < Q
2. Targeting <=Q and explicitly requesting legacy access
3. Targeting <=Q and having the WRITE_MEDIA_STORAGE permission
In other words an app targeting R has no way to have legacy storage
access. Its only option is to request MANAGE_EXTERNAL_STORAGE access
Test: Verify via dumpsys the conditions above
Bug: 144914977
Change-Id: I3c868cd9b4da4083517dd64b3a3888aea4060f18
