The best way for storing BTLE information.

Here is a topic with the question I'd like to know as well.

https://forums.garmin.com/developer/connect-iq/f/discussion/232765/best-practice-for-storing-btle-information-for-reconnecting-on-app-restart

Are there any changes since that time? As I've understood there is no way to get device's MAC while scanning (but somehow there is a call named ScanResult.hasAddress(); why?).

All another device data/manufacturer data is not unique unfortunately.

Any suggestions?

Thanks

Top Replies

All Replies

jim_m_58 over 5 years ago

This is only available on 3.2 devices:

Run the app with only the device you want to use in range.

Scan, and look for the UUID you are need, Connect to that device and when connected, save the scan result you used in Application Storage. You can also check the RSSI and look for one with a strong signal.

After that when you start up, look for a scan result in Application Storage, and if it exists, skip scanning and go right to pairing.

I do thing in a few things now and it noticeably speeds up the connection.

Aleks over 5 years ago in reply to jim_m_58

Hm. Do you mean this code should work?

Application.getApp().setProperty("LastSuccess", self._scanResult);

I tried but I got.

UnexpectedTypeException: Expected null/Number/Float/String/Array/Boolean/Dictionary/Long/Double/Char/ByteArray, given Object

Or you meant some different way?

In manifest i have

minSdkVersion="3.2.0"

And run with Target SDK 3.2.x

jim_m_58 over 5 years ago in reply to Aleks

Use Application.Storage.setValue() instead of the old object store - Application.getApp().setProperty()

Aleks over 5 years ago in reply to jim_m_58

Yes. This works! :)

Thank you again and again!

jim_m_58 over 5 years ago in reply to Aleks

You want to be consistent in an app. If you use Application.Storage/Application.Properties don't use Application.getApp().getProperty/setProperty