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

Charging jolla C with charger from jolla1, AIDA64 show USB port instead A/C power.

asked 2016-08-26 07:48:19 +0300

Schturman gravatar image

updated 2016-09-07 11:44:11 +0300

jiit gravatar image

I got my Jolla C two weeks ago. I charged it with charger from Jolla1, and when it finished, I got message about full battery and charging stopped automatically. Nice feature...
Now in this two weeks I noticed that when charging reach 100% it show the message about full battery, but charging is not stops. I checked with AIDA64 app and it show me "Power source: USB port" instead "A/C power" like on Jolla1 and Jolla Tablet.
Can someone check/approve if this what it should be on jolla C or my device have problem ?

edit retag flag offensive close delete


Looks like you need to report this BUG to Finalwire, not Jolla :D

coderus ( 2016-08-26 18:22:15 +0300 )edit

Sadly to know that....

Schturman ( 2016-08-26 19:56:45 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2016-10-17 15:05:04 +0300

spiiroin gravatar image

updated 2016-10-17 15:14:24 +0300

I kind of managed to reproduce this. But since it required really careful fiddling with the usb cable, I wonder if what I saw is the same thing that has been reported?

The usb connection state & mode selection is done by usb-moded process. The inputs it sees and actions it takes can be debugged for example by logging into the device via ssh over wlan and then running usb-moded in verbose debug mode:

systemctl stop usb-moded ; usb_moded -DT

When charger is connected usb-moded is supposed to see dedicated charger profile udev event, for example:


If cable is inserted slowly, the initial detection can go wrong (leads to ui level problem - the mode selection dialog stays there even though mode can't really be seletected), but charging still works.


However, if I really carefully do the insertion, it seems that it is possible to end up not getting the final USB_DCP event -> usb moded is left thinking that it is connected to a pc instead of charger. In which case the charging just does not commence regardless of the actions taken by usb-moded.

I tried this with a Jolla1 charger, few Samsung/Nokia chargers and couple of no-name cheap ones: If I'm careful enough, I can make it happen with all chargers. But if I just plug the cable in, charging works with all of them.

edit flag offensive delete publish link more



We had that with Jolla1 already. If you manage to plug it in too slow, any charger is recognized as PC-USB and charging does not start eventually.

chemist ( 2016-10-17 16:33:47 +0300 )edit

With JollaC I can make the "does not charge" happen maybe 1/3 or 1/2 tries (by carefully observing the usb-moded output and intentionally doing the cable connect "as wrongly as possible"). While I managed once to do the same with Jolla1, it is definately as easy as with JollaC (physical difference in usb connector or something perhaps).

But in any case it is different from getting temporary "is pc" event soon followed by "is charger" that occurs now and then when attaching the cable normally. At least I've not gotten the device in a state where it would not charge in these cases. (The ui state and to some extent usb-moded itself does not act as I would expect in these situations -> filed https://bugs.merproject.org/show_bug.cgi?id=1677 for that).

So this leaves me wondering what the issue reported here in TJC is actually about:

  1. This quite hard to reproduce cable connect issue leading to inability to charge
  2. Confusion over charging vs not-charging vs not-draining-battery in battery-full situations
  3. Something completely else
spiiroin ( 2016-10-18 09:22:40 +0300 )edit

answered 2016-08-26 09:08:40 +0300

mirumger gravatar image

I had a similar experience with different chargers and Jolla C. After plugging the charger to the USB port I was asked if I would like to open a data connection or only charging. Independent of the choice the charging didn't start. This behavior didn't change after reboot.

edit flag offensive delete publish link more


Hmmm, looks like a bug :/ what os version you use ? I'm on

Schturman ( 2016-08-26 10:08:01 +0300 )edit

This may related also to the plug design and the first detected pin when the cable is inserted, see the first two answers of these to questions: https://together.jolla.com/question/9430/charger-recognised-as-usb-cable-and-charging-doesnt-begin/https://together.jolla.com/question/78517/power-socket-connection-pops-up-usb-connection-type-dialog/

Damien Caliste ( 2016-08-26 11:03:48 +0300 )edit

Hmmm, interesting... When I connect the cable to jollaC the another end of cable already connected to wall power supply. It start charging without any problem but like I said it detected as USB port and I don't get the message about "charge only", "pc connection" etc... It happens sometimes, but most of the time no.
Now I will try first connect cable and after this to the wall power supply. Will see...

Schturman ( 2016-08-26 11:42:52 +0300 )edit

Ok, tested it, but it still detected as "USB port" :/ I changing title to BUG.

Schturman ( 2016-08-26 13:50:16 +0300 )edit

If you're on I'm afraid this is not officially a "bug"

jiit ( 2016-09-07 11:44:05 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2016-08-26 07:48:19 +0300

Seen: 876 times

Last updated: Oct 17 '16