diff --git a/docs/CROWDIN/cs/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/cs/CompatiblePumps/Future-possible-Pump-Drivers.md
index 8bd428f91272..0636b18426b3 100644
--- a/docs/CROWDIN/cs/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/cs/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ Zatímco v minulosti se společnost rozhodla nepovolit, aby bylo možné jejich
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardwarové požadavky na AAPS:** Žádné. It seems to be BT enabled.
diff --git a/docs/CROWDIN/cs/Getting-Started/Phones.md b/docs/CROWDIN/cs/Getting-Started/Phones.md
index 7c9cec4990cb..512ef799e323 100644
--- a/docs/CROWDIN/cs/Getting-Started/Phones.md
+++ b/docs/CROWDIN/cs/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Telefony
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/cs/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/cs/SettingUpAaps/BuildingAaps.md
index cc61c56db109..b39b71de212c 100644
--- a/docs/CROWDIN/cs/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/cs/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/de/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/de/CompatiblePumps/Future-possible-Pump-Drivers.md
index 24fe109e85e2..f74031ac65df 100644
--- a/docs/CROWDIN/de/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/de/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ Während das Unternehmen in der Vergangenheit entschieden hat, seine Pumpen nich
**Loop Status:** Alle drei Pumpen werden Loop Kandidaten sein.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware Voraussetzungen für AAPS:** Keine. It seems to be BT enabled.
diff --git a/docs/CROWDIN/de/Getting-Started/Phones.md b/docs/CROWDIN/de/Getting-Started/Phones.md
index 54e7219e5e22..f426601a2911 100644
--- a/docs/CROWDIN/de/Getting-Started/Phones.md
+++ b/docs/CROWDIN/de/Getting-Started/Phones.md
@@ -1,8 +1,16 @@
# Smartphones
-Die aktuelle **AAPS**-Version (3.3) setzt ein Android Smartphone mit Google **Android 11.0 oder höher** voraus. Wenn Du planst Dir (ab Dezember 2024) ein neues Smartphone zuzulegen, wäre Android 14 eine gute Wahl.
-Im November 2024 sind Probleme mit Android 15 und der Bluetooth-Konnektivität gemeldet worden. Eventuell macht es Sinn, das Update auf Android 15 zu verschieben, insbesondere dann, wenn Du den Omnipod Dash oder den Dexcom G7 nutzt. Die neuesten Informationen zu diesem Thema findest Du auf [Facebook oder Discord](../GettingHelp/WhereCanIGetHelp.md).
-Aus Sicherheitsgründen wird Dir dringend ans Herz gelegt, Dein **AAPS** auf dem neuesten Stand zu halten. Für Menschen, die kein Gerät mit Android 11 (oder neuer) nutzen können, stehen weiterhin ältere **AAPS**-Versionen für ältere Android-Versionen zur Verfügung, siehe dazu auch die [Release Notes](#maintenance-android-version-aaps-version).
+Die aktuelle **AAPS**-Version (3.3) setzt ein Android Smartphone mit Google **Android 11.0 oder höher** voraus. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
+Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. Für Menschen, die kein Gerät mit Android 11 (oder neuer) nutzen können, stehen weiterhin ältere **AAPS**-Versionen für ältere Android-Versionen zur Verfügung, siehe dazu auch die [Release Notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Einstellungen](../CompatiblePhones/Jelly.md)
- [Huawei Einstellungen](../CompatiblePhones/Huawei.md)
diff --git a/docs/CROWDIN/de/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/de/SettingUpAaps/BuildingAaps.md
index 0d02700d5919..70fd447e1918 100644
--- a/docs/CROWDIN/de/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/de/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Installiere Android Studio, indem Du, wie in den folgenden Screenshots gezeigt,
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/el/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/el/CompatiblePumps/Future-possible-Pump-Drivers.md
index 829ddba51509..d7d5b50c8880 100644
--- a/docs/CROWDIN/el/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/el/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/el/Getting-Started/Phones.md b/docs/CROWDIN/el/Getting-Started/Phones.md
index e59d2b1745b9..41a80e6b608c 100644
--- a/docs/CROWDIN/el/Getting-Started/Phones.md
+++ b/docs/CROWDIN/el/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Τηλέφωνα
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/el/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/el/SettingUpAaps/BuildingAaps.md
index 6939066a4bfa..ab9ee72b5ea0 100644
--- a/docs/CROWDIN/el/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/el/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/es/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/es/CompatiblePumps/Future-possible-Pump-Drivers.md
index a612b1b1fdc3..4cdc047cfc07 100644
--- a/docs/CROWDIN/es/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/es/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/es/Getting-Started/Phones.md b/docs/CROWDIN/es/Getting-Started/Phones.md
index 3a3c984e3ece..0aa2b6e9bb3c 100644
--- a/docs/CROWDIN/es/Getting-Started/Phones.md
+++ b/docs/CROWDIN/es/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Teléfonos
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/es/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/es/SettingUpAaps/BuildingAaps.md
index f711b48f12e4..098ac8b2cb57 100644
--- a/docs/CROWDIN/es/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/es/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/fr/AdvancedOptions/Autotune.md b/docs/CROWDIN/fr/AdvancedOptions/Autotune.md
index 815fc3028fd6..a7fee37d12a8 100644
--- a/docs/CROWDIN/fr/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/fr/AdvancedOptions/Autotune.md
@@ -1,12 +1,12 @@
# Comment utiliser le plugin Autotune (dev uniquement)
-Documentation about Autotune algorithm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html).
+La documentation sur l'algorithme Autotune peut être trouvée dans la [documentation OpenAPS](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html).
-Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
+Le plugin Autotune est une implémentation de l'algorithme autotune OpenAPS dans AAPS.
**Actuellement, le plugin Autotune n'est disponible que dans la [branche dev](../AdvancedOptions/DevBranch.md) et avec le mode Ingénierie.**
-
+
## Interface utilisateur Autotune
@@ -18,7 +18,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- Remarque : chaque fois que vous changez le paramètre Nb jours, les résultats précédents seront supprimés
- Dernier run affiche la date du dernier calcul et permet d'afficher votre dernier calcul valide. Si vous n'avez pas lancé Autotune le jour en cours, ou si les résultats précédents ont été supprimés avec une modification du paramètre de calcul ci-dessus, vous pouvez alors récupérer les paramètres et les résultats de la dernière exécution réussie.
- L'avertissement vous montre par exemple des informations sur le profil sélectionné (si vous avez plusieurs valeurs G/I ou plusieurs valeurs SI)
- - Remarque : Le calcul Autotune fonctionne avec une seule valeur de G/I et une seule valeur de SI. There is currently no existing Autotune algorithm to tune a circadian IC or circadian ISF. Si votre profil d'entrée a plusieurs valeurs, vous pouvez voir dans la section Avertissement la valeur moyenne prise en compte pour calculer votre profil.
+ - Remarque : Le calcul Autotune fonctionne avec une seule valeur de G/I et une seule valeur de SI. Il n'existe actuellement aucun algorithme Autotune pour ajuster un G/I circadien ou une SI circadienne. Si votre profil d'entrée a plusieurs valeurs, vous pouvez voir dans la section Avertissement la valeur moyenne prise en compte pour calculer votre profil.
- Le bouton Vérifiez Profil d'entrée permet d'ouvrir la Visionneuse de Profil pour vous permettre de faire une vérification rapide de votre profil (unités, DAI, G/I, SI, basal et cible)
- Remarque : Autotune ne réglera que le G/I (valeur unique), la SI (valeur unique) et les débits de basal (avec variation circadienne). Les unités, la DAI et les cibles resteront inchangées dans le profil de sortie.
@@ -87,16 +87,16 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- Changer le profil avec l'Automatisation (Désactivé par défaut) : voir [Exécuter Autotune avec une règle d'automatisation](#run-autotune-with-an-automation-rule) ci-dessous. Si vous activez ce paramètre, le profil d'entrée sera automatiquement mis à jour par le profil Tuned, et il sera activé.
- - **Be Careful, you must trust and verify during several following days, that after an update and activation of Tuned profile without modification, it improves your loop**
+ - **Soyez prudent, vous devez prendre confiance en vérifiant pendant plusieurs jours qu'après une mise à jour et l'activation du profil Tuned sans aucune modification, cela améliore effectivement votre boucle**
- Catégoriser UAM comme basal (par défaut On) : Ce paramètre est pour les utilisateurs utilisant AndroidAPS sans aucun glucide entré (Full UAM). Il empêchera (quand désactivé) de catégoriser les RNS en tant que basal.
- Remarque : si vous avez au moins une heure d'absorption de glucides détectée pendant une journée, alors toutes les données catégorisées comme "RNS" seront catégorisées en tant que basal, quel que soit ce paramètre (Activé ou Désactivé)
- Nombre de jours de données (par défaut 5) : Vous pouvez définir la valeur par défaut avec ce paramètre. À chaque fois que vous sélectionnez un nouveau profil dans le plugin Autotune, le nombre de jours sera remplacé par cette valeur par défaut
-- Apply average result in circadian IC/ISF (default Off): see [Circadian IC or ISF profile](#circadian-ic-or-isf-profile) below.
+- Appliquer le résultat moyen dans les G/I & SI circadienne (Désactivation par défaut) : voir [Profil avec G/I ou SI Circadiens](#circadian-ic-or-isf-profile) ci-dessous.
### Other settings
-- Autotune also uses Max autosens ratio and Min autosens ratio to limit variation. Vous pouvez voir et ajuster ces valeurs dans Configuration > Plugin Sensitivité > Paramètres > Paramètres Avancés
+- Autotune utilise également les ratio Max et Min Autosens pour limiter la variation. Vous pouvez voir et ajuster ces valeurs dans Configuration > Plugin Sensitivité > Paramètres > Paramètres Avancés
@@ -108,7 +108,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
### Profil avec G/I ou SI Circadiens
-- If you have important variation of IC and/or you ISF in your profile, and you fully trust in your circadian time and variation, then you can set "Apply average result in circadian IC/ISF"
+- Si vous avez des variations importantes de G/I et/ou de votre SI dans votre profil, et si vous avez entièrement confiance en vos heures et variations circadiens, alors vous pouvez définir "Appliquer le résultat G/I et SI moyen sur le profil circadien"
- Notez que le calcul Autotune sera toujours fait avec une seule valeur, et que la variation circadienne ne sera pas ajustée par Autotune. Ce paramètre n'applique que la variation moyenne calculée pour le G/I et/ou la SI sur vos valeurs circadiennes
@@ -118,15 +118,15 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-### Tune specific days of the week
+### Ajuster des jours spécifiques de la semaine
-- If you click on the checkbox with the eye on the right of "Rune days" parameter, you will see the day selection. You can specify which day of the week should be included in Autotune calculation (in screenshot below you can see an example for "working days" with Saturday and Sunday removed from autotune calculation)
- - If the number of day included in Autotune calculation is lower than the number of Tune days, then you will see how many days will be included on the right of Tune days selector (10 days in the example below)
- - This setting gives good results only if the number of remaining days is not to small (for example if you Tune a specific profile for week end days with only Sunday and Saturday selected, you should select a minimum of 21 or 28 Tune days to have 6 or 8 days included in Autotune calculation)
+- Si vous cliquez sur la case à cocher avec l'œil à droite du paramètre "Nb jours", vous verrez la sélection du jour. Vous pouvez spécifier quels jours de la semaine doivent être inclus dans le calcul Autotune (en capture d'écran ci-dessous, vous pouvez voir un exemple pour les "jours de travail" avec le samedi et le dimanche enlevé du calcul Autotune)
+ - Si le nombre de jours inclus dans le calcul Autotune est inférieur au nombre de jours sélectionnés, alors vous verrez combien de jours seront inclus dans le calcul à droite du sélecteur de jours (10 jours dans l'exemple ci-dessous)
+ - Ce paramètre ne donne de bons résultats que si le nombre de jours restants n'est pas trop petit (par exemple si vous ajustez un profil spécifique pour les jours du week-end avec seulement le dimanche et le samedi sélectionnés, vous devez sélectionner un minimum de 21 ou 28 jours de Tune pour avoir 6 ou 8 jours inclus dans le calcul Autotune)
-- During Autotune calculation, you can see the progress of the calculations ("Partial result day 3 / 10 tuned" on example below)
+- Lors du calcul Autotune, vous pouvez voir la progression des calculs ("Résultat partiel jour 3 / 10 calculé" dans l'exemple ci-dessous)
@@ -138,9 +138,9 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
La première étape est de définir le déclencheur correct pour une règle d'automatisation avec Autotune :
-Note: for more information on how to set an automation rule, see [here](../DailyLifeWithAaps/Automations.md).
+Remarque : pour plus d'informations sur la façon de définir une règle d'automatisation, voir [ici](../DailyLifeWithAaps/Automations.md).
-- You should select Recurring time trigger: only run Autotune once per day, and autotune is designed to be run daily (each new run you shift one day later and quickly profile modification should be tiny)
+- Vous devez sélectionner le déclencheur Période répétitive : il ne faut exécuter Autotune au maximum qu'une seule fois par jour, Autotune est conçu pour être exécuté tous les jours (à chaque nouvelle exécution, vous décalez la période de calcul d'un jour et rapidement les modifications du profil devrait être très faibles)
@@ -156,11 +156,11 @@ Note: for more information on how to set an automation rule, see [here](../Daily
-- After a few days, if you fully trust Autotune results and percentage of modification is low, you can modify [Autotune settings](#autotune-plugin-settings) "Automation Switch Profile" to enabled to automatically update and activate profile tuned after calculation.
+- Après quelques jours, si vous faites entièrement confiance aux résultats Autotune et si le pourcentage de modification est faible, vous pouvez modifier les [Paramètres Autotune](#autotune-plugin-settings) "Changer le Profil avec l'automatisation" pour l'activer, cela mettre à jour le profil et l'activera automatiquement après le calcul.
-Note: if you want to automatically tune profiles for specific days of the week (for example a profile for "Weekend days" and another one for "Working days"), then create one rule for each profile, select the same days in Trigger and in Autotune Action, Tune days must be high enough to be sure tuning will be done with at least 6 or 8 days, and don't forget to select time after 4AM in trigger...
+Remarque : si vous souhaitez modifier automatiquement les profils pour des jours spécifiques de la semaine (par exemple un profil pour "jours de fin de semaine" et un autre pour "jours ouvrables"), puis créez une règle pour chaque profil, sélectionnez les mêmes jours dans le déclencheur et dans l'action Autotune, Le réglage des jours doit être assez élevé pour être sûr que le réglage sera fait avec au moins 6 ou 8 jours, et n'oubliez pas de sélectionner l'heure après 4AM dans le déclencheur...
-- See below an example of rule to tune "my profile" on all "Working days" with 14 Tune days selected (so only 10 days included in autotune calculation).
+- Voir ci-dessous un exemple de règle pour régler "mon profil" sur tous les "jours de travail" avec 14 jours de travail sélectionnés (donc seulement 10 jours inclus dans le calcul autotune).
@@ -172,13 +172,13 @@ Autotune fonctionne avec les informations existantes dans votre base de données
Autotune n'est qu'une aide, il est important de vérifier régulièrement si vous êtes d'accord avec le profil calculé. Si vous avez le moindre doute, modifiez les paramètres Autotune (par exemple le nombre de jours) ou copiez les résultats dans le profil local et ajustez le profil avant de l'utiliser.
-Always use Autotune several days manually to check results before applying them. Et ce n'est que lorsque vous faites entièrement confiance aux résultats Autotune et quand la variation devient très faible entre le profil précédent et le profil calculé que vous pouvez commencer à utiliser l'automatisation (jamais avant)
+Utilisez toujours Autotune plusieurs jours manuellement pour vérifier les résultats avant de les appliquer. Et ce n'est que lorsque vous faites entièrement confiance aux résultats Autotune et quand la variation devient très faible entre le profil précédent et le profil calculé que vous pouvez commencer à utiliser l'automatisation (jamais avant)
- Autotune peut très bien fonctionner pour certains utilisateurs et pas du tout pour d'autres, donc **Si vous ne faites pas confiance au résultat Autotune, ne l'utilisez pas**
Il est également important d'analyser les résultats d'Autotune pour comprendre (ou essayer de comprendre) pourquoi Autotune propose ces modifications
-- vous pouvez avoir une augmentation ou une diminution de la globalité du profil (par exemple une augmentation du débit de basal total associé à la diminution des valeurs de la SI et du G/I). it could be associated to several following days with autosens correction above 100% (more aggressivity required) or below 100% (you are more sensitive)
+- vous pouvez avoir une augmentation ou une diminution de la globalité du profil (par exemple une augmentation du débit de basal total associé à la diminution des valeurs de la SI et du G/I). il pourrait être associé à plusieurs jours successifs avec correction autosens supérieure à 100% (plus d'agressivité requise) ou inférieure à 100% (vous êtes plus sensible)
- Parfois, Autotune propose un équilibre différent entre les taux de basal et la SI et G/I (ex basal inférieur et SI / G/I plus agressifs)
Nous recommandons de ne pas utiliser Autotune dans les cas suivants :
@@ -190,7 +190,7 @@ Nous recommandons de ne pas utiliser Autotune dans les cas suivants :
- Toutes les périodes RNS (sauf si vous n'entrez jamais vos glucides dans AAPS et que le paramètre Categoriser UAM en tant que basal est désactivé) seront catégorisées en basal, cela peut augmenter beaucoup votre Basal (beaucoup plus que nécessaire).
- L'absorption des glucides est très lente : si la plupart de vos glucides sont calculés avec un paramètre min_5m_carbimpact (vous pouvez voir ces périodes avec un petit point orange en haut de la courbe), le calcul des GA pourrait être erroné et conduire à de mauvais résultats.
- - When you practice sport, you are generally more sensitive and your BG doesn't rise a lot, so during or after an exercise, it's usual to see some periods with slow carbs. Mais si vous avez trop souvent une absorption lente inattendue des glucides, alors vous aurez besoin d'un ajustement de profil (valeur plus élevée de G/I) ou d'un min_5m_carbimpact un peu plus élevé.
-- Vous avez un "très mauvais jours", par exemple coincé plusieurs heures en hyperglycémie avec une énorme quantité d'insuline pour pouvoir descendre à l'intérieur de la cible, ou après un changement de capteur, vous avez obtenu de longues périodes avec des glycémies erronées. If during the pas weeks you only have one or 2 "bad days", you can disable manually these days in autotune calculation to exclude them from calculation, and again **check carefully if you can trust the results**
+ - Quand vous faites du sport, vous êtes généralement plus sensible et votre glycémie ne monte pas beaucoup, donc pendant ou après un exercice, il est habituel de voir quelques périodes avec des glucides lents. Mais si vous avez trop souvent une absorption lente inattendue des glucides, alors vous aurez besoin d'un ajustement de profil (valeur plus élevée de G/I) ou d'un min_5m_carbimpact un peu plus élevé.
+- Vous avez un "très mauvais jours", par exemple coincé plusieurs heures en hyperglycémie avec une énorme quantité d'insuline pour pouvoir descendre à l'intérieur de la cible, ou après un changement de capteur, vous avez obtenu de longues périodes avec des glycémies erronées. Si pendant les précédentes semaines vous avez seulement un ou deux "mauvais jours", vous pouvez désactiver manuellement ces jours dans le calcul automatique pour les exclure du calcul, et à nouveau **vérifiez soigneusement si vous pouvez faire confiance aux résultats**
- Si le pourcentage de modification est trop important
- Vous pouvez essayer d'augmenter le nombre de jours pour obtenir des résultats plus lisses
\ No newline at end of file
diff --git a/docs/CROWDIN/fr/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/fr/CompatiblePumps/Future-possible-Pump-Drivers.md
index 8bc02c1fdbc0..59fac8aa1ae5 100644
--- a/docs/CROWDIN/fr/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/fr/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/fr/Getting-Started/Phones.md b/docs/CROWDIN/fr/Getting-Started/Phones.md
index 3f0dc59e9696..c8f01a18caf4 100644
--- a/docs/CROWDIN/fr/Getting-Started/Phones.md
+++ b/docs/CROWDIN/fr/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Téléphones
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Paramètres Jelly Pro](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/fr/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/fr/SettingUpAaps/BuildingAaps.md
index 0d9ff08d57dd..e65bbec00129 100644
--- a/docs/CROWDIN/fr/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/fr/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/fr/WearOS/WearOsSmartwatch.md b/docs/CROWDIN/fr/WearOS/WearOsSmartwatch.md
index d745f6424219..0096663b3f6f 100644
--- a/docs/CROWDIN/fr/WearOS/WearOsSmartwatch.md
+++ b/docs/CROWDIN/fr/WearOS/WearOsSmartwatch.md
@@ -1,52 +1,52 @@
-# Setup AAPS on your Wear OS watch
+# Configurer AAPS sur votre montre Wear OS
-The instructions below apply to the **AAPS Wear** apk that you need to build (see [here](../WearOS/BuildingAapsWearOS.md) if you haven't yet) as you've built the phone **AAPS** apk.
+Les instructions ci-dessous s'appliquent à l'apk **AAPS Wear** que vous devez construire (voir [ici](../WearOS/BuildingAapsWearOS.md) si vous ne l'avez pas encore fait) car vous avez construit l'apk **AAPS** du téléphone.
-You can also use some of the information for the **AAPSClient** and **PumpControl** **Wear** apk that are directly available in [GitHub](https://github.com/nightscout/AndroidAPS/releases/tag/3.2.0.4). Each **Wear** app will communicate with its matching phone app. For example: the **AAPSClient Wear** app can be used to display **AAPSClient** data and not **AAPS** data.
+Vous pouvez également utiliser certaines informations pour l'apk **AAPSClient** et **PumpControl** **Wear** qui sont directement disponibles dans [GitHub](https://github.com/nightscout/AndroidAPS/releases/tag/3.2.0.4). Chaque application **Wear** ne communiquera qu'avec son application de téléphone correspondante. Par exemple : l'application **AAPSClient Wear** ne peut être utilisée que pour afficher les données de **AAPSClient** et pas celles d'**AAPS**.
-## Wear OS Versions and compatibility
+## Versions Wear OS et compatibilité
### Wear OS 3
-Install the **AAPS Wear** apk using [Wear Installer 2](https://youtu.be/abgN4jQqHb0?si=5L7WUeYMSd_8IdPV), Easy Fire Tools (described below) or ADB.
-No limitation in **AAPS Wear** operations.
+Installez l'apk **AAPS Wear** en utilisant [Wear Installer 2](https://youtu.be/abgN4jQqHb0?si=5L7WUeYMSd_8IdPV), Easy Fire Tools (décrit ci-dessous) ou ADB.
+Aucune limitation dans les opérations **AAPS Wear**.
(BuildingAapsWearOs-WearOS5)=
-### Wear OS 4 and Galaxy watch updated to Wear OS 5
+### Wear OS 4 et montres Galaxy mises à jour vers Wear OS 5
-Example: GW4, GW5, GW6
+Par example: GW4, GW5, GW6
-Install the **AAPS Wear** apk using [Wear Installer 2](https://youtu.be/abgN4jQqHb0?si=5L7WUeYMSd_8IdPV).
-No limitation in **AAPS Wear** operations.
+Installez l'apk **AAPS Wear** en utilisant [Wear Installer 2](https://youtu.be/abgN4jQqHb0?si=5L7WUeYMSd_8IdPV), Easy Fire Tools (décrit ci-dessous) ou ADB.
+Aucune limitation dans les opérations **AAPS Wear**.
```{admonition} Android Wear OS 5
:class: warning
-**FIRMWARE UPDATES WILL MOST PROBABLY BREAK AAPS WATCHFACES: DISABLE WATCH UPDATES**.
+**LES MISES A JOUR FUTURES DE FIRMWARE RISQUENT PROBABLEMENT DE SUPPRIMER LA COMPATIBILITE DES CADRANS AAPS : DESACTIVEZ LES MISES A JOUR DE LA MONTRE**.
```
-### Galaxy watch with factory installed Wear OS 5
+### Montres Galaxy avec installation usine Wear OS 5 ou supérieures
- Example: GW7, GW Ultra
+ Par example: GW7, GW Ultra
```{admonition} Android Wear OS 5
:class: warning
-Installing the AAPS Watch Face has to be done with [Wear Installer 2](https://www.youtube.com/watch?v=yef_qGvcCnk) after installing the Wear app.
-Accidental change of the Watch Face to another one requires the procedure above to be repeated.
-Changing the dedicated Watch Face parameters like: Dark, Watchdivider, etc. is not possible.
-**FIRMWARE UPDATES WILL MOST PROBABLY BREAK AAPS WATCHFACES: DISABLE WATCH UPDATES**.
+L'installation des cadrans AAPS doit être effectué avec [Wear Installer 2](https://www.youtube.com/watch?v=yef_qGvcCnk) après avoir installé l'application sur la montre.
+Un changement accidentel du cadran AAPS vers un autres cadran nécessitera de refaire la procédure d'installation ci-dessous.
+Le changement des paramètres spécifiques des cadrans comme : SombreDark, Séparateur Invisible, etc. n'est possible que via l'application AAPS montre.
+**LA MISE A JOUR DES FIRMWARE SUPPRIMERA LA COMPATIBILITE AVEC LES CADRANS AAPS : DESACTIVEZ LES MISES A JOUR DE LA MONTRE**.
```
-Consider alternatively [GlucoDataHandler](https://play.google.com/store/apps/details?id=de.michelinside.glucodatahandler) with a complication.
+Envisagez alternativement [GlucoDataHandler](https://play.google.com/store/apps/details?id=de.michelinside.glucodatahandler) avec une complication.
-### Pixel watch with Wear OS 5
+### Montre Pixel avec Wear OS 5
-Not compatible with the AAPS watchface.
-Consider [GlucoDataHandler](https://play.google.com/store/apps/details?id=de.michelinside.glucodatahandler) with a complication.
+Non compatible avec les cadrans AAPS.
+Considérez [GlucoDataHandler](https://play.google.com/store/apps/details?id=de.michelinside.glucodatahandler) avec une complication.
-## How to set up a Samsung Galaxy 4 smartwatch with **AAPS**
+## Comment configurer une SmartWatch Samsung Galaxy 4 avec **AAPS**
-This section assumes you are totally new to Smartwatches, and gives you basic orientation of a popular watch, the **Galaxy Watch 4**, followed by a step-by-step guide to setup **AAPS** on the watch.
+Cette section suppose que vous êtes totalement nouveau dans les Smartwatches, et vous donne l'orientation de base d'une montre classique, la **Galaxy Watch 4**, suivi d'un guide étape par étape pour configurer **AAPS** sur la montre.
_This guide assumes the Samsung Galaxy watch you are setting up is running Wear OS version 3 or lower._ If you are setting up a watch running Wear OS 4/OneUI 5 or later, you will need to use a new ADB pairing process, this is explained in the Samsung software on your phone and will be updated here in due course.
@@ -193,48 +193,48 @@ More troubleshooting tips can be found [here](https://freepoc.org/wear-installer
(WearOS_changing-to-AAPS-watchface)=
-## Changing to an AAPS Watchface on your WearOS watch
+## Sélectionnez un cadran AAPS sur votre montre WearOS
-There are a number of watchfaces available in the standard build of the AAPS Wear OS APK build. Once you have installed the AAPS Wear APK on your watch, they will be available. Here are the steps for selecting one:
+Il existe plusieurs cadrans de montre disponibles dans la version standard de l'APK AAPS pour Wear OS. Une fois que vous avez installé l'APK AAPS Wear sur votre montre, ils seront disponibles. Voici les étapes pour en sélectionner un :
-1. On your watch (assuming WearOS), long press on your current watchface to bring up the watchface selector screen and scroll all the way to the right until you see the "Add Watch Face" button and select it
+1. Sur votre montre (WearOS uniquement), appuyez longuement sur votre cadran actuel pour faire apparaître l'écran de sélection du cadran et faites défiler complètement vers la droite jusqu'à ce que vous voyiez le bouton "Ajouter un cadran de montre" et sélectionnez-le
-2. Scroll to the bottom of the list until you see the "Downloaded" section and find "AAPS (Custom)" and click the middle of the image to add it to your shortlist of current watchfaces. Don't worry about the current appearance of the "AAPS (Custom)" watchface, we will select your preferred skin in the next step.
+2. Faites défiler vers le bas de la liste jusqu'à ce que vous voyez la section "Téléchargées" et trouvez "AAPS (Perso)" et cliquez sur le milieu de l'image pour l'ajouter à votre shortlist de cadrans. Ne vous inquiétez pas de l'apparence actuelle de la montre "AAPS (Perso)", nous sélectionnerons votre skin préféré à l'étape suivante.
-3. Now open AAPS on your phone and go to the Wear plugin (enable it in Config Builder (under Synchronization) if you don't see it in your current plugins along the top).
+3. Maintenant, ouvrez AAPS sur votre téléphone et allez au plugin Wear (activez-le dans la Configuration (dans le bloc Synchronisation) si vous ne le voyez pas dans vos plugins actuels en haut).
-4. Click on the "Load Watchface" button and select the watchface that you like
+4. Cliquez sur le bouton « Charger le Cadran » et sélectionnez le cadran que vous voulez
-5. Check your watch, the "AAPS (Custom)" watchface should now be displaying the skin that you have selected. Give it a few seconds to refresh. You may now customize the complications, etc. by long pressing the watchface and then pressing the "Customize" button on the watchface image.
+5. Vérifiez sur votre montre, le cadran de "AAPS (Perso)" devrait maintenant afficher l'apparence que vous avez sélectionnée. Attendre quelques secondes si nécessaire. You may now customize the complications, etc. by long pressing the watchface and then pressing the "Customize" button on the watchface image.
-## AAPSv2 watchface - Legend
+## Cadran AAPS v2 - Légende
-
+
-A - time since last loop run
+A - temps écoulé depuis le dernier calcul de la boucle
-B - CGM reading
+B - lecture du capteur MGC
-C - minutes since last CGM reading
+C - nombre de minutes depuis la dernière lecture MGC
-D - change compared to last CGM reading (in mmol or mg/dl)
+D - changement par rapport à la dernière lecture MGC (en mmol ou mg/dl)
-E - average change CGM reading last 15 minutes
+E - variation moyenne des lectures MGC depuis 15 minutes
-F - phone battery
+F - niveau de batterie du téléphone
-G - basal rate (shown in U/h during standard rate and in % during TBR)
+G - débits de basal (en U/h ou en % pendant un DBT)
H - BGI (blood glucose interaction) -> the degree to which BG “should” be rising or falling based on insulin activity alone.
-I - carbs (carbs on board | e-carbs in the future)
+I - glucides (glucides actifs | e-glucides à venir)
-J - insulin on board (from bolus | from basal)
\ No newline at end of file
+J - Insuline Active (bolus | basal)
\ No newline at end of file
diff --git a/docs/CROWDIN/fr/index.md b/docs/CROWDIN/fr/index.md
index 5b613cfece7c..c9d10b8b1c79 100644
--- a/docs/CROWDIN/fr/index.md
+++ b/docs/CROWDIN/fr/index.md
@@ -5,7 +5,7 @@
```{admonition} Version 3.3
:class: note
-29/12/2024 : Version 3.3 is out. Check the [Release Notes](#version3300) to see what's new and get update instructions.
+29/12/2024 : La version 3.3 est sortie. Consultez les [Notes de version] (#version3300) pour voir ce qui est nouveau et obtenir des instructions de mise à jour.
```
@@ -66,10 +66,10 @@ Toutes les informations et le code décrits ici le sont à des fins d'informatio
## Index de la documentation AAPS
```{toctree}
-:caption: 1) Change language
+:caption: 1) Changer la langue
-Change language <./NavigateDoc/ChangeLanguage.md>
-Change version <./NavigateDoc/ChangeVersion.md>
+Changer la langue <./NavigateDoc/ChangeLanguage.md>
+Changer la version <./NavigateDoc/ChangeVersion.md>
```
```{toctree}
:caption: 2) Démarrage
diff --git a/docs/CROWDIN/he/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/he/CompatiblePumps/Future-possible-Pump-Drivers.md
index c4ea3879f67f..4d2273f6121d 100644
--- a/docs/CROWDIN/he/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/he/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/he/Getting-Started/Phones.md b/docs/CROWDIN/he/Getting-Started/Phones.md
index c026f43a3c26..9b65f5ff3515 100644
--- a/docs/CROWDIN/he/Getting-Started/Phones.md
+++ b/docs/CROWDIN/he/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# טלפונים
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [הגדרות Jelly Pro](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/he/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/he/SettingUpAaps/BuildingAaps.md
index cecbaa1937f2..b1ba920a9caf 100644
--- a/docs/CROWDIN/he/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/he/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/ko/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/ko/CompatiblePumps/Future-possible-Pump-Drivers.md
index fa9e8688f91b..ec6a27c2e61f 100644
--- a/docs/CROWDIN/ko/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/ko/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/ko/Getting-Started/Phones.md b/docs/CROWDIN/ko/Getting-Started/Phones.md
index 80277dd9efa0..8584283e09f3 100644
--- a/docs/CROWDIN/ko/Getting-Started/Phones.md
+++ b/docs/CROWDIN/ko/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# 스마트폰
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/ko/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/ko/SettingUpAaps/BuildingAaps.md
index 2345642e4309..1da17f92852f 100644
--- a/docs/CROWDIN/ko/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/ko/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/lt/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/lt/CompatiblePumps/Future-possible-Pump-Drivers.md
index c4ea3879f67f..4d2273f6121d 100644
--- a/docs/CROWDIN/lt/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/lt/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/lt/Getting-Started/Phones.md b/docs/CROWDIN/lt/Getting-Started/Phones.md
index 8a02f6019396..3ee61ed987b4 100644
--- a/docs/CROWDIN/lt/Getting-Started/Phones.md
+++ b/docs/CROWDIN/lt/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Telefonai
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/lt/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/lt/SettingUpAaps/BuildingAaps.md
index b5c53e09df74..a8c790468a23 100644
--- a/docs/CROWDIN/lt/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/lt/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/nl/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/nl/CompatiblePumps/Future-possible-Pump-Drivers.md
index e37cc17a7aa8..9d289552216e 100644
--- a/docs/CROWDIN/nl/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/nl/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/nl/Getting-Started/Phones.md b/docs/CROWDIN/nl/Getting-Started/Phones.md
index 24b3134de72a..137e4d1ecac9 100644
--- a/docs/CROWDIN/nl/Getting-Started/Phones.md
+++ b/docs/CROWDIN/nl/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Telefoons
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/nl/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/nl/SettingUpAaps/BuildingAaps.md
index ab6e03c5d4ba..e90d500793b4 100644
--- a/docs/CROWDIN/nl/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/nl/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/pb/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/pb/CompatiblePumps/Future-possible-Pump-Drivers.md
index c4ea3879f67f..4d2273f6121d 100644
--- a/docs/CROWDIN/pb/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/pb/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/pb/Getting-Started/Phones.md b/docs/CROWDIN/pb/Getting-Started/Phones.md
index c0a4fc12adc7..0d547e1c7eba 100644
--- a/docs/CROWDIN/pb/Getting-Started/Phones.md
+++ b/docs/CROWDIN/pb/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Phones
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/pb/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/pb/SettingUpAaps/BuildingAaps.md
index 93fd3d8f8f17..55e0c7feda23 100644
--- a/docs/CROWDIN/pb/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/pb/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/pl/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/pl/CompatiblePumps/Future-possible-Pump-Drivers.md
index d3a04d6a216b..bc49d0a64448 100644
--- a/docs/CROWDIN/pl/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/pl/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/pl/Getting-Started/Phones.md b/docs/CROWDIN/pl/Getting-Started/Phones.md
index d54c6a59c280..6e52535ea1a6 100644
--- a/docs/CROWDIN/pl/Getting-Started/Phones.md
+++ b/docs/CROWDIN/pl/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Telefony
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/pl/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/pl/SettingUpAaps/BuildingAaps.md
index 93fd3d8f8f17..55e0c7feda23 100644
--- a/docs/CROWDIN/pl/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/pl/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/pt/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/pt/CompatiblePumps/Future-possible-Pump-Drivers.md
index c4ea3879f67f..4d2273f6121d 100644
--- a/docs/CROWDIN/pt/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/pt/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/pt/Getting-Started/Phones.md b/docs/CROWDIN/pt/Getting-Started/Phones.md
index 17ec36ad8647..a5bb663e4ad5 100644
--- a/docs/CROWDIN/pt/Getting-Started/Phones.md
+++ b/docs/CROWDIN/pt/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Telefones
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/pt/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/pt/SettingUpAaps/BuildingAaps.md
index bb20927ddca9..6c54e44a21be 100644
--- a/docs/CROWDIN/pt/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/pt/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/ro/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/ro/CompatiblePumps/Future-possible-Pump-Drivers.md
index fab76d51af53..0daf2a306f75 100644
--- a/docs/CROWDIN/ro/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/ro/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/ro/Getting-Started/Phones.md b/docs/CROWDIN/ro/Getting-Started/Phones.md
index e8e5fb0eff5c..2374ff122069 100644
--- a/docs/CROWDIN/ro/Getting-Started/Phones.md
+++ b/docs/CROWDIN/ro/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Telefoane
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/ro/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/ro/SettingUpAaps/BuildingAaps.md
index 93fd3d8f8f17..55e0c7feda23 100644
--- a/docs/CROWDIN/ro/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/ro/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/ru/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/ru/CompatiblePumps/Future-possible-Pump-Drivers.md
index 84941db4bc5c..674b616a5540 100644
--- a/docs/CROWDIN/ru/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/ru/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ orphan: true
**Статус реализации:** Все 3 помпы будут кандидатами в ИПЖ.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Требования к оборудованию для AAPS:** Никаких. It seems to be BT enabled.
diff --git a/docs/CROWDIN/ru/Getting-Started/Phones.md b/docs/CROWDIN/ru/Getting-Started/Phones.md
index cc5775cfc32e..35de065c3cf8 100644
--- a/docs/CROWDIN/ru/Getting-Started/Phones.md
+++ b/docs/CROWDIN/ru/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Телефоны
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Настройки Jelly Pro](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/ru/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/ru/SettingUpAaps/BuildingAaps.md
index e3a4b48df130..afd6b701dbd3 100644
--- a/docs/CROWDIN/ru/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/ru/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/sk/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/sk/CompatiblePumps/Future-possible-Pump-Drivers.md
index c4ea3879f67f..4d2273f6121d 100644
--- a/docs/CROWDIN/sk/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/sk/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/sk/Getting-Started/Phones.md b/docs/CROWDIN/sk/Getting-Started/Phones.md
index c0a4fc12adc7..0d547e1c7eba 100644
--- a/docs/CROWDIN/sk/Getting-Started/Phones.md
+++ b/docs/CROWDIN/sk/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Phones
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Settings](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/sk/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/sk/SettingUpAaps/BuildingAaps.md
index 93fd3d8f8f17..55e0c7feda23 100644
--- a/docs/CROWDIN/sk/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/sk/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/tr/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/tr/CompatiblePumps/Future-possible-Pump-Drivers.md
index 0468246e9aaa..fd9fc706fec6 100644
--- a/docs/CROWDIN/tr/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/tr/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ While in the past company has decided not to allow their pumps to be controlled
**Loop status:** All 3 pumps will be Loop candidates.
-Awaiting release in Europe.
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**Hardware requirement for AAPS:** None. It seems to be BT enabled.
diff --git a/docs/CROWDIN/tr/Getting-Started/Phones.md b/docs/CROWDIN/tr/Getting-Started/Phones.md
index a24dc124e3c3..2e4e85b3c313 100644
--- a/docs/CROWDIN/tr/Getting-Started/Phones.md
+++ b/docs/CROWDIN/tr/Getting-Started/Phones.md
@@ -1,7 +1,15 @@
# Telefonlar
-The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), Android 14 is preferred.
-As of November 2024, several users have reported issues with Android 15 and Bluetooth connection. You may wish to delay the update to Android 15, especially if you are using Omnipod Dash or Dexcom G7. Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+The current version of **AAPS** (3.3) requires an Android smartphone with Google **Android 11.0 or above**. If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. However, for users unable to use a device with Android 11.0 or newer, earlier versions of **AAPS** compatible for older Android versions, remain available, see: [Release notes](#maintenance-android-version-aaps-version).
- [Jelly Pro Ayarları](../CompatiblePhones/Jelly.md)
diff --git a/docs/CROWDIN/tr/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/tr/SettingUpAaps/BuildingAaps.md
index e9cad286529b..612bee9832f2 100644
--- a/docs/CROWDIN/tr/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/tr/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Install Android Studio by clicking "Next", as shown in the following screenshots
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md
index be85463d06e2..2ee04b7f91e2 100644
--- a/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/zh_CN/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ orphan: true
**闭环状态:** 所有3款泵都将成为闭环候选。
-等待在欧洲发布。
+Awaiting release of t:mobi in Europe (other two are not yet released anywhere). Development of AAPS t:mobi support has already started and should be available by end of 2025 (see more info on Discord).
**硬件要求 AAPS：** 无。 似乎启用了蓝牙。
diff --git a/docs/CROWDIN/zh_CN/Getting-Started/Phones.md b/docs/CROWDIN/zh_CN/Getting-Started/Phones.md
index 1bcbb3483f25..00ea9da7e6e1 100644
--- a/docs/CROWDIN/zh_CN/Getting-Started/Phones.md
+++ b/docs/CROWDIN/zh_CN/Getting-Started/Phones.md
@@ -1,8 +1,16 @@
# 手机
-当前版本的**AAPS**（3.3）需要搭载**谷歌Android 11.0或更高版本**的Android智能手机。 如果你正在考虑购买新手机，（截至2024年12月），建议选择Android 14。
-截至2024年11月，一些用户报告了Android 15和蓝牙连接的问题。 您可能希望推迟更新到Android 15，特别是如果您正在使用Omnipod Dash或Dexcom G7的话。 有关此问题的最新更新，请查阅[Facebook或Discord](../GettingHelp/WhereCanIGetHelp.md)。
-出于安全原因，强烈建议用户保持其**AAPS**构建的更新状态。 但是，对于无法使用Android 11.0或更高版本设备的用户，仍然可以使用与旧版Android兼容的**AAPS**早期版本，请参阅：[发行说明](#maintenance-android-version-aaps-version)。
+当前版本的**AAPS**（3.3）需要搭载**谷歌Android 11.0或更高版本**的Android智能手机。 If you are considering buying a new phone, (as of December 2024), **Android 14 is preferred**.
+
+As of November 2024, several users have reported issues with Android 15 and Omnipod Dash Bluetooth connection.
+
+Since June 2025, many users report not being able to start Omnipod Dash with Android 16.
+
+You may wish to delay the updates, especially if you are using Omnipod Dash.
+
+Check [Facebook or Discord](../GettingHelp/WhereCanIGetHelp.md) for latest updates on this subject.
+
+Users are strongly encouraged to keep their build of **AAPS** up to date for safety reasons. 但是，对于无法使用Android 11.0或更高版本设备的用户，仍然可以使用与旧版Android兼容的**AAPS**早期版本，请参阅：[发行说明](#maintenance-android-version-aaps-version)。
- [Jelly Pro 设置](../CompatiblePhones/Jelly.md)
- [华为设置](../CompatiblePhones/Huawei.md)
diff --git a/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md
index c9f545020c4c..c7cb63aa50f2 100644
--- a/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/zh_CN/SettingUpAaps/BuildingAaps.md
@@ -146,6 +146,8 @@ Android Studio版本至关重要。 请参考[前文说明](#Building-APK-recomm
+If you want to save hard disk space, your you can uncheck Android Virtual Device: it is not used for building **AAPS**.
+
diff --git a/docs/CROWDIN/zh_TW/CompatiblePumps/Future-possible-Pump-Drivers.md b/docs/CROWDIN/zh_TW/CompatiblePumps/Future-possible-Pump-Drivers.md
index ab944c439840..33cadf80d1fc 100644
--- a/docs/CROWDIN/zh_TW/CompatiblePumps/Future-possible-Pump-Drivers.md
+++ b/docs/CROWDIN/zh_TW/CompatiblePumps/Future-possible-Pump-Drivers.md
@@ -28,7 +28,7 @@ orphan: true
**閉環狀態：** 這三款幫浦都將是閉環候選者。
-等待在歐洲上市。
+正在等待 t:mobi 在歐洲的發布（其他兩個尚未在任何地方發布）。 AAPS t:mobi 支援的開發已經開始，預計在 2025 年底前可用（詳細資訊請參閱 Discord）。
**AAPS 硬體需求：**無。 看起來已啟用藍牙 (BT)。
diff --git a/docs/CROWDIN/zh_TW/Getting-Started/Phones.md b/docs/CROWDIN/zh_TW/Getting-Started/Phones.md
index 217ab24a1da6..67f11fa6c028 100644
--- a/docs/CROWDIN/zh_TW/Getting-Started/Phones.md
+++ b/docs/CROWDIN/zh_TW/Getting-Started/Phones.md
@@ -1,8 +1,16 @@
# 手機
-目前版本的 **AAPS**（3.3）需要使用 Google **Android 11.0 或更高版本** 的 Android 智慧型手機。 如果你考慮購買新手機，(截至2024年12月)，建議使用 Android 14。
-截至2024年11月，若干用戶報告在 Android 15 和藍牙連線上遇到問題。 如果你使用 Omnipod Dash 或 Dexcom G7，你可能希望延遲更新至 Android 15。 請查閱 [Facebook 或 Discord](../GettingHelp/WhereCanIGetHelp.md) 以獲取此主題的最新更新。
-強烈建議用戶為安全原因保持 **AAPS** 的版本最新。 然而，對於無法使用 Android 11.0 或更新設備的用戶，仍可使用兼容舊版 Android 的早期 **AAPS** 版本，請參見：[發行說明](#maintenance-android-version-aaps-version)。
+目前版本的 **AAPS**（3.3）需要使用 Google **Android 11.0 或更高版本** 的 Android 智慧型手機。 如果您考慮購買新手機，(截至 2024 年 12 月)， **建議選擇 Android 14**。
+
+截至 2024 年 11 月，多位用戶報告 Android 15 與 Omnipod Dash 的藍牙連線存在問題。
+
+自 2025 年 6 月以來，許多用戶反映無法在 Android 16 上啟動 Omnipod Dash。
+
+您可能希望推遲更新，特別是在使用 Omnipod Dash 的情況下。
+
+請查看 [Facebook 或 Discord](../GettingHelp/WhereCanIGetHelp.md) 獲取有關此主題的最新更新。
+
+為安全起見，強烈建議用戶保持其 **AAPS** 的版本為最新。 然而，對於無法使用 Android 11.0 或更新設備的用戶，仍可使用兼容舊版 Android 的早期 **AAPS** 版本，請參見：[發行說明](#maintenance-android-version-aaps-version)。
- [Jelly Pro 設定](../CompatiblePhones/Jelly.md)
- [華為設定](../CompatiblePhones/Huawei.md)
diff --git a/docs/CROWDIN/zh_TW/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/zh_TW/SettingUpAaps/BuildingAaps.md
index 0415f1b77fa9..ccc32d757d4f 100644
--- a/docs/CROWDIN/zh_TW/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/zh_TW/SettingUpAaps/BuildingAaps.md
@@ -147,6 +147,8 @@ Android Studio 版本非常重要。 請參閱 [上面的指示](#Building-APK-r
+如果您希望節省硬碟空間，可以取消勾選 Android 虛擬設備：這不適用於建立 **AAPS**。
+
