<duuude>
U-Boot with kernel 2.6.28-omap1 won't get installed
<duuude>
it violates "third party package policy"
<duuude>
what to exactly do now?
<freemangordon>
it takes the last wdm device (cdc-wdm3). if I change that to use first device (cdc-wdm0), at least NAS and SMS notifications are comming
<tmlind>
freemangordon: oh nice :)
<freemangordon>
this is for device in BP mode
<freemangordon>
but I assume it will be the same if we boot leste
<tmlind>
should be yeah :)
<freemangordon>
will test that later on
<freemangordon>
also, I have upstream ofono working with it, without gsmmux
<freemangordon>
is it needed for voica calls, right?
<freemangordon>
or, is it?
<freemangordon>
if qmimodem in ofono support voice calls over qmi, do we need gsmmux?
<tmlind>
for voice call routing and mixer we need something for alsa
<freemangordon>
but do we need gsmmux?
<tmlind>
gnss should be doable over qmi too
<freemangordon>
cool
<tmlind>
you can use the tool i did to dump and diff the modem nvram and attempt to replicate the same with qmi commands
<freemangordon>
wait, WTYM? qmi interface is standard
<tmlind>
alsa needs some notification, but that might be doable with the audiocalld or whatever the newish daemon was called
<tmlind>
motorola implemented some custom calls that likely just tweak some nvram options and the modem firmware then sets things as requested
<tmlind>
the qmi calls also mostly just set nvram values fyi
<freemangordon>
are you sure motorola implementd custom qmi calls? what for?
<tmlind>
for their audio setup i think
<freemangordon>
I just doubt that motorola had to do it besides perhaps some FW download
<tmlind>
anyways, if we end up adding the gsmmux stuff to ofono later on, it should be implemented with raw read and write using ell
<freemangordon>
but we still need the kernel driver, right?
<tmlind>
no need to try to use atmodem stuff for it
<tmlind>
right, kernel driver or the userspace tool that won't work with pm
<tmlind>
whatever attach it was called
<freemangordon>
ok I lack teh details here
<tmlind>
cool nice to hear you figured out the missing notifications
<tmlind>
anyways, i agree with you, let's try to use mainline ofono with qmi where possible and then patch in the gsmmux if and when needed
<freemangordon>
:nod:
duuude has quit [Ping timeout: 256 seconds]
<freemangordon>
I'll try to prepare and send patches for upstreaming of motmdm
<tmlind>
for the voice call alsa driver, don't recall if we need to do some gsmmux modem commands beyond mixer and dtmf
<freemangordon>
I have no clue
<freemangordon>
but anyways we need qmi voice calls working in upstream first
<tmlind>
it could be we're only configuring the mcbsp and pmic for the tdm use for voice call
<freemangordon>
mhm
<freemangordon>
but you do that in the driver
<tmlind>
yeah
<freemangordon>
which looks like a hack as well, but that's another story :)
<tmlind>
right, it should be the whatever voicecallaudiod doing it nowadays and that likely already has qmi support
<freemangordon>
ok, thanks! will keep you informed on the progress.
<freemangordon>
bbl
<tmlind>
ok great, ttyl
<sicelo>
note that voicecallaudiod might not have a future ... there's talk to drop it once pipewire can handle some of those things by itself
duuude has joined #maemo-leste
<tmlind>
oh ok good to know, anyways nice to hear there's some kind of userspace path for dealing with these things
xmn has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
<duuude>
U-Boot with kernel 2.6.28-omap1 won't get installed
<duuude>
it violates "third party package policy"
<duuude>
what to exactly do now?
<duuude>
Wizzup freemangordon
<duuude>
it wasn't like this the year before or at least I don't remember such a thing.
<sicelo>
i said install it with apt. did you try that?
xmn has joined #maemo-leste
<duuude>
sicelo: I probably wasn't online when you said that
<duuude>
though, I found an apt command from postmarketos' gitlab issues which also didn't work
xmn has quit [Quit: ZZZzzz…]
<sicelo>
what command was it?
<duuude>
apt install uboot-menu? was something like this
xmn has joined #maemo-leste
<sicelo>
maybe share the link :-) ... there's no 'apt install' in maemo fremantle
<duuude>
I don't know what was the problem the first time (I had entered "apt-get") but it worked this time: apt-get install u-boot-flasher u-boot-tools u-boot-bootimg
<duuude>
sicelo: how to enable on-screen keyboard? I can't enter ">"
<duuude>
these weren't problems the first time
<sicelo>
what device?
<duuude>
n900
<duuude>
on the terminal
<sicelo>
Fn+Ctrl, i think ... the standard way in Fremantle
xmn has quit [Quit: ZZZzzz…]
<freemangordon>
tmlind: why not using AT interface for voice calls?
<freemangordon>
I tried and got NO CARRIER, but this could be because I didn;t set-up the modem properly
parazyd has joined #maemo-leste
<duuude>
I got stuck in "Welcome to Leste"
<duuude>
it doesn't seem to take input
<duuude>
it somehow went away, but looking frozen isn't good ux
<sicelo>
i think on first boot, N900 just can't handle the amount of stuff happening in the background. using a fast SD card helps somewhat
<arno11>
btw "Welcome to Leste" seems to be a problem on N900 and a bit annoying for users
<arno11>
if you click nowhere for at least 3 min once H-D is visible, everything is fine then. Otherwise N900 is slowing down a lot and users think Leste is really slow and unusable on N900...
<Wizzup>
we could have a splash screen, or ry to emit the h-d is ready signal later
duuude has joined #maemo-leste
<arno11>
a splash screen could be cool
uvos__ has joined #maemo-leste
<arno11>
btw there is quite a similar issue with 'pin entry code' applet: N900 is unusable until the applet appears on the screen. Not a major concern but also annoying for new users.
<arno11>
bbl
arno11 has left #maemo-leste [#maemo-leste]
xmn has joined #maemo-leste
diejuse has joined #maemo-leste
duuude has quit [Ping timeout: 268 seconds]
duuude has joined #maemo-leste
<duuude>
sicelo, Wizzup: addition of a text "(the freeze is normal)" could be nice.
<duuude>
would leste dry up the battery to the last second like before?
eval has quit [Ping timeout: 256 seconds]
diejuse has quit [Quit: Client closed]
gnarface has quit [Ping timeout: 256 seconds]
nohit has quit [Ping timeout: 246 seconds]
eval has joined #maemo-leste
nohit has joined #maemo-leste
eval has quit [Ping timeout: 268 seconds]
gnarface has joined #maemo-leste
eval has joined #maemo-leste
antranigv_ has joined #maemo-leste
antranigv has quit [Ping timeout: 240 seconds]
TheTechRobo has quit [Ping timeout: 264 seconds]
eval has quit [Ping timeout: 256 seconds]
antranigv_ is now known as antranigv
TheTechRobo has joined #maemo-leste
eval has joined #maemo-leste
ceene has quit [Ping timeout: 260 seconds]
nela has quit [Ping timeout: 264 seconds]
diejuse has joined #maemo-leste
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
<uvos__>
the greeting text is common to all devies
<uvos__>
only the n900 has issues so its not so easy
<uvos__>
if it really is unresponsive for 3 minutes i dont think a splash screen is enough really
<uvos__>
that calls for at least a thobber otherwise people will think its frozen
<tmlind>
freemangordon: well the at interface is buggy from what i recall..
<tmlind>
freemangordon: also, if you're booting to bp mode with m-l kernel, the gsmtty kick might cause the qmi notifications to happen for you on your x86 vm..
<freemangordon>
tmlind: I am booting from power-off and d4 is attached to my ubuntu laptop :)
TheTechRobo has quit [Ping timeout: 256 seconds]
<freemangordon>
I am not sure what you meant
TheTechRobo has joined #maemo-leste
<freemangordon>
qmi notifications didn't happen in that setup until I changed to /dev/cdc-wdm0
<freemangordon>
this https://pastebin.com/qwnjSXmG is how things look like with upstream ofono and d4 modem attached in BP only mode
<freemangordon>
only qmi interface is used, not AT, no MUX (gsmtty)
<freemangordon>
not sure how to test gps though
<freemangordon>
BTW, what is the 'official' name of the modem? m6600?
diejuse has joined #maemo-leste
<uvos__>
freemangordon: if you use bp mode from the bootloader the deivce routes out the usb interface of the modem
<uvos__>
freemangordon: if you then boot the leste kernel it might affect the result because it uses the gsmtty interface
<uvos__>
is what he is saying
<freemangordon>
uvos__: I understand that, but I think the plan is to try to not use gsmtty. Also, I doubt I will lose notifications in qmi because of gsmtty. However, will test on the device in couple of minutes and will see
<freemangordon>
also, we'll have issue with notifications as currently I am not aware of any way to disable them (on qmi interface that is) outide of ofono
<freemangordon>
and ofono does not expose any interface for doing that
<uvos__>
sure @plan, no idea at if gsmtty use by ofono on device affects qmi connected to the host
<freemangordon>
it should not, but... who knows :)
<freemangordon>
oh, but ofono *does not* use gsmtty
<freemangordon>
well, the upstream one
<freemangordon>
not what we have currently in leste
<uvos__>
sure but what we have in leste ist running in this configuration
<uvos__>
also mce kicks gsmtty
<freemangordon>
but I will replace ofono on my d4 with upstream one
<uvos__>
right ok
<uvos__>
mce still kicks gsmtty iirc
<freemangordon>
yeah
<freemangordon>
do disable RSSI on display off, right?