10-04-2017 09:18 - edited 10-04-2017 13:51
10-04-2017 09:18 - edited 10-04-2017 13:51
Considering that the ionic does not have an always on display, and the sensitivity for raising your wrist to turn on the display is about as easy as trying to push over a horse, it is absolutely imperative that I be able to override the sensitivity by having my watch face look for changes in orientation and keep the display on for longer periods of time - until the user lowers their wrist.
But it seems setting display.autoOff to false (as described in the API here: https://dev.fitbit.com/reference/device-api/display/ ) is having no effect, from either my watch face or even a watch app. Logging in console shows that it has been changed to false (and should therefore prevent the display from turning off indefinitely until display.on=false is explicitly commanded), but the display still automatically turns off.
I really really want to make this watch work. The development environment is the friendliest since the pebble, but I'm worried fitbit is going to keep it too restricted. As a developer, I need full control over the display, the sensors, click events, all of it. I can tell that it's a very early product, and most of the bugs and problems I see can definitely be fixed over time with software updates.
Anyway, am I doing something wrong with autoOff, or is this a bug?
Thanks.
Answered! Go to the Best Answer.
10-04-2017 13:24
10-04-2017 13:24
Try this:
import { display } from "display"; display.autoOff = false; display.on = true;
10-04-2017 13:24
10-04-2017 13:24
Try this:
import { display } from "display"; display.autoOff = false; display.on = true;
10-04-2017 13:49
10-04-2017 13:49
Great, that works! Thanks for the tip. I was working from your reply in another thread which was just:
import display from "display";
and that did not work, but didn't throw any errors either.
Anyway, I guess there's still a ways to go in terms of polishing the fitbit studio, and completing the API. So far what I see in terms of developing for the Ionic is pretty encouraging, although still pretty rough since it just launched. Hoping to see lots of SDK improvements over time, and hopefully to the OS itself. Cautiously optimistic, will continue developing 😄
Thanks again.