Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
The internal systemBarsForVisualComponents
right now only uses systemBars
, which doesn't include the display cutout:
Updating to systemBars.union(displayCutout)
should fix this, if that's a change we can make.
an...@google.com <an...@google.com> #3 Restricted
pu...@google.com <pu...@google.com>
pu...@google.com <pu...@google.com> #4
Not taking the display cutout into account will impact cars heavily, since some have very large display cutouts:
vv...@google.com <vv...@google.com> #5
Project: platform/frameworks/support
Branch: androidx-main
Author: Alex Vanyo <
Link:
Add displayCutout to default Material insets
Expand for full commit details
Add displayCutout to default Material insets
Relnote: "Adds displayCutout to the group of insets that Material
components take into account by default, to avoid content overlapping
with the display cutout.
This is a behavior change that will impact how inset-aware
components behave around a display cutout. This includes the default
value of the WindowInsets parameter for inset-aware Material 3
components, and the WindowInsets values provided in the component
Defaults objects for both Material 2 and Material 3.
If this change causes undesirable behavior,
manually specify the WindowInsets parameter on a per-component basis."
Fixes: 362508045
Change-Id: I43ee9ad12db0450ebb9c65ce10d5c39d12628b6c
Files:
- M
compose/material/material/src/androidMain/kotlin/androidx/compose/material/SystemBarsDefaultInsets.android.kt
- M
compose/material3/material3/src/androidInstrumentedTest/kotlin/androidx/compose/material3/MaterialComponentsInsetSupportTest.kt
- M
compose/material3/material3/src/androidMain/kotlin/androidx/compose/material3/internal/SystemBarsDefaultInsets.android.kt
Hash: 692b440ac97b1831d5b35aafff241a98aeeacb93
Date: Wed Dec 18 19:49:15 2024
Description
TLDR: Android Beta Feedback detected a Java crash issue in com.android.systemui.
What
User experience
What type of issue is this?
Crash
What steps would let us observe this issue?
What did you expect to happen?
Not black screen
What actually happened?
Black screen
What was the effect of this issue on your device usage, such as lost time or work?
High
When
Time and frequency
When did this happen?
Sep 28, 2024 02:45:43 PM GMT-05:00
How often has this happened?
Frequently
Where
Component
Suggested component: <not visible> (1630575)
Build and device data
- Build Number: google/husky_beta/husky:15/AP41.240823.009/12329489:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1
Related apps
IU del sistema
com.android.systemui
Version 35 (15)
System App (Bundled)
Related process
com.android.systemui
Debugging information
Servicios de Google Play
com.google.android.gms
Version 243734036 (24.37.34 (260408-679256246))
System App (Updated)
Android System WebView
com.google.android.webview
Version 661314833 (128.0.6613.148)
System App (Updated)
Network operator: HazloRealidad
SIM operator: Claro PE
Filed by Android Beta Feedback. Version (Updated): 2.45-betterbug.external_20240829_RC01 (DOGFOOD) https://developer.android.com/preview/feedback#feedback-app.\
Issue detected by Android Beta Feedback.
To learn more about our feedback process, please visit