Fixed
Status Update
No update yet.
Comments
al...@android.com
ch...@google.com
ya...@google.com
m....@gmail.com
Information redacted by Android Beta Feedback.
an...@gmail.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Screen record of the issue, for clarity Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4
Note: Please upload the files to google drive and share the folder to
ar...@gmail.com
- Build Number: google/cheetah_beta/cheetah:UpsideDownCake/UPB2.230407.014/10064957:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
This issue occurred when I plugged in my phone to charge it and it had fully charged. I plugged in my phone when it was at roughly 13% battery life and it said on the desk next to me charging. When battery percentage got you 100%, an error appeared in my notifications that said that the phone was either not charging or charging very slowly, it seemed to indicate a possible issue with the charger or the battery. This only started when I updated my phone recently. It seems to be that the error notification May not be ignoring the slow charge and or lack of charge when the battery has hit 100%..
Debugging information
Google Play services
com.google.android.gms
Version 231715044 (23.17.15 (190400-534251769))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567252434 (113.0.5672.24)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
This issue occurred when I plugged in my phone to charge it and it had fully charged. I plugged in my phone when it was at roughly 13% battery life and it said on the desk next to me charging. When battery percentage got you 100%, an error appeared in my notifications that said that the phone was either not charging or charging very slowly, it seemed to indicate a possible issue with the charger or the battery. This only started when I updated my phone recently. It seems to be that the error notification May not be ignoring the slow charge and or lack of charge when the battery has hit 100%..
Debugging information
Google Play services
com.google.android.gms
Version 231715044 (23.17.15 (190400-534251769))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567252434 (113.0.5672.24)
System App (Updated)
Network operator: T-Mobile
SIM operator: T-Mobile
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visit
Description
Version used: 22.2.0
Calling setChecked(false) on a NavigationView menu item does not clear the item's checked state -- or at least, does not update the NavigationView's appearance to reflect the setChecked(false).
Calling setChecked(false) and then calling view.invalidate() will update the view, but only if the group is not exclusively checkable (does not have checkableBehavior="single").
Calling setChecked(boolean) on a menu item in a group with checkableBehavior="single" always sets that item checked, even when calling setChecked(false).
For example, if you loop through all the items in a group and call setChecked(false) for each menu item, the last item in the group will appear checked after you invalidate the NavigationView.
I noticed this when trying to make checkableBehavior="single" apply across more than one group in a NavigationView.
Desired result:
Calling setChecked(false) on an item should be reflected in the NavigationView without calling view.invalidate().
Calling setChecked(false) on an item in a group with checkableBehavior="single" should not check that item (or at least, it might be nice to clarify this in the documentation). One option would be to set the checked state to "false" for all of the items in the group, as currently there is no way to remove the checked state from all items in a group.
(BTW it would be nice if there was an option to make checkableBehaviour apply across multiple groups, without needing to implement the logic ourselves.)