Hi! You know, I just tried to run some more tests and could not reproduce it. I'm sorry! I think I was confused by the fact that fso didn't power on the chip after resume even though I requested Bluetooth resource with fsoraw before suspend. Thanks for the reply!
2010/7/30 Al Johnson <[email protected]>: > On Friday 30 July 2010, Denis Shulyaka wrote: >> 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! > > Did you start bluetoothd? There is already a bug report [1] about bluetoothd > not being started because udev was removed. FSO will turn on the bluetooth > chip, but because there is no udev to start bluetoothd none of the apps can > use it. > > [1] http://www.shr-project.org/trac/ticket/1159 > _______________________________________________ > 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
