I'm currently working on an ionic capacitor app that needs to connect automatically with a ble device.
I'm using the ble ionic native plugin:
https://ionicframework.com/docs/native/ble
https://github.com/don/cordova-plugin-ble-central
The goal is sending and receiving bluetooth info and commands to the ble device, which is a car alarm central that controls a few actions like lock and unlock the doors accordingly to the RSSI values on from the device.
So, I'm using the autoconnect function to auto-connect with the device as soon the device is close to range and all works perfectly in Android and iOS. The only issue is that everytime the device reachs the ble range and the ble plugin try connecting, the system prompts the user to accept pairing with the device again.
I need it to work without that pairing prompting everytime. I tried to pairing the device previous to initialize the app but it didn't worked as well. So is it a way to make this autoconnection work without prompting the pairing acceptance everytime it is disconnected?
The issue occurs on Android versions 9 and 10 and iOS.
I've changed my ble hardware interface to ask for a PIN code. I guessed the connection could be considered secure by the OS and prevent prompting the user to pair again. Didn't work as well.
Every connection started by the plugin seems like bounding and connecting as if it was the first time connecting to the device. Even connecting to a known device is prompt the user to input the PIN, which if not provided the OS forgets the device.
Any toughts? Anyone? Thank you!
Related
I am trying to find a way to connect a Flutter app to a BLE beacon physical button whose purpose is to, when pressed, send an email through the app. So, I want the app to be permanently connected to the button and listen to its inputs, whether it's in foreground, background or terminated state. Even after a system reboot, I want it to always connect automatically and listen. What would be the best approach to do so, as I've seen that Android and iOS behave differently towards BLE devices as well as background processes.
I tried using packages like 'flutter_blue' or 'workmanager'. However, isolates created by workmanager can only run every at least 15 minutes on iOS. I am new to working with BLE devices as well as background processes in Flutter.
When I reinstall the app without disconnecting the BLE device, the phone keeps the connection so when I reinstall my app and scan for a BLE device, the last connection will appear in os level, but not in-app level. This causes me to not discover a BLE device if it is not disconnected on the app properly before. My tester insists that if I reinstall the app, I should not see a connection and discover the BLE device anyways.
I can retrieve a BLE device connection in the app if I know the UUID and services, but it is impossible without these as I see in the documentation. Is there any other way to resolve this problem?
This is precisely what retrieveConnectedPeripherals(withServices:) is for. That will return already connected (at the OS level) peripherals that advertise a particular list of services.
You will still need to call connect on the returned peripherals. "Connect" in this context means "to the app," not "to the device." The docs refer to these "app" connections as "local."
I am in process of making an app where, where when the first time app is launched the user enter the device they want to connect. Once connected, the user leaves/closes the app.
Now every time that same bluetooth device is connected or disconnected, I want a function to be called in the app. How can I achieve this?
I am using Corebluetooth currently to get names of devices etc. but cannot find a way to achieve this. Any suggestions? TIA!
I am trying to access the network with my Android Wear 2.0 App.
The Problem:
If the smartwatch is connected with the phone then I get an connection timeout. But if the smartwatch isn´t connected with the phone then the connection works fine.
I am using HttpUrlConnection.
Thanks and sorry for my bad english!
This has been answered in a different post:
Android Wear 100% packet loss
The basic idea is that you should not count on having Wi-Fi on the watch. The user may disable Wi-Fi on the watch and then your application will not work on the watch. Instead you should use your companion phone app to connect to the internet. If the phone isn't connected to your watch then use Wi-Fi.
Even if you want your app to run on an LET enabled watch the user may have turned this off or may not have a SIM card installed. At this point the user will most likely still expect your app to work.
So depending on what it is you're working on, if you want your app to work even while connected to the phone, then make a companion app for the phone. If you want your watch app to be a stand-alone app but you still want to be able to access the internet even when the watch is connected to the phone then you're basically saying that you want to drain the user's battery by using Wi-Fi/LTE instead of going via Bluetooth through the phone to access the web.
I want to write a tracking application, which reacts/record when users get in a car and phone automatically pair with Bluetooth hands free. I need also Id of the hands free device.
On Android it is easy, using Broadcast Receiver your app listen to broadcasts that device had been paired with phone. It is working even after phone had been restarted and App did not run after restart.
Is it possible on iOS(7+) ?
You can do it by reading the "Performing Long-Term Actions in the Background" part of this docs
Essentially, using state restoration, the system takes note of what your app was doing when it was killed.
If the app is searching for a bluetooth device and is killed by the system, the system will take care of continuing this research and wake up the app again when the bt device has ben found.
Note that this will work only if the app is killed by the system, not by the user (using the multitask bar). This behavior has changed since iOS 7.
Alternatively, If your BT hardware can be programmed to send advertisements using the ibeacon protocol, your app can be "awakened" by the corelocation/ibeacon api. After that prompt then maybe the corebluetooth pairing code could be initiated.