Hi @lucaweiss, I have some issues sending you a private message (the “message” icon does not appear). I just sent you using the email support@fairphone.com. Hoping you received it well. I would be happy to check this version and hopefully make the vital application work again!
Thank you for the support,
Guillaume
Hi and welcome to the forum.
New users have limits to their options, one being unable to send private messages.
Thank you for this information. I have installed Glimp, but it doesn’t work with freestyle 2.
When I try to scan the freestyle sensor, I hear two vibrations but the glycemia is not written.
And I receive the notification “Libre sensor of unknown or unsupported type”.
I read more carefully the doc of Glimp : it doesn’t work for freestyle 2.
I conclude that NFC is working (with the vibrations) but that the librelink application doesn’t work (and until now, Abott does nothing to correct it).
Apologies for what may have been seen as a solution. I have no idea on the workings of any diabetes apps or devices, I just searched and found that link to Glimp and thought it may be of use.
Hey @lucaweiss,
Do I understand correctly, that Fairphone won’t release a Hotfix for this issue, but we’ll have to wait until October for the next major release?
I would call this a Hotfix
That’s a build to test a Hotfix. Developed at a rapid velocity, which I admire. 
A Hotfix would be publishing the build, prooven to resolve the issue, as an official update. On the other hand, if one waits to release the update, to bundle it with other changes, it’s not a hotfix anymore.
Than I guess you have answered your question yourself😉why not using the fix offered even if its not officially released?
Good question 
Im using my mobile as 2fa device for my private and business banking processes, requiring an official build. Feels like we might want to continue this conversation in private, since it’s getting a bit derailed. Just send me a DM, I’m happy to keep talking.
The main question was to understand the release plan: Do you plan to wait with the release until a new minor update is ready (maybe October), or do you plan to release the fix as early as possible @lucaweiss?
A topic exists with NFC broken after latest update. But it’s not NFC, which is broken, NFC works perfectly. It’s the Abbott Freelink application, which is broken. It’s a serious problem, for the diabetic type 1 patient, who used this application.
I moved your post, as the topic is about the Freestyle Libre and not NFC in General, will update the title.
Edit: the issue as already identified and will be fixed with the next update as indicated above
Hi, I would like to opt in this special build.
Is this still possible now ? I really need this to work asap.
Cheers
Hi and welcome to the forum.
As you will note from the post you refer to you would have to send your IEMI number to the author
In that post you will note the offer has been struck through as if it is no longer an option
In order to send a message anyway you will ‘need’ to up your status
See
Your decision is perfect. Thank you really much.
Hi
Has anyone tested to new build already? Does it work?
Thanks!
Yes it works and will be implemented
When will the new build released?
And sorry, the so called hotfix with IMEI is no solution!
Worked for several years in root cause analysis team. No customer would accept such a hotfix, which brings different issues, like banking apps not working.
It would be just an exchange of one problem with an other.
Real solution would be a certified hotfix, which doesn’t cause such side-effects.
That might be correct for you and there might be others who dont have problems with an uncertified hotfix for whatever reason, else no one would have volunteered I guess…and thanks to those who volunteered else no one would know if the fix is a fix…
Why not? Why not testing hotfixes and updates inhouse, as a good working quality control would do?
I think there’s mostly a problem in communication here…
As far as I understood, the actual fix will be released with the next regular Android update that is supposed to ship soon.
The provided “hotfix” was a test build, where interested users could register for by providing their IMEI. This was done to make sure that the fix the fairphone team implemented will actually work.
As was discussed within this topic, the fairphone team is not able to actually test the fix themselves, since this is an app specific problem and the app requires a working glucose sensor to actually do stuff.
The expectation that the fairphone team will elect someone internally to buy, apply and wear a sensor is maybe a bit much, isn’t it?