Charged was set to 80%, but still charged pass 80% [391648930]

Infeasible

Bug

Platform

Needs Info

Status Update

No update yet.

Description

ka...@gmail.com

created issue #1

Jan 22, 2025 06:57PM

What

User experience

What type of Android issue is this?
Battery / Charging

What steps would let us observe this issue?

Battery was set to charge to 80%
I charge it normally
It went up to 90% then it stops
I used the battery to 65%
I charge it again without changing any setting
As I'm typing the charge went from 81% to 82%

What did you expect to happen?
Charge up to 80% then stops

What actually happened?
Charged passed 80%

What was the effect of this issue on your device usage, such as lost time or work?
Slight

When

Time and frequency

When did this happen?
Jan 23, 2025 GMT+08:00

How often has this happened?
Frequently

Where

Component

Originating component: <not visible> (1630575)

Build and device data

- Build Number: google/shiba_beta/shiba:15/BP11.241210.004/12926906: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

Debugging information
Google Play services
com.google.android.gms
Version 245034035 (24.50.34 (260400-713002902))
System App (Updated)

Android System WebView
com.google.android.webview
Version 677826033 (131.0.6778.260)
System App (Updated)

Network operator: SoSI
SIM operator: SoSI

Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Comments

ka...@gmail.com <ka...@gmail.com> Jan 22, 2025 06:57PM

Screenshot_20250123-025324-edit-edit.png

Restricted

235 KB

View

Download

vi...@google.com <vi...@google.com> #2Jan 22, 2025 09:15PM

Assigned to vi...@google.com.

This has been fixed internally and will be avilable in Fragment 1.3.0-alpha08.

Note: this fix relies on using the new state manager and will not function if it is manually disabled.

vi...@google.com <vi...@google.com> #3Jan 30, 2025 09:12PM

Please provide the information as requested in comment #2, for us to further investigate this issue. Unfortunately the issue will be closed within 7 days if there is no further update.

vi...@google.com <vi...@google.com> #4Feb 7, 2025 03:09AM

Status: Won't Fix (Infeasible)

We’ll be closing this issue due to not having enough actionable information. If you continue to have this issue, please open a new issue and add the relevant information along with a reference link to the earlier issue.