@kdfrawg Well, the external device reads the codes and send the decoded data to the app over Bluetooth. That means that I haven't done any work on the actual code reading…
In the end, it was indeed a developer error once again. The app needs to pair the device before one can connect to it. Does the Android documentation explicitly say this? Well, maybe, but not in a clear way. Now I can read barcodes and QR codes and the app stores them into its database.
Ho hum. Can't make the app connect to the barcode reader because the reader uses a Bluetooth profile that is not supported by Android by default. Luckily didn't spend days before I found this issue.
@matigo Yes. Just for the sake of scanning discoverable Bluetooth devices that are not necessarily beacons. (FYI @jws)
Also, it seems that there is either something fishy with this bar code reader or that Android just sucks balls with non-BLE devices because I have difficulties to make the phone connect to the reader. Most likely it's the combination of these two. Sigh…
Stupid user error. No wonder the app can't see the Bluetooth device because for some reason™ Android requires the app to have location permission too to be able to perform the discovery. And I haven't coded the app to ask for the permission at launch yet.
@33mhz It may sound drastic, but he has reasons. Very good reasons that nobody should have in my opinion.
@streakmachine Give me link, and I'll ask them "nicely" about their meaning of remote job.
Hmm. Patrick Rhone is taking a sabbatical from all online publishing. That means he won't be blogging (which has decreased quite much during the couple of years) nor will he be chatting on social media.