Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Royce Simpson
    @roycesimpson
    Should I expect different behavior in xdrip now that I'm using the "native algorithm" options? Does it take a few readings to adjust?
    Do do see that a reading has come in after that calibration and it's jumped to 87... about half way between my prior-to-calibration reading and the actual calibration.
    teleriddler
    @teleriddler
    calibrations in general usually wait about 15 minutes, I believe to make sure there is not a spiking value so sit can compare over 3 values to normalize the trend a bit. This is what I have observed but others may be able to give more specific information.
    Julius de Bruijn
    @pimeys
    yeah, first it puts the calibration in queue, next time you get a value from the sensor, it sends the calibration to the transmitter
    then the next time you get a value from the transmitter, it gives back a value calibrated with the new measurement
    actually now when I don't use AAPS, I like the xdrip algorithm way better
    Royce Simpson
    @roycesimpson
    @pimeys @teleriddler Thanks, makes sense. Yeah, I think I like the xdrip algorithm better too but I'll give this a few days. I also like having that grey "filtered plot" on the graph which doesn't show up anymore with this native algorithm.
    Julius de Bruijn
    @pimeys
    yeah, native algorithm makes sense if you do closed loop with android apis
    and use oref1 smb
    Royce Simpson
    @roycesimpson
    Curious, do I need to enable these native settings to use the G6 transmitter/sensor? I got those on order and will be replacing the g5 soon.
    Julius de Bruijn
    @pimeys
    I think it should work just as G5
    nsghub
    @nsghub
    @jamorham Do you have any idea why my LG W100 hangs on boot after patching with the care pack? Build version does match the one in the PDF. (NightscoutFoundation/xDrip#582)
    JamOrHam
    @jamorham
    @nsghub I'm sorry I don't know if the build version matches it should be identical to the reference one I made the patches from
    The current Nightly/Alpha release is the current release candidate. If all remains good then I will push this out to everyone sometime soon so please make sure you're using it and report any new issues. Thanks
    nsghub
    @nsghub
    @jamorham I assumed that ;) Just tried it again. After attempting to apply the patch I get "ERROR: with patch!!" and "Failed to mount '/system' (No such device)". Now I'm not sure if that's ok or not. Because the pdf says that those "system" errors can be ignored.
    nsghub
    @nsghub
    Hmm, executed the xdelta3 command in the shell. It tells me that the source file is not the one it expects: "xdelta3: target window checksum mismatch: XD3_INVALID_INPUT"
    "
    so my system partition is different from the one you had
    nsghub
    @nsghub
    disabled checksum, fingers crossed
    nsghub
    @nsghub
    of course the watch still doesn't boot (as expected). Can you provide the complete system.img?
    dansuk
    @dansuk
    I'm using xdrip+ with Blucon and it has generally been working really well with the recent nightly (much more stable connection than I have experienced previously). However, I am received intermittent missed readings today and checking the logs I am seeing various "*COMMAND NOT FOUND! messages. Any thoughts on what can be causing this?
    dansuk
    @dansuk
    Following above post, eventually I received the message persistently in the logs and no readings. Reseting blucon didn't help but after restarting my phone everything is working again!
    dansuk
    @dansuk
    Update: Got one reading and now * COMMAND NOT FOUND! again :(
    DunePlodder
    @DunePlodder
    A couple of months ago I was having a problem with every reading being sent to my Pebble Classic as a notification - i.e. every 5 minutes. Disabling "Run Collector in foreground" stopped this but it also stopped the notification graph on the lock screen. Yesterday I tried enabling "Run Collector in the foreground" & it's all working fine. Presumably some changes were made, thank you.
    Grégory Beloncle
    @gregorybel
    @dansuk can you post some lines before and after? or maybe a screenshot?
    Zach Gohr
    @zgohr
    Got the new zenwatch2 downgraded to the necessary build and demigod enabled but cannot get it to collect. Went through all the debugging steps to no avail. If anyone has gone through this recently and can give me a tip or two of things to try I’d appreciate it.
    Royce Simpson
    @roycesimpson
    Hi, does anyone know if I can use g6 transmitter/sensors directly with xdrip+ without the official dexcom app or receiver? I've seen that the the transmitter won't start without the official app or receiver.
    which would really suck
    JamOrHam
    @jamorham
    @roycesimpson no its fine, just make sure to be using the Alpha or Nightly version and enable native mode. Ideally long press the xDrip drop icon on the app home screen and enable the source wizard and select G6. That will ensure you have all the standard settings
    Royce Simpson
    @roycesimpson
    wow, really @jamorham that is great news!!! Also, is there anything built into xdrip+ for g6 now that allows for longer than 90 day transmitter and 10 day sensor hard cutoffs?
    JamOrHam
    @jamorham
    @roycesimpson yes thats all in there too
    Royce Simpson
    @roycesimpson
    My goodness. That takes me from "maybe g6 isn't where I want to go yet" to "hell yeah!" thanks @jamorham
    JamOrHam
    @jamorham
    G6 is very good, hats off to dexcom
    Royce Simpson
    @roycesimpson
    in googling all this I did see that they may allow the sensors to go 14 days here in the next 6 months or so
    which is about what I get on average anyway.
    they being Dexcom
    CaroGo
    @CaroGo
    So, is it absolutely necessary to use native mode with g6 then?
    old-square-eyes
    @old-square-eyes
    Good question
    Also has anyone managed a battery replacement on the G6?
    LMGTFM
    You can: https://seemycgm.com/2018/07/12/g6-transmitter-battery-replacement/
    Grégory Beloncle
    @gregorybel
    @dansuk Looks like a bug, which version of xdrip? when did you buy your Blucon? can you delete your second screenshot?
    dansuk
    @dansuk
    @gregorybel It's version d1d4887-2018.09.08 (1809080944) - I bought Blucon back in January. I can reshare a link without the second screenshot if that helps? Let me know if you need anything else.
    old-square-eyes
    @old-square-eyes
    @dansuk I think it's just that your second screenshot has unnecessary info and maybe too much info in the logs.
    dansuk
    @dansuk
    @gregorybel @old-square-eyes no problem, I've created a new link here: https://photos.app.goo.gl/zdSs9ezdYkZKKJry9 (sorry, can't work out how to remove from the original link!)
    nsghub
    @nsghub
    @jamorham Maybe this issue can be fixed before the next release?! NightscoutFoundation/xDrip#492
    n0rbertg
    @n0rbertg
    @CaroGo No, you don't have to use native mode with g6 if you don't want to
    CaroGo
    @CaroGo
    @norbertgaal thanks... So, it is just the same as with G5?
    n0rbertg
    @n0rbertg
    @CaroGo I believe so (although I haven't used G5). You can use native mode and it'll restart the sensors automatically or just go without native mode and leave it as long as it runs. You also have the option to reset the transmitter if you'd like to go with native
    JamOrHam
    @jamorham
    You have to enable engineering mode to use G6 without native mode I think
    CaroGo
    @CaroGo
    @jamorham @norbertgaal... Ok.. Engeneering mode is enabled. With G5 I just leave it running,that is the easiest way and works fine. Why should I want to reset the transmitter