I agree with both of you. I am really happy with my Nexus5 and SailfishOS. And 'Yes', the Bluetooth Fix is very good for battery life.

@dubliner:

I see your 'bluetooth' problem and can confirm it. In some rare cases the script that I wrote after some discussions with Mautz hangs... Sometimes though it is the Bluetooth stack itself that fails, and the problem is not related to the script. You can try to recover bluetooth with the following commands...

Or use a script that you can start with one command, like 'devel-su bt-fix.sh
# In the example bt-fix.sh and bt-sleep-monitor.sh are located in my /home/nemo folder.

Hi everyone,

i am very busy lately so i wasn't able to post here. I found some bugs in my CM13 port.

I didn't had the time to investigate the bluetooth call issue, but i'll look into this next week.

Minimecs bt script isn't working on cm13 port at the moment, because hcitool doesn't show any connections when it is connected to a bt speaker, so it quits the connection after 120 seconds. Minimec could you check this on cm13?

Call volume is not adjustable on cm13, i don't know if it was adjustable on cm12.1, could anyone please give me feddback on this?

The screen freeze bug is still occurs on cm13, like on many other ports, but i found out, that sometimes if a three or four finger touch wasn't enough, a 8 or 9 finger touch will get the UI workin again.

How is battery life on cm12.1 with working suspend mode on cm12.1?

I'm trying to figure out the above issues and going to release the cm13 port, when 2.1 is released, so i can check if OTA is working.

Hopefully i'll find the time to get an sfdroid compatible build released, but i don't have the time to do this at the moment.

And it would be nice, if you could post if you want custom kernels for cm13 and if yes, which features i should include.

Have a nice weekend!

Call volume IS adjustable in CM12! My battery life is not as good as yours, I'm going to try the BT suspend mode tomorrow. But maybe the cause is the use of AlienDalvik.

I'm not sure I understood correctly. But I wanted to tell you when I had the opportunity. Thanks for your porting works and is it possible to have double tap to wake up feature?

There is already a sort of double tap, it turns on the screen with the proximity sensor and then you can unlock it just by tapping

My custom kernel has double tap to wake feature, but since this is not an original feature of the Nexus5 it will cause a massive battery drain.

Better use the fake dt2w with LPM mode.

I've installed the kernel for BT sleep, installed the script with the chmod -x but it doesn't work, I still get 0 in suspend time. What do I have missed?

did you mean chmod +x ? it gives scritp executable permissions. maybe this is an issue

Yes I mean that command, just copied and pasted from the post of Minimec to terminal. Maybe I didn't do it as root

Could someone tell me what commands do I have to run?

Let's debug your issue. First after boot, I would check that you have the 'bluetooth-sleep-kernel' by Mautz installed and running.

The output should be this...
If you don't start the 'bt-sleep-monitor.sh' script in some startup script or systemd service, you have to start it manually. (I pretend that the script is in the /home/nemo folder)

You should now be able to monitor the script and get the suspend stats
To recover borken bluetooth, you can try
If it's just the script that hangs...

Would be cool if others could give it a try too...
Kernel can be downloaded here.
The script can be downloaded here... including all relevant informations...