LjL has quit [Read error: Connection reset by peer]
LjL has joined #maemo-leste
enyc has quit [Remote host closed the connection]
enyc has joined #maemo-leste
fifi has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
fifi has quit [Remote host closed the connection]
fifi has joined #maemo-leste
wunderwungiel has joined #maemo-leste
wunderwungiel has quit [Remote host closed the connection]
maemish_ has joined #maemo-leste
fifi has quit [Remote host closed the connection]
fifi has joined #maemo-leste
ahmed_sam has quit [Read error: Connection reset by peer]
rafael2k has quit [Ping timeout: 244 seconds]
fifi has quit [Quit: Leaving]
rafael2k has joined #maemo-leste
akossh has joined #maemo-leste
fab_ has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
fab_ has quit [Quit: fab_]
maemish_ has quit [Quit: Connection closed for inactivity]
fab_ has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: timeout during writing]
Guest91 has joined #maemo-leste
Guest91 has quit [Client Quit]
maxwelld has left #maemo-leste [Error from remote client]
wunderwungiel has joined #maemo-leste
<wunderwungiel>
Is there some command like startxfce4 but starting Hildon on Leste through command line?
xmn has joined #maemo-leste
akossh has quit [Read error: Connection reset by peer]
<Wizzup>
I would look at what diejuse did
akossh has joined #maemo-leste
<wunderwungiel>
Yeah I'm analyzing it right now
<wunderwungiel>
I want to run Leste on Android without root, through proot on Termux, just like the distros from Andronix apps and similar
<wunderwungiel>
For now I can access Leste's raspi2 image command line
<wunderwungiel>
I once accessed the Hildon, but without any backgrouds, and colors. But I was able to launch apps. Now I don't remember what I exactly did and I can't repeat it :D
<Wizzup>
so the geneic image I gave you didn't work?
<wunderwungiel>
AlienDalvik on F(x)tec is arm32
<wunderwungiel>
I will try yours image on S5e which is arm64 soon
wunderwungiel has quit [Ping timeout: 246 seconds]
<Wizzup>
ah
fab_ has quit [Quit: fab_]
wunderwungiel has joined #maemo-leste
fab_ has joined #maemo-leste
pere has quit [Ping timeout: 245 seconds]
wunderwungiel has quit [Quit: Konversation terminated!]
<sicelo>
i decided to just email him and explain my findings, because i could see he was still active (in fact is the maintainer of the IR framework anyway) ... he offered to resubmit the patch.
<sicelo>
bencoh: know a thing or two about alsa/asoc/dapm?
* sicelo
is angry at N900's audio codec :p
<bencoh>
ehh ... I've read code and fiddled a bit, but not that much ... I'd be glad to help if I can :)
<sicelo>
i'm trying to get the earpiece working, so with arno's great work, we can have 'normal' calls
<sicelo>
i can see how this whole thing fits together, by looking at the schematics, and the driver
<sicelo>
but so far i've not had success getting sound out of it
<bencoh>
on n900 the earpiece is connected to cpu / audio codec, right? or is the audio from the modem routed to earpiece?
<sicelo>
i can summarize it as follows: the earpiece is connected to an output of the 2nd codec (well, 2nd stage of the one codec). the input of this codec is hardwired to a mono output of the first codec
<bencoh>
uhh
<bencoh>
that's funky, but ... so be it
<sicelo>
so in connection with modem audio, it will be cpu -> codec A -> DAC(A) -> mono out -> line2r (codec B) -> ... -> Left High Power Output (codec B)
<bencoh>
so basically you should be able to just play audio from linux to that specific codec output to test it?
<sicelo>
yes, that's what i've been doing
<sicelo>
except, clearly i'm getting it wrong somewhere, since aplay hangs (which is normal if you've got the routing wrong)
<bencoh>
possibly meaning that something should be enabled/powered first
<sicelo>
i *think* both codecs are correctly powered
<bencoh>
did you try dumping amixer output on fremantle and compare it to what you get?
<bencoh>
also you can use /sys/kernel/debug/asoc
<sicelo>
at least /sys/kernel/debug/asoc/ 'sees' both of them and can show the endpoint configurations
<bencoh>
and /sys/kernel/debug/tracing/events/asoc
<sicelo>
maybe the kernel i was testing with doesn't have correct stuff for tracing. last time tried, nothing showed up
<bencoh>
you can enable it (/sys/kernel/debug/tracing/events/asoc/enable), then enable /sys/kernel/debug/tracing/tracing_on, and tail /sys/kernel/debug/tracing/trace_pipe
<sicelo>
i'll check the config
<bencoh>
I'd suggest enabling it if it's disabled, it can be very useful for that kind of stuff
ahmed_sam has quit [Read error: Connection reset by peer]
parazyd has joined #maemo-leste
<sicelo>
thanks. i'll have a go at it again.
<sicelo>
i can see jack insertion events
Juest has joined #maemo-leste
parazyd has quit [Read error: Connection reset by peer]
<sicelo>
bencoh: the next question is probably: how to interpret the trace? :p
<sicelo>
this one was not specific to earpiece ... just testing how the thing works
parazyd has joined #maemo-leste
<sicelo>
previously i had looked at /sys/kernel/debug/tracing/trace , so i guess that's why i never saw anything useful
arno11 has joined #maemo-leste
<sicelo>
arno11: so it looks like we have no alternative - BT really *must* work before the fm receiver works
<sicelo>
while it has i2c access, by default it's ... dead. i2cdetect won't find it. to turn on the i2c access, you need to send it a specific bluetooth command :p
<arno11>
ok
akossh1 has joined #maemo-leste
akossh has quit [Ping timeout: 256 seconds]
<arno11>
btw i successfully ported Pierogi ! the app works fine (like Fremantle but a bit slower), able to send pulses (visible with a phone camera) but pulses seems a bit too slow to be recognized well (that's a well known issue with pwm-ir-tx...). I got better results with LIRC/irsend because it's easy to repeat pulses quickly