CGM Libre or Dexcom issue after A536BXXU6CWE9 update

[xamrex]

Hello

I, and many other people, after updating A53 phone with A536BXXU6CWE9  update, got issues with alarms in LibreLink app or in DEXCOM

As i know A52, A53, and A54 user got the same issue. There is something wrong with bluetooth after this update.

Is it possible to highlight the issue to guys form software team and ask them to fix issue. Many people over the word right now dont have alarms that are important for people with diabetic.

Galaxy A53 5G 

[Old_man_on_dirtbike]

Any response? We're currently getting the run-around from support. Delete this, disconnect that, restart, we even factory reset the phone. Still drops the connection within a few minutes. Agreed that this is stressful, Type 1's rely on this connection to stay alive, literally.

[Ove_A]

I have the same issue with my A53 5G. However - the device has no problem finding other bluetooth-devices, so I'm not sure it's a bluetooth problem... But a device-problem, defenitly. I restarded a cracked A51 with One UI-version 5.1 and that device has no problem keeping contact... Really frustrating, and it's no difference between G6 or G7... How do we report this to Samsung support?

[Morphee7]

Im also one of you type 1 diabetics with this issue. i lose the signal if i move my A53 more than 30cm away from the Dexcom G6 transmitter. This is causing me alot of distress as im getting no signal while im sleeping and this is the main reason i went on a CGM because of the low sugar through the night. But like you i cant get any info off samsung about this and gone through all the steps with Dexcom

[Old_man_on_dirtbike]

I've given up. Samsung Service is just giving me the run around. Almost two weeks in and the last contact I had with them wants me to take the device to a service centre, 100kms away, leave it so I don't have a phone, and the threat of payment if they can't identify the issue. The device is now useless for its intended purpose, and I hope others who end up on this page avoid the A53, and possibly Samsung, because you're not going to get a resolution in any reasonable amount of time. Samsung have no appreciation for the dangerous situation in which they have placed their users.

Galaxy A53 5G #DEXCOM #Update #Bluetooth #Diabetes #Type1

[Morphee7]

When last speaking with a Dexcom support member they told me that the higher ups at Dexcom know of this issue and are working with Samsung "apparently" and they also told me to speak to my diabetic nurse/consultant to contact them to get a receiver sent to me to solve this issue for now. But yet again i had to go through all the check settings and reinstall the app again with them just to prove my point, but with the NHS being tight on cash they are reluctant to release the funds to provide me with one. We still havnt the closed loop here so that would of solved the issue aswell 

[Old_man_on_dirtbike]

We contacted our supplier, and were supplied a new transmitter. It made no difference. IT connects, then after a few minutes, disconnects. I'm not sure if there is a new model coming, but it sort of doesn't deal with the issue of the update breaking it for existing receivers. Samsung support doesn't comprehend the fact it takes up to 30 minutes for the transmitters to re-register when you clear out the Bluetooth settings and are forced to set up the transmitter again. They also cannot see what the app is doing remotely, as the Dexcom interface is blocked to support.

Edited (transmitter, not receiver)

[AJKohl]

I have just seen this thread.

I have learnt on another forum that an update that Samsung made to its A series smartphones is alleged to have caused Bluetooth to fail to communicate on certain Samsung A series smartphones to communicate with the Freestyle Libre 2 glucose sensor, the Freestyle LibreLink glucose monitoring app and the Dexcom G6 glucose monitoring sensors. This, in turn, has allegedly led to an automated insulin delivery system not communicating properly to insulin-dependent diabetics.

The report I read suggests that Samsumg are aware of the issue and they are supposed be be preparing and issuing an update (due on or around 24 July 2023) that will resolve the Bluetooth connectivity issues on Samsung A series smartphones.

On a broader point, I really do wish the software developers of the pharmaceutical companies, mobile smartphone manufacturers and mobile operating systems providers would talk to each other.

They know that Big Pharma are now making glucose monitoring sensors and software apps that rely on the Bluetooth technology in smartphones to communicate medical data - in real time - to diabetics. That medical data is used by diabetics when deciding whether or not to make medical treatment decisions, such as taking insulin to treat hyperglycemia or eating something to treat hypoglycaemia.

The failure to be able to make those decisions in a timely way can lead to diabetics becoming unconscious, having seizures, going into a coma, and even dying.

It is - literally - life and death stuff.

Every time Bluetooth settings on any smartphone are updated by a phone manufacturer it potentially stops these glucose monitoring sensors and related sensor apps working as they are meant to work.

The fact that some smartphone manufacturers - including Samsung and Apple - have been working for many years on their own devices to measure blood glucose in order to enter the glucose monitoring products market does not absolve you of your responsibility to talk to Big Pharma about Bluetooth and other connectivity issues to maximise existing functionality and connectivity with existing third party medical devices and software so that they work as they are meant to work on your mobile products.

PLEASE talk to each other BEFORE you alter Bluetooth!

Many thanks.

[Morphee7]

Ive just manually checked for an update and got the latest one (installing as i type) says on the release notes that they have improved bluetooth connectivity and reliability so heres hoping its solved our CGM issues 

[clarkydv]

Has the latest update made a difference for anyone? I installed it today but I am still having issues connecting to Dexcom One app with an A53 phone