Hi,When I place the phone near the L2 sensor it vibrates twice and displays the same scan error 335 (with lengthy description stating it can't scan the L2 and I should try again).
Thanks for your thoughts!Curious one. I had a quick look at NFC specs and they are not region-specific - the same chips and radio settings are used worldwide, unlike say WiFi where there are 11 2.4Ghz channels available for non-licensed use in the US while there are 13 available channels in most other countries. NFC is indeed the same everywhere.
That's not to say the use of specific devices in specific regions is not restricted though. Medical devices must be approved by the regulatory authority in the market for which they are sold - so the FDA in the US, the EU regulators in the EU, Japanese in Japan and so-on. Both the app and the sensor need approval as a paired system before it can be sold as a medical device. For this reason when you go to download the LibreLink app it will give you a version that is specific to your region, determined by the region of your app store, and the app probably won't work with sensors sold in other regions. You might have a regulatory boundary problem that's not due to NFC.
Are the region settings on your phone working correctly as a UK-based phone? You might be able to tell from the title of the LibreLink app in the app store - when I search for LibreLink in the Google Play store the title of the result I get is 'FreeStyle LibreLink - IE' denoting that the app version I'd be downloading is the one specific to Ireland. Do you see 'UK' at the end of the app title in the store? Another quick way to test store region is to search for an app that is only available in the UK - for example 'BBC iPlayer'. That's an app that's not available on my phone.
I'm not sure how app store regions are set - it might be a phone setting or it might be based on IP address or similar as a way to determine the phone's location. The VPN solution might work if it's IP address based and if the phone is currently in a country outside of the regulatory jurisdiction in which the sensor was purchased. I.e. - if you bought a sensor in the UK but your phone was in the US, using a VPN service to fool the app store into thinking your phone was on UK soil might allow you to download the matching app version.
Beyond that I don't have any ideas. I don't know a lot about NFC as applies to this problem beyond the fact that at a hardware level the standards devices are built to are identical worldwide.
Yeah I know what you mean... finding the NFC sensor is tricky sometimes.Hi,
Have you placed the NFC area directly to the sensor, holding steady for a while?
Or sort of “Jedi mind trick” waived the device over the Libre?
Did you “clone” from your old phone? Which usually grabs purchased apps from your installed history. (free ones too.)
You might need to log back into accounts. I can’t remember if I needed to with librelink..
Yeah...I'm kinda hoping the issue is this tbh. The NFC on this phone is temperamental so the issue may be a weak or laggy signal ...which then makes it much harder to find the sweet spot. That said, it could also be a weak/laggy L2 sensor too. Two replacement sensors are coming direct from Abbott so I'll find out soon enough.I don't think this is a regional lock issue as AFAIK Abbott have a different error message for that case.
This may be just a case of NFC unreliability. If you are getting the 335 error, then the Libre is able to realise that you are trying to scan the sensor (so NFC is working), but the scan does not complete.
My only suggestion is to try to find where on the phone the NFC sensor is located and try to hold that over the sensor. If you are like me, you might tend of move the phone about while trying to get it to scan - which could mean you start to get a signal and then move away before the scan is complete (which is why the 335 message talks about hold the phone steady).
I've changed my phone recently and haven't figured out yet the trick to scanning reliably so my Event log is full or 335 errors, but it does scan eventually.
I’ve got a 4300 mAh battery on my device with librelink & Diabox running in the background which can comfortably get me through the day..When it's working correctly, the Libre connection really doesn't use that much battery. Mine is currently showing as 0.5% of my total battery usage.
I remember there was a bug in some earlier versions where it was consuming more like 50%, but that was fixed long ago.
You still need to start up sensor via NFC. No other way.Options would be to use the Bluetooth from the libre to pull data into another app (Shuggah, xDrip+ etc) and bypass the Librelink NFC scanning.
That way you could scan and start the sensor using the BG meter, and pick the readings up from your phone (I know that can be done using xDrip - not sure about Shuggah as not a user).
That opens up all sorts of other possibilities (BG on a watch, better reporting etc) as well, worth consideration
Correct - that's why I mentioned starting a sensor with a BG meterYou still need to start up sensor via NFC. No other way.
Sounds a bit daft.Thanks for all the replies. I've been researching various approaches since the original post. Upshot is, unfortunately I can't use my kick-ass Doogee mobile because of the NFC issue (which is confirmed not to work with Libre sensors). Massive shame, but haho.
I'm successfully using my old Google 3XL as a burn phone really with both LibreLink and Diabox apps running on it. I manully NFC scan my Libre once a day and then 'force stop' to push ALL the days data to LibreView.
Diabox is mirrored to my Gwatch4, which is working brilliantly so far. Still got thing to sort like data and calibrating ,but on the whole, this setup seems to be giving me improved control.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?