maemo.org - Talk - 2.1.1/Jämsänjoki EA

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

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

- - 2.1.1/Jämsänjoki EA (https://talk.maemo.org/showthread.php?t=99643)

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by nieldk (Post 1534830)

Not sure how they get their releases on cBeta.
But the only (highest) version avail on Jolla repos are 2.1.1.26.

In a post on TJC that was somehow visible to everyone (despite of being marked as "only for CBeta"), 2.1.2.2 was mentioned, but as you said, it wasn't available.

Cached version: https://webcache.googleusercontent.c...122-randomly/+

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by pisarz1958 (Post 1534846)

Interesting :)
Thanks for that info, I suppose they even pulled that version completely (at least I can’t find it)

Re: 2.1.1/Jämsänjoki EA

2.1.1 discontinued.

https://blog.jolla.com/sailfish-os-2...-early-access/

Interesting decision. Either resources are low, or the 2.1.2 release is near (or both).

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by jukk (Post 1534899)

Either resources are low, or the 2.1.2 release is near (or both).

Why fix it in 2.1.1, when it's already fixed in 2.1.2? ;)

Re: 2.1.1/Jämsänjoki EA

Update: Version 2.1.2.3 is online (at least by commandline-fu)

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by nieldk (Post 1535654)

Update: Version 2.1.2.3 is online (at least by commandline-fu)

Is there a changelog somewhere? Any news about buggy bluetooth on J1?

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by nieldk (Post 1535654)

Update: Version 2.1.2.3 is online (at least by commandline-fu)

You already got the 2.1.2 ?

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by nieldk (Post 1535654)

Update: Version 2.1.2.3 is online (at least by commandline-fu)

I assume that's what they will launch with on October 11th for the Sony phone image

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by karlos devel (Post 1535658)

You already got the 2.1.2 ?

Yup :)

Attachment 39584

Re: 2.1.1/Jämsänjoki EA

My tablet is still on 2.1.0.11
Will there be more updates for this device?

EDIT: Ok, looks like I need to learn how to read! 2.1.1 was discontinued and have to wait for 2.1.2.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by mscion (Post 1535662)

My tablet is still on 2.1.0.11
Will there be more updates for this device?

2.1.1 was never officially released. If you have early access or if you update from command line, you can update to 2.1.1 (unless it was completely withdrawn?) and now also to 2.1.2.3. My tablet is on 2.1.1 because I updated from command line (it is nagging about updating(!) to 2.1.0, though).

Jolla tablet is still supported, because in 2.1.2.3 Release Notes it says:

Quote:

Aliendalvik

Updated Android Support of Jolla Tablet and Jolla C to version 1.0.69-1 (no update for Jolla1)

Re: 2.1.1/Jämsänjoki EA

afaik, the only devices to be cautious with updates from cli are Aquafish and *oh yeah i finally forgot the name* *wait, no* Turing Phone(s).
Updating Tablet, J1 and C at the moment but download is (temporarily?) slooow

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by pichlo (Post 1535660)

Yup :)

Attachment 39584

do you have patch manager installed?

what patches work ?

Re: 2.1.1/Jämsänjoki EA

holy camoly, could please someone confirm massive improvement in gesture reception and overall speed on jolla c.
Or is it clean update and reboot effect only on my end?
I am so flashed, i drove aside on my way to frankfurt just to express my surprise with this update. Also drop box backup works again for me.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by kibet85 (Post 1535670)

do you have patch manager installed?
what patches work ?

Note there is another condition too for 2.1.2/2.1.1:
https://together.jolla.com/question/...-kiiminkijoki/
....
If you have Call Recorder from Openrepos installed, uninstall it before the upgrade.
...

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by hhbbap (Post 1535690)

Th Call Recorder is always to be uninstalled. This is mentioned in every update.

EDIT: Thx for the link. This answers my question earlier on. And not to best best it seems :(

Quote:

bluetooth pairing may fail with some car models especially in case of Jolla C devices. Sometimes synchronizing the phonebook may fail, too.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by kibet85 (Post 1535670)

do you have patch manager installed?

what patches work ?

For me all patches that have been working on 2.1.1.11 and 2.1.1.26 are still working on 2.1.2.3 - that includes Old button styles, Launcher combined, maze lock, enhanced power menu, voicecall combined, conversation background and more ...

Only thing that doesn’t work for me is meecast event view (as they changed the native event view) but that’s not a patch though
Edit: uninstalling the native weather app and restarting homescreen brings back the meecast eventsview - so for now it’s not possible to have them both intalled ....

Everything else seems smooth so far (but I haven’t had any problems with the 2.1.1.26 either)

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by mosen (Post 1535666)

Just on this has anyone tried to update a Turing phone to 2.1.2.3? 2.1.1 killed it and caused an infinite boot loop.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by kibet85 (Post 1535670)

do you have patch manager installed?
what patches work ?

Yes, I do. I do not have the phone with me today so cannot tell you exactly which patches work and which don't but, as elastic said,

Quote:

Originally Posted by elastic (Post 1535698)

For me all patches that have been working on 2.1.1.11 and 2.1.1.26 are still working on 2.1.2.3

Which is to say, not many. I used to have about 15 to 20 patches before 2.1.1.x, but only about 5 or 6 after. The ones that definitely did not work were mazelock, return old menu style and all those that can adjust the remorse timers, but I did not spend much time chasing them, so please forgive me if there are updates available.

Quote:

Originally Posted by hhbbap (Post 1535690)

If you have Call Recorder from Openrepos installed, uninstall it before the upgrade.

I do have Call Recorder and I did not uninstall it before the update. Nothing visibly broke (as in, the phone did not refuse to boot up or anything dramatic like that), but I do not currently have a SIM in that phone so I could not check the recording still works.

Should Kiimikijoki discussions go to a new thread?

Re: 2.1.1/Jämsänjoki EA

Hi,

Here is my problem when i try to install the new update on my Jolla C.

How to resolve that?

EDIT: SMS BOMB in settings app need to be uninstalled before install new update.
Now it works :)

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by mosen (Post 1535673)

holy camoly, could please someone confirm massive improvement in gesture reception and overall speed on jolla c.

I can confirm that on Jolla 1 and Jolla C as well.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by atlochowski (Post 1535717)

I can confirm that on Jolla 1 and Jolla C as well.

to the extend that i feel a little bad for my quadruple tab rant a month ago. It works like a charm now with double tap regardless the tap speed or applied pressure or wideness of finger on the surface.

The trade off seems to be larger apps being killed more often by oom again. At least android navigations get killed rather quick when switching away from them.
Prove to me that it was a sad circumstance to have only 1Gb on j1. 3GB on Xperia X might be what they are optimizing for good now?

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by mosen (Post 1535719)

t
Prove to me that it was a sad circumstance to have only 1Gb on j1. 3GB on Xperia X might be what they are optimizing for good now?

I don't know. J1 is my daily driver and I don't use android apps. I'm happy for its performance.
I can compare j1 to to jolla C and second one is a little bit faster but not so much.
The only app I have problem with is default webrowser. The problem exists on both phones.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by n950 (Post 1535716)

Hi,

Here is my problem when i try to install the new update on my Jolla C.

How to resolve that?

EDIT: SMS BOMB in settings app need to be uninstalled before install new update.
Now it works :)

I guess the same here, cannot be installed, try again later. Wtf.. J1 with 1.1.26. Any ideas?

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by wrm (Post 1535730)

I guess the same here, cannot be installed, try again later. Wtf.. J1 with 1.1.26. Any ideas?

check /var/log/systemupdate.log

If you don't find anything wrong in this logs you can try to update this way. it usually works for me:

Code:

devel-su               ## Use your SSH password here

ssu release 2.1.2.3   ## The next STOP RELEASE (*) or the latest OS release

version --dup

Re: 2.1.1/Jämsänjoki EA

Jolla tablet works fine with 2.1.2.3.

Re: 2.1.1/Jämsänjoki EA

So my Jolla 1 went to bootloop after trying to update.
How can I try again in recovery mode?

"ssu release 2.1.2.3" just gives error:
ssu: error while loading shared libraries: libsystemd-journal.so.0: cannot open shared object file: No such file or directory

Do I need to mount something?

Edit: Trying to reset. First reset in almost 4 years.
Edit2: Didint because it says it will also reset userdata and not only apps.
Edit3: Maybe I have to take my Xperia X out of the box if I am able to fix Jolla later.
Edit4: After tapping no to about 5000 popups telling me to improve software and add accounts I have Xperia running. If anyone got any ideas how to fix my Jolla I will try. If not I have do bit backups and do factory reset.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by atlochowski (Post 1535731)

check /var/log/systemupdate.log

If you don't find anything wrong in this logs you can try to update this way. it usually works for me:

Code:

devel-su               ## Use your SSH password here

ssu release 2.1.2.3   ## The next STOP RELEASE (*) or the latest OS release

version --dup

Homescreen restarted during update, somewhere around 90%, so i just waited for another 10 minutes and rebooted. Now it says up to date, so guess ir worked..

Re: 2.1.1/Jämsänjoki EA

Am I in beetween updates or what? :confused:
This is what I get if I try reinstall lipstick-qt5 from recovery. Downgrade didint work.

Code:

 Warning: Disabling repository 'store' because of the above error.

Loading repository data...

Reading installed packages...

Forcing installation of 'lipstick-qt5-0.30.4-1.81.4.armv7hl' from repository 'jolla'.

Resolving package dependencies...



Problem: lipstick-qt5-0.30.4-1.81.4.armv7hl requires libsystemd-daemon.so.0, but this requirement cannot be provided

  uninstallable providers: systemd-libs-208-1.12.3.armv7hl[jolla]

 Solution 1: Following actions will be done:

  downgrade of systemd-libs-225+git5-1.15.1.armv7hl to systemd-libs-208-1.12.3.armv7hl

  downgrade of dbus-1.10.8+git1-1.10.4.armv7hl to dbus-1.10.8+git1-1.10.2.armv7hl

  downgrade of dbus-libs-1.10.8+git1-1.10.4.armv7hl to dbus-libs-1.10.8+git1-1.10.2.armv7hl

  downgrade of mapplauncherd-4.1.25-1.17.1.armv7hl to mapplauncherd-4.1.23-1.15.3.armv7hl

  downgrade of pulseaudio-8.0+git12-1.24.1.armv7hl to pulseaudio-8.0+git5-1.21.2.armv7hl

  downgrade of qt5-qtcore-5.6.2+git16-1.35.1.armv7hl to qt5-qtcore-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of timed-qt5-3.4-1.21.2.armv7hl to timed-qt5-3.3-1.20.3.armv7hl

  downgrade of qt5-plugin-imageformat-jpeg-5.6.2+git16-1.35.1.armv7hl to qt5-plugin-imageformat-jpeg-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-plugin-sqldriver-sqlite-5.6.2+git16-1.35.1.armv7hl to qt5-plugin-sqldriver-sqlite-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtdbus-5.6.2+git16-1.35.1.armv7hl to qt5-qtdbus-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtgui-5.6.2+git16-1.35.1.armv7hl to qt5-qtgui-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtnetwork-5.6.2+git16-1.35.1.armv7hl to qt5-qtnetwork-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtopengl-5.6.2+git16-1.35.1.armv7hl to qt5-qtopengl-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtprintsupport-5.6.2+git16-1.35.1.armv7hl to qt5-qtprintsupport-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtsql-5.6.2+git16-1.35.1.armv7hl to qt5-qtsql-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtwidgets-5.6.2+git16-1.35.1.armv7hl to qt5-qtwidgets-5.6.2+git12.1-1.34.1.armv7hl

  downgrade of qt5-qtxml-5.6.2+git16-1.35.1.armv7hl to qt5-qtxml-5.6.2+git12.1-1.34.1.armv7hl

 Solution 2: do not install lipstick-qt5-0.30.4-1.81.4.armv7hl

 Solution 3: break lipstick-qt5-0.30.4-1.81.4.armv7hl by ignoring some of its dependencies



Choose from above solutions by number or cancel [1/2/3/c] (c):

Any suggestions?

Should I try zypper dub? It would downgrade lot of packages (if it works).

Code:

Warning: Disabling repository 'store' because of the above error.

Loading repository data...

Reading installed packages...

Computing distribution upgrade...



The following NEW pattern is going to be installed:

  jolla-mw 



The following packages are going to be REMOVED:

  libgsupplicant upower 



The following packages are going to be upgraded:

  bluez-libs busybox busybox-symlinks-dhcp busybox-symlinks-gzip feature-alien feature-eas feature-xt9 jolla-recovery-sbj kmod-mysatroker-sbj libpython3_4m1_0 

  libtrace lsof python3-base sbj-version sbj-wlan statefs-provider-qt5 telepathy-gabble 



The following packages are going to be downgraded:

  SDL2 all-translations-pack alsa-lib archivemount as-daemon-all-translations-pack attr augeas-libs bash boost-filesystem boost-system btrfs-progs bzip2 bzip2-libs 

  cairo cor coreutils curl db4 db4-utils dbus dbus-glib dbus-libs dbus-python dconf deltarpm desktop-file-utils device-mapper device-mapper-event 

  device-mapper-event-libs device-mapper-libs diffutils droid-system-packager droid-system-sbj droid-system-sbj-users droid-tools droidmedia e2fsprogs e2fsprogs-libs 

  elfutils-libelf exempi expat farstream file file-libs findutils flac flash-partition fontconfig fuse fuse-libs gawk gdb-gdbserver gdbm geoclue giflib glib2 glibc 

  glibc-common gnupg2 grep groff gstreamer1.0 gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good harfbuzz hunspell hwdata info iproute 

  iptables iputils iw jolla-alarm-ui-all-translations jolla-alarm-ui-all-translations-pack jolla-calculator-all-translations jolla-calculator-all-translations-pack 

  jolla-calendar-all-translations jolla-calendar-all-translations-pack jolla-clock-all-translations jolla-clock-all-translations-pack jolla-developer-mode-profile 

  jolla-email-all-translations-pack jolla-gallery-extensions-ts jolla-mediaplayer-all-translations jolla-mediaplayer-all-translations-pack 

  jolla-settings-system-about-avc jolla-settings-system-about-icasa-jollaphone jolla-settings-system-about-mp3 jolla-settings-system-about-mp4 

  jolla-settings-system-about-product-license-jolla kbd kernel-adaptation-sbj kmod kmod-libs libaccounts-glib libaccounts-glib-tools libacl libarchive libattr libav 

  libblkid libcap libcom_err libcommhistory-qt5 libcontacts-qt5 libcurl libdbus-qeventloop-qt5 libdbuslogserver-dbus libdres libdsme libenca libenca-libenca0 libfdisk 

  libffi libgcc libgcrypt libglibutil libgofono libgofonoext libgpg-error libgrilio libgrilo libgsf libhybris-sbj libhybris-sbj-libEGL libhybris-sbj-libGLESv2 

  libhybris-sbj-libhardware libhybris-sbj-libnfc libhybris-sbj-libwayland-egl libicu52 libiodata-qt5 libiphb libiptcdata libjpeg-turbo libkeepalive-glib 

  libkeepalive-glib-tools liblua libmce-glib libmlocale-qt5 libmount libngf-qt5 libngf-qt5-declarative libnice libnl libpcap libpng libqapk libqofono-qt5 libqtaround2 

  libqtwebkit5 libqtwebkit5-widgets libresource libresourceqt-qt5 libsailfishapp libsailfishkeyprovider libsbc libsmartcols libsndfile libsolv-tools libsolv0 libss 

  libstdc++ libtasn1 libtiff libuser libutempter libuuid libwbxml2 libxml2 libxslt lsb-release lua lvm2 lvm2-libs make mapplauncherd mapplauncherd-privileges-jolla 

  mapplauncherd-qt5 mlite-qt5 mobile-broadband-provider-info mtdev mtp-vendor-configuration-sailfish nano ncurses ncurses-base ncurses-libs 

  nemo-gstreamer1.0-interfaces nemo-qml-plugin-configuration-qt5 nemo-qml-plugin-dbus-qt5 nemo-qml-plugin-models-qt5 nemo-qml-plugin-notifications-qt5 

  nemo-qml-plugin-thumbnailer-qt5 net-tools ngfd ngfd-settings-sailfish nspr nss nss-softokn-freebl nss-sysinit obexd-calldata-provider oneshot openconnect openobex 

  openssl openssl-libs openvpn orc p11-kit p11-kit-nss-ckbi p11-kit-trust pacrunner pam pango passwd patch pcre perl perl-Filter perl-Module-Pluggable 

  perl-Pod-Escapes perl-Pod-Parser perl-Pod-Perldoc perl-Pod-Simple perl-Scalar-List-Utils perl-Socket perl-libs perl-macros perl-parent perl-threads 

  perl-threads-shared pkgconfig policy-settings-common poppler poppler-glib popt prelink procps profiled psmisc pulseaudio python python-libs 

  qmf-notifications-plugin-all-translations-pack qt5-plugin-imageformat-jpeg qt5-plugin-sqldriver-sqlite qt5-qtconcurrent qt5-qtcore qt5-qtdbus qt5-qtdeclarative 

  qt5-qtdeclarative-import-multimedia qt5-qtdeclarative-import-qtquick2plugin qt5-qtdeclarative-import-window2 qt5-qtdeclarative-qtquick 

  qt5-qtdeclarative-qtquickparticles qt5-qtdeclarative-qtquicktest qt5-qtgui qt5-qtmultimedia qt5-qtmultimedia-gsttools qt5-qtmultimedia-plugin-audio-pulseaudio 

  qt5-qtmultimedia-plugin-mediaservice-gstmediaplayer qt5-qtnetwork qt5-qtopengl qt5-qtprintsupport qt5-qtqml-import-webkitplugin 

  qt5-qtqml-import-webkitplugin-experimental qt5-qtsensors qt5-qtsql qt5-qttest qt5-qtwayland-wayland_egl qt5-qtwebkit-uiprocess-launcher qt5-qtwidgets qt5-qtxml 

  qt5-qtxmlpatterns qtaround-dbus qtcontacts-sqlite-qt5 rpm rpm-libs rsync sailfish-content-apps-default-configs sailfish-content-graphics-closed 

  sailfish-content-graphics-closed-z1.0 sailfish-content-graphics-default-base sailfish-content-graphics-default-z1.0-base sailfish-maps-all-translations 

  sailfish-maps-all-translations-pack sailfish-office-all-translations sailfish-office-all-translations-pack sailfish-silica-background-qt5 sailfish-tutorial-data 

  sailfishsilica-qt5 sbj-platform-images screen sed setup shadow-utils shared-mime-info speex sqlite statefs statefs-contextkit-subscriber statefs-pp statefs-qt5 

  swi-prolog swi-prolog-library-core swi-prolog-runtime-lib systemd systemd-config-sailfish systemd-libs tar tcl telepathy-farstream telepathy-glib 

  telepathy-mission-control time timed-qt5 tzdata tzdata-timed unzip usb-moded-connection-sharing-android-config util-linux vim-minimal vmtouch vpnc wayland 

  wireless-regdb xdg-user-dirs xz xz-libs zlib 



The following packages are going to be reinstalled:

  calligra-data calligra-sheets-core-plugins recode 



17 packages to upgrade, 330 to downgrade, 3 to reinstall, 2 to remove.

Overall download size: 193.5 MiB. After the operation, 6.9 MiB will be freed.

Continue? [y/n/?] (y):

Seems like these were just network problems. So first I need to get internet working. I used this as guide before: https://together.jolla.com/question/...#post-id-45710

Re: 2.1.1/Jämsänjoki EA

I just checked the corrected CVE's from the Kiiminkijoki release notes and it seems that CVE-2017-14315 blueborne is not fixed yet :(

https://cve.mitre.org/cgi-bin/cvenam...CVE-2017-14315
https://www.armis.com/blueborne

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by n950 (Post 1535716)

Hi,

Here is my problem when i try to install the new update on my Jolla C.

How to resolve that?

EDIT: SMS BOMB in settings app need to be uninstalled before install new update.
Now it works :)

Hmmm, don't know why you decided that related to Bomb sms, I updated both my Jolla (1/C) with this app installed... For me it also not worked from first time, but from attempt 2 or 3 update installed without any problem...

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by Mikkosssss (Post 1535747)

So my Jolla 1 went to bootloop after trying to update.
How can I try again in recovery mode?
{...}
If anyone got any ideas how to fix my Jolla I will try. If not I have do bit backups and do factory reset.

For the recovery mode, the procedure would be something along the lines of :
- mount the root (subvolume "@") on /mnt/
- mount the home (subvolume "@home") on /mnt/home/
- bind-mount the few software defined directory (like /proc /sys /dev) into /mnt/home
- mount the few other blocks

chroot into /mnt/
and try restarting the update and/or checking with zypper/pkgcon if there aren't other problems (packages conflicts).

For reference, mounts currently effective on my 2.1.1-running Jolla 1 :

Code:

/dev/mmcblk0p28 on / type btrfs (rw,noatime,ssd,noacl,space_cache,autodefrag)

devtmpfs on /dev type devtmpfs (rw,relatime,size=412956k,nr_inodes=103239,mode=755)

none on /proc type proc (rw,relatime)

none on /sys type sysfs (rw,relatime)

tmpfs on /dev/shm type tmpfs (rw,relatime)

devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)

tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)

tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)

cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)

cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)

cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)

cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)

cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug)

cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)

cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)

cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)

cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)

fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)

tmpfs on /tmp type tmpfs (rw)

debugfs on /sys/kernel/debug type debugfs (rw,relatime)

mtp on /dev/mtp type functionfs (rw,relatime)

/dev/mmcblk0p9 on /var/systemlog type ext4 (rw,nosuid,nodev,relatime,data=ordered)

/dev/mmcblk0p28 on /home type btrfs (rw,noatime,ssd,noacl,space_cache,autodefrag)

/dev/mmcblk0p25 on /persist type ext4 (ro,nosuid,nodev,relatime,data=ordered)

/dev/mmcblk0p18 on /firmware type vfat (ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)

/dev/mmcblk0p19 on /drm type ext4 (rw,nosuid,nodev,relatime,data=ordered)

tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)

tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)

statefs on /run/state type fuse.statefs (rw,nosuid,nodev,relatime,user_id=0,group_id=998,default_permissions,allow_other)

tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)

tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)

tmpfs on /run/user/100000 type tmpfs (rw,nosuid,nodev,relatime,size=82872k,mode=700,uid=100000,gid=100000)

/dev/mmcblk0p28 on /opt/alien/usr type btrfs (rw,noatime,ssd,noacl,space_cache,autodefrag)

statefs on /run/user/100000/state type fuse.statefs (rw,nosuid,nodev,relatime,user_id=100000,group_id=100000,default_permissions,allow_other)

Otherwise, yeah, if that doesn't work, I suspect you'll be needing to backup / factory reset / upgrade / restore

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by jukk (Post 1535663)

Just to debunk some myths:

SFOS 2.1.1.26 was available as an official OS update for a few days. I am not an Early Access subscriber and received it this way on my two sbj1.
And it is not "completely pulled", as that would cause havoc for those having SFOS 2.1.1 installed, when installing additional packages from Jolla's repos.
So it sounds to me that something went slightly wrong with your CLI update to 2.1.1 (device "is nagging about updating(!) to 2.1.0").

WRT Jolla's advice to uninstall Call Recorder before any SFOS upgrade:
IMO it does not have to be uninstalled (as it is not replacing SFOS RPMs), but one has to ensure that its service is not running when upgrading, otherwise your device will likely be screwed. So this is a dangerous route (forgetting to will probably lead you to a Factory Reset), thus it is well understandable that Jolla simply advises to uninstall it before upgrading.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by DrYak (Post 1535853)

I got to that if you look at my another message but I think I failed at setting up internet.
Ping didint work but zypper seems to have some data about package versions? And it shows that many packages wont match the system version if I understand correctly.
If anyone wants to help me I can come to #jollamobile IRC.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by olf (Post 1535858)

IMO it does not have to be uninstalled (as it is not replacing SFOS RPMs), but one has to ensure that its service is not running when upgrading, otherwise your device will likely be screwed. So this is a dangerous route (forgetting to will probably lead you to a Factory Reset), thus it is well understandable that Jolla simply advises to uninstall it before upgrading.

From my systemupdate.log

Code:

....

Oct 03 19:15:55 Sailfish systemd[905]: Stopping User session.

Oct 03 19:15:55 Sailfish systemd[905]: Stopped target User session.

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Call Recorder Daemon...

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Telepathy mission control daemon...

Oct 03 19:15:55 Sailfish systemd[905]: Stopping PulseAudio...

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Non-Graphic Feedback Daemon...

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Ambience daemon...

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Voicecall manager...

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Generic application launch booster...

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Application launch booster for Sailfish Browser...

....

Re: 2.1.1/Jämsänjoki EA

Anecdata: I had call recorder installed (and presumably running) when I did one of the recent updates (maybe 2.1.1 early access?) on a Jolla 1 because I didn't check the release notes, and they'd only recently added it.

No apparent ill effects. Not taking any chances though, and removed it for 2.1.2.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by Mikkosssss (Post 1535872)

From my systemupdate.log

Code:

....

Oct 03 19:15:55 Sailfish systemd[905]: Stopping Call Recorder Daemon...

....

Thanks @Mikkosssss for pointing this out. But now I understand even less, what the issue with Call Recorder while upgrading SFOS is.
NB: I also had it still installed while upgrading to 2.1.0.11 and 2.1.1.26 and apparently nothing bad happened, but we all may not look for negative effects at the right places, as AFAIK nobody has provided a comprehensive explanation for the advice to uninstall Call Recorder before upgrading SFOS, yet.

Re: 2.1.1/Jämsänjoki EA

Wasn't there an issue with call recorder breaking a previous update? I'd say Jolla couldn't figured out what exactly caused the issue and how to fix this, so they add this advice for all future updates just to be save...

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by jenix (Post 1535920)

Wasn't there an issue with call recorder breaking a previous update?

Not just Call Recorder, any daemon. In my case it was TOHOLED. The workaround was booting with TOHOLED removed and putting it back on only after the UI started.

Re: 2.1.1/Jämsänjoki EA

Quote:

Originally Posted by pichlo (Post 1535923)

Not just Call Recorder, any daemon. [...]

Well we're running in circles now: As @Mikkosssss already pointed out by quoting update.log, all systemd services are stopped before an SFOS upgrade is installed.
So that explanation is too simple; maybe @jenix's guess is closer to the real reason for Jolla's advice (i.e. they also do not fully understand what is going on, but simply want to avoid failing SFOS upgrades).