System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
vectis has quit [Ping timeout: 252 seconds]
vectis has joined #maemo-leste
<tmlind>
Wizzup: i've noticed voice call audio often does not work on the first call but only works on the second call after booting.. i've mostly followed the mainline with the same old pending patches rebased, will try rebase again after -rc1
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
joerg has quit [Ping timeout: 260 seconds]
joerg has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
<Wizzup>
tmlind: ah, interested, I will try that as well then
Livio has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
<Wizzup>
interesting*
Madda has quit [Ping timeout: 255 seconds]
Madda has joined #maemo-leste
pere has quit [Ping timeout: 272 seconds]
Madda has quit [Ping timeout: 268 seconds]
Madda has joined #maemo-leste
Livio has quit [Ping timeout: 260 seconds]
arno11 has joined #maemo-leste
<arno11>
Wizzup: for ringtones not working (or randomly) on D4 and N900, i just figured out that it is a lack of read permission.
<arno11>
using chmod +r in MyDocs/.sound solved the issue (at least on my device)
<Wizzup>
interesting, they do work for me normally I think, what did you find?
<Wizzup>
hm
<Wizzup>
interesting.
<arno11>
i added comments to the 2 related issues on gh
<Wizzup>
ok
<arno11>
and it seems that it was the reason why the sphone UI was slow to start on N900 during incoming calls
<arno11>
now it starts quickly
<arno11>
it works really nicely now :)
<Wizzup>
strange, but good to know
<arno11>
now the only thing to solve is the 'hangup bug' (with vcm/telepathy) on N900. otherwise it works @100%
<Wizzup>
right
arno11 has left #maemo-leste [#maemo-leste]
f_ has joined #maemo-leste
mdz has joined #maemo-leste
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
f_ has joined #maemo-leste
f_ has joined #maemo-leste
f_ has quit [Client Quit]
f_ has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
noidea__ has joined #maemo-leste
noidea_ has quit [Ping timeout: 268 seconds]
Juest has quit [Ping timeout: 256 seconds]
System_Error has quit [Ping timeout: 260 seconds]
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
System_Error has joined #maemo-leste
System_Error has quit [Read error: Connection reset by peer]
SystemError has joined #maemo-leste
<sicelo>
arno11 and the pinentry dialog being slow
arno11 has joined #maemo-leste
<arno11>
sicelo: yeah, i wonder what's going on with it
mdz has quit [Ping timeout: 264 seconds]
<arno11>
btw what is the process/script controlling PIN stuff ?
<arno11>
i really don't understand why it starts so late, on fremantle it starts before H-D, not in leste (at least on N900)
<arno11>
and btw it is not slow to use (once loaded) without the bloody blur effect...
arno11 has left #maemo-leste [#maemo-leste]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 272 seconds]
arno11 has joined #maemo-leste
f_ has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
<arno11>
Wizzup: any idea why pinentry applet starts so late ?
<Wizzup>
it's part of xsession and we might have made it start later because it used to block the entire device from starting
<arno11>
ah ok
<arno11>
what is the xsession script involved btw ?
<arno11>
(sorry for that question, but i failed to find anything in xsession.d and .post lol)
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
it's startup-pin-query iirc
<Wizzup>
I can look a bit more in a bit
Juest has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
ok ty
<arno11>
ah, startup-pin-query is part of connui-cellular
<freemangordon>
and it is h-s-m that invokes pin-query dialog
<freemangordon>
because now we support SIM/modem hot-plug
<freemangordon>
so it cannot be part of boot process
<freemangordon>
so, if you modified h-s-m xsession script to start later, so will pin-entry dialog
<arno11>
ok i see now
<arno11>
ty
<arno11>
so we have to figure out what is wrong with h-s-m
<freemangordon>
right, though there is something wrong with some of the plugins I think
<arno11>
yes probably with the original ones (because the issue occurs from fresh install)
<freemangordon>
I really hope I will finally found time this Sunday for leste, Saturday is already occupied :(
<arno11>
ok :)
<freemangordon>
s/found/find/
<arno11>
brb
Livio has joined #maemo-leste
fab_ has joined #maemo-leste
akossh has joined #maemo-leste
arno11 has quit [Quit: leaving]
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
arno11 has joined #maemo-leste
<arno11>
looking @h-s-m debug logs, it seems that it looks at /home/user/.config dir to find status-menu.conf and .plugins and can't find them (ofc there not here)
<arno11>
there are in /etc/hildon-desktop/ according to h-s-m.install
<arno11>
indeed there are here
<arno11>
tomorrow i'll cp .plugins and .conf in .config dir and start h-s-m earlier on boot to see if it works better
akossh has quit [Quit: Leaving.]
<arno11>
well, i have a fresh install on another sd, probably better to try on it
<Wizzup>
I am preparing for a 2 day maemo stand
<Wizzup>
tomorrow and friday
<Wizzup>
so I might be around more than usual but maybe not for dev stuff :D
<Wizzup>
21:54 < arno11> looking @h-s-m debug logs, it seems that it looks at /home/user/.config dir to find status-menu.conf and .plugins and can't find them (ofc there not here)