Yeah, BT after resume was f'ed for me too. Solved it by: - upgrading bluez to 5.49: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez - hacking a script that toggles rfkill (un)block <hci0 dev id> on resume

BT applet, at least on Unity (yes, I'm one of those people) seems to be borked in that it can't enable BT after resume. I'm guessing it's because it remembers the wrong BT device ID (which gets incremented after every sleep/resume, at least on my system).