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.

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
link: Systematically, I started a new project like you said. I added all of the library resources first, then I copied over my Main activity into Main, I d

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
link: The service is part of the process. If the process is not running then the service is not running as well. You are probably looking for intent filter
link: Hi Erel, I'm having an issue, Suddenly my app stop calling a service, and when I use Callsub3(..) it returns: “… java.lang.NumberFormatException

it's not realy a Service, it's a Code Module named "Service"

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
link: this jumps out: 07/16/2024 15:32:30.254 - Atlas SOS - svc_service::Service_Start::error - android.app.: Starting FGS without a type callerApp=Process
link: : Starting FGS without a type callerApp=ProcessRecord{c706a2d 26526:com.is.vitllinkSOS/u0a343} targetSDK=34 ** Service (svc_service) Destroy ** 07/16

A service is also an activity.
link: 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
link: A service is not an activity :)

I have two questions: 1) Does "Service.AutomaticForegroundMode = Service.AUTOMATIC_FOREGROUND_ALWAYS" work EXACTLY the same as Service.StartForeground(nid, CreateNotification("Message")) in the context of keeping the service alive? 2) To give a service the best chance to staying alive, should eith
link: Do I always need the Service.StopAutomaticForeground? And is the Sub Service_Start the correct place to put it?

Please note, a service does not run on a separate thread Source: https://developer.android.com/develop/background-work/services#:~:text=Caution: A service runs in the same process as the,service slows down activity performance.

1. Service is a unique Android feature. 2. B4J doesn't support BLE. It is simple to make your app run in the background with B4J (search for jSystemTray). 3. You cannot run BLE in the background in iOS with the exception of discovering beacons.

Risolto. In MyLocation: Service.AutomaticForegroundMode = Service.AUTOMATIC_FOREGROUND_NEVER 'we are handling it ourselves "lo gestiamo da soli" perché in una routine viene inviata una notifica ogni 10 secondi, il che dovrebbe impedire al S.O. di uccidere l'app. Cambiato in: Service.Automa

Powered by ColBERT