Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    JamOrHam
    @jamorham
    @MilosKozak maybe, but isn't the setting Append source info to device name in the xDrip Upload settings what should be enabled for this extra detail?
    Milos Kozak
    @MilosKozak
    that's it. Thanks!
    updated AAPS wiki to do this
    JamOrHam
    @jamorham
    @MilosKozak I can make xDrip automatically set the setting if it is always needed in the presence of AAPS, we do this for other broadcast settings etc.
    Milos Kozak
    @MilosKozak
    ok, great
    old-square-eyes
    @old-square-eyes
    xDrip keeps crashing on my SW3. Have updated to latest nightly, still happens. Reset Wear DB and resynced Wear apps and turned off Wear collection.
    Still happens
    Any idea how to debug?
    n0rbertg
    @n0rbertg
    what's in the log?
    Zach Gohr
    @zgohr
    Troubles patching a zenwatch2 502Q. “ERROR: could not patch BT with demigod mode” but no other hints
    ronaldhacker
    @ronaldhacker
    Not to sound dumb, but what is AAPS?
    Eric
    @ecc1
    Android APS
    (openaps ported to Android)
    old-square-eyes
    @old-square-eyes
    Have to enable Wear logs. Will report back.
    Zach Gohr
    @zgohr
    @jamorham any ideas on getting my Zenwatch2 502Q patched? Everything goes fine until actual patching, then I just see the generic “could not patch BT” error message.
    JamOrHam
    @jamorham
    @zgohr does your watch build number match the one described in the care package PDF ?
    Zach Gohr
    @zgohr
    it does not. looks nothing like it
    /facepalm
    JamOrHam
    @jamorham
    @zgohr either it needs up or downgrading so it matches
    Zach Gohr
    @zgohr
    How would one go about doing that?
    Royce Simpson
    @roycesimpson
    Hello all. I just fired up the "native algorithm" options on xdrip+ and g5... I enabled that for a sensor that I've had for a few days and just "stopped/started" the sensor and went through the 2 hour warm up... that was last night. Now, when I calibrate, it doesn't seem to do anything. For example, xdrip is showing I'm at 80 but when I enter a calibration of 100, the number and graph stay at 80. That doesn't seem right.
    Should I expect different behavior in xdrip now that I'm using the "native algorithm" options? Does it take a few readings to adjust?
    Royce Simpson
    @roycesimpson
    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?