I can confirm moodroids problem: The hotspot does not work.
I also checked everything mentioned in the first post. I can confirm most of it, except Video recording: It actually works

I see this mentioned in the thread, but maybe the post should be updated.

Bluetooth does pair, but does not work otherwise.

Wifi worked after the first reboot

Pin is curious: At first boot I entered it "Wrong Pin",
entered it again "Wrong Pin", pressed cancel and saw that the pin actually worked.
After the third boot it now still displays "Wrong Pin" but closes the pin requester a second later by itself.

And finally I have the 100% battery problem. Its horrible. I have made many reboots and its still stuck at 100%, having the phone shut of at "random" times is very bad. Also it seems like the phone doesn't charge in that state, or does it? I don't know.

Finally: Sailfish is awesome! So much more fluid than the stock rom! I love it.

After about 15 reboots I got the battery working. After about 100 I can say, the chance for my device is about 20% that it works, this really needs to be fixed.

GPS is not working:
I get accurate speed and height, but the location is not accurate. Sometimes its exact to the town (2km), sometimes only to the state. This also seems to be reboot dependent.
The compass is not picked up.

After seeing the bad state of the drivers: Would it maybe be possible to use open source drivers which have been mainlined?http://elektranox.org/droid4/

The keyboard backlight can be manually controlled via /sys/class/leds/keyboard-backlight/brightness. 255 is maximum brightness.

I want to help getting Sailfish fully running on the droid 4, but I have no experience at all in developing for Linux and porting. Only with programming. Feel free to show me where I can contribute.

Further testing results:
After about 15 reboots I got the battery working. After about 100 I can say, the chance for my device is about 20% that it works, this really needs to be fixed.

The way battery level is calculated on Droid 4 is weird compared to newer devices. Basically it depends on closed userspace daemon. I tried to fix it and supposed I've fixed it before (the conditions when it starts and when it fails are pretty uncertain), but going to look again then with newer SailfishOS build.

Originally Posted by Macros

Further testing results:
After seeing the bad state of the drivers: Would it maybe be possible to use open source drivers which have been mainlined?http://elektranox.org/droid4/

The mainlining work for Droid 4 is pretty cool and I'm aware of it, however, the issue is there is no 3D acceleration support, and SailfishOS UI would be painfully useless with software rendering. If any way to port PowerVR kernel driver to mainline and use PowerVR blobs is found, Maemo Leste will benefit from this as well, see for details: https://leste.maemo.org/Motorola_Droid_4/PowerVR

Is there any way to start /system/bin/battd manually?
When I run it, it just exits. Even if we had to manually restart it when the 100% battery problem occurs, it'd still be a major improvement over rebooting several times.
Thanks, as always, to TheKit for making this excellent rom available.

Is there any way to start /system/bin/battd manually?
When I run it, it just exits. Even if we had to manually restart it when the 100% battery problem occurs, it'd still be a major improvement over rebooting several times.
Thanks, as always, to TheKit for making this excellent rom available.

battd, as far as I know, is just middleware for an actual battery read daemon. And again, as far as I know, the issue isn't with battd but rather the actual root battery daemon not sending battery information to battd to show in the actual UI without very specific circumstances that TheKit has had trouble recreating. Again take what I say with a grain of salt, I don't have much experience with OMAP devices and porting because the PowerVR graphics that usually accompany them are a nightmare to work with.

Thanks for the info. I don't know anything about it. I'd just observed that whenever the % was wrong, that /system/bin/battd was no longer running. For me, pretty much whenever I reboot this occurs. Still love this rom though!