DexShareCollectionService got the status 133 bug bad news! #400
Comments
|
It is interesting to understand if something has changed in the phone (was
there any update lately)?
In any case, please move to xDrip+.
Thanks
Tzachi
…On Wed, Dec 28, 2016 at 5:01 AM, grincher ***@***.***> wrote:
Dexcom with Share connected to 205 beta xDrip running on Moto X (2nd gen)
has been working for months. Now I'm getting DexShareCollectionService got
the status 133 bug bad news! in the error log. Dexcom with Share no longer
shows bt symbol. I've tried forgetting the devices and power cycling both
devices and starting all over on pairing. Same result. Installed beta 206.
Same result. What to do next?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#400>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHkw5JVAEZgBY4dLMUZK1BXMSopR1s0Jks5rMdECgaJpZM4LWo9Q>
.
|
|
The phone has not been changed. After posting my question I realized a
possible change that might be affecting the situation: The patient started
wearing a Garmin vivofit2 BLE wrist worn device that has an app installed
on the phone. Can the phone not handle two bt devices? or is xDrip somehow
assuming it will be the only one?
When I try to install xDrip+ (xDrip-plus-20161124-9bf0276.apk) it states
"App not installed".
…On Dec 28, 2016 12:22 AM, "tzachi-dar" ***@***.***> wrote:
It is interesting to understand if something has changed in the phone (was
there any update lately)?
In any case, please move to xDrip+.
Thanks
Tzachi
On Wed, Dec 28, 2016 at 5:01 AM, grincher ***@***.***>
wrote:
> Dexcom with Share connected to 205 beta xDrip running on Moto X (2nd gen)
> has been working for months. Now I'm getting DexShareCollectionService
got
> the status 133 bug bad news! in the error log. Dexcom with Share no
longer
> shows bt symbol. I've tried forgetting the devices and power cycling both
> devices and starting all over on pairing. Same result. Installed beta
206.
> Same result. What to do next?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/StephenBlackWasAlreadyTaken/
xDrip-Experimental/issues/400>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AHkw5JVAEZgBY4dLMUZK1BXMSopR1s0Jks5rMdECgaJpZM4LWo9Q>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#400 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQT_aDwNTV_8v6WPTXruAeKuGrXg5RIhks5rMg4qgaJpZM4LWo9Q>
.
|
|
xDrip+ (apk obviously signed by a different builder) installed fine after
uninstalling beta 206. patient is re-pairing devices and we'll see how it
goes.
On Dec 28, 2016 9:45 AM, "grincher" <[email protected]> wrote:
The phone has not been changed. After posting my question I realized a
possible change that might be affecting the situation: The patient started
wearing a Garmin vivofit2 BLE wrist worn device that has an app installed
on the phone. Can the phone not handle two bt devices? or is xDrip somehow
assuming it will be the only one?
When I try to install xDrip+ (xDrip-plus-20161124-9bf0276.apk) it states
"App not installed".
…On Dec 28, 2016 12:22 AM, "tzachi-dar" ***@***.***> wrote:
It is interesting to understand if something has changed in the phone (was
there any update lately)?
In any case, please move to xDrip+.
Thanks
Tzachi
On Wed, Dec 28, 2016 at 5:01 AM, grincher ***@***.***>
wrote:
> Dexcom with Share connected to 205 beta xDrip running on Moto X (2nd gen)
> has been working for months. Now I'm getting DexShareCollectionService
got
> the status 133 bug bad news! in the error log. Dexcom with Share no
longer
> shows bt symbol. I've tried forgetting the devices and power cycling both
> devices and starting all over on pairing. Same result. Installed beta
206.
> Same result. What to do next?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/StephenBlackWasAlreadyTaken/xDrip-
Experimental/issues/400>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHkw5JVAE
ZgBY4dLMUZK1BXMSopR1s0Jks5rMdECgaJpZM4LWo9Q>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#400 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQT_aDwNTV_8v6WPTXruAeKuGrXg5RIhks5rMg4qgaJpZM4LWo9Q>
.
|
|
xDrip+ gave me some trouble getting set up, but it does seem to be working
now, including uploading data to Dexcom share site so followers can see the
data. I'm not sure how long to wait to declare success, maybe 24 hours?
I'm watching the error log closely. thanks.
…On Dec 28, 2016 10:00, "grincher" ***@***.***> wrote:
xDrip+ (apk obviously signed by a different builder) installed fine after
uninstalling beta 206. patient is re-pairing devices and we'll see how it
goes.
On Dec 28, 2016 9:45 AM, "grincher" ***@***.***> wrote:
The phone has not been changed. After posting my question I realized a
possible change that might be affecting the situation: The patient started
wearing a Garmin vivofit2 BLE wrist worn device that has an app installed
on the phone. Can the phone not handle two bt devices? or is xDrip somehow
assuming it will be the only one?
When I try to install xDrip+ (xDrip-plus-20161124-9bf0276.apk) it states
"App not installed".
On Dec 28, 2016 12:22 AM, "tzachi-dar" ***@***.***> wrote:
> It is interesting to understand if something has changed in the phone (was
> there any update lately)?
>
> In any case, please move to xDrip+.
>
> Thanks
> Tzachi
>
> On Wed, Dec 28, 2016 at 5:01 AM, grincher ***@***.***>
> wrote:
>
> > Dexcom with Share connected to 205 beta xDrip running on Moto X (2nd
> gen)
> > has been working for months. Now I'm getting DexShareCollectionService
> got
> > the status 133 bug bad news! in the error log. Dexcom with Share no
> longer
> > shows bt symbol. I've tried forgetting the devices and power cycling
> both
> > devices and starting all over on pairing. Same result. Installed beta
> 206.
> > Same result. What to do next?
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/StephenBlackWasAlreadyTaken/xDrip-Experi
> mental/issues/400>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AHkw5JVAE
> ZgBY4dLMUZK1BXMSopR1s0Jks5rMdECgaJpZM4LWo9Q>
> > .
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#400 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AQT_aDwNTV_8v6WPTXruAeKuGrXg5RIhks5rMg4qgaJpZM4LWo9Q>
> .
>
|
|
Happy to hear. |
|
yes, it has been working well for a couple weeks now!
thanks
…On Thu, Dec 29, 2016 at 2:19 AM, tzachi-dar ***@***.***> wrote:
Happy to hear.
I hope that this is still working.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dexcom with Share connected to 205 beta xDrip running on Moto X (2nd gen) has been working for months. Now I'm getting DexShareCollectionService got the status 133 bug bad news! in the error log. Dexcom with Share no longer shows bt symbol. I've tried forgetting the devices and power cycling both devices and starting all over on pairing. Same result. Installed beta 206. Same result. What to do next?
The text was updated successfully, but these errors were encountered: