jwoglom/controlX2

Issues

• Update to v7.7 Changes Pairing code Format

  #17 opened a month ago by NethCoder
  5

• Install on WearOS Watch Causes Loading Issue

  #16 opened a year ago by NethCoder
  2

• Stuck at stage 3

  #6 opened 2 years ago by diabeticp
  4

• Current status?

  #9 opened 2 years ago by Miquest
  4

• ControlX2 serivce does not initialize when running LineageOS with MicroG

  #15 opened 2 years ago by bathompson
  0

• Use sqlite database for state

  #14 opened 2 years ago by jwoglom
  1

• "Disconnected, reconnecting" gets out of sync with actual connection state

  #11 opened 2 years ago by jwoglom
  0

• Remove requirement for legacy Wear OS comm stack for phone-only operation

  #13 opened 2 years ago by jwoglom
  0

• App requires "Wear OS" Application, despite App already being Installed

  #12 opened 2 years ago by NethCoder
  1

• Dark Mode doesn't Invert the Color of the Mobile Bolus TextViews

  #10 opened 2 years ago by NethCoder
  1

• Evaluate minSdk

  #8 opened 2 years ago by jwoglom
  0

• ControlX2 doesn't see Wear OS app

  #7 opened 2 years ago by diabeticp
  3

• Phone UI: Bolus window shows previous BolusSnapshot state

  #2 opened 2 years ago by jwoglom
  0

• Phone Service: Persistent notification should be of persistent type

  #3 opened 2 years ago by jwoglom
  0

• Nice Work!

  #4 opened 2 years ago by Miquest
  2

• Phone: Require biometrics for bolus confirmation

  #5 opened 2 years ago by jwoglom
  0

• Connection won't last

  #1 opened 2 years ago by JSSSVZ
  9