<arno11>
donihalim: depends of what you mean: testing/optimizing new functionalities or fixing existing issues :P
<arno11>
(or porting new stuff ?)
<arno11>
i mean, apart modern web, almost everything else already works but needs most of the time optimization
<arno11>
(ah i forgot camera and bluetooth, which are the last not working things)
<sicelo>
with the omap3isp patch, camera at least probes correctly now, and shows the required v4l2 endpoints. it should be possible to get some images out of it
<arno11>
really cool
<sicelo>
with the bluetooth, i would like to investigate how to provide a bluetooth address to the driver. from discussion with sre, there's a timing issue somewhere (firmware perhaps?) which will be very hard to troubleshoot
<sicelo>
anyway you never know ... maybe if we provide the address early enough, it might just make all the difference in the world
<sicelo>
with BT working (even if not perfectly), we would then be able to bring up the FM radio receiver :-)
<arno11>
:)
<inky>
> with the omap3isp patch, camera at least probes correctly now, and shows the required v4l2 endpoints. it should be possible to get some images out of it
<inky>
omg
<Wizzup>
my droid strangely doesn't want to connect to the network some of the time
<arno11>
i also got some troubles with chimaera: disconnections, wlan1 issue. not anymore with fresh daedalus
<Wizzup>
sorry, I meant the mobile network
<arno11>
ah ok
<arno11>
is it with ofono1 or 2 ?
<sicelo>
arno11: regarding wlan1 ... someday i'll submit patch to make that problem history. we would no longer require the interface to be named wlan0
<Wizzup>
ofono 2
<arno11>
nice
<Wizzup>
sicelo: yeah that does need fixing
<sicelo>
i've looked at it a bit, and can see how we could implement it. -ETIME is the only major problem atm :-)
<sicelo>
on the wlan topic, anyone has an opinion on iwd?
<Wizzup>
as opposed to wpa_supplicant?
<sicelo>
yes
<Wizzup>
I haven't tried it, but I'd be worried about compat with older devices and how we'd do host mode
<Wizzup>
and of course having to rewrite a bunch of C code :P
<sicelo>
it supports hotspot. and works fine on N900, which i guess is oldest device we will ever support
<Wizzup>
what makes it more suited than wpa_supplicant?
<sicelo>
I don't really know 😆
<Wizzup>
imo, if we wanted to swap out some things I'd want to replace PA with pipewire at some point
<sicelo>
it is said to be mobile optimized (comes from ofono people)
<Wizzup>
if it can do host mode in the same daemon that could be somewhat useful
<sicelo>
yes, hotspot is builtin
<Wizzup>
imo I'd prefer to defer just because it's more work
<sicelo>
yeah, completely agree. it's a project for some future day :-)
<sicelo>
never ending list
<Wizzup>
I hope that at some point it won't be never ending :)
<Wizzup>
but for now, YES :D
<Wizzup>
if we were to set up gitea on say git.maemo.org or src.maemo.org (preferences?), should we allow openid/oauth logins from github and the like?
<sicelo>
sauce.maemo.org :-)
<sicelo>
jokes aside, I'd probably go for git.*
arno11 has quit [Quit: leaving]
arno11 has joined #maemo-leste
Livio has joined #maemo-leste
<arno11>
hmm got again that random issue when wifi burns +30mA...disappearing if i disconnect/reconnect
<sicelo>
how do you correlate that to wifi?
<arno11>
well, idle is around 45-47mA idle with modem on (3.5g). with wifi connected: 52-58mA
<arno11>
but sometimes 85mA with wifi
<arno11>
until i reconnect it
<arno11>
(or until i disconnect it and idle is back to normal 45-47mA)
<sicelo>
ok. maybe wpa_supplicant? we're still using same kernel from chimaera, right?
<arno11>
yes same kernel
<sicelo>
maybe htop or dmesg could give you clues?
<arno11>
6.6.53
<donihalim>
arno11: how you measure the power consumtion?
<arno11>
sicelo: no htop or dmesg unusual stuff
<arno11>
donihalim: have a look in /sys/class/power_supply/bq27200-0/
<arno11>
very useful
<arno11>
i.e to get quite accurate idle current draw: sleep 30 && cat /sys/class/power_supply/bq27200-0/current_now
<arno11>
you can even check battery health and temperature
n900 has joined #maemo-leste
<donihalim>
Cool, thanks for the tips
<arno11>
np
Daanct12 has quit [Quit: WeeChat 4.5.2]
<mkf>
hello
kiva has joined #maemo-leste
hm has quit [Read error: Connection reset by peer]
<mkf>
can the latest images be flashed on n900 or they are borken?
narodnik has joined #maemo-leste
hm has joined #maemo-leste
<arno11>
mkf: hi
<Wizzup>
mkf: hi
<mkf>
mkf: hi
<arno11>
latest daedalus works fine but you need to edit fstab to switch to sdswap
<mkf>
it uses mmc?
<Wizzup>
arno11: let me see if I can figure out the rootfs-overlay
<Wizzup>
I think we can modify daedalus.blend, where it rsyncs the files, and see if we can have it be more clever
<arno11>
mkf: yes but just because of building issue
<kiva>
how newcomers can know what imege should dl with any device? How many had dl some image that does not work and gave up and newer check leste again?
<donihalim>
another n900 user, cool :)
<kiva>
should separate stable and dev images?
<Wizzup>
I think the problem is doing swapon in the postinstall
<Wizzup>
maybe we should not do that
<Wizzup>
arno11 ^
<Wizzup>
in leste config postinst
<Wizzup>
I think mkswap and fstab writing makes sense, but swapon does it
<Wizzup>
does not*
<Wizzup>
agree?
<sicelo>
yes, i agree
<Wizzup>
will fix
halftux has quit [Quit: leaving]
<arno11>
Wizzup: let me few min to check something
<arno11>
yes you're right
<arno11>
that's probably the problem
<arno11>
'sw' option in fstab makes the swapon iirc
<Wizzup>
no, we called swapon explicitly
<arno11>
yes i know
<sicelo>
what is that option? i can't find it in `man 5 fstab`
<arno11>
well, we don't need 'swapon /swap' but we need sw option
<mkf>
(alongside of rw, rq, ro and xx options)
<sicelo>
on my N900 i have `/swap none swap defaults 0 0`
<arno11>
otherwise, there is no swap on boot at all iirc
<Wizzup>
I think we have it don't we?
<arno11>
yes that's what i said
<arno11>
sicelo: weird, iirc it didn't work before (without sw)
kiva has quit [Quit: Client closed]
<sicelo>
devuan fstab also doesn't show that 'sw' :-)
<arno11>
on my ubuntu fstab, it is
<arno11>
anyway, the problem seems swapon /swap
<Wizzup>
back in a bit
<Wizzup>
yeah, the image-builder still had it enabled as swap :D
<Wizzup>
that's why the rm failed
System_Error has quit [Ping timeout: 264 seconds]
Daanct12 has quit [Quit: WeeChat 4.5.2]
<arno11>
sicelo: oh now i remember how it works with sw
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #maemo-leste
<arno11>
if you create the swapfile yourself, you don't need the sw option. at the opposit, if the swap file is created during the postinstall, you need it
<arno11>
otherwise, no swap at all
<arno11>
*opposite
<donihalim>
/swap is created when dist-upgrade to devel
<arno11>
Wizzup: ^^^ we had this issue when we switched to emmc swap by default (see irc logs)
<arno11>
donihalim: yes with chimaera, that's normal, emmc swap is still the default one without devel
<arno11>
donihalim: on daedalus, default is sdswap (like chimaera -devel) because emmc is buggy with kernel 6.6
_fab has quit [Quit: _fab]
System_Error has joined #maemo-leste
<Wizzup>
Yes, the swap file is created by postinst
<Wizzup>
that is normal
ceene has quit [Ping timeout: 246 seconds]
<arno11>
should work fine now (hopefully)
<Wizzup>
I still need to fix the fstab, but the postinst should be ok
<arno11>
ah yes @fstab
<Wizzup>
the problem is that our daedalus.blend just overrides the fstab regardless
<Wizzup>
Maybe we have it append instead?
_fab has joined #maemo-leste
<Wizzup>
hm... actually... there's *two* places where we override fstab, lol
<arno11>
lol
<Wizzup>
arm-sdk writes it, extra/n900/etc/fstab
<Wizzup>
and daedalus.blend writes it
<Wizzup>
cat <<EOF | sudo tee "$strapdir/etc/fstab" >/dev/null
<Wizzup>
so I can change arm-sdk not to write the emmc entry, which I think is what is still present, right?
<arno11>
yes agree
<sicelo>
the workings of the builder seem to be a mystery to me :(
<sicelo>
and i need to understand it in order to add the L5 ..
<Wizzup>
it's actually not that hard, it is just a bit tricky because arm-sdk and vm-sdk aim to work to build images for devuan, regardless of maemo
<Wizzup>
and then 'maemo' is added as a 'blend'
<Wizzup>
so devuan has its own idea of what etc/fstab should look like
<Wizzup>
and then so does maemo with its rootfs overlay, and then our .blend file (mistakenly, imo) also overrides that
<Wizzup>
probably not more than 10-15 minutes of dedicated concentation to fix
<sicelo>
i'll give it a closer look again
hm has quit [Remote host closed the connection]
hm has joined #maemo-leste
<arno11>
for an hobbyist like me, yeah indeed builder is not so complicated: it is pleasant to troubleshoot compared to deal with valgrind and memory leaks lol
arno11 has quit [Quit: leaving]
pere has quit [Ping timeout: 260 seconds]
<inky>
my bionic (which is stable) says it got an update for calendar and for some reason from ovi store. Is it expected?
<inky>
(:
<inky>
but the description is 'an open source clone of the default maemo calendar application'
<dsc_>
yes calendar was updated recently
<inky>
good, thank you
<dsc_>
they added new days and months
<inky>
the 'ovi store' made me wonder where those words come from.
<dsc_>
I'm not sure about 'ovi store'
<dsc_>
where do you read it?
<dsc_>
what is it?
<inky>
alas i didnt screenshot
<dsc_>
ah nokia
<inky>
when i tapped on the update indicator on the status bar it opened ham, i think, which mentioned at the top 'ovi store' and below 'calendar'.
<dsc_>
but yes it was updated
<inky>
good to know, thank you (:
<dsc_>
yw
pere has joined #maemo-leste
<Wizzup>
inky: 'ovi store' is just some translation string I think
<Wizzup>
but yeah it's funny, I think it's due to the domain changes by freemangordon
<Wizzup>
19:50 < mkf> tries to run x11, dies somewhere before i can see a thing
<Wizzup>
19:50 < mkf> i can only see tty.
<Wizzup>
I think this is upower
<sicelo>
yes, he needs to charge, then upower won't trouble him
arno11 has joined #maemo-leste
<mkf>
hm, i dont have a charger, i can charge batteries
<mkf>
(using a charge module)
<mkf>
i wonder if that casues the phone to not calibrate and think my phone is ran out of battery
<mkf>
i've tried two batteries right now.
<mkf>
i recall when i used leste before it thought my battery had 0 out of 2560(?) mW, which wasn't correct (and i had a regular BL-5J), so i wonder if that's because my battery isn't calibarated in leste (i wonder how can i do so without a charger port)
<sicelo>
mkf: that won't help you (charging externally) ... the problem here is that the fuel gauge, which is inside the N900, is currently reporting 0% *even if* your battery has charge