Open kalpo opened 2 years ago
./nfc.py on: (...) if the feature is already on it gives some grief:
I don't know whether we'd be able to distinguish "device on" and "device communication problem" cases.
I highly encourage any volunteer to poke around this device as the traffic dumps do not show any kind of checking being done by the Windows driver.
Unfortunately I don't have time to analyze this now, but I'll leave it as an open item.
./nfc.py reset: Also fails if it is already on in the same way. So I guess it seems to do what it is supposed to do?
It definitely does not fail in the same way - there is no communication with the device in the reset method. Could you provide the logs for failed reset? It is a low-level reset that works for me every time - whether the NFC is on or off.
You are right. It seems like a hassle that is not worth the trouble.
Regarding the reset thing. You are also right, I must have mistyped something because it now works perfectly.
Thanks again!
I have tested the script on my latitude e7270
./nfc.py off: works great every single time ./nfc.py on: works great when coming from an off state. But if the feature is already on it gives some grief:
./nfc.py reset: Also fails if it is already on in the same way. So I guess it seems to do what it is supposed to do?
Anyway, hope this is of any help. I would suggest adding an exception or a check to contain the tracebacks.