Chaos in the Diabox update

From the update of yesterday, December 6, a complete chaos with the connection to Bluetoood.It is impossible.And with this, the compatibility to see the data in Garmin when exercising.The same thing happens to you?

By the way: I have never appeared the free sensor 2 as a device connected in the Bluetoood connections, although it has always worked.Any explanation?

And besides, to complete the day, I am in hyper and not changing pen

Yes, yes ... I have returned to the February beta

They have just put another update with error correction

And what about seeing me free as a device connected to the Blue?Do you see it?

To me on connected devices, the sensor has never appeared, but it is registering the data.

I will try the new one, I sister hanging on telegran today Dec 7 at 11:29

I downloaded it and ... at first glance we continue without Bluetooth connection with the sensor.In the observations, this error would have been remedied either

Diabox, [12/07/2022 15:17]
Just Found The Root Casue About Yesterday and Today's Release, You Can Stay On Feb Release, Give Me Time To Fix It

Back back in the update .....

Immensely grateful to a person who dedicates much of his time to create a free application for all the people who need it.

If you have problems with the update, as I have had it, the log is sent with the mistakes to help correct them :)

I thank the creator very much, but the Bluetooth connection does not work for me either
I have returned to the February beta

A few days ago, the February beta began to fail when my Samsung update Android 13, yesterday I put the new version and worse still, do not synchronize frozen clock data and Bluetooh that does not connect.Today I have put the new beta and has not solved the theme, I have sent log to the mail they have put in the Telegram group.It doesn't work for me or the beta of February, boring to try so much I have uninstalled and wait if they take something that works.

In the end and after several attempts I have managed to return to the February version, and everything will work again except some disconnection with free 2, and this despite the update to Android 13 that yesterday made my Sansung A52s.

wave said:
in the end and after several attempts I have managed to return to the February version, and everything will work again except some disconnection with free 2, and this despite the update to Android 13 thatYesterday I made my sansung a52s.

This update is a mié ..
It happened to me with xdrip, problems to Tutiphen

In any case, hopefully they will fix it and do not miss Diabox.Thanks for your work.The information in my Garmin would be lost and what a task when seeing the data on the wrist to train ... or think about it.
That we soon get used to the good.
So ... to pray they touch

wave said:
in the end and after several attempts I have managed to return to the February version, and everything will work again except some disconnection with free 2, and this despite the update to Android 13 thatYesterday I made my sansung a52s.

I have the same mobile, I will try again with the February beta to see if it hooks, if not to wait and fuck.

I use the A52S;I made a data backup and uninstalled the new version, I put the February beta, I identified and loaded the Backhup without problems.He has not given me any failure, even in connection with the smartwatch (I use the weros)

ruthbia said:
I use the A52s;I made a data backup and uninstalled the new version, I put the February beta, I identified and loaded the Backhup without problems.It has not given me any failure, even in connection with the smartwatch (I use the weros)

Before disappointing I made a Clean Up in case, and then install the old beta.
In IT issues sometimes you have to uninstall several times, data remains may remain.

What I am clear is that I do not go new version until it has been running for a month :)

It is that if something works for me ... I find it a lot to touch it.
Thanks for warning.

I updated it yesterday morning and better not have touched anything.
All day yesterday and everything we carry without connection and jumping the signal loss alarm every two by three.
FreeLink even fails and I don't know if it has something to do.
I just returned to the previous version like an hour, but still has no stable connection as I had before updating.
PD: The sensor has a week and until I updated yesterday Diabox was relatively well.