[Release notes] Struven ketju 4.5.0.19

Thanks! What a nice surprise to get fixes to Xperia 10 III suddenly
:partying_face:

2 Likes

Update doesn’t start at all on my Xperia 10 III. I did download it once but only triggered the installation one or two days later.
After rebooting, the phone immediately reported that the update cannot be processed and there was a restart button flickering in the lower third of the display. With that, the current 4.5.0.16 installation came up again flawlessly.
So I just thought, to download the update again. However, that doesn’t work now:
It is detected, that 4.5.0.19 is available but when I want to trigger the download via the pulley menu, it says ‘waiting for connection’ and that’s it.
It stops waiting after a minute or so and then nothing happens. I can only check for updates using the other pulley menu option (which seems to work, since the timestamp of the notification below changes to ‘just now’), but that doesn’t help with the download at all.
Internet connection is fine as you can see this post, which has been created right after a new download attempt.
Any suggestions?

1 Like

Try:

  1. See If it keeps failing section and do the: Cleaning up section
  2. Try the update again, if it fails do the clean up section again.
  3. If step 3 is successfull do the: Final clean up
1 Like

Have Xperia 10 II Dual SIM XQ-AU52 running 4.5.0.18.

When repeatedly checking for SFOS updates today, I steadily just get the message that the phone is updated.

1 Like

Have I misunderstood – that the 4.5.0.19 rather doesn’t apply to Xperia I0 II’s but only applies to 10 III’s?

  • or why does my phone now still report that it is updated when it is running the .18 version?
1 Like

Yes, the update is also for the 10II and other devices.
See
https://shop.jolla.com/downloads/

Search on the forum for command line update.
Perhaps you can find some way to get more info on what is going on with yours.

Also:

https://openrepos.net/content/olf/sfos-upgrade

1 Like

Updated from 4.4 a couple of days ago. Installation didn’t complete – left it 20 mins and rebooted.

MobaXterm’s SFTP no longer works properly. All files uploaded have 0 bytes. Downloading works. I updated MobaXterm, no joy. This is my main way to transfer files (and do terminal stuff) due to lack of our own Windows tool.

Tried FileZilla on port 21 – doesn’t evern find the phone, which is an XA2 single SIM.

1 Like

Enable SSH in Developer settings, and use the login with port 22 in Filezilla.

1 Like

I won’t work. You have to use Site Manager (Ctr+S) and set Protocol as SFTP. Set Host only, Port field leave empty.

1 Like

On trying to install ‘Textractor’ from Storeman, it didn’t install (eternal spinning wheel) and reported:

Nichts stellt ‘tesseract-language >= 3.02’ bereit, welches von the to be installed tesseract-ocr.3.05.00-1-164.1.aarch64 benötigt wird

(really this denglish words)
What can I do? SFOS 4.5.0.19 / Volla

edit: tried to install tesseract manually, got this error msg:

[root@VollaPhone defaultuser]# pkcon install tesseract-ocr
Auflösen                                                                                                                                   
Änderungen werden getestet                                                                                                                 
Fertig                                                                                                                                     
Schwerwiegender Fehler: nichts stellt 'tesseract-language >= 3.02' bereit, das vom zu installierenden tesseract-ocr-3.05.00-1.164.1.aarch64 benötigt wird
[root@VollaPhone defaultuser]# 

edit: got help by private mail…
pkcon install harbour-textractor command did work. Problem solved, many thanks!

1 Like

Thanks – I figured it out. The ‘dd’ backup filled up my SD card without reporting an error and MobaXterm & FileZilla didn’t detect that either. I only found out by trying to edit the file with nano. :upside_down_face:

@kan_ibal Using port 22 seems to automatically set SFTP in Filezilla, by the way.

1 Like

I seem to have considerably increased battery consumption on my Xperia XA2 after this update. Otherwise it’s working fine. Previously I did not have any issues with the battery draining to 0% overnight, now it has happened multiple times and I am finding I need to charge it during the day also if I use it at all.

2 Likes

when the battery is going down fast or the phone is getting hot, if you check top in a terminal, do you find the process sdcard or android.providers.media.module running with high cpu?

for me, SFOS4.5 aliendalvik uses enormous cpu forever in those two procs (and SFOS4.4 does not)

i have to stop android service whenever i put my phone down or it will be dead in four hours

edit: this is still a constant issue after a full week. it is not an initial media scan, which always happens when installing or reinstalling aliendalvik, and takes about 5minutes for me in SFOS4.4

1 Like

No problems with App Support on my XA2 – an extra 5% drain at most overnight, same as 4.4.

1 Like

Hi, this is my feedback about the release - It is my first time with Sailfish OS

Installation:

I followed the standard installation procedure but the initial phone conditions were not completely matched: Andorid 12 instead of Android 11 and possibly something other like BSP/driver?

System:

  • Xperia X10 II dual SIM, model XQ-AU52 originally with Andorid 12
  • Sailfish OS Jolla-4.5.0.19 qau52-1.0.0.19
  • AOSP Android 10.0 kernel 4.14 seine
  • Free license

Defects:

  • critical : no SIMs, GPS on, WLAN connected but no position: InfoGPS found 7 satellite 0 lock

  • critical : SIM in routing, network manual selection is slow and often back to search

  • annoying : automatic timezone does not work even with internet connection and GPS on

  • annoying : Xperia 10 II mobile data does not work in 2G and 3G networks on SIM2 which is a known issue¹ but it works for me on a Xperia 10 II with 4.5.0.19 (customisations: my ofono is allowed to load the qmi plug-in which by default is disabled + the network on the SIM2 is set manually).

  • function: InfoGPS installed among other default applications for GPS testing at first installation

  • aesthetic: SIM renaming and signal strenght bar are missing in “Mobile Network(s)” config menu

  • aesthetic: in Settings:Apps page, every icon should be added a subscript-i for info²

    The GPS failure can influence the timezone as well and without a position, Finland as default?

Software:

Suggestions:

  • Fixing the critical issues in same order listed above
  • Offer a try-and-buy-or-reset license

The try-and-buy-or-reset license would last e.g. 30gg [30days] and it might be free or cost €5. It let the user to try the Sailfish OS full license features and then decide to pay in full the license fee (€49 - €5) or having the phone reset to the free license or better locked than reset like a ransomware but legal.

Personally, I would buy it just to see if there is some way (upgrade, patch) that fixes or improve considerably the performance about the 2 first critical issues. I hope that 2 issues (GPS cannot lock satellites, routing manual network) are regression, is it right? Uhm, not really recent at least…

Notes:

  • ¹ Known Issues | Sailfish OS Documentation
  • ² despite the topmenu header Apps, System, Accounts is easy to confuse the new users with the apps list from which the applications can be started instead of quieried.

Now I am trying to apply this suggestion hoping that it will fix the GPS problem at reduced privacy counter-balance:

Obviously, downloading data that help to get a faster localisation on the urban/city areas would not solve the problem of not having access to the real GPS.

3 Likes

So you are still running it installed starting from Android 12? Then several of the issues are bound to be your fault. Until you do it properly, please keep your complaints to yourself.

The license adds features; it does not change how things you already have will work.

1 Like

Hi, wait a minute before blaming me… (nothing personal, here :slightly_smiling_face:)

I have received the smartphone with Android 12 and I do not see how this might influence the Sailfish OS installation but probably because I am not acknoledged about this kind of hardware/system.

Moreover, in the installation instructions there is the suggestion of to upgrade 11 from 10 but nothing about downgrading 12 to 11. There is also no any warning about, like

  • DO NOT INSTALL SAILFISH UNLESS bla bla.

Is there a restore procedure that bring the smartphone to Andorid 12 so I can sell it back or to Android 11 in such a way I can start the installation of Sailfish OS again?

By the way: I am not the only one that had problem with GPS… :wink: and Jolla is not going to sell a lot of licenses with the “it is your fault” attitude! :wink: :wink:

P.S.: 30gg [30days] license would also allow to activate the “developer options”

2 Likes

I must admit i don’t understand what you mean with “no SIMs” followed by “SIM in routing” now that i read it again. Initially i had that down as “modem doesn’t work”… but i guess you put a precondition as the first part of a compeltely different issue?

I’d still say Android 11 in bold is very clear instructions. Some config/initialization/blobs persist from Android; other you add at installation time. I can’t see why you’s want to go to Android 12 to go to Android 11, just flash it directly.

You are probably perfectly capable of googling, but none the less:

What even is “gg”?

And surely you can enable developer mode without a license.

1 Like

Sorry “gg” is in italian, I added the correction also in previous posts:

30gg = 30days license It is about this:


About this:

I have tested the phone with 2 SIMs (dual SIM) and also without any SIM. Currently without any SIMs because the foreign routing with manual network selection does not work, as well.


About this:

As you can see, there is no any warning about Android 12 OEM pre-installation might influence the Sailfish OS behaviour. IMHO, I intended the prerequisite of having Android 11 (or 10 at least) for the installation procedure not about the following functioning. I think that this part should be updated:

I want to downgrade to Android 11 in such a way I can re-install the Sailfish OS from a well-known working starting-point. However, if this attempt will also fail, I am going to reinstall Android 12 to give away a piece of hardware that contains configurations which are incompatible with Sailfish OS nowadays.


Finally, the GPS and foreign countries routing manual network selection problems were in place also the first time I installed Sailfish OS following the standard procedure. Then, after, I decided to give a try using different AOSP from the default one just to see if that AOSP can fix the problem. Worse than before, I go back reflashing the standard AOSP. After all, in the forum I read that trying a different AOSP was safe even if it would not work.

1 Like

I would use Emma to go to A11 and then retest all the features in Andy as recommended. Only after that I would reflash SFOS.

There is already a free license and it’s even not time limited.

3 Likes