Location based tracking does not work about trackworktime HOT 8 CLOSED

Having the same problem and I am already using Automate for some other tasks, I did try to implement a broadcast to simply ClockIn and ClockOut nothing else in a manual Automate workflow, but this doesn't seem to work. I use Broadcast send and I believe I tried all possible combinations using package, receiver class and action.

I could solve it myself by using the pick receiver method and choosing the ThirdPartyReceiver.

from trackworktime.

The mechanism for tracking by location works with cell coordinates and uses no GPS even if available because that would drain the battery really fast. If your phone company only has one base station covering the whole area, the location can be really inaccurate (some stations in Germany only provide a location with 2.5 km tolerance).

Did you try the menu item "Here = Work" (screenshot)? By using it, TWT uses the current location (as provided by the base station(s) in reach) as work location - perhaps that helps.

from trackworktime.

Perhaps checking GPS once every 30 mins or so would not drain the battery so much?
It might indeed be the case that there is only one cell tower in the region. One way that occurs to me for checking that is to tap Here = Work at my workplace and home and compare the results.

But ultimately I would like to find a way to rely on the GPS for this since the precision is much better. Perhaps by using Llama/Tasker? Are you aware of any other apps that do this?

from trackworktime.

My goal for writing TWT was to clock in and out by the minute so checking for GPS position every 30 minutes would not help (although the battery consumption would be considerably lower than checking for GPS position every minute, you're right).

I don't use general automation apps at the moment, but I'm sure Tasker, Llama or Automate could help. All the app has to do is to create intents as described here (or in the README).

Could you report the result when you tried Here = Work at both your workplace and home? I'd like to know if that's really the problem. You don't have to give the exact values, anonymized values are fine - the difference is interesting. 😄

from trackworktime.

OK so I did that. First strange thing is that Tolerance, both at home and work is 2000. The Latitude is exactly the same in the two locations, and the Longitude has a difference of 0.025202.

I installed Automate but can't figure out how to configure it to send the clock-in and clock-out broadcast intents.

from trackworktime.

Depending on where you are located, a difference of 0.025202 in longitude is 2.8 kilometers at maximum (along the equator). Given the tolerance your cell tower combination is only able to provide, it is possible that the app still sees your phone in the same (rough) location and therefore does not clock you in.

Regarding Automate, the information at https://llamalab.com/automate/doc/block/activity_start.html could help. But did you try Llama and Tasker? Those apps are known to work with TWT.

from trackworktime.

Llama also uses phone masts iirc..

Edit: I now see it has an experimental GPS option.

from trackworktime.

@berceanu: I released a fix for background services on Android 8+ (see #37). Could you test again (using version 1.0.3) if the location checking does work now? I'm optimistic that it will work. 😃

I'd also like to hear your opinion on alternatives you tested!

from trackworktime.