Pazaan/develop basal rates

Pazaan/develop basal rates

Pazaan/develop basal rates

rename bolusApi to bolusEndpoints to be consistant

Add support for getting pump basal rates.

Merge branch 'feature/PR104' of https://github.com/pazaan/640gAndroidUploader into pazaan/develop-basal-rates

Merge branch 'feature/PR105' of https://github.com/pazaan/640gAndroidUploader into pazaan/develop-basal-rates

* develop:
  Make app reading data directly again if triggered by use
  align restart of polling with last known event. It'll try to align with the last poll up to 2h (hardcoded). After that we assume that there is may be a sensor initialisation and restart polling immediately
  branch name can be added to VERSION_NAME
  change chart to GraphView
  change chart to GraphView
  fixing #95

Develop invincible

# Conflicts:
#	app/src/main/java/info/nightscout/android/medtronic/MainActivity.java

Feature/pr104

- cleanup commented out code

- move sgv format conversion to main

- removed need for EHSM pump comms

- removed redundant channel change detection

- removed temporary dbg code

- added single retry for get pump time and status as occasional short lived noise can casue bad comms and retrying once catchs this rather then waiting until next poll

Access Nightscout API via Retrofit

Conflicts:
	app/build.gradle
	app/src/main/java/info/nightscout/android/medtronic/GetHmacAndKeyActivity.java
	app/src/main/java/info/nightscout/android/medtronic/service/MedtronicCnlIntentService.java
	app/src/main/java/info/nightscout/android/upload/nightscout/NightscoutUploadIntentService.java
	app/src/main/res/values/strings.xml

Access Nightscout API via Retrofit

align restart of polling with last known event. It'll try to align with the last poll up to 2h (hardcoded). After that we assume that there is may be a sensor initialisation and restart polling immediately

using a read "pause" has no effect on outcome and likely redundant due to clearMessage intercepting unread messages

changed the hardcoded 500 to use TIMEOUT_MS and set it to 0 while long term testing

If user has double polling set then poll sooner with this error type

 Intercept unexpected messages from the CNL

These usually come from pump requests as it can occasionally resend message responses several times (possibly due to a missed CNL ACK during CNL-PUMP comms?)

Mostly noted on the higher radio channels, channel 26 shows this the most

If these messages are not cleared the CNL will likely error needing to be unplugged to reset as it expects them to be read before any further commands are sent

- user attempts to initiate a poll too close to sensor/pump comms will inform user to wait that poll is due in number of seconds

- app restarted and a poll is requested but close too sensor/pump comms will inform user to wait that poll is due in number of seconds

- startup poll time clash with sensor/pump is detected and auto adjusted

- unavailable SGV from pump due sensor/pump poll time changes/clashes will auto adjust poll time

- ongoing unavailable SGV attempts will start poll time auto adjust and user warned and number of unavailable SGV attempts shown

- missed SGV due to radio channel change avoids EHSM comms reducing the chance of extended channel changes

- occasionly the pump is late with the current SGV and returns the same SGV event as privious poll, this is detected and a new poll is scheduled

Uploading before cnl comms finishes and may cause occasional channel changes due to wifi noise - cnl intent already handles ns upload trigger after all comms finish