<dsc_>
actually we're talking about bookmarks right now, its already half implemented. There is bookmarkmodel.cpp
<dsc_>
but not used
<Wizzup>
after that I will build another kernel
<dsc_>
Wizzup: thanks
<Wizzup>
uvos: so I think today I would like to work on the rtcom logging stuff we discussed, I'll dig through the logs to find the most recent approach we agreed upon, unless you have some other ideas now?
<uvos>
no but that exactly needs the framework changes i would like to do myself
<uvos>
so please work on something today else ill do this tomorrow
<uvos>
*else today
<uvos>
dsc_: if you are implementing bookmarks soon i wolnt bother, i was thinking of pining things as a bookmarks-lite
<dsc_>
i need half a day to implement bookmarks
<dsc_>
maybe ill do it tomorrow
<Wizzup>
uvos: ok, ty
<Wizzup>
uvos: no need to do it assuming you're busy, but I think wifi hotspot started to work sometime in the stable 6.1.y patches
<Wizzup>
so I would wager that it doesn't work in stable, but it works on devel kernel
<Wizzup>
maybe we can try to identify that fix commit and pull it in - since 6.6.y doesn't work again
<uvos>
hmm
<uvos>
i kinda doubt there is a commit that fixes this persay since i would expect them to apply this to 6.6 stable too
<uvos>
but bisecting might give a clue why it sometimes works and sometimes dosent
<uvos>
i remember it not working 5.9 or something and then suddenly working in 5.10 again
<uvos>
so this has been flip floping for a while
<Wizzup>
it did not work in 6.1 earlier but does now in -devel
<uvos>
i get that
<uvos>
but i expect fixes to be backported to 6.1 to also be backported to 6.6
<uvos>
so if a obvious fix patch exists, i expect it would be applied, so i suspect that its not a fix persay but that something is racy, which would explain why it breaks often in random kernel version ranges
<Wizzup>
maybe, I also blame hostapd version changes
<Wizzup>
like maybe it tries to enable wpa3 or something silly
arno11 has joined #maemo-leste
<Wizzup>
arno11: building new kernel with likely header fix
<arno11>
cool
<arno11>
i still wonder where slowdown is comming from: conversations or other qt stuff take 25 sec to launch sometimes ! instead of 1 or 2 sec on 6.1
<arno11>
how kernel could affect mostly/only qt5 ?
<uvos>
Wizzup: could be
<uvos>
arno11: since the n900 is esstanly oom when launching qt stuf the kernels choices can have a big impact
<arno11>
it really doesn't seem oom honestly
<uvos>
i mean its fairly deep into swap no?
<uvos>
it was last time i tried
<uvos>
which pages the kenrel decides to ejct makes a big difference here, ofc im just thinking out loud i dont really know why it would change that mutch
<arno11>
i didn't noticed any diff with swap in 6.6 atm. it usually only uses around 100MB of swap
<arno11>
and issue is really random
<arno11>
sometimes it works fine
<uvos>
i maen 100mb of swap is alot on a 256mb machine
<uvos>
but yeah i have no idea about the root cause
<Wizzup>
freemangordon: btw on fremantle I can get xmpp calls ti work with my xmpp server to a certain degree: my n900 can hear my laptop sound, but not vice versa (probably stun rtelated)
<arno11>
uvos: yes indeed that's a lot but perfectly fine with 6.1
<arno11>
Wizzup: yes probably @stun or maybe the mic ?
Livio has joined #maemo-leste
<arno11>
ah cool build seems ok, let's try to upgrade again
<sicelo>
arno11: what qt programs give you problems?
<sicelo>
i generally stay away from qt applications anyway (even on desktop), so i haven't really seen the excessive slow downs you mention
<sicelo>
(or I'm just too patient 😃)
<Wizzup>
a lot of maemo leste is qt so..
<sicelo>
yeah, I'm aware (which is a pity ... Fremantle was mostly gtk)
<Wizzup>
I don't think it's a pity, gtk3 and gtk4 have gotten significantly more memory heavy and sluggish afaict
<arno11>
sicelo: all qt5 apps but only on 6.6, quite fast on 6.1
<Wizzup>
and we can't stay on gtk2 forever
<Wizzup>
arno11: try new kernel wrt dkms
<arno11>
i just finished upgrade, iphb-dkms is ok :)
<arno11>
need to reboot now
<sicelo>
not really (@gtk3/4 getting worse). at least going by the fact that plasma mobile is still heavier than phosh (gtk3) ... which is funny since plamo is fully accelerated while large parts of phosh/gtk aren't
<sicelo>
arno11: will retest soon on mine
<uvos>
thats qtquick
<uvos>
i find qt widgets alot better than gtk4 and generally lighter too
Wikiwide has quit [Remote host closed the connection]
<uvos>
no suprise given how gtk4 works
Wikiwide has joined #maemo-leste
<uvos>
but yes quick is extreamly slow
<arno11>
sicelo: ok
arno11 has left #maemo-leste [#maemo-leste]
<sicelo>
btw, yesterday evening i was playing with alarms on the d4 ... the face-down-to-silence gesture did not work. known issue?
<uvos>
yes i think so
<uvos>
i dimly remember something missing in mce
<sicelo>
mmm, maybe I'll look into it over the weekend
<uvos>
if you do please add some way to disable this
Wikiwide has quit [Remote host closed the connection]
<uvos>
as i hate this feature on android
Wikiwide has joined #maemo-leste
<uvos>
(after haveing being bitten by it with my gfs phone being in her handbag a couple of times)
Wikiwide has quit [Remote host closed the connection]
<sicelo>
i suppose accelerometer and proximity are hooked and working via mce, so sounds strange why it shouldn't be working already (i forget if it's based on prox or accel)
<uvos>
iirc its both
<uvos>
and mce sends a special signal for it
<uvos>
but i may be wrong this is all a long time ago
<sicelo>
i'm not expecting the values to be different at this point :-/
arno11 has joined #maemo-leste
<arno11>
Wizzup: uvos: to make it short, the swap issue is due to emmc itself (with 6.6, not with 6.1)
<arno11>
i got a well working stuff using sd swap file
<arno11>
now it is stable
<arno11>
and almost as fast as 6.1
<arno11>
but it took several minutes to swapoff emmc
<arno11>
maybe something is wrong on boot ?
<sicelo>
sounds all good to me :-)
<sicelo>
it's correct for swapoff to take some time
<gnarface>
why not use zram for swap? just curious
<arno11>
according to irc logs it was problematic on N900
<gnarface>
oh, didn't know that
<arno11>
but i don't know exactly why
<arno11>
fmg should know
<sicelo>
time to build latest/upstream iio-s-p i guess
<gnarface>
how much ram does it have? maybe it's not enough
<sicelo>
256MB
<gnarface>
oh. yea, maybe that's why. also, now that i realize you're using a N900, i revise the parameters for optimal dd block size use; 8MB may be too much. some multiple of the physical emmc block size for sure, but maybe start with 2x or 4x and work your way up doing some benchmarks
<arno11>
with 1MB i got similar results with both 6.1 and 6.6
<arno11>
btw, not related but calls works fine with no more hangup issue, boost mode is ok, conversations ok, i still need to kill hsm as usual but apparently no other issues
<arno11>
so excepting swap, everything seems similar to 6.1 now so i'm happy :)
branon has quit [Read error: Connection reset by peer]
branon has joined #maemo-leste
akossh has quit [Quit: Leaving.]
Livio has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
System_Error has quit [Remote host closed the connection]
<sicelo>
quick and dirty ... will cleanup tomorrow. midnight now
<sicelo>
side effect - this reveals that the mount matrix i calculated for N900 is wrong for the Z axis :p
<sicelo>
oh, i should mention that i didn't (yet) solve the issue shown at https://paste.debian.net/1323081/ ... at least on the Droid 4. my current test/patch was done from N900 running postmarketOS. that corruption of values doesn't happen there (pmOS)
<sicelo>
will check why it happens under Leste. the patch itself should apply with no change at all under Leste, since the file it touches has not been modified since iio-sp 3.0 (version in Leste)
xmn has quit [Read error: Connection reset by peer]