JobIntentService

My application determines the speed limit by the user's location and tells the user if he has exceeded it. Starting with Android API level 30 and higher, Google has defined IntentService as deprecated and suggests using WorkManager or JobIntentService and also states that it is necessary to migrate from Firebase JobDispatcher to WorkManager. I see two ways to solve this problem:

1. Start OneTimeWorkRequest and specify to restart this method periodically in this method while the application is running in the background.
2. Run PeriodicWorkRequest with a minimum allowed interval of 15 minutes. In this method, run the JobIntentService method, which runs for up to about 10 minutes, but the method may not run or may be destroyed by the system before it is complete.

I'm worried about:

• potential memory leaks;
• potential problems with WorkManager or JobIntentService when going from foreground to background and vice versa
• the ability to use the MVVM pattern

I have home screen widget, which has a simple AppWidgetProvider and JobIntentService, where I do all the work.

Problem is - it works kind of randomly. Sometimes it does, sometimes it doesnt - weirdest thing is, I can see in the log, that on each widget update enqueueWork method of JobIntentService is ALWAYS called, but onHandleWork method only sometimes.

(I have found there is strong, though not 100% correlancy with battery optimization. If I turn of "Manage apps automatically", then it 99% works reliably. If it is turned on, its like flipping a coin. Sometimes it does, sometimes it doesnt. Best to ilustrate behavior would be this short simple video

This is my code (Widget provider):

I want to get a List from my Room-Database for a notification, where I use a BroadcastReceiver and a JobIntentService.

Because I don't have a context I can't obtain the ViewModel. So I need another way to get the data.

In this article I read something about a Singleton. But I don't know how to get the data now from the database with the Singleton.

Following FetchAddressIntentService implementation with IntentService (in kotlin):

I have a JobIntentService which is supposed to do an API call and do a broadcast once the result is available.

I am using a Coroutine to do the network call using Retrofit. However, if I do sendBroadcast within the CoroutineScope , it does not trigger the BroadcastReceiver

This is my service code -

MyService.kt

I use Firebase high priority push notifications to trigger Panic alarms in Android devices. For first few tries of push, immediately push notifications arrives and it works great. But when i keep triggering push notifications after certain amount of time slowly delay keeps increasing.

I want it to trigger immediately as it is Panic situation.

I also followed the documentation which read:

High priority: FCM attempts to deliver high priority messages immediately, allowing the FCM service to wake a sleeping device when necessary and to run some limited processing (including very limited network access). High priority messages generally should result in user interaction with your app or its notifications. If FCM detects a pattern in which they don't, your messages may be de-prioritized. Android P introduced app standby buckets which limit the number of FCM high priority messages you can send to your app that don't result in the user using your app or viewing a notification. If, in response to a high priority message, a notification is displayed in a way that is visible to the user, then your app standby bucket quota will not be consumed by that message.

Because a small portion of the Android mobile population are on high latency networks, avoid opening a connection to your servers before displaying a notification. Calling back to the server before the end of the allowed processing time may be risky for users on high latency networks. Instead, include the notification content in the FCM message and display it immediately. If you need to sync for additional in-app content on Android, you can schedule an FJD job or a JobIntentService to handle that in the background.

How can I make sure high priority messages are triggered as soon as possible? May be within a minute in all cases.

I've custom JobIntentService witn static method enqueueWork.

I'm working on an android app for tracking daily app usage. The idea is that a user can set daily time limit for any app and a notification will appear within at most 2 minutes after the limit is exceeded. (The reason for delay: I've created an alarm system using AlarmManager class that will go off every minute to run a JobIntentService which will check whether limit for any app is exceeded)

I've used queryEvents method of UsageStatsManager class to count app usage time.

Here's my code for counting app usage time (I've followed How to use queryEvents):

What have I done so far...

I am using Tasks.await blocking mechanism for firebase calls in worker threads for avoiding callbacks.

I am using a worker thread (JobIntentService) for some initialization progress. JobIntentService starts when app opens and runs only once. below is my worker thread code