On Friday 23 July 2010, Valery Febvre wrote: > On 07/23/2010 02:50 PM, Carmelo Ferrante wrote: > > > On Friday 23 July 2010, Al Johnson wrote: > > > > On Friday 23 July 2010, pridurok wrote: > > > > > >Is it only me to have this problem? Do you think that flashing > > > > > >SHR-U again > > > > > > > > > > would solve it? > > > > > > > > > > I have same problem with same image. > > > > > > > > I've just stuck the latest [1] full shr-u on a new partition and > > > > tried it, > > > > > > and you are correct - it doesn't work. This is because bluetoothd > > > > isn't running, which is because udev is no longer there to start it > > > > when a bluetooth device appears. I'll go and make a bug report. > > > > > > > > As a workaround you can run /usr/sbin/bluetoothd after starting > > > > bluetooth > > > > > > and things should behave correctly. > > > > > > > > [1] shr-full-eglibc-ipk--20100721-om-gta02.rootfs.tar.gz > > > > > > Bug filed. > > > > > > http://www.shr-project.org/trac/ticket/1159 > > > > Thanks a lot! > > Workaround you suggest does not work on my phone, but it's not a > > problem, I'll wait for community to fix it! > > I think that bluetoothd must be start with --udev option > > # /usr/sbin/bluetoothd --udev
I think that option just makes it wait for dbus to become available. It's used in the udev rule so that if the event happens at boot it will wait for dbus to be started by its init script rather than exit immediately because dbus is missing. _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
