<arno11>
sicelo: any idea why sometimes idle current draw increases @10mA when i unplug charger ?
<sicelo>
no idea
<sicelo>
I only ever heard that musb is a complicated mess that everyone doesn't want to touch with a ten foot pole
<arno11>
(example: idle 48mA, plug to wall charger, unplug charger, then idle @58mA)
<arno11>
ok i see :)
<sicelo>
maybe we have problems in the interaction between isp1707, bq24150a, and twl4030 ... races perhaps?
<arno11>
maybe yes
<sicelo>
so once it increases, it remains high until next boot? or there's some way to 'recover?
<arno11>
reboot is needed or plug-unplug sometimes solves the issue
<buZz>
'ten foot pole' is one of my favorite bands ;)
<Wizzup>
sicelo: could this be related to your upower whitelist removal?
<sicelo>
no, it was like this already for a long time (same as the other issues, such as never reporting full)
<Wizzup>
ok
<Wizzup>
maybe spinals old patches give some hints
Daanct12 has quit [Quit: WeeChat 4.4.2]
xmn has joined #maemo-leste
<sicelo>
he fixed the issues in upower, which is alright. i am fixing them in kernel, so things are more likely to work ootb
<sicelo>
e.g. after fixing the charger (bq24150) in kernel, upower immediately handled it properly, hence we no longer needed the blacklist
<sicelo>
upower itself isn't the nicest software around, so yeah, some fixes will most likely still be needed. anyway, the cl
<sicelo>
*the more conformant our drivers, the more likely we can use upstream upower, for example.
<Wizzup>
agreed
ceene has quit [Remote host closed the connection]
fab_ has quit [Quit: fab_]
fab_ has joined #maemo-leste
System_Error has quit [Ping timeout: 260 seconds]
System_Error has joined #maemo-leste
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 244 seconds]
akossh has joined #maemo-leste
uvos__ has joined #maemo-leste
<sicelo>
by the way, although I haven't verified it yet, I think that since we have a logind session now, upower probably shuts down devices once it thinks we're out of power
<Wizzup>
we should check if this is still mce controlled, it should be I think
<Wizzup>
I think you can turn this off in some config file
<Wizzup>
see /etc/logind/logind.conf.d/maemo-leste.conf
<Wizzup>
(might not be enough, but hey)
DFP has quit [Quit: Leaving]
ikmaak2 has quit [Ping timeout: 248 seconds]
ikmaak has joined #maemo-leste
<sicelo>
is it just my droid 4 or there's boot issues somewhere? i frequently find mine hangs at boot, with faint backlight
<sicelo>
i know my battery is kaput ... maybe it's just that?
<buZz>
sicelo: not SDcard full?
<buZz>
i havent had 'hung on boot' often on droid4 but sometimes, usually had such issue
<sicelo>
nah, it's not SD
<buZz>
alright
<buZz>
one of these days i still want to make a usb-uart cable for the droid4
<sicelo>
easy. make for N900 😜
<sicelo>
and make for Librem5
<freemangordon>
sicelo: no issues booting d4 whatsoever, besides with flat battery
<freemangordon>
which happens occasionally now shotdown does not work on 6.6
<freemangordon>
*shutdown
<freemangordon>
flat == *really flat*
<sicelo>
right. I suspect my battery is just excessively worn.
<buZz>
one of these days i'm gonna retry stuffing a LG cell on the droid4 BMS
fab_ has quit [Quit: fab_]
mdz has quit [Remote host closed the connection]
akossh has quit [Quit: Leaving.]
<Wizzup>
sicelo: maybe charge mode is hitting you?
<Wizzup>
or what fmg says
<sicelo>
no, charge mode works fine. this looks like kernel doesn't even start.
<Wizzup>
yeah that sounds like battery issues
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Read error: Connection reset by peer]
uvos has joined #maemo-leste
<uvos>
nah
<uvos>
what sicelo sees is not related to his battery
DFP has joined #maemo-leste
<sicelo>
what's up then?
xmn has quit [Ping timeout: 260 seconds]
<uvos>
when the battery is below some voltage threshold and you boot via usb plug the device hangs before the display is initalized, this was true before 6.6 but 6.6 now hangs on shutdown sometimes so you see it now. i dont know any more than that, the issue is ofc resistant to debugging since you cant trigger it while having any output from the deivce at all.
<uvos>
since it triggers only with usb plugged
<sicelo>
yes i'm getting this when the device boots after connecting to charger
<uvos>
the only way i know to even theoreticly debug this issue would be to bitbang a uart on the gpio 2 pins on the back of the device and use that for console output
arno11 has left #maemo-leste [#maemo-leste]
<buZz>
maybe that was what i was hitting with chargers too, prevented with a usbcondom?
Juest has quit [Ping timeout: 248 seconds]
uvos__ has quit [Remote host closed the connection]