I just tried your path and it actually broke things: My bluetooth doesn't work anymore, even after rebooting from Windows.
When I sudo service bluetooth start ; blueman-applet, the applet behaves like the adapter is disabled. When I try to enable it, It does nothing. Retrying another time makes the applet say that the device is active but nothing is possible. With the stock kernel from Ubuntu 15.04, this works when the computer was rebooted from Windows.
Maybe this can help: I found this "reboot from Windows" trick by guessing that the firmware of the chipset might not be (correctly) sent to the chipset (maybe the wrong firmware is sent ? or no firmware is not sent at all? or the way of doing it is wrong?).
In this hypothesis, Windows would correctly send the firmware (or at least correctly initialize the chipset), making the adapter work in Linux after rebooting. I might be completely wrong, I could not verify this hypothesis is right.
I just tried your path and it actually broke things: My bluetooth doesn't work anymore, even after rebooting from Windows.
When I sudo service bluetooth start ; blueman-applet, the applet behaves like the adapter is disabled. When I try to enable it, It does nothing. Retrying another time makes the applet say that the device is active but nothing is possible. With the stock kernel from Ubuntu 15.04, this works when the computer was rebooted from Windows.
Maybe this can help: I found this "reboot from Windows" trick by guessing that the firmware of the chipset might not be (correctly) sent to the chipset (maybe the wrong firmware is sent ? or no firmware is not sent at all? or the way of doing it is wrong?).
In this hypothesis, Windows would correctly send the firmware (or at least correctly initialize the chipset), making the adapter work in Linux after rebooting. I might be completely wrong, I could not verify this hypothesis is right.