@cibersheep thanks a lot for that hint. It was not the database path, but the name. I had used some template code with whitespaces ("Sample database", ....) after removing the whitespaces it works now on the phone, too

@unisuperbox
How about an app for bugreporting? It could save your github/gitlsb credentials and automatically file the bug via REST API or whatever. Sorry I`m no experienced web programmer, but the threshold would be lower for people to file bugs. Especially since the UT version. Phone type, etc could be read by the app.
Anything except brick bug or Wifi. + mobile data failure could be reported this way.

@arubislander Bluetooth with mode 'Hands free speaking system' did work on FP2 in stable channel, sadly not with FP3 in dev channel. Would be awesome if someone can make it work.

@lumpology so cool! Thanks for sharing this workflow.

I can relate to your situation, as I am having the same issues with my FP3+. Surely the largest pain is (in this order): Camera slow/unreliable, missing working podcast app, bluetooth connectivity.
Still I will not go back to google because of my concerns with their monopoly and data collection.
Personally, the experience of a free and private phone outweigh the mentioned disadvantages I have.
And considering this project is largely community driven, what a huge achievement. My utmost respect to all os and app developers and supporters to this amazing project.
I will hold out for future improvements.

UT Bug Report App:
Using Github Rest Api it should be possible to make a simple app or big reporting.
App could automatically retrieve phone type and UT OS Built version and channel to submit bug reports to github.
Obviously only works for bugs that dont break UT or internet on the phone.