Watch Face: Last Known Position

benjamin.serant over 8 years ago

What is the good practice to obtain the Last Known Position from a Watch Face?

serekmedia over 8 years ago

Don't ask, or "battery consumption" ;)

benjamin.serant over 8 years ago

Don't ask, or "battery consumption" ;)

Strange response... It's no sense to answer like this.

"Known Last Position" must be a data stored in cache... so, it's not could be "battery consumption".

I read on several WatchFace Detail information about Known Last GPS Position, but I don't know if the information is available on each device of if each developer must develop specific cache storage.

serekmedia over 8 years ago

Plaese read: ~1 year ago:
https://forums.garmin.com/showthread.php?210013-REQUEST-watchface-access-to-system-data&p=516198#post516198

"Lowpower mode" is an ansfer ;) - not matter - it makes sense or not ;)

teadriven over 8 years ago

I think this has been discussed elsewhere, but I have used the following (and it works on a VA):

var position = Activity.getActivityInfo().currentLocation;

Which will return one of these containing the last known location.
I believe that it returns null if there has been no GPS related activity.

EDIT: Some feedback for my watchface suggests that on other models, such as the epix, the currentLocation is only available for a limited time once the GPS is no longer being used. Some caching may be required!

benjamin.serant over 8 years ago

Thank teadriven,

it's exactly what I want.
It's feel good with 920xt.

Now, I will analyze it in order to know if I need to manage the cache or if it's automatic.

cizister 3 months ago in reply to teadriven

Does it have a solution? I have an exact same problem with this code....

location = activityInfo.currentLocation;
if (location) {
    location = activityInfo.currentLocation.toRadians();
    app.Storage.setValue("location", location);
} else {
    location = app.Storage.getValue("location");
}

jim_m_58 3 months ago in reply to cizister

Understand that when to put stuff in Storage with setValue, it must be of an allowed data type. When I save a location in Storage I save it as lat/lon as floats.

You are trying to save an array of doubles, which I think should work per the doc. Do you get any kind of an error? It could be an error in the doc.

From the API Doc:

Keys can be of the following types:

Values can be of the following types:

String
Number
Float
Boolean
Char
Long
Double
BitmapResource (Since 3.0.0)
AnimationResource (Since 3.0.8)
ScanResult (Since 3.2.0)
null

cizister 3 months ago in reply to jim_m_58

It means, if understand correctly that the object location cannot be safe "as is" and should be divided into two variables like lat and long and then when I store these vars into Storage it should work?

Anyway thanks a lot for the reaction!

andyj713 3 months ago in reply to cizister

Arrays and Dictionaries are allowed for values as well. That's how I store the previous position.