Does anyone make bluetooth work on ICS?
I really don't know how to do that,and I need some info about that.
Thank you.
on ICS yes.
But i guess your question in on panda ICS?
I suppose this link can help ?
http://omappedia.org/wiki/Device_Driver_Interface_of_WiLink_Solution
You can also choose to go by the hciattach way ...
>
>
--
--Pavan Savoy
I haven't checked whether the google build for panda (ics branch) -
actually has BT working..
This would be something you can try.
As far as info goes, WiLink is the BT chip on Panda - connected to
UART2, so if you have enabled HCI_UART in your kernel.
You should be able to get BT working with right entries in init.rc for
hciattach.
> How about you?
>
>
--
--Pavan Savoy
As omappedia.org would suggest there are 2 ways the BT on the wilink
devices can be made use of,
1. hciattach + HCI_UART way
2. UIM and BTWILINK way (which requires ti-st to be enabled).
For just BT, you can use the hciattach and HCI_UART.
regards,
Pavan
--
--Pavan Savoy
[ 13.076904] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
[ 13.094940] (stc): st_register(2)
[ 13.104095] (stc): chnl_id list empty :2
[ 13.108825] (stk) : st_kim_start
[ 13.228393] (stk) :ldisc_install = 1shell@android:/ $
[ 14.236755] (stk) :line disc installation timed out
[ 14.249176] (stk) :ldisc_install = 0
[ 14.447174] (stk) :ldisc_install = 1
[ 15.456298] (stk) :line disc installation timed out
[ 15.461853] (stk) :ldisc_install = 0
[ 15.644622] (stk) :ldisc_install = 1
[ 16.655181] (stk) :line disc installation timed out
[ 16.665985] (stk) :ldisc_install = 0
[ 16.841644] (stk) :ldisc_install = 1
[ 17.847808] (stk) :line disc installation timed out
[ 17.853302] (stk) :ldisc_install = 0
[ 17.959594] (stk) :ldisc_install = 1
[ 18.964233] (stk) :line disc installation timed out
[ 18.969635] (stk) :ldisc_install = 0
[ 19.077209] (stk) :ldisc_install = 1
[ 20.081451] (stk) :line disc installation timed out
[ 20.086517] (stk) :ldisc_install = 0
[ 20.098052] Bluetooth: st_register failed -22
What's wrong with it?
BTW, cannot see uim service by ps command.
Yep, there's the problem.
You will have to run UIM to get the hci0 up.
The latest is available at git.omapzoom.org project hardware/ti/wpan.git
The one's over there is for Android, shouldn't be too difficult to get
it working for ubuntu ...
>
>
>
--
--Pavan Savoy
Can you share logs of the error ?
##droid sent - ignore typos
[ 149.664184] (stc): st_register(2)
[ 149.668090] (stc): chnl_id list empty :2
[ 149.672576] (stk) : st_kim_start
[ 149.786956] (stk) :ldisc_install = 1
[ 150.784484] (stk) :line disc installation timed out
[ 150.790039] (stk) :ldisc_install = 0
[ 150.903228] (stk) :ldisc_install = 1
[ 151.909423] (stk) :line disc installation timed out
[ 151.915527] (stk) :ldisc_install = 0
[ 152.033020] (stk) :ldisc_install = 1
[ 153.034484] (stk) :line disc installation timed out
[ 153.034515] (stk) :ldisc_install = 0
[ 153.162384] (stk) :ldisc_install = 1
[ 154.159484] (stk) :line disc installation timed out
[ 154.165069] (stk) :ldisc_install = 0
[ 154.276580] (stk) :ldisc_install = 1
[ 155.285064] (stk) :line disc installation timed out
[ 155.290588] (stk) :ldisc_install = 0
[ 155.409393] (stk) :ldisc_install = 1
[ 156.409454] (stk) :line disc installation timed out
[ 156.415008] (stk) :ldisc_install = 0
[ 156.419067] Bluetooth: st_register failed -22
And after i open UIM_DEBUG, i found out the UIM always reporting:
E/uim-sysfs( 751): uim: Inside main
E/uim-sysfs( 751): uim: Inside insmod
E/uim-sysfs( 751): uim: Error inserting st_drv module
even i put st_drv.ko In the root "/" for Android.
The UIM should be there running and saying "polling....".
regards,
Pavan Savoy.
--
--Pavan Savoy
Well you can try and follow this procedure,
http://omappedia.org/wiki/Device_Driver_Interface_of_WiLink_Solution#On_Boot_Check
> The only way now to let ICS bluetooth work is to use USB BT dongle, enable
> BT_HCIBTUSB in kernel. And set
>
> chmod 0660 /sys/class/rfkill/rfkill0/state
> chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
>
> in init.omap4pandaboard.rc
Well this seems redundant, since a wilink chip is already provided on
the panda board....
--
--Pavan Savoy
hello richi
I'm trying to enable USB BT dongle as you mentioned.
but I still cannot see Bluetooth in the Settings.How do you check
bluetooth is working
How about android.hardware.bluetooth.xml in system/etc/permissions ?
##droid sent - ignore typos
Hi VH,
You could forgot copy "android.bluetooth.hardware.xml" into system.
best regards...
yeah, I guess you will have to create like on in here...
http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=android.hardware.bluetooth.xml;h=e058dbda78c0b1a1c195ba2de95513b5d91560fb;hb=refs/heads/ics-mr1
> -Vinayaka
>
> On Jan 18, 7:31 am, wang marco <marco681...@gmail.com> wrote:
>> Hi ,
>>
>> Yes,you need to copy this file into /system/etc/permissions
>>
>> best regards~~
--
--Pavan Savoy
Yes, I've observed that too.. like wifi - but for wifi the file exists.
But I have not found bluetooth in any of the google published
frameworks/base project ...
Better off to be in device/**/** project itself along with rest of
product definitions..
>
> -VH
>
> On Jan 18, 9:46 am, Pavan Savoy <pavan.sa...@gmail.com> wrote:
>> On Wed, Jan 18, 2012 at 10:12 AM, VH <hegdev...@gmail.com> wrote:
>> > Thanks to Wang marco and Pavan Savoy for the inputs.
>> > I am not able to locate android.bluetooth.hardware.xml file anywhere
>> > in the package Where can I find this file? Is this generated file?
>>
>> yeah, I guess you will have to create like on in here...http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=android.hardw...
>>
>> > -Vinayaka
>>
>> > On Jan 18, 7:31 am, wang marco <marco681...@gmail.com> wrote:
>> >> Hi ,
>>
>> >> Yes,you need to copy this file into /system/etc/permissions
>>
>> >> best regards~~
>>
>> --
>> --Pavan Savoy
--
--Pavan Savoy
>> After downloading the mentioned repo (except prebuilt I have downloaded all), I am getting the following error while building.
"build/core/java.mk:20: *** Pandaboard_ICS/dalvik/dexgen: Invalid
LOCAL_SDK_VERSION '4' Choices are: current . Stop."
Richi chen Is the build uses anything from prebuilt? or is the
prebuilt is must for building the code?
>> When I am trying other options I found some new issues. The type in rfkill0 is wlan and hence it is unable to find the blue tooth. How to change this? or where can I find the settings for this?
If I force the type to bluetooth, then HCI ioctl() is failing and
giving "bt_enable: ret: -1, errno: 19"
Has any one know this error?
Regards
--->
BTW, the new SGX libs of omapzoom ics_mr1 branch will cause some problems, i'm looking at.
Regards
1) check out master AOSP
2) add ti-wpan project from omapzoom (git://git.omapzoom.org/platform/hardware/ti/wpan.git) to hardware/ti/wpan
3) modify device/ti/panda/ as follows:
a) add TIInit_7.2.31.bts firmware from pandroid project in TI gforge (https://gforge.ti.com/gf/download/frsrelease/567/4721/Bluetooth_WLAN_KernelPatches_Firmware_Config_L27.12.1-P2-Pandroid-1.0-Linux-x86-Install) -- it's a linux installer, copy the firmware from the installed directory to ti/panda
b) add android.hardware.bluetooth.xml from omapzoom blaze_tablet (http://git.omapzoom.org/?p=device/ti/blaze_tablet.git;a=blob;f=android.hardware.bluetooth.xml;h=569f857e6b71418ffc8ab17b136f86a27cc6f003;hb=ics-mr1)
c) modify device.mk with:
PRODUCT_COPY_FILES := device/ti/panda/TIInit_7.2.31.bts:system/etc/firmware/TIInit_7.2.31.bts \
device/ti/panda/android.hardware.bluetooth.xml:system/etc/permissions/android.hardware.bluetooth.xml
PRODUCT_PACKAGES := $(call inherit-product-if-exists, hardware/ti/wpan/ti-wpan-products.mk)
d) modify BoardConfig.mk with:
BOARD_HAVE_BLUETOOTH := true
e) modify init.omap4pandaboard.rc with:
# change permissions for Bluetooth/FM/GPS
chmod 0600 /sys/class/rfkill/rfkill0/state
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
chmod 0600 /dev/ttyO1
chown bluetooth bluetooth /dev/ttyO1
#shared transport user space mgr service for Bluetooth, FM and GPS
service uim /system/bin/uim-sysfs
class core
user bluetooth
group bluetooth net_bt_admin
f - IMPORTANT) re-compile kernel from AOSP: https://android.googlesource.com/kernel/omap (branch remotes/origin/android-omap-panda-3.0) with the following:
1) make sure you copy the original defconfig from arch/arm/configs/panda_defconfig to .config in kernel root
2) make menuconfig with ARCH=arm
3) Networking Support->Bluetooth subsystem support->
a) turn on L2CAP, SCO, RFCOMM (with tty), BNEP, and HIDP
b) Bluetooth device drivers-> make sure you have HCI UART (H4 protocol) and Texas Instruments WiLink7 driver enabled
4) exit and save
5) re-compile, use the zImage (not the uImage) and replace the kernel in ti/panda/kernel with it.
4) Re-compile AOSP with new kernel, see if BT and wifi works :-D
Can you make sure you have uim-sysfs running when you see that error? May be on certain boot android AFS isn't starting services? Or restarting due to some error?
Droid sent - Ignore typos
Pavan
Am booting ICS chipsee linaro release on pandaboard
Bluetooth was working well . Now its not getting registered. which left me with
[ 9.839538] (stk) :ldisc_install = 1
[ 10.834381] (stk) :line disc installation timed out
[ 10.834381] (stk) :ldisc_install = 0
[ 11.987152] (stk) :ldisc_install = 1
[ 12.991363] (stk) :line disc installation timed out
[ 12.991363] (stk) :ldisc_install = 0
[ 14.122558] (stk) :ldisc_install = 1
[ 15.127258] (stk) :line disc installation timed out
[ 15.132537] (stk) :ldisc_install = 0
[ 16.280090] (stk) :ldisc_install = 1
[ 17.289733] (stk) :line disc installation timed out
[ 17.295104] (stk) :ldisc_install = 0
[ 18.400573] (stk) :ldisc_install = 1
[ 19.398590] (stk) :line disc installation timed out
[ 19.403991] (stk) :ldisc_install = 0
[ 20.481597] Bluetooth: st_register failed -22
When I reboot some time later it sometimes turns on .
Now its not turning on .
What possibly could be the bug?
Regards
prasanna
0x04 is the Bluetooth response event's first byte. The response should include baud rate change ack or firmware version.
Droid sent - Ignore typos
Also ti_st_uim-sysfs_uim.c says
UIM_VER(" read_hci_event");
if (size <= 0)
return -1;
/* The first byte identifies the packet type. For HCI event packets, it
* should be 0x04, so we read until we get to the 0x04. */
while (reading) {
rd = read(fd, buf, 1);
if (rd <= 0 && rd_retry_count++ < 4) {
nanosleep(&tm, NULL);
continue;
} else if (rd_retry_count >= 4) {
return -1;
}
if (buf[0] == RESP_PREFIX) {
break;
}
}
so what actually Does it read until 0x04 ? from where does this buffer written from ?