General Discussion

• S

  Pairing rejected by: ...
  • SparkyRih

  7
  0
  Votes
  7
  Posts
  84
  Views

  R

  Yeah, I wouldn't be surprised to learn that battery level affects it, especially on newer API levels. the low/high energy settings you refer to only affect scanning. Is the problem that they can't connect, or that they can't find the device to connect to?
• M

  Prevent reconnect regardless of disconnect reason
  • mkurtz

  15
  0
  Votes
  15
  Posts
  344
  Views

  M

  @ryanbis Ah, good to know. I will be sure to test this thoroughly. Thanks for the tip!
• A

  BleTransaction.Auth() documentation
  • Activ84HealthEU

  2
  0
  Votes
  2
  Posts
  31
  Views

  R

  @Activ84HealthEU, I need a bit more info in order to help you. Does it actually ble connect to the device? (You may have to look at logcat). When the write fails in the transaction, what is the status()? That should at least give you a hint at what's going on. NOTE: When using any transaction, you MUST call either succeed(), or fail(). Otherwise, even if the write went through, it would just stall out and do nothing afterward (and the DeviceConnectListener onEvent will never get called, at least not for being connected).
• S

  Radio strength?
  • SparkyRih

  5
  0
  Votes
  5
  Posts
  128
  Views

  S

  `Well, the Sweetblue library does already make a big improvement on connection time, and the amount of phones even being able to connect... I'm mostly worried about the phones that sometimes don't connect at all, but so far, I've only seen that on a Sony in my small test team... Too bad the guy doesn't want to test again to see if my latest fixes work for that issue :S
• S

  NullPointerxceptoin in library?
  • SparkyRih

  2
  0
  Votes
  2
  Posts
  81
  Views

  R

  Unfortunately those line numbers are WAY off. If you're using proguard, please add these lines to your proguard file: -keep class com.idevicesinc.sweetblue.** { *; } -keepattributes SourceFile,LineNumberTable,Signature,*Annotation*,EnclosingMethod -dontwarn com.idevicesinc.sweetblue.**
• 

  Unbond behavior on App termination
  • AlejandroHCruz

  4
  0
  Votes
  4
  Posts
  118
  Views

  R

  That shouldn't matter (where you set the config). However, if you want it to apply to all devices, I would just set the options in the BleManagerConfig when instantiating the BleManager instance. (BleManagerConfig extends BleDeviceConfig mainly for this purpose). Try doing this, and see if you get any different results.
• G

  timeout__LONG_TERM value can't be changed
  • gunnark

  6
  0
  Votes
  6
  Posts
  183
  Views

  G

  @ryanbis Awesome! We look forward to the release. Cheers, Gunnar
• W

  NPE within ReadWriteListener$ReadWriteEvent.isNull
  • wouterh

  6
  1
  Votes
  6
  Posts
  237
  Views

  W

  Glad to hear! Looking forward to the next release.
• 

  Interacting with device that's already connected to the OS
  • AlejandroHCruz

  7
  0
  Votes
  7
  Posts
  191
  Views

  

  Got it, thanks! Will look to alternative solutions like keeping a service in the background. Our goal is to provide push notification capabilities to the custom BLE device.
• W

  Device state incorrect after RECONNECTING_LONG_TERM using DefaultDeviceReconnectFilter
  device state reconnectfilter reconnecting bug • • wouterh

  10
  0
  Votes
  10
  Posts
  282
  Views

  R

  Excellent, please let me know if you still see the problem.
• N

  UhOhListener triggered too soon
  • Niels

  2
  0
  Votes
  2
  Posts
  182
  Views

  

  Great suggestion, thanks!
• B

  DeviceStateLister pop after Bluetooth turn off
  statelistener turn off turn on pop listener • • Bjoern_ilockit

  5
  0
  Votes
  5
  Posts
  189
  Views

  N

  I'm having the same problems on v3.0.2, where as I connect, turn Bluetooth off and on again, it'll automatically reconnect (at least that's what the sensor says),but a NATIVE_CONNECTION_FAILED is given.
• 

  Explicit disconnect triggers automatic reconnect?
  • AlejandroHCruz

  8
  0
  Votes
  8
  Posts
  270
  Views

  

  Removing all the calls to unbond() from our side does not mitigate the automatic reconnection.
• E

  Are there any sample projects that besides the SweetBlue v2 toolbox found on github?
  • Eheartlyanderson

  2
  1
  Votes
  2
  Posts
  118
  Views

  

  The sample projects should be published here: https://forum.sweetblue.io/category/6/sample-apps Hope they upload some soon.
• 

  Disable automatic bonding upon connection
  • AlejandroHCruz

  7
  0
  Votes
  7
  Posts
  256
  Views

  

  Gotcha, sounds great!
• 

  Link the source code of v3 to Android Studio
  • AlejandroHCruz

  1
  0
  Votes
  1
  Posts
  112
  Views

  No one has replied

• B

  Notify on characteristic only trigger one time
  blenotify characteristic enablenotify • • Bjoern_ilockit

  3
  0
  Votes
  3
  Posts
  146
  Views

  R

  I've updated the logic for enabling/disabling notifications. Now if you pass in a notification listener in a BleNotify instance, it will set that listener as the default only if there are no other NotificationListeners set for the device. This will be in the next version.
• B

  New reconnect filter don't work well
  • Bjoern_ilockit

  5
  0
  Votes
  5
  Posts
  229
  Views

  R

  Bjoern, How are you setting your reconnect filter?
• S

  Toolbox App V3: Device connection only works during scan
  • sebroth

  5
  0
  Votes
  5
  Posts
  235
  Views

  R

  Try setting the delay between tasks option in the settings menu to something like .5 seconds (the value is in seconds). See if it improves the connection rate at all. I've heard sometimes delaying after service discovery can sometimes help with 133 gatt errors when connecting. This test should at least give us some proof that this is true or not.
• I

  Subscribing to Notifications/Indications
  blenotify uuid descriptor • • isansys

  19
  0
  Votes
  19
  Posts
  674
  Views

  I

  Excellent news, thank you!