search

j-kaltes / Juggluco

Android app for Freestyle Libre 1,2 and 3 and Chinese Sibionics sensors
GNU General Public License v3.0
217 stars 56 forks source link

Scan error on FSL2-RU sensor change #154

Open AgushkaNightscout opened 6 months ago

AgushkaNightscout commented 6 months ago

I have same#41 issue with L2 RU version sensor. My dia-phone (Cubot Poket, Android 10) can't intercept already activated (by Realme 10) with Abbot's original app L2-RU sensor with NFC (error 18), although L3 could activate. But another phone (Realme 10, Android 13) can (no error)! I activate sensor with Realme and then transfer the sensor to Cubot using Juggluco's "Get Glucose values on Android device without NFC" greatest option. Why can this happen?

j-kaltes commented 6 months ago

It is certainly not the same issue as you refer to. That issue was solved long ago with an update of Juggluco.

When you can't scan a sensor with a particular phone, there is something wrong with NFC of that phone.

AgushkaNightscout commented 6 months ago

"I changed to a new libre2 sensor and it scans reliably in libre2 app, but juggluco always gets a scan error (18)." - I have exactly the same app behavior (version 8.0.3). Why does FS3 activate without problems but FS2RU does not activate (intercept) with error 18? Do they have such different NFC elements?

j-kaltes commented 6 months ago

But you can scan the same Libre 2 sensor with Juggluco on another phone?

AgushkaNightscout commented 6 months ago

Yeah, and it's totally confusing. Cubot can't even activate FS2RU with original Abbot's app. I'll try to take it apart and see what's wrong with the NFC module. But why FSL3 can be activated? I can't get my head around)

j-kaltes commented 6 months ago

You can run a logging version from https://www.juggluco.nl/Juggluco/download.html#bugreport and e-mail trace.log to me. You can also send logcat.txt: adb logcat -d >logcat.txt

If it is a US like Libre 2 sensor, the scanning is very complicated.

AgushkaNightscout commented 6 months ago

Ok, thank you for advice! Sensor will expire in 5 days, then I will activate (intercept) a new one with the logging version and send you logcat.txt.

j-kaltes commented 6 months ago

Why not just scan with you current sensor and send trace.log and logcat.txt?

AgushkaNightscout commented 6 months ago

Oh, right! I forgot how cool your app is! When my kid gets home from kindergarten, I'll scan it.

AgushkaNightscout commented 6 months ago

Just emailed the logs to you, please take a look at them.

j-kaltes commented 6 months ago

I looked at the logs. You scanned two times with two different errors. A scan consists of multiple NFC commands and some of them succeed and others failed. But NFC often fails momentarily because the sensor wasn't placed on the right spot of the phone or so, as was certainly the case with the first error. Because I have only one scan, I can't judge whether scanning never comes past the point of the second scan error.

AgushkaNightscout commented 6 months ago

I applied the phone a few times, all the time error 18, please take a look at logs on email.