QtMoko audio state work

2012-11-25 Thread Neil Jerram
Hi Radek, After a day yesterday where the A3 audio didn't work for me in several calls, I decided to take a closer look at the QtMoko audio code. That led to a sequence of small (I think) cleanups, and a reworking of the audio state handling code, and I'd appreciate hearing what you think about t

Re: QtMoko audio state work

2012-11-26 Thread Radek Polak
On Sunday, November 25, 2012 02:55:59 PM Neil Jerram wrote: > Hi Radek, > > After a day yesterday where the A3 audio didn't work for me in several > calls, I decided to take a closer look at the QtMoko audio code. That > led to a sequence of small (I think) cleanups, and a reworking of the > aud

Re: QtMoko audio state work

2012-11-26 Thread Neil Jerram
Radek Polak writes: > Hi Neil, > thanks for the patches, i'll take a look at them in a few days. I am going to > have a busy weeks at paid work probably until the Christmas so i have to slow > down on QtMoko side a bit... No problem, and thanks. I hope that other work goes well! Regards,

Re: QtMoko audio state work

2012-12-01 Thread Radek Polak
On Sunday, November 25, 2012 02:55:59 PM Neil Jerram wrote: > After a day yesterday where the A3 audio didn't work for me in several > calls, I decided to take a closer look at the QtMoko audio code. That > led to a sequence of small (I think) cleanups, and a reworking of the > audio state handli

Re: QtMoko audio state work

2012-12-01 Thread Neil Jerram
Radek Polak writes: > Yup it looks ok, will test it later but it's alreaady pulled in my git. Thanks. Given that, I think it's worth me writing a bit more about where/how my work is going, and there's one bugfix below that you should cherry-pick: please look for "While doing that I noticed a bu

Re: QtMoko audio state work

2012-12-01 Thread Radek Polak
On Saturday, December 01, 2012 06:15:04 PM Neil Jerram wrote: > Given that, I think it's worth me writing a bit more about where/how my > work is going, and there's one bugfix below that you should cherry-pick: > please look for "While doing that I noticed a bug". Apart from that > bugfix I don't

Re: QtMoko audio state work

2013-01-16 Thread Neil Jerram
I wanted to write a bit of an update on my recent GTA04/QtMoko work, and would appreciate people's thoughts. This is still focussed on audio handling, because with my A3 I still haven't reached a point of having fully reliable phone calls. (As usual, for the sake of avoiding any possible negative

Re: QtMoko audio state work

2013-01-17 Thread Radek Polak
On Thursday, January 17, 2013 01:52:57 AM Neil Jerram wrote: > (In general, for some reason, it appears that the floating point code > in Pulseaudio and its dependencies doesn't run any better on armhf > than it does on armel.) Hi Neil, do you have also armhf compiled kernel? I had armel ke

Re: QtMoko audio state work

2013-01-17 Thread Radek Polak
On Thursday, January 17, 2013 01:52:57 AM Neil Jerram wrote: > (As usual, for the sake of avoiding any possible negative marketing, I > should point out that the main problems here are A3-specific. I hope, > and believe to be the case, that phone calls are already reliable on > A4.) Yes, A4 work

Re: QtMoko audio state work

2013-01-17 Thread Neil Jerram
On Thursday, January 17, 2013 12:49:04, Radek Polak wrote: > On Thursday, January 17, 2013 01:52:57 AM Neil Jerram wrote: > > > (In general, for some reason, it appears that the floating point code > > in Pulseaudio and its dependencies doesn't run any better on armhf > > than it does on ar

Re: QtMoko audio state work

2013-01-22 Thread Neil Jerram
Radek Polak writes: >> I've now reimplemented the GTA04 neoaudioplugin.cpp code so that it >> moves between audio states by changing those 7 switches, instead of >> using ALSA state files, and that seems to work well (including for >> PhoneHeadset, subject to A3 software routing trouble). > > Nic

Re: QtMoko audio state work

2013-01-27 Thread Neil Jerram
Neil Jerram writes: > I'm pretty sure I saw some voice routing problems on a few occasions > even with pasuspender. > > However, since moving back to gta04-gsm-voice-routing, and adding Neil > Brown's change to start the 2 capture streams at the same time, I've had > a few successful calls and no

Re: QtMoko audio state work

2013-01-28 Thread Neil Jerram
Neil Jerram writes: > I had an unsuccessful call this evening; it was an incoming one. The > gsm-voice-routing log for it is below; I plan to analyse this more > myself to see if there's a repeating pattern of overruns and underruns, > but thought it worth posting in case someone else sees and u

Re: [Gta04-owner] QtMoko audio state work

2013-01-17 Thread Neil Jerram
On Thursday, January 17, 2013 01:37:58, NeilBrown wrote: > On Thu, 17 Jan 2013 00:52:57 + Neil Jerram > wrote: > > > > The upshot of all that is that I'm now inclined to look more again at > > the other possible solutions, i.e. gta04-gsm-voice-routing (by Radek) > > and alsaloop (as used in

Re: [Gta04-owner] QtMoko audio state work

2013-01-17 Thread Radek Polak
On Thursday, January 17, 2013 02:50:54 PM Neil Jerram wrote: > On several occasions, on receipt of a real incoming call, I've just got a > kind of distorted quiet growling noise > instead of proper audio from the far > end. For me the growling took just one 1 second - IMO it was some old recorde

Re: [Gta04-owner] QtMoko audio state work

2013-01-17 Thread NeilBrown
On Thu, 17 Jan 2013 14:43:19 +0100 Radek Polak wrote: > > The simplicity of > > gta04-gsm-voice-routing is appealing, but I know from previous > > experience that it sometimes fails completely. > > For me the problem was that some other program had soundcard open and gta04- > gsm-voice-routing

Re: [Gta04-owner] QtMoko audio state work

2013-01-17 Thread NeilBrown
On Thu, 17 Jan 2013 13:50:54 + Neil Jerram wrote: > > > > What sort of stability problems do/did you experience with > > gsm-voice-routing? > > On several occasions, on receipt of a real incoming call, I've just got a kind > of distorted quiet growling noise > instead of proper audio from