Closed GoogleCodeExporter closed 9 years ago
Go on Settings > Easy configuration > And choose "Only for outgoing"
With this configuration, csipsimple will *not* automatically re-register when
wifi goes up again.
Note that choosing this option, you'll not receive sip calls unless the
register icon is in the notification bar (you go in the app and don't quit
using the quit button).
But that is the aim of this setting. (You can also be more precise in Setting >
Network and choose if you want csipsimple to run for incomings calls on wifi
only and not in 3G for example).
For now csipsimple is still in alpha phase but in future release the easy
configuration will be prompted at first run allowing you to choose want you
want directly.
-- Another really really important thing --
DO *NOT* trust task killer app!!!
What you think is that when csipsimple appear in the task list, it drain the
battery (even if there is no account set). That's wrong.
And that is not said by me, relayed by android core developpers :
http://blog.radioactiveyak.com/2010/05/when-to-include-exit-button-in-android.ht
ml
It explains why thinking a task killer is a good thing can drain the battery.
When csipsimple appear in the list and is not registered to anything, it
consume absolutely nothing. (I don't say that there is no problems when you are
registered and that battery consumption could not be optimized on csipsimple...
but certainly not making it disappearing from the task list !)
Let me know if setting properly the app in "Only outgoing mode" solve the
problem for you (quit using the quit button as you did, which aim to unregister
everything. The label is not really good, but, more clear for users).
Original comment by r3gis...@gmail.com
on 17 Aug 2010 at 3:27
This seems to work, thanks for clearing this up. The user interface isn't quite
intuitive yet, but the functionality seems to make sense.
Wrt the task killer, I used the background services and running applications
info from the android application settings. I'll investigate if the higher
power drain with csipsimple listed there, but accounts disabled is reproducible
or was just a mistake in my ad-hoc testing. I've seen it two out of two times I
tried, but that is not a high number samples.
Original comment by stefando...@gmail.com
on 19 Aug 2010 at 3:22
Regarding task killer or the application settings (or a linux ps command) it is
the same. All will provide you the same information (with more or less
details).
The important thing is that even if an app is cleanly destroyed and not running
it can remain in the process list. The reason is explained here :
http://blog.radioactiveyak.com/2010/05/when-to-include-exit-button-in-android.ht
ml : Android système manage things as it want and will free memory when it
will be necessary. Since the app doesn't consume any cpu it's not important
that it is kept frozen in a memory slot.
For the UI, you are right, it's not enough intuitive yet. In the future the
Easy setting panel will be prompted at the first run. And the quit button will
not be available when configured for incoming calls on the current network (and
if incoming call is available for another network, when quit is pressed a
toaster will notify user that csipsimple will automatically restart when
network will be favorable).
Original comment by r3gis...@gmail.com
on 19 Aug 2010 at 5:30
Original issue reported on code.google.com by
stefando...@gmail.com
on 17 Aug 2010 at 3:00