Open GoogleCodeExporter opened 9 years ago
Seems like Hardware (some Phones work, some like ZTE and Pulse wont) and may
caused by Sipdroid too because 1.3.7 works here on Pulse for Example.
Original comment by holger2...@gmail.com
on 27 Mar 2011 at 11:46
Many reported, that 1.3.7 works well, for ZTE (Blade) also, that's indicates
the problem is (also?) in the code. But not sure.
Original comment by gthrepw...@gmail.com
on 27 Mar 2011 at 1:02
ZTE Blade, same issue. Seriously, how much time it takes to fix this?
Original comment by flake.re...@gmail.com
on 4 Apr 2011 at 2:45
Please provide configurable audio output device settings.
Original comment by mironr...@gmail.com
on 10 Apr 2011 at 3:36
I'm hitting the same issue on a ZTE Blade. Funny enough, Skype has the same
problem and this is the supposed fix:
http://android.modaco.com/content/zte-blade-blade-modaco-com/331808/skype-speake
r-fix/
I'm guessing sipdroid is using similar API calls to Skype. Perhaps the same
solution can be used.
Thanks!
Original comment by mal...@gmail.com
on 11 Apr 2011 at 2:27
Based on the link in Comment 55, I have posted a patch in Comment 94 for Issue
366 which fixes the problem for ZTE Blade a week ago, but so far no reaction...
Original comment by morav...@gmail.com
on 15 May 2011 at 6:52
Snap on Samsung GT i5800 on android 2.1, If you toggle between the two
(ear/loud) for about 10 - 60 seconds, u will hear the audio, crackle in until
its perminant.
HTC & My old ZTE Racer ran sipdroid perfectly......shame samsung is troublesome
Original comment by badger...@gmail.com
on 1 Nov 2011 at 12:46
i´ve had the same problem using an zte skate / medion p4310 / base lutea 2
i changed to pbxes.com and the problem was gone :-D
Original comment by knex...@gmail.com
on 7 Nov 2011 at 5:06
[deleted comment]
The fix works fine for me with a ZTE Crescent. Would be nice to see an official
fix/option to toggle speaker modes in preferences though.
Original comment by timsudal...@gmail.com
on 17 May 2012 at 12:00
Attachments:
[deleted comment]
Same problem for me now android 4.0.4 cyanogenmod9 /htc sensation.
It just go through speaker for some calls or maybe it's just random, i'm still
testing it out.
Original comment by kapusn...@gmail.com
on 18 Oct 2012 at 6:17
How is this still an issue, almost 3 years after first being reported?
sipdroid has been working acceptably since I installed it, but then I upgraded
to the 1/23 version of cyanogenmod 10.1, and suddenly all audio is coming out
of the external speaker. Even after completely wiping my Verizon Galaxy S3 and
re-installing the latest 1/25 build of cm10.1, the issue still persists.
How does it make any sense that changing a sip address from .com to .org should
affect which speaker the audio is played out of? That is ridiculous. In the
sipdroid settings, we should be able to control where the primary call audio
plays out of, and it shouldn't be dependent on anything else.
Original comment by nesslook...@gmail.com
on 27 Jan 2013 at 12:53
Nevermind, seems to be an issue of the most recent 4-5 d2vzw cyanogenmod 10.1
builds (oddly enough). Doing a complete wipe (system, cache, data) and flashing
the mastamoon's 20130123 build with reverts fixed the issue (as well as fixed
in-call volume control).
http://d-h.st/PN0
Original comment by nesslook...@gmail.com
on 27 Jan 2013 at 2:39
Still present on Sipdroid 3.5 beta
Android 2.2 on ZTE BLADE (BASE BAND: P729B01, kernel: 2.6.32-9-perf,
compilation no.:; ZTE4-BLADEV1.0.0B04)
Sorry but I'm going back to another voip client :S
Original comment by alejandr...@gmail.com
on 20 Jul 2014 at 1:28
Same issue, with Nexus 4 running on 5.0.1.
In my case this started all of a sudden yesterday.
(Side note: I have been playing around last weekend with a MiKey button that
goes into the headset socket).
Reboot not working. Factory reset not tried yet.
Original comment by Kelvin...@gmail.com
on 24 Feb 2015 at 7:05
Issue gone since today.
Almost certain it was resolved by uninstalling the apps KeyCut and Clicky.
Phone not rooted and no factory reset was done.
Original comment by Kelvin...@gmail.com
on 24 Feb 2015 at 6:24
Original issue reported on code.google.com by
derhoch@gmail.com
on 23 Feb 2010 at 10:33