frameworks-base

Fork

Merge remote-tracking branch 'cm/cm-13.0' into cm-13.0-x86

Merge remote-tracking branch 'x86/marshmallow-x86' into cm-13.0-x86

fd_utils: fix DEBUG mode booting issue

Remove the "/android/" prefix before the white list checking.

Suggested by Chris Vandomelen <chris@sightworks.com>.

Android 6.0.1 release 74
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEABECAAYFAlgczssACgkQ6K0/gZqxDngq9wCdHv6RKynT3mm2Vll1EXgDnUb5
6SUAn3zCdEse9JCp57B457LkzKtbbY/o
=VDQb
-----END PGP SIGNATURE-----

Merge tag 'android-6.0.1_r74' into marshmallow-x86

Android 6.0.1 release 74

StatusBarIconView: Enable notification icon count by default

This used to be enabled by default in previous releases.

Change-Id: I24766bed58d081a0dd4763b9602379ff6435e092

SettingsProvider: Remove def_notif_count overlay

This is no longer used.

Change-Id: Ifd8eaa1d9d1f156dbfa4fdf278f95213ee32271e

Automatic translation import

Change-Id: I251ee7b9d1508a91692a8a8c1ba863730fcf125b
Ticket: -

Fix "Error parsing XML: not well-formed"

frameworks/base/packages/SystemUI/res/values-zh-rTW/cm_strings.xml:65: error: Error parsing XML: not well-formed (invalid token)

Change-Id: Ic29b77776c48d4a663656bf6ea40c8c4f0253414

Automatic translation import

Change-Id: Ic49d5ed34f92ca0298510b6ca8a3a279a0ea6e4d
Ticket: -

Automatic translation import

Change-Id: Icd3adceb4cfd523f56b7072934a037a203fd0b81
Ticket: -

Automatic translation import

Change-Id: I7eff0ec212cba24f97f35bddf3310e39b5fd1ce6
Ticket: -

Automatic translation import

Change-Id: I86e57b89e58d2cf5985e62b8d582f49285c265f3
Ticket: -

Automatic translation import

Change-Id: I53e8f93c43ddb93433c81d457e9721c0fff07b81
Ticket: -

DO NOT MERGE) ExifInterface: Close the file when an exception happens

CYNGNOS-3312
Bug: 32068647, Bug: 30936376
Change-Id: I22fa2384348c890ca726d2b1632cd54e59d25a8f
(cherry picked from commit cb17930077de640411407636eebc000e2d06dd9c)
(cherry picked from commit 2c79cada8897dcb171b8227b4ea91c292400702f)

DO NOT MERGE Isolated processes don't get precached system service binders

More specifically, they get a PackageManager binder -- necessary for
Android process startup and configuration -- but none of the other
usual preloaded service binders.

CYNGNOS-3312
Bug 30202228

Change-Id: I3810649f504cd631665ece338a83d2e54d41ad05
(cherry picked from commit 2c61c57ac53cbb270b4e76b9d04465f8a3f6eadc)
(cherry picked from commit f4d23f30c92bc80808f57677caab0282c8d28dc6)
(cherry picked from commit 9357830a380c8174ce5130941a7a53915d680819)

Automatic translation import

Change-Id: If3346af7ccc0e84d99d03b1c50f6b9e413d984b7
Ticket: -

Support for MODE_ASK in commandline

Change-Id: Idaf46295aff58259c786de4a4fef9c475c363cff

AppOps: Do not prune apps that are not present

Do not prune apps that are not currently present in the device (like
USB memory ones). While booting, they are not available but must not
be purged from AppOps, because they are still present in the Android
app database.

Issue-Id: CYAN-2811
Change-Id: I6680cbdf0022812b45d966dffee754399e92accb
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>

Automatic translation import

Change-Id: Ic80541e78c8570809868ce067a5176acb9d6a5a2
Ticket: -

Automatic translation import

Change-Id: I38a02ada64c66994c99ba5aee59a522931227337
Ticket: -

Themes: Don't cache explicitly themed resources

When a nav bar should be unchanged in the process of
customization(like changing icons,fonts)
the nav bar changes due to explicitly caching themed
resources.

Change-Id: I3135fac9df82a0551879908f6bf24deba0da0339

Build: use UserHandle.isApp for M compatibility

Change-Id: Ie4511c547d9afe2697e1ac3519f41a9b19784f18

Make Build.TYPE and Build.FINGERPRINT consistent for apps.

Some apps (namely Android Wear) like to do comparisons between TYPE and
FINGERPRINT and throw errors on inconsistencies. As our fingerprints are
almost always taken from stock ROMs, they don't really match our builds,
causing said comparisons to fail. Avoid those failures by taking build
type out of fingerprint for apps.

Change-Id: I8e8db64de7ea224572ecb3695c85abea91e0e29f

Print more switch events

Zygote: Add CAP_WAKE_ALARM to system_server to properly support timerfd alarms

The when the timerfd alarm logic was added to the kernel, an oversight was made
and the interface does not check for the CAP_WAKE_ALARM permissions as required
via other kernel methods to trigger an alarm timer.

In v4.8-rc kernels, the change 2895a5e5b3a ("timerfd: Reject ALARM timerfds
without CAP_WAKE_ALARM") was added by Eric Caruso <ejcaruso@google.com>.

After this change (which may be backported to -stable), the AlarmManager will
fail on the first timerfd_create call, and will not be able to set the time
or handle other necessary functions.

The solution here is to add CAP_WAKE_ALARM to the system_server process.

Change-Id: Ifdb16f3ef42711e553f727165de3922d484b5be4
Signed-off-by: John Stultz <john.stultz@linaro.org>

zygote: Allow device to append extra whitelisted paths

Change-Id: Ic5b056d7ead520da8648db9be28e16a81ec27c73

SettingsLib: Fix possible NPEs

getText() can return null, resulting in a NPE when trying to call
toString(). Add a null check to prevent this.
Additionally add a null check for packageInfo, as this can also be null.

Change-Id: Ia76326522872f4de4702ef56640b2f7b357c2bb7
Reference: BugDumps 20161104-10 L#135

zygote: Add /proc/ged to the FD whitelist

This is used by some platforms' gfx stack

Change-Id: Ife6e1b0df30fc23eff7fb6a16ff95c3e7b16a9c7

frameworks/base: Addition of Changes for ZeroBalance feature

--Addition of code to receive broadcast from ZeroBalanceHelper
application for executing command to write block/unblock
rule to Iptable.
--Addition of ZeroBalanceHelper file to be accesible by other
modules to notify ZeroBalanceHelper application about update
on change of SIM balance.
--Addition of rule to allow browser uid when rest all applications
are in blocked state.
--Addition of feature flag to control the zerobalance feature.

CRs-Fixed: 927258

Change-Id: Ifdf4c46fd63ab78193047a9bc8b62bf41065a665

NotificationManager: Concentrate LED light capabilities at a single location

We had(have) a bunch of individual boolean toggles for various LED behaviors
and combinations, which end up getting used as a similarly sprawling bunch
of getResource() calls across various locations. And they keep piling up...

So... create a new overlayable array of LED capabilities (config_deviceLightCapabilities)
where we can throw everything (and expand in the future). Also, create a
helper to abstract usage of the old (multi-resource) and new (single resource
array) formats to avoid breaking any deployed devices.

Change-Id: I7d627914b058861048071fc15776031c4152157f