Echo issue on OM2008.08 potentially solved

Jean-Eric Cuendet ml.jecuendet at gmail.com
Sat Aug 30 23:42:16 CEST 2008


> Now you can request a new device for the modem using:
> identvar=$(date +%s)
> dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer
> /org/pyneo/Muxer
> org.freesmartphone.GSM.MUX.AllocChannel string:$identvar | grep
> string | awk -F '"' '{ print $2 }'
>
> It should print something like '/dev/pts/2'. Now use 'minicom -s' and
> set the device under 'serial device' to the value printed by dbus-send.
> Wait for a response to the AT initiation sequence and then type in:
> AT%N0187
>

Did that. But echo still here...
Could it be that the mic gain is still too high? How to change it?
And when leaving minicom, should I exit with reset or without?
Is it still active after a reboot or should I do that after each reboot?
Thanks.
-jec




>
> The modem should respond with a message that AEC and Noise reduction is
> now on.
>
> Call the Neo from another phone where you heard an echo before and see
> if the echo is gone.
>
> Cheers,
>        Florian
>
> [1]
>
> http://n2.nabble.com/calypso-hardware-echo-suppression--tp784752p786187.html
> --
> DI Florian Hackenberger
> florian at hackenberger.at
> www.hackenberger.at
>
> _______________________________________________
> Openmoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/community/attachments/20080830/b1041385/attachment-0001.htm 


More information about the community mailing list