Google Play Services on Xperia 10 III Sailfish 4.4.0.64 (now 5.0.0.76)

Thanks, TIL.

For @rafaelvlmendes AFAICT if you mod the 2 related top variables accordingly, I think it’ll just work :trade_mark:

GAPPS_DIR=/opt2/gapps-for-appsupport
...
SYSTEM_IMG=/opt2/appsupport/system.img
1 Like

Are these scripts modifying the system.img? That’s a bit risky in the long run.

I used to. It also worked, but yes, bit more fiddling on updates.

Now we’re on bind mounts, latest strategy described at Google Play Services on Xperia 10 III Sailfish 4.4.0.64 (now 5.0.0.76) - #92 by lkraav

I actually tested it by editing the script and it worked perfectly. Tested on an XA2 and Ultra.

However, to work perfectly I had to install the applications in the /Produt/Priv-App folder and install a current version of the Play Store.

Hello Ikraav,

How do I go about updating from 5.0.0.72 (using a modified system.img [AAS 11] with OpenGApps) to 5.0.0.76 using the “Bind-Mount Strategy” (MindTheGapps)?

Will all installed Android apps (AAS 11) be preserved?

(Translated with Deepl de-en)

Main thing: I disabled AAS auto-start on boot. This makes it easier to control debugging and log following on first start, for if anything ever fails.

I can’t recall if .76 changed system.img vs .72, so the only certain move should be

  • stop AAS
  • restore original system.img from script backup
  • run installgapps-mount.sh

Yep, my install continued working as-is just fine.

Thanks for the instructions.
I’m a little confused. Should I run installgapps-mount.sh (.72 with AAS11) before updating SFOS to version .76?
Sorry for my uncertainty.

Yes. (20 chars) abcdefgh

1 Like

5.0.0.73 → .77 ( new release before I got the time to update ) - same

5.0.0.72 → .77 update on X10III. Everything works just like before with AAS11.
Thank you for your work.

1 Like