> Hi, why not try my repo. based on omapzoom ics-mr1 branch.
> 1. get & make
> repo init -u git://github.com/richi-chen/Pandaboard-ICS-repo.git -b > omapzoom
> repo sync
> . build/envsetup.sh
> lunch full_richi_panda-eng
> make
> 2. patch the kernel, build kernel & driver modules
> cp device/ti/richi-panda/panda-add-btwilink-support-for-ics.patch kernel/
> cd kernel/
> git apply panda-add-btwilink-support-for-ics.patch
> cd ..
> make kernel_build
> 3. rebuild boot/system image
> make
> Don't forget to manually format the SD card media partition to ext4, it > will mount the internal /sdcard to real physical media partition while > booting.
> It also support external USB storage.
if you use aosp's old u-boot loader(ex.
device/ti/richi-panda/bootloader.bin) to format partitions (by 'fastboot
oem format'), there will be a media partion created. You must manually
format it to ext4. And add
mount ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/media /data/media
wait rw
in init.omap4pandaboard.rc to mount it. The /sdcard will be mounted to the
media partion.
If you use new u-boot loader (ex. device/ti/richi-panda/u-boot.bin), there
will be no media partion created. The /sdcard will be mounted to
/data/media on userdata partion. Remember to adjust
BOARD_USERDATAIMAGE_PARTITION_SIZE in BoardConfig.mk according to the size
of userdata partion that the u-boot loader reported.
On Wed, Apr 18, 2012 at 10:56 PM, AlexV <alexandr...@gmail.com> wrote:
> Hi richi,
> Could you please describe what've you done to make physical media
> partition mount to /sdcard?
> суббота, 21 января 2012 г., 14:18:44 UTC+3 пользователь richi chen написал:
>> Hi, why not try my repo. based on omapzoom ics-mr1 branch.
>> 1. get & make
>> repo init -u git://github.com/richi-chen/**Pandaboard-ICS-repo.git<http://github.com/richi-chen/Pandaboard-ICS-repo.git>-b omapzoom
>> repo sync
>> . build/envsetup.sh
>> lunch full_richi_panda-eng
>> make
>> 2. patch the kernel, build kernel & driver modules
>> cp device/ti/richi-panda/panda-**add-btwilink-support-for-ics.**patch
>> kernel/
>> cd kernel/
>> git apply panda-add-btwilink-support-**for-ics.patch
>> cd ..
>> make kernel_build
>> 3. rebuild boot/system image
>> make
>> Don't forget to manually format the SD card media partition to ext4, it
>> will mount the internal /sdcard to real physical media partition while
>> booting.
>> It also support external USB storage.
I'm beginner on android porting.
I encounter the same problem about bluetooth proting too.
But my bt status different with you, i use ttyUSB0 to control non-ti bluetooth module and linaro 12.01 release bsp source
As below informations are my encounter
#dmesg
root@android:/ # bluetoothd -n
bluetoothd[974]: Bluetooth deamon 4.93
bluetoothd[974]: Unable to get on D-Bus
#logcat
I/bluedroid( 182): Starting bluetoothd deamon
E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: org.bluez.Error.NoSuchAdapter (No such adapter)
E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop!
E/BluetoothService.cpp( 182): setBluetoothTetheringNative true
D/BluetoothEventLoop( 182): Property Changed: Pairable : false
D/BluetoothEventLoop( 182): Property Changed: Powered : false
D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6
D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7
D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8
D/BluetoothAdapterStateMachine( 182): WarmUp process message: 101
D/BluetoothAdapterStateMachine( 182): WarmUp process message: 54
D/BluetoothAdapterStateMachine( 182): WarmUp process message: 51
D/BluetoothAdapterStateMachine( 182): HotOff process message: 101
> Thanks to richi-chen and gad.krumh...@gmail.com. > I followed the steps given by gad.krumh...@gmail.com and following are > some of the important changes which may require (for me without these > changes Bluetooth didn't come up)
> In the init.omap4pandaboard.rc I have modified the following
> on boot > mount debugfs /sys/kernel/debug /sys/kernel/debug > chmod 0666 /dev/pvrsrvkm > chmod 0777 /dev/ttyO1 /* Added by me */ > chmod 0777 /dev/tty* > chmod 0777 /dev/tty
> and > service uim /system/bin/uim-sysfs > class core > user bluetooth > group bluetooth net_bt_admin > group bluetooth root /* Added by me. But not sure is this > really > required or not. Yet to try without having this line */
> After this Bluetooth is started working. I mean able to see the > devices, not yet tried file transfer options
> -VH
> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote: > > I have incorporated your changes and Wifi is working fine now. The > > problem of bluetooth still remains. It is giving IO error. The logcat > > displays: > > uim: Un-installed N_TI_WL Line displine.
> > also
> > uim: Install set to 1 > > uim: Cant open /dev/tty01
> I'm beginner on android porting.
> I encounter the same problem about bluetooth proting too.
> But my bt status different with you, i use ttyUSB0 to control non-ti > bluetooth module and linaro 12.01 release bsp source
> As below informations are my encounter
> #dmesg
> root@android:/ # bluetoothd -n
> bluetoothd[974]: Bluetooth deamon 4.93
> bluetoothd[974]: Unable to get on D-Bus
> #logcat
> I/bluedroid( 182): Starting bluetoothd deamon
> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not > provided by any .service files)
> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not > provided by any .service files)
> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not > provided by any .service files)
> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > org.bluez.Error.NoSuchAdapter (No such adapter)
> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop!
> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true
> D/BluetoothEventLoop( 182): Property Changed: Pairable : false
> D/BluetoothEventLoop( 182): Property Changed: Powered : false
> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6
> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7
> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8
> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 101
> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 54
> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 51
> D/BluetoothAdapterStateMachine( 182): HotOff process message: 101
> Could you provide more information for me?
> Thanks
> VH於 2012年2月21日星期二UTC+8下午7時36分09秒寫道:
>> Thanks to richi-chen and gad.krumh...@gmail.com. >> I followed the steps given by gad.krumh...@gmail.com and following are >> some of the important changes which may require (for me without these >> changes Bluetooth didn't come up)
>> In the init.omap4pandaboard.rc I have modified the following
>> on boot >> mount debugfs /sys/kernel/debug /sys/kernel/debug >> chmod 0666 /dev/pvrsrvkm >> chmod 0777 /dev/ttyO1 /* Added by me */ >> chmod 0777 /dev/tty* >> chmod 0777 /dev/tty
>> and >> service uim /system/bin/uim-sysfs >> class core >> user bluetooth >> group bluetooth net_bt_admin >> group bluetooth root /* Added by me. But not sure is this >> really >> required or not. Yet to try without having this line */
>> After this Bluetooth is started working. I mean able to see the >> devices, not yet tried file transfer options
>> -VH
>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote: >> > I have incorporated your changes and Wifi is working fine now. The >> > problem of bluetooth still remains. It is giving IO error. The logcat >> > displays: >> > uim: Un-installed N_TI_WL Line displine.
>> > also
>> > uim: Install set to 1 >> > uim: Cant open /dev/tty01
On Mon, Sep 10, 2012 at 9:25 PM, <liutao.l...@gmail.com> wrote:
> Hi CJ,
> I have the same question with you now, I am obsessed bythis problem. Have
> you solved this question,could you tell me how?Thanks a lot!!!!!
the problem exists on almost all platforms.
Bluetooth enabler - the one that starts bluetoothd, hciattach does
rfkill doesn't necessarily wait for bluetoothd to setup dbus before
starting event-loop.
dbus also lacks a function which could sort of check existance of an
object on system bus... ideally we should have one..
try increasing the sleep time in get_adapter_path (usleep) to about
100ms... chances are that the dbus object is ready by the 2nd
iteration itself...
>> I'm beginner on android porting.
>> I encounter the same problem about bluetooth proting too.
>> But my bt status different with you, i use ttyUSB0 to control non-ti
>> bluetooth module and linaro 12.01 release bsp source
>> As below informations are my encounter
>> #dmesg
>> root@android:/ # bluetoothd -n
>> bluetoothd[974]: Bluetooth deamon 4.93
>> bluetoothd[974]: Unable to get on D-Bus
>> #logcat
>> I/bluedroid( 182): Starting bluetoothd deamon
>> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not
>> provided by any .service files)
>> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not
>> provided by any .service files)
>> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not
>> provided by any .service files)
>> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> org.bluez.Error.NoSuchAdapter (No such adapter)
>> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop!
>> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true
>> D/BluetoothEventLoop( 182): Property Changed: Pairable : false
>> D/BluetoothEventLoop( 182): Property Changed: Powered : false
>> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6
>> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7
>> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8
>> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 101
>> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 54
>> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 51
>> D/BluetoothAdapterStateMachine( 182): HotOff process message: 101
>> Could you provide more information for me?
>> Thanks
>> VH於 2012年2月21日星期二UTC+8下午7時36分09秒寫道:
>>> Thanks to richi-chen and gad.krumh...@gmail.com.
>>> I followed the steps given by gad.krumh...@gmail.com and following are
>>> some of the important changes which may require (for me without these
>>> changes Bluetooth didn't come up)
>>> In the init.omap4pandaboard.rc I have modified the following
>>> on boot
>>> mount debugfs /sys/kernel/debug /sys/kernel/debug
>>> chmod 0666 /dev/pvrsrvkm
>>> chmod 0777 /dev/ttyO1 /* Added by me */
>>> chmod 0777 /dev/tty*
>>> chmod 0777 /dev/tty
>>> and
>>> service uim /system/bin/uim-sysfs
>>> class core
>>> user bluetooth
>>> group bluetooth net_bt_admin
>>> group bluetooth root /* Added by me. But not sure is this
>>> really
>>> required or not. Yet to try without having this line */
>>> After this Bluetooth is started working. I mean able to see the
>>> devices, not yet tried file transfer options
>>> -VH
>>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote:
>>> > I have incorporated your changes and Wifi is working fine now. The
>>> > problem of bluetooth still remains. It is giving IO error. The logcat
>>> > displays:
>>> > uim: Un-installed N_TI_WL Line displine.
>>> > also
>>> > uim: Install set to 1
>>> > uim: Cant open /dev/tty01
On Tuesday, September 11, 2012 7:03:05 PM UTC+5:30, Pavan Savoy wrote:
> On Mon, Sep 10, 2012 at 9:25 PM, <liuta...@gmail.com <javascript:>> > wrote: > > Hi CJ,
> > I have the same question with you now, I am obsessed bythis problem. > Have > > you solved this question,could you tell me how?Thanks a lot!!!!!
> the problem exists on almost all platforms. > Bluetooth enabler - the one that starts bluetoothd, hciattach does > rfkill doesn't necessarily wait for bluetoothd to setup dbus before > starting event-loop.
> dbus also lacks a function which could sort of check existance of an > object on system bus... ideally we should have one..
> try increasing the sleep time in get_adapter_path (usleep) to about > 100ms... chances are that the dbus object is ready by the 2nd > iteration itself...
> > 在 2012年7月4日星期三UTC+8下午3时02分23秒,CJ写道:
> >> Hi VH,
> >> I'm beginner on android porting. > >> I encounter the same problem about bluetooth proting too. > >> But my bt status different with you, i use ttyUSB0 to control non-ti > >> bluetooth module and linaro 12.01 release bsp source > >> As below informations are my encounter
> >> #dmesg > >> root@android:/ # bluetoothd -n > >> bluetoothd[974]: Bluetooth deamon 4.93 > >> bluetoothd[974]: Unable to get on D-Bus
> >> #logcat > >> I/bluedroid( 182): Starting bluetoothd deamon > >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > >> org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not > >> provided by any .service files) > >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > >> org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not > >> provided by any .service files) > >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > >> org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not > >> provided by any .service files) > >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: > >> org.bluez.Error.NoSuchAdapter (No such adapter) > >> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop! > >> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true > >> D/BluetoothEventLoop( 182): Property Changed: Pairable : false > >> D/BluetoothEventLoop( 182): Property Changed: Powered : false > >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6 > >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7 > >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8 > >> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 101 > >> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 54 > >> D/BluetoothAdapterStateMachine( 182): WarmUp process message: 51 > >> D/BluetoothAdapterStateMachine( 182): HotOff process message: 101
> >> Could you provide more information for me? > >> Thanks
> >> VH於 2012年2月21日星期二UTC+8下午7時36分09秒寫道:
> >>> Thanks to richi-chen and gad.krumh...@gmail.com. > >>> I followed the steps given by gad.krumh...@gmail.com and following > are > >>> some of the important changes which may require (for me without these > >>> changes Bluetooth didn't come up)
> >>> In the init.omap4pandaboard.rc I have modified the following
> >>> on boot > >>> mount debugfs /sys/kernel/debug /sys/kernel/debug > >>> chmod 0666 /dev/pvrsrvkm > >>> chmod 0777 /dev/ttyO1 /* Added by me */ > >>> chmod 0777 /dev/tty* > >>> chmod 0777 /dev/tty
> >>> and > >>> service uim /system/bin/uim-sysfs > >>> class core > >>> user bluetooth > >>> group bluetooth net_bt_admin > >>> group bluetooth root /* Added by me. But not sure is this > >>> really > >>> required or not. Yet to try without having this line */
> >>> After this Bluetooth is started working. I mean able to see the > >>> devices, not yet tried file transfer options
> >>> -VH
> >>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote: > >>> > I have incorporated your changes and Wifi is working fine now. The > >>> > problem of bluetooth still remains. It is giving IO error. The > logcat > >>> > displays: > >>> > uim: Un-installed N_TI_WL Line displine.
> >>> > also
> >>> > uim: Install set to 1 > >>> > uim: Cant open /dev/tty01
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
On Jan 4, 2013 10:36 AM, <prasannakarthik...@gmail.com> wrote:
> When I reboot some time later it sometimes turns on .
> Now its not turning on .
> What possibly could be the bug?
> Regards
> prasanna
> On Tuesday, September 11, 2012 7:03:05 PM UTC+5:30, Pavan Savoy wrote:
>> On Mon, Sep 10, 2012 at 9:25 PM, <liuta...@gmail.com> wrote:
>> > Hi CJ,
>> > I have the same question with you now, I am obsessed bythis problem.
>> Have
>> > you solved this question,could you tell me how?Thanks a lot!!!!!
>> the problem exists on almost all platforms.
>> Bluetooth enabler - the one that starts bluetoothd, hciattach does
>> rfkill doesn't necessarily wait for bluetoothd to setup dbus before
>> starting event-loop.
>> dbus also lacks a function which could sort of check existance of an
>> object on system bus... ideally we should have one..
>> try increasing the sleep time in get_adapter_path (usleep) to about
>> 100ms... chances are that the dbus object is ready by the 2nd
>> iteration itself...
>> > 在 2012年7月4日星期三UTC+8下午3时02分23秒,**CJ写道:
>> >> Hi VH,
>> >> I'm beginner on android porting.
>> >> I encounter the same problem about bluetooth proting too.
>> >> But my bt status different with you, i use ttyUSB0 to control non-ti
>> >> bluetooth module and linaro 12.01 release bsp source
>> >> As below informations are my encounter
>> >> #dmesg
>> >> root@android:/ # bluetoothd -n
>> >> bluetoothd[974]: Bluetooth deamon 4.93
>> >> bluetoothd[974]: Unable to get on D-Bus
>> >> #logcat
>> >> I/bluedroid( 182): Starting bluetoothd deamon
>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was
>> not
>> >> provided by any .service files)
>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was
>> not
>> >> provided by any .service files)
>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was
>> not
>> >> provided by any .service files)
>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>> >> org.bluez.Error.NoSuchAdapter (No such adapter)
>> >> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop!
>> >> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true
>> >> D/BluetoothEventLoop( 182): Property Changed: Pairable : false
>> >> D/BluetoothEventLoop( 182): Property Changed: Powered : false
>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6
>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7
>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8
>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 101
>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 54
>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 51
>> >> D/**BluetoothAdapterStateMachine( 182): HotOff process message: 101
>> >> Could you provide more information for me?
>> >> Thanks
>> >> VH於 2012年2月21日星期二UTC+**8下午7時36分09秒寫道:
>> >>> Thanks to richi-chen and gad.krumh...@gmail.com.
>> >>> I followed the steps given by gad.krumh...@gmail.com and following
>> are
>> >>> some of the important changes which may require (for me without these
>> >>> changes Bluetooth didn't come up)
>> >>> In the init.omap4pandaboard.rc I have modified the following
>> >>> on boot
>> >>> mount debugfs /sys/kernel/debug /sys/kernel/debug
>> >>> chmod 0666 /dev/pvrsrvkm
>> >>> chmod 0777 /dev/ttyO1 /* Added by me */
>> >>> chmod 0777 /dev/tty*
>> >>> chmod 0777 /dev/tty
>> >>> and
>> >>> service uim /system/bin/uim-sysfs
>> >>> class core
>> >>> user bluetooth
>> >>> group bluetooth net_bt_admin
>> >>> group bluetooth root /* Added by me. But not sure is this
>> >>> really
>> >>> required or not. Yet to try without having this line */
>> >>> After this Bluetooth is started working. I mean able to see the
>> >>> devices, not yet tried file transfer options
>> >>> -VH
>> >>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote:
>> >>> > I have incorporated your changes and Wifi is working fine now. The
>> >>> > problem of bluetooth still remains. It is giving IO error. The
>> logcat
>> >>> > displays:
>> >>> > uim: Un-installed N_TI_WL Line displine.
>> >>> > also
>> >>> > uim: Install set to 1
>> >>> > uim: Cant open /dev/tty01
Pavan I see /system/bin/uim running. from ps list. I dont have uim-sysfs
Earlier I had bluetooth working without that
uim get me this
*1|root@android:/system/bin # uim*
uim:@ main
uim:install set previously...
uim:@ st_uart_config
uim: signal received, opening /dev/ttyO1
uim:@ set_baud_rate
uim:set_baud_rate() done
uim:Setting speed to 3000000
uim:@ read_command_complete
uim: Command complete started
uim:@ read_hci_event
uim: read_hci_event
uim:Invalid response
uim:begin polling...
uim:poll broke due to event 10(PRI:2/ERR:8)
uim:read 0 from install uim:@ st_uart_config
uim:Un-Installed N_TI_WL Line displine
uim:begin polling...
uim:poll broke due to event 10(PRI:2/ERR:8)
uim:read 1 from install uim:@ st_uart_config
uim: signal received, opening /dev/ttyO1
*
kernel messages dmesg*
Bluetooth: st_register failed -22
(stk) :line disc installation timed out (stk) :ldisc_install = 0
*Few minutes back I had uim running from terminal and I had bluetooth on suddenly and once I make BT off or restart it again fails to register.
What actually could be the problem with ttyO1?*
*
my init.rc contents*
insmod /system/modules/st_drv.ko
insmod /system/modules/bluetooth.ko
insmod /system/modules/bnep.ko
insmod /system/modules/hci_uart.ko
insmod /system/modules/rfcomm.ko
insmod /system/modules/btwilink.ko
chown system system /sys/class/rfkill/rfkill0/type
chown system system /sys/class/rfkill/rfkill0/state
insmod /system/modules/wl1273-core.ko
insmod /system/modules/wl12xx.ko
#userspace daemon needed for bluetooth
service uim /system/bin/uim
class main
user root
oneshot
On Friday, January 4, 2013 10:24:05 PM UTC+5:30, Pavan Savoy wrote:
> 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
> On Jan 4, 2013 10:36 AM, <prasannak...@gmail.com <javascript:>> wrote:
>> Pavan
>> Am booting ICS chipsee linaro release on pandaboard
>> Bluetooth was working well . Now its not getting registered. which left >> me with
>> When I reboot some time later it sometimes turns on .
>> Now its not turning on .
>> What possibly could be the bug?
>> Regards
>> prasanna
>> On Tuesday, September 11, 2012 7:03:05 PM UTC+5:30, Pavan Savoy wrote:
>>> On Mon, Sep 10, 2012 at 9:25 PM, <liuta...@gmail.com> wrote: >>> > Hi CJ,
>>> > I have the same question with you now, I am obsessed bythis problem. >>> Have >>> > you solved this question,could you tell me how?Thanks a lot!!!!!
>>> the problem exists on almost all platforms. >>> Bluetooth enabler - the one that starts bluetoothd, hciattach does >>> rfkill doesn't necessarily wait for bluetoothd to setup dbus before >>> starting event-loop.
>>> dbus also lacks a function which could sort of check existance of an >>> object on system bus... ideally we should have one..
>>> try increasing the sleep time in get_adapter_path (usleep) to about >>> 100ms... chances are that the dbus object is ready by the 2nd >>> iteration itself...
>>> > 在 2012年7月4日星期三UTC+8下午3时02分23秒,**CJ写道:
>>> >> Hi VH,
>>> >> I'm beginner on android porting. >>> >> I encounter the same problem about bluetooth proting too. >>> >> But my bt status different with you, i use ttyUSB0 to control non-ti >>> >> bluetooth module and linaro 12.01 release bsp source >>> >> As below informations are my encounter
>>> >> #dmesg >>> >> root@android:/ # bluetoothd -n >>> >> bluetoothd[974]: Bluetooth deamon 4.93 >>> >> bluetoothd[974]: Unable to get on D-Bus
>>> >> #logcat >>> >> I/bluedroid( 182): Starting bluetoothd deamon >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.bluez.Error.NoSuchAdapter (No such adapter) >>> >> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop! >>> >> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true >>> >> D/BluetoothEventLoop( 182): Property Changed: Pairable : false >>> >> D/BluetoothEventLoop( 182): Property Changed: Powered : false >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6 >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7 >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 101 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 54 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 51 >>> >> D/**BluetoothAdapterStateMachine( 182): HotOff process message: 101
>>> >> Could you provide more information for me? >>> >> Thanks
>>> >> VH於 2012年2月21日星期二UTC+**8下午7時36分09秒寫道:
>>> >>> Thanks to richi-chen and gad.krumh...@gmail.com. >>> >>> I followed the steps given by gad.krumh...@gmail.com and following >>> are >>> >>> some of the important changes which may require (for me without >>> these >>> >>> changes Bluetooth didn't come up)
>>> >>> In the init.omap4pandaboard.rc I have modified the following
>>> >>> on boot >>> >>> mount debugfs /sys/kernel/debug /sys/kernel/debug >>> >>> chmod 0666 /dev/pvrsrvkm >>> >>> chmod 0777 /dev/ttyO1 /* Added by me */ >>> >>> chmod 0777 /dev/tty* >>> >>> chmod 0777 /dev/tty
>>> >>> and >>> >>> service uim /system/bin/uim-sysfs >>> >>> class core >>> >>> user bluetooth >>> >>> group bluetooth net_bt_admin >>> >>> group bluetooth root /* Added by me. But not sure is >>> this >>> >>> really >>> >>> required or not. Yet to try without having this line */
>>> >>> After this Bluetooth is started working. I mean able to see the >>> >>> devices, not yet tried file transfer options
>>> >>> -VH
>>> >>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote: >>> >>> > I have incorporated your changes and Wifi is working fine now. The >>> >>> > problem of bluetooth still remains. It is giving IO error. The >>> logcat >>> >>> > displays: >>> >>> > uim: Un-installed N_TI_WL Line displine.
>>> >>> > also
>>> >>> > uim: Install set to 1 >>> >>> > uim: Cant open /dev/tty01
On Friday, January 4, 2013 10:24:05 PM UTC+5:30, Pavan Savoy wrote:
> 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
> On Jan 4, 2013 10:36 AM, <prasannak...@gmail.com <javascript:>> wrote:
>> Pavan
>> Am booting ICS chipsee linaro release on pandaboard
>> Bluetooth was working well . Now its not getting registered. which left >> me with
>> When I reboot some time later it sometimes turns on .
>> Now its not turning on .
>> What possibly could be the bug?
>> Regards
>> prasanna
>> On Tuesday, September 11, 2012 7:03:05 PM UTC+5:30, Pavan Savoy wrote:
>>> On Mon, Sep 10, 2012 at 9:25 PM, <liuta...@gmail.com> wrote: >>> > Hi CJ,
>>> > I have the same question with you now, I am obsessed bythis problem. >>> Have >>> > you solved this question,could you tell me how?Thanks a lot!!!!!
>>> the problem exists on almost all platforms. >>> Bluetooth enabler - the one that starts bluetoothd, hciattach does >>> rfkill doesn't necessarily wait for bluetoothd to setup dbus before >>> starting event-loop.
>>> dbus also lacks a function which could sort of check existance of an >>> object on system bus... ideally we should have one..
>>> try increasing the sleep time in get_adapter_path (usleep) to about >>> 100ms... chances are that the dbus object is ready by the 2nd >>> iteration itself...
>>> > 在 2012年7月4日星期三UTC+8下午3时02分23秒,**CJ写道:
>>> >> Hi VH,
>>> >> I'm beginner on android porting. >>> >> I encounter the same problem about bluetooth proting too. >>> >> But my bt status different with you, i use ttyUSB0 to control non-ti >>> >> bluetooth module and linaro 12.01 release bsp source >>> >> As below informations are my encounter
>>> >> #dmesg >>> >> root@android:/ # bluetoothd -n >>> >> bluetoothd[974]: Bluetooth deamon 4.93 >>> >> bluetoothd[974]: Unable to get on D-Bus
>>> >> #logcat >>> >> I/bluedroid( 182): Starting bluetoothd deamon >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.bluez.Error.NoSuchAdapter (No such adapter) >>> >> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop! >>> >> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true >>> >> D/BluetoothEventLoop( 182): Property Changed: Pairable : false >>> >> D/BluetoothEventLoop( 182): Property Changed: Powered : false >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6 >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7 >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 101 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 54 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 51 >>> >> D/**BluetoothAdapterStateMachine( 182): HotOff process message: 101
>>> >> Could you provide more information for me? >>> >> Thanks
>>> >> VH於 2012年2月21日星期二UTC+**8下午7時36分09秒寫道:
>>> >>> Thanks to richi-chen and gad.krumh...@gmail.com. >>> >>> I followed the steps given by gad.krumh...@gmail.com and following >>> are >>> >>> some of the important changes which may require (for me without >>> these >>> >>> changes Bluetooth didn't come up)
>>> >>> In the init.omap4pandaboard.rc I have modified the following
>>> >>> on boot >>> >>> mount debugfs /sys/kernel/debug /sys/kernel/debug >>> >>> chmod 0666 /dev/pvrsrvkm >>> >>> chmod 0777 /dev/ttyO1 /* Added by me */ >>> >>> chmod 0777 /dev/tty* >>> >>> chmod 0777 /dev/tty
>>> >>> and >>> >>> service uim /system/bin/uim-sysfs >>> >>> class core >>> >>> user bluetooth >>> >>> group bluetooth net_bt_admin >>> >>> group bluetooth root /* Added by me. But not sure is >>> this >>> >>> really >>> >>> required or not. Yet to try without having this line */
>>> >>> After this Bluetooth is started working. I mean able to see the >>> >>> devices, not yet tried file transfer options
>>> >>> -VH
>>> >>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote: >>> >>> > I have incorporated your changes and Wifi is working fine now. The >>> >>> > problem of bluetooth still remains. It is giving IO error. The >>> logcat >>> >>> > displays: >>> >>> > uim: Un-installed N_TI_WL Line displine.
>>> >>> > also
>>> >>> > uim: Install set to 1 >>> >>> > uim: Cant open /dev/tty01
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 ?
On Friday, January 4, 2013 10:24:05 PM UTC+5:30, Pavan Savoy wrote:
> 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
> On Jan 4, 2013 10:36 AM, <prasannak...@gmail.com <javascript:>> wrote:
>> Pavan
>> Am booting ICS chipsee linaro release on pandaboard
>> Bluetooth was working well . Now its not getting registered. which left >> me with
>> When I reboot some time later it sometimes turns on .
>> Now its not turning on .
>> What possibly could be the bug?
>> Regards
>> prasanna
>> On Tuesday, September 11, 2012 7:03:05 PM UTC+5:30, Pavan Savoy wrote:
>>> On Mon, Sep 10, 2012 at 9:25 PM, <liuta...@gmail.com> wrote: >>> > Hi CJ,
>>> > I have the same question with you now, I am obsessed bythis problem. >>> Have >>> > you solved this question,could you tell me how?Thanks a lot!!!!!
>>> the problem exists on almost all platforms. >>> Bluetooth enabler - the one that starts bluetoothd, hciattach does >>> rfkill doesn't necessarily wait for bluetoothd to setup dbus before >>> starting event-loop.
>>> dbus also lacks a function which could sort of check existance of an >>> object on system bus... ideally we should have one..
>>> try increasing the sleep time in get_adapter_path (usleep) to about >>> 100ms... chances are that the dbus object is ready by the 2nd >>> iteration itself...
>>> > 在 2012年7月4日星期三UTC+8下午3时02分23秒,**CJ写道:
>>> >> Hi VH,
>>> >> I'm beginner on android porting. >>> >> I encounter the same problem about bluetooth proting too. >>> >> But my bt status different with you, i use ttyUSB0 to control non-ti >>> >> bluetooth module and linaro 12.01 release bsp source >>> >> As below informations are my encounter
>>> >> #dmesg >>> >> root@android:/ # bluetoothd -n >>> >> bluetoothd[974]: Bluetooth deamon 4.93 >>> >> bluetoothd[974]: Unable to get on D-Bus
>>> >> #logcat >>> >> I/bluedroid( 182): Starting bluetoothd deamon >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.freedesktop.DBus.Error.**ServiceUnknown (The name org.bluez was >>> not >>> >> provided by any .service files) >>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error: >>> >> org.bluez.Error.NoSuchAdapter (No such adapter) >>> >> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop! >>> >> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true >>> >> D/BluetoothEventLoop( 182): Property Changed: Pairable : false >>> >> D/BluetoothEventLoop( 182): Property Changed: Powered : false >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6 >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7 >>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 101 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 54 >>> >> D/**BluetoothAdapterStateMachine( 182): WarmUp process message: 51 >>> >> D/**BluetoothAdapterStateMachine( 182): HotOff process message: 101
>>> >> Could you provide more information for me? >>> >> Thanks
>>> >> VH於 2012年2月21日星期二UTC+**8下午7時36分09秒寫道:
>>> >>> Thanks to richi-chen and gad.krumh...@gmail.com. >>> >>> I followed the steps given by gad.krumh...@gmail.com and following >>> are >>> >>> some of the important changes which may require (for me without >>> these >>> >>> changes Bluetooth didn't come up)
>>> >>> In the init.omap4pandaboard.rc I have modified the following
>>> >>> on boot >>> >>> mount debugfs /sys/kernel/debug /sys/kernel/debug >>> >>> chmod 0666 /dev/pvrsrvkm >>> >>> chmod 0777 /dev/ttyO1 /* Added by me */ >>> >>> chmod 0777 /dev/tty* >>> >>> chmod 0777 /dev/tty
>>> >>> and >>> >>> service uim /system/bin/uim-sysfs >>> >>> class core >>> >>> user bluetooth >>> >>> group bluetooth net_bt_admin >>> >>> group bluetooth root /* Added by me. But not sure is >>> this >>> >>> really >>> >>> required or not. Yet to try without having this line */
>>> >>> After this Bluetooth is started working. I mean able to see the >>> >>> devices, not yet tried file transfer options
>>> >>> -VH
>>> >>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote: >>> >>> > I have incorporated your changes and Wifi is working fine now. The >>> >>> > problem of bluetooth still remains. It is giving IO error. The >>> logcat >>> >>> > displays: >>> >>> > uim: Un-installed N_TI_WL Line displine.
>>> >>> > also
>>> >>> > uim: Install set to 1 >>> >>> > uim: Cant open /dev/tty01
> 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 ?
> On Friday, January 4, 2013 10:24:05 PM UTC+5:30, Pavan Savoy wrote:
>> 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
>> On Jan 4, 2013 10:36 AM, <prasannak...@gmail.com> wrote:
>>> Pavan
>>> Am booting ICS chipsee linaro release on pandaboard
>>> Bluetooth was working well . Now its not getting registered. which left
>>> me with
>>> When I reboot some time later it sometimes turns on .
>>> Now its not turning on .
>>> What possibly could be the bug?
>>> Regards
>>> prasanna
>>> On Tuesday, September 11, 2012 7:03:05 PM UTC+5:30, Pavan Savoy wrote:
>>>> On Mon, Sep 10, 2012 at 9:25 PM, <liuta...@gmail.com> wrote:
>>>> > Hi CJ,
>>>> > I have the same question with you now, I am obsessed bythis problem.
>>>> Have
>>>> > you solved this question,could you tell me how?Thanks a lot!!!!!
>>>> the problem exists on almost all platforms.
>>>> Bluetooth enabler - the one that starts bluetoothd, hciattach does
>>>> rfkill doesn't necessarily wait for bluetoothd to setup dbus before
>>>> starting event-loop.
>>>> dbus also lacks a function which could sort of check existance of an
>>>> object on system bus... ideally we should have one..
>>>> try increasing the sleep time in get_adapter_path (usleep) to about
>>>> 100ms... chances are that the dbus object is ready by the 2nd
>>>> iteration itself...
>>>> > 在 2012年7月4日星期三UTC+8下午3时02分23秒,**CJ**写道:
>>>> >> Hi VH,
>>>> >> I'm beginner on android porting.
>>>> >> I encounter the same problem about bluetooth proting too.
>>>> >> But my bt status different with you, i use ttyUSB0 to control non-ti
>>>> >> bluetooth module and linaro 12.01 release bsp source
>>>> >> As below informations are my encounter
>>>> >> #dmesg
>>>> >> root@android:/ # bluetoothd -n
>>>> >> bluetoothd[974]: Bluetooth deamon 4.93
>>>> >> bluetoothd[974]: Unable to get on D-Bus
>>>> >> #logcat
>>>> >> I/bluedroid( 182): Starting bluetoothd deamon
>>>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>>>> >> org.freedesktop.DBus.Error.**Ser**viceUnknown (The name org.bluez
>>>> was not
>>>> >> provided by any .service files)
>>>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>>>> >> org.freedesktop.DBus.Error.**Ser**viceUnknown (The name org.bluez
>>>> was not
>>>> >> provided by any .service files)
>>>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>>>> >> org.freedesktop.DBus.Error.**Ser**viceUnknown (The name org.bluez
>>>> was not
>>>> >> provided by any .service files)
>>>> >> E/BluetoothEventLoop.cpp( 182): get_adapter_path: D-Bus error:
>>>> >> org.bluez.Error.NoSuchAdapter (No such adapter)
>>>> >> E/BluetoothEventLoop.cpp( 182): failure setting up Event Loop!
>>>> >> E/BluetoothService.cpp( 182): setBluetoothTetheringNative true
>>>> >> D/BluetoothEventLoop( 182): Property Changed: Pairable : false
>>>> >> D/BluetoothEventLoop( 182): Property Changed: Powered : false
>>>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 6
>>>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 7
>>>> >> D/BluetoothEventLoop( 182): Property Changed: UUIDs : 8
>>>> >> D/**BluetoothAdapterStateMachine**( 182): WarmUp process message:
>>>> 101
>>>> >> D/**BluetoothAdapterStateMachine**( 182): WarmUp process message:
>>>> 54
>>>> >> D/**BluetoothAdapterStateMachine**( 182): WarmUp process message:
>>>> 51
>>>> >> D/**BluetoothAdapterStateMachine**( 182): HotOff process message:
>>>> 101
>>>> >> Could you provide more information for me?
>>>> >> Thanks
>>>> >> VH於 2012年2月21日星期二UTC+**8下午7時36分09秒寫道**:
>>>> >>> Thanks to richi-chen and gad.krumh...@gmail.com.
>>>> >>> I followed the steps given by gad.krumh...@gmail.com and following
>>>> are
>>>> >>> some of the important changes which may require (for me without
>>>> these
>>>> >>> changes Bluetooth didn't come up)
>>>> >>> In the init.omap4pandaboard.rc I have modified the following
>>>> >>> on boot
>>>> >>> mount debugfs /sys/kernel/debug /sys/kernel/debug
>>>> >>> chmod 0666 /dev/pvrsrvkm
>>>> >>> chmod 0777 /dev/ttyO1 /* Added by me */
>>>> >>> chmod 0777 /dev/tty*
>>>> >>> chmod 0777 /dev/tty
>>>> >>> and
>>>> >>> service uim /system/bin/uim-sysfs
>>>> >>> class core
>>>> >>> user bluetooth
>>>> >>> group bluetooth net_bt_admin
>>>> >>> group bluetooth root /* Added by me. But not sure is
>>>> this
>>>> >>> really
>>>> >>> required or not. Yet to try without having this line */
>>>> >>> After this Bluetooth is started working. I mean able to see the
>>>> >>> devices, not yet tried file transfer options
>>>> >>> -VH
>>>> >>> On Feb 20, 2:50 pm, Shantanu <unrealsh...@gmail.com> wrote:
>>>> >>> > I have incorporated your changes and Wifi is working fine now.
>>>> The
>>>> >>> > problem of bluetooth still remains. It is giving IO error. The
>>>> logcat
>>>> >>> > displays:
>>>> >>> > uim: Un-installed N_TI_WL Line displine.
>>>> >>> > also
>>>> >>> > uim: Install set to 1
>>>> >>> > uim: Cant open /dev/tty01