Thasgolas
commented
8 years ago * SOLVED * -- but perhaps with what my workplace calls a "Do Out" : I tried pairing the receiver with an iPhone and Dexcom Share2. When it failed, it reported why: Serial Number Mismatch. I'd been trying the serial number wrong by a digit!
I think a really good idea would be for xDrip to have that capability -- will save someone else a headache. (Or am I the only one who'd do this?)
Changed phones last week - ironically because of unrelated bluetooth issues. Have a Samsung S7 Edge now (Android v.6.0.1). Even though Privacy Guard is not on by default, I needed to enable location permission for xDrip to 'see' the receiver. I've also tried clearing the BT cache and wiped the system cache, as some have posted elseweb for S7 Edge BT issues (for car systems).
What happens is that the Receiver's BT icon flashes until I attempt to pair the device (either from within xDrip or from the BT settings), at the point that connection should be made, the icon becomes sable for an instant, then flicks off. The phone's settings report "Connected". xDrip's status sometimes also says "Connected' -- but no data is received. i have tried two receivers with the same results.
(Note: With my previous phone, I was able to make (these) connections, though, occasionally had to reconnect. (That phone gave me terrible problems connecting to my car, which is why I had to replace it.) ) So far, the S7 phone has had no trouble with connections to any other BT devices - car system, Pebble Time, Asus (Android Wear) watch -- so both regular and LE bluetooth connections work solidly -- just not to the Dexcom receiver. Help!?