You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[3.1.0.3](#version3100)| 2020.3.1 | up to Otter | 7.3.3 | 17 |
25
-
|[3.2.0.4](#version3204)| Hedgehog (2023.1.1) | up to Otter | 8.2 | 17 |
26
-
|[3.3.1.3](#version3300)| Ladybug Feature Drop (2024.2.2) | up to Otter | 8.10 | 21 |
27
-
|[3.3.2](#version3300)| Meerkat (2024.3.1) | up to Otter | 8.11.1 | 21 |
28
-
|[3.3.2.1](#version3321)| Narwhal (2025.1.2) | up to Otter | 8.13 | 21 |
29
-
|[3.4](#version3400)| Otter 2 Feature Drop (2025.2.2)|| 9 | 21 |
24
+
|[3.1.0.3](#version3100)| 2020.3.1 | up to Panda 2| 7.3.3 | 17 |
25
+
|[3.2.0.4](#version3204)| Hedgehog (2023.1.1) | up to Panda 2| 8.2 | 17 |
26
+
|[3.3.1.3](#version3300)| Ladybug Feature Drop (2024.2.2) | up to Panda 2| 8.10 | 21 |
27
+
|[3.3.2](#version3300)| Meerkat (2024.3.1) | up to Panda 2| 8.11.1 | 21 |
28
+
|[3.3.2.1](#version3321)| Narwhal (2025.1.2) | up to Panda 2| 8.13 | 21 |
29
+
|[3.4.1](#version3410)| Panda 2 (2025.32) || 9 | 21 |
30
30
31
31
The "preferred version" is packaged with the appropriate JVM version. The preferred version is also the minimal version you can use to build **AAPS**. You will **NOT** be able to build on a version older than the "preferred" one. If using a different version, you may encounter issues related to JVM version. See the [Troubleshooting Android Studio](#troubleshooting_androidstudio-uncommitted-changes) page to help solve these issues. If your current Android Studio version is not listed in the table, you must update it first.
Copy file name to clipboardExpand all lines: docs/CROWDIN/cs/SettingUpAaps/Preferences.md
+46-2Lines changed: 46 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -471,14 +471,58 @@ You can help develop **AAPS** further by sending crash reports to the developers
471
471
472
472
**Unattended Settings Export**<br/> By enabling this feature, you allow **AAPS** to execute settings exports without user intervention. For this the master password is securely stored on your phone (only) at the next manually export. The stored password will be used for up to 4 weeks. After 4 weeks you will be notified the password is about to expire. During a grace period of 1 week, the password can then be refreshed by manually exporting settings from the maintenance menu.
473
473
474
-
After the grace period of 1 week has passed the stored password expires and any automated settings export will abort while notifying the user, asking to reenter the password. [(**Automated settings exports**)](../DailyLifeWithAaps/Automations.md#automating-preference-settings-export) will be logged to the AAPS 'Careportal' and 'User entry' lists under Treatments.
474
+
After the grace period of 1 week has passed the stored password expires and any automated settings export will abort while notifying the user, asking to reenter the password. [(**Automated settings exports**)](../DailyLifeWithAaps/Automations.md#automating-preference-settings-export) will be logged to the **AAPS** 'Careportal' and 'User entry' lists under Treatments.
475
475
476
476
After enabling this option, make sure to perform a manual settings export, where you will be requested for your password, so that **AAPS** can store it.
477
477
478
-
(preferences-maintenance-logdirectory)= Maintenance settings also include the **AAPS** directory, which can be found directly under the Maintenance tab. This setting allows the user to choose a directory on their phone where **AAPS** will store preferences, logs, and other files.
478
+
### Log files
479
+
480
+
AAPS will save logs for troubleshooting.
481
+
482
+
Do not disable this feature: it will help understanding the reasons if something goes wrong.
483
+
484
+
If you need to send the logs to the developers, make sure you file accurately the mail contents to describe the issue. It is preferable to send logs only after being requested to do so, following an [issue report in GitHub](https://github.com/nightscout/AndroidAPS/issues).
485
+
486
+
You can find AAPS logs in your phone memory -> Android -> data -> info.nightscout.androidaps -> files.
Maintenance settings also include the **AAPS** directory, which can be found directly under the Maintenance tab. This setting allows the user to choose a directory on their phone where **AAPS** will store preferences, logs, and other files.
If you select a subdirectory of AAPS, you will see an error message. Tap "OK" and retry, selecting the correct directory (one above). Do not select "DISMISS" unless you clearly know what you are doing.
Můžete pomoci komunitě tím, že daruje vaše data do výzkumných projektů! Details are described on the [Open Humans page](../SupportingAaps/OpenHumans.md).
Choosing the default AAPS directory is recommended.</br>
148
+
Do **not** select a subdirectory of AAPS.
149
+
```
150
+
146
151
The default directory is **AAPS**, but you can use any dedicated directory of your liking. Create the directory if necessary, enter it, and choose "Use this folder":
Once a pump requiring AAPS to use Bluetooth is select, you will see a warning: AAPS requires Bluetooth permission. This will be addressed after you complete the Wizard.
Klinkněte na tlačítko "DALŠÍ" a přejděte na následující obrazovku:
517
+
518
+
V tomto případě vybereme "Virtuální pumpu".
494
519
495
520

496
521
@@ -556,4 +581,18 @@ Můžete kliknout na "ODLOŽIT" a zpráva zmizí.
556
581
557
582
If you accidentally leave the Setup Wizard at any point, you can either simply re-start the Wizard, or change the [configuration of the AAPS loop](../SettingUpAaps/ChangeAapsConfiguration.md) manually.
558
583
584
+
## Restart AAPS to validate settings
585
+
586
+
From the top right menu, select Exit to force AAPS to restart.
587
+
588
+

589
+
590
+
If you selected a Bluetooth connected pump, you will now see the permission request:
If your **AAPS** loop is now fully setup, please move on to the next section ["Completing the objectives"](../SettingUpAaps/CompletingTheObjectives.md).
Copy file name to clipboardExpand all lines: docs/CROWDIN/cs/SettingUpAaps/YourAapsProfile.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,11 +171,9 @@ See the **figure below** for an example of how ISF values could be set in an **A
171
171
172
172
Výchozím bodem pro stanovení vaší citlivosti v průběhu dne je výpočet založený na celkové denní dávce (TDD) pomocí pravidla 1700 (94). More detail is given in Chapter 7 of [“Think like a Pancreas”](https://amzn.eu/d/iVU0RGe) by Gary Scheiner.
173
173
174
-
1700 (měřeno v mg/dl) nebo 94 (mmol/L)/TDD = přibližná ISF.
Assuming your basal levels are correct, you can test this by suspending the loop, checking **IOB** is zero, and taking a few glucose tablets to get to a stable ‘high’ level.
Copy file name to clipboardExpand all lines: docs/CROWDIN/cs/WearOS/WearOsSmartwatch.md
+35-13Lines changed: 35 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,9 +77,9 @@ a) using a USB cable to put the **AAPS** wear apk file onto the phone, and then
77
77
b) cut and paste Wear.apk from Android Studio onto your Gdrive.
78
78
79
79
80
-
You can use eitherWear Installer 2 or Easy Fire tools to side-load AAPS onto the watch. Here we recommend Wear Installer 2, because the instructions and process in the video are so clear and well-explained.
80
+
To side-load AAPS onto the watch You can use either: 1) Wear Installer 2 2) Easy Fire tools 3) Android Debug Bridge (ADB) Here we recommend Wear Installer 2, because the instructions and process in the video are so clear and well-explained. If Wear Installer 2 does not work for you try via
81
81
82
-
## Using Wear Installer 2 to side-load **AAPS** Wear from the phone onto the watch
82
+
###Using Wear Installer 2 to side-load **AAPS** Wear from the phone onto the watch
2) Make yourself a developer in the watch (once set up and connected to phone):
105
+
2) Make yourself a developer in the watch (once set up and connected to phone):
107
106
108
-
Go to settings >about watch (bottom option) >- software info > software version.
107
+
Go to settings >about watch (bottom option) >- software info > software version.
109
108
110
-
Rapidly tap on “ software version” until a notification appears that the watch is now in "developer mode". Return to the top of settings menu, scroll to the bottom
111
-
and see “developer options” below “about watch”.
109
+
Rapidly tap on “ software version” until a notification appears that the watch is now in "developer mode". Return to the top of settings menu, scroll to the bottom and see “developer options” below “about watch”.
112
110
113
-
In “developer options”, turn on “ADB debugging” and “wireless debugging”. The latter option then reveals the IP address of the watch, the final two digits of which changes each time the watch is paired with a new phone. It will be something like: **167.177.0.20.** 5555 (ignore the last 4 digits). Note that the last two digits (here, “20”) of this address will change every time you change to a new phone handset for AAPS.
111
+
In “developer options”, turn on “ADB debugging” and “wireless debugging”. The latter option then reveals the IP address of the watch, the final two digits of which changes each time the watch is paired with a new phone. It will be something like: **167.177.0.20.** 5555 (ignore the last 4 digits). Note that the last two digits (here, “20”) of this address will change every time you change to a new phone handset for AAPS.
STEP 3) Enter IP address _e.g._ **167.177.0.20** into Easy Fire tools on the phone (go into the left hamburger, settings and enter the IP address). Then click the plug socket icon on the top right.
115
+
STEP 3) Enter IP address _e.g._**167.177.0.20** into Easy Fire tools on the phone (go into the left hamburger, settings and enter the IP address). Then click the plug socket icon on the top right.
@@ -124,7 +122,7 @@ STEP 3) Enter IP address _e.g._ **167.177.0.20** into Easy Fire tools on the
124
122
125
123
STEP 4) Follow the instructions [here](https://wearablestouse.com/blog/2022/01/04/install-apps-apk-samsung-galaxy-watch-4/?utm_content=cmp-true) to side-load (i.e. transfer) Wear.apk onto the smartwatch using Easy Fire tools
126
124
127
-
Click side "plug-in" socket in the app, in order to upload Wear OS.apk onto the smartwatch:
125
+
Click side "plug-in" socket in the app, in order to upload Wear OS.apk onto the smartwatch:
Connect your smartwatch and computer to the same wifi network.
140
+
141
+
- To install ADB download it from: https://developer.android.com/tools/releases/platform-tools
142
+
- Open a terminal.
143
+
- After installation of ADB for windows set the path to the folder where ADB is located: `setx PATH "%PATH%;C:\platform-tools"`
144
+
- For Mac instead of installing manually you can use homebrew: `brew install android-platform-tools`
145
+
146
+
On the watch:
147
+
- Go to Settings → About watch → **Software Information**
148
+
- Tap Software version 7 times until you see Developer mode enabled.
149
+
- Go to Settings → Developer options. Enable **ADB debugging**
150
+
- Go to Settings → Developer options → Wireless debugging → **Pair new device**
151
+
152
+
You will see a wifi pariing code and ipaddress and port appearing:
153
+
<imgwidth="689"height="400"alt="Screenshot 2025-12-21 at 17 46 42"src="https://github.com/user-attachments/assets/9b73869a-e4ca-47e6-9ac4-37ecc20182e1" />
154
+
- In the terminal: `adb pair ipaddress:port` E.g. `adb pair 10.10.1.125:36443`
155
+
- You will be asked for the pairing code. Enter it.
156
+
- You will see a response:<br> `Successfully paired to 10.10.1.125:36443 [guid=adb-RXXXW20LMKJY-eh5zBj]`<br>
157
+
- In the terminal type: <br>`adb devices`.<br> You should see something like:<br> `List of devices attached`<br> `10.10.1.125:45559 offline`<br> `adb-RFAW20LMKJY-eh5zBj._adb-tls-connect._tcp device`<br>
158
+
159
+
- Now go to the folder on your computer where the Wear apk is and type<br> `adb install wear-full.apk` <br>with wear.apk replaced by the name of your apk file.
160
+
- You will see:<br> `Performing Streamed Install`<br> `Success`
161
+
162
+
141
163
### General troubleshooting recommendations for Wear OS 5
0 commit comments