Use icon size from resource instead of hardcoded

See merge request !36

Change-Id: I665f52c7a04bee33dc6b93c34a333f049261deda

Pie new settings icon

See merge request !32

Change-Id: Ia6c6ca49a2300c24e245019420b9d512bc12bee4

Merge tag 'android-9.0.0_r56' of https://android.googlesource.com/platform/packages/apps/Settings into staging/lineage-16.0_merge-android-9.0.0_r56

Android 9.0.0 release 56

* tag 'android-9.0.0_r56' of https://android.googlesource.com/platform/packages/apps/Settings:
  RESTRICT AUTOMERGE Allow LockScreenPattern to be launched in the pinning screen

Change-Id: I7cf977d7dc4deecb2e13266922978c305d444dfa

Change-Id: Ia19d1b712a21e42498c364d17895ac4702b5cbfc

Allow LockScreenPattern to be launched in the pinning screen

If work profile lock is enabled and work app is pinned, users will get a
black/white screen on the phone. That's because Settings is prevented
from other apps launch any pages of Settings in the pinning mode.

In order to launch some pages of Settings from other apps, we add a
condition to the preventive mechanism and allow the activity inherited
from SettingsBaseActivity to override the condition to have the activity
to be launched from other apps in the pinning mode.

Bug: 137015265
Bug: 135604684
Test: manual test
Change-Id: I8070de79a83350d1658efcb19e983669dad0e673
Merged-In: I8070de79a83350d1658efcb19e983669dad0e673
(cherry picked from commit 8d472055)

* We can't inject via IA if we want this.

Change-Id: I482a073e9c699d3f2bc5870567d603ceca2065b1
(cherry picked from commit 279f9fca)

[RELEASE] Sprint Freetown (pie)

See merge request !31

Android 9.0.0 Release 53 (6107734)

* tag 'android-9.0.0_r53':
  Prevent accounts page directly opening in screen pinning mode

Change-Id: I84f8d909df98b517478eea5bf67fed047db445f5

App Launcher icon updated

See merge request !28

Change-Id: I0598f99293eefb3b789dc12f3a37e5c097099c2b

In Settings there is no auth mechanism to prevent accounts page being
opened in screen pinning mode. This CL makes it so that when users are
trying to navigate to any pages in Settings from other apps in screen
pinning mode, Settings app will directly close its page.

Bug: 137015265
Bug: 135604684
Test: manual
Change-Id: If26eda408a9ef6fa03ad82e5bee51bb7185950d6
Merged-In: If26eda408a9ef6fa03ad82e5bee51bb7185950d6
(cherry picked from commit f3242dab3546c019d4b79c502f7b8850d36123a5)
(cherry picked from commit ad2502a9)

[RELEASE] Sprint Beijing (pie)

See merge request !21

grep -rl master_clear_desc | xargs sed -i '/master_clear_desc/{s/Google/\/e\//g}'

This reverts commit fa47362d.

We have /e/ account not google

See merge request !20

* Missed that this one already existed...

Change-Id: I74779f0872727fed2bbb9abc3107968be3e68940

* This is a forward port of commit
  72806b39
* Instead of directly accessing the network selection,
  we open the parent settings, as the network selection is
  not a subscreen anymore, but just two preferences

Change-Id: I3d56653157b1d773255d2cb34fd995f42572653a

Android 9.0.0 Release 49 (5794013)

* tag 'android-9.0.0_r49':
  Treat mode_default as denied for install_unknown_apps
  [RESTRICT AUTOMERGE] Make ScreenPinningSettings behaviour consistent with LockTaskController.
  Do not allow draw on top for App notification settings
  Do not allow draw on top for default sms picker.
  Hide quicksetting tile for dev options when it's turned off
  Update PBAP info for all pairing dialogs. DO NOT MERGE
  Hide SettingsSlice provider
  Disable changing lock when device is not provisioned.

Change-Id: I705fc2d3c72ea97721d4640a639078c18fbe5ac5

* Instead of always using the default tint, we get the current
  tint from system and use that for the first private storage
* Refactor the code away from hardcoded colors

Solves:
https://gitlab.com/LineageOS/issues/android/issues/1130

Change-Id: I8eca661224ee32147fd5fc95e1fa8a7d4589697f

* Lineage assigns additional network policy values for restrict on
  data and wlan etc.

* DataSaverBackend was assuming that only allow background
  and allow unrestricted background exist and therefore could both:
  i) overwrite other uid policies and ii) incorrectly think there were
  changes when there weren't.

* Change setUidPolicy to appropriate add/remove sequences and filter
  the newPolicy value in the callback to ignore everything except
  background data related policies.

Change-Id: I4c81d7fa2199441674a4176eb78b29facd0b799e

* Fixes: https://gitlab.com/LineageOS/issues/android/issues/1098

Change-Id: I228fef766b70ad4f3fc47b83cf113517eb9db99f

Change-Id: I9429f91db40874456ebe52a8b85cc2f169af53b4

Change-Id: I34924fe8e60e3d492f219aa6d0ffa54f0bd46e38