I am a deacon in the Catholic Church. There is a lot to do during the Triduum, Holy Thursday, Good Friday and the Easter Vigil. I changed G7 sensor about an hour before showering and dressing.
It’s about 22 miles to the church. At 5 miles I got a LOW alarm, but i wasn’t feeling it. When I got to my office I tested and was 109mg/dl. Over in the Church I meantion to a lady that my pump was going to beep because the sensor won’t calibrate.
I felt on my arm and couldn’t feel it. I put my phone and watch in a drawer and turned off C-IQ and stopped the sensor. No embarrassing beeps.
When I got home I looked in the shower, Not there. When I took off my shirt it was stuck on my elbow.
This sensor is not too quick to pair to the watch, while the one that fell off was quick.
I’m not part of your church yet your example gives me pause: I did in the past scuba dive and doing so while relying on the G7 for BG readings convinced me that I had been sold something that didn’t quite work.
Eventually I realized the error of my ways and went back to good old MDI; long acting (at a low dose) and a pen to shoot up when my BG started to do the same.
Never blame yourself; there is a problem and as human beings it is far too easy to blame ourselves regardless of who the god is.
The tech does not work and when doing critical things sometimes non-tech, flawed though it is, is safer; certainly not better, just safer.
Mainly I was worried about the false alarms sounding of disturbing the solemnity of the Mass, especially if picked up by a microphone. Stopping the sensor was the best solution.
I mostly posted that if anyone gets a LOW without symptoms maybe the sensor feel off.
@CarlosLuis.
I don’t use the G7, but I have tested it a few times.
I believe there is a setting on the G7 app that lets you silence ALL alarms for up to 6 hours. That would be the ideal solution for a situation like this.
I’ll check it out. At the time I was forced to multitask which is unnatural for me. Hiding phone and watch plus stopping the sensor was what came to mind.
That might silence the phone but Tandem is the other noise maker.
@CarlosLuis If using the G7 app on iPhone, go to Profile>Alerts>Show Quiet Modes, there you can turn on Vibrate or Silence All. Select the circled i and it will provide definitions for you. The other thing you need to do is check any pump app you may use for its alerts which are usually independent of the G7. It’s also a good idea to set your phone on silent mode for any alerts/calls you may received there (independent of diabetes apps).
This gives a menu which defaults to disabling everything for 60 minutes but allows up to 12 hours and “Until you re-enable”
xDrip+ does have a bug which reappears every now and then (and they consistently deny it exists); it plays a very loud “trumpet” sound at some point after inserting a new G7. It doesn’t always happen. The noise bypasses putting the 'phone into “silent” mode; it seems likely that it is using the “media audio” channel which can’t be silenced.
In Easter service today, I was low. The only treats I had were loud and crunchy! So I was trying to eat them very quietly in the service. Reminded me of your alarms @CarlosLuis.
I go slightly low many Sundays, just about at Communion-time, and my preferred remedy of a roll of smarties is just a bit noisy. Somebody on this forum (maybe Sam?) said an Altoids tin works well. I gotta pick up some Altoids to try at some point.
BTW @CarlosLuis, I can sympathize. I’ve had a number of times leading Rosary at Mass while not being totally sure my CGM was going to alarm or not… Thankfully, since I’ve switched to xdrip, I’ve got way more control over alarms. Also, a quick glance at my Garmin watch allows me to see blood sugar with alarms being on vibrate, etc. (my Garmin connects to xdrip )
@jbowler the “trumpet” sound may be related to pairing a new sensor. That’s the only time I get it. I once got it when the actual pairing took place, but now if it happens it seems to happen an hour or more after.
That’s my experience, though I never got it so fast. I had one on my last-but-one insertion after a few hours. I’m still waiting for the Trumpet of JamOrHam to sound on my latest sensor. I do use AndroidAPS too, so it could be coming from that; I can’t completely rule that out and @Navid200 has cancelled my issues a couple of times now (no blame; spurious issues in FOSS software are a major problem ATM.)
It is happening on the Android media audio channel so turning off media means it doesn’t happen (well, it makes 0 noise). I’ve had it happen while listening to audio in the 'car and it’s at 100% audio level (so louder than any professionally produced audio).
I got one in the middle of last night. I checked the error log and it corresponded to a message (informational) that “BroadCastService” had started. I think this is the local broadcast which I use to transmit readings to AAPS but AAPS was getting readings all the time…
