DHIS2 Android App version 1.1.0 is released


(Marta Vila) #1

Dear DHIS2 Community,

A new version of the DHIS2 Android App is out today.

1.1.0 is a big release for us and we expect it to be more stable than the previous ones. It addresses the problems raised through jira since the last version, plus all the fixes done during the Android academy in December and feedback received until January 21st.

There is no new DHIS2 version compatibility (currently 2.29 and 2.30), we will start working in the compatibility with 2.31 now and will release it during this month (February).

The functional improvements include changes in log in and settings screen, management of reserved id’s, program rules, data entry and many other generic issues!

There are many fixes on log in and settings screen, home screen (program list), tracker program: TEI list & search, TEI dashboard, enrollment & program stages logic, data entry form and program rules.

Check out these Jira lists for more details on the functional improvements and bugs fixed in this version.

As usual, you can read the documentation for detailed information of the functionalities included in the App and how to configure DHIS2 to use it.

Get it on:

  • Google Play (the upload is being processed in Google Play Store and will be available in the next hours)
  • Github (already available)

Remember that, if you need to take screenshots or broadcast your screen for training purposes or demos sessions, there is a Training APK available in Github .

All this information is also available in the Android Section of the DHIS2 web site !

On behalf of the Android team,

(Calle Hedberg) #2

@marta The documentation is silent on the Variable Source Type called “CALCULATED_VALUE”. Is it supported or not?

(Calle Hedberg) #3

@marta Also related to the documentation of what’s supported: For functions in program rule expressions, most rows have a green tick but some are empty (i.e. instead of having the “work in progress” or “not applicable” icon). Examples are d2:count

Does that mean that e.g. d2:count is not and will never be supported (if so, please add N/A to it instead of leaving it blank), or will those expressions be supported in future versions?


Thanks Martha … Surely this will support our scale up of the tracker capture this year …

(Muhammad Salihu) #5

Thanks for this @marta Highly appreciated. I tested this briefly with a 2.30 configuration and discovered the following issues:

  1. For an event program, the program rules for hiding data elements don’t trigger unless you navigate to a new section and return. This is the same with program rules to show error. when they do trigger, they seem to trigger continuously
  2. Data elements are seems to be erased when you navigate away from a section, but appears minutes later. Some never appear
    These happen after successfully completing an event for a short program.
    Android version 4.4.2 (Lenovo tablet) and 5.0 (using genymotion emulator - Samsung Galaxy S6)
    DHIS 2.30 db7bd50

(Muhammad Salihu) #6

Just to follow on my post above, these issues may also be a function of the RAM available for the mobile devices used for testing.

(Marta Vila) #7

Hi @Calle_Hedberg,

thanks for spotting those gaps.
Let us review it and get back to you.


(Marta Vila) #8

Hi @medallion,

thanks for the feedback. Would you mind reporting the two errors in Jira? It could be the RAM indeed, but it could be another thing, we would like to explore it and follow up.


(James Omutsani) split this topic #9

A post was split to a new topic: How to enable selection of colors when creating or editing a Legend

(Magoba Bridget) #10

Thanks @marta for the release,
@medallion, thanks for raising this, am also facing the same problem. This version of the app isnt responding to attributes and data elements hidden through program rules and the same applies to those with warnings.


(Calle Hedberg) #11

@marta I cannot get the app to properly start up (it hangs), but not sure if it relates to my hardware (LenovoPad), software (Android 6.0), the DHIS2 version (2.29), or the database size/design (e.g. orghierarchy has ~14,000 OrgUnits). See JIRA ANDROAPP-1784

So for now I’m unable to do any testing


(Muhammad Salihu) #12

Thanks @marta .
I have logged some issues on JIRA. Pablo is already working on at least one of them


New improvement: https://jira.dhis2.org/browse/ANDROAPP-1785


(Marta Vila) #13

Hi @Calle_Hedberg,

The mobile app should be tested and used with mobile users. Can you try with a user with access to a reasonable number of OU and see if it is still an issue?

(Marta Vila) #14

Hi @smuyambo I think, if you cannot select colors when creating a legend, there must be an error. Have you checked if there is any issue reported?

In any case, this question relates to legends configuration in the maintenance app. @jomutsani can you pelase refer it to right forum?

(Marta Vila) #15

Hi @Calle_Hedberg,

documentation is complete now.

(Calle Hedberg) #16

@marta Thanks for that, and I have just verified that the new app build does work if you log in as a user with only one orgunit set up for data capture. So this is important to note for other users: if you log in as a user with too many orgunits on the capture/edit side, it will fail. I don’t know yet what the practical limits are.

(James Omutsani) split this topic #17

A post was split to a new topic: How do I create a JIRA Account?

(Lusanda) #18

Hi Marta,

I came across a bug where the app automatically pages into a program stage during event synchronization , deletion and scheduling of events: https://jira.dhis2.org/browse/ANDROAPP-1786

I couldn’t upload the video clip when reporting this bug on Jira , will attach it on this reply for your investigation.



(Cha Tum) #19

Hi @dhis2-android,

We were testing the new release and noticed that the program stage sections are not getting hidden properly. There are various program stages where we have multiple program stage sections that hide/show according to the tracked entity attribute (TEA) that the user selects at the time of registration.
Prior to the update, all of the stage sections remained hidden according to the conditions we defined. However, now it seems like the first section is displayed, while the remaining are “hidden.” Could you please kindly advise?

Thank you.

(Marta Vila) #20

thanks @Calle_Hedberg, it should work with more than one org unit… I just added a comment in the documentation warning about the use of the app with users accessing hierarchies of a whole country (over thousand OU’s).