You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if anyone else would find this issue helpful, or if devs are interested in implementing this/pulling my changes?
I unfortunately uses Samsung as my main phone and OneUI's android 13 doesnt have the new mediaSession notification style. What we got is the old school squared album art on the left, and metadata on the right. While I do try to keep all my album arts to be as square as possible, occasionally there are landscape or portrait album arts mixed in. The squared album art does a "contain" instead of "cover" so annoying white spaces will show. My solution is to crop any loading album art to squares: c514071
Although is this a good idea to push a PR or better kept in my own repo?
im using a 1280*720 pic https://i.ytimg.com/vi/5IOVkstxkdE/maxresdefault.jpg
cropped pixel ->not cropped pixel -> cropped samsung -> not cropped samsung
i guess its better to make it as an option...
and very unfortunately oneUI6 still (partly) has this square notification
I wonder if anyone else would find this issue helpful, or if devs are interested in implementing this/pulling my changes?
I unfortunately uses Samsung as my main phone and OneUI's android 13 doesnt have the new mediaSession notification style. What we got is the old school squared album art on the left, and metadata on the right. While I do try to keep all my album arts to be as square as possible, occasionally there are landscape or portrait album arts mixed in. The squared album art does a "contain" instead of "cover" so annoying white spaces will show. My solution is to crop any loading album art to squares: c514071
Although is this a good idea to push a PR or better kept in my own repo?
Samsung's media notification looks like:
https://www.reddit.com/r/oneui/comments/x46hbm/concept_one_ui_5_what_couldve_been_notifications/
The text was updated successfully, but these errors were encountered: