UI Suggestions (integration settings, making calls UE)

[GoogleCodeExporter]

I'd love to see a setting on the preferred call type:
1. Prefer SIP (pick a SIP account if many are defined) when available
2. Prefer phone
3. Always ask
The current behavior will fit the "always ask" setting. 

Also I'd like to see the exception setting changed (especially if changes above 
are implemented), 
would be great if it offered a confirmations such as "the calls will be made 
using <option> unless" 
and a link to a description of what format exceptions are expected would be 
great.

Original issue reported on code.google.com by stangri%...@gtempaccount.com on 3 Jun 2010 at 4:43

• Merged into: #41

[GoogleCodeExporter]

Thanks for the suggestion.

There is already something planned for this feature.
You can read my comment here : 
http://code.google.com/p/csipsimple/issues/detail?id=41&can=1#c1
to see what is in my mind for now.
It fits your request and can also support more complicated configurations but 
can
evolves in the future.

I'll try to find something ergonomic for the user interface. I want to do 
something
powerful for users how wants to tweak anything but also something clear and 
simple
for the 80% users who just want something like you described.

So stay tuned : this feature is planned before the beta (so it's a priority). 
The next alpha release (0.00-12) will fix issues for some devices (critical 
sound
problems) and introduce call logs. But after this one, I'll start something on 
this
specific point.

Original comment by r3gis...@gmail.com on 4 Jun 2010 at 9:22

• Changed state: Accepted
• Added labels: Priority-High, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I'm one of those people with problematic phones -- Motorola Backflip. Currently 
I'm using the sipdroid 1.3.5, but 
it's an old build, it has memory leaks which force me to reboot my phone at 
least once a day and it still doesn't 
work 100% and developers couldn't care less.

I'd very much appreciate if you update CSipSimple so it would work on my phone. 
Please let me know if I can be 
of any assistance in pre-release testing.

Original comment by stangri%...@gtempaccount.com on 4 Jun 2010 at 10:34

[GoogleCodeExporter]

It would be great if you can pre-alpha test the attached release.
You have to uninstall the csipsimple version previously installed before 
installing
this one.

The native library is more robust but there is maybe still issues after the 
first call.
Let me know how it behaves and if possible send me the anr traces available in
/data/anr/traces.txt on your phone or/and the log traces available using logcat.

Many thanks in advance : it's important to me to be compatible with the most 
devices
and tests are really helpful to do so. 
That's the main reason for why I released alpha -and not yet really usable- on 
the
market.

Original comment by r3gis...@gmail.com on 5 Jun 2010 at 6:53

Attachments:

• CSipSimple.apk

[GoogleCodeExporter]

There is still crackling on spica 2.1 with the attached release but the sound 
is 
louder than previous version.

The csipsimple keyboard is smoother now!

There is a bug sometimes the ingoing interface appear even if it's a outgoing 
call!

Thanks again for your work!

Original comment by esteban4...@gmail.com on 5 Jun 2010 at 10:08

[GoogleCodeExporter]

The interface bug is present also in the 0.00-11 version on Legend

Original comment by Gianluca...@gmail.com on 5 Jun 2010 at 3:37

[GoogleCodeExporter]

I wish I had the problems of the two previous posters. :)

I've done the following:
1. Uninstalled CSipSimple
2. Rebooted phone
3. Installed the attached build and configured CSipSimple
4. Made a test sip call from CSipSimple UI

Result:
The call is made, but the phone becomes unresponsive (locks up), forcing me to 
remove the battery if the 
outgoing call is picked up. I can hang up/kill the CSipSimple process before 
the first call is picked up, but I 
get the same results with the subsequent calls.

I'm attaching logcat and traces.txt.

Original comment by stangri%...@gtempaccount.com on 5 Jun 2010 at 5:52

Attachments:

• logs.zip

[GoogleCodeExporter]

@stangri : many thanks for your test and logs.

A first thing, not related to the bug but that you should know : 
I think that "advancedtaskkillerpro" kill my app using a not clean method and 
it make
it crashes since I use some native primitives. 
So it tries indefinitely to be restarted by android. You can try to ignore 
csipsimple
in the auto-kill list if advancedtaskkillerpro allow it. 
You'll probably save battery by ignoring it : when csipsimple manage alone its 
own
process it stops itself when it is not necessary anymore (it is not yet totally 
clean
but should be the case when in a stable version).
Besides I think that my app is not alone on your phone with this problem :
.batterymanager.PowerProfileSvc 
.friendfeed/.widget.SocialWidgetProvider$WidgetService
.blur.home.message/.MessageWidgetProvider$WidgetService
.blur.contacts/.CacheService 
.blur.home.status/.StatusWidgetProvider$WidgetService 
.blur.weather/.WeatherWidgetProvider$WidgetService 
.blur.weather/.service.WeatherService
are probably also impacted.

Unfortunately I think that the problem you encounter with audio is not linked 
to this
previous note. 
It look likes things I reproduced on colleagues phones : xperia x10 and samsung
galaxy and thanks to the traces you provides me, I think that I have a little 
idea
where the problem is now. So many thanks for your test.

@Gianluca & @esteban :
I've just solved the issue with the incoming interface that appears while 
outgoing :
it was corrected once but regressed with the calllogs integration ;). 
I'll provide you a new build in this thread when i'll produce something to fix 
the
issue on the Motorola Backflip.

Original comment by r3gis...@gmail.com on 5 Jun 2010 at 9:05

[GoogleCodeExporter]

Regis -- I've had to use the ATKPro since when the call is not answered there's 
no way to exit the call window 
(hangup button doesn't seem to do anything). Along with the CSS I've killed a 
few other apps I didn't bother 
uncheck. ATKPro is not set to auto-kill anything, but I have another app which 
I use to prevent some AT&T 
crap from running and I might have used it to suspend CSS as well, as I didn't 
want to run it but wanted it 
installed so I'd get notifications when the newer version is available in the 
Market. I'll double-check/disable 
that next time I run any tests.

Please let me know when you have another build I could try. Hopefully Motorola 
designs their phones alike so 
whatever works on mine will work on all other Motorolas.

Original comment by stangri%...@gtempaccount.com on 6 Jun 2010 at 12:54

[GoogleCodeExporter]

I notice 2 others bugs (!?) :
* When we erase the calllogs in the android's interface, they still appear in 
the 
Csipsimple's interface.
* I think that the battery is more solicited than other sip software like 
sipdroid for 
example.

Original comment by esteban4...@gmail.com on 6 Jun 2010 at 8:37

[GoogleCodeExporter]

Hi guys,

Many thanks for all your tests. Another build has been done with the help of 
two colleagues with their sony X10 and their Samsung Galaxy how reproduced some 
audio issues.
I built something that solve the issue for their devices. I'm not sure it will 
fix for the backflip but worth to test.
http://code.google.com/p/csipsimple/issues/detail?id=49#c1
You can test this new build. It is not the cleanest way to handle this issue, 
but should fix things.

@esteban : Actually, the Android calllogs and the csipsimple calllogs are not 
in the same database. I can implement something that synchronize the two 
databases. Good idea.
For the battery, there is many way to tweak csipsimple right now in order to 
save battery. You can for example choose to use it only for outgoing calls, or 
also choose to don't lock wifi. 
Indeed, I didn't really optimize things for battery savings yet. Especially 
when always active. But will be done soon once every audio issues will be fixed.

Original comment by r3gis...@gmail.com on 9 Jun 2010 at 7:33

[GoogleCodeExporter]

Regis,

is there a way I can submit the logs to you directly, without exposing them to 
the world?

thanks!

Original comment by stangri%...@gtempaccount.com on 9 Jun 2010 at 8:09

[GoogleCodeExporter]

You can directly email me : r3gis.3r at gmail

You're right that's important for everybody how want to send logs.
Logs has to be reviewed. Even if there is no password written in it, my debug 
versions produces a lot of thing including sip headers and the responses to 
server challenges.
Sending it to me directly is also a good idea. Promise i'll not diffuse it ;)

Original comment by r3gis...@gmail.com on 9 Jun 2010 at 8:55

[GoogleCodeExporter]

About UI. Don't know if you're working on it but when in a connected call, the 
green call logo in the notification bar on froyo is a little too big and not 
sharp. Now I understand you use native android icons so why is this error? (Btw 
it applies to in-call and dialing interface too).

2nd point: my n1 froyo discharged itself in 20 minutes getting really hot and I 
think this happened related to csipsimple loosing network connection (maybe in 
connection with task killer?).

Thanks

Original comment by alessand...@gmail.com on 4 Aug 2010 at 11:15

[GoogleCodeExporter]

For your first point it's a wanted differentiation (in order to quickly know 
whether it is a sip call). Besides, other icons are not really native icons : 
it's icons grabbed from the official android git repository. 
The difference is that if manufacturer or rom is customized, resources from 
csipsimple will be different from those of the phone. It's the best comprise to 
get something nice and something portable without using private "APIs".

For your second point, it's possible that csipsimple fight against a auto task 
killer. I repeat and insist, autotask killer on android is a very bad idea ! 
To convice you, an article I found yesterday following the official twitter dev 
account : 
http://www.reddit.com/r/Android/comments/cwhm6/i_stopped_using_a_task_killer_las
t_week_to_see_if/
It clearly explain why task killer apps (and auto-task killer as consequence) 
drain the battery more than it save battery !!! (All the more so as using a 
nexus one which has a lot of RAM available).
Though, I would be really interested if you can get the logcat from your phone 
just before the battery draining. An error in csipsimple can't be exclude so 
worth to be checked !

Original comment by r3gis...@gmail.com on 4 Aug 2010 at 11:31

[GoogleCodeExporter]

One more thing which I stated before but probably on a wrong thread:

In call volume is set to 4 out of 5 by default. Is it possible to just use the 
standard phone in call volume? This way I wouldn't have to always adjust. Thank 
you 

Original comment by alessand...@gmail.com on 5 Aug 2010 at 3:40

[GoogleCodeExporter]

Yes was taken into account, but you're right to remind me this point, I forgot 
the interface in the preference list. (there is the pref but no way to change 
it :) )

Original comment by r3gis...@gmail.com on 5 Aug 2010 at 3:44

[GoogleCodeExporter]

Merged into issue 41. > r188 (= 0.00-12-08) provide a first way (not the final 
one, still not really user friendly) to manage exclude patterns.

Not yet fully implemented (there is not the force call using SIP feature yet) 
to match the first request.

As for the Backflip support should be tested again with latest version. Besides 
testing with codecs that doesn't need too much cpu or reducing media quality 
could be tested to determine what is supported by the device.

As for sound level at call establishement, a new option has been added in 
latest version "Initial stream level" that allow to choose the initial level of 
the android audio track (different from "Speaker amplification" which change 
the stream sent by your contact itself and not the way android render this 
stream).

If there is any sub-issue I missed and that is not open in an other issue 
please feel free to open it as a new one ! Thx.

Original comment by r3gis...@gmail.com on 8 Aug 2010 at 9:32

• Changed state: Duplicate