• Replies 13 replies
  • Subscribers 18 subscribers
  • Views 1471 views
  • Users 0 members are here
Options
Related

LOCATION_DISABLE on vivoactive 3

winder1987
Hey Guys,

I am not sure if this is a bug, a feature or what else so I ask you why this happens:
I have an option in my app to disable the GPS tracking ( Position.enableLocationEvents(Position.LOCATION_DISABLE, method(: onPosition)); ) on runtime. This works well for all devices EXCEPT the Vivo 3. On the Vivo 3 GPS is still enabled and the track is still recorded in the FIT file.
What I do is to enable the GPS on start of the app and at the onPosition I decide to turn it off again or not.

Do you have an idea, why it won't turned off on Vivo 3?

Regards
Andy
  • Why not just check if you will be using GPS before you turn it on and just not turn it on if you won't be using it?
  • Another option may be to make sure you turn off GPS before you start the recording session.
  • Hi Jim,

    Why not just check if you will be using GPS before you turn it on and just not turn it on if you won't be using it?


    yeah sure, I could do that, but this wouldn't solve the problem, when the GPS is turned off on runtime...
    I just don't understand, why there is a differen behavior between Vivo and Vivo 3 for example...
  • +1
    It is very annoying. My static location is being recorded, while stretching. Even when it is deactivated.
    And it reveals my exact home location :(
  • I have an option in my app to disable the GPS tracking ( Position.enableLocationEvents(Position.LOCATION_DISABLE, method(: onPosition)); ) on runtime.


    While the above should work (you are asking to disable GPS), have you tried...

    Position.enableLocationEvents(Position.LOCATION_DISABLE, null);


    Let me know if that makes any difference.

    Either way, I'll spend a few minutes today to write up a test case and get something filed.

    Travis
  • While the above should work (you are asking to disable GPS), have you tried...

    Position.enableLocationEvents(Position.LOCATION_DISABLE, null);


    Let me know if that makes any difference.

    Travis


    Hey,

    I tried that already and sadly it doesn't make any difference... I have absolutely no idea why this happens...

    Regards
    Andy
  • Any update on this?

    I did not really thought about it. But it seems to be worse!
    My Manifest.xml doesn't allow to fetch the Position :eek:

    That means, I cannot use Travis approach, because it would intend to enable the Position to disable the Position :rolleyes:
    And it allows recording the position without enabling it in the manifest...

    Got Fit, FitContributor & Sensor allowed.
  • There is FW bug on both the vahr and va3 at the moment, where if you have a watchface that does background communications (getting the weather is the one that's common) when you start recording an indoor activity (indoor walk, strength training, etc), GPS will be turned on the first time the background process runs. I reported this to Garmin a while back, and hopefully a fix is coming soon. No comm has to occur, it's just having a background process in the watchface with comm permissions.

    Could this be what you are seeing if your watch-app doesn't use GPS?
  • Could this be what you are seeing if your watch-app doesn't use GPS?

    It seems to be exactly what you describe!
    Got the Weather Watchface installed and activated. Then, my App without Positioning enabled/activated/used/allowed records my position.

  • Looks like Garmin solved this issue in FW 2.70.

    But it seems not to be perfect improvement: GPS with IQ App Fw 2.70
    Quite drastic :rolleyes: