You are missing the rust package. Install it with your favorite package manager.
Big thanks to Sailfish team!
I am really hoping that you are working Sailfish to Xperia 10 II.
Anyhow, I am running Pallas-Yllastunturi on XA2 and Xperia 10 at the moment and I have reflashed both from ground up (back to Android etc.). XA2 works fine as my daily driver. I just wish there was a version for my Xperia 10 II it would be awesome to have bigger battery and the screen is very nice. Camera is not the most important to have so I would be happy on one lens. Please Jolla make it happen.
No, it is not coming for Xperia X. We have communicated this previously: see question & answer #11 at https://jolla.com/sailfishx/#faq.
@jovirkku so what does it mean then? Or was it posted by mistake? Thanks!
Not a mistake: Xperia X is no longer supported as far as Aliendalvik upgrades are concerned.
But now, the 100th reply?
@Objectifnul @jovirkku but what could it mean instead. For me it means “Alien Dalvik 8.1 added support for f5121”. If it doesn’t mean this, i don’t know what it should mean or what it should tell the people!? Another mystery then
You are saying that
Sailfish can connect Bluetooth Low Energy devices now. However, Android apps cannot use peripheral devices via Bluetooth - other than for playback of the sound. Therefore smartwatches, for instance, cannot be controlled from Android apps
Is this something that is planned to be solved in the future or does this mean that using peripheral bluetooth devices with Android apps will remain (forever) impossible because of technical limitations?
Its an old log. Like I stated in the changelog thread they splitted the packages and that pulled in a lot of old changes to ad to the changelog.
The log has been fixed now. There is also the reasoning why the old items appeared in the 1st version of the log.
See: [changelog] Pallas-Yllästunturi 3.4.0
Not sure about that. Vertical gestures feel more consistent (since, you know, my phone is usually in portrait mode).
And come on, please do introduce option to disable the top menu when an app is open, so that the whole top screen margin can be used to close running app (just like it was in MeeGo and earlier Sailfish releases)
@jovirkku This issue was also fixed in this update:
I find the new incoming call experience confusing. It feels much more natural and consistent with the OS overall user experience to answer a call with a swipe down gesture.
The browser works much better now! As I said previously, the browser video playback issue was fixed. In addition, an issue I found with Google search where the user was not able to select suggestions was also fixed and a website I frequently visit now works. For this reason this has been one of the most relevant Sailfish OS releases for me.
And weather app looks much nicer now!
220.127.116.11 (RC9) rolled out today for Early Access subscribers. Please read the release notes.
Just re. swipe action, I personally get confused which actions are up and which are down, so up/side=better for me.
With. a. mixed. reception. and this thread now running at
111112 entries, a ‘poll’ thread on contentious changes might be an option - just an idea (for anyone).
Media DB doesn’t work after new 18.104.22.168 update. Resetting via sailfish utilities didn’t solve that, same goes for manually deleting the library files in nemo/.cache/tracker.
So gallery and Media Player are emtpy, no sources…
Updated from 3.3 to 22.214.171.124 on my XA2 and everything went fine. Android works, Media DB works (but never had problems with that). Wifi points are all there. Thank you
Solved - just took hours to index 1000 Files.
I’m having issues after updating. It looks as if zlib was upgraded from 1.2.9 to 1.2.11 and libpng remains at 1.6.34 and is still trying to load symbols for zlib 1.2.9 (which are no longer there). This breaks applications trying to use libpng, such as OpenStreetMap.
Just got to say - these release notes are so much better than on askbot. The side-by-side history display of the OP is not perfect, but tells me what’s changed.