updated to 4.1 today, no glaring issues. Any plans to make the offline location data for the americas available?
1 Like
I did now update her phone by cli in devel-su mode with
devel-su
ssu re 4.0.1.48
version --dup
reboot
afterwards
ssu dr customer-jolla
pkcon refresh
version --dup
Her phone is in german language, and the file browser should appear as “Dateiverwaltung”, but it did not but as File browser AND it did not display PDF files. Also the white dot on the upper right corner after tapping a PDF file was missing.
So I deinstalled the file browser manually and installed “Dateiverwaltung” new from the Jolla Store. After this it works fine.
It may not be a fix but tracking this here is much appreciated. Thanks!
I believe the newly added ‘Desktop site’ in browser’s menu wasn’t mentioned here?
-
And… Is it just my XA2? Or can we no longer access Android’s settings hitting the back button (Show Licences) ? It immediately closes the window
I installed a settings shortcut .apk(which is actually better) -
Not surely related but most probably is…
Editor could no longer open files (built-in file picker) after the update (error: could not load page)
5 Likes
Use sfos-upgrade from Open Repos.
This has never failed me.
4 Likes
Doesn’t that also affect 4.0? You can use apkd-launcher com.android.settings on the terminal or use the app AlienDalvik-Control from OpenRepos.
Probably related: Alien Dalvik options not working in 4.1.0.23 on Sony Xperia 10 Plus
No it has always worked on 4.0
I can confirm that I experienced this (on Xperia 10ii dual sim following flash of 4.1.0) where my Wifi network password was not retained. There were also other situations where, following flashing the OS, initially logins and credentials weren’t saved. After a reboot however this seems to have fixed the issues.
Examples - Google Account sign in not saved. Audio recorder app appeared not to have saved recordings (In fact recordings were saved but were not shown under Recordings tab until after a reboot.)
Also I was initially unable to complete registration of Whisperfish (Reported under Whisperfish thread) until the phone was rebooted since the registration hung after input of the OTP Signal code.
Hope this is helpful in identifying possible cause.
Zendesk typo: In the notes it mentions that 4.0.1.48 is a ‘stop release’ and it has a link to the Zendesk page: https://jolla.zendesk.com/hc/en-us/articles/201836347#4.1
The page has a typo as the Koli release is listed there as 4.1.0.48
3 Likes
With this release qr scanning in android apps (such as nextbike) works now for me. Nice!
Powering off my Xperia 10 is still impossible with the normal shut down. It’s always restarting.
1 Like
GPS Info did show wrong and chaotic permanently changing compass values after the update.
After deleting it and re-installing GPS Info from the Jolla shop, it works now.
That’s strange, I tried to shutdown twice on an Xperia 10 and it did shutdown as expected. No USB connected.
This has been reported in its own bug report:
already a month ago.
(–edit
and now fixed 
but below is still valid)
So it really seems if a bug report is not marked as „filed internally” or noted explicitly as (to be) solved we need to ping someone at Jolla directly?
But whom? There was already a topic where this was asked for…
–
oh, and there are a few topics here where the release was also wrongly mentioned like 4.1.0.48.
I corrected a few topic headings but the content of answers I am of course not allowed. It were about a dozen, so not that much work.
1 Like
Is it just me or does it seem that sailfish has become a lot more power hungry in 4.1? Looking at the power draw on my XA2 Plus before the update it was about 100 mA in flight mode, now it’s well over 200 with the same settings. Tested with all applications closed and android emulator stopped.
1 Like
That happened to me when USB was connected, but I haven’t yet tested without. Did you try without?
Same ‘feeling’ on an X.
Normally I would say/conclude it is tracker and friends.
But I have 4.1 on device since Wednesday and charged it already daily. Something I did not have to do earlier with this development/testing device.
Let us wait a few more charge cycles…
Of course I tried without USB-cable.
I’ve checked about everything I can think of. Like I said, I tested in flight mode, so it’s not related to any network connectivity. I checked for wakelocks (didn’t see any). I feel it’s probably due to the new kernel. It seems to be a build from February this year. Maybe some hardware option is not correctly set, causing a much higher power draw.
3 Likes
Updating from the previous 4.0 release, I did not get a list of all system packages to remove, but just these four:
feature-jollasailfish-content-configuration-jollasailfish-content-graphics-jolla-
sailfish-content-graphics-jolla-z1.75
I tried to see whatpkconhas to say about these:
[root@Sailfish ~]# LANG=C pkcon remove feature-jolla sailfish-content-configuration-jolla sailfish-content-graphics-jolla sailfish-content-graphics-jolla-z1.75
Resolving
Testing changes
Finished
Fatal error: This request will break your system!
My cue ball suggested that this is probably a false alert, so I updated anyway. It appears to work.
bluetooth-rfkill does not work. rfkill works on its own.
did someone experience this?