Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Mathias Walter
    @tolot27
    @nigelkeirross I know of only one problem which appeared with the Android Nov. security patch: NightscoutFoundation/xDrip#1494. This is caused by unbonding and rebonding the Dexcom transmitter (by xDrip) on every read request (every 5 minutes). This behavior is was only implemented for Dexcom communication. Nevertheless, if you setup a connection to MiaoMiao, you have to confirm the pairing once.
    nigelkeirross
    @nigelkeirross
    @tolot27 Thanks. So I believe you are saying I am OK to go ahead with the upgrade (my xDrip is from 1 October 2020), and when I connect to the mm2, I will be asked (by the system, not xDrip) once to confirm the pair (at present I am not asked by the system to confirm anything). Much appreciated.
    Mathias Walter
    @tolot27

    @nigelkeirross Because I asked on the issue log you've posted and people had said that Libre was affected, even though almost all the conversation on there was for Dexcom

    You have to distinguish how the Nov. security patch affects the Bluetooth stack (every bonding/pairing has to be confirmed from now on) and how xDrip implements BT communication to certain devices. xDrip establish only one bonding during setup of any BT device it communicates with, except for Dexcom.

    Dave
    @mistermintsgh
    Thanks @tolot27 it might be time to update finally and get rid of that annoying notification!
    4RK4N
    @4RK4N
    is there some way to restart nightscout client in xdrip? like i can do in aaps. its not uploading properly due to internet hickups. xdrip seems to not recover from those correctly
    3 values in a row not uploaded. after i had internet again it backfilled the 4 missing values but now it stopped again
    is there any specifiv log tag for nightscout so i can see whats going on?
    4RK4N
    @4RK4N
    force closed xdrip app to restart nsclient. next value still didnt get uploaded wtf?? it always worked and now it stopped without reason (short internet failure isnt a reason to stop uploading forever)
    oh what a delay. now it backfilled those 4 values again. if that continues i cant aaps that way. time to mod the app so eversense gets recognized as filtered
    4RK4N
    @4RK4N
    system status > uploaders shows some info but i need more than that. apparently if xdrip loses connection to ns it waits 5 bg values until it tries again. why?
    4RK4N
    @4RK4N
    no internet for 5 minutes resulting in xdrip not uploading for 20+ mins cant be the intended behavior
    although im back online i still get toasts/log messages "‪‪task deadlock on: synctoCloudDatabases!"
    and again that error toast
    Patrick Sonnerat
    @psonnera
    @old-square-eyes how do you start remote? I saw that best strategy is enable only wear on phone xdrip+ , wait for full graph on watch, then enable both collector and force collector (always phone) and wait 5/10 minutes. Check also wear has all authorizations including location.
    tremor
    @tremor
    @pimeys yes, now it works most of the time
    Patrick Sonnerat
    @psonnera
    @old-square-eyes all I can propose you is this and google translator... https://www.glicemiadistanza.it/sony-smartwatch-3-e-xdrip/
    Nate Collings
    @naiyt

    Anyone know if it's still possible to hard reset G6 transmitters with the latest firmware? I’ve got an 8M transmitter, firmware is 2.18.2.98, on Android 11, latest nightly build of xDrip.

    When I attempt the hard reset, it comes back with Hard Reset maybe. Failed, and the error in the logs is Failed to write ResetTxMessage: com.polidea.rxandroidble2.exceptions.BleDisconnectedException: Disconnected from MAC=‘XX:XX:XX:XX:XX:XX’ with status 19 (GATT_CONN_TERMINATE_PEER_USER)

    Dealing with some insurance issues trying to get my next transmitter, so was hoping I could get a few more days out of it (it still has battery life, but hit that 112 day limit).

    swissalpine
    @swissalpine
    No possibilty to hard reset with actual transmitters.
    You need an 80 or 81.
    Nate Collings
    @naiyt

    @swissalpine thanks, that's too bad. I kind of miss the G5, where extending both transmitters and sensors was easy. :'(

    Good to know it's not possible though, so I don't keep spending my time trying to get it to work.

    old-square-eyes
    @old-square-eyes
    @psonnera thanks. That page looks interesting. But it's an embedded PDF and won't translate or download.
    Don't worry I found the PDF link in the source
    old-square-eyes
    @old-square-eyes

    OK mostly stuff I was aware of. Although, of all the techniques I concur using old Android Wear after a reset seems the least problematic to get xDrip prefs on the phone.

    I truly despise how Google broke legacy watch compatibility and then silently updated those users to Wear OS. It's extremely irresponsible and has been reported by other non diabetic users in the past - particularly around Play Music loss of function, broken WiFi to name a couple. This just makes it worse as Play Music is thier own app.

    Translation isn't working perfectly but one thing piqued my interest...

    "When you no longer want the smartwatch to be the master, FIRST disable both boxes
    Enable Wearing G5 Collection Service and Force Wearing G5 Collector Service and AFTER,
    just in case Android Wear integration.
    If you don't follow this sequence, xDrip + may leave control to the smartwatch e
    lose the connection with miaomiao, requiring a reset of the transmitter"

    Sounds a lot like my symptoms from NightscoutFoundation/xDrip#1511 (which I am still yet unable to resolve)
    old-square-eyes
    @old-square-eyes
    1511 just resolved itself for me. Unrelated to the above. The terrifying thing is I have no idea what the issue was.
    The one clue I got was, in all the fiddling/force Wear I unexpectedly got this...
    20201126_114702.jpg
    First time I've seen that after two weeks of factory resetting and every step under the sun that the internet has to offer. I'd love to know what removes that permission, and also what triggers the request for it. Can it be manually triggered?
    Djinn
    @DjinnGallagher
    image.png
    I keep getting this error message every five minutes. Otherwise everything is working fine but it's burning through my phone battery
    Djinn
    @DjinnGallagher
    I'm using the G6 on a Samsung 8+ and it was working okay until recently - maybe the last update?
    Xdrip Version edd2c2a-2020.09.04
    old-square-eyes
    @old-square-eyes
    @DjinnGallagher my logs are flooded with those errors too. And the java Null pointer NanoStatus one.
    Djinn
    @DjinnGallagher
    @old-square-eyes Thanks - have you tried the most recent nightly that was supposed to fix this? I updated but it didn't change anything
    old-square-eyes
    @old-square-eyes
    But I'm getting 99% cap now on Wear so won't be complaining.
    Djinn
    @DjinnGallagher
    what does 99% cap mean please?
    old-square-eyes
    @old-square-eyes
    I have a bit of a unique scenario. I'm on S20+ with Android 10 and SWR50 (collecting). Haven't updated to the Nov Android patch yet.
    I have jumped around xDrip versions troubleshooting other issues and am currently on latest normal apk 2020.07.13
    So don't think it's specific to the nightly that was supposed to fix the 5min bonding issue - which I was on for a few days recently.
    old-square-eyes
    @old-square-eyes
    99% capture (realtime) basically means my watch gets every reading from the Dexcom G6, without loosing connection. The SWR50 is unbeatable, which is why I work so hard to keep it in my setup :)
    TheDiabeticWay
    @TheDiabeticWay
    Just wondering is xdrip working with a Samsung S20 if anyone knows trying to help somone setup there new mobile but never tested a s20 myself!
    4RK4N
    @4RK4N
    the app can be installed on a s20 and it doesnt crash yes. there is more to a working xdrip setup than the right phone. almost all phones work. what cgm does ur friend have and how does he plan to get the data into xdrip would be the more important questions than the phone model
    TheDiabeticWay
    @TheDiabeticWay
    @4RK4N well yes if they needed to know this I have all that detail on my web site and also an auto file to have compatibilities for mobiles but if people don't use it or fill in these details nothing I can do to figuring every mobile in the world I was just after a yes! :-) Thanks! Its ok now I got them up and running in a good time a hour! :-)
    Marcus Buzzford
    @MarcusBuzzford_twitter
    I'm using an Android company phone (Samsung) managed by the company IT department. Since a few weeks updating xDrip is impossible "blocked by your IT admin". I have contacted the IT admins but they refuse to whitelist xDrip: Only PlayStory apps are allowed from now on. :-( ... Luckily the already sideloaded xDrip app is still running (I only cannot update any more). But now "Microsoft Defender" is being rolled out on my phone as mandatory app. Does anybody know if this app will remove xDrip completely? It will scan for "malicious" apps and remove them as per company announcement. What can I do?
    Eric
    @ecc1
    @MarcusBuzzford_twitter buy a small cheap Android phone, and use your HR department to make sure you have the right to use it at work
    Marcus Buzzford
    @MarcusBuzzford_twitter
    @ecc1 : May sound like a bad excuse but my pockets already contain the company phone, wallet, keyring, car keys AND I don't want to handle two phones at the same time, e.g. big confusion if phone A or B is beeping... Simply impractical for me. The most simple solution would be xDrip+ availability in the PlayStore since my company allows all apps even for private use. They're now blocking side-loading and xDrip can only be side-loaded :-(
    old-square-eyes
    @old-square-eyes
    @MarcusBuzzford_twitter I doubt xDrip will ever reach the play store.
    @TheDiabeticWay I'm using a S20+ if it helps (with newer G6)
    Seems to work OK with a few missed readings. Backfill helps. I'm still looping mostly OK.