Closed GoogleCodeExporter closed 9 years ago
Thanks for the report.
I've a little idea (but only for the 0.00-09).
Is the phone blocked after a fix number of seconds (on the call screen there is
a
chronometer).
If my guess is right, it should freeze always when the ringtone should have
ended.
If you change your phone setting to disable ringing (use only vibrator).
If deactivating ringtone solves the problem for you, let me know i'll push an
update
tonight for this issue (that i think i've fixed it but i'm not sure that it was
due
to the ringtone).
Original comment by r3gis...@gmail.com
on 13 May 2010 at 5:53
Original comment by r3gis...@gmail.com
on 13 May 2010 at 5:53
By desactiving ringtone, the phone is no more blocked and can stop the
application
without removing battery!
But there is still a problem, i can't use the call screen : it happend nothing
by
touching the screen in order to end the call or enable speaker...
Another thing, the first call test don't work, i must restart Csipsimple and
then
it's work.
Thanks for your job!
Original comment by esteban4...@gmail.com
on 13 May 2010 at 6:24
Ok, seems to not really be linked to the ringtone in fact.
That's really strange. I can reproduce a freeze sometimes... (what's strange is
that
only on my HTC magic on android 1.5) (It works fine on Nexus One, and Archos
5IT).
Original comment by r3gis...@gmail.com
on 13 May 2010 at 7:00
I tried a second time and the phone blocked again even if the ring-tone was
off...
I never succeed to call somebody without freeze but the bugs are not always the
same.
Nevertheless the sound is better than other sip applications and the
configuration is
very easy and fast!
I hope you'll find the solution!
Original comment by esteban4...@gmail.com
on 14 May 2010 at 4:27
Yes the bug is really difficult to debug (since appears only sometimes).
It seems to be the garbage collector that goes into an infinite loop (or
something
like that).
After many tests on my htc magic, i noticed that for incoming calls the freeze
appears if you take the call within the first 5 seconds. If I wait at least for
5 or
7 seconds, the user interface doesn't freeze after that.
But I think this value depends on the overall used memory on the phone. (I
think, but
not really sure, that garbage collector try to deallocate things that it
shouldn't
manage and retry since it doesn't succeed.)
So for now, i'm testing another method for audio processing.
It will probably impact performances but at least it will not freeze (I
hope....).
I'll also try to unlink user interface management from the sip stack (it already
seems to improve a little bit things (less freeze), but not for all cases).
Original comment by r3gis...@gmail.com
on 14 May 2010 at 7:07
Calling using gsm codec and smslisto.com via hsdpa, sometimes freeze the screen
and i
can continue the conversation. I try only outgoing call.
Need to kill the app to exit.
HTC Legend with standard rom and csipsimple 09
I like the app very much.
I hope it will be possible in future versions, have a list of recent calls made
using
sip-address and will not need to specify a domain when the call is in the same
domain
Thanks
Original comment by Gianluca...@gmail.com
on 21 May 2010 at 2:08
Many thanks for your comment it confirms that it's not linked to the android
version
but probably to the CPU/RAM available when the call is taken.
The issue is really hard to debug it seems to freeze into the JVM or something
like
that :/. For now I have no solution and it afraid me a little bit...
It's an absolute priority for me and the dev of the app is frozen while I'll not
solve this issue.
For future version call logs are planned don't worry ;). (I hope also to the
android
Phone application logs if possible).
Besides you should already be able when you make a call using another android
application (for example the Phone application) to choose SIP if you want (and
it
will auto-complete the phone number with the account domain name).
Original comment by r3gis...@gmail.com
on 21 May 2010 at 3:21
Yet another try, but this time I've totally reimplemented the audio driver. I
now use
the "official" way (using JNI to pass my audio frames).
I have no freezes with this version on my HTC Magic on android 1.5 (so I hope it
solve things this time... and that if I test again in 5 minutes it will not
freeze
again...). But since the audio driver has been totally rewritten, i'm more
confident.
Perfs will be a little bit affected (but the audio comfort is still really good
- i
didn't notice the difference) (it only affects benchmarks I think).
Let me know if this new version :
* solve the freeze issue
* doesn't affect too much audio perfs
Thanks in advance !
Original comment by r3gis...@gmail.com
on 23 May 2010 at 2:11
Attachments:
On my Htc Legend on Android 2.1 I have no more freeze.
I didn't notice difference in audio quality using UMTS connection.
Thanks
On my Legend I can't use native dialer to call a sip address like
sip:account@sip.provider.com.
And even with CSipSimple text interface, I do not know where I mistake
Original comment by Gianluca...@gmail.com
on 24 May 2010 at 1:54
Thanks for the confirmation on your HTC Legend !
Great news :D
I think that i'll push the update really soon.
Ok for text dialer, you're right, there is a regression in the debug apk i
provided
in my comment. I'll fix it for the update.
Original comment by r3gis...@gmail.com
on 24 May 2010 at 2:17
Tried the market version on Acer Liquid (2.1 eclair), freeze during the call...
had
to hard reset the device.
With the posted-here version, I can confirm that is working properly, no
freezes at
all and at this time is surely the only that is working well on Liquid :)
Audio quality seems to be ok
This app is really on the right way
Original comment by eum...@gmail.com
on 24 May 2010 at 7:58
No more freeze on my Spica with the 0.00.11 version :D
Original comment by esteban4...@gmail.com
on 26 May 2010 at 12:01
Great thanks to all for your tests.
For the record, new version is now on the market 0.00-11.
Issue closed.
Original comment by r3gis...@gmail.com
on 28 May 2010 at 7:49
Original issue reported on code.google.com by
esteban4...@gmail.com
on 13 May 2010 at 5:26