convert to systemd service / init cleanups

[joolswills]

made a few init script cleanups -

Noticed an issue with it not always starting correctly. Not sure what it is though, and it doesn't seem to be consistent. Shouldn't have had sudo in though, so I removed that. I wonder if we should switch to using systemd natively though.

the /usr/bin/sixad script is a bit of a mess though imho and needs some work (I realise some cleanup has already been done) although ideally we would ditch all of this and just use the native bluetooth stack. I am going to look into if we can maintain a backported updated bluetooth perhaps with raspbian patches.

[joolswills]

This issue is for no-one in particular, feel free to comment. Mostly a heads up for @gizmo98 and a reminder for me that work needs to be done :)

[joolswills]

This method actually works reasonably well - https://www.piborg.org/rpi-ps3-help#setup-jessie and I think I may be able to automate it. Got some code in progress anyway. Only good for original controllers of course.

[gizmo98]

As i can see this is just a combination of sixpair and bluez. I think i had something like this running. The only problem was to add automated permission (trust). Newer bluez versions have builtin sixpair functionality. The ps3 controller tries to connect to the builtin bluetooth if it was connected once over usb. But the trust problem persists. Does the bluetooth connection script add trust to bluetooth devices trying to connect somehow? I have not taken a look.

[joolswills]

Supposedly the Jessie version of bluez should have sixpair functionality build in, but I couldn't get it working (Unless I misunderstood the changelogs I was reading). Work ok on my Ubuntu machine.

The bluetooth connection script doesn't handle that, but I intend to try and automate it. One of the problems is it doesn't seem to be "consistent", but I will see what I can do.

[Dark-Show]

Joolswills, I think the problem with it not always starting is more of a race condition with Bluetooth service starting on boot. If you watch the kernel messages on boot up you can see Bluetooth fails after sixad installation. Maybe look into modifying the bluetooth startup script. It's just a though, after my last init script changes I didn't look much more into it.