From: Szymon Janc <szymon.janc@tieto.com>
To: Keith Conger <keith.conger@gmail.com>
Cc: Szymon Janc <szymon.janc@gmail.com>,
BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: android-bluez with usb adapter
Date: Wed, 18 Feb 2015 20:57:20 +0100 [thread overview]
Message-ID: <2179587.DtNQVsuMNH@leonov> (raw)
In-Reply-To: <11216650.UM2e8dqFFR@leonov>
On Wednesday 18 of February 2015 20:52:06 Szymon Janc wrote:
> Hi Keith,
>
> On Wednesday 18 of February 2015 11:41:01 Keith Conger wrote:
> > Ok, things are looking somewhat better.
> >
> > It doesn't seem to work in the UI. But haltest looks good I think.
> >
> > Here is a logcat from boot to me enable Bluetooth and looking for devices:
> >
> > ########## Start Logcat ##########
> >
> > adb logcat|grep -i blue
> >
> > - waiting for device -
> >
> > W/PackageParser( 595): No actions in intent filter at
> > /system/app/Bluetooth.apk Binary XML file line #211
> >
> > W/PackageManager( 595): Unknown permission
> > com.google.android.gallery3d.permission.GALLERY_PROVIDER in package
> > com.android.bluetooth
> >
> > W/PackageManager( 595): Unknown permission
> > android.permission.MMS_SEND_OUTBOX_MSG in package
> > com.android.bluetooth
> >
> > I/SystemServer( 595): No Bluetooh Service (emulator)
> >
> > W/PackageManager( 595): Unknown permission
> > com.google.android.gallery3d.permission.GALLERY_PROVIDER in package
> > com.android.bluetooth
> >
> > W/PackageManager( 595): Unknown permission
> > android.permission.MMS_SEND_OUTBOX_MSG in package
> > com.android.bluetooth
> >
> > E/BluetoothAdapter( 727): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 727): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 654): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 654): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 727): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 654): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 654): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 654): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 717): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 717): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 595): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 595): Bluetooth binder is null
> >
> > E/BluetoothAdapter( 717): Bluetooth binder is null
> >
> > D/SubSettings( 717): Launching fragment
> > com.android.settings.bluetooth.BluetoothSettings
> >
> > E/BluetoothAdapter( 717): Bluetooth binder is null
> >
> > E/DeviceListPreferenceFragment( 717): Bluetooth is not supported on this
> > device
> >
> > ########## END Logcat ##########
> >
> >
> >
> >
> >
> > With haltest, it appears to work fine:
> >
> >
> > ########## Start haltest session ##########
> > root@beagleboneblack:/ # haltest
> >
> > hw_get_module_by_class returned -2
> >
> > hw_get_module_by_class returned -2
> >
> > thread_evt_cb: evt=ASSOCIATE_JVM
> >
> > if_bluetooth->init: BT_STATUS_SUCCESS
> >
> > get_profile_interface(handsfree) : 0xb6e2a134
> >
> > get_profile_interface(a2dp) : 0xb6e2a0ec
> >
> > get_profile_interface(avrcp) : 0xb6e2a100
> >
> > get_profile_interface(health) : 0xb6e2a3d0
> >
> > get_profile_interface(hidhost) : 0xb6e2a0a0
> >
> > get_profile_interface(pan) : 0xb6e2a0d0
> >
> > get_profile_interface(gatt) : 0xb6e2a1ac
> >
> > get_profile_interface(socket) : 0xb6e2a094
> >
> > if_av->init: BT_STATUS_SUCCESS
> >
> > if_rc->init: BT_STATUS_SUCCESS
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=1
> >
> > prop: type=BT_PROPERTY_UUIDS len=80 val={0000110e, 0000110c, 0000110a,
> > 0000113b, 00001200}
> >
> > if_gatt->init: BT_STATUS_FAIL
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=1
> >
> > prop: type=BT_PROPERTY_UUIDS len=80 val={0000110e, 0000110c, 0000110a,
> > 0000113b, 00001200}
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=1
> >
> > prop: type=BT_PROPERTY_UUIDS len=80 val={0000110e, 0000110c, 0000110a,
> > 0000113b, 00001200}
> >
> > if_hf->init: BT_STATUS_SUCCESS
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=1
> >
> > prop: type=BT_PROPERTY_UUIDS len=96 val={00001112, 0000110e, 0000110c,
> > 0000110a, 0000113b, 00001200}
> >
> > if_hh->init: BT_STATUS_SUCCESS
> >
> > if_pan->init: BT_STATUS_SUCCESS
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=1
> >
> > prop: type=BT_PROPERTY_UUIDS len=128 val={00001115, 00001116,
> > 00001112, 0000110e, 0000110c, 0000110a, 0000113b, 00001200}
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=1
> >
> > prop: type=BT_PROPERTY_UUIDS len=128 val={00001115, 00001116,
> > 00001112, 0000110e, 0000110c, 0000110a, 0000113b, 00001200}
> >
> > if_hl->init: BT_STATUS_SUCCESS
> >
> > > bluetooth init
> >
> > if_bluetooth->init: BT_STATUS_DONE
> >
> > > bluetooth enable
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=9
> >
> > prop: type=BT_PROPERTY_BDADDR len=6 val=00:18:e7:36:36:e9
> >
> > prop: type=BT_PROPERTY_BDNAME len=16 val=BeagleBone Black
> >
> > prop: type=BT_PROPERTY_CLASS_OF_DEVICE len=4 val=000000
> >
> > prop: type=BT_PROPERTY_TYPE_OF_DEVICE len=4 val=BT_DEVICE_DEVTYPE_BREDR
> >
> > prop: type=BT_PROPERTY_ADAPTER_SCAN_MODE len=4 val=BT_SCAN_MODE_NONE
> >
> > prop: type=BT_PROPERTY_ADAPTER_DISCOVERY_TIMEOUT len=4 val=120
> >
> > prop: type=BT_PROPERTY_ADAPTER_BONDED_DEVICES len=0 val={}
> >
> > prop: type=BT_PROPERTY_UUIDS len=128 val={00001115, 00001116,
> > 00001112, 0000110e, 0000110c, 0000110a, 0000113b, 00001200}
> >
> > prop: type=(unknown) len=8 val=0xb6e1da5d
> >
> > if_bluetooth->enable: BT_STATUS_SUCCESS
> >
> > adapter_properties_cb: status=BT_STATUS_SUCCESS num_properties=1
> >
> > prop: type=BT_PROPERTY_CLASS_OF_DEVICE len=4 val=0a020c
> >
> > adapter_state_changed_cb: state=BT_STATE_ON
> >
> > > bluetooth start_discovery
> >
> > if_bluetooth->start_discovery: BT_STATUS_SUCCESS
> >
> > discovery_state_changed_cb: state=BT_DISCOVERY_STARTED
> >
> > device_found_cb: num_properties=5
> >
> > prop: type=BT_PROPERTY_BDADDR len=6 val=ec:88:92:c3:1e:48
> >
> > prop: type=BT_PROPERTY_TYPE_OF_DEVICE len=4 val=BT_DEVICE_DEVTYPE_BREDR
> >
> > prop: type=BT_PROPERTY_CLASS_OF_DEVICE len=4 val=5a020c
> >
> > prop: type=BT_PROPERTY_REMOTE_RSSI len=4 val=216
> >
> > prop: type=BT_PROPERTY_BDNAME len=17 val=EC:88:92:C3:1E:48
> >
> > remote_device_properties_cb: status=BT_STATUS_SUCCESS
> > bd_addr=ec:88:92:c3:1e:48 num_properties=1
> >
> > prop: type=BT_PROPERTY_BDNAME len=7 val=Nexus 6
> >
> > discovery_state_changed_cb: state=BT_DISCOVERY_STOPPED
> >
> > ########## End haltest session ##########
>
> This looks OK. You just need to reboot your board and UI should also be
> working.
>
> This is due to Android doing test BT start while booting and if that failed
> it won't try to load BT HAL again.
>
> Also note that you cannot run BT from UI and haltest at the same.
I thing that might be affecting this test BT enable is that kernel modules are
loaded too late in boot process.
I recommend loading them in "on boot" target. See our reference tree:
https://code.google.com/p/aosp-bluez/source/browse/init.mako.rc?repo=device-lge-mako#62
--
BR
Szymon Janc
next prev parent reply other threads:[~2015-02-18 19:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 21:16 android-bluez with usb adapter Keith Conger
2015-02-17 21:47 ` Szymon Janc
[not found] ` <CALUN+EcJ4p4kkFDZDyi01iSAwDMv4M1Q=axAPiCb+YOAQ64CNQ@mail.gmail.com>
2015-02-18 7:34 ` Szymon Janc
2015-02-18 16:01 ` Keith Conger
2015-02-18 18:41 ` Keith Conger
2015-02-18 19:52 ` Szymon Janc
2015-02-18 19:57 ` Szymon Janc [this message]
[not found] ` <CALUN+EcsmogUt4PU-sSM4peusX4gdnmAF=ou1ouj5y-QPSpq3Q@mail.gmail.com>
2015-02-18 20:37 ` Szymon Janc
[not found] ` <CALUN+EfrG1o8VsTWjMxW7Y4NGe=-E3M_hz_618ToAG4QHwPZKA@mail.gmail.com>
2015-02-19 15:39 ` Keith Conger
2015-02-19 16:02 ` Andrei Emeltchenko
2015-02-19 16:06 ` Keith Conger
2015-02-19 16:08 ` Szymon Janc
2015-02-19 16:31 ` Keith Conger
2015-02-19 17:25 ` Keith Conger
2015-02-19 18:49 ` Keith Conger
2015-02-20 10:05 ` Szymon Janc
2015-02-20 14:59 ` Keith Conger
2015-02-20 16:30 ` Szymon Janc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2179587.DtNQVsuMNH@leonov \
--to=szymon.janc@tieto.com \
--cc=keith.conger@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox