00:15
Livio has quit [Ping timeout: 264 seconds]
00:29
Wikiwide has quit [Remote host closed the connection]
00:30
Wikiwide has joined #maemo-leste
01:33
Wikiwide has quit [Remote host closed the connection]
01:33
Wikiwide has joined #maemo-leste
01:33
Wikiwide has quit [Read error: Connection reset by peer]
01:38
Wikiwide has joined #maemo-leste
01:40
xmn has quit [Quit: ZZZzzz…]
02:28
Juest has joined #maemo-leste
03:07
Juest has joined #maemo-leste
04:08
joerg has quit [Ping timeout: 252 seconds]
04:09
joerg has joined #maemo-leste
04:13
xmn has joined #maemo-leste
04:48
Wikiwide has quit [Ping timeout: 264 seconds]
04:52
Wikiwide has joined #maemo-leste
05:17
Guest48 has quit [Quit: Client closed]
05:51
Wikiwide has quit [Remote host closed the connection]
05:51
Wikiwide has joined #maemo-leste
07:00
System_Error has quit [Remote host closed the connection]
07:05
System_Error has joined #maemo-leste
07:23
Wikiwide has quit [Remote host closed the connection]
07:24
Wikiwide has joined #maemo-leste
07:40
Livio has joined #maemo-leste
08:25
arno11 has joined #maemo-leste
08:28
<
arno11 >
Wizzup: i tried 6.6.36 and now call audio works. in fact everything seems to work but something still seems to slowing down Qt5
08:29
<
arno11 >
conversations is sometimes very slow to launch and use, same for hamsterfiler and calendar. but that's totally random
08:31
<
arno11 >
for calls, audio works but sphone is unusable: when you receive a call, the caller UI is too slow to appear
08:31
<
arno11 >
(sometimes it's ok, but again things happen randomly)
08:35
<
arno11 >
ah, and i got again an error during kernel install: dkms failed to find headers for 6.6
08:35
<
arno11 >
(but headers are ok)
08:41
<
arno11 >
btw i didn't notice any process burning the cpu or using too much RAM
08:46
<
arno11 >
(*troubles with sphone happen with qtloop, i didn't try without but i'll doublecheck later and i suppose it will be ok without any Qt stuff)
08:54
arno11 has left #maemo-leste [#maemo-leste]
09:29
<
Wizzup >
arno_11: maybe you didn't install/upgrade the header package again
09:38
akossh has joined #maemo-leste
09:58
xmn has quit [Quit: ZZZzzz…]
10:12
arno11 has joined #maemo-leste
10:14
<
arno11 >
Wizzup: nope, headers install/upgrade is ok
10:14
<
Wizzup >
strange...
10:14
<
Wizzup >
let me upgrade on my phone
10:14
<
arno11 >
but i found on the web that 6.6 could cause troubles with swap
10:15
<
arno11 >
and indeed, decreasing swappiness seems to be a workaround
10:15
<
Wizzup >
hm, so they didn't solve it yet in 6.6.36 eh
10:16
<
Wizzup >
you'd assume they would fix these swap issues with stable point releases
10:19
<
Wizzup >
uvos: yeah so even on 6.6.36 the hotspot doesn't work, but it works on 6.1.y :D
10:19
<
Wizzup >
arno11: ok I also see the header warning
10:24
<
arno11 >
weird, now with swappiness=10, the N900 seems very stable and fast like 6.1.76
10:25
<
arno11 >
swappiness=10 was previously unusable btw, too agressive
10:25
<
arno11 >
maybe the way it works has been changed again (pourcentage vs agressivity)
10:27
<
arno11 >
*i mean too agressive on 6.1 or older
10:29
<
Wizzup >
what was your src on 6.6 changing swap behaviour?
10:29
<
Wizzup >
keep in mind that on this latest version I also enabled a bunch of debugging stuff
10:29
<
Wizzup >
I don't think it will really slow down anything (it's just some printks that are optionally enabled) but who knows
10:29
<
Wizzup >
(but again, it is very unlikely to be the cause)
10:30
<
Wizzup >
I enabled this so that I can try to debug call audio on d4
10:31
<
Wizzup >
brb ~10-15 mins
10:47
<
arno11 >
maybe it is worth a try to disable the debugging stuff
10:53
<
Wizzup >
arno11: it is 100% not that
10:53
<
Wizzup >
since you saw this also with an earlier build that didn't have it
10:55
<
arno11 >
ah yes indeed
10:56
<
arno11 >
so we should have a deeper look @swap imo
10:57
<
Wizzup >
if a different setting works, is that enough, or?
10:57
<
Wizzup >
or is maybe zram not available even though you normally use it, or?
10:57
<
arno11 >
good questions
10:58
<
arno11 >
swappiness=10 is enough atm but multitasking with heavy apps is impossible
10:58
<
arno11 >
and for zram, i don't know
11:00
<
arno11 >
i've never understood what's going on with zram and Leste tbh
11:03
<
Wizzup >
well, you didn't use it right?
11:04
<
Wizzup >
it would show up as additional swap them
11:05
<
arno11 >
ok so it is not activated by default
11:05
<
Wizzup >
it might be :)
11:06
<
Wizzup >
I can check in a bit - have to go for a bit again
11:06
<
arno11 >
ok no probs
11:20
<
arno11 >
according to syslog, zram starts on boot and add /dev/zram0
11:21
<
arno11 >
but it doesn't appear in fstab
11:22
<
arno11 >
it appears in /dev/
11:26
gnarface has quit [Read error: Connection reset by peer]
11:33
gnarface has joined #maemo-leste
11:35
Livio has quit [Ping timeout: 272 seconds]
11:43
<
arno11 >
hm, according to irc logs (fmg, uvos), not using zram is normal on N900
11:46
<
arno11 >
so i'll rather have a look on possible kernel changes with vm stuff
11:58
Livio has joined #maemo-leste
11:58
<
Wizzup >
arno11: ok, well, I want to really try to take another look at call audio and at least write a report to tmlind and others
11:59
<
Wizzup >
hopefully we can figure it out
11:59
<
Wizzup >
call audio n d4 that is
12:00
<
arno11 >
yeah that's definitely a priority
12:03
<
arno11 >
i'll continue to 'investigate' on swap/vm stuff and LYK
12:12
Juest has quit [Ping timeout: 268 seconds]
12:15
pere has quit [Ping timeout: 268 seconds]
12:23
Juest has joined #maemo-leste
12:27
pere has joined #maemo-leste
12:30
Wikiwide has quit [Remote host closed the connection]
12:30
Wikiwide has joined #maemo-leste
12:34
Livio has quit [Ping timeout: 240 seconds]
12:46
pere has quit [Ping timeout: 260 seconds]
13:00
arno11 has left #maemo-leste [#maemo-leste]
13:05
Wikiwide has quit [Remote host closed the connection]
13:06
Wikiwide has joined #maemo-leste
13:13
gnarface has quit [Quit: Leaving]
13:27
gnarface has joined #maemo-leste
13:33
Wikiwide has quit [Remote host closed the connection]
13:33
Wikiwide has joined #maemo-leste
13:53
Wikiwide has quit [Ping timeout: 264 seconds]
15:32
xmn has joined #maemo-leste
16:12
pere has joined #maemo-leste
16:20
pere has quit [Ping timeout: 260 seconds]
16:51
Livio has joined #maemo-leste
17:02
mdz has joined #maemo-leste
17:10
arno11 has joined #maemo-leste
17:13
<
arno11 >
Wizzup: ok, for 6.6 the culprit is h-s-m again and again...so no new issue. it is just worse
17:14
<
arno11 >
i mean, usually i killall h-s-m after boot to restart it properly. it doesn't work anymore
17:14
<
sicelo >
btw hsm is?
17:15
<
arno11 >
hildon-status-menu
17:15
<
sicelo >
um, what's wrong with it?
17:15
<
arno11 >
don't know
17:15
<
sicelo >
i mean - what do you observe?
17:16
<
sicelo >
i don't recall having issues with it
17:16
<
arno11 >
pin entry freeze, availibility or other plugin buttons not visible
17:16
<
Wizzup >
the pin entry is not part of h-s-m
17:17
<
arno11 >
it is now according to fmg
17:17
<
Wizzup >
buttons not being visible means that it crashed prior and loaded only 'safe' plugins
17:17
<
sicelo >
yes, i have the pin entry issues. but haven't yet had problems with status
17:17
<
Wizzup >
I think we just need a core dump to see what happens
17:17
<
Wizzup >
I think fmg was working on enabling those
17:17
<
Wizzup >
he should be back tomorrow
17:17
<
sicelo >
arno11: what plugins do you have on hsm?
17:17
<
sicelo >
i have none.
17:18
<
arno11 >
i just do have FB
17:18
<
arno11 >
but even without it, it is buggy
17:18
<
Wizzup >
that's not a hsm plugin fwiw, that's just part of the general status plugin
17:18
<
arno11 >
oh yes indeed
17:19
<
arno11 >
i just have original plugins
17:19
<
sicelo >
i want to work on wpa_supplicant stuff at some point
17:20
<
Wizzup >
better error messages? :D
17:20
<
sicelo >
hehe, well first, signal strength
17:21
Livio has quit [Ping timeout: 246 seconds]
17:21
<
Wizzup >
wait, this works, doesn't it?
17:21
<
sicelo >
icd doesn't report correct signal strength - only reports whatever was the strength when the connection was established
17:21
<
Wizzup >
are you sure?
17:21
<
Wizzup >
that's very strange, I've seen that number change frequently
17:21
<
sicelo >
quite sure, yes
17:22
<
Wizzup >
maybe this broke from beowulf->chimaera
17:23
<
sicelo >
i don't think it ever worked correctly. there are some dbus signals we should subscribe to
17:24
<
Wizzup >
I've definitely seen that number change in the status applet
17:24
<
Wizzup >
but I believe you
17:24
<
Wizzup >
shouldn't be too hard to check I think
17:24
<
sicelo >
so yes, the number will seem to change because when making a new connectio , the correct strength will ne recorded
17:24
<
Wizzup >
do you use the wifi signal applet?
17:24
<
sicelo >
but as long as the connection is established, it won't change
17:24
<
sicelo >
no, i dont use the applet
17:24
<
Wizzup >
ok, might be worth checking to see if it works with that just in case
17:25
<
Wizzup >
in src/wlan.c see
17:25
<
sicelo >
i think it won't... i looked at its source. i
*think* it asks icd
17:25
<
Wizzup >
static void wlan_statistics(const gchar * network_type,
17:25
<
Wizzup >
enum icd_nw_levels signal = map_rssi(info->signal);
17:25
<
Wizzup >
stats_cb(link_stats_cb_token, network_type, network_attrs, network_id, 0, /* time_active */
17:26
<
Wizzup >
hm, yeah, ok, it doesn't look like info->signal gets updated
17:27
<
sicelo >
i meant to update that issue with the signal we should subscribe to, but got sidetracked
17:27
<
Wizzup >
current_bss_info should contain a new signal though
17:28
<
arno11 >
Wizzup: so excepting h-s-m troubles we already had before, i don't see any issue with 6.6 atm :)
17:28
<
Wizzup >
arno11: right, well, there's no audio at all on d4 for calls
17:28
<
Wizzup >
so that needs to be solved
17:28
<
Wizzup >
after that we're probably fine
17:28
<
Wizzup >
sicelo: see get_bss_info in src/wpaicd.c
17:28
<
arno11 >
oh yes ofc, i meant on n900
17:29
<
Wizzup >
_BSS_SIMPLE_INFO_FROM_DICT(&bss_info_dict, "Signal", &info->signal, G_VARIANT_TYPE_INT16, "n")
17:29
<
Wizzup >
this is where it gets set every time get_bss_info is called
17:29
<
sicelo >
I'm on android atm ... so i can't easily check
17:29
<
Wizzup >
I'll just install the applet and test it now, easy enough to remove it afterwards
17:29
<
sicelo >
yes, good idea
17:30
<
Wizzup >
I wouldn't have packaged it if it never worked I would hope
17:30
<
sicelo >
that get_bss_info ... does it get called again if connection remains intact? what calls it?
17:31
<
sicelo >
iirc we're not subscribing to fi.w1.wpa_supplicant1.BSS.PropertiesChanged signal.
17:31
<
sicelo >
so we don't know when signal strength of currently connected network changes
17:32
<
sicelo >
anyway, i might be wrong :-)
17:32
<
sicelo >
i
*think* i actually noticed the problem when i installed signal applet (first time ever)
17:33
<
Wizzup >
well doing that made icd2 use 50-60% cpu
17:33
<
Wizzup >
it seems to repeatedly issue dbus calls
17:33
<
Wizzup >
sicelo: yes it gets called frequently
17:33
<
Wizzup >
at least when statistics are asked for
17:33
<
sicelo >
ah! what triggers calling it
17:34
<
Wizzup >
your dbus call I would say
17:34
<
Wizzup >
and having the conndlgs open
17:34
<
Wizzup >
and opening the status menu
17:34
<
Wizzup >
and the wifi signal applet
17:34
pere has joined #maemo-leste
17:35
<
sicelo >
ok. I'll retest again.
17:37
<
Wizzup >
well the wifi signal applet for me just caused havoc
17:37
<
Wizzup >
it's gone now that I uninstalled it
17:38
<
sicelo >
hehe, what havoc? 🤪
17:42
Livio has joined #maemo-leste
17:53
<
arno11 >
Wizzup: btw did you see my msg about the 3 missing deps for drnoksnes ?
17:54
<
arno11 >
cause i expect to be able to push drnoksnes in the next couple of days :)
17:54
LjL has quit [Read error: Connection reset by peer]
17:55
LjL has joined #maemo-leste
18:11
<
Wizzup >
arno11: I did see the message
18:11
<
Wizzup >
do you need me to package them, or just to make the repos and such?
18:15
<
arno11 >
they are easy to pkg so i can do it if you want, i just need you to make the repos.
18:20
<
arno11 >
sicelo: your battery patches work, got a fully charge msg + green led
18:21
<
arno11 >
i mean, we know it works lol but works ootb now with 6.6
18:25
<
arno11 >
Wizzup: *i mean empty repos
18:26
arno11 has left #maemo-leste [#maemo-leste]
18:38
<
Wizzup >
arno11: ok, will make it
18:39
<
Wizzup >
sicelo: icon for otp would be nice btw :D
18:46
<
Wizzup >
uvos: even with my regtool I can't get call audio to work
18:47
<
Wizzup >
uvos: I think it might be somehow dapm related
18:51
<
Wizzup >
the above is with
18:51
<
Wizzup >
echo 'file cpcap.c +p' > /sys/kernel/debug/dynamic_debug/control
18:51
<
Wizzup >
echo 'file motmdm.c +p' > /sys/kernel/debug/dynamic_debug/control
18:51
<
Wizzup >
echo 'file n_gsm.c +p' > /sys/kernel/debug/dynamic_debug/control
18:51
<
Wizzup >
echo 'file soc-dapm.c +p' > /sys/kernel/debug/dynamic_debug/control
18:51
<
Wizzup >
I wonder if the hifi muting interferes with our dapm forcing
18:52
<
Wizzup >
uvos: I should note that my regtool doesn't necessarily write all regs I think, just a few that I picked
18:55
<
Wizzup >
uvos: the dapm entries definitely seem
*off*
18:56
<
Wizzup >
very strange to see what when I accept the call the Hifi is unmuted
18:57
<
Wizzup >
that has to be sphone doing something
18:58
<
Wizzup >
with 6.6 I seem to regularly lose wifi btw, it just disconnects
18:59
<
Wizzup >
much like the n900 does frequently
19:13
arno11 has joined #maemo-leste
19:14
<
arno11 >
Wizzup: ty for the 3 repos
19:15
<
arno11 >
btw i've never seen wifi disconnections on my device
19:15
<
arno11 >
and weird at hifi unmuted when call is accepted
19:16
<
arno11 >
seems really wrong
19:16
<
arno11 >
could be sphone or ucm
19:19
<
arno11 >
btw what is the call audio sample rate on D4 modem ?
19:20
<
sicelo >
arno11: nice @ applet
19:20
<
sicelo >
Wizzup: @icon ... i'm not good with that kind of stuff, but can try
19:27
<
arno11 >
ok D4 call audio rate seems 8000 | 16000
19:29
<
arno11 >
so if hifi is unmuted and use 44100 | 48000, it is normal to have no audio during calls imo
19:42
<
freemangordon >
that could be the ringing tone
19:42
<
Wizzup >
freemangordon: hi
19:42
<
freemangordon >
there is a race between ringing and call audio it seems
19:42
<
Wizzup >
freemangordon: based on what?
19:42
<
freemangordon >
gut feeling
19:43
<
Wizzup >
I am drafting a email, and I also thought that
19:43
<
freemangordon >
the only thing that unmutes hifi during call is ringing tone
19:43
<
Wizzup >
let me send it
19:44
<
Wizzup >
sicelo: maybe just pick some generic otp icon, inspired by what android does or something
19:45
<
freemangordon >
anyway, as I said I just came home from ~1000km driving. tomorrow :)
19:48
<
Wizzup >
arno11: hifi is not involved in d4 audio, it's all internal
19:50
<
arno11 >
i understand that but i suppose you can't use hifi and voice at the same time, or ?
19:50
<
Wizzup >
don't know
19:51
<
Wizzup >
my assumption is that our dapm hack is being nullified due to hifi being messed with during call setup
19:56
<
freemangordon >
Wizzup: try to disable ringiong tone and see if you can repro
20:08
Wikiwide has joined #maemo-leste
20:08
<
Wizzup >
freemangordon: this is with ringtone disabled
20:09
<
Wizzup >
profile set to silent
20:14
Livio has quit [Quit: Reconnecting]
20:14
Livio has joined #maemo-leste
20:20
<
Wizzup >
can't we make a dapm "Switch" widget hooked up in such a way that the all the call audio components get power?
20:24
<
Wizzup >
freemangordon: to me it looks like just switching ucm makes the hifi muted but the dapm (or whatever it is) turns it off only after 5 seconds (presumably a timeout)
20:27
<
Wizzup >
(on "Switch", looks like probably not...)
21:05
akossh has quit [Quit: Leaving.]
21:11
Wikiwide has quit [Ping timeout: 264 seconds]
21:22
mdz has quit [Ping timeout: 264 seconds]
21:53
arno11 has left #maemo-leste [#maemo-leste]
21:57
Livio has quit [Ping timeout: 252 seconds]
23:08
Wikiwide has joined #maemo-leste