Be aware that these semantics will change slightly between applications targeting platforms starting with
HONEYCOMB vs. those targeting prior platforms. Starting with Honeycomb, an application is not in the killable state until its onStop() has returned. This impacts whenonSaveInstanceState(Bundle) may be called (it may be safely called after onPause() and allows and application to safely wait untilonStop() to save persistent state.On Tue, Jul 7, 2015 at 8:06 AM Francis Mariano <francismariano@gmail.com> wrote:
Pessoal, bom dia.
A documentação do google diz como boa prática vincular a um serviço bind()/unbind() nos métodos onCreate/onDestroy ou onStart/onStop.
Estou fazendo isso no segundo caso.
Minha dúvida é a seguinte: de acordo com a documentação o sistema pode matar uma activity quando chamado o onPause, caso precise de recurso com urgência.
Nesse caso, se o sistema matar a activity no onPause sem chamar o unbind() que está no onStop o que acontece com o service? Ele fica rodando em background ou "morre" com a activity mesmo sem chamar o unbind()?
Obrigado desde já.
--
You received this message because you are subscribed to the Google Groups "Android Brasil - Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to androidbrasil-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Android Brasil - Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to androidbrasil-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
0 comentários:
Postar um comentário