krunal09 / sample

Automatically exported from code.google.com/p/csipsimple
0 stars 0 forks source link

Speakerphone is stuck on #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The program froze after answering a call.  I could still hear the caller
and they could still here me.  The time of call was stuck at 4 seconds and
none of the on screen buttons would work.  I was trying to hit speaker to
turn it on to test that out and nothing happened.  I had to close the
program using advanced task killer.  Since then, the speakerphone won't
turn off.  I can tap the button and the color changes like that it's either
activated or not, but it stays the same being on. Tried restarting phone
and also reinstalling but it is still stuck on inside the program.

What is the expected output? What do you see instead?
Expect to be able to turn speaker on and off.

What version of the product are you using? On what operating system?
0.00-08 and Android 1.5 on Sprint Hero.

Please provide any additional information below.
The program itself seems to work great minus a few freezes every now and
again, however, with the speakerphone stuck on it's unusable right now.

Original issue reported on code.google.com by jerod.mi...@gmail.com on 10 May 2010 at 1:30

GoogleCodeExporter commented 9 years ago
Many thanks for the report.

I've to investigate this problem. 
I know that there is a lot of issues with android 1.5 (there where many bugs in
android with native audio channels - they corrected this bug in android 1.6 but 
I
absolutely want to support android 1.5 since it's about 1/3 of the android 
devices -
so I have to get rid of this "Android" bugs in my app :( ).
I'll try to downgrade my HTC G2 to android 1.5 to be able to test under cupcake.
By the way, it has to be fixed before the beta phase (I'm still in alpha phase, 
and
android 1.5 starts to be critical to go to the beta phase)

If you are interested by alpha testing versions for android 1.5 let me know, 
i'll
provide on this issue my intermediates builds.

Original comment by r3gis...@gmail.com on 10 May 2010 at 5:51

GoogleCodeExporter commented 9 years ago

Original comment by r3gis...@gmail.com on 10 May 2010 at 5:51

GoogleCodeExporter commented 9 years ago
Yeah I'd love to Alpha test for you.  Just let me know what you need me to do.

Original comment by jerod.mi...@gmail.com on 10 May 2010 at 1:43

GoogleCodeExporter commented 9 years ago
I've just pushed an update on the market. 
I've now successfully downgraded my HTC G2 to android 1.5 and I was even able to
reproduce crashes after the establishment of the call (without even succeeding 
to try
to activate the speaker).

In fact android 1.5 was even worst that I though (it has been improved a lot in
android 1.6). So I directly push my new version on the market (there is also
important fixes that doesn't depends on the android version).

So now, on android 1.5 you should be able to establish the call. (You must 
disable
Echo cancellation in Params).
The mute and speaker option has absolutely no effect (I don't really know why, 
but
since I have a device with 1.5 on it, it 'll be easier to fix right now).
Besides, the other big bug with android 1.5 (that I already well know) is the 
fact
that at the end of the call, sometimes it could crash the app (then the android 
task
system will restart it automatically but that's not really clean).

Original comment by r3gis...@gmail.com on 10 May 2010 at 8:58

GoogleCodeExporter commented 9 years ago
I upgraded and disabled echo cancellation and I still get exactly the same 
thing,  
speaker is on when the call is connected.  

Original comment by jerod.mi...@gmail.com on 10 May 2010 at 9:10

GoogleCodeExporter commented 9 years ago
Yes, you're right :
My update only fix that it crashes/freeze after the call establishment. (It was
linked to the speaker issue, but doesn't solve it yet - just make the app more 
stable
for android 1.5).
So globally this issue isn't yet fixed (and is now marked Started :) ), but now 
it
should not freeze the app anymore.

I'll probably send you a apk file to install soon for the speaker specific 
issue and
also the mute issue since it doesn't work too.
(I've to remove the bluetooth option too since it's not yet implemented too)

If you can just confirm me the 0.00-09 doesn't freeze the interface anymore 
(while in
communication) and the End Call button should well terminate the call (even if 
it
maybe crashes after the call is well ended).

Original comment by r3gis...@gmail.com on 10 May 2010 at 10:01

GoogleCodeExporter commented 9 years ago
Actually the program freezes almost every single call now at either 4 or 5 
seconds. 
The call continues to work, just the screen freezes.

Original comment by jerod.mi...@gmail.com on 10 May 2010 at 10:43

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I though it was solved, but actually I just retested after some idle time, and 
it
still freeze. :(

Original comment by r3gis...@gmail.com on 13 May 2010 at 4:47

GoogleCodeExporter commented 9 years ago
I add a test build.

There is sometimes freezes but seems to be occurs only sometimes.
I've to understand why it still freeze since i don't use android callbacks 
anymore.

To install this apk, you must uninstall any previously installed version.

Original comment by r3gis...@gmail.com on 13 May 2010 at 4:59

Attachments:

GoogleCodeExporter commented 9 years ago
The crash seems to be due to the ringer.
If you wait for the ringer to stop and then take the call, it will not freeze.
If you don't wait it freeze when the ringer should have finished.
Can you confirm me that if you wait for the ringtone to stop it's ok?

(or if you deactivate the ringer - that's the reason why i firstly though that 
it was
solved i think...)

Original comment by r3gis...@gmail.com on 13 May 2010 at 5:25

GoogleCodeExporter commented 9 years ago
Yet another build that will make a cleaner ring stop (not based on the android 
source
code :) )

Original comment by r3gis...@gmail.com on 13 May 2010 at 5:40

Attachments:

GoogleCodeExporter commented 9 years ago
You're right it seems to only crash during the ringer.  It now seems to close 
itself 
automatically, however.  It doesn't show up in the notifications bar all the 
time like 
it used to.  Also, when I have the application closed, sometimes it will open 
itself 
backup and it is a battery drainer.  I can't get but about half a day with the 
app 
running.

Original comment by jerod.mi...@gmail.com on 13 May 2010 at 5:40

GoogleCodeExporter commented 9 years ago
The latest one you just posted won't even allow me to answer a call.  It 
freezes when i 
try to answer and I had to take the battery out of the phone in order to get 
back to 
the home screen.

Original comment by jerod.mi...@gmail.com on 13 May 2010 at 5:56

GoogleCodeExporter commented 9 years ago
A new update attached in my last comment here :
http://code.google.com/p/csipsimple/issues/detail?id=34#c9
should fix this issue. Can you confirm?

Original comment by r3gis...@gmail.com on 23 May 2010 at 6:12

GoogleCodeExporter commented 9 years ago
For the record, fixed in release 0.00-11

Original comment by r3gis...@gmail.com on 28 May 2010 at 7:50

GoogleCodeExporter commented 9 years ago
Old thread but issue appearing on my phone with version 0.02-03 (latest on 
market)

Android 2.1 (Last TCT Mod) on Huawei U8100-9

An earlier version of csipsimple viz 0.00-12-19 linked below works for me.
http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-19.
apk

Original comment by mattbb...@gmail.com on 28 Jul 2011 at 2:37

GoogleCodeExporter commented 9 years ago
@matt : can you try to play with audio routing hacks (see 
http://code.google.com/p/csipsimple/wiki/FAQ?wl=en#Audio_routing_troubleshooting
 ) .
(Specially the "Use mode audio api" option).
Let me know how it goes, if something helps I can modify default setting for 
this particular device. 
I think that in 0.00-12-19 using api mode was default for all devices while 
it's now deprecated in more recent versions (but the setting is still there ;) 
).

Original comment by r3gis...@gmail.com on 30 Jul 2011 at 8:02