Hi! I can't start bluetooth even with `echo "1" >/sys/bus/platform/devices/gta02-pm-bt.0/power_on` after suspend/resume cycle. If the phone was not suspended since boot, it works OK, but if it was, it doesn't. Where do I report about this issue?
I'm using latest SHR-U with 2.6.32.13 kernel. Thanks! 2010/7/23 Joachim Ott <[email protected]>: > On 23 July 2010 15:18, Carmelo Ferrante <[email protected]> wrote: >> >> >>> 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. >> >> In fact it does not work even with the --udev option. > > I got it to work with the above hints, that is: > > # echo "1" >/sys/bus/platform/devices/gta02-pm-bt.0/power_on > # bluetoothd -du (debug-output and udev-option) > > After that I found some other device nearby: > > # hcitool scan > Scanning ... > 00:23:45:5E:04:D9 My name is 905 > # hciconfig > hci0: Type: USB > BD Address: 00:06:6E:17:88:8B ACL MTU: 384:8 SCO MTU: 64:8 > UP RUNNING PSCAN > RX bytes:2597 acl:0 sco:0 events:86 errors:0 > TX bytes:767 acl:0 sco:0 commands:59 errors:0 > _______________________________________________ > Shr-User mailing list > [email protected] > http://lists.shr-project.org/mailman/listinfo/shr-user > _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
