How can I bypass the check for 15% in the AOD face?
Yes, I understand there’s a trade-off between seeing my watch face and battery time. I’m perfectly happy to make that trade off, even if it means I can’t publish the watch face in the play store.
You can do it by extracting the watchface.xml, building and installing it manually (ie, outside WFS). It’s not terribly easy.
With Fitbit watches, there was a chance of physical damage to the display circuitry by trying to pump more pixels than the low-power mode made available. I don’t know if that applies to other watches, but maybe there’s more at stake than just battery life.
Thanks! I’ll have a look at that.
I’ve been using the same watch face for a couple years and the brightness setting hasn’t hurt my watch yet.
I probably want 20 or 25%. It’s just that 15% is too dim for me to easily read the display unless I really crank up the display brightness, and then it’s overwhelming when the watchface is active.
I know what you mean. I’m battling with an AOD layout at the moment. In future, I might start the design with AOD and then add stuff for interactive, rather than the other way around.
There’s stuff in this forum about how to extract your watchface.xml from the .wfs file. It MAY be necessary to build the watchface in WFS for watchface.xml to be created. If so, you may need to make an adjustment which you can reverse later.
Info about how to build the watchface from the .xml is here. It’s a bit vague. I think I started by downloading and building the demo repo, and then customising that (eg, pasting in my .xml, changing package name, etc).
I plan to make a blog post or something about this somewhere/sometime.
If you know of any forum for discussion of direct use of WFF (ie, not using WFS), please let me know! Even StackOverflow has very little.
2 Likes