gapps will be in sfdroid. Android apps are not yet in the sailfish app drawer.
I just updated topic for a simpler path that includes flashing together. It should now go cm12.1=> sailfish => sensorsfix3.zip => sfdroid => gapps => reboot => devel-su usermod -G net_bt_stack -a nemo => reboot

re: libjni_latinimegoogle.so, it doesn't appear in all the gapps packages (such as the one I was testing with), but it still had the issue.

This issue was fixed in upstream CM at some point, since it's present in a snapshot without sfos from around this time. We're looking for the fix.

Edit: pico gapps still bundle in the swype support blobs, so it doesn't fix the issue. I finally properly updated the main topic with better instructions.

I just updated topic for a simpler path that includes flashing together. It should now go cm12.1=> sailfish => sensorsfix3.zip => sfdroid => gapps => reboot => devel-su usermod -G net_bt_stack -a nemo => reboot
I've got followed the sequence above, sfdroid starts, but aosp keyboard have force close, so, I can't write anything.

Same here. I've flashed nano gapps.

Very weird, I tested that method before posting it. Assuming pico or nano gapps were used, try this (no tested solution for the "stock" package):
For new installs, we're rolling our own gapps for now: http://www.mediafire.com/download/kt...oswypelibs.zip

Boot order doesn't matter with this solution (tested three different ways from clean flashes). If you want swype, you'll need to install google keyboard from the play store and use that.

well, now kb works fine, I've installed whatsapp and l'd like to install some other Android apps, is it possible to have something like a shortcut for Android apps so we will can use them in Sailfish?

I did a fresh install without gapps on my second N5. I had no keyboard issues. The stock SFOS camera stopped working after using the sfdroid camera application. I couldn't test BT and WiFi since the hardware is broken on this device. SFOS and sfdroid seems to work much faster on this build. Would the sfdroid release need a fresh install?

Network works and is controlled by sfos (using dbus). No BT functionality on sfdroid.

Thank you for pointing out the camera issue, I tested sfos camera, then aosp (sfdroid) camera, but apparently never went back to test sfos camera afterward. A reboot fixes the sfos camera again, possibly a sfos quit/reopen (can't test right now due to nonfunctional sfdroid testing).

Do you mean a fresh install for gapps? If so, there's no need so long as you use the gapps linked in the topic now. The only time a fresh install is needed for sfdroid support is if the cm12.1 base is the old "SNAPSHOT" build that was linked earlier (tags were mismatched), or cm11.0 base. When 2.0.2 is released, new flashes will be easier however due to the cloud backup/restore support.

Once you're on the new cm12.1 base, reflashes won't be necessary, and you can ota to new sfos versions in the future (since we're on obs now and patternised) .

It's not currently supported. nh1402 has been talking about working on this. For now, you need to open sfdroid to handle switching apps. My current priority is fixing a few intermittent crashes I've run into and reducing out-of-memory instances.

Which reminds me: If android is stuck on the bootanimation after leaving the card open, it crashed and hasn't been started back up correctly. Quit sfdroid, and reopen from the app drawer, then it will boot. Unfortunately if it looped too long, those count as failed boots so art will re-optimize apps. This is a pain, and is one of the reasons my priorities are on stabilizing.

Alo is possible downgrade bootloader from hhz12k to hhz12hb ? I try install cm12.1 base in recovery this package support bootloader hhz12h , thx for guide

Removing the check in the updater script should be enough I would have thought.

Can you please post the line that needs to be removed?