I think it is working from the console.
For example:
# hciconfig -a
hci0: Type: USB
BD Address: 00:07:80:93:84:47 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:978 acl:0 sco:0 events:29 errors:0
TX bytes:605 acl:0 sco:0 commands:29 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'beagleboard'
Class: 0x40020c
Service Classes: Telephony
Device Class: Phone, Smart phone
HCI Ver: 2.1 (0x4) HCI Rev: 0x13e2 LMP Ver: 2.1 (0x4) LMP Subver:
0x13e2
Manufacturer: Cambridge Silicon Radio (10)
And if I turn Bluetooth on in my phone and do an hcitool scan if finds
the phone
# hcitool scan
Scanning ...
00:23:AF:4D:xx:xx Motorola Phone
Still nothing in /sys/class/rfkill
Any suggestions on where to look?
Thanks much for your help.
Mike
On Fri, Oct 8, 2010 at 10:05 AM, Pavan Savoy <[email protected]> wrote:
> Well you have to write one.
>
>
> http://android.git.kernel.org/?p=kernel/omap.git;a=blob;f=drivers/misc/wl127x-rfkill.c;h=bc47ed43dc7cf8e66332d331266a756e8e711ebb;hb=refs/heads/android-omap-2.6.32
>
> can be your reference.
> With this sort of a driver you will get entries under /sys/class/rfkill/
> also did you first try it out from a console, just to make sure your usb-BT
> device works?
>
> because if that had worked you would have got atleast 1 entry under rfkill/
> directory from hci core BT sub-system in kernel.
>
> On Fri, Oct 8, 2010 at 10:12 AM, ms12 <[email protected]> wrote:
>
>> I found out how to get rfkill enabled in kernel, but there are no
>> directories under it, just /sys/class/rfkill. Symptoms still the
>> same, bluetooth blinks on and off immediately when trying to enable
>> it. This thread
>>
>>
>> http://groups.google.com/group/android-porting/browse_thread/thread/c37f87e81f63e7cc/32ef5a457e2eeef7?lnk=gst&q=problem+when+trying+to+on+bluetooth+under+beagleboard#32ef5a457e2eeef7
>>
>> suggests you need some drivers for the wl127x chip from TI, but this
>> is device is not a WL127x chip, it is an external eval board connected
>> via USB.
>>
>> Is there a way to get this to work?
>>
>> Thanks,
>> Mike
>>
>>
>> On Oct 7, 11:30 am, ms12 <[email protected]> wrote:
>> > Using Android 1.6 Donut
>> >
>> > I have the device (Bluegiga WT11, based on CSR Bluecore I believe)
>> > connected via usb hub to beagle board. I don't have a tty that I can
>> > spare. I have started hcid, hciconfig shows hci0 up, and I can
>> > communicate with the device to read feature, etc. So I believe it is
>> > basically working at the console level.
>> >
>> > But if I try to enable Bluetooth via the Android settings on the
>> > touchscreen, it briefly blinks on then off. The logcat shows
>> >
>> > D/BluetoothDeviceService( 907): Bluetooth state 0 -> 1
>> > D/BluetoothDeviceService( 907): Bluetooth state 1 -> 0
>> >
>> > which seems to mean it tries to turn on but goes right back off.
>> >
>> > Is there a way to get this to work, or will it only work thru a tty
>> > that is hciattach'd ?
>> >
>> > Mike
>>
>> --
>> unsubscribe:
>> [email protected]<android-porting%[email protected]>
>> website: http://groups.google.com/group/android-porting
>>
>
>
>
> --
> --Pavan Savoy
>
>
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
