You can set file permissions using git or you could write a script that sets the right permissions.

You know what is interesting. The hadk-faq says to apply these commits
But except the lines in drivers/bluetooth/Kconfig, all the other changes in the following files are already in my kernel:
- drivers/bluetooth/Makefile
- drivers/bluetooth/hci_smd.c
- include/net/bluetooth/hci.h
- include/net/bluetooth/hci_core.h

Thank you.
Maybe later I will come back to this. For now it is easier to remove the /home from sparse.

I know, but it wasn't working for me.

Why don't you set the correct user and group permissions dirctly in the sparse folder?

Because I don't know the correct permissions.

Probably it won't work for me either. Could you let me know how you got that working, please? Thank you.

/home/nemo still belongs to root, that's causing the loop.

When enabling bluetooth, there seems to be an exception in the kernel while loading the firmware.

Have you reversed everything in the bluetooth related files that you changed?

I think in that build something was missing from the kernel.

I have created a new build (wip0.15 available in my signature) and this has everything from hadk-faq 13.3
Plus I set the 'droid-config-fp2-sibon-bluez4' in the config.

If we cannot make the bluetooth working in this build (wip0.15) I will try the other solution bluez5 backport from the hadk-faq.
(Unless you know a reason not to use bluez5. )

I decided to remove the /home from the sparse for this build to avoid permission problems. So this last build installs fine.
I have rebuild the gstreamer and camera too, therefore now both work. This had a knock on effect on the torch which also works.

What I have just spotted: if I turn off the wifi, it turns off but the icon remains blue like when the wifi is on.

Edit: I have spotted that AD doesn't start.

droid-config-fp2-siphon-bluez4 is for the Fairphone2, it would be droid-config-hammerhead-bluez4 for the N5.

And as i said, i never got it working like the HADK says, maybe you need some of the commits regarding bluetooth from RealJohnGalts repo.

EDIT: Yep it is a kernel issue, check these commits:

https://github.com/RealJohnGalt/andr...90b79cb1ffb236
https://github.com/RealJohnGalt/andr...7de2fbffadc5d5
https://github.com/RealJohnGalt/andr...d3582370496904
https://github.com/RealJohnGalt/andr...a3fbf44be74284
https://github.com/RealJohnGalt/andr...7c89d694d9257f
https://github.com/RealJohnGalt/andr...23206340ef8120
https://github.com/RealJohnGalt/andr...b16fd9567bb5b8
https://github.com/RealJohnGalt/andr...0ce135204ea099
https://github.com/RealJohnGalt/andr...1c3db1934a4a35
https://github.com/RealJohnGalt/andr...6c40ede400d9e2
https://github.com/RealJohnGalt/andr...564fc68ec84be0

Compiled my custom kernel, which has these commits and bluetooth is working.

EDIT2: CONFIG_BT_MSM_SLEEP should be y.

EDIT3: When you SSH into your device do you get the nemo@sailfish bash prompt?

Thank you!
It was a good idea flashing your kernel to confirm. We did this at the very beginning when the screen was blank but I forgot to repeat that on newer builds. Thank you.

Yeah, I have been thinking about to try the bluez5 backport but probably it will be easier to apply an already proven working solution.

Therefore what I will do then. I will scrap the current kernel, as maybe there could be left something that I forgot to revert, and download the whole again. (I'll keep my current defconfig of course.)
Then I will apply the change into the fs/proc/base.c and these commits, if they required, above.
Guess with this new solution, I don't need the bluetooth.service in the /lib/system that was suggested by the hadk.

Slowly we get there.

Edit: On your question to ssh, I cannot try that now as I am not at my PC. I will try and report back.

EDIT2: Oh, and forgot to tell that when I planned to apply the backport changes, of course I wanted to use 'droid-config-hammerhead-bluez5' rather than 'droid-config-fp2-siphon-bluez5' from the example. (But the backport idea is dropped anyway. )