Hi Deva,

There is no rfkill0 subdirectory created for me in "sys/class/rfkill"
path.
If rfkill0 is created under the path then I think I can give access on
rfkill0-> state to
bluetooth.


On Feb 24, 1:29 am, Deva R <[email protected]> wrote:
> Hi,
> you need to  modify init.rc like below, to give access on rfkill0->state to
> bluetooth.
>
>    #bluetooth power up/down interface
>    chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
>    chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
>    chmod 0660                /sys/class/rfkill/rfkill0/state
>
> On Tue, Feb 23, 2010 at 2:53 PM, Paturi <[email protected]> wrote:
>
> > Hi,
>
> > Can anyone please help me out in solving the bluetooth issue on
> > beagleboard.
> > Bluetooth is not getting on from GUI. At kernel level it is working
> > good I can able to scan other bluetooth devices using hcitool.
> > From GUI it is unable to on bluetooth because it is unable to open
> > "sys/class/rfkill/rfkill0/state" path.
> > there is no rfkill0 directory in my system. Can anyone help me out to
> > sort this.
>
> > On Feb 22, 4:52 pm, Paturi <[email protected]> wrote:
> > > Hi,
>
> > > I have ported Android on BeagleBoard. But when I try to on the
> > > Bluetooth It is getting failed. In my logcat I can trace this reason
> > > since it is unable to open ("sys/class/rfkill/rfkill0/state").
> > > In my file explorer it created a structure "sys/class/rfkill" after
> > > enabling RFKILL flag in kernel config file.
> > > But rfkill directory doesnt contain any contents. In bluetooth.c it is
> > > returning error since it cant find this path. Please tell me how I can
> > > enable bluetooth? What is the use of this rfkill.
>
> > --
> > unsubscribe: 
> > [email protected]<android-porting%[email protected]>
> > website:http://groups.google.com/group/android-porting

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to