General Discussion

• M

  Scans with screen turned off on Android 8.1 and above fail
  • mkurtz

  20
  0
  Votes
  20
  Posts
  738
  Views

  R

  We're looking at around 2 weeks or so before we put out the official release.
• M

  Timeout
  • mgordon

  8
  0
  Votes
  8
  Posts
  177
  Views

  M

  Yes, those trigger. We added those when we noticed that the times we set in taskTimeoutRequestFilter or DefaultTaskTimeoutRequestFilter weren't triggering.
• 

  Android Q Support
  • AlejandroHCruz

  4
  0
  Votes
  4
  Posts
  147
  Views

  

  1 & 2. That's great! Looking forward to future updates on this topic
• L

  Using SweetBlue in library
  • ldulcic

  2
  0
  Votes
  2
  Posts
  76
  Views

  R

  You can put it in a library if you want, you would just have to get a license for each app that it goes into. If you're looking to have many apps using SweetBlue, an Enterprise license may be more what you're looking for. If that's the case, email us at sweetblue@idevicesinc.com, and we can discuss your situation.
• A

  SweetBlue 3.0.3 - Proguard Issue with TemperatureUnit?
  • allen

  1
  0
  Votes
  1
  Posts
  99
  Views

  No one has replied

• S

  Pairing rejected by: ...
  • SparkyRih

  8
  0
  Votes
  8
  Posts
  352
  Views

  S

  Well, it's mostly the connecting itself which is the issue... The scanning/finding is pretty consistent now...
• M

  Prevent reconnect regardless of disconnect reason
  • mkurtz

  15
  0
  Votes
  15
  Posts
  642
  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
  122
  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
  307
  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
  176
  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
  255
  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
  341
  Views

  G

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

  NPE within ReadWriteListener$ReadWriteEvent.isNull
  • wouterh

  6
  1
  Votes
  6
  Posts
  434
  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
  360
  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
  498
  Views

  R

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

  UhOhListener triggered too soon
  • Niels

  2
  0
  Votes
  2
  Posts
  333
  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
  333
  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
  446
  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
  197
  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
  396
  Views

  

  Gotcha, sounds great!