RTFM: https://wiki.merproject.org/wiki/Ada...for_hammerhead

And you're wrong, update through OTA works well.

is there a way to operate the haptic feedback sound on the keyboard? a guide?
Thank you

Hi. Has anybody had trouble with Bluetooth headsets or car system?
On a Nexus 5, tried 1.1.9.28/30 and 2.0.0.10

When I make or receive a call I hear an ugly noise (rain noise) all the time over the voice from the other people. If I play music, everything is just fine. I have it installed with multirom, so I also tried from Android and again everything is working ok. In Firefox Os works fine too.
It also has some problems to connect to the car-system in Sailfish. Sometimes connects sometimes not.


EDIT: Bluetooth headsets and carsystem are unusable...


Anyone can help me on this?

Pablo.

ive tried my xbox wireless headset that has bluetooth and never had any trouble? just had to fiddle about with using phone speaker and headset till it worked.

Hi. Thanks for your reply. You've tried this with a nexus 5 and SailfishOS?

it's so rare, it makes the same noise with a headset and carsystem. I've changed bluetooth connection mode to car system, headset and so on...and still the same.

I'm sure it's not the hardware of my nexus (works excellent with android or firefox os) or the devices (they work ok with other phones).
And the noise is only on my side, so the voice of the caller is too hard to hear because of that.

I think it's the codec that compress the voice when sending it to the device. I'll dig on pulseaudio 6.

Please try to test it with another device if you can, and let me know the results.

Pablo.

yes latest updates,

I've recently smashed my nexus 5 screen, and on replacement, my device worked for a bit then now is complete dead.

so :'(

hi guys

regarding android apps on sailfishos on the Nexus 5:
nh1402 has managed to start some of the android processes which are required for running android apps on his Nexus 5 while sailfishos is running.
Now we have worked on a solution to run surfaceflinger, the process which gives you android video output too. First we have succeeded in running surfaceflinger while lipstick is running, this meant surfaceflinger drew to the screen while lipstick was also drawing (which resulted in funny screen contents) this lead to the idea of pausing lipstick or surfaceflinger and thus we were able to switch between android and sailfishos without much delay, which is kind of a solution but not very convenient. In the last 3 days we managed to patch surfaceflinger such that it does not draw over lipstick and today we have been able to copy the graphic buffers composited by surfaceflinger into a shared memory location, this was very easy thanks to the work thp has done with his harmattandroid project. We are currently working on a renderer app which displays this buffer in a window in sailfishos (based on thp's work). Stay tuned! Unfortunately i don't have an android device which i can test on so i always have to send nh1402 my compiled files and need him to try, thing is nh1402 will be unavailable for some time beginning tomorrow. So if anyone with a little terminal experience wants to do the same with me as nh1402 did while he is unavailable, this would be greatly appreciated, otherwise you will have to wait a while to see the result :P.

this sounds way too gooey :/

TL;DR:
"we can (soon) start android apps in sailfishos" or rather "we can (soon) have a full android installation displayed inside a sailfishos window"


EDIT: instructions http://piratepad.net/FtZYtm4tDY

krnlyng/liar

@liar
so i don't need to stop lipstick before starting surfaceflinger anymore?

i just tried the steps you wrote and get an "Stopped ./surfaceflinger"
on the terminal. is that supposed to happen?

no need to stop lipstick anymore, in fact it has to be running now (for the sfdroid binary to work/display stuff)

thats probably a crash, i put this tutorial together without nh1402 having a look over it first so it might be incomplete

you could try running
strace -fF -o log /system/bin/surfaceflinger
and then paste the resulting log file somewhere

in the meantime i have been working on sharing the buffer handle instead of the whole buffer (but this is probably not going to work as it is implemented now, because i somehow have to share the fds properly) via shared memory although i cannot test it. when i will be able to test depends on when nh1402 returns or when my nexus 4 arrives or when somebody shows up in irc who likes to try

I may, but after a week or more.