@jdhigh Yep, that was me who had the problem with the Pixel 2. I'm glad to hear it's working for you, I will admit that my old Pixel was working so well that after BT didn't work the first few times trying on the Pixel 2, I just quickly went back to the original. So I'm glad to hear it actually does work.
@alimhassam if you want bt to stay connected to a phone when there’s no internet, you can modify oref0-online.sh to leave the bt connection up if there’s no external website to ping. Or you can setup a permanent bt tether, removing most of oref0-online.sh and allowing your phone to manage connectivity. The android phones typically don’t drop connection if there’s no cell signal.
It’s usually the rig network cycling when it can’t ping externally.
Had an interesting side effect of cleaning out my rigs last night. They’d stopped connecting via BT to the phone whilst they had very little disk space left. Clearing them out has meant that they now bt tether quite happily.
@laurathiessen Oh I just returned it to Google for a refund. And it sounds like there isn't a problem, I just got frustrated with it and didn't feel the need to replace my Pixel. @jdhigh seems to have had a good experience.
I'm getting this error for the last few hours, mmtune appears to tune ok:
Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type? Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!) mmtune: mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type? Usage: grep [OPTION]... PATTERN [FILE]... Try 'grep --help' for more information. Usage: grep [OPTION]... PATTERN [FILE]... Try 'grep --help' for more information. No wait required.
On the subject of reviewing autotune output, the understanding autotune docs show an example of output. Is it possible to pull something like that off of a rig that has been running with autotune enabled? If so, how much historical data would it take into account?
Answering my own question, found 'autotune_recommendations.log' in /myopenasp/autotune. Missed it on the first pass...
~2 weeks was our original recommendation, but even shorter than that is fine - although it's always up to you, regardless of time frame, about how much you decide to adjust your underlying pump settings
@danamlewis It was the size of my mLab MongoDB. They couldn't compact my DB below 496 MB so I had to clean out entries. Good news is I opened an Open Humans account and contributed my data before cleaning out my entries. NS back to showing OpenAPS pill.