Skip to content

Conversation

@archit9169
Copy link

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.

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.
@archit9169 archit9169 closed this Dec 30, 2016
@archit9169 archit9169 deleted the patch-1 branch December 30, 2016 09:54
@archit9169 archit9169 restored the patch-1 branch December 30, 2016 09:57
@archit9169 archit9169 reopened this Dec 30, 2016
@archit9169 archit9169 closed this Dec 30, 2016
@archit9169 archit9169 reopened this Dec 30, 2016
@archit9169
Copy link
Author

From 657c329 Mon Sep 17 00:00:00 2001
From: Archit Bajpai [email protected]
Date: Fri, 30 Dec 2016 12:42:26 +0530
Subject: [PATCH] Add support for round icons.

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 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/res/res/values/config.xml b/core/res/res/values/config.xml
index f87e52a..dd112a8 100644
--- a/core/res/res/values/config.xml
+++ b/core/res/res/values/config.xml
@@ -2735,7 +2735,7 @@
com.android.retaildemo/.DemoPlayer

 <!-- Flag indicating whether round icons should be parsed from the application manifest. -->
  • false
  • true

@lineageos-gerrit
Copy link
Contributor

Hi there;

This is an automated reply, to let you know LineageOS doesn't merge pull
requests submitted directly to our github.com repositories.

You can submit your change requests through our public review system,
located at https://review.lineageos.org/

That review system is an installation of Google's Gerrit code review.
If you've never interacted with Gerrit before, we also suggest you take
a look at https://zifnab.net/~zifnab/wiki_dump/Howto:_Gerrit.html

Thanks!

Copy link

@zaaraameera2014 zaaraameera2014 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job

@LineageOS LineageOS deleted a comment from zaaraameera2014 Jan 9, 2018
@LineageOS LineageOS locked and limited conversation to collaborators Jan 9, 2018
0xf104a pushed a commit to MilkyWayOS/android_frameworks_base that referenced this pull request Feb 24, 2024
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
0xf104a pushed a commit to MilkyWayOS/android_frameworks_base that referenced this pull request Feb 24, 2024
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants