Open GoogleCodeExporter opened 9 years ago
Can confirm same problem on a Nexus 5 with Lollipop, the voice being sent from
SipDroid is garbled. Incoming voice is decoded and played back fine, unless
the other end is an exact duplicate setup when it will obviously sound garbled!
RTP packets are being sent ok, so presume it's something to do with microphone
capture, buffering, gain etc. A fix would be much appreciated.
Original comment by Poaklan...@gmail.com
on 3 Dec 2014 at 8:00
Issue 1156 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 17 Dec 2014 at 7:36
Since I have no Android L device I can't fix it. The Samsung 10.1 2014 that I
have will be updated in March 2015.
What you could try is if voice is transmitted in speakerphone, or in bluetooth
modes.
A logcat trace might also be helpful. Any other ideas?
Original comment by pmerl...@googlemail.com
on 17 Dec 2014 at 7:37
brother pmerl, any update on this issue since you have got the lolipop update
Original comment by talkfon...@gmail.com
on 14 Apr 2015 at 5:49
I installed CM12 on my Samsung Note 10.1 (2014). Sipdroid worked fine. So it's
not a general Lollipop incompatibility. Instead it must be related to specific
devices.
Is it just the Nexus 5? Then I should get such a device to test.
Original comment by pmerl...@googlemail.com
on 29 Apr 2015 at 11:10
read Issue 1156 this is an ART runtime issue. As with the devices listed there
are not running lollipop and if they switch to dalvik runtime everything works,
but when they use the ART runtime things stop working. The reason why lollipop
is looked at is because it runs ART runtime by default
Original comment by scicomru...@gmail.com
on 30 Apr 2015 at 1:10
The issue with ART was fixed in Sipdroid 3.6 (Dec 2014). Actually I've tested
Sipdroid on my Samsug tablet with AOSP Android 5.1 which should be always on
ART.
In Android Playstore there are complaints about Sipdroid not running properly
on HTC and Nexus 4/5/7 devices, but there is nobody mentioning
incompatibilities to Samsung.
Original comment by pmerl...@googlemail.com
on 30 Apr 2015 at 2:59
Original issue reported on code.google.com by
kena...@gmail.com
on 3 Dec 2014 at 9:42