It didn’t help. The lowest value of the lower limit is 5% in BB and my battery is only 4%, maybe it’s not related, I set the upper limit above 90%
devel-su
mcetool --set-charging-mode=enable
After trying the BB app, could you also try this command? And what I’ll say is, don’t give up hope yet; if possible, it would also be good to stop by phone shops in your country, act like you’re going to buy a charging cable, and try the charging cables there. At least then you can see whether the same thing happens there too. And if this issue is hardware-related, then this is a very risky situation not just for you, but for many people right now.
Not only that. It’s also dangerous. Lithium based batteries are picky especially for charging.
Actually, it would be really good if that lithium battery could be kick-started once and properly take a charge all the way up to 100%, but…
HW issue is unfortunately possible IMO.
It’s also possible that HW charging controller or something related is stuck in some strange state. In that case it should charge after battery removal for at least 30 seconds.
True, but we don’t know if battery itself is the root cause. I highly doubt that.
It doesn’t work without restarting, I’ll try restarting.
EDIT: It doesn’t work even after restarting. I’ll be done with mobile trials in a moment, 3% left
Despite the commands we entered with primary_chg, it actually isn’t taking any charge at all. The possibility of it being a hardware issue is actually quite high too. It would be good if Jolla looked into this a bit. I hope it isn’t a chronic problem affecting many phones.
Yes, this is not an issue that can be solved with coding. When it was charging normally before, did you go into some different setting in Battery Buddy and mess around with anything? Though even when we bypassed it, it still didn’t take charge…
Also, I suggest going to a phone repair shop tomorrow and trying the cables there for a while. Who knows, maybe it might work.
You could even show the phone repair technicians the pogo pins on the back, tell them how much voltage they should receive, and try charging it from there.
I hope I’m not getting excited prematurely, disconnecting the battery for about 1 min is the solution to my problem, it’s already at 8%! Good tip, thanks.
EDIT: Battery Buddy turned off charging at the set 85%.
I will keep an eye on the discharge, I consider it resolved for now.
Thank you all, you helped me not only with advice but also with positive energy, great forum! ![]()
I will mark the find as solved when it is charged to full capacity.
It was terribly exciting to follow. I’m glad it also had a happy ending!
I think the problem has clearly been sorted out now
Honestly, I’m happy about it too. I hope you use it without any issues. Have a nice day, my friend.
It’s charging, it’s already at 45%, how little is sometimes enough for us to be happy, isn’t it!
I wish you the same, many thanks again! ![]()
Happy for you. I do hope that your issue happened because of some stray cosmic ray bit flip or any other fluke and not because of some odd shortcoming of charge controller.
Thanks, I hope so too.
Does the fix still works for you? I had the same problem and to remove the battery and wait was working for one day. It’s now the same again. When “charging” the battery part of the phone makes some noise that’s reminds me of coil whine.
I heard from a similar case. Before every loading first the battery must removed.
It is open issue!
Yes, it’s been working for me since then, I haven’t had this error again.
For me it is not working. I tried to fix with mcetool, with echo 0 and with removing the battery. I don’t use battery buddy. I use the battery settings in the system settings. Sometimes I plug the cable, then I get the message “don’t forget to disconnect the cable”.
The status says always that the battery is discharging.