Hi all,
I'm able to start bluetooth after porting only from command line.
I give following commands and it works
#hciattach -s 115200 /dev/s3c_serial1 any 460800 flow NULL
#hciattach -s 115200 /dev/s3c_serial1 bcm2035 460800 flow NULL
Doing this brings bluetooth up for me.
But I want to put
On Wed, Aug 4, 2010 at 12:19 PM, Pavan Savoy pavan.sa...@gmail.com wrote:
#service hciattachd /system/bin/hciattach -s 115200 /dev/s3c_serial1
any 460800 flow NULL
#user root
#group bluetooth net_bt_admin
#disabled
#oneshot
is almost correct except for the
Hi Pavan,
But doing only hciattach with device type as 'any' doesn't work.( I tried
that now , inside init.rc)
Do i need to put second hciattach with dev type as 'bcm2035' in init.rc???
Also in command line only after exceution of both commands , i get buletooth
running.
I stumbled across this
there should really be on 1 hciattach, i.e it needs to be run once..
I guess with mentioning bcm, the hciattach would have a custom
_init and _post function which does BCM specific initialization, like
setting baud-rate via HCI-VS and fw download...
but via cmd line.. you should probably be
Hiattach has bcm specific initialisation.
Till now to run BT I didn't do start bluetoothd command.
Also after 2 hciattach's when i manaually give hciconfig hci0 up, it gives
me Connection timed out(110) error.
But inspite of this BT will be start when clicked , since i have given those
2
don't have the execs... remove them ..
and yes debug the hciattach !!
On Wed, Aug 4, 2010 at 3:01 PM, Ajith Kamath sjce.aj...@gmail.com wrote:
Thats the thing.
I m not able to find out why 2 times of hciattach is required.
Also start hciattach and start bluetoothd didn't do anything.
can't i
In my last trial run i did start hciattach from after dbus daemon was
started :
I got following in log:
01-01 00:04:40.251: WARN/libdbus(2482): Failed to start message bus: Could
not obtain fd for android socket dbus
I had read your previous conversation with siddharth and Nick, with nick
I got it from this reference mail:
http://www.mail-archive.com/android-porting@googlegroups.com/msg01917.html
How should i proceed since previous conversation was pertaining to hcid.?
Thanks,
Ajith
On Wed, Aug 4, 2010 at 3:33 PM, Ajith Kamath sjce.aj...@gmail.com wrote:
In my last trial run
all the more reason to do start bluetoothd instead of doing a
bluetoothd -d from cmd line...
but i suppose yours is a problem with the chip init using hciattach
..(or i guess so..)
On Wed, Aug 4, 2010 at 3:40 PM, Ajith Kamath sjce.aj...@gmail.com wrote:
I got it from this reference mail:
