> On Jul 4, 2017, at 6:44 AM, Jan Mulder <jlmul...@xs4all.nl> wrote: > > On 04-07-17 15:31, Dirk Hohndel wrote: >>> On Jul 4, 2017, at 12:29 AM, Rick Walsh <rickmwa...@gmail.com> wrote: >>> >>> Hi, >>> >>> I tried to download dives from my Shearwater Petrel 2 to my phone (Samsung >>> Galaxy S7) with the latest daily Android build, 4.6.4.333-arm. With >>> previous builds, download was working correctly with standard Bluetooth. >>> Now Subsurface-mobile is now trying to connect using BLE, but failing to >>> connect. The dive computer screen continues with the waiting for PC >>> countdown the entire time. >>> >>> I tried first by selecting Vendor: Paired Bluetooth, DC: Petrel >>> (LE:00:13....) >>> > > > More in general, I have seen weird things related to BT/BLE switching. For > example, my OSTC3 paired as a type 1 (classic), type 2 (ble only), and type 3 > (bt and ble). This all just on OS (Android) level. Re-pairing solved it most > of the time (as it is definitely a type 3). > > @Rick, in the app log, there is in de beginning some debug data printed about > found paired devices. If that reports a wrong type, things will get confusing.
Unfortunately my one dual mode device seems to be broken, so this has become harder to test. But yes, Android seems to do odd things when it comes to pairing / bonding to BT/BLE devices. I tend to use the Nordic nRF Connect app to get a better sense as to whether things are the way they should be before starting Subsurface-mobile /D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
