Dear All,
Even i am still facing the same problem. I have a typical streaming
media player app. with streaming running on a different thread in the
middleware.
i go to adb shell - ps - forcefully kill the process. Which api gets
called in my application to freeup the middleware stuff?
Im using
I also met the same issue. I have an UI app with a service running at
background.
When the app is forced stop, the service could not be restarted to
correct state
without appropriate cleanup before stopping.
I understand that Android forced stop should have power to kill my app
and service
Hello,
I'm not saying that this is a bug, I just want to know if there is
any way to know from my application that it is being killed by the
application manager.
Any idea will help!
Thanks in advance.
On Oct 1, 8:37 pm, Dianne Hackborn hack...@android.com wrote:
This is what force stop does.
I'm not saying that this is a bug, I just want to know if there is
any way to know from my application that it is being killed by the
application manager.
No.
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App Developer Books: http://commonsware.com/books.html
Hello,
I was having the same issues. And i was not able to solve it the way i
wish it.
I think this is a great feature on android, but also i think it has it
faults. I think that the system MUST send to my package
ACTION_PACKAGE_RESTARTED before killing the process, or at least call
onDestroy
Please, no. There is good reason to not notify the package being
killed.
Two thoughts: 1) Maybe you guys need to ask yourselves why users are
force stopping your apps? 2) If someone uses force stop they should
already acknowledge that some information might be lost.
On Oct 2, 3:56 pm, Lucas
On Fri, Oct 2, 2009 at 12:56 PM, Lucas roll...@gmail.com wrote:
In my personal case i have a worker thread that must finish cleanly in
order to make my app re-launch in a reliable state.
If you are relying on a thread to finish cleanly for your application to
remain reliable -after- its
Hello some comments:
2) If someone uses force stop they should
already acknowledge that some information might be lost.
The user doesn't know about this, there isn't any sign or warning when
pressing that button. And also our apps doesn't know too. ;)
Whenever your app is in the background,
2009/10/2 José Prieto Garay jose.prietoga...@gmail.com
I think this is the point, normally when our application needs to be
destroyed in order to release memory, or it's in a lower priority then
onDestroy() is called.
That is not true. If the user presses home, they will leave your app, it
Hello Dianne,
Ok, I understand your point, but this Android feature is giving me a
headache. Instead of solve this issue (force stop) , lets change the
conversation angle.
I have an app (App1) that controls the excecution of another one
(App2). The problem that I have is that the app1 decides
So you want to restart your app when the user just explicitly said he
didn't want to run your app anymore?? Don't do that.
On Thu, Oct 1, 2009 at 2:13 PM, Emiliano Schiano emylya...@gmail.com wrote:
Hello Everybody,
I´m having the following issue.
The ApplicationManager is killing the process
Hello Emiliano,
I'm having the same issue, that Force Stop is destroying everything
related to my package and process: Activities, BroadcastReceivers and
Services, then callback methods aren't called, onDestroy() isn't
called for example.
It's like your package and process can't be notified
This is what force stop does. It's not a bug, it is very much a feature.
2009/10/1 José Prieto Garay jose.prietoga...@gmail.com
Hello Emiliano,
I'm having the same issue, that Force Stop is destroying everything
related to my package and process: Activities, BroadcastReceivers and
13 matches
Mail list logo
