We have moved to a new Sailfish OS Forum. Please start new discussions there.

CSD Tool assumes there are no batteries with capacity higher than original

asked 2015-08-04 19:17:00 +0200

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2015-08-04 21:45:07 +0200

V10lator gravatar image

As the title says the CSD Tool has a value hardcoded ("Design maximum"), causing the test to fail for no reason (when "Value" surpasses the hardcoded value, so when battery is fully charged as on screenshot) with better batteries like this:

image description

image description

And 12% charged ("Value" < "Design maximum") pass:

image description

edit retag flag offensive close delete


a nice one ;-)

pawel ( 2015-08-04 19:19:46 +0200 )edit

That's a laugh

lakutalo ( 2015-08-04 22:45:48 +0200 )edit

Hey guys, did you realize that the battery is for Desire 310 and you enter the CSD tool by dialing ##310##? Coinsidence? I think not. Half Life 3(10) confirmed. :)

jollailija ( 2015-08-06 14:43:40 +0200 )edit

i did check, does not work on HTC ;-)

pawel ( 2015-08-11 20:57:46 +0200 )edit

@pawel Uh, how is that related? I think you misunderstood my illuminati-HL3 joke

jollailija ( 2015-08-15 13:39:04 +0200 )edit

2 Answers

Sort by » oldest newest most voted

answered 2015-08-15 11:29:25 +0200

simo gravatar image

updated 2015-08-18 11:57:08 +0200

answer to a comment by @V10lator after he got valuable data directly from Wannsee-Electronics. Not an answer to the question itself:

@V10lator They served you either better or faster than Jolla served us in this question... Looking forward for similar chart on official Jolla battery, please Sailors. <3

You can open those files using SumatraPDF reader. I made an early check, comparing to kernel data, and unfortunately it's possible that Polarcell reaches 2100mAh with lower voltage than the official Jolla battery, meaning Jolla might report it as overcharged (CSD reading you got)

By later comment by @Giacomo Di Giacomo, this has nothing to do with actual overcharge, as the charging is stopped based on different factor (current)

Below: Polarcell (dotted curve, temperature unknown) vs. Jolla kernel data (note: maybe not the official battery itself, as kernel data might be fixed for any reasons - see the question linked above)

curve comparison Polarcell vs Jolla kernel

scaled to match with the earlier chart I posted as comment. Table data would have been easier, but we can be super thankful to Wannsee-Electronics for providing their test data - Please send them big thanks, maybe from all Jolla Phone users <3 <3

edit flag offensive delete publish link more


@simo so if I buy a Polarcell battery and continue my habit of charging to 85% I should be allright?

jollailija ( 2015-08-15 13:40:53 +0200 )edit

By this chart comparison, it seems Jolla might report the charging level exactly as same between 7% - 85%, and accurate enough even between 3% - 97%. Should be all right yes, but I just can't be 100% sure before data from Jolla.

simo ( 2015-08-15 13:50:00 +0200 )edit

@simo As a logical question: if the Jolla charges the battery with its built in parameters and comes to an "official" end at 100% with slow flashing led, shouldn't that be a guarantee that it's NOT overcharging? If the battery itself would stop the charging by using its safety circuit, Jolla should show less than 100% and shouldn't stop? So, if I see the led flashing in the morning, I can be sure not to overcharge the battery, can't I? (I'm using the polarcell continuously since the first post here and always do an overnight charge.)

Robomike ( 2015-08-16 23:47:14 +0200 )edit

@Robomike Your longer term testing is promising for the safety, great job there, but without more information about the official battery I really can't answer to you... Jolla's 100% is set to a point where Jolla official battery reaches 2100mAh, so it's not a quarantee for any other batteries (until proven 100% compatible, which I'm somehow trying to reach...) By the way, you can get some more battery information during different stages of charging via terminal, using command upower --monitor-detail in your testing. And thanks for joining us here :)

simo ( 2015-08-17 00:12:06 +0200 )edit

@simo Thanks for your answer. But, from a technical viewpoint, for the device it's impossible to know how much energy is stored, unless the battery wasn't completely empty once - which is very dangerous for Li-Ion-batteries and should be avoided in any case. Theoretically you may replace batteries with different charge state anytime, and the device shouldn't kill itself by overcharging. The only parameters the device can see are current, voltage and temperature. The end-of-charge voltage is fixed and has nothing to do with the nominal (imprinted) voltage. The device _may_ use the coded curve (the img above) to make a guess about the charging state, and if it's well programmed, it may learn something about the battery's condition by comparing the voltage/current-position with some saved values. But it will never know the exact charge. (Btw: the curve plot in your initial answer uses an odd ordinate identifier. It should be "voltage", not "current". We should try to minimize confusion :) )

Robomike ( 2015-08-17 09:35:32 +0200 )edit

answered 2015-08-04 19:45:23 +0200

simo gravatar image

Not a bug, but a feature... as Jolla Phone seems to be, unfortunately, designed to be used with official Jolla battery only :(

edit flag offensive delete publish link more



The "capacity" of 102.21% (>100) is most probably the reason that makes the test fails. But indeed only because the app thinks (in a hard-coded way) that 100% <=> Official Jolla battery capacity. By the way, isn't the CSD tool available a FOSS? Isn't it capable of running on community port on different devices? Someone should have noticed this bug already I think :X (as this tool would be great to see if you drivers work while you port the system to a new target)

Elioty ( 2015-08-04 20:02:39 +0200 )edit

@Elioty It reaches a capacity of 102.21% cause it calculates with the hardcoded value "Design maximum" instead of the one provided by the battery itself "Maximum".

According to https://wiki.merproject.org/wiki/SailfishOSS it's not.

//EDIT: Also it's not the capacity value failing. When "Value" falls below "Design Capacity" (caused by discharging the battery) the test passes while "Capacity" still shows 102.21%.

//EDIT2: @simo Still it shouldn't fail for non technical reasons. "Value" > "Design maximum" isn't technical. We need an answer from a sailor here.

//EDIT3: Even if for some weird reason the statement from EDIT2 would be technical the test should fail if the reported "Maximum" > "Design maximum" but that's not the case. So no matter how you look at it; there's a bug. ;)

V10lator ( 2015-08-04 20:40:26 +0200 )edit

Capacity is (and should be) calculated from the Design maximum value, which is set into the system by Jolla, no settings offered to change it (hence a feature: Jolla is a phone for 7.98Wh batteries (3.8V*2.100Ah) by design)

There is a workaround to manually change this value using dbus command, writing a new DesignFull value by what's expected from the battery, but before using such workaround I'd wait for information if the battery is safe to use in the first place.

simo ( 2015-08-04 21:52:26 +0200 )edit

But it's not about "Capacity" but "Value" (see also latest screenshot).

So either this is a bug or you just found the real root and this is just a symphtom. Bug no matter how you look at it... ;)

V10lator ( 2015-08-04 22:01:21 +0200 )edit

You didn't get it. Battery is seen as overcharged if the Value (current charge) > Design maximum (max accepted charge). Test SHOULD fail in this case.

simo ( 2015-08-04 22:13:11 +0200 )edit
Login/Signup to Answer

Question tools



Asked: 2015-08-04 19:17:00 +0200

Seen: 2,895 times

Last updated: Aug 18 '15