<Wizzup>
I believe one of the problems was what I mentioned before - hildon-desktop renders on the wrong display output
<Wizzup>
meanwhile I'll get my img ready
<Wizzup>
s/img/sd card/
<Wizzup>
yifei1: most of the porting typically is solving bugs, but yes, normally it'd be kernel + image-builder + leste-config stuff
<yifei1>
Wizzup: thanks! downloading and will debug it later.
<Wizzup>
if we solve the hildon-desktop bug then just kernel remains, which I think rafael did some work on
<Wizzup>
let me also drop him an email
<Wizzup>
oh looks like I already had it set up on my ppp judging from my emails
<Wizzup>
I really am overtaxing my memory :)
ac_laptop has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
mdz has joined #maemo-leste
System_Error has joined #maemo-leste
<Wizzup>
yifei1: well I got it to boot but I got frustrated due not being able to get ssh or serial (my serial cable is on a pallet on its way to me in a week or two)
<Wizzup>
if you have a serial cable you can probably get the ui to behave and I can help you with that
<Wizzup>
found another serial :)
<Wizzup>
ok so it looks like getty is not being spawned on the serial interface in rafaels image
<Wizzup>
and while trying different serial interfaces the device reset
xmn has joined #maemo-leste
ceene has quit [Ping timeout: 268 seconds]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 256 seconds]
<freemangordon>
Wizzup: I think kernel/dts issue was identified, leading to wrong display being reported by xrandr
<freemangordon>
not sure if there is a fix though
<Wizzup>
yes, so I just wanted to go in and use xrandr to get a sensible setup
<Wizzup>
but I wasn't able to use serial or keyboard well, and the ts being odd + weird refresh makes it not possible to use the ts to set up wifi either
<Wizzup>
I will try again a bit later, I just got frustrated, this has happened to me too often :D
kiva has joined #maemo-leste
<Wizzup>
(that I have a device but I just don't way a have to get a console up)
<Wizzup>
like /etc/inittab doesn't seem to start getty on serial so I just see kernel messages
<Wizzup>
and if I plug in the serial, the screen turns off
<Wizzup>
(?)
Livio has joined #maemo-leste
<kiva>
I just tested pavucontrol-qt and it was nice suprise that it has full featured Maemo UI..even screen rotation works..I think it is ready to put to download from Application Manager or even to Settings into Leste image.
<kiva>
I think it is only way set volume during phone call.
<kiva>
or is there another way?
<Wizzup>
what device are you using?\
<Wizzup>
I think -right now- the volume buttons don't yet work while in a call, but this is something we should fix
<kiva>
Pinephone Keyboard. Can there check code how osso-xterm capture volume buttons to zoom-in\out
<kiva>
?
<kiva>
same way capture to earpiecevolume.
<Wizzup>
the applet does capture these, it just doesn't switch well when you're in call
<Wizzup>
it works ok for audio/media
<Wizzup>
I need to go -- back in an hour or so
kiva has quit [Quit: Client closed]
Livio has quit [Ping timeout: 268 seconds]
f_ has joined #maemo-leste
f_ has quit [Remote host closed the connection]
f_ has joined #maemo-leste
f_ has quit [Remote host closed the connection]
f_ has joined #maemo-leste
mdz has quit [Quit: mdz]
mdz has joined #maemo-leste
retr0id9 has joined #maemo-leste
retr0id has quit [Read error: Connection reset by peer]
retr0id9 is now known as retr0id
Livio has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
Wizzup: (for conversations release) great !
<Wizzup>
yeah
arno11 has quit [Quit: Lost terminal]
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
<uvos>
Wizzup: why is the vcm plugin not setting BACKEND_FLAG_CELLULAR?
<Wizzup>
what does this flag do?
<uvos>
its given to the audio routing module that may change its behvior based on that
<uvos>
(but atm dosent)
<Wizzup>
uvos: well it shouldn't do this for say SIP calls
<Wizzup>
and the backend does both
<Wizzup>
although I guess I could -probably- change this depending on the backend type
<uvos>
the the vcm module should register 2 backends one for calls and one for sip
<uvos>
obv
<uvos>
nothing restricts it to haveing just one
<uvos>
and schemes needs to be different too
<uvos>
as do the new sphone_contact_field_t hints
<uvos>
and no_route
<uvos>
etc
<uvos>
btw backend_name
<uvos>
i find the id to be a pretty poor choice for a backend name
<uvos>
backend_name is used by sphone for display purposes only and should reflect that, so it should be cellular and maybe sip: <number> as desired
mdz has quit [Ping timeout: 245 seconds]
<Wizzup>
21:16 < uvos> i find the id to be a pretty poor choice for a backend name
<Wizzup>
yeah definitely it is
<Wizzup>
that's iwp
<Wizzup>
wip
System_Error has quit [Remote host closed the connection]