Re: SailfishOS 2.0 on Nexus 5
 

I apologize for the double post, but I believe this deserves another post.

I just massively updated the CM12.1 SFOS piratepad. There's now a section on changing the pixel_ratio (with mer-tools addition), along with a section on OTA updating. I've also edited some of the command formatting to make it easier to copy/paste multiple lines.

Also, big thanks to sledges, mal-, and kimmoli (in no particular order).


A few notes before you proceed (duplicating warnings from piratepad for good reason):

• Nobody other than me has done this yet! Only OTA if you're comfortable potentially breaking your system. If you're comfortable with ssh over usb or wifi, you will probably be able to recover however.
• The second update method is a bit more advanced, and hasn't been well tested. I also don't recommend trying it for updates to SFOS versions (for instance 2.0.0.10 => 2.0.1.11). There have been device updates since the last uploaded 2.0.1.11 release however, and it could end up being a lighter update route for more advanced users.

Device support updates to note:

• We're running on new ofono (radio support) packages, and have updated our device repos accordingly.
• Kernel changes from the test kernel posted earlier have been implemented.
• The device hostname has been changed from "localhost" to "Nexus5"
• We're now using audioflingerglue, which has (strangely) increased some volume output.

There will be a new release (cm121-beta0) uploaded shortly for those wishing to fresh flash, as well as an updated sensorsfix zip (can be flashed over existing installs with prior zip).

This cm12.1 project will be maintained in parallel with cm11 until cm12.1 sfdroid support is in a good spot. This is the reasoning behind having the packages on my home mer obs project. Additionally, the only way to update from cm11 => cm12.1 based SFOS is with a new install. There's no way around it, no matter device.

Re: SailfishOS 2.0 on Nexus 5
 

Super, is multirom supported?

Re: SailfishOS 2.0 on Nexus 5
 

Yes. On line 24 (the first bullet point in "Installation"), there is a recommended twrp recovery to use.

Re: SailfishOS 2.0 on Nexus 5
 

Thanks a lot! This night I want to try it :)

Re: SailfishOS 2.0 on Nexus 5
 

If you're fresh installing cm12.1 based, you might want to wait a day for the "cm121-beta0" build to be uploaded so there's no need (or desire) to OTA it right off the bat :).

Re: SailfishOS 2.0 on Nexus 5
 

Yes I'll do a fresh install so it's better to wait, thank you :)

Re: SailfishOS 2.0 on Nexus 5
 

Got it uploaded and tested a bit sooner than I expected. Piratepad updated ;)

Re: SailfishOS 2.0 on Nexus 5
 

My mistake, sorry.

Re: SailfishOS 2.0 on Nexus 5
 

I've just tried to install Sf on cm12.1, obviously with latest TWRP recovery of multirom, seems it's flashed but now it's stuck on "extracting boot image" of Sailfish, is it a known issue?
I know there is a recommended TWRP version, but I was too curious to try it. :)

EDIT: my fault, everything was rignt flashed and it's working fine, even with latest Multirom TWRP recovery. :)

EDIT2: Well, I've understand why the old TWRP version is recommended, if you use the new, you can't flash the sensor fix. :)
I've found a problem, I haven't any data connection with my sim, the apn is right, but in settings results disabled and in light gray, so I can't switch to enabled.
Wifi works fine.

Re: SailfishOS 2.0 on Nexus 5
 

Hi, Thanks for the great work....:)

I have used this image
sfos 2.0.1.11 https://www.mediafire.com/?cxy0piao5obk172

Is sfos 2.0.1.11 beta0 http://www.mediafire.com/download/82...m121-beta0.zip

different from what I used.

Re: SailfishOS 2.0 on Nexus 5
 

yes, the second one is the latest build

Re: SailfishOS 2.0 on Nexus 5
 

AAAAH! I can't believe I missed this. I felt very good about even tagging this as beta0, and could have sworn I tested mobile data as well. Data will be fixed *very* soon, even with instructions on fixing from that flash. I'm sorry, but I really appreciate letting us know.

In regards to store, either reboot, or run: ssu dr adaptation0, and reboot < will be added to piratepad in the new update.

I've removed the ota instructions from piratepad for now, and have restored the old link. This will be good again very soon, I apologize I missed this.

Edit: this is indeed strange, I could've sworn when I tested the new qofono packages initially, mobile data only failed to work on the first boot. Even reverting a settings workaround, it still fails to work. I might maintain the older packages through OBS for now (supporting a downgrade from the ill-tagged "beta0")

Edit2: there are device changes, that can be implemented through OTA'ing...but please don't yet. I clearly jumped the gun :/.

Edit3: I won't be able to test for ~1 day due to work. If anyone with multirom + required space are able to test this zip to see if mobile data is fixed, it would be much appreciated (ignore the weird zip name) [REMOVED]

Re: SailfishOS 2.0 on Nexus 5
 

i'm downloading now, for tomorrow I'll be able to report if it works :)

EDIT: seems data still doesn't works, same problem as before...

Re: SailfishOS 2.0 on Nexus 5
 

I don't know if can be useful, yesterday I've tried to install Facebook messenger account and skype account from warehouse, but I couldn't because some libraries is missing (telephaty-haze), so someone tried to help me and giving some command from terminal and from ssh, we faced problems with ssu, I have some screenshots, but I don't know how to upload from my phone

Inviato dal mio Sony Z5

Re: SailfishOS 2.0 on Nexus 5
 

Thank you for your testing! Looks like a configs package went missing at some point. Also for what you wanted to accomplish:
ssu dr adaptation0
devel-su
zypper ref
zypper in telepathy-haze

Using the cm11 base and trying to OTA from 1.1.9.28 to 2.0.1.11 is causing the entire mobile data section in settings to disappear. One other person is having this issue, can anyone else test that? Help is appreciated.

Re: SailfishOS 2.0 on Nexus 5
 

When I type zypper ref I got this error:
PackageKit is blocking zypper.
It happens when the update applet is running or another application etc etc
Tell to PackageKit to exit? Etc..

I'm on a new flash.

EDIT: solved stopping PackageKit

Re: SailfishOS 2.0 on Nexus 5
 

I have the same problem after downgrating from .45 version...

Re: SailfishOS 2.0 on Nexus 5
 

Okay, got data working again on the older official jolla qofono. Unfortunately, this means we'll run into issues when updating to 2.0.2.y, but mal- helped narrow it down to 5 commits in qofono where we have the breakage. Hammerhead cm12.1 is the only device that gets broken on the newer ofono, so once we bisect hopefully we can implement a fix.

The good news is, we have ota support for 2.0.1.11 at least.

Edit: if on the newer packages and missing in settings, you need to put these two files in these paths and reboot (remove sparse from paths to get an idea): https://github.com/RealJohnGalt/droi...bbd3f8f0a1fad2

We won't be using these newer packages on the cm12.1 base until we fix additional issues however.

Re: SailfishOS 2.0 on Nexus 5
 

Edit: piratepad updated finally with a new build (with official (older) ofono packages for fixed mobile data), and ota instructions (still slow due to a dbus issue I'm figuring out).

http://piratepad.net/bhP8fbzYgT

Re: SailfishOS 2.0 on Nexus 5
 

Did a clean install under Multirom. Went pretty well. Initial configuration done through my 4G connection. No issue to connect T-Mobile USA.

Tested so far

• Wifi Works
• 4G Works on T-Mobile USA
• Bluetooth pairing worked with PC
• Bluetooth filetransfer worked
• Phone call worked
• Much faster than CM11
• Jolla Store works
• Warehouse works
• Camera - Photo and Video works
• Camera flash seems to work

I could not apply the senorsfix2.zip because I have the TWRP v3.0.0 and it fails to find path to the zip file. It maybe the reason the screen orientation does not seem to rotate when set to auto.

So far it looks very very good guys. Congratulations!!!

And of course -- Thanks for your hard work!!!

Re: SailfishOS 2.0 on Nexus 5
 

Awesome! And thank you :).

If you check the piratepad, there's a recommended twrp version for flashing the sensor fix. This will eventually be turned into a package (rpm) that remounts /system/ and replaces those files, then added to one of our patterns.

Re: SailfishOS 2.0 on Nexus 5
 

Hi TWRP 3.0.0 can flash TWRP 2015.img in the lower right corner of the switch 😉

Re: SailfishOS 2.0 on Nexus 5
 

Flashed older TWRP with fastboot and applied the sensorfix2.zip. The screen rotation seems to be working fine now.

Only issue I see so far is that the Cellular Network settings go back to default every time you reboot. It allows you to edit and save and it keeps the edit until reboot.

Re: SailfishOS 2.0 on Nexus 5
 

blueslee found a major issue with OTA'ing from 2.0.0.10 to 2.0.1.11 using version --dup. I had tested ota'ing from 2.0.0.10 prior to releasing the instructions, but looking back in logs on that install, I had used zypper instead of version :/.

I need to have someone "patternise" the repo on mer obs, so in the mean time I changed the instructions to use zypper dup instead of version --dup.

Edit: If you did this, and have broken wlan or something else, don't run version --dup again. Instead, run zypper dup, and install all available updates.

blueslee, ty again for testing...even if you weren't explicitly testing this time.

Edit2: lbt "patternised" the project, but it hasn't taken effect yet. Waiting to find out when it will. In the mean time, I removed (yet again) the OTA instructions from the piratepad until the obs repo is patternised.

Regarding the cellular settings not sticking, this is a known issue on the older ofono that I'd forgotten about. Thank you.

Edit3: I edited the sailfish wiki for cm11 to no longer recommend OTAs due to the breakage in mobile data on hammerhead on new ofono.

Edit4: I've restructured the subprojects on my mer OBS home project. The packages required for using 2.0.1.11 jolla provided ofono are now in their own subproject, so cm11 users should be able to use them for ota'ing with working mobile data. I have not tested this, and cm12.1 is still my personal priority. If someone wants to and it works, I can re-edit the wiki.

Edit5: hammerhead cm11 wiki page updated to point to that common repo. ThePhxRises on xda confirmed this is a successful ota route for cm11 users, so they're back in business :).

Re: SailfishOS 2.0 on Nexus 5
 

Link https://www.mediafiro.com/?2wtaz444yrl927q does not exist, anyone experience the same problem?

Re: SailfishOS 2.0 on Nexus 5
 

At some point mediafire.com was edited to mediafiro.com, it's been fixed.

Re: SailfishOS 2.0 on Nexus 5
 

Hello, I did update to cm12.1 but when I try to install some applications I get the following dependency error:
dep-resolution-failed, nothing provides libsailfishapp-launcher

where can I get that missing package?

Thanks

Re: SailfishOS 2.0 on Nexus 5
 

Did you refresh the sourceslist ?
e.g. run

Re: SailfishOS 2.0 on Nexus 5
 

Might also need to run "ssu dr adaptation0" prior. I have had a hard time editing piratepad recently. When we get the new repo patternised for OTA support again, I'll add a FAQ.

Regarding the newer ofono issue, GOOD NEWS EVERYONE! After sharing some logs with Monich, he discovered that our RIL doesn't support RIL_REQUEST_ALLOW_DATA. Support was recently implemented in commits targeting multi-sim device data switching, but lack of support isn't a big deal for us.

Within hours, monich provided a fix to test (https://git.merproject.org/slava/ofo...9198e652232b62), and it was successful.

This means we will have full support for 2.0.2.X down the road and a solution to the ofono mobile data breakage has been discovered.

Edit: once we get the new repo patternised for OTA support, I'll also add unsupported instructions and packages for those wishing to test out 2.0.2.45.

Edit2: monich opened a PR for mer ofono https://git.merproject.org/mer-core/...ge_requests/70

Re: SailfishOS 2.0 on Nexus 5
 

Been a few days so double posting:

This is untested on the cm12.1 base at least, but it came up thanks to BluesLee finding another bug. Anyone who has issues with apns not sticking after reboot on the latest build, do: devel-su chown -R radio:radio /var/lib/ofono
Then reboot and try setting and rebooting again.

I'm in the middle of sfdroid stuff right now. krnlyng, nh1402, and I have got cm12.1 sfdroid booting and running (well even). Issues so far: no audio. On switching out of sfdroid and going back, the screen is black...tap screen once or twice and it will come back to android. Probably a lot more.

Re: SailfishOS 2.0 on Nexus 5
 

It looks like it saves the change now.
Thanks!:)

Re: SailfishOS 2.0 on Nexus 5
 

People doing new installs: until a better solution is found (or until the next sfos release when reflashes matter less), please use the cm12.1 build now linked in http://piratepad.net/bhP8fbzYgT . We've hit some issues with snapshots not matching up with cm tagging (for instance YOGP4 tag not matching up with YOGP4**** snapshots).

btw (ignore the lack of signal, not using this device due to dev)
https://i.imgur.com/gYHAGUn.png

Re: SailfishOS 2.0 on Nexus 5
 

I'm already on cm12.1, have I to do something? Upgrade, reinstall or something else?

Inviato dal mio Sony Z5

Re: SailfishOS 2.0 on Nexus 5
 

For now: wait :). If we *absolutely* need to do fresh installs, this won't be a big issue in a future sfos release due to better backup support.

Edit: fixed one crash in cm12.1 sfdroid (was fixed on cm11 sfdroid), and have been trying to get it to crash for awhile now (using android apps mainly), with no luck. Sure still issues (card is always black due to render issue, need to tap on the screen after sfos app switch to display android, and no audio), but no more crashes I've been able to create :D.

Edit2: After many issues attempting to update the piratepad, and users reporting regular downtime, I decided to make a new thread for cm12.1 base and sfdroid testing until sfdroid is stable enough to replace the cm11.0 base.

Re: SailfishOS 2.0 on Nexus 5
 

Today I have been extensively testing my new Hammerhead port of SFOS 2.0.2.48
I managed to finally build a good image with help from the people on #sailfishos-porters.

I am now planning to use this as my daily device, as pretty much most of the stuff I need seems to work well.

Up to now I have found just 3 things that need some attention;

• 1.) GPS is very slow to lock on. The device sees a full constellation of satellites, however it takes almost 10 minutes before position data starts to flow. Really mystifying thing.
• 2.) The voice call quality on my BT headset is poor, really noisy and clipping. Pretty odd as both cutespot and nettiradio output beautiful and clear sound.
• 3.) The Call Recorder by @dpurgin did not work out-of-the-box. Seems I need to look into that a bit deeper.

Re: SailfishOS 2.0 on Nexus 5
 

Isn't this the normal behaviour without A-GPS? It should go faster if you use it more often.

Re: SailfishOS 2.0 on Nexus 5
 

I think it should rather be so, that without A-GPS it does not even see the satellites. In my case it sees a lot of satellites but still gets no position.

Re: SailfishOS 2.0 on Nexus 5
 

No, mautz is right. It takes "up to" 12.5 minutes to get the first lock in the full view of at least 4 satellites. From my experience, I have to add, "in ideal circumstances". It may take well in the region of 20 minutes in real life.

This is about any GPS device. I had the same experience with my N900, my portable car navigation TomTom, a GPS Bluetooth "mouse" or my GPS watch. When you move far (read: more than a few km) from you last position, it may take that long. If you move just a little, the last known position is used as a rough guide and the satellites only to increase the accuracy. Then it takes only a few seconds. A-GPS plays exactly the same role.

Re: SailfishOS 2.0 on Nexus 5
 

Well, if you are right then I am just missing the AGPS parts in my port. Excellent, it makes this a lot easier to start debugging!

BTW, in my general understanding, usually GPS runs by black magic. I remember trying to decipher how it works on N9, and it turnend out to be such a hairball I lost all my hair trying to understand it!