libera/#maemo-leste/ Friday, 2025-04-11

sicelowith upower, status-battery, and mce done, the only remaining stuff will be: (1) shipping a modified UPower.conf [via leste-config] for devices that need it. I think N900 and Droid4 at least. I doubt devices like PP need it00:01
sicelo(2) shipping, via leste-config, an mce-ini file with the new mce keys. Droid 4 probably doesn't need these, since it can just use the CriticalVoltage key. For N900, I do recommend using the new options and not CriticalVoltage. The new keys are sure to allow the calibration trigger to be hit before shutdown begins00:04
Wizzupthat sounds good :)00:13
sicelogn for now. if there is need to clarify anything in connection with the foregoing, you can just ping00:18
Wizzupgn, will do00:25
Wizzupsicelo: I merged some of the PRs, will make releases tomorrow01:36
Wizzupmkfx: well so armel will require an additional builder, and we'll have to rebuild all our packages, deal with any compiler warnings, other flags, missing asm that nokia had for arm, etc01:37
freemangordonWizzup: I think we're hitting some ICE07:55
freemangordonugh08:12
freemangordonWizzup: tests are using /lib/arm-linux-gnueabihf/librtcom-eventlogger.so.1 :D08:12
freemangordonscratch that08:26
freemangordonWizzup: this start to look as an issue in sqlite, but need some more time to confirm08:43
freemangordonWizzup: https://paste.debian.net/1368822/09:21
freemangordonhave to stop for now, no idea when I will be able to continue09:22
freemangordonbut at first glance it looks to be either ICE or sqlite3 bug09:23
freemangordonBTW, you said you have a test program, could you share it?09:45
Wizzupfreemangordon: the test program is in /root/ - it's mostly just the failing tests10:37
WizzupI think you're at the point (or maybe past) where I got stuck as well- trying to figure out the printf problem in sqlite10:37
freemangordonyeah11:24
Wizzupfreemangordon: I guess would get either older/newer compiler or older/newer sqlite and re-test13:07
WizzupI guess we could*13:07
siceloWizzup: just to take you back to  voicecallmanager ... I understand correctly that sphone was switched to qt mainloop because vcm is qt as well?13:51
sicelomy d4 battery is toast, so I'm daily'ing the N900 now. outgoing calls are OK, but incoming is quite bad as far as UI goes. I hit answer, and UI doesn't immediately reflect this, and still vibrates. However, call has already been picked. Anyway, I blame my SD card for this13:54
Wizzupyes, sphone has to be qtloop13:54
WizzupI don't think vmg has anything to do with vibration though13:54
uvos__for sure sphone+glibloop+ofono is mutch lighter than sphone+qtloop+vcm13:59
siceloyes. what I want to ask is - is it possible to answer a vcm/telepathy call directly via dbus (like it's possible with ofono)?13:59
uvos__if you dont need vcm you should probubly use ofono on n90013:59
uvos__sicelo: yes its possible14:00
uvos__someone would have to write a native sphone telepathy sphone module14:00
uvos__Wizzup mainly chose to implement vcm because its was less work to do so14:01
Wizzupsicelo: telepathy is dbus, so yes, but you'll have to replicate many many manhours that we don't have for not a big percieved gain14:01
uvos__regarding vibration, stoping vibration happens after the backend reports the call was picked up locally14:03
siceloright I see what I'm looking for in vcm's dbus. let me make some tests14:03
uvos__which means theres a syncronous trip to the backend14:03
uvos__so it could be the vcm/telepathy stack being slow14:03
uvos__or it could be sphone stalling for some other reason14:04
Wizzupright, it could also be a bug in our code14:04
WizzupI don't think the dbus round trips are really what kill the performance jere14:04
Wizzups/jere/here/14:04
uvos__dbus round trips can be quite slow14:04
uvos__mce spends most of its time in those14:04
uvos__but yeah14:04
uvos__could be either14:05
sicelowhat I want to try is pickup the call (via dbus) with sphone killed. currently testing ...14:05
siceloWizzup: the stack is ofono -> tp -> vcm?14:07
uvos__jup14:07
uvos__-> sphone-tp -> sphone14:08
sicelook. so yes, let me see what happens at the vcm layer. I'm aware the ucm, etc. won't be working, but that's a different concern. for now I just want to see if reacting to an incoming call is fast enough on the N90014:09
sicelounfortunately seem to have run out of call credit :-p14:10
WizzupI don't have troubles on my n90014:12
siceloprolly my SD card indeed14:12
Wizzupand lack of nice/cgroups/etc14:12
siceloalso to be clear, I'm definitely not considering replacing tp/vcm. but might end up looking for a simple way to not add anything on any layer higher than these14:13
sicelofor testing/fun :-)14:14
Wizzupmy aim is to reduce additional work and use products that are supported upstream (in this case sailfishos) so that we can focus on many other things that are lacking14:15
Wizzupyour sd card is likely much slower than the emmc as well, so it's not a fair comparison then14:16
Wizzup(when comparing to fremantle)14:16
Wizzupkeep in mind that vcm also gives us xmpp/sip calls14:16
siceloagreed, that's why I'm not even remotely considering removing/bypassing it. I'll have a look at vcm's dbus interface14:20
arno11sicelo: yeah Wizzup is right imo @sdcard and lack of nice/cgroup. one more thing is the current bug with incoming call on n90015:43
arno11issue #76715:43
arno11only on daedalus15:44
siceloi saw that issue15:45
arno11ok, btw boost mode and H-D renicing to -8 should help your sdcard15:47
arno11*for incoming calls15:47
arno11Wizzup: currently working on new picodrive (almost finished) but have few questions16:21
Wizzupshoot16:23
arno111) is the buider compatible with flto (link time optimization) ?16:23
arno112) does picodrive need a new tag for new daedalus version ?16:24
arno112) if i remove cortex and neon optimization from configure file, does the buider automatically add them to armv7 ?16:26
arno11*builder16:26
arno11(in fact i'd like to make a more generic build to be able to build pico for arm64 and amd6416:27
arno11*3)16:28
arno11btw local build (with armv7 optimizations) works better than ever on n900: some 32x games run @60fps !16:36
WizzupI think we should be able to lto16:37
WizzupI think we have some default compiler flags in our builder for armhf, but there are ways not to add them16:37
arno11ok cool, if not, that's easy to fix anyway16:37
Wizzuphttps://git.maemo.org/leste/jenkins-integration/src/branch/master/debian_glue#L16616:37
arno11*@flto16:37
arno11ok @flags16:38
Wizzupnice @ 60fps :)16:38
arno11yeah i should make a video running virtua racing for next news post, as it was impossible to do that on fremantle16:39
sicelofun, `busctl --user call org.nemomobile.voicecall /calls/active org.nemomobile.voicecall.VoiceCall answer && pactl set-card-profile 0 'Voice Call'` gives me working incoming call (obviously still need to know when the call has arrived)16:39
Wizzupsicelo: making a sphone.sh? :D16:39
siceloexactly ;-)16:40
WizzupI wish we'd be able to write some of our things in rust or go, but with gtk2 this is just not doable16:40
Wizzupmaybe if/when we move to gtk3 :)16:40
arno11Wizzup: i'd like to launch a daedalus picodrive build plz :) (as a test)16:49
Wizzupmaemo/daedalus branch?16:49
arno11yes plz16:50
Wizzuprunning16:50
arno11cool ty16:50
arno11at least source is ok16:52
WizzupI'm planning to fix this also in the near future, the complexity of running jobs16:52
arno11ah indeed could be cool16:52
arno11it fails @binaries, will have a look later16:58
arno11libgles dep missing in control imo17:02
siceloWizzup: although i won't use/test this right away ... sip calls also come in via vcm? or those are only available at tp level?17:23
siceloand, if you still recall, what does  "active" call state really mean, because here's what i got on the call: https://paste.debian.net/hidden/ee140b7b/17:41
siceloi'd think active means the call has been answered, but then, (in that log) i see it changing to 'alerting', then 'active' again :-/17:42
Wizzupsicelo: well, tp, and then vcm, yes17:51
freemangordonsicelo: install procmgrd and set all dbus processes nice to -5 with it, then see if it helps with latency18:22
freemangordonsicelo: example https://paste.debian.net/1368937/18:23
freemangordonyou may want to increase tp-ring and vcm prio as well18:24
freemangordonthough, we shall control those through cgroups18:24
freemangordonsicelo: procmngd will be in repos in few minutes18:47
sicelowant to try a sip call on the N900 now. i add it via SIMPLE (haze), or I need to use a different connector?19:12
freemangordonSIMPLE does not support voice19:22
freemangordonsicelo: iirc, you need tp-rakia19:48
arno11yeah tp-rakia for sure19:55
sicelook cool, thanks. i can configure the account from UI, or needs mc-tool?19:57
arno11should work from the ui19:57
arno11sip calls work from sphone/vcm but atm the best sip results i got on n900 were through twinkle20:00
siceloi hope to try them on dbus :-P20:03
arno11yeah could be cool :)20:03
siceloi do see the sip call in vcm dbus iface... nice!!!20:43
arno11cool21:02
arno11Wizzup: btw i need another kick for picodrive plz (when you can ofc)21:03
Wizzupdone21:20
Wizzuparno11: looks like it built21:42
arno11Wizzup: yeah, cool, ty22:01
arno11at the moment, that's still experimental as the emulator is really powerfull with last notaz stuff but still not really user friendly unfortunately22:02
arno11cool, the pkg works fine, full speed. could be interesting to test on PP + kbd22:17

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!