@BluesLee: Have the problem with handsfree devices (ins cars) been solved?

Sorry, I am not using Multirom. Has anyone tried this? I'd be very interested to learn about the result.

@m4r0v3r: I haven't been able to quite understand this statement. Could you please be more specific? What did you do and what happened?

Is it possible to upgrade to 2.1.0.11?

I have the same question here...
m4r0v3r, could tell us something more specific about trying to update this version? I don't think it's because of cm12, there are other devices with the last version of Sailfish even on that Android version.

Since this build us unmaintained some packages can't be build at the moment on obs. Updating could brake the system. But maybe someone who uses multirom could try ro update and report back.
But i'm pretty sure that the gui won't work due to the switch to QT5.6.

Repo status can be seen here: https://build.merproject.org/project...ing:hammerhead

I would try, but I couldn't solve any of those problems.
As far as I understand without those packages it's not possible to update, so sad.
The point is that we have two ports for the same device, each with his pros and cons. It would be great if it would be possible to merge the best of them.

i can tell you now if you update it will break. it wonts boot effectively. since it required some middleware to be rebuilt.

I realize this is slightly off topic. Here's the thing. I'm still using the CM12.1 with SailfishOS 2.0.5.6 on the Nexus 5 (mainly because I like the video recording option).

Today the Jolla Store offered me an update to the File Browser which I (foolishly) accepted.

Now, File Browser no longer starts which leaves me a little frustrated.

How can I retrieve the old (functional) version?

Maybe one of those? https://github.com/karip/harbour-file-browser/releases

If none of this version works, just install another file browser from openrepos.

Thank you so much, Mautz!!! I am truly grateful for all your help. If it wasn't for you, my mobile device experience would be quite diminished. Please, please don't ever stop working on SFOS for the Nexus 5.

Sorry for the off topic. But I just needed to get that off my chest. :-)

In the CM13 image there is a script to enable low-power-mode for bluetooth. I did a complete rewrite of that script and it also works in the CM12 base... See: https://talk.maemo.org/showpost.php?...&postcount=310

I use that next generation script on the CM12 base for a long time now with no problems with my car audio system, bt-headphones and a HiFi bt-adapter.

Feel free to report problems...

Source: https://github.com/minimec/bt-sleep-monitor

#How it works... : A dbus-monitor process is listening for different dbus events in parallel:
# - Bluetooth power on/off
# - Bluetooth connections
# - Display events
# When an event is triggered the program will decide whether to enable/disable
# or temporarily disable bluetooth suspend (low power mode).
# If bluetooth is powered and in low power mode, a display event will disable suspend mode for 60 seconds ($BTACTIVE).
# In case there is no bluetooth connection after that time, suspend mode is enabled again.


This is a copy/paste instruction to implement script as systemd service in the CM12 port.