(The check for whether the dialog had already been shown was
accidentally removed in change I1c1bd12.)
Bug: 5069310
Change-Id: I2ea35c5891667922e78d7919132ffe599411f851
Also, the panel is no longer buried below the screen edge
when there are no notifications.
Bug: 5115158
Change-Id: I01bc8a65ceebd64143a4c4c52d63641dc3cd1c77
In Japanese, the day of week should follow the date
Bug: 4606219
Change-Id: If385b3f9989bbe5f1b4bc21293d9be651e187c1f
Signed-off-by: Mike Lockwood <lockwood@android.com>
It was configuring this to have its width follow the display size
but height be a fixed amount. As a result, during a rotation we
would end up with a surface that is 800x712, which uses a lot more
memory.
The fix is to just always set the window to a fixed size, changing
it when the display size changes.
Also the expanded view was setting itself to use a hardware layer
for no reason -- it is a top view so there is no point in this,
and anyway it is doesn't even use hw rendering. This saves 1.5MB
of the layer bitmap.
This change also fixes the returned problem where the expanded
view would flicker when pulling it down in landscape.
Change-Id: If57420b0bc3fdc2706d2d3b36cb2d287b5fc9e27
* New "X" button appears in the system bar, allowing the
user to clear all notifications. Only appears when the
notifications list is showing and there are clearable
items. (Note: the textual button on phones has also been
replaced with an X.)
* Updated panel background artwork and positioning.
* Removed a bunch of old art.
Bug: 4970588
Bug: 4974043
Bug: 3509407 (regression)
Change-Id: Ibadb638cd18c4faa751cd1f311d73ceda65cb3ca
Nice to not load 4MB bitmaps in the system process.
Also, hey, with how we are now scrolling the surface instead of
the bitmap, there is no reason to keep that 4MB bitmap loaded in
to memory. So don't.
Unfortunately it looks like for some reason the VM is still
holding on to the bitmap. I'll need to figure out why. Later.
Change-Id: Ib3503756144502fc5c8d5e294248c2417c4fe8c8
When the "ongoing"/"latest" split is removed, this will be
replaced with something less odious.
Bug: 5090331
Change-Id: Ib804de66985ff5f5df2e1df3c85437a1e31f1c49
If the user has supplied a backup password in Settings, that password
is validated during the full backup process and is used as an encryption
key for encoding the backed-up data itself. This is the fundamental
mechanism whereby users can secure their data even against malicious
parties getting physical unlocked access to their device.
Technically the user-supplied password is not used as the encryption
key for the backed-up data itself. What is actually done is that a
random key is generated to use as the raw encryption key. THAT key,
in turn, is encrypted with the user-supplied password (after random
salting and key expansion with PBKDF2). The encrypted master key
and a checksum are stored in the backup header. At restore time,
the user supplies their password, which allows the system to decrypt
the master key, which in turn allows the decryption of the backup
data itself.
The checksum is part of the archive in order to permit validation
of the user-supplied password. The checksum is the result of running
the user-supplied password through PBKDF2 with a randomly selected
salt. At restore time, the proposed password is run through PBKDF2
with the salt described by the archive header. If the result does
not match the archive's stated checksum, then the user has supplied
the wrong decryption password.
Also, suppress backup consideration for a few packages whose
data is either nonexistent or inapplicable across devices or
factory reset operations.
Bug 4901637
Change-Id: Id0cc9d0fdfc046602b129f273d48e23b7a14df36
View.setSystemUiVisibility() now properly accepts a
bitfield, including:
* SYSTEM_UI_FLAG_LOW_PROFILE: "lights out mode"
(previously known, erroneously, as STATUS_BAR_HIDDEN)
* SYSTEM_UI_FLAG_HIDE_NAVIGATION: for when you need every
single pixel on a device that also has a navigation bar
These flags are painstakingly aggregated across the entire
view hierarchy and carefully delivered to the status bar
service, which in turn gently passes them along to the bar
implementation.
To really get access to the whole screen, you need to use
HIDE_NAVIGATION in conjunction with FLAG_FULLSCREEN and
FLAG_LAYOUT_IN_SCREEN. See development/samples/Overscan for
an example of how to do this.
Change-Id: I5fbfe009d9ceebbbf71db73f14a7008ea7c1d4da
Teach NetworkPolicy limits to "snooze" when requested by user, and
notify with both dialog and notification. Register for network alerts
through NMS to trigger updates immediately instead of waiting for
next stats update.
Enforce that all NetworkPolicy are unique on a template basis, and
move SCREEN_ON/OFF broadcasts to background thread. Launch SystemUI
and Settings directly instead of using actions, and include full
NetworkTemplate in extras.
Tests to verify notification and snooze behavior.
Bug: 5057979, 5023579, 4723336, 5045721
Change-Id: I03724beff94a7c0547cb5220431ba8d4cd44d077
Otherwise the value would be left at zero since we are inserting
the database record before writing the file
Bug: 5064246
Change-Id: I54be6ff14a7f170994aaf586aaddb06c5b746e89
Signed-off-by: Mike Lockwood <lockwood@android.com>
