Frequently asked
questions

The landscape glucose graph is Juggluco’s main screen. Touch the display to open the menus.

To read the introduction again, open left menu → Settings → Intro.

No Internet connection or Juggluco account is needed for local sensor reception. The sensor communicates over Bluetooth. Glucose broadcasts to another app on the same phone also work without Internet access.

Cloud uploads and remote following are separate functions. A LibreView account identity can still be needed when taking over a running Libre 3 sensor; see FAQ-019.

Install the compatible logging APK as an update. Do not uninstall Juggluco first. Updating the existing normal installation with its compatible logging build keeps the data.

Reproduce the problem, then save the logs through left menu → Settings → Logging.

Transfer your Juggluco data before stopping the old phone’s sensor connection. Use left middle menu → Mirror → AutoQR, or the ADB transfer procedure in the phone-migration instructions.

1. Transfer the Juggluco data and sensor information from the old phone.
2. Check LibreView settings on the new phone. The ADB transfer includes the credentials; AutoQR/mirroring does not. For Libre 3, keep the activation account ID used for the running sensor.
3. Stop sensor reception on the old phone, then enable left menu → Sensor → Use Bluetooth on the new phone.
4. When the migration connection is no longer needed, remove it through Mirror → select connection → Modify → Delete.

If the sensor information was transferred successfully, a new NFC scan is not normally needed. Forget is not the handover command; see FAQ-082.

CareSens Air uses a different transfer procedure.

Recovery of the complete archive needs an existing copy: for example, data mirrored to another device or saved through ADB.

Rescanning the current sensor does not restore the entire deleted Juggluco archive. Any readings still stored in that sensor are separate from a backup of previous sensors, entered amounts and application data. See FAQ-005 for transferring an existing installation.

As of April 2026, there was no iPhone version of Juggluco, and no iOS version was being developed.

Older suggestions involving emulators were experiments, not a supported way to install Juggluco on an iPhone.

Use separate Juggluco installations with different application IDs for two people, and match the appropriate phone/watch installations.

Do not combine their measurements in one ordinary data set. This is different from overlapping two sensors worn by the same person.

Check which APK variant you installed. A Wear OS package installed on a phone was the cause of one watch-style menu report. In a separate case, the small package omitted the normal glucose notification by design.

Small, mobile and Wear OS packages are not interchangeable just because they install. Check the package before diagnosing notification permissions, a theme problem or a watch-face restriction.

Send the Sensor screen from the device that should receive directly, together with the information needed to reproduce the problem:

1. Sensor type, phone/watch model, Android or Wear OS version, and Juggluco version from Settings → About.
2. How long readings have been missing, whether the phone or watch should receive directly, and which other app/device has used the sensor.
3. The exact message and the steps already tried. Capture left menu → Sensor before rescanning or changing settings.
4. Logs from a compatible logging build when the screenshot is not enough; see FAQ-014.

An isolated error number, an old crossed-out status, or a log ending before the failure is not enough to identify the cause.

First open left menu → Sensor and check whether this is a Bluetooth connection failure or a sensor that is connected but not supplying glucose; see FAQ-011.

For a connection failure, try switching Android Bluetooth off and on, force-stop another app that could be connecting to the same sensor, and reboot the phone. After rebooting, the other app may need to be force-stopped again.

When switching a Libre 3 sensor between apps, rescan it in Juggluco after the other app has scanned it.

If the sensor is connected to an insulin pump or other treatment controller, do not disconnect that controller merely as a Juggluco troubleshooting step.

Allow Juggluco to run in the background and disable battery optimization for it. Granting Android permissions does not necessarily remove battery restrictions: check Android’s app-info and battery settings separately.

Do not silence the Juggluco notification. Bring Juggluco to the foreground temporarily to see whether reception changes.

Also check Update in doze mode, where that option is available under Sensor or Mirror → Doze mode?, and check the phone’s power-saving restrictions. Menu locations can differ between Juggluco versions.

No. A sensor-output problem and a Bluetooth connection problem are different. A sensor can remain connected and exchange Bluetooth traffic without supplying new glucose measurements.

With Libre 3, some invalid measurements are rejected inside the sensor. Juggluco does not receive an ordinary glucose value plus a reliability flag that it could simply ignore.

Check left menu → Sensor to see whether the connection itself is failing or whether the sensor is connected but not producing values. If the sensor itself has failed, Abbott support may be needed.

Distinguish an error during the NFC scan from a Bluetooth connection failure after a successful scan.

Hold the sensor against the phone’s NFC element. Try toggling NFC or rebooting the phone. For the Libre 3 scan messages ending in “Try again,” scan again; report any different persistent message exactly.

For Libre 3, check the activation account ID separately; see FAQ-019. Forget concerns Bluetooth addressing and is not a general fix for NFC errors.

No. Bluetooth status 19 and NFC “ScanError 19” are different errors.

For Bluetooth, status 19 is a disconnect indication; the cause still has to be found. One useful check is whether another app or device is also trying to connect to the sensor. A crossed-out status may refer to an earlier disconnect rather than the current state.

For Libre 1 NFC, ScanError 19 was an exception that required logcat for diagnosis.

When reporting either error, include the exact message, sensor, device and what happened immediately before it.

Install a compatible logging build as an update, without uninstalling. Logging builds are listed in the download page’s bugreport section.

1. Reproduce the problem and allow enough time to capture the failure.
2. Open left menu → Settings → Logging.
3. Save trace.log and logcat.txt.

For a native crash, a log filtered only to Juggluco’s process ID can omit the crash report. Collect full logcat or the crash buffer:

adb logcat -b crash

You can clear or disable logging from the Logging screen without reinstalling. See FAQ-015 for official-app Bluetooth logs and FAQ-127 for crash reports.

To compare a sensor that works in its official app but not in Juggluco:

1. Enable Android developer options and Bluetooth HCI snoop logging.
2. Switch Bluetooth off and on so the logging setting takes effect.
3. Run the official app and reproduce the communication. Do not run Juggluco at the same time, because both apps can interfere with each other.
4. With ADB installed, USB debugging enabled and the phone connected, run:

adb bugreport

Look in the resulting ZIP for btsnoop_hci.log and btsnoop_hci.log.last. One possible location is FS/data/misc/bluetooth/logs; the location can vary.

An Android bug report can contain unrelated private information. Review the files before sharing them. Do not disconnect an insulin pump or other treatment controller just to make this recording.

Disable logging after collecting the diagnostic files, unless it is still needed for a particular investigation. Leaving logging enabled can eventually exhaust storage.

Use left menu → Settings → Logging to disable logging or delete log files. This concerns diagnostic logs, not ordinary glucose readings.

Recognizing the Sibionics code and finding the sensor over Bluetooth are separate steps. If the code scans correctly but the Bluetooth address remains unknown, the problem is Bluetooth discovery.

Check whether a general BLE-scanner app can see the sensor, and collect Juggluco discovery logs. Include the phone model and Android version.

Juggluco 10.7.0 and later again used service-UUID filtering. A Sibionics-specific unfiltered scanner was used for testing on some phones, but it only scanned while Juggluco was in the foreground. Do not install an old test APK as a general fix.

The reproduced April 2026 scanner regression was fixed in Juggluco 10.7.3 or later.

Turning off Settings → Google Scan selects the alternative scanner in this setup. Do not start by clearing Google Play Services data: that can disrupt watch pairing.

Check the exact version and behavior before treating a camera-permission failure or an unsupported code as this regression.

Check two different causes:

1. Permission: on Android 12 or later, missing Nearby devices permission can turn off the setting.
2. Receiver selection: receiving Stream through a mirror can automatically turn off local sensor reception. Change which device receives from the sensor and the mirror direction, rather than repeatedly checking the box.

For a configured Wear OS pair, use Direct sensor-watch connection to select the receiver. Android’s Bluetooth switch and Juggluco’s Use Bluetooth setting are not the same control.

Not necessarily. A crossed-out status can be a previous error. Look at the rest of the Sensor screen, the latest successful connection/reading, and how long values have been missing.

A transient status 133 followed by successful reception is different from an ongoing connection failure. The crossed-out presentation does not mean every status 133 can be ignored; the time sequence matters.

Find the fatal event and its surrounding report, not just any caught exception in a log.

For a native crash, collect full logcat or:

adb logcat -b crash

Filtering only to Juggluco’s process ID can omit the debugger/tombstone report. If the crash is no longer present in ordinary logcat, adb bugreport can also contain tombstone/crash information.

For Libre 2/Libre 2 Plus, enable left menu → Sensor → Use Bluetooth, then scan the sensor with Juggluco at least twice.

If xDrip is already configured to receive from Juggluco, you do not need to configure xDrip again for every new Libre 2 sensor; start the new sensor by scanning it in Juggluco. See FAQ-043.

Libre 3 and pump-linked sensors use different procedures.

No. Juggluco can start a compatible Libre 3 sensor itself. Starting every sensor in Abbott’s app first is not a requirement.

Switching an already-running sensor between Juggluco and Abbott’s app is a separate matter: the activation account identity must match. See FAQ-019 and FAQ-020.

The account-related number used when scanning must match the one used to activate that Libre 3 sensor. For a sensor started in the standalone Libre 3 app while logged in, enter that LibreView account in left menu → Settings → Exchange data → LibreView and retrieve its account ID.

Changing credentials later does not itself change the sensor’s activation identity. Zero or an arbitrary new ID is not a replacement for the ID of an already-running sensor.

The upload account is a different matter. You can upload to a LibreView account that is not associated with the sensor’s activation account ID. Do not change the activation ID merely to change the upload destination.

For a compatible sensor with the correct Libre 3 activation account ID already configured:

1. To move to Abbott’s standalone Libre 3 app, terminate that sensor in Juggluco, then scan it in Abbott’s app as a new sensor.
2. To return to Juggluco, force-stop Abbott’s app and scan the sensor again in Juggluco.

Scanning supplies the information needed by the app that takes over the sensor; the two apps do not share one permanent connection.

This procedure is for the standalone Libre 3 app, not the combined Libre by Abbott app. See FAQ-021. If the activation account ID is unknown or wrong, see FAQ-022.

Do not assume instructions for the standalone Libre 3 app also work with the combined “Libre by Abbott” app.

In the US versions examined in 2026, the combined app (com.abbott.adc.freestyle.libre.us) used a different account-related number during NFC activation from the standalone Libre 3 app (com.freestylelibre3.app.us). A sensor started by the combined app could therefore not be taken over with the normal standalone-app procedure.

As of September 2026, the Netherlands version was still being investigated. When reporting this problem, include the exact app/package, country and which app started the sensor.

If a running Libre 3 sensor was started in Abbott’s Libre 3 app without signing in to LibreView, the normal Juggluco account-ID takeover procedure does not work. Signing in afterward does not change the identity that was already sent to the sensor when it was started.

A root-based procedure can recover the required identity from the phone. Simply entering a different LibreView account and rescanning is not sufficient for this situation.

Open left menu → Photo and scan the data matrix on the applicator. This is a camera scan, not a Libre-style NFC scan.

Supported Dexcom G7/ONE+ sensors can be started from Juggluco; they do not first have to be activated in Dexcom’s app. If scanning fails, report the exact message and provide a clear photo of the code.

Recognition of a code for a different Dexcom product, such as Flex, does not by itself mean that product is supported.

Do not use Juggluco and the official Dexcom app as simultaneous receivers for the same G7 or ONE+ sensor. Switching between the apps is different from keeping both connected.

Running Juggluco on Wear OS does not create an additional Dexcom “watch slot”; it uses the same type of sensor connection as the phone version.

No. Different Sibionics sensors sold as GS3 can behave differently. Juggluco added GS3 support in 10.9.0, but later GS3 variants were found with differences in code/NFC recognition and Bluetooth communication.

If a GS3 variant does not work, provide the exact data matrix, NFC content, product/market identity, firmware if available, Juggluco version and what happens after scanning. If necessary, Bluetooth logs from the official app can be compared with Juggluco; see FAQ-015.

A successful code scan only proves that the code was recognized; it does not prove that Bluetooth glucose reception is supported for that variant.

Yes. Juggluco can use more than one supported sensor at the same time. You can scan a new sensor before the old one ends. A Bluetooth reset can occasionally be needed.

This also applies when the supported sensors are different Libre types; adding a Canadian Libre 2 or Libre 3+ does not switch the whole application into a global “North American mode.” Each sensor still has its own activation/takeover requirements.

For readings from two different people, use separate Juggluco installations instead of mixing the data; see FAQ-086.

For FSL 2+ EU 301, a separate press on Terminate is not needed at normal end of life.

When that sensor stops sending near its lifetime limit, rescanning can make the additional 12 hours available, giving 15.5 days in total. After that, a scan reports “Sensor definitely terminated” and Juggluco stops using the sensor’s Bluetooth connection.

This applies to that Libre 2 Plus variant at normal end of life. A sensor that fails early or a different Libre variant can behave differently.

Do not run the official Sibionics app and Juggluco as two independent receivers for the same GS1 sensor. One app can receive stored readings requested by the other, which can leave gaps in the other app.

Before using Juggluco, disable the official app’s sensor connection. To switch back, clear left menu → Sensor → Use Bluetooth in Juggluco. You do not need to delete either app or its data.

For GS1, stored readings are sent before the current reading after reconnection. They are not the separate Libre sensor-stored series that Juggluco labels History. Later Sibionics variants can behave differently.

For Libre sensors, a device without NFC can receive by Bluetooth after another NFC-capable phone has scanned the sensor and transferred the sensor information to it.

Use Juggluco mirroring to transfer the sensor information, then switch direct Bluetooth reception to the non-NFC device. For Libre 3 activation, the NFC-capable phone must run at least Android 8.

This is a Libre procedure. Dexcom G7/ONE+ uses a camera-scanned data matrix instead of NFC.

A Libre 3 sensor started with Abbott’s physical reader cannot be moved to Juggluco through the normal LibreView account-ID takeover procedure.

The physical reader is different from Abbott’s standalone Libre 3 Android app. Switching between the Android app and Juggluco uses the activation identity explained in FAQ-019 and FAQ-020.

This answer is specific to Libre 3 and Abbott’s physical reader.

A sensor working with CamAPS FX or Omnipod does not automatically mean it can also be used by Juggluco at the same time.

For CamAPS FX, the activation identity differs from the ordinary Juggluco setup, and the proposed emulation also runs into signing/authentication restrictions. For Omnipod 5, compatibility was still unknown in the available information.

Do not disconnect an insulin pump or other treatment controller simply to test Juggluco.

The four-digit Dexcom PIN is not unique. Juggluco uses the full scanned data matrix to identify the sensor.

Use Photo to scan the code on the applicator; see FAQ-023. A sensor with a similar name or the same style of PIN can still be a different variant that Juggluco does not support.

Not necessarily. A Dexcom G7 normally disconnects after sending a glucose value and reconnects for the next five-minute reading.

Judge the connection by whether the expected readings arrive. A disconnect after each value is normal for this G7 connection pattern; long gaps between expected readings are not.

Forget removes the remembered Bluetooth device address. It is not the handover command for moving reception to a new phone.

To stop the old Juggluco installation receiving from the sensor, use Terminate in Sensor or turn off Use Bluetooth, as appropriate to the transfer procedure. Earlier sensor-selection instructions also describe selecting a terminated sensor again by scanning it.

Keep a copy of the archive before migration; see FAQ-005.

For Accu-Chek SmartGuide:

1. Activate the sensor with the official app first.
2. Stop the official app from competing for the sensor connection.
3. In Juggluco, use Photo to scan the data matrix on the applicator’s blue cap.

If the sensor is already activated, Juggluco does not start another sixty-minute activation period. These instructions reflect the SmartGuide setup available through June 2026.

Provide the exact product identity, not only the brand or marketing name. Useful information includes the data matrix, NFC content, GTIN, Bluetooth name when requested, and the Juggluco and official-app versions.

Aidex and Sibionics reports show why similar names or packaging are insufficient: related products can require different recognition or communication. Successful scanning is only one stage; receiving glucose still needs to be demonstrated.

Do not configure two simultaneous direct Bluetooth receivers for the same Libre sensor. Receive on one device and distribute the readings through mirroring instead.

To move direct reception, deliberately switch the receiver and the mirror’s Stream/Receive from direction. For a configured Wear OS pair, use Direct sensor-watch connection.

This is different from using two separate sensors, and it does not provide automatic room-to-room roaming between phones.

No. For Libre, Juggluco establishes a Bluetooth connection and enables notifications. The sensor then sends readings over that connection. If the connection is lost, Juggluco reconnects.

A healthy Libre connection does not have to be rebuilt for every reading. This differs from Dexcom G7, which normally disconnects after a reading; see FAQ-081.

It depends on the Libre generation.

• Libre 3: five-minute sensor-stored readings are available from sensor start, and recent one-minute readings can cover approximately the preceding two hours.
• Libre 2: an NFC scan can retrieve fifteen-minute sensor-stored readings for the preceding eight hours, plus the current scan value. It cannot recreate every missed one-minute Stream reading.

Juggluco calls the sensor-stored series History in parts of its interface and API. Sensor-stored readings are not a backup of all Juggluco data, and a sensor error can still leave missing or invalid measurements.

On the phone, open left menu → Watch → WearOS config and select Direct sensor-watch connection. Start Juggluco on the watch and inspect left menu → Sensor there.

Use WearOS config rather than manually changing several Bluetooth settings. It selects whether the phone or watch is the device that connects directly to the sensor.

The sensor-to-watch connection and the phone-to-watch mirror are separate. With Dexcom G7/ONE+, changing which device receives directly can take around 20 minutes before the new connection is established.

Check that the watch’s companion app on the phone is actively connected to it. A saved Android Bluetooth pairing is not the same as an active Wear OS companion connection.

If you built Juggluco yourself, also make sure the phone and watch APKs use compatible application IDs, build variants and signing keys. A self-built watch APK may not communicate correctly with a separately signed distributed phone APK.

First identify which link has failed. If the watch displays values received from the phone, that shows the mirror works; it does not show that the watch can receive directly from the sensor.

After selecting direct reception, bring Juggluco to the foreground on the watch and inspect its Sensor screen. Temporarily turning phone Bluetooth off can break the old sensor connection; toggling watch Bluetooth can reset the watch’s Bluetooth state. Allow time for a connection attempt before saving the screen.

If the watch has current readings but the phone does not, investigate the watch-to-phone mirror instead. Sync/Reinit are mirror troubleshooting controls. Recreating a working mirror does not fix sensor reception, and initialization/default resets can resend data and delay recovery.

No. Turning phone Bluetooth off is a temporary handover step, not a requirement to leave it off.

With Watch → WearOS config set for direct watch reception, Android Bluetooth can be enabled again. Check that Sensor → Use Bluetooth is off in the phone’s Juggluco installation. The Android Bluetooth switch and Juggluco’s sensor-reception setting are different controls.

No. The sensor connects to the watch through Bluetooth, not LTE. LTE can provide a separate network path for sharing readings while the watch is away from the phone.

With Dexcom G7, readings can be sent back to the phone again when the watch is within Bluetooth range. Live sharing while the watch is away requires a separate working network/mirror connection; see FAQ-090.

Start Juggluco itself on both the watch and phone, not only the watch face. Reinstalling a watch-face app is different from reinstalling Juggluco.

If Juggluco itself was uninstalled and reinstalled on the watch, remove the phone’s old connection to the previous watch installation in left middle menu → Mirror, then establish the connection again.

Check left menu → Settings → Calibration → Active on the watch. Enable it if you want the watch to display the calibrated value.

If the phone still shows a different value, compare the calibrated and uncalibrated values on both devices before assuming the difference has another cause.

For a Galaxy Watch 8 running the normal package tk.glucodata, the ADB command is:

adb shell pm grant tk.glucodata android.permission.SYSTEM_ALERT_WINDOW

This grants the floating-display permission to that package. If you installed a package variant with a different application ID, the package name in the command must match that installation.

First check which Juggluco APK and which watch-face generation you are using.

From 2026, newer Juggluco watch faces were distributed separately using Watch Face Format instead of relying only on the older face bundled in the Wear OS APK. On suitable older watches, the legacy face can still be installed with a Wear OS APK containing it. Another option is a watch face with a compatible SMALL_IMAGE complication slot.

There was also an older packaging difference: 8.0.24-small did not contain the Juggluco watch face, while that release’s Wear OS package did. If a phone itself shows watch-style menus, check that the Wear OS APK was not installed on the phone.

On the phone, open left menu → Sensor → select the sensor → Terminate.

The change should synchronize to the watch, but you may still need to press Sync. You do not first need to move the Dexcom G7 connection back from the watch to the phone.

Enable left menu → Watch → Watchdrip in Juggluco, then configure Watchdrip itself to connect to the Amazfit GTS 4.

This is different from the Wear OS direct sensor-watch setup. Juggluco must still be receiving glucose normally before Watchdrip can forward it.

On the older Juggluco watch face used on Galaxy Watch6, long-press the face → Customize → Heart rate.

That face uses the Wear OS heart-rate interface rather than Samsung’s separate heart-rate complication. Newer Watch Face Format faces can have different options; see FAQ-034.

Update both phone and watch when a Juggluco release changes the communication between them. Not every small update requires both sides to change, but the two installations must remain compatible.

For self-built versions, use the correct wear build for the watch and make sure phone and watch use compatible application IDs and signing keys.

WearOS config only lists Wear OS devices that use Google Play Services’ wearable interface. An ordinary Android watch is not automatically a Wear OS watch.

If the non-Wear-OS device can run Juggluco, configure it as an ordinary mirror device instead. Wear OS-specific features such as the Juggluco watch face are not provided by that manual mirror connection.

Check which watches the companion app has actively connected, not only which watches are saved as past pairings.

On Samsung phones, the watch currently active in Galaxy Wearable can affect which watch Juggluco can select. A setup using different companion apps can behave differently.

A saved Bluetooth pairing alone does not make a watch selectable in WearOS config.

No. Direct sensor reception and Internet mirroring are separate connections.

LTE can give the watch Internet access, but you must still configure a mirror connection to a reachable phone or Juggluco server. The normal companion Bluetooth/Wi-Fi connection does not automatically create a remote Internet mirror.

If the watch that normally receives directly from the sensor is unavailable, you can temporarily make the phone the receiver:

1. On the phone, enable Use Bluetooth.
2. In the phone’s mirror connection for the watch, uncheck Receive from and check Stream, so the phone sends readings to the watch rather than expecting them from it.
3. When the watch returns, uncheck Stream in that phone mirror connection. Turn off Use Bluetooth on the watch, or toggle Direct sensor-watch connection on and off on the phone once the watch is connected again.
4. Use Direct sensor-watch connection to restore the watch as the direct receiver. An off/on toggle may be needed.

Do not leave both devices configured to connect directly to the same sensor.

Check the watch lock’s Hide information privacy setting. When enabled, it can hide the glucose value while the watch is locked.

If the value is also missing when the watch is unlocked, check sensor reception or the phone/watch mirror instead.

The slot must accept the complication’s data type, such as short text or an image. Similar-looking slots are not necessarily interchangeable.

An adjustable complication text size was added in 9.0.1. Earlier advice that size depended only on the slot predates that setting.

A third-party watch face still needs a compatible slot; changing the text size cannot add an unsupported data type.

Use Now clamp, available from 7.4.5, to keep the current reading/time visible instead of letting the graph scroll past it.

Older workarounds were to leave more empty time range or use Floating glucose.

Enable Manually scale Glucose.

Move up/down in the upper half of the display to adjust the upper glucose limit. Move up/down in the lower half to adjust the lower limit. Vertical pinch-to-zoom is not the control for this.

For a compatible Libre setup, use left menu → Settings → Exchange data → LibreView to upload readings and share them through LibreView.

For a local report instead, enable the Web server, then use left middle menu → Statistics → Save and send the saved report to the clinic.

Export → LibreView creates a file in LibreView format. It does not upload that file to Abbott. A separate Glooko import route can use the file; see FAQ-116.

Open Settings → Exchange data → LibreView → Send amounts, and assign the appropriate LibreView category to each Juggluco label you use.

The name of a label does not determine its upload category. A missing insulin/carbohydrate entry or a blood measurement appearing as carbohydrates can result from this mapping.

LibreView categories, calibration-label selection and insulin/IOB categories are separate settings.

As of June 2026, Juggluco could upload to LibreView but could not download glucose values from LibreView or act as a LibreLinkUp client.

To receive readings from another Juggluco installation, use left middle menu → Mirror, for example Auto QR. See FAQ-042.

As of September 2026, Juggluco did not upload Dexcom readings directly to Clarity, and Dexcom ONE+ readings were not uploaded to Abbott’s LibreView service.

Use Statistics → Save for a local report, or Export → LibreView to create a file in LibreView format. That file can include Dexcom/Sibionics readings without sending them to Abbott.

The Glooko import route documented in June 2026 imported the sensor readings from that file but ignored insulin and carbohydrate entries.

LibreView and the phone graph can be using different data series. Seeing Stream readings on the phone does not mean that the corresponding sensor-stored readings have been obtained and uploaded.

On watches/sensors that have the option, enable Bluetooth history to obtain readings stored by the sensor. Juggluco calls that series History in the interface. Displaying History in the graph is a separate setting in the right middle menu.

In LibreView-format exports, record type 0 represents the sensor-stored/History series and type 1 represents individual Stream readings. If you are using an old version affected by the 2024 backfill bug, update past 9.0.12, where that specific bug was fixed.

Open left menu → Settings → Exchange data → Uploader and enter your Nightscout server address, including its port when required.

Use the authentication for the Nightscout API you selected:

• V1: the server’s API_SECRET.
• V3: an Access Token with write permission.

See FAQ-111 for details. The uploader sends data to a separate Nightscout server; enabling Juggluco’s own web server is a different function.

Enable Settings → Exchange data → Web server → Active. Leave the view and return to check whether Juggluco reports an error. On the phone itself, use:

http://127.0.0.1:17580

For another device on the home network, uncheck Local only and replace 127.0.0.1 with the Juggluco phone’s network address/hostname; Mirror shows the wlan information.

If an API secret is configured, use the authentication format required by the endpoint you are calling. Do not expose the web server publicly without authentication. If another app such as xDrip Web Service is already using the same port, see FAQ-120.

Use a Mirror/Clone connection between the two Juggluco installations. Start with left middle menu → Mirror → Auto QR.

The receiver should also receive Scans, which carries information obtained by NFC/camera scanning. Receiving mirrored readings can switch off Use Bluetooth on the receiving device to avoid two devices competing for the same sensor.

Decide which device should receive directly before re-enabling sensor Bluetooth. A temporary migration connection and an ongoing follower connection serve different purposes.

Juggluco’s local calibration and its LibreView upload are separate things.

Newer Juggluco versions can use calibrated Stream readings and calibrated sensor-stored readings (the series called History) in local statistics and web output. That does not mean LibreView receives those same calibrated values.

If LibreView and Juggluco differ, first compare the same data series. The available support information does not say that calibrated sensor-stored readings are uploaded to LibreView. See FAQ-101 for local calibration/statistics settings.

No. A FileNotFoundException does not by itself mean the API secret is wrong. Check the server URL, trailing slash, port, selected API version, authentication and the actual server response.

For Nightscout V3, use an Access Token with write permission; see FAQ-111. A wrong server/path can produce a similar exception.

If the problem appears only with a particular network path, such as a hotspot, also test another network before changing credentials.

Use a LibreView account, not simply an account for a national Abbott shop or FreeStyle website. A login that works on an Abbott website may still be a different account system from LibreView.

Select RU only when the LibreView account uses the Russian libreview.ru service. It is not a general login or connection fix.

If the sensor was started with the combined Libre app, a correct LibreView login does not solve the different activation identity; see FAQ-021.

The Nightscout uploader sends at most 30 days of stored readings in the documented December 2025 behavior. It is not intended as a way to upload an entire multi-year Juggluco archive.

Older data that is still stored in Juggluco can be read through the local web server. That is a separate interface from the Nightscout uploader.

Use the credentials for the API you selected:

• V1: the Nightscout server’s API_SECRET.
• V3: an Access Token with write permission, as specified for the corrected V3 authorization route.

Switching an existing upload between V1 and V3 can create duplicates because the identifiers differ. A FileNotFoundException can involve authentication as well as the path; check the actual server response. Use your own credentials; do not copy example secrets from GitHub.

No. Nightscout can receive the reading even when the identifier returned by the server differs from Juggluco’s identifier.

Check whether the expected readings actually appear on the Nightscout server. If they do, the identifier message alone is not an upload failure.

“Tried nothing” can mean there was no new data to send. It does not necessarily mean that a request failed.

Check that the uploader is active and saved, that new readings exist, and whether Send now/resend has anything to process. A manual change to the device clock can also affect which readings Juggluco considers already handled.

The final check is whether the expected data reached Nightscout.

First check whether readings are still arriving in the old LibreView account.

For the stale-account problem fixed in August 2026, use Juggluco 10.9.9 or later. Temporarily change the configured LibreView email address and press OK, then restore the correct address and press OK again. Use Change start separately if you need to change the period that is uploaded.

This refreshes the upload account. It does not change the activation account ID already stored in a running Libre 3 sensor; see FAQ-019.

The upload device ID identifies an app installation/uploader. It is generated, saved and reused across sensor changes.

The sensor serial number identifies the individual sensor. Neither is the same as the Libre 3 activation account ID. A difference between these identifiers is therefore expected.

Yes. Enable the Web server and use Statistics → Save to make a local report.

You can also use Export → LibreView to create a LibreView-format file containing Dexcom or Sibionics data. That file can be imported by software that supports the format, such as the Glooko workflow documented for these versions. Creating the file does not upload those sensors to Abbott’s LibreView service.

The extras/setvalue code posted in a 2024 discussion was not included in stock Juggluco.

Juggluco’s web server can read entered amounts. Amounts can be entered through Juggluco itself, through supported manual/Kerfstok input, or by NovoPen scanning, and can be mirrored between Juggluco installations.

This FAQ does not document a stock HTTP endpoint for writing new amounts.

Use one of Juggluco’s existing read interfaces:

• a glucose broadcast when an Android app needs each new reading;
• the web server when a program or network device needs to query data.

Examples include:

/x/stream
/x/amounts

An ESP32 or MQTT bridge can query the web server and then display or republish the data. Juggluco itself does not provide a built-in MQTT publisher in the versions covered here.

From another device, 127.0.0.1 refers to that other device, not to the Juggluco phone. Use the phone’s reachable network address and configure authentication.

Specify how many entries you want in the Nightscout-compatible query, for example:

/api/v1/entries/sgv?count=10000

That count limits the response, not the amount of data stored in Juggluco.

For the separate sensor-stored-readings interface, use for example:

/x/history?days=1

The API keeps the name history, but this endpoint refers to the readings stored by the sensor. Sensor-stored readings and Stream are different series.

Check the exact host, port and response. Only one service can listen on a port. If xDrip Web Service is using the port that Juggluco should use, disable the xDrip service or change the configuration.

Test a known Juggluco endpoint locally on the phone first. If you receive Path not found from another service, changing Juggluco settings will not fix that response.

Do not rely on Local only instead of authentication.

A 2024 Juggluco web-server configuration allowed a visited website to access local data when no API secret was set. The following update required an API secret longer than seven characters.

Use an API secret and do not expose the Juggluco web server directly to the public Internet.

Check the selected data series, date/end position and number of days, and confirm that the save operation reported success.

Compare the same period through the web interface, for example:

/x/stream?header&days=1

If you are using server version 8.1.1, update to 8.1.5 or later because 8.1.5 fixed a specific empty-export bug. On newer versions, investigate the selected period and the file picker/save operation instead.

In Juggluco, select the xDrip app under Settings → Exchange data → EverSense broadcast. In xDrip, choose 640G/EverSense as the hardware data source.

Once configured, start each new Libre 2 sensor by scanning it in Juggluco; xDrip receives readings from Juggluco.

EverSense broadcast for xDrip is different from xDrip broadcast for receivers such as AAPS. See FAQ-045.

Check which broadcast xDrip receives.

With patched Libre broadcast, xDrip can combine/average older readings into a five-minute value. During a rapid change, that value can therefore lag behind Juggluco’s current value.

With EverSense broadcast, that averaging is avoided in the documented setup, although xDrip still normally displays one value every five minutes.

If the difference is not explained by that, compare timestamps, calibration and the selected data series. A recovered sensor-stored reading is also not the same thing as a missed Stream reading. See FAQ-098 for arrow/rate differences.

Use left menu → Settings → Exchange data → xDrip broadcast to send Juggluco readings to AAPS.

This is different from EverSense broadcast, which is used to feed xDrip itself. This setting only selects Juggluco’s output; configure AAPS itself separately.

Use a glucose broadcast when another Android app needs each new/current reading. Use Juggluco’s web server when the other program needs older readings, backfill or entered Amounts.

A broadcast only supplies new/current values; it is not a way to request the older archive. See FAQ-118 for web-server examples.

First open Settings → Calibration, select the label that represents blood glucose, and enable calibration where required. Then enter the meter reading under that label through left middle menu → New amount.

Supported Bluetooth meters can also be selected under Settings → Exchange data → Glucose meters.

To exclude a blood measurement from calibration, mark the measurement excluded and press Save. Deleting only a derived calibration point may leave the underlying measurement included.

Check the selected sensors and data series in the right middle menu. Juggluco can show sensor-stored readings (History), uncalibrated Stream and calibrated Stream. A second sensor can add another curve.

In the interface where two checkmarks surround Stream, the checkmark before Stream controls calibrated values and the one after Stream controls uncalibrated values. Newer versions can also use calibrated sensor-stored readings.

Curve colors do not have a fixed meaning; see FAQ-051.

In the May 2026 interface explanation, the older Calibration box had been replaced by checkmarks before Stream, Scan and History (the sensor-stored readings series).

Use the controls in your installed version. Some older translations and tutorials predate calibration or later display changes; an outdated screenshot does not mean that the feature is missing.

Sensor-stored readings and Stream readings have different sampling intervals. Juggluco calls the sensor-stored series History in this interface.

• Libre 2 sensor-stored readings: one sample every 15 minutes.
• Libre 3 sensor-stored readings: one sample every 5 minutes.

Statistics can use either series, so selecting sensor-stored readings produces fewer samples than selecting one-minute Stream readings.

Curve colors change between sensors. Red, purple or another color therefore does not have one fixed meaning.

Long-press the curve, or open left menu → Sensor → Info, to see the sensor’s start and end dates. The current sensor’s end date can also appear at the right side of the main graph.

Under Settings → Number labels, set the blood-glucose label’s Weight to 1.

Weight 0 displays an entry as a number at a fixed height. Weight 1 displays a square whose height is determined by its value.

This changes the graph presentation. It does not change the measured value or select the label used for calibration.

No. An NFC scan cannot recreate missed one-minute Libre 2 Stream readings. It can retrieve the current scan value and readings that the sensor stored internally. Juggluco calls that stored series History.

For Libre 2, the sensor-stored series contains fifteen-minute samples for the previous eight hours and is delayed relative to the current Stream. Filling a gap with those stored samples does not mean the missing one-minute Stream values were recovered.

Libre 3 stores a different series: five-minute sensor-stored readings are available from sensor start. See FAQ-132.

A numeric rate and a categorical trend label are different representations. Juggluco can draw intermediate arrow angles using its configured threshold, while Libre’s text labels divide rates into broader categories.

For example, a rate near -0.97 can exceed a Juggluco arrow threshold of 0.8 while still falling inside Libre’s STABLE category. A tilted arrow and the word STABLE can therefore refer to the same rate.

The web label is STABLE; an older documentation table that said STEADY was corrected.

Bring the graph to the current time, open Statistics, and select 1 day.

The end position matters: one day while viewing an earlier point selects a different period. When comparing results, use the same Stream or sensor-stored-readings series and calibration settings.

The 50% band covers the 25th to 75th percentiles. The 90% band covers the 5th to 95th percentiles. The median is the 50th percentile, and the full outer range is the 100% envelope.

These describe the spread of the selected measurements. They are not confidence limits for a future glucose value or clinical alarm thresholds. Another report may use different data or settings.

Compare the same data series and calibration settings, including Calibration → Active and Apply to past.

The web server provides separate statistics queries for sensor-stored readings (called history in the API) and Stream:

/x/stats?history
/x/stats?calibratedhistory
/x/stats?stream
/x/stats?calibratedstream

In August 2026, adding &pastvalues did not change every rendered curve/summary graph because those renderers followed the app setting. A special 10.10.0-PastValues test build was used for that investigation; it was not a normal release instruction.

A daily-report time-window bug was fixed in Juggluco 10.9.9.

On an affected older version, the temporary workaround is Display → Manually scale → Time and set the report range to 00:00–00:00 before saving. You can undo the temporary display setting afterward.

If you already use 10.9.9 or later, check the selected report time range instead of applying this workaround.

Recreate the labels in the same order. Historical amounts are associated with a label’s position, not permanently with its name.

Restoring a familiar name at a different position does not restore the original mapping. For calibration, also select the intended Blood measurement variable.

Avoid casually reshuffling labels in an existing archive. This repairs label meaning; it does not recover amounts that were actually deleted.

The NovoPen priming filter skips a dose of 2 units or less when it occurred less than 1 minute before another registered dose.

It does not remove every dose of 2 units or less. When a small dose appears to be missing, check the time and the following recorded dose.

For Contour Next One, Juggluco can use the data-matrix scan. For other supported Bluetooth meters, use Settings → Exchange data → Glucose meters → Find devices, with pairing where required.

A meter should not be connected simultaneously through another app such as xDrip or the meter manufacturer’s app. If a meter does not appear in Juggluco’s supported-device search, this FAQ does not imply that it is compatible.

To display a manual blood value at its glucose height, set the Blood label’s Weight to 1; see FAQ-052.

Calibration belongs to the CGM sensor, not to the blood glucose meter. Measurements from two meters can use the same Blood variable; switching meters does not select a separate calibration.

Label Weight = 1 only changes where blood measurements are drawn on the graph.

Juggluco uses structured number labels and meal components, not arbitrary free-text notes.

As documented through February 2025, you can define up to 40 number labels for recurring categories. Under a carbohydrate label in New amount, choose Meal to enter food components.

Changing the order of existing labels can change how old entries are interpreted; see FAQ-103.

Juggluco sends glucose to Health Connect in mg/dL. Health Connect or another app can choose a different unit for display.

If the displayed unit differs from Juggluco, first check the unit setting in the receiving app. Compare both the numeric value and its stored unit before treating it as a conversion error.

As of May 2025, Juggluco’s Health Connect integration was one-way: Juggluco sent data to Health Connect but did not import Health Connect data back into Juggluco.

For another app to receive the values, check both steps separately: Juggluco → Health Connect and Health Connect → receiving app, including the receiving app’s permissions.

Change the time zone, not the device’s underlying clock time. Juggluco stores timestamps on a time-zone-independent basis; the displayed local time changes with the selected zone.

Manually shifting the clock itself can make measurement timestamps wrong. Changing time zone does not require resetting a special “last sent to xDrip” timestamp in Juggluco.

If another receiving app behaves incorrectly after travel, troubleshoot that app separately.

Check the alarm’s minutes deactivated setting. If it is 0 and the low/high condition remains true, the alarm can sound again on every new reading.

Also check Android’s notification sound settings and Watch → Notify. The alarm condition, repeat/deactivation interval and Android notification channel are separate controls.

On the watch: touch the notification or watch-face complication, or start Juggluco.

On the phone lock screen: use Off on the glucose notification. If the button is missing, check Settings → Glucose notification and whether Android has made that notification silent.

Stopping the current alarm does not stop it from triggering again later if the alarm condition remains true.

A watch can also show a phone alarm forwarded through Galaxy Wearable or Juggluco’s Separate notification setting. That forwarded notification is different from an alarm generated by Juggluco on the watch itself.

Talk settings belong to the active profile. Activate the profile you want, open left middle menu → Talk, and enable Speak alarms. The “alarm is” settings can also affect behavior during Do Not Disturb.

If the voice list is empty, check Android’s text-to-speech engine and installed voice data. On Samsung devices, selecting Google’s text-to-speech engine can provide a different set of voices.

The notifications can have different purposes. One persistent notification keeps Juggluco running in the background. A separate new notification can be needed by watch companion apps that forward new notifications but do not forward updates to an existing one.

Text such as “Runs to connect sensor” or “Runs to exchange data” describes why the foreground service started. It is not itself a live failure report. Check current readings and the Sensor/Mirror diagnostics.

The widget’s time shows how old the last reading is. If Juggluco is killed, the widget can remain visible with the last old value, so check the time before assuming readings are still arriving.

Floating glucose has an option to hide its time. The floating display disappears when Juggluco is killed.

Bring Juggluco to the foreground and hold the back of the pen against the phone’s NFC element. Keep it there long enough for the transfer; a pen scan can take longer than a CGM scan.

Note any beep or exact error. Try toggling NFC or rebooting the phone, and test whether another NFC object produces any response.

Juggluco may no longer appear in Android’s app chooser when a pen is scanned, but scanning still works from inside Juggluco.

If only small doses are missing, check the NovoPen priming filter instead; see FAQ-104.

As of June 2026, Juggluco did not have a built-in insulin-use statistics screen.

If LibreView amount uploads are configured, LibreView can show some insulin totals. For your own processing, Juggluco’s web server exposes entered amounts at:

http://127.0.0.1:17580/x/amounts

For access from another device, use the phone’s reachable network address instead of 127.0.0.1 and configure the required authorization.

Select the app language through Settings → Display → Language.

Number labels are different: the initial labels are created in the device language at installation and then become user-editable labels under Settings → Number labels. Changing the app language does not replace them with new translated defaults.

Historical amounts use the label’s position, not just its name. Renaming, deleting or re-adding labels can change how old entries appear. Recreate labels in the same order when repairing a changed mapping; see FAQ-103.

Use a scheduled switch to another profile so that a temporary alarm profile automatically changes back later.

This is profile scheduling; it is not a one-tap “snooze this profile for 60 or 90 minutes” control.

Use the alarm’s enable/disable control under left menu → Settings → Alarms. A disabled alarm does not trigger, so you do not need to move its threshold to an extreme value.

Under Ringtone, sound duration, ringtone, vibration and flash can be configured separately. Disabling an alarm is different from stopping an alarm that is currently sounding or changing its repeat interval.

Check Value available. It can vibrate or sound when readings return after the configured no-value interval; twenty minutes is the default documented in the March 2026 answer. Its sound/vibration settings are separate from the high/low alarms.

Also check Android’s glucose-notification channel and watch-notification settings, which can produce their own vibration.

The Alarm is alarm setting selects Android’s alarm audio stream. When it is not set, Juggluco uses ringtone volume. Press Save after changing the setting.

The Disturb option and Android’s Do Not Disturb policy are separate settings. Speaker/headphone routing can also depend on the Android device.

After starting a new sensor, Juggluco can open the calendar app so you can create one or more reminders for the sensor’s end date.

These are ordinary calendar reminders. They are separate from Juggluco’s low, high and no-value alarms.

This calendar workflow was documented in May 2023.

If a .java file contains only a relative path instead of Java source, it may actually be a symbolic link whose link information was lost when the source tree was copied or unpacked.

ZXing.java was one such file. Clone the repository in a way that preserves symbolic links, or replace the broken file with the content from its link target.

If the first compiler error is elsewhere, investigate that error separately; not every missing source file is a symlink problem.

Use the build files and build variant from the same source checkout, then start with the first real compiler or linker error rather than the final Gradle/Ninja summary.

Past build failures have had different causes: missing files, symbolic links unpacked incorrectly, or native libraries that did not match the source/APK version. The July 2026 host build of rtlpp, for example, needed ICU::uc / ICU::i18n.

Do not copy old absolute paths from another developer’s build. Windows support also changed over time, so use the instructions and Gradle files from the checkout you are building.

Phone and Wear OS builds use the same project source. Select a wear build variant rather than mobile.

In the March 2024 example, release2 was a release variant with .debug added to the application ID. It was not necessarily the same installation identity as the distributed app.

Check Common/build.gradle in your checkout for its actual variants. App identity and signing compatibility also affect phone/watch communication.

Use the repository that owns the text you want to change:

• Website: j-kaltes/j-kaltes.github.io.
• In-app help: j-kaltes/Jugglucohelp.

Android string resources and the native jugglucotext sources are separate application-text locations. Help translations also need the repository’s conversion/build step; copying translated HTML into the Android project is not sufficient by itself.

A closed GitHub issue or discussion does not necessarily mean the requested feature was implemented. A thread can be closed after an explanation, a negative answer, a redirect to another discussion, or a workaround.

For example, a closed request for custom rapid-rise alerts was answered with a suggestion to write an app that receives Juggluco broadcasts; that did not add a new built-in alarm.

When using an old GitHub thread, look for an explicit release/version saying the change was implemented.