Expose device information in medic-android so we can store it against monthly telemetry readings

[SCdF]

It would be really helpful to be able to add hardware-specific information into our monthly telemetry documents that you can't find out from the browser.

Off the top of my head that could be:

• Phone make and model
• android major version and patch level
• Max and free disk space
• RAM, CPU, GPU (unless that's covered by make and model? Probably best to be explicit)
• Network capacity re: their sim card (this is may be hard because we might just catch them at a bad time or whatever. It would have to be a static truth that was representative regardless of when we compiled it).

This would be exposed to medic-webapp via the JS bridge.

Code links to follow telemetry merge.

[garethbowen]

Telemetry is merged, so let's get this added!

[kennsippell]

From medic/cht-core#5540, some memory metrics for consideration are:

• Runtime.maxMemory
• ActivityManager.getMemoryClass
• MemoryInfo.availMemory
• MemoryInfo.threshold
• Chrome's performance.memory (although they are quantized)

[tookam]

Ready for AT, medic-android: 64-expose-device-info-to-webapp, cht-core: 64-expose-device-info-to-webapp

[ngaruko]

LGTM (storing device info)

The CPU info looks somehow inaccurate though. @wtekeu ?

"cpuInfo": {
          "cores": 0
        }

The downSpeed == upSpeed also looks suspicious !

    "network": {
        "downSpeed": 1048576,
        "upSpeed": 1048576
      }

[tookam]

@ngaruko I changed the way I get the number of cores, please give it a try.

Also, downSpeed == upSpeed == 1048576 because they correspond to the max link speed available for your device and connection type. You are probably using wifi of type AC.

[ngaruko]

Looks better. Thanks @wtekeu