Oh, and one more thing:
Thatâs REALLY bad (if true), considering that it was mid 2018 when Rostelecom joined, so 2019-2020 must have been among their fattest years.
Oh, and one more thing:
Thatâs REALLY bad (if true), considering that it was mid 2018 when Rostelecom joined, so 2019-2020 must have been among their fattest years.
I agree 100%, a solid modern browser is key for the longlivety of a mobile phone. I used BB10 until very recently, like 2023. What forced me to change was the speed of the CPU and the browser couldnât keep up with modern home pages.
If a phone can browse the internet like a normal PC, then it is surely useful regardless of app support.
Android app support is not that important for me as I usually always use the web service if there is any before the app. For Android apps I have an Android burner phone if necessary. Android app support is nice but not a game changer for me.
Yes, a modern browser should be the cornerstone of any mobile OS. My N9 was incredibly useful for many years after it was abandoned by Nokia because a fresh Firefox Mobile was available at OpenRepos. This, together with excellent online/offline navigation and a terminal, was all I needed.
SFOS is in a much better position as it has many apps, along with an Android compatibility layer. However, it is lacking on the native browser part. Personally, I think maintaining a modern browser is a huge task and Jolla doesnât seem to have enough resources. Firefox has some old builds for Mer, it should not be a lot of work for Mozilla to get it working.
Other relevant discussions:
The question is more, who would back the effort, money wise?
in fact, the browser is not firefox, but gecko + xulrunner, which has been deprecated upstream(and I guess hence is maintained by Jolla only?)
About the xperia IV et al updates; I bought the 10iv as well, and started to regret it first when i noticed that c2 has a better camera, then when it surfaced that camera wont be working still for a while, namely until sony provides better blobsâŚ
you see where this is going right? I hope I am wrong, but considering the shrinking market size of the xperias, and the current financial trendsâŚthree hints make a proof, right? (I hate to be right btw prove me.wrong please )
Youâre off-topic. Several of you.
I was going to say something interesting about what you have diverged to; but iâll keep it to myself since it is off-topic.
I also have an Xperia 10 V here awaiting to be flashed, if you need help with that
i donât think they need help, but you can test it yourself, well if you can, i could just compile the kernel and compiling hybris failed unfortunately. here are the instructions: Sailfish X Xperia Android 13 Build and Flash | Sailfish OS Documentation
maybe the sources were only partially downloaded, like stated in the common pitfalls, but i donât know
I know. I did it for the Xperia X Compact, so I know how to do it. Unfortunately Iâm currently stuck with Android 14 because I was not able to downgrade to AOSP 13. Thatâs why Iâm waiting for the adaption of AOSP 14 for SFOS for 10 V. Donât want to mess with 14 + SFOS built for 13.
Think it possible to do it with the Emma tool. When I bought the 10v, I did an update and that was fot android 14. I then change to android 13 , using Emma tools.
Unfortunately Emma just for Windows
Works okay with virtual windows⌠vbox or similar.
I tried with Emma. Didnât work unfortunately (downgrading). I know there is a different way, but I thought it might be ok to wait, as support for 14 was announced.
At the time I was starting my journey with sailfish I have a lot of difficulties to get all the stuff just working regarding flashing adb emma etc. All I can say that most of my problems were caused by wrongly assigned/wrong drivers. Despite all of my prievious knowledge with sailfish I started learning again.
Yet never faced info about the tampered software. Imo try as someone suggested. Unlock&Relock device again. Let it erase and try again
Not to be a party pooper, because Iâm aware its brilliant, long-awaited news that the 10IV and V are now supported, but given the following three post excerpts:
Has anyone got SFOS running on a XQ-xC72, or know anything more about that roadmap? I know asking Jolla for a timeframe is like asking how long is a piece of string, but it sounds like there isnât a ton of work involved in the 72 variants now that the 54 images are live. Are we waiting on Sony again? Whatâs the story?
Not using it as a daily driver yet, but I was able to install onto a XQ-DC72 successfully. Needed to edit the flash-config.sh
in the installer to accept XQ-DC72
as a VALID_PRODUCTS
, and update the MD5s to allow that install to proceed (can provide literal steps, if helpful)
For anyone thatâs interested, in Australia, it seems that VoLTE doesnât work with Telstra (tried via Boost), but does seem to work with Optus
Youâre a legend in your own lunchbox, Bruce. I have an XQ-CC72 running Android in Australia on Amaysim at the minute, and am very keen to get Sailfish on it.
Can you confirm what is or isnât working on your phone? Is it the same list as for the 54 variant or are there extra deal-breakers on the 72?
Atm, the dual sim wonât work (I havenât done anything to try and make it work - but it doesnât appear in the settings menu, so just using a sim in sim slot 1).
I havenât tried 5g, so not sure about it.
But otherwise, it just seems to be the expected things, afaict (Although, havenât tried doing a lot with it - so havenât tested extensively)
I also have a 72 variant of 10v with sailfish os. Audio Jack isnât working, camera isnât working, and usb headsets arenât working, but host mode for usb sticks is working and Bluetooth sometimes isnât possible to be turned on. But pure maps didnât crash for me. On the xperia 10ii it often crashed and the browser crashes only very rarely compared to on the 10ii. After boot if i enter the unlock code immediately it takes a few minutes to decrypt the file systems, but if i wait a little bit itâs much faster in decrypting. The 10ii would have had a spinning circle forever if i entered the unlock code immediately after boot
the Android 14 release is not yet available/visible on the sony website; I assume Jolla has been able to ge their hands on some pre-release version?
then again, as releases are per country; this can explain.
But then, if you trust other sites:
grimmer info s come up(like the jan one being the last update for this model??)