Actually, there is a problem with App Support – it doesn’t start most of the time.
It starts fine if I do it manually from Settings.
It never (roughly) starts automatically on boot in spite of being set to do so.
It starts around 50% of the time when trying to start an Android app. Starting the Android app then immediately going into Settings → App Support may help.
Tried by now: I passed from 4G to 3G and still have connectivity and mobile data on SIM2, the same for 2G which I am using to send this reply. I have the sensation that is about network operator OR because my SIM1 is set to 2G (I go to test). Nope, SIM1 4G and SIM2 in 2G connected with mobile data and here I am writing.
Customisations: my ofono is allowed to load the qmi plug-in which by default is disabled + the network on the SIM2 is set manually
It does not support the last version 4.5.0.19 in which there is a similar icon for the topmenu but it brings to the Andorid Support page. This button is supposed to enable/disable the Android Support, instead. Is it right? Will the author update it for the last version, also?
Hi @robang74! The patch works in the last version of sfos, I’m using it without any problem.
And yes, this patch enable/disable Android support with a toggle
I just hope Jolla will release a new hotfix or let’s say, minor update to 4.5, to address hw acceleration on videos on browser not working, randomingly not login on passcode on my xperia 10, wifi status new page bugged, and some bugs exposed as 4.5.0.19.
Will be warmly welcomed
edit: this, of course, before the next 4.6 update or whatever they are planning to do… who knows, a Sailfish 5 release wow
This link was working at the time I have posted here - as far as I remember - but now it does not work anymore and since v4.5.0.21 every images to download require some extra fields in the url: {Policy, Signature, Key-Pair-Id} which is supposed being unique for each customer / registered user.
and you will enjoy the 403 forbidden error. I think that this is an sensitive step towards a more restrictive distribution policy. With positive and negative implications, depending the point of view:
negative - because the community is even more thigh to Jolla Oy and its destiny
positive - because Jolla Oy affirmed in a practical way their right to limit the re-distribution of their proprietary software and the vendor’s one.
I cannot exclude that this decision has been taken under the pressure of the vendors, but I do not think it is about Sony because all the stuff is anonymously downloadable from their website. Possibly Qualcomm which is the producer of the SoC, instead.
UPDATE
For the next release, I suggest to apply this patch:
--- flash-config.sh 2023-07-11 11:54:29.000000000 +0200
+++ flash-config.sh 2023-07-06 23:37:32.870895987 +0200
@@ -8,6 +8,7 @@ FLASH_OPS=(
"flash dtbo_b dtbo.img"
"flash userdata sailfish.img001"
"flash_blob oem_a *_v12b_seine.img"
+"flash_blob oem_b *_v12b_seine.img"
)
GETVAR_ERROR_secure="
@@ -32,5 +33,6 @@ Please remove any additional files.
"
FLASH_COMPLETED_MESSAGE="
-Remove the USB cable and bootup the device by pressing powerkey.
+Remove the USB cable and bootup the device by pressing powerkey off.
+Alternatively execute 'sudo fastboot reboot' to reboot it.
"
Possibly I am wrong but I remember to have used a direct link without any {Policy, Signature, Key-Pair-Id} to download that image. For sure in posting that link, I did not removed anything from.
Update went almost perfect; Xperia XA2 seems little smoother, faster.
One issue: my openvpn entries were gone; had to reinstall them one by one.
Very nice job…thanks
Hello in this old topic.
do any of you have link to 4.5.0.x sailfish? I need recovery file from this version. My update to 4.6. sauna went bad and with recovery file from sauna i can’t reach recovery mode.
Xperia 10 I.
Thank you.