SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
xes has quit [Remote host closed the connection]
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
Gary_ has joined #maemo-leste
_Gary has quit [Ping timeout: 240 seconds]
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
Gary__ has joined #maemo-leste
Gary_ has quit [Ping timeout: 246 seconds]
Gary_ has joined #maemo-leste
Gary__ has quit [Ping timeout: 268 seconds]
joerg has quit [Ping timeout: 256 seconds]
joerg has joined #maemo-leste
fab_ has joined #maemo-leste
Gary__ has joined #maemo-leste
Gary_ has quit [Ping timeout: 268 seconds]
fab_ has quit [Quit: fab_]
ceene has joined #maemo-leste
fab_ has joined #maemo-leste
Gary__ has quit [Read error: Connection reset by peer]
<sicelo>
Wizzup: so today i made first call with telepathy ... went really well
<sicelo>
then i got an incoming call - for some reason it was not possible to accept the call. the phone rang, and vibrator turned on. i couldn't click the button. seemed to be the touchscreen issue i've mentioned before
<sicelo>
so i locked the screen and unlocked, and tried to accept call to no avail. i guess somewhere along the line, sphone got itself in some state where it just kept vibrating and showing the incoming call window. i think by that time, the actual call was gone, i.e. the call timed out because i did not pick it
<sicelo>
i ended up rebooting. next time i'll see if i can debug or something
xes has joined #maemo-leste
xes has quit [Quit: WeeChat 3.5]
xes has joined #maemo-leste
<Wizzup>
sicelo: interesting, d4, or?
mdz has joined #maemo-leste
mdz has quit [Client Quit]
mdz has joined #maemo-leste
<Wizzup>
sicelo: I do remember seeing this once, I will see if I can reproduce it
xs has quit [Quit: Cheers!]
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
xs has joined #maemo-leste
xs is now known as Guest1159
ac_laptop has joined #maemo-leste
xmn has quit [Ping timeout: 252 seconds]
ac_laptop has quit [Ping timeout: 256 seconds]
diejuse has joined #maemo-leste
ac_laptop has joined #maemo-leste
DFP has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
Wizzup: thx :)
<arno11>
btw i still have the hangup bug on n900, but that's the only one i noticed with sphone/telepathy/vcm
<arno11>
no PA troubles after calls
<LeePen>
What is the best/correct way to set light transitions on n900?
<arno11>
LeePen: imo the correct/easy way for that is to backup /usr/share/hildon-desktop/transitions.ini file and modify the original one
<LeePen>
arno11: thanks. And what are the recommended values for 'light'
<LeePen>
?
<arno11>
well, it depends if you want to keep a bit of transitions/effects/animations or not
<LeePen>
I am more interested in reducing slowness, and you highlighted this as a significant contributor.
<arno11>
so you can try the one in leste github (transitions OFF)
<sicelo>
or did it come after i enabled -devel? can't recall exactly now. otherwise i did nothing else to enable/select tp
<freemangordon>
sicelo: audio issues are not call related
<freemangordon>
well, at least call audio is not affected
Gary_ has joined #maemo-leste
<sicelo>
ok
<sicelo>
the audio issues you were talking about affect the ringtone?
<freemangordon>
mafw
<sicelo>
ok
_Gary has quit [Ping timeout: 268 seconds]
<sicelo>
i'll install pavucontrol tonight, and see tomorrow if there's anything weird going on with the mixers or something. otherwise i'll have to end the experiment for the time being
<sicelo>
oh but iirc call audio bypasses everything? can pavucontrol control it?
<Wizzup>
yes pavucontrol can by switching ucm profile
<Wizzup>
iirc
<Wizzup>
sphone switches ucm profile
<Wizzup>
telepathy-ring does not touch audio
<Wizzup>
which is why it was weird to me that this (tp-ring) would impact it at all
<sicelo>
yeah, i did mention it's not related to tp. was thinking it's the audio thing instead, but seems not either
<sicelo>
16:38 < sicelo> i have extra report: unfortunately there were many times that the other party did not hear me, but i always heard them
<sicelo>
16:39 < sicelo> i suppose it's that issue fmg reported?
<sicelo>
i actually doubt tp is responsible for any of the issues i experienced, because the UI problem with accepting the incoming call is likely somewhere ... TS or tklock, or something similar
<Wizzup>
ok
<Wizzup>
I was mostly checking this because you said that it started happening today
<sicelo>
i understand. well i haven't used the D4 in a while (borked install) ... yesterday i burned new image and transferred a SIM to it.
<sicelo>
i get frequent calls on this SIM (it's a work SIM)
<Wizzup>
this is on -devel?
<sicelo>
yes
<sicelo>
btw there's also something with mce(?) that causes kbd backlight to behave in an erratic manner ... coming on an off in an unexpected manner. i noticed this on N900 a while back, and the D4 is doing the same thing
* sicelo
will find time to open GH issues for this stuff, and hopefully investigate further as well
brabo has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
sicelo: (for hangup) if the other side closes the call, it stays active in sphone and the only way to hang up is killing sphone
<arno11>
if i close the call, no issue
<arno11>
and the call is closed on the other side
<sicelo>
if you ever get a chance in future, check what ofono reports after the remote end terminates the call
<arno11>
ah ok, i can try a bit later with my andro phone.
<sicelo>
a simple way is ... run `busctl tree org.ofono` after the remote party has terminated the call, while sphone still shows ongoing call. if "voicecall1" (or similar is listed), the problem is likely in ofono. if it's not listed, then very likely it's sphone
<arno11>
ok
<arno11>
btw this issue only happens with telepathy/vcm, otherwise, no troubles
<sicelo>
oh
fab_ has joined #maemo-leste
<sicelo>
i guess my suggestion was too simplistic then ... i *thought* you had this issue all along (i.e. even without tp)
<arno11>
ah ok
SystemError has quit [Ping timeout: 260 seconds]
SystemError has joined #maemo-leste
fab_ has quit [Quit: fab_]
<arno11>
btw it is amazing how n900 works well now with no overclock and the last tweaks :)
* sicelo
has still never overclocked his N900 ... must give it a go one of these days
<arno11>
videos, drnoksnes, pcsx, picodrive, all work smooth @600MHz max now
<arno11>
*with sound ofc
<arno11>
for example drnoksnes works now @50/60 fps constantly with sound @48KHz and @600MHz max (fullscreen 4/3)
<sicelo>
what changed?
<arno11>
mostly trackers OFF and transitions OFF
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
<arno11>
(see logs from yesterday)
<sicelo>
yes i read it :-)
<Wizzup>
having some of this in gh issues is probably helpful, just as a reminder and due to the nature of irc logs
<Wizzup>
I do want to investigate both tracker overhead and the startup overhead for qt you mentioned
<arno11>
yes indeed
<arno11>
ah ok cool
<sicelo>
Wizzup: on my N900, which also has tp, i don't get SMS's in either sphone or conversations ... but i guess something didn't go right with update or something, since it seems i got sms on D4, that went to conversations
<sicelo>
on N900, i can see the SMS if i monitor dbus
<arno11>
ah maybe your db is corrupted like it happened to me
<arno11>
when i did the update
<arno11>
*conversations update
<arno11>
sms didn't work for me too
<arno11>
deleting the db solved the issue
<arno11>
(automatically re generated)
<sicelo>
ah, i don't have any important messages to worry about
<arno11>
ok
f_ 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/.]
ac_laptop has quit [Ping timeout: 268 seconds]
arno11 has left #maemo-leste [#maemo-leste]
SystemError has quit [Remote host closed the connection]