Which is the exact way to send the location while in the background. In previous times, sending the location was extremely simple. Now I haven't made it.
I used a phone with an old version of android 9 and it worked perfectly. install the same program on a phone with android 11, and it stopped working.
My question is: may or may not send in the background at present?. I have done all the examples and I do not get the solution
Simple example of a foreground service that keeps the process running in the background. The current location is shown in the persistent notification. The app starts at boot and theoretically should run all the time. It also schedules itself to run with StartServiceAt. This can help in cases...
www.b4x.com
Not sure if it still a working solution. I read often about the same problem. You need to try
Android is more restrictive with every update.
In the DonManfred link you have this advice, have you do this?
There is a new requirement in Android 10+ devices.
In order for the location tracking to continue working in the background, if the user chooses the "allow while app is open" permission option we need to add this line to the manifest editor:
Android is more restrictive with every update.
In the DonManfred link you have this advice, have you do this?
There is a new requirement in Android 10+ devices.
In order for the location tracking to continue working in the background, if the user chooses the "allow while app is open" permission option we need to add this line to the manifest editor:
Simple example of a foreground service that keeps the process running in the background. The current location is shown in the persistent notification. The app starts at boot and theoretically should run all the time. It also schedules itself to run with StartServiceAt. This can help in cases...
www.b4x.com
Not sure if it still a working solution. I read often about the same problem. You need to try
Android es más restrictivo con cada actualización.
En el enlace de DonManfred tienes este consejo, ¿has hecho esto?
Hay un nuevo requisito en los dispositivos Android 10+.
Para que el seguimiento de ubicación continúe funcionando en segundo plano, si el usuario elige la opción de permiso "permitir mientras la aplicación está abierta", debemos agregar esta línea al editor de manifiesto:
[código]
SetServiceAttribute(Tracker, android:foregroundServiceType, "ubicación")
[/código]
Android is more restrictive with every update.
In the DonManfred link you have this advice, have you do this?
There is a new requirement in Android 10+ devices.
In order for the location tracking to continue working in the background, if the user chooses the "allow while app is open" permission option we need to add this line to the manifest editor:
Thanks jose, I've already tried it and nothing. It's like it stopped working.
As I mentioned before, on a phone with android version 9 it works perfectly, I have even written that in the manifest and nothing does not work
I remember there is a very helpful thread from a forum member where he was testing a lot of things with services and differents versions of android, but I can't find it. Maybe was @Sandman or @Mahares ? Not sure.
Anyway, if you test some apps that runs in background for long time, now it shows you some tips before redirecting you to the permission settings (i.e. Ignore app from battery optimization, etc...)
Hi guys, I runs this example on my phone : Android 9, EMUI 9.1, B4A 9.8 https://www.b4x.com/android/forum/threads/background-location-tracking.99873/#content The app is suppose to runs forever but in my case, when phone slept for a few minutes, OS killed it. I changed the codes at service...
Just a confirmation if I'm doing correctly: I have declared in "configure paths" the android-23 platform. This because I want to manage a runtime permission in Android 6 and force the user to exclude the App from the battery optimization Sub Activity_Resume If GetAndroidApiLevel>=23 Then...
I remember there is a very helpful thread from a forum member where he was testing a lot of things with services and differents versions of android, but I can't find it. Maybe was @Sandman or @Mahares ? Not sure.
Anyway, if you test some apps that runs in background for long time, now it shows you some tips before redirecting you to the permission settings (i.e. Ignore app from battery optimization, etc...)
Hi guys, I runs this example on my phone : Android 9, EMUI 9.1, B4A 9.8 https://www.b4x.com/android/forum/threads/background-location-tracking.99873/#content The app is suppose to runs forever but in my case, when phone slept for a few minutes, OS killed it. I changed the codes at service...
Just a confirmation if I'm doing correctly: I have declared in "configure paths" the android-23 platform. This because I want to manage a runtime permission in Android 6 and force the user to exclude the App from the battery optimization Sub Activity_Resume If GetAndroidApiLevel>=23 Then...
Jose, super grateful, for your time and for your interest in helping me solve this problem that is serious for me, since I have an app which is very important to use location sending in the background, I will read the information and I tell you if it works for me
This document describes the different types of location requirements for Android apps, including foreground and background access, and varying accuracy levels, explaining how to request the appropriate location permissions for each use case.
This document describes the different types of location requirements for Android apps, including foreground and background access, and varying accuracy levels, explaining how to request the appropriate location permissions for each use case.
This document provides guidelines and best practices for Android apps requiring background location access, focusing on critical functionality, user benefits, and compliance with Google Play policies and privacy. It includes a checklist for identifying and evaluating background location usage...
This document provides guidelines and best practices for Android apps requiring background location access, focusing on critical functionality, user benefits, and compliance with Google Play policies and privacy. It includes a checklist for identifying and evaluating background location usage...
Hello TILogistic, thanks for providing a possible solution to the problem. Yes indeed, I use FusedLocationProvider.
I have removed all the code and I have left only the base code (the one that appears in the demos in its most recent version of FusedLocationProvider)
but nothing, I remember that the same code had been working for me for a year without any problem. but from a while ago it didn't work anymore.
I have already tried this option and it does not work: the problem is basically: We have a service which records the location, the problem is that when calling "waze" in an intent ,the application goes to the background and immediately stops send position, when closing waze and returning to the foreground once it starts sending correctly
I explain in more detail:
the problem is basically: We have a service which records the location perfectly, the problem is that when calling "waze" in an INTENT the application goes to the background and immediately stops sending position, when closing waze and resume the foreground once starts sending successfully