<sicelo>
with those in place, the battery icon on status stops animating when charge full, and the green led works (at least on N900)
<sicelo>
arno11: you can also test :-)
SystemError has joined #maemo-leste
stack_overflow has quit [Ping timeout: 255 seconds]
<sicelo>
to test the updated packages without rebooting, (1) sudo rc-service mce stop, (2) sudo pkill -f upower, (3) sudo rc-service mce start
xmn has quit [Ping timeout: 272 seconds]
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
joerg has quit [Ping timeout: 240 seconds]
joerg has joined #maemo-leste
<tmlind>
freemangordon: seems like that should work though.. at least the wake up enable bit gets set when omap-usb-host is runtime suspended
mdz has joined #maemo-leste
fab_ has joined #maemo-leste
duuude has joined #maemo-leste
duuude has quit [Ping timeout: 272 seconds]
duuude has joined #maemo-leste
fab_ has quit [Ping timeout: 252 seconds]
akossh has quit [Quit: Leaving.]
akossh has joined #maemo-leste
<freemangordon>
tmlind: yes, but no interrupt
f__ has joined #maemo-leste
f_ has quit [Ping timeout: 268 seconds]
f__ is now known as funderscore
xmn has joined #maemo-leste
mdz has quit [Ping timeout: 256 seconds]
duuude has quit [Ping timeout: 255 seconds]
duuude has joined #maemo-leste
pere_ has quit [Ping timeout: 256 seconds]
duuude has quit [Read error: Connection reset by peer]
noidea_ has joined #maemo-leste
akossh has quit [Quit: Leaving.]
<sicelo>
i have internet problems today for some reason, so i'm struggling with updating my git repositories for droid4-linux. i have a patch that i sent as an issue. https://github.com/maemo-leste/droid4-linux/issues/7
<sicelo>
please review and merge ... i'll also get it ready for upstream
<freemangordon>
sicelo: why not send it to upstream?
<freemangordon>
ah, sorry
pere_ has joined #maemo-leste
<sicelo>
i would like it to hit Leste in the meantime, since of course upstream will take a while. no idea as well if they'd decide to backport it to the kernel we're on
<sicelo>
it fixes that issue with charging animation never stopping while a charger is connected, even when battery is really full
pere_ has quit [Ping timeout: 268 seconds]
noidea_ has quit [Ping timeout: 255 seconds]
<freemangordon>
sicelo: yeah, I understand what it is used for, the point is that we can backport it easily after upstream comments on it. And that usually happens in 1-2 days
<freemangordon>
and at least I will not have time soon to test it :(
funderscore is now known as f_
<sicelo>
let's see after i get a chance to refresh my repos
pere_ has joined #maemo-leste
pere_ has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
<Wizzup>
freemangordon: we often include patches before they go to upstream fwiw
<sicelo>
the thing is ... in status-area-applet-battery, he eventually reverted it
<sicelo>
i'll be working on dropping the n900-related blacklist entries, so i was wondering about the one for d4
<Wizzup>
(will check after dinner)
<freemangordon>
Wizzup: I know
<freemangordon>
I don't object, just saying that perhaps review will happen faster if sent to upstream :)
<tmlind>
freemangordon: maybe the kernel driver for qmi does not handle usb suspend so the modem won't know to initiate a wake-up? i'd asssume the pad wake-up event works just fine..
<tmlind>
freemangordon: it could be the kernel driver just tells the qmi modem to shut up while suspended..
<freemangordon>
could be, any idea where to look in?
<freemangordon>
this is option driver?
<freemangordon>
or cdc-wdm?
<freemangordon>
maybe I can connect my ec20 to d4 to see what will happen
<freemangordon>
tmlind: ^^^
<freemangordon>
does it make sense to write to the ML?
<tmlind>
freemangordon: no idea where to look.. yeah maybe asking the qmi folks would help or try to test with your usb modem on a pc with wakeup and autosuspend enabled
<freemangordon>
also, do you know how it behaves with vendor kernel?
<freemangordon>
I was not able to make it suspend when connected to my laptop
<tmlind>
freemangordon: afaik the android kernel uses the gsmmux for everything except for cell data
<freemangordon>
yeah
<freemangordon>
do you have any idea why would it not suspend when connected to PC?
<tmlind>
testing with a usb mouse with autosuspend and wakeup enabled on some similar device could help..
<tmlind>
freemangordon: did you enable d4 modem autosuspend (and wakeup) on your pc via sysfs?
<freemangordon>
autosuspend is enable (200 ms for the modem, 0 ms for the port)
<freemangordon>
wakeup is disabled
<freemangordon>
*2000 ms
<freemangordon>
but runtime_status stays active
<freemangordon>
the same happens in leste VM
<freemangordon>
maybe because kernel there is older, dunno
<tmlind>
so you did echo auto on pc?
<freemangordon>
control?
<tmlind>
yeah
<freemangordon>
oh, wait, it is on
<freemangordon>
lemme try
<tmlind>
ok
<tmlind>
so i think after you enable autosuspend on some usb device like a mouse, the mouse will send the k-state wake when you click on a button
<freemangordon>
yeah, ok, ec20 is suspended now
<tmlind>
ok
<freemangordon>
will try with d4, gimme a minute
<tmlind>
so then you need some command to remotely get modem(s) to do something, like send them sms?
<freemangordon>
hmm, will take more time
<freemangordon>
I need to add my patches in VM ofono
<tmlind>
ok
<freemangordon>
otherwise it is easy to test it, RSSI gets reported on every change
duuude has joined #maemo-leste
<freemangordon>
ok, will let you know what I test it, most-probably tomorrow as otherwise GF will get angry on me :)
<freemangordon>
*when I test
<tmlind>
yeah ok, maybe check with a usb mouse too if modems won't work for wake-up
<freemangordon>
ubuntu kernel on my laptop refuses to suspend it :(
<freemangordon>
tmlind: what happens on d4 seems to happen in the VM when modem gets suspended
<freemangordon>
no wakeup happens, despite it is enabled
<freemangordon>
I enabled wakeup on both modem and its parent
<freemangordon>
to no use
<tmlind>
ok, also for your usb qmi modem?
<freemangordon>
lemme check with it
<freemangordon>
tmlind: yeah, looks like the same
<freemangordon>
so most-probably qmi driver does not properly support suspend
<freemangordon>
:(
<freemangordon>
tmlind: ^^^
<freemangordon>
ttyl
<tmlind>
yeah ok ttyl
<tmlind>
freemangordon: maybe it's related to the needs_remote_wakeup in usb drivers, at least qmi_wwan_manage_power() uses it
<Wizzup>
sicelo: re your questions, I don't really know, maybe we can do without?
<sicelo>
sure. i can't think of a reason too. and yes, spinal did revert it in status-area-applet-battery. i'll drop it in an MR i'm yet to submit, while dropping the others. only bq24150 will remain in blacklist
<sicelo>
i'll fix the kernel driver for that, and the upower problem will fix itself