Dominik Dzienia

Ad 4) it is because phone app formats and prepares output for watch, so we decide on contents at phone app (wear plugin) level. It allows wear implementation be way...

Understood! It should be possible, only concern is to have it compatible between different versions of wear and main versions of AAPS.

> I have updated wiki page about settings in watch : https://androidaps.readthedocs.io/en/latest/EN/Configuration/Watchfaces.html#settings-in-wear-watch Wow, that is impressive work! I will review it, work on _Complications_ section, and research what _Animation_ setting...

@Rhabarbara745 please try: - watchface without AAPS complications (but with other frequently refreshed ones) - to exclude watchface-complication-os interactions - does usage is the same with other complication-enabled watchfaces Unfortunately,...

I will work on rewriting complications refresh algorithm, but it is quite complex topic

Passwords (including settings_password) **are never stored in plain text.** The way the password is stored (HMAC) make it difficult to being recovered from exported preferences. Moreover - whole exported file...

the purpose of that feature is not to distinguish if the WiFi is safe or not, only to exclude/block networks that are *unsafe for sure*, without claims about other networks...

@twain47 i agree it should, but currently it is not required/enforced by app configuration, http urls are accepted AFAIK (if not - point me line of code that do that,...

i agree that additional two-way securing of communication between NS and AAPS would be better, but it would require non trivial changes to NS, having user configuring it properly on...

feel free to move paragraph above to separate issue for that matter, you are also welcome to discuss that on gitter to agree with other maintainers if that is preferable...