@horacebury, not running, doesn’t mean it’s closed. by default android doesn’t close the apps. so they are running in background, even if you doesn’t see them in your background tab windows.
Android Unlike iOS, local notifications on Android are managed by the application and not by the operating system. This means that all scheduled notifications and status bar notifications will be cleared when the application process terminates. However, pressing the Back key to exit the application window will not terminate the application process — this only destroys the application window which runs your project's Lua scripts and it will receive the "applicationExit" system event just before being destroyed. Thus, the application process will continue to run in the background — this is standard Android application behavior which allows its notifications to remain available. If the application process gets fully terminated, Corona will automatically restore all pending notifications when the application restarts. This said, calling os.exit() will terminate the application process and clear all notifications. If you need to close just the application window, call native.requestExit() which only exits the application window and keeps the application process alive, thus keeping your notifications alive.
my point, is there are many apps out there that “really closes” not used apps for a long time, my htc have that by default on is OS. or other apps with memory manager that will close them. if the app is terminated, local notifications will not work if I understood right about local notifications. in that case, local notifications are useless in android for long time notifications or i’m missing some point?
