Bug report

If you encounter a problem in Juggluco, you can send an e-mail to jaapkorthalsaltes@gmail.com

The e-mail should contain all the information needed to diagnose the problem. Some suggestions:

• Description of problem plus screenshots to illustrate the problem.

• Screenshot(s) of settings (Left menu, Settings)

• Screenshot of Left menu, Sensor (for each sensor) after Juggluco is trying to get a connection with the sensor for at least 20 minutes. Open de Left menu->Sensor immediately before making the screenshot, because the screen isn't updated automatically.

• If alarms give problems, screenshots of alarm settings.

• If Mirror function gives problems, screenshot of Mirror (left middle menu, Mirror).

• When Libreview gives problems, a screenshot of Left menu->Settings->Exchange data->Libreview at least 20 minutes it is turned on or "Get Account ID" is pressed.

• Urls of Android apps with which the sensor does work

• Sensor type

• Sensor id: e.g. 3MH0078YXXW

• Information about phone (Android Settings->About Phone):

  • Phone type

  • Model

  • Android version

  • Build number

• Everything else you consider relevant.

• When Juggluco crashes, logcat is very helpful. To make it, you have to enable developer options on your phone and install adb on your computer. Then from a command shell run: adb shell logcat -d > logcat.txt to generate a general logcat. More helpful is a logcat specific for Juggluco. For this you first have to find out the pid of Juggluco and then press adb shell logcat --pid $PID -d > logcat.$PID where $PID stand for the pid. If you can regenerate the crash, you first start Juggluco then press adb shell pidof tk.glucodata to get the pid. Let Juggluco crash and then press adb shell logcat --pid $PID -d > logcat.$PID or immediately press adb shell logcat --pid $PID > logcat.$PID and keep it running while you let Juggluco crash. Thereafter you can send me logcat.txt and logcat.$PID.