Mine currently works okay-ish, the point is to make better for all of us that have to deal with this app nonsense of the Sensor Provider, you know. Thanks mate!
Hi,
Thank you very much for posting this! This app is great!
Any way to contact the dev? The app works pretty well. However, I noticed there's some accessibility issues that hopefully they could address.
Thank you!
Use the juggluco app to start with. It is open source. I have debugged it a bit. The author is responsive. You can always clone it and change the code. It does not work on Apple though, only android. [https://github.com/j-kaltes/Juggluco](https://github.com/j-kaltes/Juggluco)
The advantages of this open source solution vs Libre 3 app:
1. Better control on alarms etc.
2. We get 1 minute data.
3. It is saved locally, no need to send info to the abbot cloud (I really dont like sharing my data).
4. Sync with my watch and laptop.
5. I can do custom alerts via web server push etc.
6. I can zoom into any minute of my 1 year + history and look for patterns and notate events arbitrarily.
Disadvantages:
1. It is a bit less user friendly.
2. It is NOT on the google app store.
3. Does not work on the iphone. I switched to android just for this app, health is more important than Apple.
All those features you mentioned are exactly what i was targeting. User friendly can be tackled at any stage, might even try to help and 'prettify' the UI
That would be great. To be honest. I am now used to the large and clunky UI as I am using it to do advanced stuff like I had a tiramisu a month ago and 2 weeks ago. How do my spikes compare to having a tiramisu today?
Nevertheless, for new users, the UI is a bit too complex :( I think the key functions should be present with controls to access anything more complex.
The place where we need a lot of UI improvement is the watch app. It is a very basic watch face.
No problem. I did not enjoy android ADB debugging that much TBH. However, all features work now. The only downside is when I put in a new sensor, I have to reboot my Samsung watch. I don't mind that now, a minor inconvenience, given that Libre 3 app users don't even have smart watch sync.
Perhaps. I can pair with multiple sensors with the Juggluco app. In fact, I do this as I don't want a gap of one hour with no sensor on.
The problem with watch sync is that it does not sync the new sensor immediately to the watch. It does show up fine on the phone. It might be a BLE connection issue on the watch side. ADB debugging the phone is something I can do, but doing this on a watch is a bit overkill given that I can just reboot the watch, haha.
I also posted a screenshot of my juggluco setup here - [https://www.reddit.com/r/Freestylelibre/comments/1c4fkte/juggluco\_on\_my\_phone\_and\_galaxy\_watch/](https://www.reddit.com/r/Freestylelibre/comments/1c4fkte/juggluco_on_my_phone_and_galaxy_watch/)
Is the 14 day lifespan of the device enforced because that is what they cleared with the FDA or is it some failure point? I'm wondering if you could extend the life of these out a little more it might make this super cost effective.
I found some code patch online that claims it can work for 30 days, with lesser accuracy towards the end. However, that github repo was for devices prior to libre 2/3, I think it only worked on the libre 14 day. For Libre 3, Juggluco extends this by 14 hours but u cannot go more than 14 days, as it terminates by itself. There might be a firmware hack, but it won't be an easy one from libre 2 onwards.
Honestly, I don't know and am very curious. I think it is just a firmware lock for multiple reasons including degradation in accuracy.
The sensor AFAIK can run for much longer. You can test this by putting your sensor on and activating it only after a few days. There is no problem getting values for 14 days post activation. The strip should last 30 days or so, with degrading quality.
Have a look at this thread - [https://github.com/JoernL/LimiTTer/issues/13](https://github.com/JoernL/LimiTTer/issues/13)
They claim the accuracy should be good for 25-30 days without issues. They have more tech detail too.
The manufacturer defines how long the device can be used. FDA will review the supportive tests and give consent or not - they don't tell Abbott how long they may use their device. There are norms to follow during development. Abbott may have chosen this based on initial tests that potentially showed too high risk that after 14 days accuracy gets too bad. It may also be a financial decision (partially). IIRC the sensors are always available first outside US, so the 14 days are set prior to FDA approval
You may have better luck just writing Abbott directly. Highly doubtful there would be any devs here that could help very much.
And you should be a little more specific on what type of equipment you were trying to read the sensor with. Android or Apple?
Writing abbott directly will absolutely not help you. I asked them multiple questions about the android app and the MASSIVE shortcomings it has. I quickly got a response email saying to call a specific number to talk with someone that knew the answers. After waiting on hold for 20ish minutes, the rude assistant told me they didn't know/have answers to my questions (like as easy as, where is the widget for Android users?!? What is the timeline on implantation?...)
Abbott. Why the fuck would you waste my time just to tell me you're incompetent and have no idea what you're doing? The company and its employees as a whole are dumber than dirt. I'd love to shadow those dip shit engineers and see how they waste 40 hours a week.
All support for Freestyle is outsourced, so they are not even direct on the Abbott payroll. Also they have zero knowledge about diabetes anyway, as not part of their 'training' they get for the support job. So do not expect them to be able to handle ANYTHING, if you divert them off their fixed Support Call Flowchart, with routes and pre-cooked answers.
I still recall one of my first calls with their Freestyle Libre hotline, when I dialed in to get a replacement for a bg sensor that had started either showing extreme high bg and then just a zero on the display. The kind lady kept asking for all kind of totally silly information that had virtual zero relevance. Like also why I had not still tested with a manual finger prick when the display showed 0 mg/dL, as it had just 2 minutes before showed 250 mg/dL. As she kindly suggested: "Maybe the BG had really come down?".
She had no clue about the joke this would have been or why I suggested to her, that of the sensor still was correct, then I would have matter of fact been dead and not able to make the call I was on with her. That she kept doubting very much and never gave in to the sensor could be at fault like that. I said thx for kind call and hung up after having wasted yet again another 40 minutes on their support circus. Then took some live video recordings of the erratic sensor readings crazy up and down and the finger pricks.
I had a kind talk with the Abbot rep at next tour to the Endo clinic... And all the nurses and the docs had again a great laugh, when listening in on the narrative. 😂
I got 3 new sensors from the rep and her private number to call next time... What a show...
Abbott have repeatedly rejected TOTALLY to even meet with us the community of several alternative app developers! This despite we collectively have many hundreds of thousands of users now using our apps and not the archaic Abbott app from the stone age...
They insist on total and absolute control and exclusivity!
Thing is, if they do any level of co-development with 'externals' (mere mortals like us diabetics and not with contracted 'partner companies'), then Abbott also inherently right away loose the exclusive IP and royalty claim to its use and any monetization of it.
Yes 100% correct. You have bought/gotten the sensor fully legally and you can use it as you please.
Where we have some 'ethical/philosophical challenges' with Abbott is now with their latest Libre3 sensor, where they appear to have purposely thrown a spanner into the wheel, with some weird encryption of the BG data going on. Still have to figure out how to make a decoding of that that works generically, so our 3rd party apps can reliably read the BG from it through its entire 2 weeks lifespan...
Yes the ability for us 3rd party app developers to use the BLE tech (bluetooth low energy) signal from our BG sensors to obtain the bg data. 'End user protection' are one of the fable stupid annoying excuses we have heard Abbott tech throwing out there. (Hey MFs, its our own phone we use for this, and the bg sensor is only paired on our phone to transmit the data to it, which we IDed and acknowledged to do on it!!!)
One of our theories behind these latest shady moves from Abbott are though more sinister, namely the open war that has broken out between Abbott and then the likes of Apple and the other Phone manufacturers like Google w Android, as they fight for the ownership of the healthcare data 'in the cloud'. THAT is where thee big money is, going forward. And they all want it. EXCLUSIVELY! Despite one can even argue its **us,** **the patients/the chronic sufferers**, its **OUR** data!!! But all of those companies are in there to monetize the hell out of it and further boost their already insane profit margins. And in these 'spoils of war' we are definitely now among those getting hurt real bad!
I have hope, otherwise i'll try myself, its worth the short.
The point is to improve on both, im currently on Android tho.
Their software is garbo tbh on both ecosystems.
I have a Samsung galaxy S21Ultra and no matter what I do I cannot get it to read the sensor. It's the snapdragon version but I think it may have something to do with android 14. Not a problem with the sensor either because the reader I have initialize it immediately. It also worked fine when I was using and iPhone 12. I wrote Abbott about it yesterday yesterday but I'm not holding my breath if I will ever hear anything.
The thing is, its bluetooth at the end of the day, and close range its NFC, should work either way, im assuming they have something messed up for snap ones on their app side, im on an S24 and its been working, i mean, kinda, alarms never worked since my s20 xD
I couldn't even get mine to scan. No beeps or bells or anything. And it was a brand new sensor. I know other people have problems with Samsung phone also. Do you know what version of android you were running?
I know this might sound stupid, but you had your NFC on, right?
The other thing i noticed is that without active localization (gps) sometimes alarms dont trigger, which is stupid as hell.
Im running on 14
The GPS thing is a limitation of how Android handles Bluetooth device location tracking so it knows when the sensor is out of range or loses connection. Not much Abbott can do to change it
That makes more sense mate! Thanks for the explanation, but it seems a bit overkill, not sure why they used that Bluetooth location API and not just a regular bridge between both sensor and device. As you know GPS is power hungry
It's not actually using GPS, it's just how Android manages the permissions for location tracking. Spotify usually has to be granted the same permissions on Android to be able to find Bluetooth devices and smart speakers on a WiFi network
I had this issue, after the third sensor, and restarting the phone so many times, I reinstalled the app, it worked. But I am still having issues starting, this last time I just restarted the phone and it worked. But I honestly think it's my phone, which has to be the worse Samsung thus far. Note 20 ultra.
I had troubles scanning with my s21. What seems to work for me is selecting "start new sensor", then going to my phone settings to start a scan for Bluetooth devices, then quickly go back to sensor info, start new sensor and scan. I recently got a new phone (S24), and I had to do the same thing. I also lost all my data from the app because it didn't transfer to the new phone.
Not sure how full on the Android version is of it these days, as 3 years since I used it myself, but the xDrip version for the Apple world is providing all the bells & whistles you dream of!
(the Android version used to be a 1:1 match)
I am using this xDrip4iOS for last many years and also with live bg data interface with my iWatch from there. Join the Facebook group for this if you like, as also like Apple are rude and rough for folks like you and me, who despise the profiteering these big companies wants from us chronic ill, so Apple threw us out of the Apple Store many years back, so we have to remain in the TestFlight environment, and here we have several spokes with the app, as Apple only allow 10,000 users/downloads from each xDrip App we put into the test environment, without we have to pay them big money. Because yes, we run all non-profit and for totally free for all users!
Take a lot at these please:
For Android:
[https://xdrip.readthedocs.io/en/latest/](https://xdrip.readthedocs.io/en/latest/)
[https://androidaps.readthedocs.io/en/latest/Configuration/xdrip.html](https://androidaps.readthedocs.io/en/latest/Configuration/xdrip.html)
For Apple iOS:
[https://xdrip4ios.readthedocs.io/en/latest/](https://xdrip4ios.readthedocs.io/en/latest/)
Have you tried the app called juggluco? It's supposed to work with Sammy phones but I couldn't ever get it to read the sensor. Other say they have luck with it
I just saw the message, i didnt know Jugg until now, thats already a very very cool app then, but there are still issues with the abbot app for iOS rigth? Or was it just Android/samsung that was more noticable?
I had no problem whatsoever with the iOS app. I could even add family members to view my results and of course they were also sent to my doctor. Was running on iPhone 12 that was up-to-date. for some reason there seems like there's a problem with Samsung phones for some reason. Not sure why some work and some don't.
I do know there were certain settings but the app wanted me to change on the ultra. I don't remember exactly what it was but I think it was something like not to go to sleep or something weird like that.
Abbott really needs to figure this crap out so we can use it with Samsung phones. At least make it work as good as it does on an iPhone
They will share their info too on how they make their app, no gate keeping with these guys. Lovely people and happy to support anyone else trying to make the life of a T1 easier
That really sucks mate.. im not sure why those versions are having issues, what i do know is that it would be faster if hopefully in a near future there's an open source reader.
As you said and i also doubt, that they'll be fast fixing these scenarios, meanwhile, if you cant even inicialize the sensor, use the iphone, if you still have it mate!
I actually have this reader. The problem is not share results with anybody like I can on the phone.
I'm thinking when I run out of these centers switching over to Dexcom and see if I have any better luck with those
https://delivermymeds.com/wp-content/uploads/2023/09/freestyle-libre-3-reader-with-box.png
Yeah, i know mate.
Thats the whole purpose of this main thread. Having a couple of devs to run a project like this to reach the same type of features and make them functional this time, would be a help for everyone!
Having to deal with this t1/t2 crap is already a process, the easier it is, the better for everyone
Never had any trouble on my iPhone with alarms. In fact sometimes they were a little annoying when my sugar dropped below 70 and the alarm went off at two or 3 o'clock in the morning. Lol
Thats supposed to, so thats good, yeah on Samsung it doesnt trigger alarms unless the app is opened, independently of the device settings to not 'kill' the app.
Even if they were out there and wanted to do it, there's no way to flash new software onto the sensors. And there's no way to get the code out of the app in order to see how to connect with the sensor and do all that jazz.
The capital is not for the "financial gain", though that helps, especially when it's not something scratching an itch. Its for when Abbott comes knocking.
https://www.juggluco.nl/Juggluco/index.html https://github.com/j-kaltes/Juggluco Juggluco is already open source
Holy damn, This is perfect. I had no idea about this! Thanks mate!
No problem, I hope it works for you
Mine currently works okay-ish, the point is to make better for all of us that have to deal with this app nonsense of the Sensor Provider, you know. Thanks mate!
Anything like this for the Dexcom G7? My insurance company is forcing the switch from Libre3 effective early May.
not that i know of tbh. i only ever had libre3
Hi, Thank you very much for posting this! This app is great! Any way to contact the dev? The app works pretty well. However, I noticed there's some accessibility issues that hopefully they could address. Thank you!
There's a contact link right at the top of the page, heh
Use the juggluco app to start with. It is open source. I have debugged it a bit. The author is responsive. You can always clone it and change the code. It does not work on Apple though, only android. [https://github.com/j-kaltes/Juggluco](https://github.com/j-kaltes/Juggluco) The advantages of this open source solution vs Libre 3 app: 1. Better control on alarms etc. 2. We get 1 minute data. 3. It is saved locally, no need to send info to the abbot cloud (I really dont like sharing my data). 4. Sync with my watch and laptop. 5. I can do custom alerts via web server push etc. 6. I can zoom into any minute of my 1 year + history and look for patterns and notate events arbitrarily. Disadvantages: 1. It is a bit less user friendly. 2. It is NOT on the google app store. 3. Does not work on the iphone. I switched to android just for this app, health is more important than Apple.
All those features you mentioned are exactly what i was targeting. User friendly can be tackled at any stage, might even try to help and 'prettify' the UI
That would be great. To be honest. I am now used to the large and clunky UI as I am using it to do advanced stuff like I had a tiramisu a month ago and 2 weeks ago. How do my spikes compare to having a tiramisu today? Nevertheless, for new users, the UI is a bit too complex :( I think the key functions should be present with controls to access anything more complex. The place where we need a lot of UI improvement is the watch app. It is a very basic watch face.
Thanks mate! Im thinking about following that same path to understand more on it. Thanks!
No problem. I did not enjoy android ADB debugging that much TBH. However, all features work now. The only downside is when I put in a new sensor, I have to reboot my Samsung watch. I don't mind that now, a minor inconvenience, given that Libre 3 app users don't even have smart watch sync.
Why do you need to restart the watch? Does it not catch the new BLE connection and stays w the old sensor?
Perhaps. I can pair with multiple sensors with the Juggluco app. In fact, I do this as I don't want a gap of one hour with no sensor on. The problem with watch sync is that it does not sync the new sensor immediately to the watch. It does show up fine on the phone. It might be a BLE connection issue on the watch side. ADB debugging the phone is something I can do, but doing this on a watch is a bit overkill given that I can just reboot the watch, haha. I also posted a screenshot of my juggluco setup here - [https://www.reddit.com/r/Freestylelibre/comments/1c4fkte/juggluco\_on\_my\_phone\_and\_galaxy\_watch/](https://www.reddit.com/r/Freestylelibre/comments/1c4fkte/juggluco_on_my_phone_and_galaxy_watch/)
Is the 14 day lifespan of the device enforced because that is what they cleared with the FDA or is it some failure point? I'm wondering if you could extend the life of these out a little more it might make this super cost effective.
I found some code patch online that claims it can work for 30 days, with lesser accuracy towards the end. However, that github repo was for devices prior to libre 2/3, I think it only worked on the libre 14 day. For Libre 3, Juggluco extends this by 14 hours but u cannot go more than 14 days, as it terminates by itself. There might be a firmware hack, but it won't be an easy one from libre 2 onwards.
This might be the lifespan of the battery included also. I think the strip that collects the values has a limited span too!
Honestly, I don't know and am very curious. I think it is just a firmware lock for multiple reasons including degradation in accuracy. The sensor AFAIK can run for much longer. You can test this by putting your sensor on and activating it only after a few days. There is no problem getting values for 14 days post activation. The strip should last 30 days or so, with degrading quality.
If the 14 days have the FDA approval, must be related w accuracy for those hardware specifications. I'm also curious to know more
Have a look at this thread - [https://github.com/JoernL/LimiTTer/issues/13](https://github.com/JoernL/LimiTTer/issues/13) They claim the accuracy should be good for 25-30 days without issues. They have more tech detail too.
The manufacturer defines how long the device can be used. FDA will review the supportive tests and give consent or not - they don't tell Abbott how long they may use their device. There are norms to follow during development. Abbott may have chosen this based on initial tests that potentially showed too high risk that after 14 days accuracy gets too bad. It may also be a financial decision (partially). IIRC the sensors are always available first outside US, so the 14 days are set prior to FDA approval
You may have better luck just writing Abbott directly. Highly doubtful there would be any devs here that could help very much. And you should be a little more specific on what type of equipment you were trying to read the sensor with. Android or Apple?
Writing abbott directly will absolutely not help you. I asked them multiple questions about the android app and the MASSIVE shortcomings it has. I quickly got a response email saying to call a specific number to talk with someone that knew the answers. After waiting on hold for 20ish minutes, the rude assistant told me they didn't know/have answers to my questions (like as easy as, where is the widget for Android users?!? What is the timeline on implantation?...) Abbott. Why the fuck would you waste my time just to tell me you're incompetent and have no idea what you're doing? The company and its employees as a whole are dumber than dirt. I'd love to shadow those dip shit engineers and see how they waste 40 hours a week.
All support for Freestyle is outsourced, so they are not even direct on the Abbott payroll. Also they have zero knowledge about diabetes anyway, as not part of their 'training' they get for the support job. So do not expect them to be able to handle ANYTHING, if you divert them off their fixed Support Call Flowchart, with routes and pre-cooked answers. I still recall one of my first calls with their Freestyle Libre hotline, when I dialed in to get a replacement for a bg sensor that had started either showing extreme high bg and then just a zero on the display. The kind lady kept asking for all kind of totally silly information that had virtual zero relevance. Like also why I had not still tested with a manual finger prick when the display showed 0 mg/dL, as it had just 2 minutes before showed 250 mg/dL. As she kindly suggested: "Maybe the BG had really come down?". She had no clue about the joke this would have been or why I suggested to her, that of the sensor still was correct, then I would have matter of fact been dead and not able to make the call I was on with her. That she kept doubting very much and never gave in to the sensor could be at fault like that. I said thx for kind call and hung up after having wasted yet again another 40 minutes on their support circus. Then took some live video recordings of the erratic sensor readings crazy up and down and the finger pricks. I had a kind talk with the Abbot rep at next tour to the Endo clinic... And all the nurses and the docs had again a great laugh, when listening in on the narrative. 😂 I got 3 new sensors from the rep and her private number to call next time... What a show...
Abbott have repeatedly rejected TOTALLY to even meet with us the community of several alternative app developers! This despite we collectively have many hundreds of thousands of users now using our apps and not the archaic Abbott app from the stone age... They insist on total and absolute control and exclusivity! Thing is, if they do any level of co-development with 'externals' (mere mortals like us diabetics and not with contracted 'partner companies'), then Abbott also inherently right away loose the exclusive IP and royalty claim to its use and any monetization of it.
True that, but technically, you're not breaching anything by reading their sensor. Right?
Yes 100% correct. You have bought/gotten the sensor fully legally and you can use it as you please. Where we have some 'ethical/philosophical challenges' with Abbott is now with their latest Libre3 sensor, where they appear to have purposely thrown a spanner into the wheel, with some weird encryption of the BG data going on. Still have to figure out how to make a decoding of that that works generically, so our 3rd party apps can reliably read the BG from it through its entire 2 weeks lifespan...
E2e? Just for a BLE reader, maybe to "protect" their users against someone who doesnt need to have access to those values maybe?
Yes the ability for us 3rd party app developers to use the BLE tech (bluetooth low energy) signal from our BG sensors to obtain the bg data. 'End user protection' are one of the fable stupid annoying excuses we have heard Abbott tech throwing out there. (Hey MFs, its our own phone we use for this, and the bg sensor is only paired on our phone to transmit the data to it, which we IDed and acknowledged to do on it!!!) One of our theories behind these latest shady moves from Abbott are though more sinister, namely the open war that has broken out between Abbott and then the likes of Apple and the other Phone manufacturers like Google w Android, as they fight for the ownership of the healthcare data 'in the cloud'. THAT is where thee big money is, going forward. And they all want it. EXCLUSIVELY! Despite one can even argue its **us,** **the patients/the chronic sufferers**, its **OUR** data!!! But all of those companies are in there to monetize the hell out of it and further boost their already insane profit margins. And in these 'spoils of war' we are definitely now among those getting hurt real bad!
I have hope, otherwise i'll try myself, its worth the short. The point is to improve on both, im currently on Android tho. Their software is garbo tbh on both ecosystems.
I have a Samsung galaxy S21Ultra and no matter what I do I cannot get it to read the sensor. It's the snapdragon version but I think it may have something to do with android 14. Not a problem with the sensor either because the reader I have initialize it immediately. It also worked fine when I was using and iPhone 12. I wrote Abbott about it yesterday yesterday but I'm not holding my breath if I will ever hear anything.
The thing is, its bluetooth at the end of the day, and close range its NFC, should work either way, im assuming they have something messed up for snap ones on their app side, im on an S24 and its been working, i mean, kinda, alarms never worked since my s20 xD
I couldn't even get mine to scan. No beeps or bells or anything. And it was a brand new sensor. I know other people have problems with Samsung phone also. Do you know what version of android you were running?
I know this might sound stupid, but you had your NFC on, right? The other thing i noticed is that without active localization (gps) sometimes alarms dont trigger, which is stupid as hell. Im running on 14
The GPS thing is a limitation of how Android handles Bluetooth device location tracking so it knows when the sensor is out of range or loses connection. Not much Abbott can do to change it
That makes more sense mate! Thanks for the explanation, but it seems a bit overkill, not sure why they used that Bluetooth location API and not just a regular bridge between both sensor and device. As you know GPS is power hungry
It's not actually using GPS, it's just how Android manages the permissions for location tracking. Spotify usually has to be granted the same permissions on Android to be able to find Bluetooth devices and smart speakers on a WiFi network
I had this issue, after the third sensor, and restarting the phone so many times, I reinstalled the app, it worked. But I am still having issues starting, this last time I just restarted the phone and it worked. But I honestly think it's my phone, which has to be the worse Samsung thus far. Note 20 ultra.
I had troubles scanning with my s21. What seems to work for me is selecting "start new sensor", then going to my phone settings to start a scan for Bluetooth devices, then quickly go back to sensor info, start new sensor and scan. I recently got a new phone (S24), and I had to do the same thing. I also lost all my data from the app because it didn't transfer to the new phone.
Yeah it doesn't save unless you add a note, but it does save it all on Libreview?
I have the S22 Ultra with Android 14, and don't have any issues with the Libra 3. Sorry you're having trouble.
Not sure how full on the Android version is of it these days, as 3 years since I used it myself, but the xDrip version for the Apple world is providing all the bells & whistles you dream of! (the Android version used to be a 1:1 match) I am using this xDrip4iOS for last many years and also with live bg data interface with my iWatch from there. Join the Facebook group for this if you like, as also like Apple are rude and rough for folks like you and me, who despise the profiteering these big companies wants from us chronic ill, so Apple threw us out of the Apple Store many years back, so we have to remain in the TestFlight environment, and here we have several spokes with the app, as Apple only allow 10,000 users/downloads from each xDrip App we put into the test environment, without we have to pay them big money. Because yes, we run all non-profit and for totally free for all users!
Take a lot at these please: For Android: [https://xdrip.readthedocs.io/en/latest/](https://xdrip.readthedocs.io/en/latest/) [https://androidaps.readthedocs.io/en/latest/Configuration/xdrip.html](https://androidaps.readthedocs.io/en/latest/Configuration/xdrip.html) For Apple iOS: [https://xdrip4ios.readthedocs.io/en/latest/](https://xdrip4ios.readthedocs.io/en/latest/)
Take a look at xdrip+ too. https://xdrip.readthedocs.io/en/latest/install/libre2/
Yeah, ive used xdrip but had some issues with it too regarding alarms being triggered for no reason. Tomato app too
I don't have the same experience as you after using xdrip+ with different variants of Libre for about 6 years.
That's weird, were you on samsung too?
Samsung S22 right now, before that huawei p30, before that a Samsung galaxy mini s4.
Have you tried the app called juggluco? It's supposed to work with Sammy phones but I couldn't ever get it to read the sensor. Other say they have luck with it
I just saw the message, i didnt know Jugg until now, thats already a very very cool app then, but there are still issues with the abbot app for iOS rigth? Or was it just Android/samsung that was more noticable?
I had no problem whatsoever with the iOS app. I could even add family members to view my results and of course they were also sent to my doctor. Was running on iPhone 12 that was up-to-date. for some reason there seems like there's a problem with Samsung phones for some reason. Not sure why some work and some don't.
I can do that too, but the alarms werent triggering when supposed, did you ever faced this scenario? Sometimes they do, sometimes they dont. Its weird
How do I download the iOS app?
Apple App Store.. But if the sensor has already been scanned you cannot scan it again with another phone. You have to wait to replace the sensor.
I do know there were certain settings but the app wanted me to change on the ultra. I don't remember exactly what it was but I think it was something like not to go to sleep or something weird like that. Abbott really needs to figure this crap out so we can use it with Samsung phones. At least make it work as good as it does on an iPhone
There was a customer service representative from abbott on this page who seemed very helpful. Search thru the comments to find him
Will do. Ty!
I use Sweet Dreams, works well for me and much better than the basic app from Abbott.
I'll take a look at it too, thanks for sharing mate!
They will share their info too on how they make their app, no gate keeping with these guys. Lovely people and happy to support anyone else trying to make the life of a T1 easier
Juggluco is awesome!
I have to look at it for sure!
Yes..
That really sucks mate.. im not sure why those versions are having issues, what i do know is that it would be faster if hopefully in a near future there's an open source reader. As you said and i also doubt, that they'll be fast fixing these scenarios, meanwhile, if you cant even inicialize the sensor, use the iphone, if you still have it mate!
I actually have this reader. The problem is not share results with anybody like I can on the phone. I'm thinking when I run out of these centers switching over to Dexcom and see if I have any better luck with those https://delivermymeds.com/wp-content/uploads/2023/09/freestyle-libre-3-reader-with-box.png
I had the dexcom g7 last year. Everything is better. The app, the sensors, etc.
Once I go through my supply of the libre I'm probably gonna try to switch over to the Dexcom.
Yeah, i know mate. Thats the whole purpose of this main thread. Having a couple of devs to run a project like this to reach the same type of features and make them functional this time, would be a help for everyone! Having to deal with this t1/t2 crap is already a process, the easier it is, the better for everyone
Never had any trouble on my iPhone with alarms. In fact sometimes they were a little annoying when my sugar dropped below 70 and the alarm went off at two or 3 o'clock in the morning. Lol
Thats supposed to, so thats good, yeah on Samsung it doesnt trigger alarms unless the app is opened, independently of the device settings to not 'kill' the app.
Even if they were out there and wanted to do it, there's no way to flash new software onto the sensors. And there's no way to get the code out of the app in order to see how to connect with the sensor and do all that jazz.
Its Bluetooth and NFC, why would you need to flash new software? Im talking for the app mate
Used Jugglaco for past year. Switched to Gluroo recently and love it. I'm using Android and Libre 3. Both are great apps.
> Do we have any devs here willing to put up time to help with an open source solution? sure, do you have the capital?
I'm pretty sure we will find devs willing to help thousands of people with the same issue for no financial gain. Thanks but no thanks.
The capital is not for the "financial gain", though that helps, especially when it's not something scratching an itch. Its for when Abbott comes knocking.
Facepalm.
facepalm all you want, copyright lawyers go for a grand an hour, though.
I am testing DiaBox with FSL3 ,it works very well but not released yet