Handling autolock feature in an app

Hi,

I’ve had a user bug report with autolock basically messing up everything... and I haven’t (AFAIK) got autolock on my watch to test. I searched and found only a single_old_ thread saying the problem is “by design” so tough.

I cannot believe that’s the end of it! So three questions:

1. How can I simulate autolock?

2. Is there a way to block autolock when an activity has been started in my app?

3. Can I (and how can I) distinguish between autolock and other forms of onHide?

Thanks

Top Replies

jim_m_58 over 5 years ago in reply to 9635560 +1 verified

You can try using Force onHide and Force onShow in the sim. It appears to be any time that something is pushed on top of your view.
jim_m_58 over 5 years ago in reply to jim_m_58 +1

BTW, what happens when you lock, is if you try to interact with the watch, a lock icon shows on the screen for a second or so, then goes away.
Travis.ConnectIQ over 5 years ago in reply to 9635560 +1

9635560 said:
It’s a 735xt and definitely no autolock in that location.

The Display Auto Lock feature is usually something that is only available on touch screen devices. The fr735xt isn't a touch device…

All Replies

0 Travis.ConnectIQ over 5 years ago in reply to 9635560

9635560 said:
It’s a 735xt and definitely no autolock in that location.

The Display Auto Lock feature is usually something that is only available on touch screen devices. The fr735xt isn't a touch device so I wouldn't expect to find it there.

I looked through and I'm not seeing it anywhere, so I'm pretty sure this is the case.

0 jim_m_58 over 5 years ago in reply to Travis.ConnectIQ

I see auto lock on the f5+, 645 and others so it's not just touch. In this case I was testing with manual lock.

This seems to be a case where something between onShow() and onHide() gets confused.

0 9635560 over 5 years ago

Thanks, Jim!

I think I have a fix now.

0 9635560 over 5 years ago in reply to Travis.ConnectIQ

All good information on a feature I have only recently found out existed!

I'll try not to dredge up old threads here, but I wish there were a way to find some of these things out without simply building a personal encyclopaedic knowledge of every single Garmin device out there and / or waiting for a user to tell me something I didn't know existed has broken something I hadn't anticipated ever being a problem.

[*side note: I will not complain if anybody does want to give me every single Garmin device out there with a view to forming an encyclopaedic knowledge thereof. ]

0 jim_m_58 over 5 years ago in reply to 9635560

Getting a newer device than the 735 would probably help a great deal. It was announce May 2016, so 4 years back. One of the few things left on CIQ2, and there's been a world of change to devices capibilities since then, be they vivoactives, Forerunners, or Fenixs, Using a newer device for a few days can teach you a lot about the current generation of devices in general.

There's no in-person summit this year, but in the past, you came home with a new device.

0 9635560 over 5 years ago in reply to jim_m_58

jim_m_58 said:
There's no in-person summit this year, but in the past, you came home with a new device.

If it helps, I’ll pretend I went there if Garmin pretends it happened and then sends me a new device?