I had this problem with Aurora beta version (4.5 I think, I installed a beta version to solve an issue in the past, then forgot I was on beta). I reverted back to latest stable version (4.4.4 or something) and Aurora started working again. Don’t know if this is your issue, but looks a lot like what I experienced.
I’m not even on SFOS 4.6 yet, still on 4.5 on my Xperia 10 III because I can’t afford instabilities on my daily driver.
Yes, it would be best if you disabled the developer options in the Android settings.
Thanks for answering. It didn’t make a difference though.
Thank you! Downgrading Aurora store to 4.4.4 did the trick. I recently installed Aurora store 4.5.0 (since F-Droid doesn’t list it as beta any longer). I must have updated it about the same time as I upgraded Sailfish to 4.6.0.13.
No, still happens sometimes, but not always.
(android apps close on pressing the back button, e.g. When Leaving a signal chat
Settings / Applications still only shows ‘Couln’t get application status’ instead of settings page for Android apps when AppSupport isn’t running. Prior to 4.6.0.11 those settings pages were accessible regardless of whether AppSupport was running or not.
Settings / Storage / System data details no longer shows space occupied by Android. The reported value is 0 kB - 20 kB or so.
AppSupport still shows wrong battery level. It gets stuck with the battery level from the moment that AppSupport was launched, and then never updates it.
How do I clear out the 4.6.0.11 download that I havn’t installed, and get update to start again and download the 4.6.0.13 ?
I’d rather not play lock-up roulette with the older update.
I use OneDrive for backups, and after the upgrade to 4.6.0.13 (Xperia 10), on Settings->Accounts, it tells that I’m not signed in my account. I did not notice this in 4.6.0.11, but I’m not sure if it worked.
If I click the account, Settings shows a page asking me to sign in using the browser.
The browser appears showing some content of the microsoft login page, but closes the page. And Settings becomes the active application.
In Settings, the message changes to error: “Virhe tilissä Tilin kirjautumistietoja ei voinut päivittää”. Can’t update the sign-in data.
Journalctl printout contains messages “OAuthAccountSetupPage: account update failed: 7 invalid_scope” and “OAuth account creation error: 7 invalid_scope” at 11:02:12.
– Logs begin at Sun 2024-06-16 10:59:58 EEST, end at Sun 2024-06-16 11:02:28 EEST. –
kesä 16 11:02:01 Xperia10-DualSIM invoker[8352]: WARNING: An inactive plugin is misbehaving - tried to show a window!
kesä 16 11:02:01 Xperia10-DualSIM invoker[8352]: WARNING: requestActivate() called for QQuickView(0x7d1508) which has Qt::WindowDoesNotAcceptFocus set.
kesä 16 11:02:04 Xperia10-DualSIM dbus-daemon[3405]: SailfishKeyProvider_storedKey():error: no such stored key exists
kesä 16 11:02:04 Xperia10-DualSIM dbus-daemon[3405]: dbus-daemon[3405]: [session uid=100000 pid=3405] Activating service name=‘com.google.code.AccountsSSO.SingleSignOn’ requested by ‘:1.1196’ (uid=100000 pid=19784 comm="booster [silica-qt5] " label=“u:r:kernel:s0”)
kesä 16 11:02:04 Xperia10-DualSIM dbus-daemon[3405]: dbus-daemon[3405]: [session uid=100000 pid=3405] Successfully activated service ‘com.google.code.AccountsSSO.SingleSignOn’
kesä 16 11:02:04 Xperia10-DualSIM signonpluginprocess[23511]: QConnmanEngine: Unable to translate the bearer type of the unknown connection type: “bluetooth”
kesä 16 11:02:04 Xperia10-DualSIM dbus-daemon[3405]: dbus-daemon[3405]: [session uid=100000 pid=3405] Activating service name=‘org.sailfishos.browser.ui’ requested by ‘:1.1196’ (uid=100000 pid=19784 comm="booster [silica-qt5] " label=“u:r:kernel:s0”)
kesä 16 11:02:04 Xperia10-DualSIM prestart[11464]: warning: ignoring argument: -prestart
kesä 16 11:02:04 Xperia10-DualSIM dbus-daemon[3405]: dbus-daemon[3405]: [session uid=100000 pid=3405] Successfully activated service ‘org.sailfishos.browser.ui’
kesä 16 11:02:05 Xperia10-DualSIM mce[1116]: modules/battery-udev.c: mcebat_update(): battery_level : 80 → 79
kesä 16 11:02:05 Xperia10-DualSIM prestart[11464]: ssusysinfo_load_ssu_config: expected ssu config version 14, found 0
kesä 16 11:02:05 Xperia10-DualSIM booster-browser[23523]: [D] unknown:0 - Using Wayland-EGL
kesä 16 11:02:06 Xperia10-DualSIM prestart[11464]: [W] unknown:0 - QConnmanEngine: Unable to translate the bearer type of the unknown connection type: “bluetooth”
kesä 16 11:02:06 Xperia10-DualSIM prestart[11464]: [D] onCompleted:108 - ViewPlaceholder requires a SilicaFlickable parent
kesä 16 11:02:06 Xperia10-DualSIM lipstick[7925]: [D] onCompleted:264 - coverActionIndicators created sailfish-browser.desktop
kesä 16 11:02:06 Xperia10-DualSIM lipstick[7925]: [W] unknown:0 - WindowPixmapItem does not have a source texture, cover will be dropped…
kesä 16 11:02:07 Xperia10-DualSIM prestart[11464]: [D] unknown:0 - Updating services as GetServices returns
kesä 16 11:02:07 Xperia10-DualSIM prestart[11464]: [D] unknown:0 - No default route set, services: 23
kesä 16 11:02:07 Xperia10-DualSIM prestart[11464]: [D] unknown:0 - Selected service “polle-5GHz” path “/net/connman/service/wifi_3878626cb356_706f6c6c652d3547487a_managed_psk”
kesä 16 11:02:12 Xperia10-DualSIM estart[19784]: [D] _accountUpdateFailed:141 - OAuthAccountSetupPage: account update failed: 7 invalid_scope
kesä 16 11:02:12 Xperia10-DualSIM estart[19784]: [D] done:105 - OAuth account creation error: 7 invalid_scope
kesä 16 11:02:16 Xperia10-DualSIM gecko-camera[11464]: codec init:66 – Initialized codec plugin at /usr/lib/gecko-camera/plugins/libgeckocamera-droid.so
kesä 16 11:02:18 Xperia10-DualSIM invoker[8352]: WARNING: An inactive plugin is misbehaving - tried to show a window!
kesä 16 11:02:18 Xperia10-DualSIM invoker[8352]: WARNING: requestActivate() called for QQuickView(0x7d1508) which has Qt::WindowDoesNotAcceptFocus set.
kesä 16 11:02:22 Xperia10-DualSIM buteo-oopp-runner[23893]: [W] unknown:0 - QConnmanEngine: Unable to translate the bearer type of the unknown connection type: “bluetooth”
kesä 16 11:02:23 Xperia10-DualSIM signonpluginprocess[23920]: QConnmanEngine: Unable to translate the bearer type of the unknown connection type: “bluetooth”
kesä 16 11:02:28 Xperia10-DualSIM [5591]: [W] unknown:0 - “jolla-signon-ui: CredentialsNeedUpdate now false. From: . Notification currently exists: false”
I sustain this. Early (even if smoke-tested) delivery ftw.
This has happened to me for a very long time across lots of releases and lots of account types - email, dropbox, onedrive, etc. The only way I’ve found to ‘fix’ it is to delete the account on the SFOS phone and then recreate it.
You’re right. Majority of space occupied by AppSupport is now on the /home/ partition. On the rootfs partition only a tiny amount of space is taken. So the small value reported in the “System data” entry is correct, as the actual taken space is reported on the “User data” page.
However, the other two issues, i.e. incorrect battery level in AppSupport, and Settings / Applications pages of Android apps not working when AppSupport isn’t running, still persist.
Thanks. Deleting and recreating the account worked.
Hi,
After install of 4.6.0.13 when I restart (or it restarts due to OOM killer) AppSupport loses a mobile internet connection.
Restart of network stack does not help, going to flightmode either, as well as turning on/of mobile network (used to work in case of network issues in android before upgrade)
Could anybody help me debug the issue?
logcat shows bunch of NetUtilsWrapper: Unexpected command /system/bin/ip -w -t .... commands (ip does not even have -w switch).journal does not mention any alien or network issues, warnings or errors.What else could be helpful to see what’s happening?
Edit: Seem like an issue with name resolving, any hints?
Try devel-su systemctl restart ofono
I’ve been able to twice resurrect missing mobile data connectivity for App Support, where no other method short of reboot worked.
Maybe Jolla could add “Restart/Reset MPRIS” to Tools, because in 50% of the cases i have sometimes the Problem that the Mediaplayer-Info and Controls are not working with my Car-Audio (LG MediaNAV-Evolution). Sometimes its enough to restart the Player-App (Deadbeef or Jolla Mediaplayer) for 2-3 Times.
4.6.0.13 has been officially released today for everyone, so I assume that the “launch from app grid” problem has not been addressed further. 
Wondering when the stop release status is determined…
Shouldn’t really matter until the next update
Switched to Sailfish OS a couple days ago after being curious about it for almost a decade. I’m very glad to see it being actively developed and I’m also very happy with the general UX, UI and app catalog of Sailfish OS.
Thanks!
One question, though: What exactly is a “stop release”?