Jolla 1 with SailfishOS 2 questions

[avhakola]

@Blumenkraft

Devicelock code is the one you use to unlock your phone during bootup. If you don’t have it set, then IIRC recovery doesn’t ask for it. If you want to be sure, you can reset it in the settings.

Now that I try to remember, I think you are right!

@Blumenkraft

Not to be rude, but just to be sure, are you telling you don’t have your devicelock code, you cannot enter your phone and therefore you are reinstalling the OS?

@Bohdan already said in his latest message that he had restored the defaults from the Settings so I think it is safe to assume he has full access to the OS.

[Bohdan]

I successfully restored my Jolla 1 in recovery mode
Thanks everyone!

The reason why I didn’t want to proceed is this hysterical youtube video.
Of course I understood that nothing wrong should happen as long as I know my password / have no password at all, still I asked the community just in case.

Answering my original question, I found that SFOS 2.2 performs much better than 3.4 (in terms of… um… overall perceptible smoothness. Yes, this is very subjective), so I glad that I can choose.

I also couldn’t activate developer mode on SFOS 2.2 (stuck on “making preparations” screen), so I did a reset again and activated developer mode on SFOS 2.0, then updated the device. It is crucial to have Terminal, considering that old version of Storeman is no longer able to connect to openrepos.net

[olf]

@olf

P.S.: I will try to remember to look up the appropriate Firefox Mobile and F-Droid client apps’ version numbers.

These are the last releases which run on Android 4.1.2 (API level 16):

• F-Droid client app 1.12.1
  _{F-Droid client app 0.102.3 was the last version with the original, clean GUI, but that does not support the “new” index format, hence I gave up using it.}
• Firefox mobile 68.0.2 (later 68.x.y releases should also work)
• Fennec F-Droid (a recompiled Firefox mobile, available at F-Droid) 68.12.0

@Bohdan

It is crucial to have Terminal, considering that old version of Storeman is no longer able to connect to openrepos.net

This is not true, Storeman 0.1.8 from the Storeman-legacy page at OpenRepos works fine (tested on SailfishOS 2.2.1) when the CA certificates are updated and the OpenSSL 1.1.1+1.0.2 combi package is installed.

[Bohdan]

This is not true, Storeman 0.0.18 from the Storeman-legacy page at OpenRepos works fine (tested on SailfishOS 2.2.1) when the CA certificates are updated and the OpenSSL 1.1.1+1.0.2 combi package is installed.

Wow, thank you! I tried Storeman 0.1.8 before (unsuccessfully), but I had no idea I can make it work on SFOS 2.2. Thank you for help!

[Bohdan]

One question left with SFOS 2.2 on Jolla 1 is date&time issue. I believe it’s not connected to updated CA certificates and OpenSSL package that I installed, but hours is out of sync for some reason now. It is 3 hours earlier than it should, so I enter correct date, but when I reboot the clock is reset again.

So I tried to set time as root
date {mmddhhmiyyyy.ss}
and disabled automatic time configuration, but it still go back three hours after reboot. Timezone and date are right, but not hours

[nephros]

Nah I think that’s an ancient and long-standing bug with the timezone sticking to Finland.

IIRC it was a permission issue on some config file.

Edit: this, and
the linked, among other bug reports:

Automatic update - Time and date

REPRODUCIBILITY: 100% BUILD ID = 4.2.0.19 EA HARDWARE: Xperia 10 ii UI LANGUAGE: English REGRESSION: Yes DESCRIPTION: My time zone is ‘Spain, Madrid’, if I then check ‘Automatic update’, the time rolls back 1 hour and ‘Time zone’ shows ‘Finland, Helsinki’ EXPECTED RESULT: Time zone to show the time zone I have set ACTUAL RESULT: As per my description ADDITIONAL INFO Notably, on my Jolla1, this is working correctly under SFOS 3.4.0.24. By setting ‘Automatic update’, my time zone stay…

[Bohdan]

It could be, although I set time manually, not automatically. Besides, I’m in Kyiv, which means that I’m in the same time zone as Helsinki

[olf]

If “[Bug] Time zone changes to Finland, Helsinki when enabling "Automatic update" while no SIM card is inserted - together.jolla.com” did not help you, maybe “Factory reset, several upgrades->3.2.0 : Timezone issues [solution] - together.jolla.com” does?

[Bohdan]

devel-su
cd /etc
rm -v localtime*
ln -sv ../var/lib/timed/localtime localtime

this worked indeed, thank you!

[Bohdan]

Hi @olf, after I did this:

OpenRepos works now, but Camera stopped working.

The UI is launching, but not the image itself. Reinstalling Camera app didn’t help unfortunately. Camera works with android apps though. How can this possibly be fixed?

Update: after doing restore from recovery several times, it seems that system get broken after
zypper up -Dd --repo foo ca-certificates
or
zypper up -Dd ca-certificates
It doesn’t allow me to select only certificates to be updated, prompting update of 30+ packages, after that Camera app get broken. Maybe for SFOS 2.2.0 (stop release for Jolla 1) certificate fixes can’t be applied (you said that tested it with 2.2.1)

[olf]

@Bohdan

It doesn’t allow me to select only certificates to be updated, prompting update of 30+ packages, after that Camera app get broken.
Maybe for SFOS 2.2.0 (stop release for Jolla 1) certificate fixes can’t be applied (you said that tested it with 2.2.1)

“prompting update of 30+ packages” is not good.

Still I see no real reason (but may miss some aspect) not to upgrade to SailfishOS 2.2.1. Why do you prefer SailfishOS 2.2.0?

Presumably using SailfishOS 2.2.1 is the easiest way out (not only for Storeman’s use of OpenRepos, but also for many other internet services and websites), other ways require some slightly advanced use of zypper or pkcon.

[Bohdan]

Well, I would update to 2.2.1 of course if I knew how… In Settings the system only proposes to update to 3.0.0 next. Is there a way I could go 2.2.0 → 2.2.1?

[olf]

Install sfos-upgrade and execute in a terminal session as root user (by devel-su):
sfos-upgrade 2.2.1.18

See also (e.g. where to get the exact version numbers from) https://together.jolla.com/question/187284/release-notes-221-nurmonjoki/#187284-update-version-history or for other SailfishOS releases you want to upgrade to their corresponding release notes.

P.S.: I already pointed to sfos-upgrade.

[nephros]

I’m sure it is mentiined somewhere, but:

After reaching your desired version you should disable the update checker service.

It can have bad side effects.

[Bohdan]

Not mentioned before, what command will do that?
From what I found on old forum I thought it’s impossible to disable SFOS update check

[kan_ibal]

That is not a command. I find setting Checking For Updates to Manual disables updates in effect.

[olf]

@nephros

I’m sure it is mentioned somewhere, but:

After reaching your desired version you should disable the update checker service.

Yes, that is documented here, including workarounds to alleviate the issue: [Bug] /usr/libexec/sailfish-osupdateservice osupdate-check sets ssu re

@kan_ibal

That is not a command. I find setting Checking For Updates to Manual disables updates in effect.

No, IIRC that does not work. IMO it takes one of the workarounds described in aforementioned bug report (rsp. its follow-up posts) to alleviate the bad side-effects of the misbehaving systemd user unit osupdate-check.service.

[Bohdan]

Thank you, I updated to 2.2.1 succesfully and applied update checker service fix. Storeman is working too thanks to your decribed method B3 from here. (on SFOS 2.2.0 method B3 for updating certificates did not work, so update to 2.2.1 indeed helped. Also, on 2.2.0 OpenVPN didn’t work, but on 2.2.1 it works flawlessly)

I also installed OpenSSL 1.1.1 + 1.0.2 from openrepos.

The problem is, in Storeman I can’t install packages that I could before, namely Meecast by vasvlad, and Recorder by osetr. Storeman tells it can’t find libstdc++.so.6(CXXABI_1.3.9) and libc.so.6(glibc_2.28), respectively. Didn’t have this when I installed these packages on 2.2.0…

[olf]

@Bohdan

Storeman tells it can’t find libstdc++.so.6(CXXABI_1.3.9) and libc.so.6(glibc_2.28) , respectively.

This means: This executable file was compiled with Jolla’s Sailfish-SDK for a newer version of SailfishOS than the installed one; the specific version numbers in the error message depend on the SDK version used.

Note that the author of an RPM file can specify which SailfishOS releases it supports, all app store client apps (Jolla Store app, Storeman, SailfishOS:Chum GUI app) automatically select the newest RPM file which still supports the installed SailfishOS release (more precisely: the release which SailfishOS names as installed).

Specifically here an older version of MeeCast was installed on SailfishOS 2.2.0 than the one Storeman downloads and tries to install on 2.2.1. Consequently you can …

1. manually download and install an older version of MeeCast.
2. ask vasvlad or somebody else to recompile the newest version of MeeCast, which advertises itself to be compatible with SailfishOS 2.2.1 with the Sailfish-SDK for SailfishOS 2.2.1. Note that vasvlad is kind, but not very responsive, because he does not own an SailfishOS device any more for years (still he continues to maintain MeeCast!). You better ask at GitHub or both, OpenRepos and GitHub (but cross-link both requests, denoting that they address the same issue).

[Bohdan]

Solved

Ok, I remember I installed Meecast Event View version 1.1-1 on SFOS 2.2.0.

I tried now to manually install .rpm files of all versions that exist on openrepos, from 0.1 to 1.1 – and all failed to install…

Thanks for explanation! Meecast Event View v1.0-4 works, which is all what I wanted