On Sun, Nov 30, 2008 at 01:32:20PM +0000, Rui Miguel Silva Seabra wrote:
> On Sun, Nov 30, 2008 at 07:50:22PM +0800, John Lee wrote:
> > Echo:
> > 
> > Since there are different hw versions out there (a5, a6, a7), it's
> > impossible to provide one alsa state file that suits all models.
> > However, it seems you can always find appropriate values for your
> > neo.  My way is to adjust
> > control.4 Speaker Playback Volume in
> > /usr/share/openmoko/scenarios/gsmhandset.state
> > 
> > the max value is 127, 95 works best on my a5.  With volume level 3 or
> > 4 in qtopia dialer, the other side can hear no echo while I get good
> > audio quality.
> 
> This is interesting, I have an a5 and the default value of FSO M4.1a:
> 
>         control.4 {                             
>                 comment.access 'read write'     
>                 comment.type INTEGER            
>                 comment.count 2                 
>                 comment.range '0 - 127'         
>                 iface MIXER                     
>                 name 'Speaker Playback Volume'  
>                 value.0 116                     
>                 value.1 116                   
>         }                                     
> 
> Sometimes I ask people on the other side: do you hear echo? The answer
> has been no.
> 
> Rui

116 was the old value I use before I updated the alsa state file from
FDOM.  There was no/very little echo, but the other side always
complains they cannot hear me very well.  I also feel the receiver
(handset speaker) is unnecessarily loud sometimes.

The new alsa state file uses 116, but boosts the mic path a little bit
more, so it solved the "can't hear me" problem while makes the echo
even easier to happen.  With the new state file, 95 is the best value
for me because I can always make it louder if necessary with Tick's
volume bar in qtopia.


- John

_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Reply via email to