OK, so if it is installed, can I switch it on/off with this option and if MG isn’t installed, the button does nothing?
I did not dare to update, and until I can figure out the following, I won’t update, ever.
My current version is 5.0.0.68.
The first and last update I tried was, I think, 5.0.0.70 or .71, I do not remember, alas.
All I remember that naively I thought it should “just work”, pressed the button, it downloaded itself, asked me to reboot, and then… recovery mode. Asked me to telnet. I did, but no luck, even factory reset did not work, so I had to flash the ROM again from scratch.
So now I am back to 5.0.0.68. Phone is SONY Xperia XA2 Ultra dual SIM
I do not dare to do any new updates until I can secure this working version to revert to.
I do not want to burn bridges behind me, I lost all apps, had to re-install everything.
Sure, my backups still worked, but those backups only copy a tiny fraction of what I had on the Internal Drive, and somehow I cannot install apps onto the SD card, because Android App system does not have write permission to the SD card and I cannot figure out how to enable it.
I hope there was really nothing important in these new updates since then, because I am really frightened about any updates now until a safe path is discovered how to 100% revert to what I have now… Any idea? TIA 
2 Likes
You wouldn’t need to reflash if you would read the forum and notice that there was a solution within hours of update. In this very topic.
4 Likes
19 posts were split to a new topic: Backing up a device with dd
This backup discussion is a bit off-topic for this thread.
But yes, dumping the whole sailfish partition with dd should be possible from recovery mode, though requires some knowledge. The exact partition depends on device model, as we need to go with the underlying partition layout used and required by the android hardware adaptation. And to either mount an sd-card in the recovery shell where to dump the partition, or run the ssh server in recovery mode and pipe stuff over ssh connection. So writing simple and comprehensive instructions for this is a bit tricky.
5 Likes
Update went smooth for XA2 Ultra, no problems
1 Like
updatte went ok on XA2 ultra
just one remark browsing seems to beas slow as it was
and
could somedody explain me why it is needed to make 500 MB free for such a small update (50 MB)
cleaning an reinstalling various apps is a pain in the neck
Thank’s for this update. My Xperia 10 is not my daily driver (C2 is), but I use it as hotspot provider in some cases. It had ever since the problem that it did not shut down, but it did a reboot. Every 10th to 30th try it shut down. With 5.0.0.71 it booted in recovery mode. By accident I found out that plugging the usb cable in and out it eventually booted into Sailfishos.
So I updated to 5.0.0.72. Now the phone boots up correctly and shutdown works always.
5 Likes
Luckily my Xperia 10 always booted fine (v. 71 + 72), but unfortunately still always reboots after a ‘normal’ shutdown / switch off attempt. Still have to push and hold vol up + pwr until it vibrates 3 times.
Q: As the bug seems to be found and pwr off now works for so many user: What was the reason for this bug? What/where could I research deep in the system and try to tweak something to fix it?
edit:
The often reported AAS bug also occured yesterday on one of my devices (AAS periodically starting & crashing loop).
Also I found in the settings menu, that there are now 2 entries to control AAS:
One in Settings/TopMenu/Switches section, the last entry, there is new ‘Android Appsupport’ on/off check button.
The second in Settings/TopMenu/Info section (the last one) is still the old ‘AAS’ on/off check button that always was there.
Why now 2 AAS control checkboxes in the top menu? Do they interfere / one disturb the other or presence of 2 control elements cause chaos?
The settings of the 2 checkboxes don’t affect the bug. If the AAS loop bug occurs, changing the 2 settings or also the 4 settings for AAS (autostart, MicroG, media + contacts access) don’t change the behavior, if it occurs.
edit: updated now my daily phone from 71 to 72. The Power Off bug seems to be gone now. It’s possible to shut down the phone by looong pressing the Power button until the ‘Goodbye’ Message on the screen disappears. Releasing the button then → Phone stays off and doesn’t reboot AT THE MOMENT. I’m curious how long this lasts and will report later if something changes.
edit: Reboot fails. LED glows white eternally. Pressing PWR button → LED turns to red. After a minute phone reboots. Asks for code, then a second time, then SIM PIN. Phone booted OK. Start AAS manually. Stays ON. Seems to be OK now.
edit: updating everything from Storeman and Chum and performing a post_sfos-upgrade as devel-su also was very helpful.
If I want to find the correct devices before using dd I run lsblk.
1 Like
Since upgrading my Sony Xperia 10 iii to .71/ .72 all Android app notifications via MicroG (i.e. The cloud based notifications) have stopped appearing. In MicroG settings all the ‘test boxes’ are ticked (with the exception of allowing one android app to overlay another) and it tells me I have 14 Android apps registered for cloud notifications. In the SFOS appsupport settings I have the new ‘Enable MicroG’ set. On my Sony Xperia 10v, still on .68 and without the new appsupport microG settings, but installed with identical android apps, I still get all the cloud based notifications. Has anybody else seen this issue?
xperia 10 III - appsupport stil not starting as good as in the earlier versions. Restart stil solves the problem in the best way. Using adroid apps causes high battery drainage! (in frequent use only 3-5 hours) Some apps just freeze completely at the beginning… (latest sonos app) or DB train app in germany slowly defreezes after some time. Its getting worse with every update and my phone is dying slowly. Xperia 10 V ist rotting in the drawer… will there be soon ™ a solution for this mess? I’m no programmer but a stubborn sailfish user… so i cannot contribute to help.
lets see how long i can endure…
10% battery gone by the end of this post.
1 Like
That’s very bad. I would definitely reflash.
EDIT: Better option is to find offending app.
1 Like
Check if there’s a CPU hog (I use Lighthouse GUI or top in terminal ).
If nothing there, maybe the battery itself is on its heels?
For me it’s the background daemon of Wire (a android messaging app) who goes heavy on CPU and drains battery. No particular pattern for it; opening/closing Wire (the app) stops that - probably it restarts its background service.
1 Like
Reflash. My 10 III with manual AAS behaves just as ever.
I could be a one especially bad Android app slowing you down, though.
And you might try to restart just AAS and not the whole system. AAS will become more stable once your images are indexed, I think
Hint: you can control the rights of an Android app by Settings/Apps/tap on Android app icon/Open Android settings/.
There is:
Notifications (Benachrichtigungen)
Rights (Berechtigungen)
Memory and cache
Mobile data and WLAN
Extended.
Under Rights you can control what the app is granted or denied to access.
When using the app / Ask every time / deny
and remove rights when app ist’t in use, or not remove.
Under Notifications you also can control a lot of fine tuning settings.
Background notifications ON logically means some Android daemons running and therefore more battery drain.
I did turn them all to OFF, so have normal battery drain, but logically no notifications and have to open an app and have a look if I want to know what’s going on. Unfortunately that’s true.
Good luck!
Thanks!
Wire is a messaging app, so notifications are useful when they work.
But yes, polling could work too - esp with the issues in AAS…
I wish i could reflash but my usb c Port is broken and no data transfer available. Only charging works. and I have already changed the battery becouse the first one was broken. I took it from my wifes device which had a broken Display. its the first device witch such Battery problems. My wife uses now 10 V with standard android, becouse the Sailfish immage got delayed…Thats Why I say its a bad situation for me and i dont want to go back du F….ing Android bloatware device. But no alternative right now. have to backup my Data over WLAN… first and watch my phone how it slowly dies.
1 Like
Since youre hardware is broken in so many aspects SFOS does not seem to be the main problem. Your phone is done.
replacing the usb-c port is easy and cheap! i did it in july for exactly this reason. i got the charging port daughter board for 10$USD on ebay. also, since you already replaced the battery, you presumably have everything you need (mobile screwdrivers, heat gun or blow dryer, back cover adhesive)
2 Likes