Update to a new version or branch¶
Install git (if you don’t have it)
- Any git version should work. For example https://git-scm.com/download/win
- Let Studio know where is git.exe located: File - Settings - Version Control - Git
Update your local copy
- Click: VCS->Git->Fetch
- If you want to change branch select another branch from tray: master (latest release) or another version (please see below)
and then checkout (You can use ‘Checkout as New Branch’ if ‘Checkout’ is not available.)
Updating branch from Github
- Press Ctrl+T, select Merge method and press OK
On the tray you’ll see green message about updated project
Upload to phone
Generate signed apk as described in Building APK
Attention: The dev version of AndroidAPS is only for developers and testers comfortable dealing with stacktraces, looking through log files and maybe firing up the debugger to produce bug reports that are helpful to the developers (in short: people that know what they are doing without being assisted!). Therefore many unfinished features are disabled. To enable these features enter Engineering Mode by creating a file named
engineering_mode in the same directory where you would find the log files. Enabling the engineering mode might break the loop entirely.
The most stable version of AndroidAPS to use is that in the Master branch. It is advised to stay on the Master branch while you complete the Objectives and get practiced at looping.
However, the Dev branch is a good place to see what features are being tested and to help iron out the bugs and give feedback on how the new features work in practice. Often people will test the Dev branch on an old phone and pump until they are confident it is stable - any use of it is at your own risk.
A short summary of some of the changes to old features or development of new features currently in the Dev branch is listed below, and links to any key issues known will be shared (if applicable).
Super Micro Bolus (SMB)
More can be read on Super Micro Boluses (SMB) on OpenAPS docs.
Remember that you are choosing to test a still-in-development feature. Do so at your own risk & with due diligence to keep yourself safe.
You should have run basic closed looping for more than four weeks (having completed Objective 7), and be very aware of all the types of situations in which your APS might fail.
You may need to adjust your settings to allow SMB to work effectively. A good place to start is increasing your max IOB to normal meal bolus + 3x max daily basal. But remain vigilant and adjust settings with care.
As with all updates, previous code has been cleaned, improved and bugs fixed.
If you find a bug or think something wrong has happened when using the Dev branch, then view the issues tab to check whether anyone else has found it, or add it yourself if not. The more information you can share here the better (don’t forget you may need to share your log files. The new features can also be discussed in the gitter room.
If you would like to be up-to-date on the Dev Branch you can use the same steps as already outlined above. You just need to change to the corresponding “dev”-Branch in Android Studio.