This question already has answers here:
How to show daily offline notifications in Android 10?
(3 answers)
Closed 2 years ago.
I literally read all threads about this subject but none of them worked. (None of them also has a accepted valid answer that everyone says yay! reading it)
What I am trying to do is to send notification to the user at specific time that user specifies. these are what I tried so far:
Alarm manager + Broadcast receiver: this work on the emulator, but not on my device (Xiaomi Redmi note 8). It actually works for short periods like 1 or 2 minutes, but doesnt work for longer periods like 10 or 15 minutes. there is a funny bug about alarms that I will explain later.
wrokmanager: again works on the emulator, but not on my device.
Alarm manager + Broadcast receiver + JobServiceIntent: this doesn't change anything. again it works fine on emulator as expected. But on my phone, it works for short periods but not when the alarm is set for 15 minutes later.
P.S: I also tried many variation, like different types of alarm (RTC, RTC_WAKEUP). or different methods to set it like setExact, setReapiting etc. did the same with workmanger.
Final Result(Important):
after days of research I reached to this thread and I was convinced that these are all forced by manufacturers and there is no way to solve it rather than asking the user to do some manual changes (like auto start, battery saver etc). However, I found an app that is not one of those whitelisted apps(like facebook, whatsapp etc), it's a local app and is sending notifications on time. First I though it is using FCM, then I turned off my internet connection and I still received notification exactly on time.
Now I can not really think of any other solutions, and couldn't find any on other threads that actually work. Any helps would be appreciated from the bottom of my heart.
this is my BROADCASTRECEIVER:
public class AlarmReceiver extends BroadcastReceiver {
#Override
public void onReceive(Context context, Intent intent) {
Log.d("NOTIF","YESSSS, IT's WORKING");
NotifJobIntentService.enqueueWork(context,intent);
}}
this is my JobIntentSerice class:
public class NotifJobIntentService extends JobIntentService {
private static final String TAG = "NotifJobIntentService";
private Context context;
static void enqueueWork(Context context, Intent intent) {
enqueueWork(context, NotifJobIntentService.class, 123 , intent);
}
#Override
public void onCreate() {
super.onCreate();
Log.d(TAG, "onCreate");
}
#Override
protected void onHandleWork(#NonNull Intent intent) {
context = getApplicationContext();
Log.d(TAG, "OnHandleWork");
String input = intent.getStringExtra("inputExtra");
intent.setFlags(intent.FLAG_INCLUDE_STOPPED_PACKAGES);
Intent intent1 = new Intent(context , MainFragment.class);
PendingIntent pIntent = PendingIntent.getActivity(context, 0, intent, 0);
// TODO: Make this accessible to exterior projects, such as web interface.
Notification.Builder builder = new Notification.Builder(context)
.setTicker("Notification")
.setContentTitle("Important Message")
.setContentText("This is an example of a push notification using a Navigation Manager")
.setSmallIcon(R.drawable.ic_add)
.setContentIntent(pIntent);
NotificationManager notificationManager = (NotificationManager) context.getSystemService(context.NOTIFICATION_SERVICE);
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O)
{
String channelId = "Your_channel_id";
NotificationChannel channel = new NotificationChannel(
channelId,
"Reminder to remind to review your notes",
NotificationManager.IMPORTANCE_HIGH);
channel.setDescription("Hello Dear friends"); //this is to test what this is
notificationManager.createNotificationChannel(channel);
builder.setChannelId(channelId);
}
Notification notification = builder.build();
notification.flags = Notification.FLAG_AUTO_CANCEL;
notificationManager.notify(0, notification);
}
#Override
public void onDestroy() {
super.onDestroy();
Log.d(TAG, "onDestroy");
}
#Override
public boolean onStopCurrentWork() {
Log.d(TAG, "onStopCurrentWork");
return false;
}
}
this is my Main activity that sets the alarm manager:
private void setNotificationAlarm(){
//Alarm Manager
Calendar time = Calendar.getInstance();
time.set(Calendar.HOUR_OF_DAY,11);//set the alarm time
time.set(Calendar.MINUTE, 30);
time.set(Calendar.SECOND,0);
AlarmManager am =( AlarmManager)getContext().getSystemService(Context.ALARM_SERVICE);
Intent i = new Intent(getActivity(), AlarmReceiver.class);
i.setAction("android.intent.action.NOTIFY");
PendingIntent pi = PendingIntent.getBroadcast(getContext(), 0, i, PendingIntent.FLAG_ONE_SHOT);
if (Build.VERSION.SDK_INT >= 23){
am.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP,time.getTimeInMillis(),pi);
}
else{
am.set(AlarmManager.RTC_WAKEUP,time.getTimeInMillis(),pi);
}
}
and here is my manifest:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="ir.zima.schema">
<application
android:name=".CustomApplication"
android:allowBackup="true"
android:icon="#mipmap/ic_launcher"
android:label="#string/app_name"
android:roundIcon="#mipmap/ic_launcher_round"
android:supportsRtl="true"
android:theme="#style/Theme.AppCompat.Light.NoActionBar">
<activity android:name=".MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name=".ListActivity"></activity>
<activity android:name=".MenuItemActivity"></activity>
<service
android:name=".NotifJobIntentService"
android:permission="android.permission.BIND_JOB_SERVICE"
android:exported="true"
android:enabled="true"/>
<receiver android:name=".AlarmReceiver" android:exported="true">
<intent-filter>
<action android:name="android.intent.action.NOTIFY">
</action>
</intent-filter>
</receiver>
</application>
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
and finally the funny bug:
There are many threads that say alarm set by alarm manager is cleared when you swipe away your app and that actually happens (i figured that with adb shell dumpsys...). However after days of research I finally found it in this thread accidently that there is something like a bug. If you run your app via android studio (clicking "run app" button) and then swipe the app away, all alarms will be cleared(adb shell dumpsys returns nothing). But if you run the same app using the launcher Icon and then swipe it away, the alarms are set and adb shell dumpsys also shows it. (which those alarms still work fine on emulator but not on my device).
Once I had made an app that gets data from server (one hour interval) then show notifications based on the data. I basically created an AlarmManager which will trigger each hour and start an IntentService which will initiate the network call and show notifications. You can see here how to start the AlarmManager. Then you can see this nice articale from Journaldev. That should work. But one thing I want to mention that, it is possible that the alarmmanger may be cleared as you mentioned. In my case I created 3 alarmanager instances, one is the main, and the other 2 was for checking that 1 was triggered or not. Worked just fine for me though it is not a good solution.
I am sharing the code. But I should tell you that it is not the most efficient and recommended way. This will only serve your needs.
For setting and canceling alarm:
private void setAlarmTask(AlarmManager alarmManager, long time, Intent intent, int request_code){
PendingIntent pendingIntent = PendingIntent.getBroadcast(this, request_code, intent, 0);
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, time, AlarmManager.INTERVAL_HOUR, pendingIntent);
}
private void cancelAlarmTask(Intent intent, int request_code){
PendingIntent pendingIntent = PendingIntent.getBroadcast(this, request_code, intent, 0);
pendingIntent.cancel();
}
For starting scheduler:
private void setScheduler(long time_in_miliseconds){
Calendar calendar = Calendar.getInstance();
calendar.setTimeInMillis(time_in_miliseconds);
AlarmManager mainAlarmManager = (AlarmManager) getSystemService(Context.ALARM_SERVICE);
AlarmManager failSafeAlarmManager = (AlarmManager) getSystemService(Context.ALARM_SERVICE);
AlarmManager failSafeAlarmManager_2 = (AlarmManager) getSystemService(Context.ALARM_SERVICE);
Intent scheduleServiceExecuterIntent = new Intent(this, ScheduledServiceExecuter.class);
scheduleServiceExecuterIntent.putExtra("state", "Main");
setAlarmTask(mainAlarmManager, time_in_miliseconds, scheduleServiceExecuterIntent, 0);
calendar.add(calendar.MINUTE, 5);
scheduleServiceExecuterIntent.putExtra("state", "Fail Safe");
setAlarmTask(failSafeAlarmManager, calendar.getTimeInMillis(), scheduleServiceExecuterIntent, 1);
calendar.add(calendar.MINUTE, 5);
scheduleServiceExecuterIntent.putExtra("state", "Fail Safe 2");
setAlarmTask(failSafeAlarmManager_2, calendar.getTimeInMillis(), scheduleServiceExecuterIntent, 2);
}
For Stopping scheduler:
private void stopScheduler(){
Intent scheduleServiceExecuterIntent = new Intent(this, ScheduledServiceExecuter.class);
cancelAlarmTask(scheduleServiceExecuterIntent,0);
cancelAlarmTask(scheduleServiceExecuterIntent,1);
cancelAlarmTask(scheduleServiceExecuterIntent,2);
}
I am trying to get "DeleteIntent" callback from my notification.
BroadcastReceiver.onReceive not called from PendengIntent, while it works OK when broadcast is launched manually with sendBroadcast(deleteIntent).
It works well when intent target is Activity (hits Activity.onNewIntent) but it is weird to use it since activity goes foreground when message dismissed.
Please, help to get onReceive call to BroadcastReceiver.
It is visible, exported and enabled, located in the same package.
MyCancelReceiver class
public class MyCancelReceiver extends BroadcastReceiver {
#Override
public void onReceive(Context context, Intent intent) {
}
}
Android manifest
<activity android:name=".MainActivity" android:launchMode="singleTask">
<MyCancelReceiver" android:enabled="true" android:exported="true">
<intent-filter>
<action android:name="notification_cancelled"/>
</intent-filter>
</receiver>
MainActivity
private MyCancelReceiver mReceiver;
#Override
public void onStart() {
super.onStart();
IntentFilter filter = new IntentFilter();
filter.addAction("notification_cancelled");
mReceiver = new MyCancelReceiver();
registerReceiver(mReceiver, filter);
}
#Override
public void onStop() {
super.onStop();
unregisterReceiver(mReceiver);
}
Notification creation:
Intent cancelIntent = new Intent(getApplicationContext(), MyCancelReceiver.class);
cancelIntent.setAction("notification_cancelled");
cancelIntent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
PendingIntent deleteIntent = PendingIntent.getActivity(getApplicationContext(), 0, cancelIntent, PendingIntent.FLAG_CANCEL_CURRENT);
Notification not = new Notification.Builder(getApplicationContext(), Util.ANDROID_CHANNEL_ID)
.setContentTitle(messageTitle)
.setContentText(messageBody)
.setSmallIcon(R.drawable.default)
.setAutoCancel(true)
.setDeleteIntent(deleteIntent)
.setContentIntent(contentIntent)
.build();
NotificationManager notificationManager = (NotificationManager) this.getSystemService(Context.NOTIFICATION_SERVICE);
notificationManager.notify(0, not);
Thank you in advance.
It's because when you start your activity, onStart() gets called and you will get a callback in onReceive() as soon as the activity is launched. But when you click your notification onStart won't be called as the activity is already created, In this case, onStart wont be called. Try registering in onResume(), I am pretty sure it will work.
Problem solved using an answer from this thread Click on android notification icon does not trigger broadcast receiver
Explicit intent replaced with implicit one.
Intent cancelIntent = new Intent("notification_canceled");
Alarm Manager broadcast is not received in some devices when app is not in memory ( swiped off from app-tray ) . Device in which it is not working runs with API 25 and is ONE PLUS 3 device. however same thing works in Nexus 6 (with API 25).
Strange thing is , I can see in system logs that Alarm is being triggered. I can see log below when alarm is supposed to go off. Just that broadCast is not received. again, this happens only when app is not in memory. Broadcast is received properly when app is in memory.
V/AlarmManager: Triggering alarm #0: 0 when =1508843147121 package=net.IntAppoperation =*walarm*:com.intapp.receivers.NOTIFICATION_ALARM
Here is how I'm setting alarm
In Manifest :
<receiver android:name="com.intapp.receivers.ReminderReceiver"
android:exported="false"
android:enabled="true">
<intent-filter>
<action android:name="com.intapp.receivers.NOTIFICATION_ALARM" />
</intent-filter>
</receiver>
And then When I want to set alarm :
public static final String ACTION = "com.intapp.receivers.NOTIFICATION_ALARM";
AlarmManager alarmManager = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);
Intent intent = new Intent(context, ReminderReceiver.class);
intent.setAction(ACTION);
int randomNum = new Random().nextInt(Integer.MAX_VALUE - 1 + 1);
PendingIntent alarmIntent = PendingIntent.getBroadcast(context, randomNum, intent, PendingIntent.FLAG_ONE_SHOT);
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), alarmIntent); // I get time from calendar instance in my function
} else {
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
alarmManager.setExact(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), alarmIntent);
} else {
alarmManager.set(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), alarmIntent);
}
}
Here's my implementation of Receiver :
public class ReminderReceiver extends BroadcastReceiver {
#Override
public void onReceive(Context context, Intent intent) {
Log.d(TAG, "Receiver called ");
// my implementation
}
}
EDIT:
Seems like problem is a little bigger. I have also registered for CALL_STATE by which I can listen to incoming/outgoing calls. That broadcast receiver is also not firing when app is not in memory. Plus, This happens on Samsung device too running on API 25. Is this (Manifest broadcast not working) known problem for API 25 on some devices?
I have an OnePlus 3 as well... And yes, this happens a lot to me as well. Even when I register for a BootReceiver. I fixed my problem by uninstalling and reinstalling my application.
I would suggest to implement a WakeLock in your Application, to prevent the device from killing your app, so the BroadcastReceiver remains active.
Let's hope OnePlus will do it better in the future.
I'm trying to make an Alarm using the Alarm Manager. The app runs without any error messages, but nothing happens.
I tried solutions from developer.android.com and suggestions from stackoverflow.
I also tried copying a complete tutorial i found, but nothing worked.
The app runs on API22 and was tested on an emulator(API23) and a real device(API22).
This is my Code:
MainActivity.java startAlarm():
AlarmManager manager = (AlarmManager)getSystemService(Context.ALARM_SERVICE);
Intent myIntent = new Intent(MainActivity.this,AlarmReceiver.class);
PendingIntent pendingIntent = PendingIntent.getBroadcast(this,0,myIntent,0);
manager.set(AlarmManager.RTC_WAKEUP, SystemClock.elapsedRealtime()+3000,pendingIntent);
AlarmReceiver.java:
public class AlarmReceiver extends BroadcastReceiver {
public void onReceive(Context context, Intent intent) {
Toast.makeText(context,"THIS IS MY ALARM",Toast.LENGTH_LONG).show();
}
}
AndroidManifest.xml, between <manifest...> and </manifest>:
<receiver android:process=":remote" android:name=".AlarmReceiver"></receiver>
your reciever name is AlarmToastReceiver not AlarmReceiver
try:
<receiver android:process=":remote" android:name=".AlarmToastReceiver "></receiver>
I am using a BroadcastReceiver to enable a button when it is triggered. I have an AlarmManager that runs for a certain amount of time. When the time has elapsed, it sends a broadcast like this:
Intent i = new Intent("polarCap1Status");
i.putExtra("polarCap1Stat", true);
LocalBroadcastManager.getInstance(context).sendBroadcast(i);
I use this code to receive the broadcast:
//broadcast receiver to allow button to be clicked again
mMessageReceiver1 = new BroadcastReceiver()
{
#Override
public void onReceive(Context context, Intent intent)
{
clickOnOff1 = intent.getBooleanExtra("polarCap1Stat", false);
polarCap1.setEnabled(clickOnOff1);
updateScores();
resources.edit().putBoolean("pc1Set", false).commit();
}//end onReceive function
};
LocalBroadcastManager.getInstance(getApplicationContext()).registerReceiver(mMessageReceiver1, new IntentFilter("polarCap1Status"));
I have the receiver setup in my manifest like so:
<receiver android:name="com.twentytwentythree.sab.SetupTimerPC1" >
<intent-filter>
<action android:name="polarCap1Status" />
</intent-filter>
</receiver>
SetupTimerPC1 is the name of the class that is sending the broadcast. It is sending it to another class called runGraphics.
Please let me know if you need any more information.
Edit:
I added an intent-filter to the receiver in the manifest but it has not changed anything.