Hi Marco,
your last sentence is not correct!
You can activate the sensor with Libre2 device first and use the smartphone as 2nd device.
The only point ist that the 2nd device can not use the alarm function.
User that so all the time with both devices 
I have the same problem. After the update 8901.4.A.0016.6, I have “scan error” each time, I try to scan the sensor.
Same problem here. I rely on the phone to get glucose readings and it’s a huge inconvenience having to switch to alternative tools.
Hi,
It would be good if anyone can capture adb logs when the scanning is done(and the error is shown).
adb logcat -c && adb logcat -b all > nfc_issue.log and adb logcat -c && adb logcat -b all "*:E" > nfc_issue_errors.log the next time.
I am just curious to understand what’s going wrong and see if I can do something.
Thanks.
Hi everyone,
Instead of the adb logcat logs as @TeamB58 mentioned, it might be easier to grab a “bug report” on the device after the scan failed, see:
You can upload the zip here:
https://fileshare.fairphone.com/filedrop/software-longevity-FP3
Also for anyone familiar with this sensor, is it possible to read anything from the sensor fresh out of the packaging without it being applied on the arm for testing purposes? If that would be possible we can buy one to test and debug in the office.
I have the same issue and users have been trying to help, but no solution yet. It sounds like my phone is in the same state as yours.
If it doesn’t get fixed I am moving to a google phone - I don’t need the extra hassle of a phone not working properly.
Wishing you luck!
Why would you go for a Google phone aka Pixel phone when they also had troubles with NFC ? Source : Google Pixel 'NFC pay' broken or unavailable after June update for some
As far as I know, it won’t work if it’s not applied on the arm.
Hello @lucaweiss, nice meeting you. I’ve uploaded an android bug report at the URL you shared above. Let me know if that’s what you need or I can help in any other way.
I managed to reset the phone and reapply the last working version. (Quite complex and inconsistently documented.) Then restored Google backup, and fiddled about getting my phone to behave and look the way it used to. (All in all, about 1/2 day.) The good news was that after logging back into my LibreView account, I was able to resume scanning the sensor I was wearing as if nothing had happened!
Hi all,
we’ve prepared a beta build with minimal changes to try to see if it fixes this issue.
For anybody interested, please send me the IMEI1 of your FP3 via forum direct message so we can add you to this special build.
Please note that this build is not Google certified so any apps relying on certification (e.g. banking apps or Netflix) probably won’t work on that version. Also this won’t sign you up to the regular beta program, just for special builds for this issue.
Thanks for everyone who reached out and who confirmed that the experimental build solves the issue! We’ll be including this fix in the next update that is being worked on right now.
Since there was at least no immediate outcry that it would be nonsense, can you or anybody from the development team say, whether this here could be considered by Fairphone or why it would be impossible …
IMEI [Edited, see below]
I’ll consider the beta if there’s a good chance it fixes the issue. I do not use the phone for banking etc.
Simon (Bill_Yellow)
Forum consensus seems to be it is not a good idea to post the IMEI publicly, therefore edited.
Another indication for this is that interested users were asked …
To send a direct message, tap or click on → @lucaweiss ← (or the avatar picture accompanying the posts) and then use the “Message” link.
Thanks, I did not intend to publicly share my IMEI, but not really au fait with how this forum interface works.
What exactly does that update fix? NFC only, the bluetooth-issue, too?
@MikeSixPointEight It’s just a change for NFC that aligns some code to how it was in the previous update. Otherwise it’s identical to the 0016.6 build.
While we’re looking into buying one of these Freestyle Libre 2 sensors to hopefully reproduce the issue, currently we don’t have a way to do so. So we’re hoping to know whether this change fixes the issue or not.
@kizorro You would be able to switch back to the normal stable builds with the next MR release which will presumably be released in October. Downgrades on Android are not supported.
Too bad, but ok, you’re working on the problems. I like that.
Hi, I have the same problem
My IMEI1 is: xxx
Thanks
hi and welcome to the community, I removed your IMEI number, please contact lucaweiss in a private message instead