Quick question to understand backgrounding

[Julio_Spinelli]

Doesn't work on all phones...

[Salvatore_Oliva]

Hi Sunny,

I am Salvatore, I well remember about you, I got your help some months ago to include Deep Link feature in an AI2 app of mine: thank you again for your valuable and effective support, you were very nice.

I take occasion to get in touch with you again in this specific thread, because I have noticed your GitHub project of an AI2 extension for background tasks (https://github.com/vknow360/BackgroundTask) and I would be quite interested about that. Nowadays, is your extension ready and usable? Could you compile and release it in AIX format and provide some documentation and example as well, please?

Hoping for your kind feedback. Cheers.

Salvatore

[vknow360]

Hi @Salvatore_Oliva
Unfortunately, I have stopped working on that project due to time limitations.
I am sure that will be completed in near future.

[Salvatore_Oliva]

Hi Sunny, thank you for your kind feedback.
Please, keep us informed about that project of yours, the attention on it seems to be high. I am very interested in it and several other people and I would like to see it completed and get published here in the community. I do believe it would be a strong success. I would be pleased to be personally informed when the project is ready and I can offer my availability to test and debug it.
Hoping to hear from you soon. Thank you again, my deep respects.

[Patryk_F]

You can try this extension:
https://ullisroboterseite.de/android-AI2-KeepAlive-en.html

[Anke]

@Patryk_F

You can try this extension:

As I said before, this extension has nothing to do with a → Background service, it is all about a → Foreground service in order to prevent → Doze mode from becoming active.
Note: And a Background service has no effect on Doze mode.

[sp.rokith]

Thank you soon much for the extension.

It works perfectly on my phone. My app is running in background and triggering the timer perfectly.

Thank you soo much again.

[Hikmet_1]

Hi Anke,
How we can solve this problem.
I'm trying to write an application with a time counter.
The app sleeps after a while even when charging

[Anke]

@Hikmet_1

I'm trying to write an application with a time counter.
The app sleeps after a while even when charging

Show your blocks.
And did you enable TimerAlwaysFires?

[Hikmet_1]

Yes Anke,

But 1 or 2 min. is sleeping applicaiton.

[Hikmet_1]

And even when i add it to "never go to sleep" section from andorid settings the app is still sleeping!...

[Anke]

@Hikmet_1

the app is still sleeping

What is your goal? Do you only want to keep the screen on?
Or do you claim that the timer does not work in idle (sleep) mode even when the device is charging?

[Hikmet_1]

My aim is this;
I want the application I wrote to continue to run in the background.
The user ran the application.
The seconds began to increase. It also started increasing by +1 on a counter.
User switched to Instagram. Or turned off the screen, the screen is now black.
I want the application to keep counting the seconds, the counter to keep moving.
I wonder if I could explain

[Anke]

@Hikmet_SOYDAM

I want the application to keep counting the seconds, the counter to keep moving.

Ok, the reason why the timer stops in background / idle / sleep mode is that Doze mode strikes and shuts down / throttles all possible functions (CPU, WiFi, timers, internet connection / LTE etc). But that shouldn't happen while the device is charging. I've checked this on dozen of devices running all versions of Android (for years).

In order for it to work without charging, a Foreground service is definitely required. Search hereafter in the forum and you will find my answers / solution (AI2, Kodular, ...).

Last here:

Alarm Clock can not work

Galaxy Note8 (Android 9) and Pixel 2XL (Android 11). Typically, Doze mode has a particularly drastic effect on Samsung devices and throttles all possible functions (WiFi connection, timer, CPU etc.) when the device is in the background / idle mode. In order to effectively prevent this on all devices, a Foreground service must be used. Check it out, if the problem also occurs when the device is connected to a charging cable and charging during the test. See e.g. here:

Se detiene el audio al apagar la pantalla del teléfono

This should work (if the app is in the foreground, the screen is visible). I've tested this over and over again on dozens of devices and all versions of Android for years. But if the app is in the background or in idle (sleep) mode, a Foreground service is always required so that it works on all devices (i.e. the device does not fall into Doze mode). The problems with streaming / radio apps have been discussed intensively and extensively in all forums (AI2, Kodular, …) for years (also with th…

[Hikmet_1]

Hi Anke,
I am a Sansung Galaxy A50 and Android 11 version user.
The timer stops while the phone is charging, it definitely lags behind.
At the same time I am running a stopwatch on another device.
There is a very obvious difference between them.

[Anke]

@Hikmet_1

The timer stops while the phone is charging, it definitely lags behind.
At the same time I am running a stopwatch on another device.
There is a very obvious difference between them.

What duration are we talking about? 5 min?

It is well known that the Clock component is not accurate. It is always something lagging behind, which is clearly noticeable over a long period of time compared to a chronometer. On average (device-dependent) the timer loses around 1 second per minute.

[Hikmet_1]

@Anke

What duration are we talking about? 5 min?

It is well known that the Clock component is not accurate. It is always something lagging behind, which is clearly noticeable over a long period of time compared to a chronometer. On average (device-dependent) the timer loses around 1 second per minute.

Definitely in a 20 minute experiment, 5-10 min. lags behind. After the first 1-2 minutes, my application stops (sleeping). It doesn't work until I call it back to the screen. I don't care about milliseconds anyway. It's enough for me to be the same for about seconds. do you understand? For example, I am making a taximeter. I am making a bike rental application.

[Anke]

@Hikmet_1

Definitely in a 20 minute experiment, 5-10 min. lags behind.

Ok, I'll check this again on my 16 test devices (Android 4.x, 5.x, 7, 8.x, 9, 10, 11).
Maybe something has changed in the meantime ...

[Hikmet_1]

Thank you so much.

[Anke]

@Hikmet_1

Definitely in a 20 minute experiment, 5-10 min. lags behind. After the first 1-2 minutes, my application stops (sleeping). It doesn't work until I call it back to the screen. I don't care about milliseconds anyway.

Try this app. It shouldn't lose a single millisecond, even not when the screen (the app) is in the background or in idle (sleep) mode (also not, if the app is running for many hours):

preciseTimer_2.apk

Compare it to a chronometer.