-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dual-cell models recognize the wrong (half) current value #266
Comments
But the charging switch is still not stable, especially when using wireless charging (even a slow charge) There are three instances of instability:
There are normal conditions: Conditions for recurrence of unstable situations: And “charger/online 1” here always seems to show a connected charger? Does it have an effect on the above question. |
Try the new build with the stock config (batt_status_workaround=true and everything else default). |
Thanks for the reply. It doesn't test well after upgrading though (have restored all default parameters via acc -sr a), with or without charging the battery state while charging changes between 'charge', 'idle', ' discharge', with logs acc-logs-arcfox_2024-12-16_16-53-29.zip And the current values seem to be farther off, then I set it to af=250000 to barely look close to the current values found by other tools. |
The current is farther off because of a recent change that can easily be reverted. |
Keep testing with |
Tried again, and not good yet -_- The auto switch is failing, charging won't stop as expected, and manually setting the switch to wireless boost en doesn't work anymore. With bsw=true. So I really doubt that the problem is caused by abnormal current value detection. Returning to version 6.2 with the following parameters works stably, just not controlling wired charging. |
acc_v2024.12.21-rc_202412210_1349.zip This fixes the issue with |
Tested it some days and it's much better than the first two versions. Wired charging ok, 15W wireless (actually 20W+, higher than before) charging to pause occasionally gets very hot, and there have been a couple of “exit code-7” when charging has been suspended. Do I need to attach a log? Doesn't reproduce very consistently. |
acc_v2024.12.29-rc_202412290_2033.zip |
Occasional problems. Earlier logs are high temperature and exit code 7 after charging to 75, later logs are charging to 75 paused and then resumed to continue charging。 |
Using wireless fast charging, high temperatures when approaching a power pause. Force “wireless_boost_en 0 1”, only this switch takes effect. |
and this version looks like a problem recognizing the current polarity, now I have to set bsw to false to match the actual charging state. |
Model: Moto Razr 50 Ultra
Android version: Android14, MyUI7.0
ACC version: v2024.6.2-rc,any installation method
Other settings:
charging_ switch="/sys/class/qcom-battery/wireless_boost_en 0 1 --" //Because the default charging switch doesn't work.
batt_status_workaround=false //Because of the battery polarity is misrecognized by default.
Charging optimization and overcharge protection that comes with the system
Folding models such as the moto razr50 have two battery cells, resulting in the acc reporting current always being half of what it actually is.
acc-logs-arcfox_2024-08-02_14-50-24.zip
The text was updated successfully, but these errors were encountered: