Fixed
Status Update
Comments
va...@google.com <va...@google.com> #2
I guess this is because packages.list now is not readable by anyone:
Android 4.0.4:
-rw-rw-r--
Android 4.3:
-rw-rw----
Please provide a way to fix or work-around it.
Android 4.0.4:
-rw-rw-r--
Android 4.3:
-rw-rw----
Please provide a way to fix or work-around it.
ci...@google.com <ci...@google.com> #3
I'm having this problem as well on my Nexus 10. Fortunately I haven't updated the Nexus 7 yet, so I can still work.
va...@google.com <va...@google.com> #4
The /data/system/packages.list was not world-readable even in 4.2.2. Would you please 1. the Build number of your 4.3 Nexus 7, and
2. that you're invoking "adb shell run-as" for a package which is definitely installed?
2. that you're invoking "adb shell run-as" for a package which is definitely installed?
ap...@google.com <ap...@google.com> #5
i have this problem (run-as returns: package is unknown) on my Galaxy Nexus.
i used adb shell and run-as to download database to my PC, and now it doesn't work.
i used adb shell and run-as to download database to my PC, and now it doesn't work.
va...@google.com <va...@google.com>
pr...@google.com <pr...@google.com> #6
Same problem here. Reproduced on Nexus 7 and Nexus 4. Before the 4.3 update it worked fine.
Description
Jetpack Compose version:
Material Library Version (M2, M3 or Both?):
Material Compose component used:
androidx.compose.material3.Scaffold
Steps to Reproduce:
MainActivity.kt
, (a)enableEdgeToEdge
is called and (b)Scaffold's PaddingValues
(calledinnerPadding
here) is applied to the entire content.See attached image (
Scaffold_DisplayCutout.png
). I've modified the sample code to make the issue more apparent. Notice the Composable, which is usinginnerPadding
, avoids the system bars region but does not avoid the display cutout region.Severity: To ensure Scaffold's edge-to-edge is enforced in Android 15.
PaddingValues
makes going edge-to-edge easy, it should account for display cutouts. Otherwise, developers shouldn't use Scaffold'sPaddingValues
and should instead use alternatives likeWindowInsets.safeDrawing
,WindowInsets.safeGestures
, orWindowInsets.safeContent
. This is especially important as