[[NO-TRANS]]Desastre con los sensores Freestyle libre

I wanted to share my experience in case someone else is experiencing the same thing.

I have contacted Abbott Diabetes Care because I am having problems with the sensor.The answer they gave me is that the problem is due to the fact that the application is not updated for my mobile phone and that, at the moment, they have no plans to update it.The only alternative they offer me is to send me a list of compatible phones.

What bothers me the most is that this same situation already happened to me about a year and a half ago.On that occasion they told me that I had to change my phone, and I ended up going from a Samsung A54 5G to a Samsung S24 5G.Now I run into the same problem again.

Changing phones every time they stop providing support is not a solution.We are talking about devices that cost close to €1,000, and it is not something that most people can do overnight.

In my case, I also have type 3 diabetes and I need very strict glucose control because I suffer very pronounced drops.That the sensor stops working correctly is not a simple annoyance, but a problem that directly affects my safety.

The feeling I am left with is that Abbott offers very good words, but few real solutions.If the only answer is "change your phone", I think something is wrong.I expected greater engagement with users, especially when we depend on these devices to manage a chronic illness.

Hello @juanen_

In my case I already have 4 sensors from the same batch with problems: 3 of them were constantly disconnected and one on the second day started with the reading pause error until the error that the sensor reached the end of its life came out (despite which it continued to work).

I sent an email to Abbott to comment on it, identifying the batch number, without claiming anything or asking for explanations, simply in case they have to evaluate this batch to take measures such as withdrawing it or whatever.Wow, my intention was to inform you for your interest.

The response was a shitty response.The same as in your case, they gave me a list with the compatibility of devices and operating systems without even asking me which one was mine.

I think the worst of all, more than a defective batch, is that the treatment of patient care (not customer) is regrettable.

Does anyone have experience raising these issues to the corresponding health department?Or the AEMPS?

@pva91 said:

Hello@juanen_

In my case I already have 4 sensors from the same batch with problems: 3 of them were constantly disconnected and one on the second day started with the reading pause error until the error that the sensor reached the end of its life came out (despite which it continued to work).

I sent an email to Abbott to comment on it, identifying the batch number, without claiming anything or asking for explanations, simply in case they have to evaluate this batch to take measures such as withdrawing it or whatever.Wow, my intention was to inform you for your interest.

The response was a shitty response.The same as in your case, they gave me a list with the compatibility of devices and operating systems without even asking me which one was mine.

I think the worst of all, more than a defective batch, is that the treatment of patient care (not customer) is regrettable.

Does anyone have experience raising these issues to the corresponding health department?Or the AEMPS?

This is what usually happens when they omit patients' complaints, recommendations, suggestions because they see themselves as having an advantage (Healthcare concession) over the competition.When you lose that and the competition eats your toast, what is happening to them with dexcom when they win the concession, they are no longer interested in being attentive and kind.I hope that more sensors continue to appear on the market and healthcare values ​​them so that patients can benefit from the best and most reliable.

For my part, screw Abbot, he deserves it well for ignoring the users of his sensors, who have been reporting errors for some time now, without providing a solution, just changing the sensor (there would be more to do), but without guaranteeing that it would fail again, because for them the failure is always due to the user's mobile device.

Hello good @

The S24 is a compatible terminal (I have the S24 Ultra and they don't give me any problems when I call them).

That does not mean that the sensors give a lot of errors, but the terminal is on its compatible list.

Yes @BaradDurr but I have the S24 5g and the "engineers" say that it is not the same as the S24... what do you think...

The mother who P....

BaradDurr said:
@BaradDurr said:

Hello good @

The S24 is a compatible terminal (I have the S24 Ultra and they don't give me any problems when I call them).

That does not mean that the sensors give a lot of errors, but the terminal is on its compatible list.

This compatibility lag is an immense absurdity no matter how you look at it, it turns out that both Apple and Samsung are compatible with all their current and previous models.What a coincidence that this same circumstance occurs in the competitors' sensors.Now, the only thing that differentiates one Android mobile from another is its customization layer, but the Android version is the same and the PlayStore is the same.I don't understand that an application is limited to a specific terminal, because if my terminal is not compatible it shouldn't let me install from the PlayStore.

What differentiates one cell phone from another in terms of connections (NFC Bluetooth,...) is the hardware it uses - which can be different even in the same manufacturer -, and what we call 'device driver', the small program that communicates the 'iron' (hardware) with the OS.And that is different too.Specific to each circuit and OS

These elements are what most influence the communications protocol between the sensor and the phone's OS to work well.

Older Bluetooth versions (before LE) used a lot of battery.For me, 14% is having the car phone activated.Without being in it!!!!

Now the LEs spend almost nothing and everyone wears headphones, watches.... So I lose the connection more times going down the street than at home.So much device emitting around...

(I have to change my phone this fall, Ufff how scary)

[[NO-TRANS]]

Grati said:
@Grati dijo:

Lo que diferencia a un movil de otro en cuanto a conexiones (NFC Bluetooth, ...) es el hardware que use -que puede ser diferente incluso en el mismo fabricante-, y lo que llamamos 'driver de dispositivo' el pequeño programita que comunica el 'hierro' (hardware) con el SO. Y que es diferente también. Específico para cada circuito y SO

Esos elementos son lo que más influye en que funcionen bien el protocolo de comunicaciones entre el sensor y el SO del teléfono

Las versiones de Bluetooth antiguas (antes de la LE) gastaban muchisima batería. A mi un 14% el tener activado el teléfono del coche. Sin estar en él!!!!

Ahora las LE gastan casi nada y todo el mundo lleva auriculares, relojes .... Con lo que pierdo más veces la conexión yendo por la calle que en casa. Tanto aparato emitiendo alrededor ...

(tengo que cambiar de movil este otoño, Ufff que miedo)

Pero todo lo que comentas se supone que  los móviles actuales lo tienen, lo que no entiendo es este estilismo para las lecturas de sensores por marcar como Samsung y Apple. Me parece absurdo tanta tontería de compatibilidad y que por ejemplo no empleen el esfuerzo en pie ejemplo que nuestros datos (a los que te obligan a ceder o no te deja registrar) estén a buen recaudo y seguros, no siendo utilizados para  lucrarse. Lo más gracioso es que luego las app no son nada del otro mundo y sin embargo hay aplicaciones de código abierto no oficiales que les dan mil vueltas a las oficiales, pero es preferible emplear el tiempo en intentar que esas app no oficiales les quiten la tostada capando y restringiendo la conexión con el sensor de ahí viene la incompatibilidad con muchísimos móviles.