A notification is posted when the system storage gets too low.
Currently, it redirects into the Storage Settings. Instead,
it should redirect into the Deletion Helper to directly let the
user clear out their storage.
Bug: 29437277
Change-Id: I4e35adf300d5e479d4171f1e6f090f2a757400f2
In order to attribute storage savings, we log how much data has
been freed and the last time that the automatic storage manager
has run.
Bug: 29643106
Change-Id: Ibb57b44b5e7550d4ab11e95b47db2f5d6599a96f
Provide persistable state for cell radio
to handle airplane mode similar to any
other radio in the system.
Change-Id: I87398fe84de3f6a10b0e1002e9e5bf7e61f9441f
We send a handle to the generation tracker along with the first accessed
setting but don't send the generation id of when the setting was
actually looked up. So by the time the client gets the setting with the
generation tracker from which to get and cache the last generation the
setting may have changed. We need to pass the generation id along with
the value and the generation tracker.
bug:29458487
Change-Id: I0ac4955ba5b10b547f8fe653a7c28e048a4691eb
Use the new API that contains multiple hash prefixes and a mask. Also
do some small refactoring necessary to handle multiple prefixes and
use a common implementation of the hash generation
Change-Id: Ib52f767ea6aadc30c67c5bdee949e9f9c5f04e44
This flag is used to set how many days of storage the automatic
storage manager will retain when clearing data.
Bug: 28965462
Change-Id: I87afafb7d3252d8c390ea43b7c45fd923f911e4e
1. Added config_supportSystemNavigationKeys to config and symbols
2. Added SYSTEM_NAVIGATION_KEYS_ENABLED to Settings.Global
3. Updated PhoneWindowManager to check for the system navigation keys enabled
flag before expanding or collapsing the notification panel.
Bug 29120082
Change-Id: Ia73078520474ce5a1cbf2256c0d793ed74bbf589
am: d958f83a01
* commit 'd958f83a017dde230203d91c8daedf36d40c22a6':
make the notification enqueue rate threshold a setting
Change-Id: I5172c1a0f0832f3b93d05f0ab7b7b1ab7233d334
am: 43c3a7e5a7
* commit '43c3a7e5a781640b862cf6f51805b3823f46fd02':
make the notification enqueue rate threshold a setting
Change-Id: I3e8c37aead7e1f2d5dc9fc89b72f82294bd16cfe
am: 912e2b2c80
* commit '912e2b2c80ba7641f649ae7e130d9febc4caac44':
Add support for source-specific VVM state in VoicemailContract
Change-Id: I0d0555fc9d2d4dfcee9a8cfb29acfe3a109be094
Negative values of the field CONFIGURATION_STATE, DATA_CHANNEL_STATE,
NOTIFICATION_CHANNEL_STATE is reserved to voicemail source for its'
specific errors. SOURCE_TYPE can be set to help interpret the error
codes.
Typically the OMTP visual voicemail source will set SOURCE_TYPE to the
same value of visual voicemail type set with
CarrierConfigManager.KEY_VVM_TYPE_STRING, such as "vvm_type_omtp".
For example, the OMTP visual voicemail source could set
CONFIGURAITON_STATE to -5 and SOURCE_TYPE to "vvm_type_foo", and the
client can find -5 for "vvm_type_foo" means "PIN is not set by the user"
+ Field SOURCE_TYPE
+ Docs to specify negative values are reserved for the source
- Removed hidden helper method SetStatus() and SetQuota(). The 'ignore'
value is conflicting with reserved values.
Bug:26944391
Change-Id: I0930f684dadd25ae94e3ea68a7658c7ae423e3e3
We now have a new settings key that provides all of the existing
tuning parameters, plus some newly redone ones for dealing with
different memory levels.
Changed the minimum batching for overall jobs from 2 to 1, so
we will never get in the way of immediately scheduling jobs
when the developer asks for this. We should now be able to rely
on the doze modes to do better batching of jobs for us when it
is really important.
Also work on issue #28981330: Excessive JobScheduler wakeup alarms.
Use a work source with scheduled alarms to blame them on the app
whose job they are being scheduled for, and add a check for whether
a job's timing constraint has been satisfied before considering it
a possible candidate for the next alarm. (If it is satisified,
the time is in the past, so we should not schedule an alarm for it.)
Finally clean up a bunch of the dumpsys output to make it easier
to understand.
Change-Id: I06cf2c1310448f47cf386f393e9b267335fabaeb
am: 8c8ea506d9
* commit '8c8ea506d91db44de1d312612a8f63ab107af799':
Allow apps to bypass Power Save restrictions when launched from a Notification's PendingIntent.
Change-Id: Iaffe5981b299eca5756666bd03c67a84c8e15283
am: efa291a860
* commit 'efa291a8605e91d775faf46ada349ec7f81fcdb9':
Allow apps to bypass Power Save restrictions when launched from a Notification's PendingIntent.
Change-Id: I11bf96280ac5e143d5260cb20238da38b4e0eaa3
am: efa291a860
* commit 'efa291a8605e91d775faf46ada349ec7f81fcdb9':
Allow apps to bypass Power Save restrictions when launched from a Notification's PendingIntent.
Change-Id: Ibd09b082140b66d25bd8583040761581bb20af76
This scenario typically happens when the device is on Doze Mode and a
notification action is triggered from a Wear device.
In a nutshell, the workflow is:
- ProcessRecord has a flag telling whether a process has "whitelist
management" privileges.
- When NotificationManager binds a new NotificationListenerService, it
sets the BIND_ALLOW_WHITELIST_MANAGEMENT flag.
- On bind(), ActiveService asserts that only system apps can set that
flag.
- On computeOomAdjLocked(), ActivityManagerService sets the
ProcessRecord flag if necessary.
- Upon creating a notification, NotificationManager calls AM to mark its
PendingIntents as coming from a notification.
- When PendingIntentRecord sends it to the target, it checks if it's
from a notification and if so calls AM to do the temp whitelist.
- On unbind(), ActiveService removes the ProcessRecord flag if necessary.
Fixes: 28818704
Change-Id: I00d46036a2cbb73f7f733fd35bf0b743a02807a1
am: b03e7217f3
* commit 'b03e7217f3fa3144f69119a4e109cce934d6065a':
Fix system locale propagation during user creation.
Change-Id: I6955bad489926525f6b50709bcf14b829ca9392d
am: ce9f5e3657
* commit 'ce9f5e3657b7a8fb68c6c65a2cd5a27eaf556cc8':
Fix system locale propagation during user creation.
Change-Id: If31dcbe28d108ec12aa9f4aef4382dcb2da90aaf
am: ce9f5e3657
* commit 'ce9f5e3657b7a8fb68c6c65a2cd5a27eaf556cc8':
Fix system locale propagation during user creation.
Change-Id: I020babcf2ce1aa632099457f2baf3497f5ac2946
