You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two android devices I've been testing the RFIDtools app with; a Pixel 3a (Android 11) and a Samsung Galaxy J7 Perx (Android 8.1). When attempting to connect to the device via the Blue Shark module on the Pixel 3a, I receive the following error message: "Communication error, please check permission or voltage!" . However on the J7, I am able to connect and start a Termux session successfully. I have tried reinstalling the app
The resolution here may have to deal with the changes in permissions have that occurred in the latest Android, but its unclear to me at this time. However, the ideal resolution is to get this to start a connected session via Termux on Android 11. I have tried to give the application full location permissions (not just while running), but the issue isn't resolved.
The text was updated successfully, but these errors were encountered:
Although I don't have an Android 11 version of the mobile phone (official),
but I still flash my OnePlus5T to a unofficial Android 11 version of the system.
On my oneplus5T, I didn't find any connection problems...
So, can you reboot your phone or reinstall "RFID Tools"?
This may be the Bluetooth problem of the mobile phone, or the Bluetooth problem of the PM3.
Because that message only appears when the connect to Bluetooth SPP fails.
I have two android devices I've been testing the RFIDtools app with; a Pixel 3a (Android 11) and a Samsung Galaxy J7 Perx (Android 8.1). When attempting to connect to the device via the Blue Shark module on the Pixel 3a, I receive the following error message: "Communication error, please check permission or voltage!" . However on the J7, I am able to connect and start a Termux session successfully. I have tried reinstalling the app
The resolution here may have to deal with the changes in permissions have that occurred in the latest Android, but its unclear to me at this time. However, the ideal resolution is to get this to start a connected session via Termux on Android 11. I have tried to give the application full location permissions (not just while running), but the issue isn't resolved.
The text was updated successfully, but these errors were encountered: