Hi, weird issue. I am using the nRF toolbox to connect the nRF52832 (configured for HRM) for use on android. The thing is, on my personal phone ( Samsung galaxy s10+) everything is working as expected and fine. I have a dev phone (no SIM card atttached), a samsung Galaxy A10, that i try to run the same thing on, no changes. It cannot find the Ble device. I used nRF connect to try and find it but no luck, it can see a lot of other devices though. The A10 dev phone has been completely updated to most recent software, and is connected to wifi. It can even grab a gps location, I have tested it. What should I do?
Just so the cart is behind the horse so to speak.
Does the app have BT access authorization?And have you disconnected the other phone from the nrf device?
Yes. I went into settings and gave the app full permissions manually. I'm pretty sure You don't need to request permission to access Bluetooth as it is a normal permission. Nonetheless, I have accepted any request given on said device. And yes i have disconnected the other phone from the nrf device.
Are you working on an nRF52 Development Kit, or is this a custom board? Are you sure the nRF52832 is advertising at all? Did you program the chip with the ble_app_hrs example?
hi simon, yes this is a sparkfun nrf52832 breakout board. The board is advertising, it can be seen on the bluetooth menu of another phone, i can check with a 3rd phone if need be but I'm fairly certain that is not the problem. The chip is programmed with the ble_app_hrs example. The galaxy A10 can see other devices with the nRF connect and can see my personal phone and some other bluetooth devices, just not the board. This is where i'm stumped. I restarted the phone, updated the software, turned bluetooth on and off, enabled bluetooth HCI snoop log, enabled show ble devices without names, all without luck. Not sure where to go next. I'll see if I can find it on a 3rd phone
Thanks for clarifying your predicament! Can you please go through these "fixes" for the Samsung Galaxy Bluetooth issues? Even though it says S10, the procedure should be rather similar on the A10 as well. In the meantime, I'll ask internally if anyone has had similar experiences using the Galaxy A10.