Hi, I have installed sailfish os in my fairphone 2 some day ago.
It work fine but now the sound not work.
The pulseaudio daemon does not start at the start of the phone and run csd command in terminal cause to reboot the phone.
I do not know how fix this problem.
Whoa, thanks for the tip on the new camera module availability. Do these need new kernel modules for Sailfish?
I havenāt heard of such issues before, assuming you have the correct android base on the device. When did you buy the phone? Did it have android 6 installed as new? Some of the latest devices might need to wait for the next Sailfish OS release.
The new camera module needs the latest kernel included in Android 6. So to use it you need to wait for my next Sailfish OS release.
4 Likes
I donāt remember that but i have installed sailfish os using an installer created by a user of this forum.
I have used this discussion to have it: SailfishOS on the Fairphone 2 - Images for installation
The fairphone that i bought was secondhand.
2 Likes
@mal do you have any bandwidth to provide blueborne security patch for sailfish fp2? itās kinda scary.
I can include that to the next release, or if people really want it sooner then I can fix it for the current release so kernel could be manually updated via command line.
1 Like
I guess depends on the next release timeframe. If 4-8+ weeks away, perhaps updating the current kernel would make sense.
1 Like
Just in case someone wants to use the double tap to wake - I found a little workaround ā¦
Install @coderus āDisplay Sneek Peak (LPM)ā patch (no mce tools required) and when you now take the device out of your pocket or flip it (when the display has been facing down ā¦) LPM display mode will be enabled and you can wake up the whole OS by double tap ā¦
Itās not the real thing, but at least no button is needed any more 
1 Like
Grmblfx - messed my device up ā¦
After everything has been running smooth now I decided to finally update to 2.1.0.11 (had still 2.1.0.9) everything went through until an error about missing jolla-settings-system-sideloading - retried automatically 9 times then error ā¦
After that the store sent error messages - sure I changed the repos - this was the point where I should have set back the release to 2.1.0.9 ā¦
But I thought Iām clever and just could do a rollback with my twrp backup ā¦
ā¦ unfortunately that ended with an Error 255 and a reboot loop ā¦
So for now Iām going to flash Lineage so I can at least test the new camera modules and wait for the next Sailfish port release with the new kernel ā¦
I have reinstalled sailfish os, I wanted to ask if is normal that when i select āsearch deviceā in the pulley menu in āsettings -> bluetoothā, the phone reboot.
Iām wondering what repos you used since that jolla-settings-system-sideloading package should be used only on 2.1.1.x releases and the patterns for 2.1.0.11 do not contain that. From the 2.1.0.9 version I assume you used devel repos?
That is an quite odd issue. I heard of that issue two days ago but cannot reproduce it.
I can confirm that Emma Smithās latest Fairphone installation for Noob elicits this response using these attributes if any help:
Version Info:
Date: 2017-09-09
Script version: 1.53
Sailfish OS: 2.1.0.11
Fairphone Open: 16.10.0/17.07.6
Changelog:
The cache and system files in the TWRP image āSailfishOS_2.1.0.11_fp2-sibon-16.10.0_csp_v0.1ā have been excluded from the installer, as Sailfish contains files in data and boot partitions only (saves 236 MB).
Has been tested on Windows 7/Ubuntu 16.04 LTS AND Windows 8.1 (thank you, āaspergerguyā).
Layout has been adjusted to prevent wrapping of user input.
1 Like
Not sure if I understood correctly what you wrote. Do you mean with that Noob installation image the bluetooth reboot issue appears?
1 Like
Correct, I had noticed that Bluetooth was enabled right after installing Sailfish image via TWRP but hadnāt looked any further until seeing this post.
Ok, that sounds bad. I will have to check how that image was created because I havenāt heard of anyone else than the users of that image complaining about the issue and I have never observed it myself. I use the the normal instructions described in the wiki page since Iām the one who wrote those. The Noob installation image was created by others and I had nothing to do with that except I gave some hints for improving the script used for the installation. I never tested it myself.
1 Like
I will try and check if this behaviour is elicited in both of the versions that Emma Smith has compiled from ExplITās image as hadnāt noticed it first time around. I had just been ensuring that batch file worked upon Windows 8.1 64-bit and Windows 10 32-bit as hadnāt got Ubuntu available. As ExplIT no longer has FP2 device he was in no position to follow this installation process unfortunately.
1 Like
I have used the script with windows 10