AlarmManager firing in emulator but not on physical device?

And in the Manifiest I have the obligatory entry android:process=":remote is anti-obligatory. Please remove it. Quickly On an actual device if I start MyApplication, add an alarm and then kill the process using a task killer Task killers remove the app's alarms as well, though this issue is resolved with Android 2.2.

And in the Manifiest I have the obligatory entry android:process=":remote" is anti-obligatory. Please remove it. Quickly.

On an actual device if I start MyApplication, add an alarm and then kill the process using a task killer Task killers remove the app's alarms as well, though this issue is resolved with Android 2.2.

I've seen this :remote here-there. What is used for and when do we need? – Pentium10 Jun 27 '10 at 19:19 thanks for the answer Mark – user312443 Jun 27 '10 at 19:20 @Pentium10: It forces the component (in this case, a BroadcastReceiver) to run in a separate process from other components.

Considering how tight most Android devices are on RAM, I know of no good reason why an SDK application should be using it. – CommonsWare Jun 27 '10 at 20:07.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.