Search Results

From developers.android.com: Services overview A Service is an application component that can perform long-running operations in the background. It does not provide a user interface.

This is an old tutorial. Most of the information here is no longer correct. 255402345 Basic4android v1.2 adds support for Service modules. Service modules play an important role in the application and process life cycle. Start with this tutorial if you haven't read it before: Android Process and

This will not work. The minimum interval is 15 or 30 minutes. If you want to do something every 30 seconds then you should use a foreground service.
link: Hello all, i've been noticing this problem for a very long time, i have read all the threads that talk about Services, I stopped working on an app alm
link: Read this https://www.b4x.-foreground-mode.90546/

When I start the app, the service starts and I can clearly see the message appearing every 10 seconds, even when the app itself is not active (when I'm at the homescreen for instance). However, as soon as I kill the app in Android, the service doesn't run anymore. I was expecting the service to cont
link: StartServiceAt interval should be 15 minutes or more. For shorter intervals you need to keep the service running as a foreground service. Background l
link: As long as my app is not killed (swiped away), the notification is shown every 10 seconds, so StartServiceAt seems to be working fine with shorter val

Services are neither processes nor threads. The services code runs on the main thread.
link: if i start 2 different services from an app, will they spawn 2 different processes or are they just 2 threads? in other words: 2 different service mod
link: so, no parallel processing is possible between 2 services

Ok, was able to get your error message. Real simple solution: Don't name any Service/Activity/Code Module Service. Service is an Object of the Core library. If you name a Service module Service, you are "overriding" the Service object. If that makes sense. Just try it. Recreate your project and do n

It really depends on your requirements. There is no right or wrong here. One of the main advantages of using services is that you are not tied to the activities life cycle. Nothing bad happens if the service keeps running in the background for a few minutes.
link: No. You let the OS take care of it. It is actually not problematic at all on Android 8+. Services are stopped after one minute. On the other hand if

Hi Use StartServiceAt for run service in every 5 minute Also use Service.AutomaticForegroundMode = Service.AUTOMATIC_FOREGROUND_ALWAYS Use this code in end of service that you get location there And after finish service's job,use Service.StopAutomaticForeground
link: Sorry for any grammatical mistake, I'm not native to the language. Any help is appreciated.

This should be the behavior but a service is a running activity and if you kill it the public variables of it wont be accessable any more and you have lot of apps that sell you stories by saying they will make your phone faster and what they do is they kill all background activities. So if the start

The service svc_service is a long running background service that manages other services and functions of the application. I already use the FGS methods as you can see in the manifest file I already posted. svc_service handles the foregound notifcation, it does funtionality does not appear in the sp

Powered by ColBERT