This object is in archive!
Possible API issue with Classic 3.6
Solved
from a post on the reddit tasker forum
the intent to start track recording works fine with LM4
but with LM3.6 classic, after changer the tasker task to locus.pro etc
it doesnt start the track recording
The same problem 
User says it works fine with 3.63.1, doesnt with 3.64 with same data etc
User says it works fine with 3.63.1, doesnt with 3.64 with same data etc
1. Realme, android 12
It's a problem after an update. Backup - reinstalling the older version (3.63.1) - Restore. The plugin works fine.
2. LineageOs, android 10
works even without a plugin. The data from the documentation that I provided at the beginning is enough.
3. I don't understand anything anymore. Realme, android 12 - version 3.63 works, 3.64 does not. Old phone, lineage, android 10. Older and newer versions work same. 🤷
It seems that the Android version may be the problem.
1. Realme, android 12
It's a problem after an update. Backup - reinstalling the older version (3.63.1) - Restore. The plugin works fine.
2. LineageOs, android 10
works even without a plugin. The data from the documentation that I provided at the beginning is enough.
3. I don't understand anything anymore. Realme, android 12 - version 3.63 works, 3.64 does not. Old phone, lineage, android 10. Older and newer versions work same. 🤷
It seems that the Android version may be the problem.
Hi guys,
I'm just working on it, but not sure if there is any solution, anyway give me a while. Problem is, that we were forced to update the so-called "Target API" to a new version and since then, there are new restrictions from Google applied to Locus Map as well. In this case, the option to start foreground service, like Track recording, over intent.
---
Hmm, I've probably found a method. The app needs to be excluded from the battery optimization. In case, app already is a "Device admin" (if you used screen on/off functionality), disable it first.
I've improved the setup on the app side so in the next app version (probably this week), request to "Disable optimization" should be automatic.
Hi guys,
I'm just working on it, but not sure if there is any solution, anyway give me a while. Problem is, that we were forced to update the so-called "Target API" to a new version and since then, there are new restrictions from Google applied to Locus Map as well. In this case, the option to start foreground service, like Track recording, over intent.
---
Hmm, I've probably found a method. The app needs to be excluded from the battery optimization. In case, app already is a "Device admin" (if you used screen on/off functionality), disable it first.
I've improved the setup on the app side so in the next app version (probably this week), request to "Disable optimization" should be automatic.
Replies have been locked on this page!