Android BT/BLE with Petrel 2
Rick Walsh
rickmwalsh at gmail.com
Tue Jul 4 13:51:12 PDT 2017
On 5 Jul. 2017 4:09 am, "Linus Torvalds" <torvalds at linux-foundation.org>
wrote:
On Tue, Jul 4, 2017 at 6:31 AM, Dirk Hohndel <dirk at hohndel.org> wrote:
>> 07-04 19:19:20.268 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: Creating Android Central/Client
support for BTLE
>> 07-04 19:19:20.272 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: qt_ble_open( 00:13:43:0E:6B:D0 )
>> 07-04 19:19:20.394 5484 32204 D BtGatt.GattService: clientConnect(org.subsurfacedivelog.mobile)
- address = 00:13:43:0E:6B:D0, isDirect=true transport =2 set own addr =
false own addr type:0, clientIf: 4
>> 07-04 19:19:20.877 2423 2423 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO:
"LocalDeviceBroadcastReceiver::onReceive()
- event: android.bluetooth.device.action.ACL_CONNECTED"
>> 07-04 19:19:20.898 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: Connection updated: error:
QLowEnergyController::Error(NoError) oldState: QLowEnergyController::
ControllerState(ConnectingState) newState: QLowEnergyController::
ControllerState(ConnectedState)
>> 07-04 19:19:21.000 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: connected to the controller for
device 00:13:43:0E:6B:D0
>> 07-04 19:19:21.001 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: .. discovering services
>> 07-04 19:19:21.006 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: Service discovery initiated
>> 07-04 19:19:33.409 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: .. done discovering services
>> 07-04 19:19:33.409 2423 2520 D /data/newandroid/subsurface/
qt-models/messagehandlermodel.cpp: INFO: failed to find suitable service on
00:13:43:0E:6B:D0
>> 07-04 19:19:33.420 5484 27635 D BtGatt.GattService:
clientDisconnect(org.subsurfacedivelog.mobile) - address=00:13:43:0E:6B:D0,
connId=4, clientIf: 4
>> 07-04 19:19:33.439 5484 27630 D BtGatt.GattService:
clientDisconnect(org.subsurfacedivelog.mobile) - address=00:13:43:0E:6B:D0,
connId=null, clientIf: 4
>
> That's odd. Not sure if Linus will have a moment to look at this.
It doesn't seem to be discovering any services at all, much less one
that is write/notify. So it gives up.
I have no idea why. Testing with the Nordic nRF app would be good, and
maybe making sure it's bonded there and shows all services..
I downloaded the Nordic nRF Connect app. It shows the Petrel (2) as bonded
and I can connect with it. But the DC screen still continues with its
countdown.
3 client primary service's are shown:
Generic access 0x1800
Device incformation 0x180a
Unknown service fe25c237-0ece-443c-b0aa-e02033e7209d
Interestingly, the device list shows the Petrel as type: ble only. That is
consistent with the subsurface-mobile logcat output. But i have definitely
used it as traditional Bluetooth.
Cheers?
Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20170705/6be688f2/attachment-0001.html>
More information about the subsurface
mailing list