[Gta04-owner] Replicant: no sound during calls

[Lukas Maerdian]

Am 13.01.2015 um 22:40 schrieb L.B.:
> 
>> Great, that's exactly what can be expected right now.
> 
> Good to know :)
>>
>> But: when you suspend the phone, the modem logout from the network and
>> only login after resume, also 3G data will be broken after resume (you
>> have to disable and re-enable it, to make it work again).
> ok, yet I managed to call the phone while it was in suspend. However the
> modem was not accessible and the phone could not hang up, as you can expect.
> 
>> Also, I did not yet optimize anything for power management/consumption,
>> so don't expect it to last too long.
> 
> 8h use time is enough for me to get a useable phone for work.

I did not yet test how many hours we get with the current state. If you
do an experiment, please let us know!

>> The non-optimal sound quality/distorted voice is expected (because of
>> software-routing). This will be gone once we get hardware voice routing
>> to work. You can experiment with it if you have an GTA04A4, by adopting
>> the values in /system/etc/tinyalsa-audio.xml.
>> I only have an A3 and thus could not implement/test hardware-routing. If
>> you get it to work, please send in your patches! It should just be a
>> matter of a correct tinyalsa-audio.xml configuration.
>>
>> You can enable hardware-routing, by changing the "Voice route" control
>> from "Voice to SoC" to "Voice to twl4030", and then you need to find
>> good values for all the other controls, in order to make the voice come
>> through.
>>
> I do have an A4 board, I've been experimenting with hardware routing but
> so far, no luck. Is the sound routing the same with VoIP? That would
> make testing easier. Also, is it possible to modify the
> tinyalsa-audio.xml file via ssh (or other remote tool)? If so, how can I
> update the changes/reload alsa?

VoIP works with nice voice quality. But the routing is completely
different to GSM voice routing, as the voice does not have to get
transferred to and from the modem module.

tinyalsa-audio.xml can be modified remotely via the Android Debug Bridge
("adb shell"). The changes are reloaded on reboot, there probably is a
more elegant way to reload alsa, but I don't know it.

Best,
  Lukas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.goldelico.com/pipermail/gta04-owner/attachments/20150113/14ccaba2/attachment.asc>