diff --git a/docs/CROWDIN/it/AdvancedOptions/DevBranch.md b/docs/CROWDIN/it/AdvancedOptions/DevBranch.md
index d7bff5f9321f..bd061585ea8b 100644
--- a/docs/CROWDIN/it/AdvancedOptions/DevBranch.md
+++ b/docs/CROWDIN/it/AdvancedOptions/DevBranch.md
@@ -12,6 +12,16 @@ Se trovi un bug o pensi che sia successo qualcosa di sbagliato quando usi il ram
Una versione Dev ha una data di scadenza. Questo sembra scomodo quando lo usi in modo soddisfacente, ma serve a uno scopo. Quando una singola versione dev è in giro, è più facile tenere traccia degli errori che le persone segnalano. Gli sviluppatori non vogliono essere in una posizione in cui ci sono tre versioni di dev in giro, dove i bug sono risolti in alcuni e non altri, e la gente continua a segnalare quelli fissi.
+(branch-ci-test)=
+
+## Test a specific branch (branch-ci)
+
+To build a test branch, select branch-ci, which allows you to choose a specific branch for APK creation. You can use this method when you need to test the dev branch.
+
+
+
+
+
(github-pr-test)=
## Test items in a pull request (GitHub CI actions deploy)
diff --git a/docs/CROWDIN/it/CompatibleCgms/Caresens.md b/docs/CROWDIN/it/CompatibleCgms/Caresens.md
new file mode 100644
index 000000000000..cedbaf10ec22
--- /dev/null
+++ b/docs/CROWDIN/it/CompatibleCgms/Caresens.md
@@ -0,0 +1,29 @@
+# CareSens
+
+There are different ways to use CareSens data with **AAPS**:
+
+- xDrip+
+- Juggluco
+
+**Note:** You do not need the Sens365 follower app to connect to AAPS.
+
+## 1. xDrip+
+
+1. Install and set up the official CareSens app.
+2. In CareSens app, go to settings -> Manage Data and Connections -> turn on xDrip switch. If prefered, turn off the data connections to CareLevo, DIA:CONN, CloudLoop, etc. in "others" .
+
+
+
+
+2. Install xDrip+: [xDrip](https://github.com/NightscoutFoundation/xDrip).
+3. In xDrip+, go to settings -> hardware data source, select `Companion App` as data source.
+4. In **AAPS**, select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
+
+
+## 2. Juggluco
+
+1. Install the Juggluco app.
+2. In Juggluco, open the left menu and select `Photo`
+3. Scan the QR code on the package of the sensor.
+4. In left menu -> settings -> exchange data make sure xDrip broadcast is turned on.
+5. In **AAPS**, select xDrip+ in [ConfigBuilder, BG Source](#Config-Builder-bg-source).
diff --git a/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md b/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md
index a9a7a125ebf8..982f27469c97 100644
--- a/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md
+++ b/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md
@@ -1,31 +1,37 @@
-# Timezone traveling with pumps
+# Timezone Change and Daylight Saving
-## DanaR, Korean DanaR
+## Timezone traveling with pumps
+
+## Timezone change for Omnipod Dash
+
+* Refresh the Dash tab
+* Temporarily select a different **Profile** and then switch back to your original or desired **Profile**
+
+## Timezone change for DanaR, Korean DanaR
There is no issue with changing timezone in phone because pump doesn't use history
-(timezone-traveling-danarv2-danars)=
-## DanaRv2, DanaRS
+## Timezone change for DanaRv2, DanaRS
-These pumps need a special care because AAPS is using history from the pump but the records in pump don't have timezone stamp. **That means if you simple change timezone in phone, records will be read with different timezone and will be doubled.**
+These pumps require special care because **AAPS** uses history from the pump but the records in pump do not have timezone stamp. **This means that if you change time zone in your phone, records will be read with different time zone and will be doubled.**
To avoid this there are two possibilities:
### Option 1: Keep home time and timeshift profile
-* Turn off 'Automatic date and time' in your phone settings (manual time zone change).
+* Turn off 'Automatic date and time' in your phone's settings (manual time zone change).
-* Phone must keep your standard time as at home for the whole travel period.
+* Your phone must keep your standard time as at home for the whole travel period.
-* Time-shift your profile according to time difference between home time and destination time.
- * Long-press profile name (middle of top section on homescreen)
- * Select 'Profile Switch'
+* Time-shift your **Profile** according to time difference between home time and destination time.
+ * Long-press **Profile** name (middle of top section on homescreen)
+ * Select '**Profile Switch**'
* Set 'Time shift' according to your destination.
- * i.e. Vienna -> New York: profile switch +6 hours
- * i.e. Vienna -> Sydney: profile switch -8 hours
+ * i.e. Vienna -> New York: **Profile Switch** +6 hours
+ * i.e. Vienna -> Sydney: **Profile Switch** -8 hours
### Option 2: Delete pump history
@@ -41,18 +47,18 @@ When get out of plane:
* turn on phone
* let phone connect to the pump and fine-tune time
-(timezone-traveling-insight)=
-## Insight
+
+## Timezone Change for Insight
The driver automatically adjusts the time of the pump to the time of the phone.
-The Insight also records the history entries in which moment time was changed and from which (old) time to which (new) time. So the correct time can be determined in AAPS despite the time change.
+The Insight also records the history entries in which moment time was changed and from which (old) time to which (new) time. So the correct time can be determined in **AAPS** despite the time change.
-It may cause inaccuracies in the TDDs. But it shouldn't be a problem.
+It may cause inaccuracies in the **TDDs**. But it shouldn't be a problem.
So the Insight user doesn't have to worry about timezone changes and time changes. There is one exception to this rule: The Insight pump has a small internal battery to power time etc. while you are changing the "real" battery. If changing battery takes to long this internal battery runs out of energy, the clock is reset and you are asked to enter time and date after inserting a new battery. In this case all entries prior to the battery change are skipped in calculation in AAPS as the correct time cannot be identified properly.
-## Accu-Chek Combo
+## Timezone Change for Accu-Chek Combo
The [new Combo driver](../CompatiblePumps/Accu-Chek-Combo-Pump-v2.md) automatically adjusts the time of the pump to the time of the phone. The Combo cannot store timezones, only local time, which is precisely what the new driver programs into the pump. In addition, it stores the timezone in the local AAPS preferences to be able to convert the pump's localtime to a full timestamp that has a timezone offset. The user does not have to do anything; if the time on the Combo deviates too much from the phone's current time, the pump's time is automatically adjusted.
@@ -60,26 +66,78 @@ Note that this takes some time, however, since it can only be done in the remote
The old, Ruffy-based driver does not adjust the time automatically. The user has to do that manually. See below for the steps necessary to do that safely in case the timezone / daylight savings is the reason for the change.
-## Medtrum
+## Timezone Change for Medtrum
The driver automatically adjusts the time of the pump to the time of the phone.
-Timezone changes keep the history in tact, only TDD may be affected. Manually changing the time on the phone can cause problems with the history and IOB. If you change time manually double check the IOB.
+Time zone changes keep the history intact, only TDD may be affected. Manually changing the time on the phone can cause problems with the history and **IOB**. If you change time manually double check the **IOB**.
+
+When the time zone or time changes running **TBR's** are stopped.
+
+
+## DAYLIGHT SAVING (DST)
+Time adjustment daylight savings time
+
+Depending on your pump and CGM setup, jumps in time can lead to problems with **AAPS** to function correctlyy. For instance with the Combo pump, the pump history is read twice leading to duplicate entries. For some pumps it is better to make time zone adjustments while awake and not during the night.
+
+
+### DST automatic adjustment for most pumps
+
+* This adjustment feature is available for **AAPS** version 2.2 onwards.
+* Howeever, the fully closed Loop will be deactivated for 3 hours AFTER the DST switch (usually 1am onwards) has taken place and **AAPS** will default to background basal as selected in your **Profile**. This is done for safety reasons - **IOB** may be too high due to duplicated bolus prior to DST change.
+* After DST has taken place, select **Profile Switch** to user's desired **Profile** to enable fully closed Loop.
+* You will also receive a notification on **AAPS** main screen prior to DST change that the Fully Closed Loop has been disabled temporarily. This message will appear without beep, vibration or anything.**
+
+
+If you bolus with **AAPS'** calculator please do not use **COB** and **IOB** data unless you are sure this data is absolutely correct. Take caution and do not use this feature for a couple of hours after DST switch has taken place.
+
+### DST for Accu-Chek Insight
+
+* Change to DST is done automatically. No action required.
+
+### DST for Medtrum
+
+* Change to DST is done automatically. No action required.
+
+### DST for Omnipod Dash
+
+* Either allow **AAPS** to temporarily default background basal after DST has taken place as explained above.
+* Otherwise, if you do not want **AAPS** to temporarily default to background basal overnight, you can change the time zone the day prior DST is due to take place to avoid overnight disruption. NOTE THIS OPTION MAY CAUSE YOUR POD TO PREMATURELY EXPIRE. PLEASE HAVE SUPPLIES WITH YOU IF OPTING FOR THE FEATURE BELOW.
+
+#### Actions to take before the clock change
+1. Switch OFF any Phone's settings that automatically sets the Phone's time zone, so the user can change to a time zone that does not use DST. How to enable this will depend on your smartphone and Android version.
+
+ * Some phones have two settings, one for automatic setting of the time (which ideally should remain on) and one for automatic setting of the time zone (which you must turn OFF).
+ * Unfortunately, some Android versions have a single switch to enable automatic setting of both the time and the timezone. You’ll have to turn this off for now.
+
+
+
+
+
+2. Find a timezone that has the same time as your current location but doesn't use DST.
+
+ * A list of these countries is available [https://greenwichmeantime.com/countries](https://greenwichmeantime.com/countries/)
+ * For Central European Time (CET) this could be "Brazzaville" (Kongo). Change your phone's timezone to Kongo.
+
+
-When the timezone or time changes running TBR's are stopped.
-(time-adjustment-daylight-savings-time-dst)=
-## Time adjustment daylight savings time (DST)
+
-Depending on pump and CGM setup, jumps in time can lead to problems. With the Combo e.g. the pump history gets read again and it would lead to duplicate entries. So please do the adjustment while awake and not during the night.
-If you bolus with the calculator please don't use COB and IOB unless you made sure they are absolutely correct - better don't use them for a couple of hours after DST switch.
-### Accu-Chek Combo
+3. **AAPS** refresh your pump and switch to your desired **Profile**.
-**NOTE**: As mentioned above, this section is only valid for the old, Ruffy-based driver. The new driver adjusts date and time and DST automatically.
+3. Check **AAPS's** **IOB** and **COB** and if this is inaccurate disable the Fully Closed Loop for at least one DIA and Max-Carb-Time - whatever is bigger.
-AAPS will issue an alarm if the time between pump and phone differs too much. In case of DST time adjustment, this would be in the middle of the night. To prevent this and enjoy your sleep instead, follow these steps so that you can force the time change at a time convenient to yourself:
+4. Actions to take after the clock change. A good time to make revert to local time zone is with low **IOB**. E.g. an hour before a meal such as breakfast. Ideally your **COB** and **IOB** should both be close to zero.
+
+
+### DST for Accu-Chek Combo
+
+This section is only valid for the old, Ruffy-based driver. The new driver adjusts date and time and DST automatically.
+
+**AAPS** will issue an alarm if the time between pump and phone differs too much. In case of DST time adjustment, this would be in the middle of the night. To prevent this and enjoy your sleep instead, follow these steps so that you can force the time change at a time convenient to yourself:
#### Actions to take before the clock change
1. Switch OFF any setting that automatically sets the timezone, so you can force the time change when you want to. How you can do this will depend on your smartphone and Android version.
@@ -87,12 +145,15 @@ AAPS will issue an alarm if the time between pump and phone differs too much. In
* Some have two settings, one for automatic setting of the time (which ideally should remain on) and one for automatic setting of the timezone (which you must turn OFF).
* Unfortunately some Android versions have a single switch to enable automatic setting of both the time and the timezone. You’ll have to turn this off for now.
-2. Find a time zone that has the same time as your current location but doesn't use DST.
+ Screenshot_20260329-110315 (1)
+
+2. Find a timezone that has the same time as your current location but doesn't use DST.
* A list of these countries is available [https://greenwichmeantime.com/countries](https://greenwichmeantime.com/countries/)
* For Central European Time (CET) this could be "Brazzaville" (Kongo). Change your phone's timezone to Kongo.
-3. In AAPS refresh your pump.
+3. In **AAPS** refresh your pump.
+
4. Check the Treatments tab... If you see any duplicate treatments:
* DON'T press "delete treatments in the future"
@@ -101,11 +162,11 @@ AAPS will issue an alarm if the time between pump and phone differs too much. In
5. If the situation on how much IOB/COB is unclear - for safety please disable the loop for at least one DIA and Max-Carb-Time - whatever is bigger.*
#### Actions to take after the clock change
-A good time to make this switch would be with low IOB. E.g. E.g. an hour before a meal such as breakfast, (any recent boluses in the pump history will have been small SMB corrections. Your COB and IOB should both be close to zero.)
+A good time to make this switch would be with low **IOB**. E.g. E.g. an hour before a meal such as breakfast, (any recent boluses in the pump history will have been small SMB corrections. Your **COB** and **IOB** should both be close to zero.)
1. Change the Android timezone back to your current location and re-enable automatic timezone.
-2. AAPS will soon start alerting you that the Combo’s clock doesn’t match. So update the pump’s clock manually via the pump’s screen and buttons.
-3. On the AAPS “Combo” screen, press Refresh.
+2. **AAPS** will soon start alerting you that the Combo’s clock doesn’t match. So update the pump’s clock manually via the pump’s screen and buttons.
+3. On the **AAPS** “Combo” screen, press Refresh.
4. Then go to the Treatments screen, and look for any events in the future. There shouldn’t be many.
* DON'T press "delete treatments in the future"
@@ -114,16 +175,11 @@ A good time to make this switch would be with low IOB. E.g. E.g. an hour before
5. If the situation on how much IOB/COB is unclear - for safety please disable the loop for at least one DIA and Max-Carb-Time - whatever is bigger.*
6. Continue as normal.
-### Accu-Chek Insight
-* Change to DST is done automatically. No action required.
-### Medtrum
-* Change to DST is done automatically. No action required.
-### Other pumps
-* This feature is available since AAPS version 2.2.
-* To prevent difficulties the Loop will be deactivated for 3 hours AFTER the DST switch. This is done for safety reasons (IOB too high due to duplicated bolus prior to DST change).
-* You will receive a notification on the main screen prior to DST change that loop will be disabled temporarily. This message will appear without beep, vibration or anything.
+
+
+
diff --git a/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md b/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
index 4d31c89e0ebd..3f8258bde5e2 100644
--- a/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
+++ b/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
@@ -9,22 +9,25 @@ Questa sezione fornisce una breve panoramica di tutti i **sensori CGMs/FGMs** co
* [Impostazioni xDrip+](../CompatibleCgms/xDrip.md)
* [Nightscout come fonte di valori di glicemia](../CompatibleCgms/CgmNightscoutUpload.md): Mentre è possibile utilizzare Nightscout come fonte di glicemia per il rilascio di insulina a circuito chiuso, **questo metodo non è raccomandato** a causa della sua dipendenza da dati mobili stabili o connettività Wi-Fi. Ciò significa che i tuoi dati di **glicemia** saranno ricevuti solo da **AAPS** quando hai una connessione online al tuo sito Nightscout. Per una configurazione più affidabile, utilizzare un sensore con trasmissione locale dal ricevitore (come elencato di seguito) a **AAPS**, è un'opzione molto migliore.
-| CGM | Available [BG Sources](#Config-Builder-bg-source) |
-| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
-| [Dexcom G7](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) or [Juggluco](../CompatibleCgms/Juggluco.md) |
-| [Dexcom ONE+ and Stelo](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
-| [Dexcom G6](../CompatibleCgms/DexcomG6.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
-| [Dexcom ONE](../CompatibleCgms/DexcomG6.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
-| [Dexcom G5](../CompatibleCgms/DexcomG5.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
-| [Libre 3/3+](../CompatibleCgms/Libre3.md) | [Juggluco](../CompatibleCgms/Juggluco.md) (with or without xDrip+) |
-| [Libre 2/2+](../CompatibleCgms/Libre2.md) | [xDrip+](../CompatibleCgms/xDrip.md) (EU only) or [Juggluco](../CompatibleCgms/Juggluco.md) (with or without xDrip+) |
-| [Libre 1](../CompatibleCgms/Libre1.md) | [xDrip+](../CompatibleCgms/xDrip.md), Glimp, Tomato or Diabox. Serve un trasmettitore |
-| [Eversense](../CompatibleCgms/Eversense.md) | [xDrip+](../CompatibleCgms/xDrip.md) or ESEL/Eversense patched App |
-| [Enlite (MM640G/MM630G)](../CompatibleCgms/MM640g.md) | [xDrip+](../CompatibleCgms/xDrip.md) or MM640g + 600SeriesAndroidUploader App |
-| [PocTech](../CompatibleCgms/PocTech.md) | PocTech |
-| [Ottai](../CompatibleCgms/OttaiM8.md) | Ottai |
-| [Syai Tag](../CompatibleCgms/SyaiTagX1.md) | Syai Tag |
-| Sibionics CGM | [Juggluco](../CompatibleCgms/Juggluco.md) |
+| CGM | Available [BG Sources](#Config-Builder-bg-source) |
+| --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| [Dexcom G7](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) or [Juggluco](../CompatibleCgms/Juggluco.md) |
+| [Dexcom ONE+ and Stelo](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
+| [Dexcom G6](../CompatibleCgms/DexcomG6.md) | BYODA or [xDrip+](../CompatibleCgms/xDrip.md) |
+| [Dexcom ONE](../CompatibleCgms/DexcomG6.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
+| [Libre 3/3+](../CompatibleCgms/Libre3.md) | [Juggluco](../CompatibleCgms/Juggluco.md) (with or without xDrip+) |
+| [Libre 2/2+](../CompatibleCgms/Libre2.md) | [xDrip+](../CompatibleCgms/xDrip.md) (EU only) or [Juggluco](../CompatibleCgms/Juggluco.md) (with or without xDrip+) |
+| [Libre 1](../CompatibleCgms/Libre1.md) | [xDrip+](../CompatibleCgms/xDrip.md) or Diabox. Serve un trasmettitore |
+| [Eversense](../CompatibleCgms/Eversense.md) | [xDrip+](../CompatibleCgms/xDrip.md) or ESEL/Eversense patched App |
+| [Enlite (MM640G/MM630G)](../CompatibleCgms/MM640g.md) | [xDrip+](../CompatibleCgms/xDrip.md) or MM640g + 600SeriesAndroidUploader App |
+| [PocTech](../CompatibleCgms/PocTech.md) | PocTech app |
+| Glunovo | Glunovo App |
+| Intelligo | Intelligo App |
+| [Ottai](../CompatibleCgms/OttaiM8.md) | Ottai App |
+| [Syai](../CompatibleCgms/SyaiTagX1.md) | Syai Tag App |
+| Sibionics CGM | [Juggluco](../CompatibleCgms/Juggluco.md) or Patched SI App |
+| Sinocare | Patched Sino App |
+| [Caresens](../CompatibleCgms/Caresens.md), Simplera, iCan, LinX, SmartGuide | xDrip+ Companion App |
(GettingStarted-TrustedBGSource)=
@@ -43,5 +46,6 @@ Trusted data sources allow **SMB** delivery, all the time.
| Dexcom ONE/ONE+/Stelo | xDrip+ (**Direct, Native**) |
| Libre 2/2+ (EU) | xDrip+ (OOP2 **no calibration**), Juggluco (**xDrip broadcast** without xDrip+, or **Patched Libre** with xDrip+) |
| Libre 2/2+/3/3+ | Juggluco (**xDrip broadcast** without xDrip+, or **Patched Libre** with xDrip+) |
+| Syai | Syai App |
**Note: xDrip+ Companion apps and Follower modes (includes 640G/Eversense) are not trusted data sources.**
diff --git a/docs/CROWDIN/it/Getting-Started/Introduction.md b/docs/CROWDIN/it/Getting-Started/Introduction.md
index 63d003b6ce6c..1bcf452fbfd8 100644
--- a/docs/CROWDIN/it/Getting-Started/Introduction.md
+++ b/docs/CROWDIN/it/Getting-Started/Introduction.md
@@ -25,11 +25,11 @@ La soluzione migliore per il diabete di tipo 1 sarebbe una “cura funzionale”
## Come e perché ha avuto inizio il circuito chiuso?
-Lo sviluppo della tecnologia commerciale per le persone con diabete di tipo 1 (DT1) è molto lento. Nel 2013 la comunità T1D ha fondato il movimento #WeAreNotWaiting. Loro stessi hanno sviluppato sistemi utilizzando la tecnologia approvata esistente (microinfusori per insulina e sensori) per migliorare il controllo del glucosio nel sangue, la sicurezza e la qualità della vita. Questi sono noti come sistemi fai da te (do-it-yourself), perché non sono formalmente approvati da organismi sanitari (FDA, NHS ecc). Ci sono quattro principali sistemi fai da te disponibili: [OpenAPS](https://openaps.org/what-is-openaps/), **AAPS**, [Loop](https://loopkit.github.io/loopdocs/#what-is-loop) e [iAPS](https://github.com/Artificial-Pancreas/iAPS?fbclid=IwAR2fA9Y9YqYzpKSrtEsotfXl5b67UclDkKgyrv52tQLzYbOoBeNGRmjlJJI).
+Lo sviluppo della tecnologia commerciale per le persone con diabete di tipo 1 (DT1) è molto lento. Nel 2013 la comunità T1D ha fondato il movimento #WeAreNotWaiting. Loro stessi hanno sviluppato sistemi utilizzando la tecnologia approvata esistente (microinfusori per insulina e sensori) per migliorare il controllo del glucosio nel sangue, la sicurezza e la qualità della vita. These are known as OS-AID (Open-Source Automated Insulin Dosing) systems (formerly DIY systems), because they are not formally approved by health bodies (FDA, NHS etc). There are four main DIY systems available: [OpenAPS](https://openaps.org/what-is-openaps/), **AAPS**, [Loop](https://loopkit.github.io/loopdocs/#what-is-loop) and [Trio](https://triodocs.org).
Un ottimo modo per capire i fondamenti del circuito chiuso fai da te è leggere il libro di Dana Lewis “Automated Insulin Delivery”. È possibile accedervi [qui](https://www.artificialpancreasbook.com/) gratuitamente (o acquistare una copia cartacea del libro). Se vuoi saperne di più su [OpenAPS](https://openaps.org/what-is-openaps/), dal quale **AAPS** è stato sviluppato, il sito [OpenAPS](https://openaps.org/what-is-openaps/) è un ottima risorsa.
-Sono stati rilasciati diversi sistemi commerciali a circuito chiuso ibrido, i più recenti sono [CamAPS FX](https://camdiab.com/) (UK e UE) e [Omnipod 5](https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA e UE). Questi sono molto diversi dai sistemi fai da te, principalmente perché entrambi includono un “algoritmo di apprendimento” che regola la quantità di insulina erogata in base al fabbisogno insulinico dei giorni precedenti. Molte persone nella comunità fai da te hanno già provato questi sistemi commerciali e li hanno confrontati con il loro sistema fai da te. È possibile scoprire di più su come i diversi sistemi si confrontano chiedendo sui gruppi Facebook dedicati per questi sistemi, sul gruppo [AAPS Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) o su [Discord](https://discord.com/invite/4fQUWHZ4Mw).
+Sono stati rilasciati diversi sistemi commerciali a circuito chiuso ibrido, i più recenti sono [CamAPS FX](https://camdiab.com/) (UK e UE) e [Omnipod 5](https://www.omnipod.com/en-gb/what-is-omnipod/omnipod-5) (USA e UE). These are very different to OS-AID systems, mainly because they both include a “learning algorithm” which adjusts how much insulin is delivered according to your insulin needs from previous days. Many people in the OS-AID community have already tried out these commercial systems and compared them with their OS-AID system. È possibile scoprire di più su come i diversi sistemi si confrontano chiedendo sui gruppi Facebook dedicati per questi sistemi, sul gruppo [AAPS Facebook](https://www.facebook.com/groups/AndroidAPSUsers/) o su [Discord](https://discord.com/invite/4fQUWHZ4Mw).
## Che cos’è Android APS (AAPS)?
@@ -118,44 +118,42 @@ Multiple daily injections (MDI, (a) in **Figure 2** below) usually involve givin
## How does AAPS compare to other looping systems?
-As of June 25 2023, there are four major open source closed loop systems available: [OpenAPS](https://openaps.readthedocs.io/), **AAPS**, [Loop](https://loopkit.github.io/loopdocs/#what-is-loop) and [iAPS](https://github.com/Artificial-Pancreas/iAPS?fbclid=IwAR2fA9Y9YqYzpKSrtEsotfXl5b67UclDkKgyrv52tQLzYbOoBeNGRmjlJJI), (formerly FreeAPS X). The features of the different systems are shown in the table below:
-
-
-| Devicestype | Name | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [Open APS](https://openaps.readthedocs.io/en/latest/) | [iAPS](https://iaps.readthedocs.io/en/latest/) |
-| ----------- | ------------------------------------------------------------------- | ----------------------------------------- | ------------------------------------------- | ----------------------------------------------------- | ---------------------------------------------- |
-| Phone | Android |  |  |  |  |
-| Phone | iPhone |  |  |  |  |
-| Rig | tiny computer (1) |  |  |  |  |
-| PUMP | [Dana I](../CompatiblePumps/DanaRS-Insulin-Pump.md) |  |  |  |  |
-| PUMP | [Dana RS](../CompatiblePumps/DanaRS-Insulin-Pump.md) |  |  |  |  |
-| PUMP | [Dana R](../CompatiblePumps/DanaR-Insulin-Pump.md) |  |  |  |  |
-| PUMP | [Omnipod (Dash)](../CompatiblePumps/OmnipodDASH.md) (2) |  |  |  |  |
-| PUMP | [Omnipod (Eros)](../CompatiblePumps/OmnipodEros.md) |  |  |  |  |
-| PUMP | [Diaconn G8](../CompatiblePumps/DiaconnG8.md) |  |  |  |  |
-| PUMP | [EOPatch 2](../CompatiblePumps/EOPatch2.md) |  |  |  |  |
-| PUMP | [Medtrum TouchCare Nano](../CompatiblePumps/MedtrumNano.md) |  |  |  |  |
-| PUMP | [Medtrum TouchCare 300U](../CompatiblePumps/MedtrumNano.md) |  |  |  |  |
-| PUMP | [Roche Combo](../CompatiblePumps/Accu-Chek-Combo-Pump-v2.md) |  |  |  |  |
-| PUMP | [Roche Insight](../CompatiblePumps/Accu-Chek-Insight-Pump.md) |  |  |  |  |
-| PUMP | [Older Medtronic](../CompatiblePumps/MedtronicPump.md) |  |  |  |  |
-| PUMP | [Equil 5.3](../CompatiblePumps/Equil5.3.md) |  |  |  |  |
-| CGM | [Dexcom G7](../CompatibleCgms/DexcomG7.md) |  |  |  |  |
-| CGM | [Dexcom One](../CompatibleCgms/DexcomG6.md) |  |  |  |  |
-| CGM | [Dexcom G6](../CompatibleCgms/DexcomG6.md) |  |  |  |  |
-| CGM | [Dexcom G5](../CompatibleCgms/DexcomG5.md) |  |  |  |  |
-| CGM | [Libre 3](../CompatibleCgms/Libre3.md) |  |  |  |  |
-| CGM | [Libre 2](../CompatibleCgms/Libre2.md) |  |  |  |  |
-| CGM | [Libre 1](../CompatibleCgms/Libre1.md) |  |  |  |  |
-| CGM | [Eversense](../CompatibleCgms/Eversense.md) |  |  |  |  |
-| CGM | [MM640g/MM630g](../CompatibleCgms/MM640g.md) |  |  |  |  |
-| CGM | [PocTech](../CompatibleCgms/PocTech.md) |  |  |  |  |
-| CGM | [Ottai](../CompatibleCgms/OttaiM8.md) |  |  |  |  |
-| CGM | [Syai Tag](../CompatibleCgms/SyaiTagX1.md) |  |  |  |  |
-| CGM | [Nightscout as BG Source](../CompatibleCgms/CgmNightscoutUpload.md) |  |  |  |  |
+As of June 25 2023, there are four major open source closed loop systems available: [OpenAPS](https://openaps.readthedocs.io/), **AAPS**, [Loop](https://loopkit.github.io/loopdocs/#what-is-loop) and [Trio](https://triodocs.org), (formerly FreeAPS X). The features of the different systems are shown in the table below:
+
+
+| Devicestype | Name | [AAPS](https://wiki.aaps.app) | [Loop](https://loopkit.github.io/loopdocs/) | [Open APS](https://openaps.readthedocs.io/en/latest/) | [Trio](https://triodocs.org) |
+| ----------- | ------------------------------------------------------------------- | ----------------------------------------- | ------------------------------------------- | ----------------------------------------------------- | ----------------------------------------- |
+| Phone | Android |  |  |  |  |
+| Phone | iPhone |  |  |  |  |
+| Rig | tiny computer (1) |  |  |  |  |
+| PUMP | [Dana I](../CompatiblePumps/DanaRS-Insulin-Pump.md) |  |  |  |  |
+| PUMP | [Dana RS](../CompatiblePumps/DanaRS-Insulin-Pump.md) |  |  |  |  |
+| PUMP | [Dana R](../CompatiblePumps/DanaR-Insulin-Pump.md) |  |  |  |  |
+| PUMP | [Omnipod (Dash)](../CompatiblePumps/OmnipodDASH.md) |  |  |  |  |
+| PUMP | [Omnipod (Eros)](../CompatiblePumps/OmnipodEros.md) |  |  |  |  |
+| PUMP | [Diaconn G8](../CompatiblePumps/DiaconnG8.md) |  |  |  |  |
+| PUMP | [EOPatch 2](../CompatiblePumps/EOPatch2.md) |  |  |  |  |
+| PUMP | [Medtrum TouchCare Nano](../CompatiblePumps/MedtrumNano.md) |  |  |  |  |
+| PUMP | [Medtrum TouchCare 300U](../CompatiblePumps/MedtrumNano.md) |  |  |  |  |
+| PUMP | [Roche Combo](../CompatiblePumps/Accu-Chek-Combo-Pump-v2.md) |  |  |  |  |
+| PUMP | [Roche Insight](../CompatiblePumps/Accu-Chek-Insight-Pump.md) |  |  |  |  |
+| PUMP | [Older Medtronic](../CompatiblePumps/MedtronicPump.md) |  |  |  |  |
+| PUMP | [Equil 5.3](../CompatiblePumps/Equil5.3.md) |  |  |  |  |
+| CGM | [Dexcom G7/One+/Stelo](../CompatibleCgms/DexcomG7.md) |  |  |  |  |
+| CGM | [Dexcom One](../CompatibleCgms/DexcomG6.md) |  |  |  |  |
+| CGM | [Dexcom G6](../CompatibleCgms/DexcomG6.md) |  |  |  |  |
+| CGM | [Libre 3/3+](../CompatibleCgms/Libre3.md) |  |  |  |  |
+| CGM | [Libre 2/2+](../CompatibleCgms/Libre2.md) |  |  |  |  |
+| CGM | [Libre 1](../CompatibleCgms/Libre1.md) |  |  |  |  |
+| CGM | [Eversense](../CompatibleCgms/Eversense.md) |  |  |  |  |
+| CGM | [MM640g/MM630g](../CompatibleCgms/MM640g.md) |  |  |  |  |
+| CGM | [PocTech](../CompatibleCgms/PocTech.md) |  |  |  |  |
+| CGM | [Ottai](../CompatibleCgms/OttaiM8.md) |  |  |  |  |
+| CGM | [Syai Tag](../CompatibleCgms/SyaiTagX1.md) |  |  |  |  |
+| CGM | [Nightscout as BG Source](../CompatibleCgms/CgmNightscoutUpload.md) |  |  |  |  |
_Table notes:_
-1. A **rig** is a small computer which you carry around with you, without a monitor. One supported device type is Intel Edison + Explorer Board and the other Raspberry Pi + Explorer HAT or Adafruit RFM69HCW Bonnet. The first APS were based on this setup, as mobile phones were not capable of running the required algorithms. Use of these systems has declined, as the setup on mobile phones has become easier, and phones have a display included. Intel has also stopped selling the Intel Edison. The excellent OpenAPS algorithms **oref0** and **oref1** are now incorporated in AAPS and iAPS.
-2. Omnipod Dash is the successor of Omnipod Eros. It supports bluetooth communication and does not need a rig gateway to communicate between the Omnipod and mobile phone. If you have a choice, we recommend use of the Dash instead of Eros.
+1. A **rig** is a small computer which you carry around with you, without a monitor. One supported device type is Intel Edison + Explorer Board and the other Raspberry Pi + Explorer HAT or Adafruit RFM69HCW Bonnet. The first APS were based on this setup, as mobile phones were not capable of running the required algorithms. Use of these systems has declined, as the setup on mobile phones has become easier, and phones have a display included. Intel has also stopped selling the Intel Edison. The excellent OpenAPS algorithms **oref0** and **oref1** are now incorporated in AAPS and Trio.
An international peer-reviewed consensus statement containing practical guidance on open source looping was written by and for health-care professionals, and published in a leading medical journal in 2022: [_Lancet Diabetes Endocrinol_, 2022; 10: 58–74](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/)(_1_). It is well worth a read (including for your diabetes clinic) and summarises the main technical differences between the different open-source hybrid closed loop systems.
@@ -165,7 +163,7 @@ It is hard to get a “feel” for any system without using it, or talking to ot
## Does AAPS use artificial intelligence or any learning algorithm?
-The current master version of **AAPS** (3.3.1.3) does not have any machine learning algorithms, multiple-parameter insulin response models, or artificial intelligence. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger customised profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery.
+The current master version of **AAPS** (3.4) does not have any machine learning algorithms, multiple-parameter insulin response models, or artificial intelligence. As such, the system is open and transparent in how it works, and has the ability to be understood not just by experts, but also by clinicians and patients. It also means that if you have a sharply varying schedule (maybe switching from a stressful week at work to a relaxing holiday) and are likely to need a significantly different amount of insulin, you can immediately switch **AAPS** to run a weaker/stronger customised profile. A ‘learning system’ will do this adjustment for you automatically, but is likely to take longer to adjust the insulin delivery.
## Which system is right for me or my dependant?
@@ -178,7 +176,7 @@ It is important to note that the **AAPS** user needs to be proactive to troubles
## Is it safe to use open-source systems like AAPS?
### Safety of the AAPS system
-A more accurate question is probably “is it safe **compared** with my current insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent [paper](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) looked at the use of **AAPS** in a computer simulated set-up, which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 10,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally.
+A more accurate question is probably “is it safe **compared** with my current insulin delivery system?” since no method of insulin delivery is without risk. There are many checks and balances in place with **AAPS**. A recent [paper](https://www.liebertpub.com/doi/epub/10.1089/dia.2019.0375) looked at the use of **AAPS** in a computer simulated set-up, which was an effective way to unobjectively trial how safe and effective the system is. More generally, it is estimated that over 30,000 individuals worldwide are using open-source automated-insulin delivery systems, and uptake continues to increase globally.
Any device that uses radio communications could be hacked, and this is true for a non-looping insulin pump as well. Currently, we are not aware of anyone attempting to harm individuals by hacking their diabetes-related medical equipment. However, there are multiple ways to protect against such risks:
@@ -192,7 +190,7 @@ If a malicious attack was made on your insulin pump, these strategies would sign
#### Safety considerations around improving blood glucose control too fast
-A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a timeplan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the [safety section [here](#preparing-safety-first).
+A rapid reduction in HbA1c and improved blood glucose control sounds appealing. However, reducing average blood glucose levels _too fast_ by starting any closed loop system can cause permanent damage, including to the eyes, and painful neuropathy that never goes away. This damage can be avoided simply by reducing levels more slowly. If you currently have an elevated HbA1c and are moving to AAPS (or any other closed loop system), please discuss this potential risk with your clinical team before starting, and agree a time plan with them. More general information on how to reduce your glucose levels safely, including links to medical literature is given in the safety section [here](#preparing-safety-first).
#### Medical safety around devices, consumable supplies and other medications
@@ -220,7 +218,7 @@ Ask if your team has any patients under their care who already use DIY looping.
If you feel unsupported by your team to loop with **AAPS**, the following discussion points may help:
-a) The **AAPS** system has been designed BY patients and their caregivers. It has been designed ultimately for safety, but also drawing on in-depth patient experience. There are currently around **10,000** AAPS users worldwide. There is therefore likely to be other patients using DIY looping in your clinic's patient population (whether they know about it or not).
+a) The **AAPS** system has been designed BY patients and their caregivers. It has been designed ultimately for safety, but also drawing on in-depth patient experience. There are currently around **20,000** AAPS users worldwide. There is therefore likely to be other patients using DIY looping in your clinic's patient population (whether they know about it or not).
b) Recent peer-reviewed published guidance in the internationally leading medical journal [The Lancet](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8720075/pdf/nihms-1765784.pdf)_(1)_ has confirmed that DIY loops are **safe** and **effective at improving diabetic control**, including time in range. There are regular articles in leading journals like [Nature](https://doi.org/10.1038/d41586-023-02648-9)_(3)_ which highlight the progress of the DIY looping community.
@@ -323,7 +321,7 @@ David Burren [https://bionicwookie.com/](https://bionicwookie.com/)
The above table assumes that the user has access to both continuous gluocse monitor and insulin pump.
-*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including Nightscout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioural considerations.
+*All data from **AAPS** can be made available to healthcare professionals via data sharing platforms, including Nightscout that provides logging and real time monitoring of CGM data, insulin delivery, carbohydrate entries, predictions and settings. Nightscout records include daily and weekly reports which can aid healthcare professionals' discussions with type 1 patients with more accurate data on glycemic control and any behavioral considerations.
(accessibility-for-users-aaps-who-are-partially-or-completely-blind)=
@@ -333,7 +331,7 @@ The above table assumes that the user has access to both continuous gluocse moni
AAPS can be used by blind people. On Android devices, the operating system has a program called TalkBack. This allows screen orientation via voice output as part of the operating system. By using TalkBack you can operate both your smartphone and AAPS without needing to be able to see.
#### Building the AAPS app:
-As a user you will build the AAPS app in Android Studio. Many people use Microsoft Windows for this purpose, where there is the Screenreader analogous to TalkBack. Since Android Studio is a Java application, the “Java Access Bridge” component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio.
+As a user you will build the AAPS app in Android Studio. Many people use Microsoft Windows for this purpose, where there is the screen reader analogous to TalkBack. Since Android Studio is a Java application, the “Java Access Bridge” component must be enabled in the Control Panel. Otherwise, the screen reader of the PC will not speak in Android Studio.
How you do this depends on your operating system, two methods are outlined below:
diff --git a/docs/CROWDIN/it/Getting-Started/Phones.md b/docs/CROWDIN/it/Getting-Started/Phones.md
index 914a43d2f0bd..01e5928cd2d2 100644
--- a/docs/CROWDIN/it/Getting-Started/Phones.md
+++ b/docs/CROWDIN/it/Getting-Started/Phones.md
@@ -1,10 +1,10 @@
# Users are creating a [list of tested phones and watches](https://docs.google.com/spreadsheets/d/1gZAsN6f0gv6tkgy9EBsYl0BQNhna0RDqA9QGycAqCQc/edit?usp=sharing)
-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**.
+The current version of **AAPS** (3.4) requires an Android smartphone with Google **Android 12.0 or above**. If you are considering buying a new phone, (as of January 2026), **Android 16 is preferred**, Android 15 is not recommended.
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).
+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 12.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)
- [Huawei Settings](../CompatiblePhones/Huawei.md)
@@ -13,7 +13,7 @@ Users are strongly encouraged to keep their build of **AAPS** up to date for saf
## List of tested Phones
-We maintain a list of the [tested hardware setups](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true).
+We maintain a list of the [tested hardware setups](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) that you can [explore with a friendly interface](https://vnniyb.github.io/androidAPS_testedHardwareEasyBrowser/). Contribute by filling out the [Google form](https://docs.google.com/forms/d/e/1FAIpQLSfoGKLYEx4aUAJ5RWL3xLJeNdmRyxtXmDzpGhuU3Rfcj2H_Jw/viewform) and adding your setup!
This list provides user feedback on the usage of a phone along with **AAPS** and a given pump and CGM. It can help you check if your phone / pump / CGM has been used successfully by other users.
@@ -36,4 +36,4 @@ Design: Thiago :) If you want to decorate your phone with more AndroidAPS,
-Design: Thiago :)
\ No newline at end of file
+Design: Thiago :)
diff --git a/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md b/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md
index e0d6f93548ba..6bd0167b09b3 100644
--- a/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md
+++ b/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md
@@ -1,5 +1,10 @@
# Docs updates & changes
+## March 2026
+
+- [Add CLI Build option](../SettingUpAaps/CLIBuild.md) @je-l
+- Rename *Computer Build* to *Android Studio Build*. Preserve file names for URLs.
+
## January 2025
- [3.4](#version3400) release and documentation update roll-up (Wizard, Computer build versions, Config Builder)
diff --git a/docs/CROWDIN/it/Maintenance/ExportImportSettings.md b/docs/CROWDIN/it/Maintenance/ExportImportSettings.md
index 4261e83070c2..06faac8f0fb4 100644
--- a/docs/CROWDIN/it/Maintenance/ExportImportSettings.md
+++ b/docs/CROWDIN/it/Maintenance/ExportImportSettings.md
@@ -36,9 +36,16 @@ In case your main **AAPS** phone is lost or damaged, having a copy of the APK av
**How to back-up:** Maintain a copy on the computer used to build the APK with Android Studio. Additionally, it is recommended to use a cloud platform to store a copy of the installer APK. Make sure you know how to locate both backups when needed. Consider setting up dedicated folders to store these backups.
### AAPS settings file (also referred to as 'Preferences')
+
+```{admonition} Where are preferences stored on my phone?
+:class: tip
+You will find your settings in the **AAPS Directory** you have selected during [AAPS setup](#SetupWizard-StoragePermission).
+You can also change the **AAPS Directory** in Preferences > [Maintenance Settings](#preferences-maintenance-settings).
+```
+
With a copy of the APK installer file (see above) and your **Settings** file, you can quickly get up and running on an existing or new phone.
-The **Settings** file is used t customize the AAPS application to fit your specific setup. They encompass details such as your config builder settings, objective status, third-party communication settings (e.g., Nightscout, Tidepool), automations, and profiles.
+The **Settings** file is used to customize the AAPS application to fit your specific setup. They encompass details such as your config builder settings, objective status, third-party communication settings (e.g., Nightscout, Tidepool), automations, and profiles.
Exporting the AAPS settings to file enables you to restore its configuration to a specific point in time. As mentioned, in addition to all configuration settings, the export file also contains the status of your objectives, which you need to restore when **(re)installing** AAPS. Without this you will be required to redo all objectives from start to enable closed loop. Settings files also enable you to restore "last known good" settings for undoing any configuration changes.
@@ -63,6 +70,12 @@ Exporting the AAPS settings to file enables you to restore its configuration to
## Settings Export
+```{admonition} Where are preferences stored on my phone?
+:class: tip
+You will find your settings in the **AAPS Directory** you have selected during [AAPS setup](#SetupWizard-StoragePermission).
+You can also change the **AAPS Directory** in Preferences > [Maintenance Settings](#preferences-maintenance-settings).
+```
+
It is recommended to do regular settings exports, especially before and after making configuration changes. You can choose to do exports **manually or (preferred) through automation**. Make sure to take a note of your AAPS master password and to backup your settings files by copying them off your phone to for instance a cloud storage location.
**Note**: _The exported settings will be encrypted with your AAPS master password: without the master password used for exporting you will be unable to import the settings file!_
@@ -85,6 +98,13 @@ _**Note:** On importing settings to user always needs to enter the AAPS password
(ExportImportSettings-restoring-from-your-backups-on-a-new-phone-or-fresh-installation-of-aaps)=
## Restoring from your backups on a new phone or fresh installation of AAPS
+
+```{admonition} Where are preferences stored on my phone?
+:class: tip
+You will find your settings in the **AAPS Directory** you have selected during [AAPS setup](#SetupWizard-StoragePermission).
+You can also change the **AAPS Directory** in Preferences > [Maintenance Settings](#preferences-maintenance-settings).
+```
+
Use these instructions if you have a back-up of your APK and **Preferences** that you want to load on to a new phone or if you needed to delete and reinstall the APK on your existing phone for any reason.
_If you are updating **AAPS** using an APK built with the same keystore you should not need to follow this process. However, it is still advised to create a back-up before you apply the update._
@@ -108,13 +128,15 @@ Importing a **Preferences** file will deactivate your current pod if those **Pre
5. From the **AAPS** home screen, set the master password in [Preferences > General > Protection](#Preferences-master-password) to the same password as you used with your back-ups.
-6. From the **AAPS** home screen, select the three line (hamburger) menu in the top left > Maintenance > Export settings > type in Master password set above > Ok. This will create the preferences folder if it does not already exist on your phone.
+6. If you haven't done it yet, [set the **AAPS Directory**](#preferences-maintenance-settings): from the **AAPS** home screen, select the three line (hamburger) menu in the top left > Maintenance > AAPS DIRECTORY.
+
+7. From the **AAPS** home screen, select the three line (hamburger) menu in the top left > Maintenance > Export settings > type in Master password set above > Ok. This will create the preferences folder if it does not already exist on your phone.
-7. Download the back-up of your **Preferences** file from your cloud platform.
+8. Download the back-up of your **Preferences** file from your cloud platform.
-8. Use your file explorer (commonly called “Files” or “My Files”) to move the file from your downloads to `/internal storage/AAPS/preferences`
+9. Use your file explorer (commonly called “Files” or “My Files”) to move the file from your downloads to `/internal storage/AAPS/preferences` if your **AAPS Directory** has been set `/internal storage/AAPS`
-9. From the **AAPS** home screen, select the three line (hamburger) menu in the top left > Maintenance > Import settings > select the preferences file you want to back-up from > Ok > type in Master password set above > Ok. Make sure you select the correct preferences file, all .json files from the preferences folder will be shown.
+10. From the **AAPS** home screen, select the three line (hamburger) menu in the top left > Maintenance > Import settings > select the preferences file you want to back-up from > Ok > type in Master password set above > Ok. Make sure you select the correct preferences file, all .json files from the preferences folder will be shown.
 
diff --git a/docs/CROWDIN/it/Maintenance/ReleaseNotes.md b/docs/CROWDIN/it/Maintenance/ReleaseNotes.md
index 688492cd5c4f..3bdd68de4150 100644
--- a/docs/CROWDIN/it/Maintenance/ReleaseNotes.md
+++ b/docs/CROWDIN/it/Maintenance/ReleaseNotes.md
@@ -1,23 +1,15 @@
# Release notes
-Please follow the instructions in the [update manual](UpdateToNewVersion). The troubleshooting section also addresses the most common difficulties encountered when updating **AAPS** on the update manual page.
+Please follow the instructions in the [update manual](UpdateToNewVersion) to update to a new version. The troubleshooting section also addresses the most common difficulties encountered when updating **AAPS** on the update manual page.
-You will receive the information as soon as a new update is available. If you do not update until expiration date **AAPS** will switch to Open Loop.
+You will receive a notification like this when a new update is available:
-This prompt is important, should not be ignored and is not intended to bug you. New versions of **AAPS** do not only provide new features but also important safety fixes. Therefore it is necessary that every **AAPS** user updates to the latest version a.s.a.p. Unfortunately there are still bug reports from very old versions so this an effort to try to improve the safety for each **AAPS** user and the DIY community. Thank you for your understanding.
+If you do not update until expiration date **AAPS** will switch to Open Loop.
-```{admonition} First version of **AAPS**
-:class: note
-
-The first test version started already in 2015. In 2016 has been the first released version.
-
-The chronology of these releases is not available at the moment but as this question is asked several times we document it here.
-
-```
-
+**Do not ignore the notification.** New versions of **AAPS** provide important safety fixes. Therefore, every **AAPS** user must update to the latest version as soon as possible. This an effort to try to improve the safety for each **AAPS** user and the DIY community. Thank you for your understanding.
(maintenance-android-version-aaps-version)=
@@ -62,6 +54,79 @@ WearOS 5, API level 34 (Android 14) has [limitations](#BuildingAapsWearOs-WearOS
(latestrelease)=
+(version3422)=
+
+## Version 3.4.2.2
+
+- Fixing issues with Equil and Medtronic
+- Improve safety of Medtrum
+
+(version3421)=
+
+## Version 3.4.2.1
+
+- Equil: fix Pairing and progress dialog @MilosKozak
+
+(version3420)=
+
+## Version 3.4.2.0
+
+Release date: 04-02-2026
+
+- Equil: Fix resistance for different models @hhfcvmars
+- Tidepool: Fix session @MilosKozak
+- Medtrum: Fix activation path by preveting double fill @MilosKozak
+- COB: Fix COB calculation (covers dangerous edge case) @MilosKozak
+
+(version3410)=
+
+## Version 3.4.1.0
+
+Release date: 03-08-2026
+
+### Core
+- Fix DST handling @MilosKozak
+- Improve and unify normal target identification (mgdl > 99, mmol > 5.5) @MilosKozak
+- SMS: protect RESTART by PIN @MilosKozak
+- Maintenance: warn if wrong directory selected @MilosKozak
+
+### Pump Driver Improvements
+- **Omnipod Dash**: refactor BLE driver code to omnipod/common module @jwoglom
+- **Omnipod Dash**: try to fix connection state @MilosKozak
+- **Omnipod**: validate profile before pod activation to prevent wasting pods (#4534) @brianV
+- **Medtronic**: fix same encoding type displayed in settings dialog @mifi100
+- **Medtronic**: prepare pump common classes (Tandem preparation) @andy-rozman
+- **RileyLink**: encoding fix (#4519) @mifi100
+- **Equil**: expand insulin pump compatibility by serial number prefix (#4510) @hhfcvmars
+- **Equil**: add logging @MilosKozak
+- **Diaconn G8**: fix log sync bug and add firmware 3.58+ support @miyeongkim
+- **Diaconn**: fix TBR duration unit conversion @miyeongkim
+- **Diaconn**: use commandQueue.loadEvents() for history sync @miyeongkim
+- Allow insulin delivery while loop is suspended but pump is available @cschuijt
+
+### Cloud / Backup
+- Add backup to Google Drive @Angus-repo
+- Notify UI on cloud storage error state change @Angus-repo
+- Allow both local and cloud storage at the same time @Angus-repo
+
+### Tidepool
+- Improve Tidepool OAuth2 migration @MilosKozak
+- Fix indefinite Tidepool BLOCKED state, fix rejecting empty SSIDs @michaeln-synapse
+
+### NSClient
+- NSCv3: improve reconnection @MilosKozak
+
+### Wear OS
+- Display New IOB in Wizard Result if IOB is used in calculations @olorinmaia
+- Fix Wear BolusProgress with Total Amount @Philoul
+
+### UI
+- Improve ic_none icon for Site Rotation @Philoul
+- Fix site rotation manage pump setting not being used @samfundev
+
+### Contributors
+@MilosKozak @Philoul @olorinmaia @jwoglom @mifi100 @andy-rozman @Angus-repo @brianV @cschuijt @hhfcvmars @miyeongkim @samfundev @michaeln-synapse
+
(version3400)=
## Version 3.4.0.0
@@ -931,3 +996,15 @@ Release date: 03-11-2018
- Option to keep screen on
- Option to show notification as Android notification
- Advanced filtering (allowing to always enable SMB and 6h after meals) supported with patched Dexcom app or xDrip with G5 native mode as BG source.
+
+## Version 1.0
+
+```{admonition} First version of **AAPS**
+:class: note
+
+The first test version started in 2015 and the first release was in 2016.
+
+The exact chronology of these releases is not available at the moment but as this question has been asked several times we document it here.
+
+```
+
diff --git a/docs/CROWDIN/it/Maintenance/UpdateBrowserBuild.md b/docs/CROWDIN/it/Maintenance/UpdateBrowserBuild.md
index 4968313f412b..ce75c314c31c 100644
--- a/docs/CROWDIN/it/Maintenance/UpdateBrowserBuild.md
+++ b/docs/CROWDIN/it/Maintenance/UpdateBrowserBuild.md
@@ -70,7 +70,7 @@ You have now synchronized (updated) your own copy with the latest release of And
-5. Select the branch you want to deploy (master), the [variant](variant) (fullRelease) and tap Run Workflow.
+5. Keep the branch set to master, select the AAPS Version you want to build — either the latest version or a specific required version — choose the [variant](variant) (fullRelease), and then tap Run workflow.
diff --git a/docs/CROWDIN/it/Maintenance/UpdateComputerBuild.md b/docs/CROWDIN/it/Maintenance/UpdateComputerBuild.md
new file mode 100644
index 000000000000..5382357cc05a
--- /dev/null
+++ b/docs/CROWDIN/it/Maintenance/UpdateComputerBuild.md
@@ -0,0 +1,103 @@
+# Update with Android Studio
+
+## Build yourself instead of download
+
+**AAPS** is not available to download, due to regulations concerning medical devices. It is legal to build the app for your own use, but you must not give a copy to others! 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 Android Studio
+
+```{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.
+
+ 
+
+* In the menu bar of Android Studio, select Git -> Fetch
+
+ 
+
+* You will see a message in the lower right corner that Fetch was successful.
+
+ 
+
+* In the menu bar, now select Git -> Pull
+
+ 
+
+* Leave all options as they are (origin/master) and select Pull
+
+ 
+
+* 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
+ ```
+
+ 
+
+* Gradle Sync will be running to download some dependencies. Wait until it is finished.
+
+ 
+
+### 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).
\ No newline at end of file
diff --git a/docs/CROWDIN/it/Maintenance/UpdateToNewVersion.md b/docs/CROWDIN/it/Maintenance/UpdateToNewVersion.md
index 8d8d89ec6655..d7bf7e55adf6 100644
--- a/docs/CROWDIN/it/Maintenance/UpdateToNewVersion.md
+++ b/docs/CROWDIN/it/Maintenance/UpdateToNewVersion.md
@@ -15,10 +15,14 @@
If you already built your AAPS app with the Browser Build method, follow [these instructions](./UpdateBrowserBuild.md).
-## Update AAPS with a computer
+## Update AAPS with Android Studio
Follow [these instructions.](./UpdateComputerBuild.md).
+## Update AAPS with the command-line
+
+Use the [same instructions](../SettingUpAaps/CLIBuild.md) as when building AAPS previously, but pull new changes with git.
+
(Update-to-new-version-check-aaps-version-on-phone)=
### Controlla la versione di AAPS sul telefono
diff --git a/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md
index 9c4a4a78ca2b..d797c25a42f7 100644
--- a/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md
@@ -35,7 +35,7 @@ To differentiate between the two apps, some elements have a different background
**AAPSClient** can be installed on a single phone or multiple follower phones (i.e. parent 1’s follower phone and parent 2’s follower phone) in order for both caregivers to be granted access and remote control a patient's **AAPS** phone.
-To download **AAPSClient**, navigate to the [GitHUb repository](https://github.com/nightscout/AndroidAPS/releases/) and click on the asset **“app-AAPSClient-release_x.x.x.x”** (it may be a newer version to that shown in the screenshot below):
+To download **AAPSClient**, navigate to the [Github repository](https://github.com/nightscout/AndroidAPS/releases/) and click on the asset **“app-AAPSClient-release_x.x.x.x”** (it may be a newer version to that shown in the screenshot below):
diff --git a/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
index 4637dca54ba2..c8f03502312c 100644
--- a/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
@@ -62,10 +62,10 @@ Scroll down the next screen and tap **Create Fork**.
```{note}
You cannot fork and you see this?
-`**Create a new fork**`
-`A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. View existing forks.`
-`*Required fields are marked with an asterisk (*).*`
-`**No available destinations to fork this repository.**`
+**`Create a new fork`**
+`A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. View existing forks.`
+*`Required fields are marked with an asterisk (*).`*
+**`No available destinations to fork this repository.`**
This means you already have an existing fork of AndroidAPS.
Make sure it's up to date and continue to Preparation Steps.
```
@@ -196,10 +196,16 @@ Skip the next section and continue [here](#aaps-ci-google-drive-auth).
```
+
+
(aaps-ci-google-drive-auth)=
### AAPS-CI Google Drive Auth
+```{warning}
+No matter which of the prior sets of instructions you followed (option 1 or option 2), you MUST add the Google Drive authorization to successfully use the Browser Build.
+```
+
Note: If you already followed this part in the video, you can now skip to [here](#github-build-apk).
Return to the File Explorer Plus tab.
@@ -252,6 +258,10 @@ Switch back to the GitHub tab.
+You should have either two (option 1) or five (option 2) secrets entries now.
+
+
+
GitHub will now be able to store the AAPS apk file in your Google Drive, once built.
(github-build-apk)=
@@ -313,6 +323,15 @@ Variants ending with “Debug” indicates that the APK will be built in debug m
+(aaps-ci-google-token-expired)=
+### Google Refresh Token Expired
+ - Google OAuth2 refresh tokens will expire if not used for 6 months, and may also become invalid under other conditions (e.g., you have changed your Google account password, or manually revoked access). For more details, see the [Google OAuth2 documentation](https://developers.google.com/identity/protocols/oauth2).
+ - You will see an error indicating that the access token is invalid, as shown below:
+
+ 
+
+ - If your build fails due to an expired or revoked Google refresh token, you will need to redo the [Google Drive Auth](#aaps-ci-google-drive-auth) steps to obtain a new `GDRIVE_OAUTH2` token and update the secret in your GitHub repository, then re-run the build workflow.
+
(aaps-ci-disable-software)=
### Disable Software That May Interfere With OAUTH Verification
- Disable any VPN or security app (firewall, antimalware,...) on the phone before trying to get the OAUTH key.
diff --git a/docs/CROWDIN/it/SettingUpAaps/BrowserBuildCIS.md b/docs/CROWDIN/it/SettingUpAaps/BrowserBuildCIS.md
index ab5ed29b81ae..8ad0f3b9e862 100644
--- a/docs/CROWDIN/it/SettingUpAaps/BrowserBuildCIS.md
+++ b/docs/CROWDIN/it/SettingUpAaps/BrowserBuildCIS.md
@@ -1,7 +1,3 @@
-- - -
-orphan: true
-- - -
-
### Run the Workflow to Build the Signed APK
1. In your GitHub copy of AndroidAPS, select Actions.
@@ -14,7 +10,7 @@ orphan: true
-5. Select the branch you want to deploy (master), the [variant](#variant) (fullRelease) and tap Run Workflow.
+5. Select the branch you want to deploy (master), the [variant](variant) (fullRelease) and tap Run Workflow.
diff --git a/docs/CROWDIN/it/SettingUpAaps/BuildingAaps.md b/docs/CROWDIN/it/SettingUpAaps/BuildingAaps.md
index bdc1487316be..fd72ff07d985 100644
--- a/docs/CROWDIN/it/SettingUpAaps/BuildingAaps.md
+++ b/docs/CROWDIN/it/SettingUpAaps/BuildingAaps.md
@@ -8,9 +8,9 @@ Vedi la pagina [Domande frequenti](../UsefulLinks/FAQ.md) per i dettagli.
---
-Two methods are available to build the AAPS app:
+Three methods are available to build the AAPS app:
-### Build with a browser
+### Build with a browser (recommended)
You can build the app with your smartphone using GitHub actions, and save it in your Google Drive.
@@ -18,9 +18,16 @@ You can build the app with your smartphone using GitHub actions, and save it in
----
-### Build with a computer
+### Build with Android Studio
-You can build the app with your computer using Android Studio.
+You can build the app with your computer using Android Studio. This used to be the only build option, nowadays Android Studio is mostly used by developers who consider making code changes.
**[Follow these instructions.](./ComputerBuild.md)**
+----
+
+### Build using the command-line
+
+This option is intended for those who prefer to build AAPS in local command-line, without installing Android Studio.
+
+**[Follow these instructions.](./CLIBuild.md)**
diff --git a/docs/CROWDIN/it/SettingUpAaps/CLIBuild.md b/docs/CROWDIN/it/SettingUpAaps/CLIBuild.md
new file mode 100644
index 000000000000..91bcee48b1db
--- /dev/null
+++ b/docs/CROWDIN/it/SettingUpAaps/CLIBuild.md
@@ -0,0 +1,54 @@
+# Build instructions for the command-line
+
+```{admonition} For users familiar with the command-line and git
+:class: information
+
+The simplest option to build AAPS is the [Browser build](./BrowserBuild.md) alternative.
+```
+
+Tested with Fedora and Debian Linux, other systems should work with minimal adjustments.
+
+## Requirements
+
+Consult the minimum required Java version from [this table](#Building-APK-recommended-specification-of-computer-for-building-apk-file). Install the appropriate OpenJDK package using the system package manager. For example in Debian, the packages are named like `openjdk-21-jdk`. It should include `javac` and `keytool` binaries.
+
+Download the *Android Command line tools* package from the [Android Studio page](https://developer.android.com/studio#command-line-tools-only). Android Studio itself is not required. More information about installing this package is found in [sdkmanager docs](https://developer.android.com/tools/sdkmanager). After the package is installed, you should manually set two [environment variables](https://developer.android.com/tools/variables): `ANDROID_HOME` and `PATH`. Finally, run `sdkmanager --licenses` to finish the installation.
+
+## Building AAPS with Gradle wrapper
+
+### 1. Generate a Java keystore file for signing AAPS
+
+If you already have a keystore file for signing AAPS, reuse that.
+
+```sh
+keytool -genkeypair -v \
+ -keystore aaps-keystore.jks \
+ -alias aaps-key \
+ -keyalg RSA \
+ -keysize 4096 \
+ -validity 20000
+```
+
+You will need the keystore file and passphrase every time you update AAPS.
+
+### 2. Compile the AAPS APK file
+
+Clone the [git repo](https://github.com/nightscout/AndroidAPS) if not already cloned. AAPS uses master branch for the latest stable version, ensure you are on the branch/tag you want to build.
+
+Run `./gradlew :app:assembleFullRelease` in the repo. It automatically downloads Gradle, dependencies, and then compiles the code. When the build succeeds, you should have an unsigned APK at `app/build/outputs/apk/full/release/app-full-release-unsigned.apk`. It should have also installed an `apksigner` binary to `$ANDROID_HOME`. Update your `PATH` again.
+
+### 3. Create a signed APK file from the unsigned one
+
+
+
+Change to your home directory and create a signed APK file:
+
+```sh
+apksigner sign \
+ --ks path/to/aaps-keystore.jks \
+ --ks-key-alias aaps-key \
+ --out app-full-release-signed.apk \
+ ./AndroidAPS/app/build/outputs/apk/full/release/app-full-release-unsigned.apk
+```
+
+Now you have `app-full-release-signed.apk` ready for installation or upgrade.
diff --git a/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md
index 1908571be457..4a1ec5606bdc 100644
--- a/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md
+++ b/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md
@@ -1,4 +1,6 @@
-# Computer Build
+
+
+# Android Studio Build
This is the traditional method to build your AAPS app.
@@ -21,11 +23,12 @@ See [FAQ page](../UsefulLinks/FAQ.md) for details.
| ----------------------- | ---------------------------------------------------- | ------------------------------------------------------ | ------ |:--- |
| 2.6.2 | 3.6.1 | | 5.6.4 | 11 |
| 2.8.2.1 | 4.1.1 | | 6.1.1 | 13 |
-| [3.1.0.3](#version3100) | 2020.3.1 | up to Otter | 7.3.3 | 17 |
-| [3.2.0.4](#version3204) | Hedgehog (2023.1.1) | up to Otter | 8.2 | 17 |
-| [3.3.1.3](#version3300) | Ladybug Feature Drop (2024.2.2) | up to Otter | 8.10 | 21 |
-| [3.3.2](#version3300) | Meerkat (2024.3.1) | up to Otter | 8.11.1 | 21 |
-| [3.3.2.1](#version3321) | Narwhal (2025.1.2) | Otter | 8.13 | 21 |
+| [3.1.0.3](#version3100) | 2020.3.1 | up to Panda 2 | 7.3.3 | 17 |
+| [3.2.0.4](#version3204) | Hedgehog (2023.1.1) | up to Panda 2 | 8.2 | 17 |
+| [3.3.1.3](#version3300) | Ladybug Feature Drop (2024.2.2) | up to Panda 2 | 8.10 | 21 |
+| [3.3.2](#version3300) | Meerkat (2024.3.1) | up to Panda 2 | 8.11.1 | 21 |
+| [3.3.2.1](#version3321) | Narwhal (2025.1.2) | up to Panda 2 | 8.13 | 21 |
+| [3.4.1](#version3410) | Panda 2 (2025.32) | | 9 | 21 |
The "preferred version" is packaged with the appropriate JVM version. The preferred version is also the minimal version you can use to build **AAPS**. You will **NOT** be able to build on a version older than the "preferred" one. If using a different version, you may encounter issues related to JVM version. See the [Troubleshooting Android Studio](#troubleshooting_androidstudio-uncommitted-changes) page to help solve these issues. If your current Android Studio version is not listed in the table, you must update it first.
@@ -70,7 +73,7 @@ The Gradle version is linked to the source code, you will always get the correct
## Help and support during the building process
-If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio) section, please consult that first.
+If you run into difficulties in the process of building the **AAPS** app, there is a dedicated [**troubleshooting Android Studio**](../GettingHelp/TroubleshootingAndroidStudio.md) section, please consult that first.
If you think something in the building instructions is wrong, missing or confusing, or you are still struggling, please reach out to other **AAPS** users group on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). If you want to change something yourself (updating screenshots _etc_), please submit a [pull request (PR)](../SupportingAaps/HowToEditTheDocs.md).
@@ -409,7 +412,7 @@ Android Studio will display the information "BUILD SUCCESSFUL" after build is fi
-**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio)._**
+**_If the build was not successful, refer to the [Android Studio Troubleshooting section](../GettingHelp/TroubleshootingAndroidStudio.md)._**
In the Notifications box, click on the blue link "locate":
diff --git a/docs/CROWDIN/it/SettingUpAaps/SetupWizard.md b/docs/CROWDIN/it/SettingUpAaps/SetupWizard.md
index c20849fd1103..ea8bf903e493 100644
--- a/docs/CROWDIN/it/SettingUpAaps/SetupWizard.md
+++ b/docs/CROWDIN/it/SettingUpAaps/SetupWizard.md
@@ -125,6 +125,8 @@ Follow these steps on Android 16, other versions will varies slightly from the p
+(SetupWizard-StoragePermission)=
+
### Storage permission
**AAPS** needs to log information to the permanent storage of your smartphone. Permanent storage means that it will be available even after rebooting your smartphone. Other information is just lost, as it is not saved to permanent storage.
diff --git a/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md b/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md
index 91f0d1eface2..60de383aa43d 100644
--- a/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md
+++ b/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md
@@ -77,9 +77,9 @@ a) using a USB cable to put the **AAPS** wear apk file onto the phone, and then
b) cut and paste Wear.apk from Android Studio onto your Gdrive.
-You can use either Wear Installer 2 or Easy Fire tools to side-load AAPS onto the watch. Here we recommend Wear Installer 2, because the instructions and process in the video are so clear and well-explained.
+To side-load AAPS onto the watch You can use either: 1) Wear Installer 2 2) Easy Fire tools 3) Android Debug Bridge (ADB) Here we recommend Wear Installer 2, because the instructions and process in the video are so clear and well-explained. If Wear Installer 2 does not work for you try via
-## Using Wear Installer 2 to side-load **AAPS** Wear from the phone onto the watch
+### Using Wear Installer 2 to side-load **AAPS** Wear from the phone onto the watch
@@ -96,54 +96,76 @@ As mentioned in the video, once complete, switch ADB debugging off on the watch,
Alternatively, but not for Wear OS 5, you can:
-```{admonition} Use Easy Fire tools to side-load the **AAPS** wear on the watch
-:class: dropdown
+### Use Easy Fire tools to side-load the **AAPS** wear on the watch
-1) Download _Easy Fire Tools_ from playstore onto phone
+1) Download _[Easy Fire Tools](https://play.google.com/store/apps/details?id=de.agondev.easyfiretools&hl=en)_ from the Play Store onto phone
-
+
-2) Make yourself a developer in the watch (once set up and connected to phone):
+2) Make yourself a developer in the watch (once set up and connected to phone):
-Go to settings >about watch (bottom option) >- software info > software version.
+Go to settings >about watch (bottom option) -> software info -> software version.
-Rapidly tap on “ software version” until a notification appears that the watch is now in "developer mode". Return to the top of settings menu, scroll to the bottom
- and see “developer options” below “about watch”.
+
-In “developer options”, turn on “ADB debugging” and “wireless debugging”. The latter option then reveals the IP address of the watch, the final two digits of which changes each time the watch is paired with a new phone. It will be something like: **167.177.0.20.** 5555 (ignore the last 4 digits). Note that the last two digits (here, “20”) of this address will change every time you change to a new phone handset for AAPS.
+Rapidly tap on “ software version” until a notification appears that the watch is now in "developer mode".
-
+
-STEP 3) Enter IP address _e.g._ **167.177.0.20** into Easy Fire tools on the phone (go into the left hamburger, settings and enter the IP address). Then click the plug socket icon on the top right.
+Return to the top of settings menu, scroll to the bottom and see “developer options” below “about watch”.
-
+In “developer options”, turn on “ADB debugging” and “wireless debugging”. The latter option then reveals the IP address of the watch, the final two digits of which changes each time the watch is paired with a new phone. It will be something like: **192.168.1.214**.5555 (ignore the last 4 digits). Note that the last two digits (here, “20”) of this address will change every time you change to a new phone handset for AAPS.
+
-
+STEP 3) Enter IP address _e.g._ **192.168.1.214** into Easy Fire tools on the phone (go into the left hamburger, settings and enter the IP address).
+
-STEP 4) Follow the instructions [here](https://wearablestouse.com/blog/2022/01/04/install-apps-apk-samsung-galaxy-watch-4/?utm_content=cmp-true) to side-load (i.e. transfer) Wear.apk onto the smartwatch using Easy Fire tools
+Then click the plug socket icon on the top right. It will turn green when connected.
-Click side "plug-in" socket in the app, in order to upload Wear OS.apk onto the smartwatch:
+
-
+STEP 4) Follow the instructions [here](https://wearablestouse.com/blog/2022/01/04/install-apps-apk-samsung-galaxy-watch-4/?utm_content=cmp-true) to side-load (i.e. transfer) aaps-wear.apk onto the smartwatch using Easy Fire tools
- Next step > accept the authorisation request on the smartwatch
+
-
-
-```
(BuildingAapsWearOs-WearOS5-TShoot)=
+### Using the terminal
+Connect your smartwatch and computer to the same Wi-Fi network.
+
+- To install ADB download it from: https://developer.android.com/tools/releases/platform-tools
+- Open a terminal.
+- For Windows, create a new folder named `adb` under your disk `C:`. Open the `platform-tools-latest-windows.zip` file you downloaded above. Copy all files inside `platform-tools` to `C:\adb` and open this folder with a command prompt (right click and Open in Terminal). Type the command below to set the path to the folder where ADB is located: `setx PATH "%PATH%;C:\adb"`
+- For Mac instead of installing manually you can use homebrew: `brew install android-platform-tools`
+
+On the watch:
+- Go to Settings → About watch → **Software Information**
+- Tap Software version 7 times until you see Developer mode enabled.
+- Go to Settings → Developer options. Enable **ADB debugging**
+- Go to Settings → Developer options → Wireless debugging → **Pair new device**
+
+You will see a Wi-Fi paring code and IP address and port appearing: 
+
+- In the terminal: `adb pair ipaddress:port` E.g. `adb pair 10.10.1.125:36299`
+- You will be asked for the pairing code. Enter it.
+- You will see a response:
`Successfully paired to 10.10.1.125:36299 [guid=adb-RXXXW20LMKJY-eh5zBj]`
+- In the terminal type:
`adb devices`.
You should see something like:
`List of devices attached`
`10.10.1.125:36299 offline`
`adb-RFAW20LMKJY-eh5zBj._adb-tls-connect._tcp device`
+
+- Now go to the folder on your computer where the Wear apk is and type
`adb install wear-full.apk`
with wear.apk replaced by the name of your apk file.
+- You will see:
`Performing Streamed Install`
`Success`
+
+
### General troubleshooting recommendations for Wear OS 5
- Do not use Wi-Fi Tethering. That won't work.
- You do not need to enable adb debugging on the phone (only on the watch). Disable adb debugging on the Phone.
- Make sure you are connecting to your local network where phone and watch can see each other (do not use your Wi-Fi guest network to connect).
-- For GW7 you need to install using Wear Installer as it gives you the option to select the AAPS(Custom) watchface on installation.
+- For GW7 you need to install using Wear Installer 2 as it gives you the option to select the AAPS (Custom) watchface on installation.
- Make sure both watch and phone are on the same network and Wi-Fi device. Especially Wi-Fi repeaters or access points may create problems.
- Make sure to be near your main router, then restart both phone and watch.
diff --git a/docs/CROWDIN/it/images/Building-the-App/CI/BrowserBuildGAUTH8.png b/docs/CROWDIN/it/images/Building-the-App/CI/BrowserBuildGAUTH8.png
new file mode 100644
index 000000000000..4156e1a0c44f
Binary files /dev/null and b/docs/CROWDIN/it/images/Building-the-App/CI/BrowserBuildGAUTH8.png differ
diff --git a/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_branch_ci1.png b/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_branch_ci1.png
new file mode 100644
index 000000000000..26eadb17b325
Binary files /dev/null and b/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_branch_ci1.png differ
diff --git a/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_branch_ci2.png b/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_branch_ci2.png
new file mode 100644
index 000000000000..6ac69234b85b
Binary files /dev/null and b/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_branch_ci2.png differ
diff --git a/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_token_expired.jpg b/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_token_expired.jpg
new file mode 100644
index 000000000000..fb3dd116443c
Binary files /dev/null and b/docs/CROWDIN/it/images/Building-the-App/CI/aaps_ci_token_expired.jpg differ
diff --git a/docs/CROWDIN/it/images/eversenseapp-dataconnections.png b/docs/CROWDIN/it/images/eversenseapp-dataconnections.png
new file mode 100644
index 000000000000..0960be56ae94
Binary files /dev/null and b/docs/CROWDIN/it/images/eversenseapp-dataconnections.png differ
diff --git a/docs/CROWDIN/it/images/update/CI/GitHubActions3.png b/docs/CROWDIN/it/images/update/CI/GitHubActions3.png
new file mode 100644
index 000000000000..ac3f50336128
Binary files /dev/null and b/docs/CROWDIN/it/images/update/CI/GitHubActions3.png differ
diff --git a/docs/CROWDIN/it/images/wearos/ADB03.png b/docs/CROWDIN/it/images/wearos/ADB03.png
new file mode 100644
index 000000000000..63fb435b2f0e
Binary files /dev/null and b/docs/CROWDIN/it/images/wearos/ADB03.png differ
diff --git a/docs/CROWDIN/it/images/wearos/easyfire02.png b/docs/CROWDIN/it/images/wearos/easyfire02.png
new file mode 100644
index 000000000000..e0050e5fc5d8
Binary files /dev/null and b/docs/CROWDIN/it/images/wearos/easyfire02.png differ
diff --git a/docs/CROWDIN/it/images/wearos/easyfire03.png b/docs/CROWDIN/it/images/wearos/easyfire03.png
new file mode 100644
index 000000000000..c1309b7ab89a
Binary files /dev/null and b/docs/CROWDIN/it/images/wearos/easyfire03.png differ
diff --git a/docs/CROWDIN/it/images/wearos/easyfire04.png b/docs/CROWDIN/it/images/wearos/easyfire04.png
new file mode 100644
index 000000000000..a771738aa067
Binary files /dev/null and b/docs/CROWDIN/it/images/wearos/easyfire04.png differ
diff --git a/docs/CROWDIN/it/images/wearos/easyfire05.png b/docs/CROWDIN/it/images/wearos/easyfire05.png
new file mode 100644
index 000000000000..0d8136765a9f
Binary files /dev/null and b/docs/CROWDIN/it/images/wearos/easyfire05.png differ
diff --git a/docs/CROWDIN/it/images/wearos/easyfire06.png b/docs/CROWDIN/it/images/wearos/easyfire06.png
new file mode 100644
index 000000000000..d048886e188d
Binary files /dev/null and b/docs/CROWDIN/it/images/wearos/easyfire06.png differ
diff --git a/docs/CROWDIN/it/images/wearos/easyfire07.png b/docs/CROWDIN/it/images/wearos/easyfire07.png
new file mode 100644
index 000000000000..70bcf2f53a91
Binary files /dev/null and b/docs/CROWDIN/it/images/wearos/easyfire07.png differ
diff --git a/docs/CROWDIN/it/index.md b/docs/CROWDIN/it/index.md
index dfebe1b55206..4dcb9a50a707 100644
--- a/docs/CROWDIN/it/index.md
+++ b/docs/CROWDIN/it/index.md
@@ -5,7 +5,7 @@
```{admonition} Latest Release
:class: note
-14/08/2025 : Version 3.3.2.1 is out. Check the [Release Notes](#latestrelease) to see what's new and get update instructions.
+ 10 April 2026 : Version 3.4.2.2 is out. Check the [Release Notes](#latestrelease) to see what's new and follow the instructions in the [update manual](#UpdateToNewVersion) to update to a the version.
```
@@ -91,7 +91,8 @@ Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
Building AAPS <./SettingUpAaps/BuildingAaps.md>
- Browser Build <./SettingUpAaps/BrowserBuild.md>
-- Computer Build <./SettingUpAaps/ComputerBuild.md>
+- Android Studio Build <./SettingUpAaps/ComputerBuild.md>
+- CLI Build <./SettingUpAaps/CLIBuild.md>
Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
Setup Wizard <./SettingUpAaps/SetupWizard.md>
Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
@@ -149,7 +150,7 @@ AAPS Release Notes <./Maintenance/ReleaseNotes.md>
Documentation updates <./Maintenance/DocumentationUpdate.md>
Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
- Browser Update <./Maintenance/UpdateBrowserBuild.md>
-- Computer Update <./Maintenance/UpdateComputerBuild.md>
+- Android Studio Update <./Maintenance/UpdateComputerBuild.md>
```
@@ -159,6 +160,7 @@ Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md>
General troubleshooting <./GettingHelp/GeneralTroubleshooting.md>
- Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md>
+Profile Tuning Guide <./GettingHelp/ProfileTuning.md>
Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md>
Accessing logfiles <./GettingHelp/AccessingLogFiles.md>
```