Fixed
Status Update
No update yet.
Comments
jb...@google.com
va...@google.com
[Comment deleted]
ya...@google.com
[Comment deleted]
ya...@google.com
Happens every time I return to homescreen on Nexus 5.
ap...@google.com
This is a real problem. As the hours pass system ram consumed gets bigger and bigger. It gets to the point that I have to reboot my device because apps keep reloading and sometimes even the launcher has to reload.It is a serious issue. I have to reboot daily
va...@google.com
ya...@google.com
pr...@google.com
When play music crashed in the background today, with maps navigation running in the forefront, system ram usage was at 780mb. Maps ram usage was at 280mb. The play music process was stuck in "restarting" status until I swiped it out of recents and restarted it. This was after around 48 hours uptime. Camera app also started crashing mid-photosphere shortly after this. After a reboot system usage dropped to ~380mb and everything's working fine again.
Description
Version used: 1.8.0-alpha03
When trying out the new `enableEdgeToEdge` method, I ran into one slightly annoying aspect.
When apps have their own theme picker for choosing dark mode and light mode, the resulting UI them (light vs dark) that the app uses may differ from the system theme, as passed down via the `Configuration`.
`enableEdgeToEdge` always looks at the system theme via the `Configuration`, so there isn't a good way to have a different source of truth for choosing whether to show a dark or light theme.
It also doesn't directly work to have an `if` statement and call `SystemBarStyle.light` or `SystemBarStyle.dark`, because those don't have the transparent behavior that `SystemBarStyle.auto` does on API 29 and above.
Maybe `enableEdgeToEdge` could take an optional lambda for `isShowingDarkTheme`, with a default implementation that uses the `Configuration`.