Xperia 10: update got stuck at 100%
had force reboot.
booted successfully !
ah, forgot to mentioned: it complaid about chum gui. Did ignore that message
Xperia 10: update got stuck at 100%
had force reboot.
booted successfully !
ah, forgot to mentioned: it complaid about chum gui. Did ignore that message
Please check Settings > Display > Orientation. Make it “Automatic”.
Restart the phone.
The value used to be “Dynamic” but was renamed to “Automatic” on 4.5.0. I wonder if this change could have caused the problems discussed here.
Same here. But i can’t reinstall chum (missing libpackagekit dependency). I guess a new version of chum will be released soon. Outside this, everything seems to work ok. Android apps seems to no longer complain about network not being available.
Hey guys ive used the opengapps script to install google play store on the new 4.5 update and i used the android 11 pico but the terminal returns the umount:/home/.aliendvlik_systemimg_patch/tmp/systemimg_mount:no mount error
Update on my 10III went well even thou I had to force a reset.
Great update so far.
The firat thing I noticed… Amazon Music app and a play button. App is not started and the play button is without function
Video playback doesn’t work on many sites now on my XA2: bbc.com, Invidious instances etc. The error messages are: The content is not available in a compatible codec, No compatible source was found for this media, etc.
Piped instances work somewhat, with 0.1 frames/second or something like that. YouTube also works, but similarly bad (with 1080p, +95% of frames are dropped). This used to run smoothly on my XA2 with SFOS 4.4.
The debugging info copied from YouTube: YouTube debugging for SFOS 4.5 EA on an XA2 · GitHub
I’ve also tested a pristine user on my XA2, same issues there too.
Later Edit : Have flashed latest 4.4 and retried the EA update with no luck. Codecs are borked on my device with this first 4.5 version. It’s not only video, I’ve noticed Reddit videos have no audio at all in the native browser after updating.
Update was not that smooth like I expected. I let it run for roundabout 2.5 hours, then aborted.
The log is showing the following contend:
Feb 02 20:35:38 XperiaXA2 sailfish-upgrade-ui[4100]: Progress: 98
Feb 02 20:35:38 XperiaXA2 sailfish-upgrade-ui[4100]: Package: sailfish-components-calendar-qt5;1.1.5-1.9.1.jolla;armv7hl;apps, QML components to display calendar events
Feb 02 20:35:38 XperiaXA2 sailfish-upgrade-ui[4100]: Package: jolla-mediaplayer;1.3.5-1.6.1.jolla;armv7hl;apps, Jolla mediaplayer application
Feb 02 20:35:38 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:38 XperiaXA2 sailfish-upgrade-ui[4100]: Package: jolla-calendar;1.1.5-1.9.1.jolla;armv7hl;apps, Jolla Calendar Application
Feb 02 20:35:39 XperiaXA2 sailfish-upgrade-ui[4100]: Package: jolla-email-settings;1.1.37-1.11.1.jolla;armv7hl;apps, Setting page for jolla-email
Feb 02 20:35:39 XperiaXA2 sailfish-upgrade-ui[4100]: Package: jolla-email;1.1.37-1.11.1.jolla;armv7hl;apps, Jolla Email Application
Feb 02 20:35:39 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:40 XperiaXA2 sailfish-upgrade-ui[4100]: Package: sailfish-components-weather-qt5;1.1.16-1.7.3.jolla;armv7hl;jolla, Sailfish weather UI components
Feb 02 20:35:40 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:41 XperiaXA2 sailfish-upgrade-ui[4100]: Package: patterns-sailfish-applications;1.1.27.1-1.13.1.jolla;noarch;jolla, Sailfish Applications
Feb 02 20:35:41 XperiaXA2 sailfish-upgrade-ui[4100]: Package: patterns-sailfish-device-configuration-common-h3113;0.2.83-1.6.1.jolla;armv7hl;adaptation0, Jolla Configuration common
Feb 02 20:35:41 XperiaXA2 sailfish-upgrade-ui[4100]: Package: droid-hal-version-h3113;1.0.0-1.4.7.jolla;armv7hl;adaptation0, SailfishOS HW Adaptation droid version package 1.0.0.7 (release)
Feb 02 20:35:41 XperiaXA2 sailfish-upgrade-ui[4100]: Progress: 99
Feb 02 20:35:41 XperiaXA2 sailfish-upgrade-ui[4100]: Package: patterns-sailfish-device-configuration-h3113;0.2.83-1.6.1.jolla;armv7hl;adaptation0, Jolla Configuration h3113
Feb 02 20:35:41 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:42 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:43 XperiaXA2 sailfish-upgrade-ui[4100]: Progress: 100
Feb 02 20:35:43 XperiaXA2 PackageKit[4253]: upgrade-system transaction /8847_abbccddb from uid 0 finished with success after 455869ms
Feb 02 20:35:43 XperiaXA2 sailfish-upgrade-ui[4100]: Upgrade completed with code 1
Feb 02 20:35:43 XperiaXA2 sailfish-upgrade-ui[4100]: Reverting the enabled state of store to true
Feb 02 20:35:43 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:44 XperiaXA2 PackageKit[4253]: repo-enable transaction /8848_ecbeadcb from uid 0 finished with success after 151ms
Feb 02 20:35:44 XperiaXA2 sailfish-upgrade-ui[4100]: Reverting the enabled state of sailfishos-chum to true
Feb 02 20:35:44 XperiaXA2 sailfish-upgrade-ui[4100]: Distribution upgrade error: [sailfishos-chum|] Repository not found.
Feb 02 20:35:44 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:45 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:46 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:47 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:48 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:49 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:50 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:51 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:52 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:53 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:54 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:55 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:56 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:57 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:58 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Feb 02 20:35:59 XperiaXA2 kernel: binder: 19101:19101 --> 0:0 transaction failed 29189/0, size 32-0 line 2149
Please let me now if I can contribute some more logs.
So far, anything works great! Thank you for the nice new features and bug fixes
Have you noticed, that now even remote calendars can have emojis in it’s names? Nice
But the most valuable improvement in terms to security is the improved lock code. Many thank’s for that!
I’ve updated my XA2 and I suspect microg is not working: my android app uses google maps services and it doesn’t show maps now. Before updating, all was working fine.
Does anyone know how to solve it?
That’s the way those notifications work on Android. It’s ridiculous, but apparently it’s the only way an application can reliably run a background service without having to rely on Google. Dismissing the ‘undismissable’ Android notifications on Sailfish previously just led to them reappearing either instantly or whenever the app felt like it.
Edit: of course, the only reason it works this way on Android is so Google can tell people they really do need Google if they want Android to work well.
Weird, the first Android app I tested was Google Maps (being one of the most prone to issues) and it worked fine. Did you check the if the “Disable system packet verification” in Android Support settings has been accidentally turned off?
Yeh, but we didn’t find a better way to do it. As you mentioned the horizontal swipe is already used for something else. The reason to have it as tiny buttons is not to take too much screen estate and assuming that you don’t change the view often, one can use two hand when needed. The last reason was also to get the week view itself out, even if the way to get it is not as optimized as it could be.
Indeed. The large space below the day numbers is a reserved space for all day events. I tried a version were this space is collapsed when there is no all day event during the week, but when you swipe to other weeks, and you arrive on a week with all day events, there is a jump of the hour view below which was not nice. I tried also to put a small label there as a placeholder, mentioning that there is no all day event this week, but it was discarded because it cluttered the UI too much.
All that being said, I’m happy to get feedback and start discussions on how to optimise this first public implementation. If you would like to, maybe start a new dedicated thread for better visibility.
Thank you! It’s so great that this highly useful (and hardly known by anyone) functionality hasn’t been removed. So there’s nothing to stop me from upgrading
Well, that’s the whole point of Partnerspace. The application(s) you enable in it get autostarted (and even instantly restarted if they crash) and they’re always available on the Partnerspace screen.
Same here, auto orientation did not work after first reboot.
Weather widget connectivity is still totally random on my XA2.
After the upgrade it was working. Now I rebooted the phone to “fix” orientation detection and since then no weather widget.
Issue #2, XA2, dual sim.
Somatimes after a reboot, both sims are stuck in 2G mode. Wait 5 minutes, still stuck in 2G. Reboot again, back to 4G immediately.
Anyone else? Long standing issue, not v4.5 specific, but still an issue.
Issue #3, XA2, dual sim.
Sometimes sending SMS messages doesn’t work. After typing the message and hitting send, I get an error message and an icon that I can click to retry. No matter how many times I retry, it doesn’t send.
Reboot the phone, click again retry, and the message is sent immediately.
Anyone else? Long standing issue, not v4.5 specific, but still an issue.
Removing android support from the Jolla store doesn’t remove android support.
Can anyone confirm ?
which devices got Android 11?
10 III successfully updated with little struggles.
First thing: The Update is very big with 1 GB. Nevertheless the download was extremely fast, just took two or three minutes. Previous, much smaller updates needed at least 30 minutes if not more.
Nevertheless the update git stuck after installation - forced reset after an hour solved the problem. Android Icons where there from the beginning, don’t had to wait for them to appear.
Further testing will follow.
Automatic rotation works for me on standard browser on XA2.