Guest John Bieling Posted April 6, 2011 Report Posted April 6, 2011 (edited) Hi, the issue I refer to is not only restricted to sipdroid, almost any other voip app sends the sound which should go to the earpeace to the speaker of my ZTE Blade (Gen1, orange). Not good if you wish to talk in private :-) The error is due to a false behaviour of the API call "setSpeakerphoneOn" and "setMode" (this is over my head already). Someone patched my voip app, so it works again, but the real error is in the system, not the app. So my question, do you know the issue I am talking about and has it been resolved in one of the customs ROMs? Thanks John Edited April 6, 2011 by John Bieling
Guest kgian Posted April 6, 2011 Report Posted April 6, 2011 Hi, the issue I refer to is not only restricted to sipdroid, almost any other voip app sends the sound which should go to the earpeace to the speaker of my ZTE Blade (Gen1, orange). Not good if you wish to talk in private :-) The error is due to a false behaviour of the API call "setSpeakerphoneOn" and "setMode" (this is over my head already). Someone patched my voip app, so it works again, but the real error is in the system, not the app. So my question, do you know the issue I am talking about and has it been resolved in one of the customs ROMs? Thanks John I just tried csipsimple with voipdiscount account. With SS RLS 4b sound is going through the internal speaker. With JJ RLS 8 which was my previous rom it was coming out of the speakerphone. I guess same goes for sipdroid too...
Guest rickyxt Posted April 6, 2011 Report Posted April 6, 2011 I had this issue as well with the latest version of sipdroid from the market. I've just tried an earlier version of sipdroid (1.3.7) and this seems to work fine on the blade (output not routed to external speaker).
Guest redandr Posted April 7, 2011 Report Posted April 7, 2011 User night builds of csipsimple, this issue is corrected there.
Guest Maz2011 Posted April 8, 2011 Report Posted April 8, 2011 Csipsimple never connects on my Blade, no matter which SIP provider or build I use. It just times out. Sipdroid does connect perfectly using the same settings, but it has the rear speaker problem. Fring connects fine and the speaker works properly also, so that's the software I use and I have configured it for my Sipgate account. This is with Cyanogen RC4 I would like to find just one normal SIP dialler that actually works properly on the Blade, and supports multiple accounts. I thought that Android 2.3 was supposed to have native SIP support anyway. Does anyone know how that works?
Guest Maz2011 Posted April 15, 2011 Report Posted April 15, 2011 To answer my own question: the built-in SIP support in 2.3 (I'm using CM7 RC4) can be found under settings: call settings: accounts. It works very well (and connects to my SIP servers which Csipsimple still wont do) but sadly the built-in SIP service also directs all sound to the rear speaker.
Guest ZakMcRofl Posted April 15, 2011 Report Posted April 15, 2011 To answer my own question: the built-in SIP support in 2.3 (I'm using CM7 RC4) can be found under settings: call settings: accounts. It works very well (and connects to my SIP servers which Csipsimple still wont do) but sadly the built-in SIP service also directs all sound to the rear speaker. The "audio through rear speaker" problem is fixed in GIT now, thanks to Tom Giordano http://review.cyanogenmod.com/#change,4660 Looking forward to doing some SIP testing...
Guest Maz2011 Posted April 15, 2011 Report Posted April 15, 2011 Yes, I saw that update also. I'm still using RC4 as I have too many problems with more recent "stable" versions, so I will have to wait until the nightly versions fix some of those problems before I can try the SIP out.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now