Yeah, would make those 5 bucks definitely a better sale than updates twice a year, rolling EA distribution channel for the brave?
2 Likes
If closing an Android App by swiping down instead of using the back button, does it still kill the backgrounf process?
The one uses WhatsApp and accepting its privacy policy is the one that is harming themselves.
1 Like
Yeah, but there are people who have different priorities and want to use sfos even with spyware, no point in shaming them, you keep using it as a degoogler/defacebooker/deandroider, let others use it as a linux phone with android app capabilities
7 Likes
So glad it’s working again. Can anyone explain what “stop release” is?
1 Like
@kan_ibal
There are also people who are forced to use certain applications for work or other circumstances.
While I appreciate hard stance of some organizations like FSF for maintenance of an ideal, the life demands pragmatism. It is always better to have the option of slightly compromised system rather than the choice between „unusable pure” and „completely corrupted”.
10 Likes
For me the update (from 4.6.0.12, 10ii dual sim) says that I have to remove
appsupport11-system-unprivileged
sailfish-version
sailfish-version-variant
and fails.
Exactly the same as me.
run
pkcon remove appsupport11-system-unprivileged
and you should be good to upgrade.
You’ll have to reinstall AppSupport afterwards.
2 Likes
I understand what you’re saying, Kan_ibal. Yes, it was work-related. I’m not skilled enough to prove, so I hope that the remaining personal communications I have in Whisperfish are segregated from WhatsApp. I don’t have both apps actively open in hopes of preventing data “leakage” to WA.
But, yes, work precipitated WA usage. And that still ostracized me. Everyone else (USA) here uses group texts for communications. Via this forum, I’ve learned that this is a U.S.-only thing that makes no fiscal sense anywhere else in the world, is not supported in SFOS, and I’ve resigned myself to never seeing implemented in SFOS. So WA was the alternative with widest acceptance by colleagues and clients to accomplish group messaging and media sharing.
Working on live events with teams of people that need to have group communications, but whose team members change for every event, it’s wearying trying to overcome inertia of literally everyone simply doing group texts. WA was the least-resisted option.
But I love SFOS and have been a staunch supporter since the introduction of the N9, which I still have on a shelf.
Thanks for your input, though. Others who may not be aware of WA privacy issues may find your post informative in the future.
6 Likes
Apparently, in this version, Aurora quits unexpectedly after a download is complete and ready to be installed. Should I disable the options that I enabled for it to work in 4.6.0.12?
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.
2 Likes
Yes, it would be best if you disabled the developer options in the Android settings.
2 Likes
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.
1 Like
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”