Im trying to connect my NOKIA 1200 headphones (has bluetooth 5.0) on my OnePlus 9 (android 13) via a simple app that i built (using this tutorial) and no matter what i do i cant find the headphones in the listBLE (I see a lot of other devices).
I gave the app the permission to see nearby devices and the GPS location via the settings.
those are my blocks:
i also tried to use the bluetooth client (with this tutorial) and there in the listBLE i see only a list of old devices that my phone was connected to them in the past and it seems that the scan is not working.
Can you add these headphones using settings in your phone?
If yes, can you see them in your app after you connected them in your settings?
Did you find some API documentation about your headphones? Maybe they have special requirements and maybe these headphones do not like being connected to by just anyone except their own apps or interfaces.
Yes, I can add them using the normal way through the settings.
I can see them on the list only in the Bluetooth client app, but when I try to connect to them, it says "Error 507" that the device may be turned off.
I will explain my purpose: I use these headphones regularly by connecting them to my phone via Bluetooth in the normal way, and it works fine. Now, I have a mission to build an app using App Inventor and connect to a device through it with bluetooth. I'm trying it on different kinds of devices, and the issue has been the same with all of them.
Or use some Arduino device, there are enough examples here on the forum. Or use a micro:bit, see the iot section on the appinventor site if you want to use BLE. It is not so difficult to drive a little robot for example with it, or automatically water your plants.
I tried to connect my phone to my laptop, and the problem persists. I searched forums and attempted every example I found, but the issue persists there as well.
My project involves connecting to a Bluetooth speaker using App Inventor.
My project involves connecting to a Bluetooth speaker using App Inventor.
I tried to connect my phone to my laptop, and the problem persists. I searched forums and attempted every example I found, but the issue persists there as well.
Do you see other BT devices in your scan? If yes, you should look better at the device you want to connect to, maybe it does not want to be connected to by 3rd party apps. Does it have any technical documentation you can look at?
Another possibility is that you are not using the latest BLE extension and that your app does not have the required permissions. So, what is the version of it?
Edit:
With bluetooth scanner app from google play I can see that the bluetooth protocal of the devide is BR/EDR.
It means that I can only connect it with the bluetooth client option in the app inventor?
Another question ,it has bluetooth 5.0 shouldnt it use BLE?
That is not exactly what I meant. My question is, whether the device has any API (application programming interface) information.
BT 5.0 should indeed be BLE. And, normally, you do not want to be a BL server.
Did you also try the BTClient for BT < 5?
What did the BT scanner app tell you? Could you connect to your headset with it?
I don't believe the device has an API; it's a standard headset.
I also tried to use the bluetooth client (with this tutorial ) and there in the listPicker i see only a list of old devices that my phone was connected to them in the past and it seems that the scan is not working.
To clarify, the problem is that I can't detect any new devices. I have to initially connect them through the phone settings, unpair, and only then do they show up in the scan list of the MIT app. Even then, when I attempt to connect to the headset, it returns an 'error 507: unable to connect.'
Im able to connect the headset with the BTScanner from the google play
Any guidance or suggestions would be greatly appreciated.
People have arms and legs, devices have API’s. What I meant is that maybe the way to access most headsets is similar, and I do not know a thing about headsets.
Anyway, I will stop replying in this thread, too much confusion.
