Explore
Example searches that return results — click one to run it.
Local mirrors of the official setup guides:
Top distilled records
Complete symptom → cause → fix extracts (all three parts) from the most-discussed, highest-confidence solved threads.
-
distilled GitHub Restart sensor and preemptive restarts option no longer works with new transmitter SN 81xxxx
SymptomWith a new transmitter whose serial number starts with 81xxxx, preemptive sensor restart stops working; xDrip reports errors like 'Sensor Failed Start', 'Sensor marked FAILED', and 'Session Start Failed: Invalid'. The only workaround is to start the sensor using the Dexcom receiver and wait through the full two-hour warm-up. Other users with 81xxxx transmitters report that preemptive restart says 'not capable' or fails.
CauseDexcom has restricted restart functionality in newer G6 transmitters. According to the maintainer, xDrip can currently only hard reset and perform preemptive restarts on G6 transmitters with firmware version 1.6.5.25, which includes all 80XXXX and some 81XXXX transmitters; transmitters with newer firmware (e.g., 1.6.5.27) cannot be restarted this way.
FixNo xDrip-side fix. The maintainer states that only G6 transmitters with firmware 1.6.5.25 (all 80XXXX and some 81XXXX) support hard reset/preemptive restart, and restarting other G6 transmitters requires temporarily removing the transmitter. A reported workaround is to start the sensor through the Dexcom receiver and wait through the warm-up period.
-
distilled GitHub Number wall on lock screen causing other apps to restart
SymptomExternal Android apps appear to restart at the precise Xdrip+ polling interval: Chrome web content refreshes and clears unsubmitted input fields, social media feeds refresh to the top of the scroll, and YouTube videos stop and reset to the beginning. The reported symptom was later narrowed to the xDrip+ lock screen number wall refreshing every 5 minutes.
CauseThe xDrip+ lock screen number wall refresh on Android 12 interrupts other apps, causing them to restart. Disabling the lock screen number display resolves it.
FixDisable the xDrip+ lock screen number display / Number Wall feature. Removing the value from the lock screen was reported to 100% fix the issue.
-
distilled GitHub Enable 640G as full data source via 640G Uploader application to allow Sync following to work correctly
SymptomUsers with a Medtronic 640G/Enlite want xDrip to include the Nightscout Medtronic/600SeriesAndroidUploader as a data source in master mode, so readings can be sent directly to xDrip followers and smartwatches with audible alarms. The Medtronic 640G's own alarms are quiet or not perceived, making xDrip's loud alarms desirable.
CausexDrip did not have the Medtronic 600SeriesAndroidUploader/uploader integrated as a source, so it could receive data only in follower mode, not master mode, preventing direct forwarding to followers.
FixDeveloper jamorham implemented the 640G uploader as a source in xDrip and released it in the 21 Aug version; the issue was then closed.
-
distilled GitHub No Pod activation possible since Android 16 Update
SymptomAfter updating a Pixel phone to Android 16, deactivating an old Omnipod DASH pod works, but activating a new pod fails with 'Failed to connect to pod'. Manual bonding mode also does not work, while an already-active pod continues to work.
CauseThe Android 16 update exposes a compatibility bug in AAPS's DASH connection code that prevents activation of new pods, requiring a code hotfix.
FixUpdate to AAPS 3.3.2.1 (which contains the fix), or build the dev332 branch; alternatively apply the hotfix-a16-dash commits 6153bc4 and 39dd2e6 to master. A temporary workaround is to activate the pod on a backup phone and import the settings export into the main phone.
Or browse the whole index at once — distilled first, then threads and docs.