maemo.org - Talk - SailfishOS 2.0 Nexus5 based on CM13 alpha release

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - SailfishOS 2.0 Nexus5 based on CM13 alpha release (https://talk.maemo.org/showthread.php?t=99377)

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Hi everyone,

could anyone with multirom try an OTA update to 2.2.1.18 please? Can't find my Nexus at the moment to try this myself. Please do not upgrade on your working system, i don't know if this update works.

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

@mautz I would but I could not. First error on downloading to cache with the error message that it could not resolve host "repo.merproject.org". ....
I am on sfos 2.1.3.7. Or could I not update from that version to version 2.2.1.18?

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by forb'S (Post 1550012)

Sorry, i had to fix the OBS repo, so maybe it wasn't there when you tried to OTA. Could you try again? Do at your own risk...

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1550010)

Hi mautz.

I took the time and wanted to do the latest upgrades. As I was on 2.1.4.14 (Lapuanjoki), my first step was to upgrade 2.2.0.29 (Mouhijoki), as this is a so called mandatory 'stop release' (described here) This upgrade fails with the following message:

Code:

[root@Sailfish nemo]# version --dup

REFRESHING CACHE AND DOWNLOADING PACKAGES

Resolving: 100%

Error: nothing provides pattern:jolla-sailfish-applications needed by pattern:jolla-configuration-hammerhead-0.0.25-10.30.4.jolla.noarch

Finished transaction (status=2, runtime=63032ms)

I then did a 'version --dup' within 2.1.4.14 and then upgraded to 2.1.4.15. The first update pulled quiet some packages; the upgrade to 2.1.4.15 only the following ones...

Code:

Install (4 packages)

 - jolla-camera-lockscreen;0.4.31.1-10.4.1.jolla;armv7hl;jolla

 - jolla-camera-settings;0.4.31.1-10.4.1.jolla;armv7hl;jolla

 - jolla-camera;0.4.31.1-10.4.1.jolla;armv7hl;jolla

 - sailfish-version;2.1.4-10.3.15.jolla;noarch;jolla

As a 'nice' (WTF!!!) side effect the camera that worked before (at least for photos) now shows the gstreamer testing pattern.

I don't know if it was the .15 upgrade or the updates within 2.1.4.14 that fu..d up the camera. The upgrade package list seem to indicate that it was the .15 upgrade. But I do remember having had problems once doing updates within a current release... on the cm12 port.

I hope that a further working upgrade to 2.2.0.29 (Mouhijoki) solves the problem. ;)

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Sorry, upgrading to 2.2.0.29 couldn't work, since this version was not on my repo.

For updating to 2.2.0.29 adaptation-community-hammerhead must point to

Code:

http://repo.merproject.org/obs/home:/mautz/sailfishos_2.2.0.29/

to update further

Code:

http://repo.merproject.org/obs/home:/mautz:/sfos-latest/sailfishos/

should be used.

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

@minimec Sorry, pattern description in configs has changed in 2.2.0.29...hopefully fixed that.

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1550048)

@minimec Sorry, pattern description in configs has changed in 2.2.0.29...hopefully fixed that.

Unfortunately that did not do the trick. I still get the same error.

Code:

[root@Sailfish nemo]# version --dup

REFRESHING CACHE AND DOWNLOADING PACKAGES

Resolving: 100%

Error: nothing provides pattern:jolla-sailfish-applications needed by pattern:jolla-configuration-hammerhead-0.0.25-10.30.4.jolla.noarch

Finished transaction (status=2, runtime=30342ms)

Here is the output of my enabled repos

Code:

[root@Sailfish nemo]# ssu lr

Enabled repositories (global): 

 - adaptation-community-common ... http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfish_latest_armv7hl/

 - apps                        ... https://releases.jolla.com/jolla-apps/2.2.0.29/armv7hl/

 - hotfixes                    ... https://releases.jolla.com/releases/2.2.0.29/hotfixes/armv7hl/

 - jolla                       ... https://releases.jolla.com/releases/2.2.0.29/jolla/armv7hl/



Enabled repositories (user): 

 - adaptation-community-hammerhead ... http://repo.merproject.org/obs/home:/mautz/sailfishos_2.2.0.29/

 - store                           ... https://store-repository.jolla.com/hammerhead/armv7hl/?version=2.2.0.29

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

@minimec

Sorry again, missed to update the patterns file on OBS. Hopefully the problem is solved now.

I'm going to repair my Nexus 5. This takes way too long if i can't test the changes by myself.

Maybe it is necessary to point the adaptation-community-common repo to

Code:

http://repo.merproject.org/obs/nemo:/devel:/hw:/common/sailfishos_2.1.2.3/

instead to latest when updating to 2.2.0.29.

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Quote:

Originally Posted by mautz (Post 1550109)

@minimec

Sorry again, missed to update the patterns file on OBS. Hopefully the problem is solved now.

Hi mautz.

Ok. This time both upgrades went well. So I am on SailfishOS 2.2.1.18. There are some good and some bad news...

First the good news: The Bluetooth-Sound-Routing-Bug is gone, and my cameras are recognized correctly again as well.

Now the bad news: There is a huge regression on sensors! Using AIDA64, only Magnetometer and the Rotation Sensor are working. That means that Accelerometer, Ambient Light, Compass, Gyroscope, Light Sensor, Orientation Sensor, Proximity Sensor are NOT WORKING.

It is possible that this regression was introduced in 2.2.0.29 already, as this was the first 2.2.x release, but unfortunately I did not test that. I upgraded to 2.2.1.18 right away.

Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release

Note to myself, never update things without reading commits...

@ minimec

Could you please test if creating the following file

Code:

https://git.merproject.org/mer-core/sensorfw/blob/master/config/60-sensors-DEVICE.conf

in /etc/sensorfw/sensord.conf.d/ and set the corresponding sensors to true fixes the sensors problem?