Another interesting bug:
If you disabble bluetooth, besides it 2on't turn on again, it will spam the system log (you can launch dmesg -wH to view the live output) with a particular line:
[...]
[ +0.102396] BthIsr():-->HCI_RUNNING not set!
[...]
I guess it has something to do with rtbth_core_bluez.c, which is mentioned a lot on sites that try to fix this bug. Oh, and it's the only file that contains references to the aforementioned log.
Another interesting bug:
If you disabble bluetooth, besides it 2on't turn on again, it will spam the system log (you can launch dmesg -wH to view the live output) with a particular line:
[...] ):-->HCI_ RUNNING not set!
[ +0.102396] BthIsr(
[...]
I guess it has something to do with rtbth_core_bluez.c, which is mentioned a lot on sites that try to fix this bug. Oh, and it's the only file that contains references to the aforementioned log.