openaps · psonnera · Aug 20, 2025 · Aug 19, 2025 · Aug 19, 2025 · Aug 19, 2025
diff --git a/docs/CROWDIN/cs/Maintenance/DocumentationUpdate.md b/docs/CROWDIN/cs/Maintenance/DocumentationUpdate.md
@@ -4,7 +4,7 @@
 
 - Updated versions and Android Studio prerequisites
 - Added [3.3.2.1](#version3321) release, removed Android 16 references (fixed)
-- Added [Browser Build](browser-build) @Angus
+- Added [Browser Build](#browser-build) @Angus
 
 ## May 2025
 

diff --git a/docs/CROWDIN/cs/Maintenance/ReleaseNotes.md b/docs/CROWDIN/cs/Maintenance/ReleaseNotes.md
@@ -55,6 +55,8 @@ Aby bylo uživatelům se starším Androidem umožněno používat starší verz
 WearOS 5, API level 34 (Android 14) has [limitations](#BuildingAapsWearOs-WearOS5).
 ```
 
+(latestrelease)=
+
 (version3321)=
 
 ## Version 3.3.2.1

diff --git a/docs/CROWDIN/cs/Maintenance/UpdateBrowserBuild.md b/docs/CROWDIN/cs/Maintenance/UpdateBrowserBuild.md
@@ -0,0 +1,101 @@
+# Update with a browser
+
+## Vyrobte si místo stažení
+
+**AAPS** is not available to download, due to regulations concerning medical devices. Je legální vytvořit aplikaci pro své vlastní použití, ale nesmíte dát kopii ostatním! See [FAQ page](../UsefulLinks/FAQ.md) for details.
+
+```{note}
+In case you want to upgrade **AAPS** with a browser for the first time : copy your back-up keystore file to your Google Drive. Then follow the [Browser Build **AAPS** procedure](../SettingUpAaps/BrowserBuild.md) instead of this guide. Instead of creating a new keystore, you must select the one you have copied from your computer.
+This operation will be mandatory only the first time, then for successive upgrades you will be able to follow this guide.
+```
+
+## Overview for updating to a new version of AAPS with a browser
+
+```{contents} Steps for updating to a new version of AAPS
+:depth: 1
+:local: true
+```
+
+In case you experience problems, see separate page for [troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio).
+
+### Export your settings
+
+Export your settings from the existing **AAPS** version on your phone. You might not need it, but better be safe than sorry.
+
+See the [Export & import settings](ExportImportSettings.md) page if you don't remember how to do this.
+
+(Update-to-new-version-update-your-repo)=
+### Update your GitHub repository
+
+```{admonition} WARNING
+:class: warning
+Browser Build is available from AAPS version 3.3.2.1.
+```
+
+[Log into GitHub](https://github.com/login).
+
+1. Select Repositories.
+2. Scroll down and select your own AndroidAPS repository.
+
+![Select AndroidAPS repo](../images/update/CI/GitHubUpdate1.png)
+
+3. Verify you are using your own copy of AndroidAPS (Forked from nightscout/AndroidAPS)
+4. Tap Sync Fork to update it (the number of commits behind might differ from the picture)
+
+
+
+![Sync AndroidAPS repo](../images/update/CI/GitHubUpdate2.png)
+
+5. Tap Update Branch
+
+![Update AndroidAPS repo](../images/update/CI/GitHubUpdate3.png)
+
+Note: if you have modified your copy of AndroidAPS by mistake, you will see this screen. Discard all changes (commits) to return to the released version.
+
+![Discard rogue modifications](../images/update/CI/GitHubUpdate4.png)
+
+You have now synchronized (updated) your own copy with the latest release of Android APS. Good job.
+
+![Repo sync'ed](../images/update/CI/GitHubUpdate5.png)
+
+### Run the Workflow to Build the Signed APK
+
+1. In your GitHub copy of AndroidAPS, select Actions.
+2. Expand All Workflows.
+3. Select AAPS-CI
+
+![Actions AAPS-CI](../images/update/CI/GitHubActions1.png)
+
+4. Scroll down and tap Run Workflow.
+
+![Run Workflow](../images/update/CI/GitHubActions2.png)
+
+5. Select the branch you want to deploy (master), the [variant](variant) (fullRelease) and tap Run Workflow.
+
+
+
+![Run Workflow](../images/update/CI/GitHubActions3.png)
+
+6. You will see the message Workflow run was successfully requested. Refresh your browser page and you will be able to monitor the build progress. When the action completes, the AAPS CI action will show a green tick mark. You have successfully built the updated version of Android APS.
+
+![Monitor Workflow](../images/update/CI/GitHubActions4.png)
+
+### Install the AAPS APK
+
+1. Open your Google Drive
+2. Browse into AAPS, select the new version folder and you will find both the phone and Android Wear versions.
+
+![Google Drive Location](../images/update/CI/GitHubActions5.png)
+
+
+Continue [here](#Update-to-new-version-check-aaps-version-on-phone)
+
+## Troubleshooting
+
+If anything goes wrong, don't panic.
+
+Take a breath!
+
+Then see the [troubleshooting tips](#aaps-ci-preparation) if your problem is already documented!
+
+If you need further help, please reach out to other **AAPS** users on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw).
diff --git a/docs/CROWDIN/cs/Maintenance/UpdateComputerBuild.md b/docs/CROWDIN/cs/Maintenance/UpdateComputerBuild.md
@@ -0,0 +1,103 @@
+# Update with a computer
+
+## Vyrobte si místo stažení
+
+**AAPS** is not available to download, due to regulations concerning medical devices. Je legální vytvořit aplikaci pro své vlastní použití, ale nesmíte dát kopii ostatním! See [FAQ page](../UsefulLinks/FAQ.md) for details.
+
+```{note}
+In case you want to build **AAPS** on a new computer : copy your back-up keystore file to the new computer. Then follow the [Initial build **AAPS** procedure](../SettingUpAaps/BuildingAaps.md) instead of this guide. With the only difference that instead of creating a new keystore, you can select the one you have copied on the new computer.
+```
+
+## Overview for updating to a new version of AAPS with a computer
+
+```{contents} Steps for updating to a new version of AAPS
+:depth: 1
+:local: true
+```
+
+In case you experience problems, see separate page for [troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio).
+
+### Export your settings
+
+Export your settings from the existing **AAPS** version on your phone. You might not need it, but better be safe than sorry.
+
+See the [Export & import settings](ExportImportSettings.md) page if you don't remember how to do this.
+
+### Check your Android Studio version
+
+The minimal version required is described in the [Building Instructions](#Building-APK-recommended-specification-of-computer-for-building-apk-file). If your version is older, please [update Android Studio first](#Building-APK-install-android-studio)!
+
+(Update-to-new-version-update-your-local-copy)=
+### Update your local copy
+
+```{admonition} WARNING
+:class: warning
+If you update from versions prior to 2.8.x, please follow the instructions to do a [New clone](../SettingUpAaps/BuildingAaps.md), as this guide will not work for you!
+```
+
+* Open your existing AAPS project with Android Studio. You might need to select your project. (Double) click on the AAPS project.
+
+  ![Android Studio - Select Project](../images/update/01_ProjectSelection.png)
+
+* In the menu bar of Android Studio, select Git -> Fetch
+
+   ![Android Studio Menu - Git - Fetch](../images/update/02_GitFetch.png)
+
+* You will see a message in the lower right corner that Fetch was successful.
+
+   ![Android Studio Menu - Git - Fetch successful](../images/update/03_GitFetchSuccessful.png)
+
+* In the menu bar, now select Git -> Pull
+
+   ![Android Studio Menu - Git - Pull](../images/update/04_GitPull.png)
+
+* Leave all options as they are (origin/master) and select Pull
+
+   ![Android Studio - Git - Pull dialog](../images/update/05_GitPullOptions.png)
+
+* Wait while download is in progress, you will see this as info in the bottom bar. When it's done, you will see a success message.
+
+  ```{note}
+  The files that were updated may vary! This is not an indication
+  ```
+
+   ![Android Studio - Pull successful](../images/update/06_GitPullSuccess.png)
+
+* Gradle Sync will be running to download some dependencies. Wait until it is finished.
+
+  ![Android Studio - Gradle Sync](../images/studioSetup/40_BackgroundTasks.png)
+
+### Check JVM version
+
+This check is particularly indicated if you have already built a previous version of **AAPS** on the same computer.
+
+Check in the [Building Instructions](#Building-APK-recommended-specification-of-computer-for-building-apk-file) the required version for JVM, matching the **AAPS** version you are now building. Then follow the steps described at [Incompatible Gradle JVM](#incompatible-gradle-jvm) to make sure you currently use the correct version.
+
+(Update-to-new-version-build-the-signed-apk)=
+### Build the Signed APK
+
+Your sourcecode is now the current released version, and all prerequisites have been checked. It's time to build the signed apk as described in the [build signed apk section](#Building-APK-generate-signed-apk).
+
+(Update-to-new-version-transfer-and-install)=
+
+### Transfer and install the apk
+You need to transfer the apk to your phone so you can install it.
+
+```{note}
+If you completed the build with the same existing key store in Android Studio, then you do not need to remove the existing app on your phone. When you install the apk, follow the prompts to install updates.
+For other scenarios such as establishing a new key store in Android Studio for your signed apk, you will need to delete the old app before installing the apk. **Make sure to export your settings!**
+```
+
+See the instructions for [transferring and installing AAPS](../SettingUpAaps/TransferringAndInstallingAaps.md)
+
+Continue [here](#Update-to-new-version-check-aaps-version-on-phone).
+
+## Troubleshooting
+
+If anything goes wrong, don't panic.
+
+Take a breath!
+
+Then see the separate page [troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) if your problem is already documented!
+
+If you need further help, please reach out to other **AAPS** users on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw).
diff --git a/docs/CROWDIN/cs/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/cs/Maintenance/UpdateToNewVersion.md
@@ -10,91 +10,14 @@
 * When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
 * The new version will also be announced on Facebook at the time of release.
 * Following the release, please read the [Release Notes](ReleaseNotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
-
-    ```{note}
-    In case you want to build **AAPS** on a new computer : copy your back-up keystore file to the new computer. Then follow the [Initial build **AAPS** procedure](../SettingUpAaps/BuildingAaps.md) instead of this guide. With the only difference that instead of creating a new keystore, you can select the one you have copied on the new computer.
-    ```
 
-## Overview for updating to a new version of AAPS
+## Update AAPS with browser build
 
-```{contents} Steps for updating to a new version of AAPS :depth: 1 :local: true
+If you already built your AAPS app with the Browser Build method, follow [these instructions](./UpdateBrowserBuild.md).
 
-    <br />In case you experience problems, see separate page for [troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio).
-
-    ### Export your settings
-
-    Export your settings from the existing **AAPS** version on your phone. You might not need it, but better be safe than sorry.
-
-    See the [Export & import settings](ExportImportSettings.md) page if you don't remember how to do this.
-
-    ### Check your Android Studio version
-
-    The minimal version required is described in the [Building Instructions](#Building-APK-recommended-specification-of-computer-for-building-apk-file). If your version is older, please [update Android Studio first](#Building-APK-install-android-studio)!
-
-    (Update-to-new-version-update-your-local-copy)=
-    ### Update your local copy
-
-    ```{admonition} WARNING
-    :class: warning
-    If you update from versions prior to 2.8.x, please follow the instructions to do a [New clone](../SettingUpAaps/BuildingAaps.md), as this guide will not work for you!
-
+## Update AAPS with a computer
 
-* Open your existing AAPS project with Android Studio. You might need to select your project. (Double) click on the AAPS project.
-
-    ![Android Studio - Select Project](../images/update/01_ProjectSelection.png)
-
-* In the menu bar of Android Studio, select Git -> Fetch
-
-    ![Android Studio Menu - Git - Fetch](../images/update/02_GitFetch.png)
-
-* You will see a message in the lower right corner that Fetch was successful.
-
-    ![Android Studio Menu - Git - Fetch successful](../images/update/03_GitFetchSuccessful.png)
-
-* In the menu bar, now select Git -> Pull
-
-    ![Android Studio Menu - Git - Pull](../images/update/04_GitPull.png)
-
-* Leave all options as they are (origin/master) and select Pull
-
-    ![Android Studio - Git - Pull dialog](../images/update/05_GitPullOptions.png)
-
-* Wait while download is in progress, you will see this as info in the bottom bar. When it's done, you will see a success message.
-
-    ```{note}
-    The files that were updated may vary! This is not an indication
-    ```
-
-    ![Android Studio - Pull successful](../images/update/06_GitPullSuccess.png)
-
-* Gradle Sync will be running to download some dependencies. Wait until it is finished.
-
-    ![Android Studio - Gradle Sync](../images/studioSetup/40_BackgroundTasks.png)
-
-### Check JVM version
-
-This check is particularly indicated if you have already built a previous version of **AAPS** on the same computer.
-
-Check in the [Building Instructions](#Building-APK-recommended-specification-of-computer-for-building-apk-file) the required version for JVM, matching the **AAPS** version you are now building. Then follow the steps described at [Incompatible Gradle JVM](#incompatible-gradle-jvm) to make sure you currently use the correct version.
-
-(Update-to-new-version-build-the-signed-apk)=
-
-### Build the Signed APK
-
-Your sourcecode is now the current released version, and all prerequisites have been checked. It's time to build the signed apk as described in the [build signed apk section](#Building-APK-generate-signed-apk).
-
-(Update-to-new-version-transfer-and-install)=
-
-### Transfer and install the apk
-
-You need to transfer the apk to your phone so you can install it.
-
-```{note}
-If you completed the build with the same existing key store in Android Studio, then you do not need to remove the existing app on your phone. When you install the apk, follow the prompts to install updates.
-For other scenarios such as establishing a new key store in Android Studio for your signed apk, you will need to delete the old app before installing the apk. **Make sure to export your settings!**
-```
-
-See the instructions for [transferring and installing AAPS](../SettingUpAaps/TransferringAndInstallingAaps.md)
+Follow [these instructions.](./UpdateComputerBuild.md).
 
 (Update-to-new-version-check-aaps-version-on-phone)=
 
@@ -104,14 +27,4 @@ After you installed the new apk, you can check the AAPS version on your phone by
 
 ![Nainstalovaná verze AAPS](../images/Update_VersionCheck.png)
 
-Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
-
-## Troubleshooting
-
-If anything goes wrong, don't panic.
-
-Take a breath!
-
-Then see the separate page [troubleshooting Android Studio](../GettingHelp/TroubleshootingAndroidStudio) if your problem is already documented!
-
-If you need further help, please reach out to other **AAPS** users on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw).
+Check in the [Release Notes](../Maintenance/ReleaseNotes.md) if there are any specific instructions after update.
diff --git a/docs/CROWDIN/cs/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/cs/SettingUpAaps/BrowserBuild.md
@@ -1,3 +1,5 @@
+(browser-build)=
+
 # Browser build
 
 Building AAPS with GitHub Actions.

diff --git a/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server.png b/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server.png
diff --git a/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step1.png b/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step1.png
diff --git a/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step2.png b/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step2.png
diff --git a/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step3.png b/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step3.png
diff --git a/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step4.png b/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_step4.png
diff --git a/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_store.png b/docs/CROWDIN/cs/images/Building-the-App/CI/aaps_ci_simple_http_server_store.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubActions1.png b/docs/CROWDIN/cs/images/update/CI/GitHubActions1.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubActions2.png b/docs/CROWDIN/cs/images/update/CI/GitHubActions2.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubActions3.png b/docs/CROWDIN/cs/images/update/CI/GitHubActions3.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubActions4.png b/docs/CROWDIN/cs/images/update/CI/GitHubActions4.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubActions5.png b/docs/CROWDIN/cs/images/update/CI/GitHubActions5.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubUpdate1.png b/docs/CROWDIN/cs/images/update/CI/GitHubUpdate1.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubUpdate2.png b/docs/CROWDIN/cs/images/update/CI/GitHubUpdate2.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubUpdate3.png b/docs/CROWDIN/cs/images/update/CI/GitHubUpdate3.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubUpdate4.png b/docs/CROWDIN/cs/images/update/CI/GitHubUpdate4.png
diff --git a/docs/CROWDIN/cs/images/update/CI/GitHubUpdate5.png b/docs/CROWDIN/cs/images/update/CI/GitHubUpdate5.png
diff --git a/docs/CROWDIN/cs/index.md b/docs/CROWDIN/cs/index.md
@@ -2,10 +2,10 @@
 
 ![image](./images/basic-outline-of-AAPS.png)
 
-```{admonition} Version 3.3
+```{admonition} Latest Release
 :class: note
 
-29/12/2024 : Version 3.3 is out. Check the [Release Notes](#version3300) to see what's new and get update instructions.
+14/08/2025 : Version 3.3.2.1 is out. Check the [Release Notes](#latestrelease) to see what's new and get update instructions.
 
 ```
 
@@ -21,7 +21,7 @@ Section **2) Getting Started**, the [Introduction](Getting-Started/Introduction.
 
 Now that you have a solid understanding of the process, you can start assembling your **AAPS** loop.
 
-Section **3) Setting up AAPS** contains step-by-step instructions to do this. It covers choosing and [setting up your reporting server](./SettingUpAaps/SettingUpTheReportingServer.md) (Nightscout or Tidepool) so you can review and share your data, getting your computer ready for building the AAPS app, building the AAPS app and transferring the AAPS app to your phone. It also covers setting up the **AAPS** app using the setup Wizard, linking it with your CGM app, and either a real or virtual insulin pump, as well as linking **AAPS** to your reporting server. You are then slowly introduced to the full usage of what **AAPS** has to offer via a safe and carefully calibrated step-by-step process designed to make sure that you/your child are thoroughly familiar and comfortable navigating all the different levels and menu configurations before graduating on the next phase, commonly referred to as the next "Objective", until you are have enough experience to begin using the more advanced options available within the app. These Objectives are specially designed in such a way that will gradually unlock more possibilities of **AAPS** and switch from Open Loop to Closed Loop.
+Section **3) Setting up AAPS** contains step-by-step instructions to do this. It covers choosing and [setting up your reporting server](./SettingUpAaps/SettingUpTheReportingServer.md) (Nightscout or Tidepool) so you can review and share your data, getting ready for building the AAPS app, building the AAPS app and transferring the AAPS app to your phone. It also covers setting up the **AAPS** app using the setup Wizard, linking it with your CGM app, and either a real or virtual insulin pump, as well as linking **AAPS** to your reporting server. You are then slowly introduced to the full usage of what **AAPS** has to offer via a safe and carefully calibrated step-by-step process designed to make sure that you/your child are thoroughly familiar and comfortable navigating all the different levels and menu configurations before graduating on the next phase, commonly referred to as the next "Objective", until you are have enough experience to begin using the more advanced options available within the app. These Objectives are specially designed in such a way that will gradually unlock more possibilities of **AAPS** and switch from Open Loop to Closed Loop.
 
 Section **4) Daily life with AAPS** covers key **AAPS** features, to help you use (and customise)  **AAPS**. This including understanding the screens, carbs-on-board, sensitivity, profile switching, temp targets, extended carbs (or eCarbs), automations, and DynamicISF. It also covers frequent topics like how to manage different types of meals, how to deal with cannula and sensor changes, smartphone updates, daylight saving changes, and [travelling with AAPS](DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md) and sports. Common questions and answers are located within the troubleshooting section.
 

diff --git a/docs/CROWDIN/de/Maintenance/DocumentationUpdate.md b/docs/CROWDIN/de/Maintenance/DocumentationUpdate.md
@@ -4,7 +4,7 @@
 
 - Updated versions and Android Studio prerequisites
 - Added [3.3.2.1](#version3321) release, removed Android 16 references (fixed)
-- Added [Browser Build](browser-build) @Angus
+- Added [Browser Build](#browser-build) @Angus
 
 ## Mai 2025
 

diff --git a/docs/CROWDIN/de/Maintenance/ReleaseNotes.md b/docs/CROWDIN/de/Maintenance/ReleaseNotes.md
@@ -55,6 +55,8 @@ Damit Benutzer älterer Android-Versionen nicht ausgeschlossen werden, wurden zw
 WearOS 5, API Level 34 (Android 14) hat [einige Einschränkungen](#BuildingAapsWearOs-WearOS5).
 ```
 
+(latestrelease)=
+
 (version3321)=
 
 ## Version 3.3.2.1