Search Results

1. StartServiceAt(Me, NextTimeInstance(21, 50) ,True) Is a code to start A SERVICE! You CAN NOT start an activity as a Service. FORGET about Activities: Switch to B4XPages. And use a SERVICE to start with StartServiceAt

Just do a search in this forum - this was the first entry: StartServiceAt (Service As Object, Time As Long, DuringSleep As Boolean)Schedules the given service to start at the given time. Service - The service module. Pass Me when calling from a service module that schedules itself. Time - The time
link: And remember, the StartServiceAt API will run your app's service in the background (at the set time) even of the employee doesn't manually start your
link: Can you show me some examples how to use StartServiceAt ? Thanks
link: Thanks Do I need to call StartServiceAt on main activity create?

Use: StartServiceAt(YourServiceName, DateTime.Now, True) This will start your service straight away. The service will get killed but will automataclly start again. Don't forget to add: #Region Service Attributes #StartAtBoot: True #StartCommandReturnValue: android.app.Service.START_STIC
link: No. startserviceat is a ONE-TIME-Shedule... If you set the time to 1 minute in future then the service will be killed and restarted at the given time.
link: Thanks for the opinons im using this StartServiceAt("", DateTime.Now + 1 * DateTime.TicksPerMinute, True) so the service will do a scheduled task
link: Sorry DonManfred if it is not clear with me, does it mean I will call to start the service every interval using StartServiceAt ? in other words( the

StartServiceAt(AlarmService, Alarm, True)
link: 1. You should use B4XDialog with B4XDateTemplate. 2. Why is Alarm set to be string? It should be Long 3. All of these calculations are not needed. Yo

Upload a small project where it is not working. I don´t see a reason why it should not work at all. Only keep in mind that you´ll not able to restart your app every 5 minutes.... The time between should be 30 minutes+ Also note that you should NOT use the starter service for this. Use another servic
link: Attached is zip. App runs and rings alarm in 10 seconds and displays button. Press the button and alarm rings 10 seconds later. However if app is c
link: How do I have my app's StartServiceAt still work (ie: start a service at a set time) even when user has closed the app. I have an alarm clock (not mi

You can use StartServiceAt to schedule a service to start at a specific time.

Yes. Note that swiping the app from the recent apps list doesn't put the app in the STOPPED state (on most devices). This is different then closing it from the settings. An app in the STOPPED state cannot be started without the user explicitly starting it.
link: As per Erel Old thread and i am assuming it still stands as what it says?
link: I am trying to understand the StartServiceAt behavior. I call StartServiceAt in Service Start at 30 minutes (testing at 1 minute) and when i Force Cl

I made a project with B4A_3.82 + JDK_1.7 + API_19 about many years ago. It runs normally in Android 4.4 devices. But it runs abnormally in Android 5.0 or above devices. StartServiceAt("", DateTime.Now + 1000, True) It runs every 1000 ms in Android 4.4 devices , but it runs every 5000 ms to 7000
link: You must use B4A v8+ if you want to start from the background on Android 8+ devices. The minimum interval on new devices is 15 or 30 minutes.
link: Maybe this? https://www.b4x.com/android/forum/threads/now-android-6-servicestartatexact-not-accurate.65117/#post-412286 Looks like newer versions of B
link: Use a timer. Why are you using StartServiceAt?

StartServiceAt / StartServiceAtExact will not work on Android 12+. This is related to new Android restrictions. You need to use StartReceiverAt instead. It has nothing to do with Google. This is a permission that the user grants your app. B4A-Bridge uses it for example. With push notifications y
link: The CancelScheduledService keyword, which cancels services scheduled with StartServiceAt, also works with receivers scheduled with StartReceiverAt. B4

1. StartServiceAt will not help you if you need to do something every 30 seconds. The minimum interval is 15 minutes or 30 minutes. 2. StartServiceAt will not help too much if you want your app to run in the background. The only way to do it is demonstrated in the background location example. As y
link: This is more of an open discussion than a solution. According to this thread StartServiceAt uses the Android AlarmManager to do its tricks. While go
link: 1. StartServiceAt is not accurate by definition. StartServiceAtExact will be more accurate. 2. Android 6 is quite old now. Test it on newer versions.
link: This seems important and probably needs the StartServiceAt writer (presumably Erel) to comment.

Powered by ColBERT