-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add support for round icons. #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Lineage is based on keeping aosp look with awesome features, so i propose, we should enable round icons to keep up with the aosp looks.
|
From 657c329 Mon Sep 17 00:00:00 2001 Lineage is based on keeping aosp look with awesome features, so i propose, we should enable round icons to keep up with the aosp looks.core/res/res/values/config.xml | 2 +- diff --git a/core/res/res/values/config.xml b/core/res/res/values/config.xml
|
|
Hi there; This is an automated reply, to let you know LineageOS doesn't merge pull You can submit your change requests through our public review system, That review system is an installation of Google's Gerrit code review. Thanks! |
zaaraameera2014
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job
There are two existing cases where apps that share a sharedUserId potentially end up in separate SELinux domains. 1. An app installed in /system/priv-app runs in the priv_app domain. An app installed on the /data partition which shares a sharedUserId with that priv_app would run in the untrusted_app domain (e.g. GTS b/72235911). This issue has existed since Android N. 2. The untrusted_app domain may now deprecate permissions based on targetSdkVersion, so apps with sharedUserId may have different permissions based on which targetSdkVersion they use. This issue has existed since Android O, but is particularly problematic for feature "Deprecate world accessible app data" which puts every app targeting P+ into its own selinux domain. This change fixes LineageOS#1 and adds a temporary workaround to prevent LineageOS#2. Test: cts-tradefed run cts -m CtsSelinuxTargetSdkCurrentTestCases Test: cts-tradefed run cts -m CtsSelinuxTargetSdk27TestCases Test: cts-tradefed run cts -m CtsSelinuxTargetSdk25TestCases Bug: 72290969 Change-Id: I211de05ad6f10b69e3e082cfe977f2dd43d90549
There are two existing cases where apps that share a sharedUserId potentially end up in separate SELinux domains. 1. An app installed in /system/priv-app runs in the priv_app domain. An app installed on the /data partition which shares a sharedUserId with that priv_app would run in the untrusted_app domain (e.g. GTS b/72235911). This issue has existed since Android N. 2. The untrusted_app domain may now deprecate permissions based on targetSdkVersion, so apps with sharedUserId may have different permissions based on which targetSdkVersion they use. This issue has existed since Android O, but is particularly problematic for feature "Deprecate world accessible app data" which puts every app targeting P+ into its own selinux domain. This change fixes LineageOS#1 and adds a temporary workaround to prevent LineageOS#2. Updated version considers both SharedUserSetting.isPrivileged() and pkg.isPrivileged() for the case where the app has a shared User. Test: cts-tradefed run cts -m CtsSelinuxTargetSdkCurrentTestCases Test: cts-tradefed run cts -m CtsSelinuxTargetSdk27TestCases Test: cts-tradefed run cts -m CtsSelinuxTargetSdk25TestCases Test: confirm via packages.list that apps end up in the same selinux domain before and after this patch. Bug: 72290969 Change-Id: I974bea88004622b70633fdeb54a1372fd04c6eff
Lineage is based on keeping aosp look with awesome features, so i propose, we should enable round icons to keep up with the aosp looks.