maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)
-   -   [Solved] No data or battery not calibrated (https://talk.maemo.org/showthread.php?t=92576)

LavaCroft 2014-02-02 06:06
[Solved] No data or battery not calibrated
 
The above message popped up in the battery applet out of the blue.
Running CSSU-thumb2, BME replacement and using the pali-recommended "modprobe -r rx51_battery".
Charging to green LED and/or rebooting does not fix it. Modprobe rx51_battery gives some numbers, but they are the wrong numbers.
Trying to recalibrate the battery with the bq27x00_battery module gives a "resource or device busy", without it the calibration script gives a read error on one of the cat commands.

Is there any way, short of reflashing, to just get this to work again?

Thanks in advance!

Estel 2014-02-02 07:09
Re: No data or battery not calibrated
 
Ironically, reflashing wouldn't help, at all. I think you just had >32 charging cycles since last calibration. For some reasons, device hadn't chance to calibrate itself automaticaly (maybe you were always charging it before it reached very low level/never let it shut itself down due to out of charge?).

To fix, you need to calibrate manually:

1. Charge battery to full, until VDQ flag turns to 1
2.
Code:
modprobe -r bq27x00_battery
modprobe -r rx51_battery
3. Use your device normally, but don't shut it down, charge, or reboot. Checking battery level manually, from time to time (battery applet *won't* give you correct readings, due to modules being not loaded). Always ensure that VDQ flag is 1, otherwise, you need to start back from scratch. Accidental reboot may or may not turn VDQ to 0, depending on circumstances.

4. When voltage drops to ~3300 mV, stop whatever you're doing on device and start monitoring it closely.

5. The goal now is to get under 3248 mV and stay there for at least 15 seconds, without voltage either going above, or too much under (less than ~2900 mV), causing device to "faint" due to low power. The most reliable - although, time consuming - way is to set screen to never dim, and/or enable flashlight - so device will consume steady ammount of current. Monitor voltage and VDQ.

6. When voltage dros below threeshold (3248 mV) and stays there for 15 seconds, VDQ will immediately turn to 0 and chip recalibrate.

7. Power device off via normal way, before it "faints" - if you miss that step, it *won't* spoil calibration, but you may get your /home filesystem corrupted. You better not miss this step, or you will give yourself quite a homework (see next steps). In case of failing it, for some reason, follow step 8. Otherwise, you're finished now - start using device normally.

8. (optional, in case of missing step 7)
This step require you to run latest cssu-thumb or cssu-testing. Precisely, it require updated e2fsprogs&friends, cause Maemo's vanilla ones were ancient and segfaulted mid-way, leaving filesystem in total mess.

Boot into any recovery console (backupmenu's one, Mentalist Traceur's one, Pali's one, etc), and:
Code:
fsck /dev/mmcblk0p2 -f -p
a) If it says (amongst other things) "<filesystem name> clean" - with or without "recovering journal" before - and exits, you're good to go. Power off, and you're finished. Start using device normally.

b) If it informs about fixing some things, but exits cleanly, see point a.

c) If it ends with something like "Unexpected inconsistency, run FSCK manually", do:
Code:
fsck /dev/mmcblk0p2 -f -y -v >> /path/where/you/want/log/saved/fsck.log
Ensure, that path where you save log isn't any temporary directory (that will get nuked after boot), as you may really need that log later.

Where to save, depends on the recovery shell you're using. If you have rootfs mounted, /path/where/rootfs/is/mounted/var/log/fsck.log is a good place. Using backupmenu's root console (and *only* after mounting rootfs via 'mountroot' command), it is /tmp/mnt/rootfs/var/log/fsck.log, If I remember correctly (you can use auto-completion via TAB).

When it's finished, repeat this point (8) from the beginning, and follow approriate sub-point.

8.1. After you boot into Maemo, check fsck.log you've create in point 8 - it will contain (amongst other things), pathes to files that were repaired/salvaged (connected to lost+found) during manual fsck repair. Check every file's integrity individually. In case it "vanished", check /home/lost+found, it may be sitting there. In case of problems, determine which package missing file depend to, and reinstall whole package.
---

Appendix:
To check VDQ flag and voltage conveniently, either use bq27200.sh script, or package BNF (the latter is my favorite method, but no surprise here, as I've created it ;) ).

Appendinx 2:
Don't get scared by ammount of text here - I tried to explain everything in details, and half of this (as it turned to be) tutorial is an emergency kit for worst-case scenario of filesystem corruption, due to device fainting of low power. By being at least basically aware of situation, you won't hit it, saving yourself half of this ;)

Cheers,
/Estel

LavaCroft 2014-02-02 17:19
Re: No data or battery not calibrated
 
Thanks for the excellent reply. I will let you know how it works out.

[EDIT] Can I trust the N900 to actually stop charging once the battery is full? Might be a silly questions, but I'm slightly concerned about it.

pichlo 2014-02-02 18:54
Re: No data or battery not calibrated
 
Quote:
Originally Posted by LavaCroft (Post 1410481)
Can I trust the N900 to actually stop charging once the battery is full?
Yes. (10 chars)

LavaCroft 2014-02-02 23:23
Re: No data or battery not calibrated
 
The process seems to have worked. Thanks a lot.

About your hunches as to why it happened, both the >32 recharge cycles and the 'always charging' ideas were correct. I will have to keep this in mind for the future.

Estel 2014-02-03 05:37
Re: [Solved] No data or battery not calibrated
 
I' glad it have worked for you :) As for >32 cycles, yea - it is good idea to let it, from time to time (like, once or twice in month) - discharge 'till shutdown, so it will update it's calibration data, and won't hit threeshold anytime soon.

Of course, it only makes sense if VDQ is 1 during that discharge (when battery is low and you think "heck, I could let it discharge now", just check if VDQ is still 1), otherwise it won't recalibrate. Just be sure to not have any unnecessary applications running, when expecting to let it shutdown itself. Standard Maemo stuff is OK, doesn't need to deliberately kill things from terminal.

Obviously, by "discharge and shutdown", I mean doing so with bq27x00_battery and rx51_battery modules *loaded*, so it will shutdown safe way, just after recalibrating - *not* letting it fade out due to low power at ~2900 mV, with modules unloaded (otherwise, points 8+ from previous post, aka "filesystem corruption", apply ;) ).

/Estel

felangga 2017-09-01 10:01
Re: No data or battery not calibrated
 
Quote:
Originally Posted by Estel (Post 1410393)
Ironically, reflashing wouldn't help, at all. I think you just had >32 charging cycles since last calibration. For some reasons, device hadn't chance to calibrate itself automaticaly (maybe you were always charging it before it reached very low level/never let it shut itself down due to out of charge?).

To fix, you need to calibrate manually:

1. Charge battery to full, until VDQ flag turns to 1
2.
Code:
modprobe -r bq27x00_battery
modprobe -r rx51_battery
3. Use your device normally, but don't shut it down, charge, or reboot. Checking battery level manually, from time to time (battery applet *won't* give you correct readings, due to modules being not loaded). Always ensure that VDQ flag is 1, otherwise, you need to start back from scratch. Accidental reboot may or may not turn VDQ to 0, depending on circumstances.

4. When voltage drops to ~3300 mV, stop whatever you're doing on device and start monitoring it closely.

5. The goal now is to get under 3248 mV and stay there for at least 15 seconds, without voltage either going above, or too much under (less than ~2900 mV), causing device to "faint" due to low power. The most reliable - although, time consuming - way is to set screen to never dim, and/or enable flashlight - so device will consume steady ammount of current. Monitor voltage and VDQ.

6. When voltage dros below threeshold (3248 mV) and stays there for 15 seconds, VDQ will immediately turn to 0 and chip recalibrate.

7. Power device off via normal way, before it "faints" - if you miss that step, it *won't* spoil calibration, but you may get your /home filesystem corrupted. You better not miss this step, or you will give yourself quite a homework (see next steps). In case of failing it, for some reason, follow step 8. Otherwise, you're finished now - start using device normally.

8. (optional, in case of missing step 7)
This step require you to run latest cssu-thumb or cssu-testing. Precisely, it require updated e2fsprogs&friends, cause Maemo's vanilla ones were ancient and segfaulted mid-way, leaving filesystem in total mess.

Boot into any recovery console (backupmenu's one, Mentalist Traceur's one, Pali's one, etc), and:
Code:
fsck /dev/mmcblk0p2 -f -p
a) If it says (amongst other things) "<filesystem name> clean" - with or without "recovering journal" before - and exits, you're good to go. Power off, and you're finished. Start using device normally.

b) If it informs about fixing some things, but exits cleanly, see point a.

c) If it ends with something like "Unexpected inconsistency, run FSCK manually", do:
Code:
fsck /dev/mmcblk0p2 -f -y -v >> /path/where/you/want/log/saved/fsck.log
Ensure, that path where you save log isn't any temporary directory (that will get nuked after boot), as you may really need that log later.

Where to save, depends on the recovery shell you're using. If you have rootfs mounted, /path/where/rootfs/is/mounted/var/log/fsck.log is a good place. Using backupmenu's root console (and *only* after mounting rootfs via 'mountroot' command), it is /tmp/mnt/rootfs/var/log/fsck.log, If I remember correctly (you can use auto-completion via TAB).

When it's finished, repeat this point (8) from the beginning, and follow approriate sub-point.

8.1. After you boot into Maemo, check fsck.log you've create in point 8 - it will contain (amongst other things), pathes to files that were repaired/salvaged (connected to lost+found) during manual fsck repair. Check every file's integrity individually. In case it "vanished", check /home/lost+found, it may be sitting there. In case of problems, determine which package missing file depend to, and reinstall whole package.
---

Appendix:
To check VDQ flag and voltage conveniently, either use bq27200.sh script, or package BNF (the latter is my favorite method, but no surprise here, as I've created it ;) ).

Appendinx 2:
Don't get scared by ammount of text here - I tried to explain everything in details, and half of this (as it turned to be) tutorial is an emergency kit for worst-case scenario of filesystem corruption, due to device fainting of low power. By being at least basically aware of situation, you won't hit it, saving yourself half of this ;)

Cheers,
/Estel
I've tried this method, but before 3248mV my phone will auto-shutdown. Did it means that modprobe -r doesn't work ? Or something else in the system did auto shutdown to prevent corruption?

My battery only detected as 13xxmAH but actually it 2000mAh.
Please help :(

Ridd92 2018-11-11 19:11
Re: [Solved] No data or battery not calibrated
 
I will revive a thread a little bit as I got new batteries for two units and have been struggling to get them calibrated. Disabling both the bq27x00 and rx51 battery modules does't seen to prevent the device to shut down automaticly I think the bnf is doing this.

Although I've calibrated one battery after voltage dropes somewhere below the 3248 and device shut down (Not fainted) I recharged it with both mentioned modules In -r mode and now it is working fine with bq27x00 module.

The second one (Same new battery, same manufaturer) show that it's got 868mAh, charge to 660 (Each and every time) and got discharged in very slow way. Battery seems to have good, original capacity but I've found no way to calibrate it.

I will try it later with some scripts I need to work on first without the bnf. We will see.

Ridd92 2018-11-11 19:14
Re: No data or battery not calibrated
 
Quote:
Originally Posted by felangga (Post 1533767)
(...) My battery only detected as 13xxmAH but actually it 2000mAh.
Please help :(
If it is not the double battery (Like the mungen one) I can assure you it doesn't have 2000 mAh, Those are only the numbers to get you to buy this particular one :)

Ridd92 2018-11-12 20:11
Re: [Solved] No data or battery not calibrated
 
How does this battery calibration works from dvice point of view? Is it just some software/hardware adaptation? Because it looks like it is some fixed information in battery that I can't get around. I know it sound silly, but each of my units now shows that battery is 660/660 mAh trough out at least half of battery's charge. Some else expirienced this?

Ridd92 2018-11-15 16:08
Re: [Solved] No data or battery not calibrated
 
Ok, I've calibrated this battery somehow, at least partially, but can someone explain this?

This is from rx51_battery:

https://i.postimg.cc/PqYhJnFq/Screen...115-170055.png

This is from bq27x00_battery:

https://i.postimg.cc/BQrV6PWx/Screen...115-165902.png

And this is from BNf with above modules wirh -r

https://i.postimg.cc/d1gxyhkP/Screen...115-170126.png

WT*??

sicelo 2018-11-15 19:43
Re: [Solved] No data or battery not calibrated
 
No idea why you are removing modules if you want/need to use the system applet for battery information. I'm on CSSU-T(humb) and are using bme-replacement, and all the modules are loaded,

Code:
~ $ lsmod | grep battery
bq27x00_battery        7120  0
rx51_battery            2240  0
power_supply            6916  3 bq27x00_battery,bq2415x_charger,rx51_battery
My battery readout is correct too.

Maybe try this adaptation of the original bq27200 script, https://talk.maemo.org/showthread.php?t=95816

You will not need to unload any modules for that script either. Good luck.

Ridd92 2018-11-15 20:30
Re: [Solved] No data or battery not calibrated
 
Sicelo, I removed those modules only during the calibration of battery as described in post #2 in this thread:
http://talk.maemo.org/showpost.php?p...93&postcount=2

I want to work with bq battery module as most of my scripts to make battery works longer relay on it. I calibrated 3 batteries this ways and this works. But this one is not. I don't know why,

What I'm showing in post above is what happend after trying to calibrate this particular one battery.

I will continue to try, but after few days of fighting I'm running out of moves...

And so with o without removing those modules BNF shows the same info.

When I put battery into another device problem is the same.

bdbogart 2019-11-23 17:01
Re: No data or battery not calibrated
 
Hello @Estel,

I realize this is an *old* thread, but I got a new 2450mAh battery (https://www.amazon.ca/gp/product/B07B46XKZC) for my N900 and would like to calibrate it.

I'm using CSSU Stable, I see that VDQ is 1, calibration needed is 1 and the normal battery modules are unloaded:

Code:
~ $ lsmod | grep battery
~ $
I've tried twice now and what happens is that the device "faints" (screen goes black and device is unresponsive) when voltage is just above 3300 mV, so I can't continue with the instructions because the device has already fainted. The device has not corrupted the filesystem, I presume because I plug it in as soon as the "faint" occurs.

So, is there any way to calibrate this battery?


Quote:
Originally Posted by Estel (Post 1410393)
Ironically, reflashing wouldn't help, at all. I think you just had >32 charging cycles since last calibration. For some reasons, device hadn't chance to calibrate itself automaticaly (maybe you were always charging it before it reached very low level/never let it shut itself down due to out of charge?).

To fix, you need to calibrate manually:

1. Charge battery to full, until VDQ flag turns to 1
2.
Code:
modprobe -r bq27x00_battery
modprobe -r rx51_battery
3. Use your device normally, but don't shut it down, charge, or reboot. Checking battery level manually, from time to time (battery applet *won't* give you correct readings, due to modules being not loaded). Always ensure that VDQ flag is 1, otherwise, you need to start back from scratch. Accidental reboot may or may not turn VDQ to 0, depending on circumstances.

4. When voltage drops to ~3300 mV, stop whatever you're doing on device and start monitoring it closely.

5. The goal now is to get under 3248 mV and stay there for at least 15 seconds, without voltage either going above, or too much under (less than ~2900 mV), causing device to "faint" due to low power. The most reliable - although, time consuming - way is to set screen to never dim, and/or enable flashlight - so device will consume steady ammount of current. Monitor voltage and VDQ.

6. When voltage dros below threeshold (3248 mV) and stays there for 15 seconds, VDQ will immediately turn to 0 and chip recalibrate.

7. Power device off via normal way, before it "faints" - if you miss that step, it *won't* spoil calibration, but you may get your /home filesystem corrupted. You better not miss this step, or you will give yourself quite a homework (see next steps). In case of failing it, for some reason, follow step 8. Otherwise, you're finished now - start using device normally.

8. (optional, in case of missing step 7)
This step require you to run latest cssu-thumb or cssu-testing. Precisely, it require updated e2fsprogs&friends, cause Maemo's vanilla ones were ancient and segfaulted mid-way, leaving filesystem in total mess.

Boot into any recovery console (backupmenu's one, Mentalist Traceur's one, Pali's one, etc), and:
Code:
fsck /dev/mmcblk0p2 -f -p
a) If it says (amongst other things) "<filesystem name> clean" - with or without "recovering journal" before - and exits, you're good to go. Power off, and you're finished. Start using device normally.

b) If it informs about fixing some things, but exits cleanly, see point a.

c) If it ends with something like "Unexpected inconsistency, run FSCK manually", do:
Code:
fsck /dev/mmcblk0p2 -f -y -v >> /path/where/you/want/log/saved/fsck.log
Ensure, that path where you save log isn't any temporary directory (that will get nuked after boot), as you may really need that log later.

Where to save, depends on the recovery shell you're using. If you have rootfs mounted, /path/where/rootfs/is/mounted/var/log/fsck.log is a good place. Using backupmenu's root console (and *only* after mounting rootfs via 'mountroot' command), it is /tmp/mnt/rootfs/var/log/fsck.log, If I remember correctly (you can use auto-completion via TAB).

When it's finished, repeat this point (8) from the beginning, and follow approriate sub-point.

8.1. After you boot into Maemo, check fsck.log you've create in point 8 - it will contain (amongst other things), pathes to files that were repaired/salvaged (connected to lost+found) during manual fsck repair. Check every file's integrity individually. In case it "vanished", check /home/lost+found, it may be sitting there. In case of problems, determine which package missing file depend to, and reinstall whole package.
---

Appendix:
To check VDQ flag and voltage conveniently, either use bq27200.sh script, or package BNF (the latter is my favorite method, but no surprise here, as I've created it ;) ).

Appendinx 2:
Don't get scared by ammount of text here - I tried to explain everything in details, and half of this (as it turned to be) tutorial is an emergency kit for worst-case scenario of filesystem corruption, due to device fainting of low power. By being at least basically aware of situation, you won't hit it, saving yourself half of this ;)

Cheers,
/Estel

peterleinchen 2019-11-23 20:53
Re: [Solved] No data or battery not calibrated
 
@Estel is long gone.

And I cannot remember how I did it earlier.
But what I remember is that putting in a new batterh let it start with double amount of capacity. I just left it run from full loaded down to empty and full load, empty...
for a few cycles (each cycle reduced off-capacity by half iirc)
but then it calibrated itself

Koiruus 2019-11-24 02:55
Re: [Solved] No data or battery not calibrated
 
Having double capacity shouldn't affect this as we are speaking voltages (in mV) and the device faints when voltage drops too low. And it drops when battery gets empty enough, regardless it's size. For example there is many capacities (in Ah) of batteries for cars, for example 65Ah or 130Ah. Regardless their size their voltage is around 12,8V when full and close to 12 when empty. I am no electrician/engineer so this is basically all my knowledge about elecricity, plus the usual facts: It's blue and hurts :D

Anyway, for me this kind of situation happened when I still had some battery module loaded, and it makes the device switch itself off because it detects the voltage is dropping too low for the device to operate. So requirement of the calibration is to prevent this happening by unloading the modules. You probably knew this already and I have no solution/ideas what to do. So I guess this was quite an useless post, but I'll publish it anyway..

biketool 2019-11-24 07:27
Re: [Solved] No data or battery not calibrated
 
I used to use a Mugen battery cover and a double-cell battery on several N900s.
I discovered that the pressure from the doubled up BL-5Js was flexing the system board and breaking the modem connection, leading to the no-SIM of death. It was really too bad as the phones were in great shape otherwise. I repurposed them as wifi tablets with a bunch of N64 and webOS games and gifted them out to kids.

bdbogart 2019-12-03 03:07
Re: [Solved] No data or battery not calibrated
 
I realized I did not have the power-kernel installed, so I did not have those modules to begin with, but that did not make a difference, device still faints before getting to 3.3v. I guess I'm stuck for calibration!

Koiruus 2019-12-03 19:55
Re: [Solved] No data or battery not calibrated
 
Ummm. Do you have Pali's BME Replacement installed? If not, you should install it first. Thread here https://talk.maemo.org/showthread.php?t=93183

bdbogart 2019-12-10 19:45
Re: [Solved] No data or battery not calibrated
 
Thanks all for the help. I've now given up, but this is what I ended up doing:

* Installed CSSU Testing (had stable before) (and reboot)
* Installed power kernel (and reboot)
* Installed Pali's BME replacement (and reboot)
* Unloaded battery kernel modules
* Changed battery to full such that VDQ = 1.

Things I noticed, BNF stopped working with the BME replacement, which seemed odd. Device still "faints" before (at?) 3.3v, so I could never calibrate.

I went back to the stock (testing?) BME... and I'll deal with the uncalibrated battery gauge.

Koiruus 2019-12-10 21:03
Re: [Solved] No data or battery not calibrated
 
Sounds odd. Usually the BNF stops working with BME replacement as/if battery is not calibrated, but starts working when you modprobe -r the battery modules. I think it's intended to work that way. And with bme replaced, you should be able to recalibrate the battery with bigger capacity. I have now switched to Fxtec Pro1, but when I was using n900 I used 1600mAh batteries and they were calibrated ok.

I still think that your device does not actually faint, but shuts down instead. Where the difference is that shutting down is intended and fainting is not. Fainting happens because the voltage have dropped too low for the device to operate, which makes the device to faint immediately, without for example unmounting partitions etc. And this causes very likely some damage. On the other hand, shutting down is intended, and is caused by the os recognizing too low (but not low enough to faint) voltage and shutting down before anything bad happens. This shutting down have set to happen before the voltage drops to dangerously low, and also before battery gets calibrated. Modprobe -r should prevent those safe systems working, but somehow you still have them running. I still have no skills to help you with this, but a pity that you gave up :( Did you try to use the bq2700.sh script instead of bnf? Don't know why it would make a diffence though. Yoy can find it here, along with some useful info http://talk.maemo.org/showpost.php?p...&postcount=846
Those instructions to calibrate battery are not succesful, however. You probably know this already, but here's the working procedure: http://talk.maemo.org/showpost.php?p...93&postcount=2

bdbogart 2019-12-23 19:54
Re: [Solved] No data or battery not calibrated
 
Thanks Koiruus,

I tried again, and finally success!!! Reinstalled Pali's BME removed the modules and let the battery slowly drain. I actually left it overnight by itself and I think it worked because with modules loaded BNF works and "calibration needed" is 0! The trick seemed to be a very very very slow drain. I actually let it drain overnight without using it at all, no sound, no display. It seemed that was just the low enough drain to get that 15s needed. Of course I'm not sure since I was not watching it!

http://www.ekran.org/tmp/Screenshot-20191223-105738.png

having advanced power installed was confusing things, but now that I removed that things look to be working well! thanks for the help everyone.

Koiruus 2019-12-23 22:57
Re: [Solved] No data or battery not calibrated
 
Quote:
Originally Posted by bdbogart (Post 1563643)
Thanks Koiruus,

I tried again, and finally success!!! Reinstalled Pali's BME removed the modules and let the battery slowly drain. I actually left it overnight by itself and I think it worked because with modules loaded BNF works and "calibration needed" is 0! The trick seemed to be a very very very slow drain. I actually let it drain overnight without using it at all, no sound, no display. It seemed that was just the low enough drain to get that 15s needed. Of course I'm not sure since I was not watching it!

http://www.ekran.org/tmp/Screenshot-20191223-105738.png

having advanced power installed was confusing things, but now that I removed that things look to be working well! thanks for the help everyone.
Great! But, is that screenshot after calibration? Because it says Battery capacity is 1140mAh. Shouldn't it be more?

bdbogart 2019-12-30 17:49
Re: [Solved] No data or battery not calibrated
 
hmmm. The battery says 2450mah on it... I tried calibrating again but it says the same thing, not sure how that # is calculated... I see the following:

Code:
~ $ cat /sys/class/power_supply/bq27200-0/charge_full_design
2056320
~ $ cat /sys/class/power_supply/bq27200-0/charge_full       
1138830
~ $
So the "design" charge looks correct. I used this battery without re-calibrating for quite some time (months and months) so perhaps I've damaged it's capacity by never letting it totally decharge after quite a few charge cycles.

sicelo 2019-12-30 19:07
Re: [Solved] No data or battery not calibrated
 
@bdbogart - the charge_full_design doesn't really mean anything on N900 (unless i'm too mistaken).

You will still need other discharge cycles to get your capacity properly calibrated, since the chip is believed to not allow capacity changes greater than 6% at a time.

Unless you're unlucky to have a fake battery.

bdbogart 2019-12-31 17:53
Re: [Solved] No data or battery not calibrated
 
Quote:
Originally Posted by sicelo (Post 1563892)
You will still need other discharge cycles to get your capacity properly calibrated, since the chip is believed to not allow capacity changes greater than 6% at a time.

Unless you're unlucky to have a fake battery.
hmmm. I did one more cycle and now the full charge value is 996mah! A difference of 13%? (1140-996)/1140 = ~0.126

The difference between 996 and 2450 is 6% increments is a quite a few cycles, especially if (as just happened) some cycles have the potential to decrease the apparent capacity...

Hopefully not a fake battery, though there does not seem to be any in stock any longer: https://www.amazon.ca/gp/product/B07B46XKZC


All times are GMT. The time now is 13:04.

vBulletin® Version 3.8.8