<uvos>
no idea about what is in 608 then, but something else presumably
<uvos>
probubly mbm6600 going by specs
<Wizzup>
will probably know more tomorrow
<Wizzup>
is it a lot of work to kick off a kernel from experimental for the branch you linked earlier?
<Wizzup>
btw, the utags for mz609 are for 32GB I think, so this might be a problem
<Wizzup>
also, tdlib on armhf runs out of address space in cc1plus :(
uvos has quit [Ping timeout: 252 seconds]
<Wizzup>
ok, worked around that with -O1 for now
akossh has quit [Quit: Leaving.]
Armen7 has joined #maemo-leste
Armen has quit [Ping timeout: 245 seconds]
Armen7 is now known as Armen
DaRiX has quit [Ping timeout: 268 seconds]
mrkrisprolls has quit [Read error: Connection reset by peer]
DaRiX has joined #maemo-leste
mrkrisprolls has joined #maemo-leste
mqlnv has quit [Ping timeout: 252 seconds]
mqlnv has joined #maemo-leste
elastic_dog has quit [Ping timeout: 256 seconds]
<tmlind>
Wizzup: i only tested flashing mz608 as mz609 after clearing that one partition, did not try doing it on mz615 so far
sch has quit [Ping timeout: 268 seconds]
<tmlind>
uvos: possibly if you mess up utags on mz617 and then reset the device from recovery utags also gets reset, unconfirmed though
<tmlind>
hmm so which xyboard tablet models have a working micro-sd then?
<tmlind>
the mz609 variants have a sucky touchscreen controller not supported in the mainline kernel btw, vendor upstreamed earlier controller then never bothered to send updates so nobody has cared about the new controller i think
elastic_dog has joined #maemo-leste
<tmlind>
i'll be sending the updated display bridge patches to the lists after -rc1
<tmlind>
with those mz617 should be mostly usable with mainline kernels
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
ikmaak has quit [Ping timeout: 264 seconds]
ikmaak has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
xmn has joined #maemo-leste
DaRiX has quit [Ping timeout: 276 seconds]
gnarface has quit [Read error: Connection reset by peer]
gnarface has joined #maemo-leste
gnarface has quit [Quit: Leaving]
gnarface has joined #maemo-leste
elastic_dog has quit [Ping timeout: 264 seconds]
elastic_dog has joined #maemo-leste
<freemangordon>
Wizzup: ping
<freemangordon>
I need some help with gdbus
<Wizzup>
freemangordon: hi
<freemangordon>
hi
<Wizzup>
tmlind: mz608 should have working microsd, as does mz607 I think
<freemangordon>
Wizzup: how should I iterate over "(@a(oa{sv}))" ?
<freemangordon>
'o' is object path I guess
<freemangordon>
but what is a{sv}?
<freemangordon>
array of?
<freemangordon>
what?
<Wizzup>
I think thas is a map
<Wizzup>
hang on
<freemangordon>
ah, dictionary
<freemangordon>
right
<Wizzup>
a{sv} is a map[string]=variant
<Wizzup>
I think
<freemangordon>
hmm, ok
<Wizzup>
do you have some example of this in dbus, or not?
<freemangordon>
no idea
<Wizzup>
I am looking at my wpaicd.c code from libicd-network-wpasupplicant to see if there is anything analogous
<Wizzup>
is this tp related?
<freemangordon>
I think it should be while (g_variant_iter_loop (iter, "(oa{sv})", &path, &map) )
<freemangordon>
ofono
<freemangordon>
GetModems
<Wizzup>
I see
<Wizzup>
and yes o is object path, so (oa{sv}) is a tpuple of two values, with the first being an object path and the second a map
<Wizzup>
so I think this is indeed ok
<freemangordon>
ok, thanks
<Wizzup>
btw, I don't know how tricky this would be, and maybe it already does, but if tp-haze could export some of the Room interfaces, it could be used to get channel identifiers
<Wizzup>
like on telegram the channel ids are just chat-124435435343
<freemangordon>
Yes, I know
<Wizzup>
ah ok :)
<freemangordon>
actually, I ythink we already do it, at least partially
<freemangordon>
but I didn't dig much into it
<Wizzup>
ok, it might also depend on the purple plugin being loaded
<Wizzup>
I could definitely get the participant names btw :)
<freemangordon>
Wizzup: how to get value from dictionary? shall I iterate?
<freemangordon>
ah g_variant_lookup_value
<Wizzup>
yeah
<Wizzup>
sicelo: hm, having trouble with totp and gitlab now
mdz has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
<Wizzup>
digging deeper in this tablet with mz608 firmware, I don't see a microsd card, only a sim slot, so that's a bit weird
<Wizzup>
this mz616 definitely has one though
<Wizzup>
I suppose for mz616 the dts will need to be modified to support a microsd
<Wizzup>
actually looks like common still has mmc1 entry
<Wizzup>
ah, ok, yeah, the tablet dts overrides it
<Wizzup>
tmlind: anything meaningful I can extract from mz616 with android 4.0.4? maybe where microsd card and where modem is?
<Wizzup>
I've at least verified that this mz616 has both microsd and modem working in android 4.0.4
<sicelo>
Wizzup: what's the problem?
* sicelo
is not available though, at least for next 6 hours
<Wizzup>
sicelo: 'did not work' :)
<Wizzup>
maybe I need to sync time or sometghing
<Wizzup>
sicelo: as in, code not accepted
<Wizzup>
it's not too important, I'll debug that later
<sicelo>
ok. plausible @time
<sicelo>
otherwise on the d4, i have a token for gitlab
<Wizzup>
ok
gnarface has quit [Quit: Leaving]
gnarface has joined #maemo-leste
<tmlind>
Wizzup: ok, not sure if the microsd is added properly on any tablets as it's not working on mz617
<tmlind>
the mmc regulator is different from d4 i recall
<Wizzup>
mz616 has a working microsd
<Wizzup>
I tested it on android 4.0.4 just now
<Wizzup>
inserted a microsd card and formatted it through the android ui
<tmlind>
ok, if you get a chance to open one at some point would be interesting to see if there are some extra components populated on the micro-sd card cable compared to mz617 that seems to be missing the micro-sd cage
<tmlind>
tried popping in a micro-sd card to mz608, it seems to move sideways in the slot, not sure if it's functional
<Wizzup>
I'll open up the mz616 today
<Wizzup>
wrt mz608, is that the sim slot or microsd card slot
<Wizzup>
I thought it was a microsd card slot on my mz608, but I think it is the sim slot
<arno11>
hi guys, i noticed few things today: idle current draw increased a bit on N900: around 8-10mA (modem On, screen Off, hspda network: 57mA instead of 47). there is no effect if i change cpu frequency: same result @250MHz and 850. BTW default governor 'ondemand' doesn't work properly and keeps the max freq available all the time
<Wizzup>
if it is with internet on, it could just mean the modem is idle less often?
<arno11>
conservative governor works far better
<arno11>
internet is off
<Wizzup>
oh, I got confused because you said HSDPA network
<Wizzup>
you meant just 3.5g?
<arno11>
ah ok
<arno11>
yes
<Wizzup>
did anything change on your side?
<arno11>
absolutely nothing
<arno11>
idle was usually around 47 since march 2023 in normal conditions
<Wizzup>
when was the draw 47mA?
<arno11>
wdym exactly ?
<Wizzup>
you wrote it was 47mA
<Wizzup>
when did you measure this?
<arno11>
every weeks usually
<arno11>
idle current draw has been stable and the same for several months
<Wizzup>
is iphbd installed?
<arno11>
iirc yes
<Wizzup>
can you check?
<arno11>
yes it is installed
<Wizzup>
hm
<arno11>
stopping it and things are back to normal :)
<freemangordon>
hmm, that's weird
<freemangordon>
it should decrease the usage, not increase :)
<arno11>
lol indeed that's a problem
<freemangordon>
do you have iphb module loaded?
<arno11>
ah it seems to not be loaded by default
<freemangordon>
it is loaded, if it is build at
<Wizzup>
tmlind: apart from no microsd holder from my photos there does not seem to be a difference between mz616 and mz617
<freemangordon>
arno11: do you have iphb-dkms installed?
<arno11>
let me check
<freemangordon>
arno11: hmm, stopping iphbd removes the module as well
<arno11>
ah ok
<arno11>
(iphb-dkms is installed btw)
<freemangordon>
still, does modprobe iphb loads it?
<freemangordon>
in the meanwhile I am testing on d4
<freemangordon>
with/without iphbd
<arno11>
ok but power_avg is not relevant for idle only imo
<freemangordon>
it is
<freemangordon>
most of the time
<freemangordon>
hmm, it seems the same happens on d4
<freemangordon>
lets wait 2 more minutes to be sure
<arno11>
ok
<Wizzup>
uvos: tmlind: well, android also idles in off mode it seems at least
<freemangordon>
arno11: I see no increase here because of iphbd
<freemangordon>
there is something else going on
<arno11>
freemangordon: results are pretty similar for me (power_avg / voltage_now)
<freemangordon>
voltage_now?
<arno11>
i mean pretty similar to current_now
<freemangordon>
how is voltage_now relevant?
<freemangordon>
ah
<freemangordon>
ok
<arno11>
:)
<freemangordon>
so, may I have the output of iphbd?
<arno11>
i already sent, no ?
<freemangordon>
"waiting with sleeptime 3600, nfds=1, clients=0" is the last?
<arno11>
yes
<freemangordon>
I don;t see how it could increase idle draw
<freemangordon>
arno11: lets try another thing
<arno11>
i don't know :( maybe iphb is not directly the root cause ?
<freemangordon>
stop iphbd
sunshavi_ has joined #maemo-leste
<freemangordon>
and start it again as '/usr/bin/iphbd -d -k'
<freemangordon>
you should see 'iphb:TCP keepalive queuing disabled'
<freemangordon>
-k prevents opening kernel module
<arno11>
ok
<freemangordon>
so we can check if there is any issue there
sunshavi has quit [Ping timeout: 256 seconds]
<arno11>
yes i got the same msg
<freemangordon>
ok
<freemangordon>
how's the current now?
<arno11>
currently waiting for the result
<freemangordon>
ok
<arno11>
argh wifi was on (ssh), need to test again
<freemangordon>
ok
<arno11>
ah it's better (?!)
<arno11>
let me check gain
<arno11>
*again
<arno11>
got 50mA now
<freemangordon>
ok, but iphbd waits in select(), so it cannot increase the idle draw, iiuc
<freemangordon>
also, the kernel driver is not involved
<freemangordon>
arno11: basically, kernel driver queues keepalives untile there is some other activity
<freemangordon>
so I can;t see how would it increase the idle consumption as it prevents radios from being turned on
<arno11>
but that's a fact that current draw is higher if we don't restart ipbh properly
<arno11>
like h-s-m or nokia-modem sometimes btw
<freemangordon>
wthym "properly"?
<arno11>
i mean using the right command
<freemangordon>
arno11: process waiting in poll() is idle
<freemangordon>
and this is where iphbd stays most of the time
<freemangordon>
if not all the time
<arno11>
ok
<freemangordon>
so it is something else, IIUC
<arno11>
maybe something is unstable on boot
<freemangordon>
?
<arno11>
i mean, ATM, i have to restart h-s-m, ipbh and sometimes nokia modem after boot
<freemangordon>
why?
<freemangordon>
do you still have issue with presence-ui?
<arno11>
ofc
<freemangordon>
ok, lets debug that first
<freemangordon>
maybe there is a common root for all the issues you have
<arno11>
yes i think so
<freemangordon>
so, after boot there is no "availability" button in h-s-m?
<arno11>
yes
<freemangordon>
and there is no coredomp for h-s-m?
<freemangordon>
*coredump
<arno11>
no coredumps, i need to go (kids), back in 30 min
<freemangordon>
ok
arno11 has left #maemo-leste [#maemo-leste]
arno11 has joined #maemo-leste
<Wizzup>
tmlind: for kexecboot on mz617 we need android 4.0.4 as well yeah, not 4.1.2?
<Wizzup>
hm it's still 3.0.8
<Wizzup>
tmlind: uvos: as I understand it, cache is only 900MB, so that's all we get for our rootfs?
<Wizzup>
ah I see uvos write this (way) earlier:
<Wizzup>
00:10 < uvos> we have to create a small 600 mb ish image that we flash to preinstall that copyies itself over to userdata and then downloads the rest of the packages
<Wizzup>
ok, so I have root now om mz617, and almost done reading the whole backlog over the last years regarding mz617
<Wizzup>
it seems like I can nuke some android partitions for mainline now that I have it hooked up to lab psu, since I won't run into battery charging problems
<Wizzup>
one thing that is not clear to me yet is is the utags-mz617-32 are also ok for a mz617 16GB tablet
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
my mz616 is also rooted, and it is 32GB, so it seems like I should be able to get kexecboot on there
parazyd has joined #maemo-leste
<Wizzup>
uvos: tmlind: ok, so I got my mz616 flashed with kexecboot. I dd'd both utags and kexecboot from android, and then I got kexecboot. that booted into android, and that molested my cache partition and thus kexecboot, but then with fastboot I can restore kexecboot and so get back in
<Wizzup>
I think the next step is for me to get some serial set up because kexecboot really quickly just wants to boot to android
mqlnv has quit [Ping timeout: 268 seconds]
mqlnv has joined #maemo-leste
<Wizzup>
uvos: you didn't pull in the commits for builddeb in the maemo-6.6 branch
<Wizzup>
uvos: I pushed untested changes to builddeb to maemo-6.6-buildeb
<Wizzup>
I'll try for an experimental build
<Wizzup>
uvos: did you also include all the config changes that we have in our maemo branches?
<Wizzup>
looks like we didn't have them anymore (?)
<Wizzup>
in any case, let's see if/where this experimental build fails
<Wizzup>
uvos:
<Wizzup>
arch/arm/boot/dts/ti/omap/motorola-mapphone-common.dtsi:237.30-250.4: ERROR (phandle_references): /ocp/interconnect@48000000/segment@0/target-module@72000/i2c@0/touchscreen@4a: Reference to non-existent node or label "touchscreen_pins"
<Wizzup>
arch/arm/boot/dts/ti/omap/motorola-mapphone-common.dtsi:252.14-261.4: ERROR (phandle_references): /ocp/interconnect@48000000/segment@0/target-module@72000/i2c@0/isl29030@44: Reference to non-existent node or label "als_proximity_pins"