I can report quite the same for X 10 III. Only differences:
- happens since Update to 4.5
- Retry after reboot fails as well.
SMS seems completely broken.
Found a solution for my case: SFOS 4.5 feedback thread - #223 by FrankSiebert
Thank you for that valuable help. Disabling VoLTE made SMS work for me again as well.
X 10 III
Here is described how to apply the change: Beta VoLTE on the Xperia 10 III, disabled by default
Concerning problems with internet access from Andoid apps:
On my 10 III I disabled ip v6 for mobile connections because of problems roaming in Poland and Austria.
I kept that setting and just set it to ip v6 only for a test:
Fennec can access the internet with settings to dual or ip and fails with ip v6.
A broken ip v6 stack might explain a lot of problems with certain providers, roaming etc.
2 Likes
Xperia 10 II
Audio is not working on sverigesradio.se âLjudfilen stöds inte av webblĂ€sarenâ (audio file is not supported by the browser), worked on 4.4.
Audio/video works on youtube.com
Hi jovirkku. I prepared the logs via Collect Persistent Logs | Sailfish OS Documentation. How can I send you my log file? Is there any upload functions in this forum? Or do you have an e-mail address where I can send my log file.
Later I uploaded the file via care@jolla.zendesk.com to jolla care support succesfully.
Apparently the upgrade to ffmpeg 5 broke some parts of the browser playback. This has been fixed, but did not make the release. Letâs hope for a hotfix.
Meanwhile⊠may i suggest the SâPlay app?
3 Likes
Ok, found out how it works (@peterleinchen interested??).
Start app-support, ps auxw|grep lxc shows you ârcfile=/tmp/appsupport/aliendalvik/config, there in you have lxc.include = /tmp/appsupport/aliendalvik/10-bsp_config.
Hunting the source of this, since this is volatile. systemctl status aliendalvik gives you the script /usr/lib/systemd/system/aliendalvik.service, there in Requires=aliendalvik-prepare.service and there in âŠ"$CONTAINER_CONFIG_PATH/10-bsp_config". Bingo!
Added thereafter:
echo âlxc.mount.entry = /etc/hosts system/etc/hosts none bind,create=file 0 0â >> â$CONTAINER_CONFIG_PATH/10-bsp_configâ and restat app-support.
Verify:
devel-su appsupport-attach cat /etc/hosts
(this changed in 4.5, see Testing Advice | Sailfish OS Documentation )
Warning: have no idea if this interferes with system updates!
5 Likes
So far, Iâm pretty happy with the 4.5 update, a lot of things have been fixed. Iâve reinstalled from scratch on my 10 III, and updated on the last day of Early Access, I literally woke up to the news of public release.
Until today, where I noticed a seemingly familiar bug where audio stops working altogether (no notifications, calls seemingly dont ever start, no media playback) - In 4.4.0.72 the fix was just a pulseaudio -k away (which starts a new pulseaudio instance, -killing any existing ones) and you can carry on like nothing happened. However, this happened twice today. I figured Iâd try a pulseaudio -k again but sadly, it did not work. I had to reboot the device to have audio again.
After rebooting, I also noticed that thereâs a delay in the AppSupport starting? I tried opening signal but it didnât open, I had to open it a second time and see the notificaiton App Support is starting to open Signal or similar, and then Signal opened.
I think you can start (or search an existing thread) specific to /etc/hosts and post this there too:)
1 Like
Having a problem with WhatsApp not being able to find itâs storage.
I can send and receive messages, but not images/files.
Receiving an image gives this error:
Download failed
Canât download because no internal storage is available. Please unmount it as a disk drive, and try again.
I also get an error trying to attach from gallery:
Internal storage required
Please turn off USB storage and try again.
And for images I sent previously:
Sorry, this media file doesnât exist on your internal storage.
In the WhatsApp logs (/home/.android/data/data/com.whatsapp/files/Logs/whatsapp.log) itâs looking for /storage/emulated/0/WhatsApp/Media/âŠ
...
2023-02-12 03:14:58.376 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder/mkdirs failed: /storage/emulated/0/WhatsApp/Media/WhatsApp Video
2023-02-12 03:14:58.379 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder/mkdirs failed: /storage/emulated/0/WhatsApp/Media/WhatsApp Images
2023-02-12 03:14:58.379 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder/mkdirs failed: /storage/emulated/0/WhatsApp/Media/WhatsApp Documents
2023-02-12 03:14:58.380 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder/mkdirs failed: /storage/emulated/0/WhatsApp/Media/WallPaper
2023-02-12 03:14:58.380 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder/mkdirs failed: /storage/emulated/0/WhatsApp/Media/WhatsApp Profile Photos
2023-02-12 03:14:58.382 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder/mkdirs failed: /storage/emulated/0/WhatsApp/Media/.Links
2023-02-12 03:14:58.382 LL_D W [313:WhatsApp Worker #4] fmessageio/prepareFolder/nomedia doesn't exist, creating in /storage/emulated/0/WhatsApp/Media/.Links
2023-02-12 03:14:58.383 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder /storage/emulated/0/WhatsApp/Media/.Links; exception=java.io.IOException: No such file or directory
2023-02-12 03:14:58.386 LL_E W [313:WhatsApp Worker #4] fmessageio/prepareFolder/mkdirs failed: /storage/emulated/0/WhatsApp/Media/.Statuses
...
*lots* more just like it
Weird thing is my chats are still all there and accessible, so Iâm not sure where itâs picking those up from.
My old data still exists in
/home/defaultuser/android_storage/WhatsApp
Because Iâm not sure that the root dir looks like to Android apps I tried a few mappings:
/storage/emulated/0 â /home/defaultuser/android_storage
/home/defaultuser/android_storage/emulated/0 â /home/defaultuser/android_storage
/home/defaultuser/android_storage/storage/emulated/0 â /home/defaultuser/android_storage
Iâm assuming this is to do with the new scoped storage in Android 11.
Iâm also wondering if because I think I âcheatedâ a while ago to create space the easy way I mapped android_storage straight to the sdcard it messed things up in this migration:
/home/defaultuser/android_storage â sdcard
So does anyone know how Android 11 âscoped storageâ works? Itâs is different structure or just permissions?
Any suggestions on how to handle this?
I also canât backup my chats because no internal storage was found.
Everything else with 4.5 so far seems to be working well for me.
Thanks, that will do until the fix. (I usually use the news clip flow, but SR does not seem to provide an API for it HÀmta ut enskilda nyheter frÄn API:t - Forum för teknisk support - Sveriges Radio)
It would help if separate bug reports are created for issues that are discussed here. Information is likely lost in such a long thread
6 Likes
Official 4.5.0.16 update on XA2 Plus dual sim went smoothly.
After that Bluetooth wonât turn on at all.
Several reboots, normal (power->top menu) or power+volume_up bring no help.
Settings->Bluetooth Restart doesnât help either.
Not possible to turn on Bluetooth at all! Any Ideas?
The empty bar at the bottom is there so you can actually get out of the folder. That being said, you were probably using launcher patches before, because nothing was changed about the way the launcher works - in fact Iâm pretty sure nothingâs changed about the way it works since 2017 or so.
3 Likes
I use this opportunity the continue the list:
Yle (Finnish national broadcasting company) news site is somewhat broken. Usually the browser crashes instantly, when opening the given link. I was able to reach the fifth tab of that article, but I had to close Android App Support and all the apps I had running, but even then it took a ridiculous amount of attempts.
MTV (the biggest Finnish commercial media company) news remain unreadable, since the page layout gets all wonky and the actual news content is not shown.
At least on XA2 bluetooth does not seem to work unless the bluetooth subsystem is restarted from Settings->Utilities. If search this thread you will find simiar posts. I hope there will be a hotfix release.
Youâre welcome. After all you started it somehow when asking one year ago how hard it would be to create a week view. After some initial thoughts, I started it as a challenge : can we do the full layouting in QML ? And to answer your question, it took something like 2 weeks, not so hard after all. Then I started discussing with pvuorela and martin from Jolla for integration. My initial design was changed by martin and it took some more weeks to adjust. Finally after long reviews and discussion with pvuorela on technicalities the QML layouting was dropped in favour of reusing the CPP one of the day view.
Here are two screenshots of the initial design:
6 Likes
ok, i have restore the mobile from setting and upgrade other time from 4.1 all version to 4.5; all working fine now.
for keyboard i suppose the problem is come because i have installed this two app very useful
https://openrepos.net/content/mkiol/speech-note
https://openrepos.net/content/mkiol/speech-keyboard
i hope will be included in the official repository
Enrico
1 Like
I respond to myself.
The problem was not the phone. The Router had selected channel 13 as autochannelâŠ
Youâre right. I got mistaken by those 4 rows on the XA2 because I already got used to the 10 IIIâs much taller screen which fits 6 rows without scrolling. And yes, Iâve been using various launcher patches since ever, so I already forgot how the genuine launcher looks like. Sorry for the confusion.
Which is amazingly unproductive. No wonder that patches like âLauncher combinedâ allow exiting the folder view by swiping left or right or tapping anywhere where there are no icons, which works just as good and doesnât waste any screen real estate. A bar consuming 20% of the screen only to be tapped when one wants to exit the view (and serving absolutely no other purpose) must have been the UI designerâs worst idea ever.
I donât know what changes were introduced in 4.5âs launcher but the code does differ quite a bit making all patches which used to work on 4.3 and 4.4 incompatible with 4.5.
1 Like