hello, i hipe this is right forum section for this question. on many websites there are messages, that the browser is not compatible. are there any plans for update the browser, and what is planed with new Jolla phone?
An Update of the Browser to ESR 102 (i think) is in the works. Browser version is not tied to the device, so for Jolla Phone 2 it will be the same
ok. thanks for info. but why ESR102? this version is already too old. or do I not understand something?
I guess because the âsailfishificationâ process takes a very long time and the ESR release schedule moves far quicker than Jolla can realisically cope with. ESR 102 went out of support in September 2023 I believe, the oldest ESR version still in support now being ESR 115 until March 2026.
Jolla is therefore always playing catch-up. Probably a different approach for the browser is needed, one where Jolla has to do little or no work to get it to run, or to maintain it at modern versions, on Sailfish.
Have you tried Angelfish?
Not yet, but then I will try soon. Thanks.
pls search before posting https://forum.sailfishos.org/t/browser-soon-incompatible-with-sailfishos-forum/24652/4?u=rgrnetalk
I really tried, but didnât find this thread. But thanks ![]()
For a very in-detail answer to this, read
where Flypig explains in detail his efforts that lead to the current SFOS browser, based on ESR91.
The introduction also covers why it makes sense to go from ESR to ESR and not jump over a release.
Wow, for that story in the blog I would need some time and popcorn ![]()
![]()
Angelfish qt6 Version is a little better than stock browser. But not official yet. Will probably come to storeman in release 5.1⌠Unofficial version is possible doing special things in terminal, description can be found in other threats. I already have it in oneplus 6.
Otherwise still the best way is AAS (android app support) with regular Firefox. Or with waydroid.
looks like mostly onemanshow.. is not very goot to know that. why even mostly every linux fistro can provide fresh update within days or some weeks⌠I mean, this is like basic scop of every OS to have actual browser. and yes, it donât need to be always the latest onr, but security fixes are anyway important.. I hope this will be better in the future.
I read through flypigâs dev diary. Still, a possibly stupid question: wouldnât it be easier to follow the path of other mobile distros and use standard esr firefox with mobile-config? Or is SFOS so much different from other distros that you canât build firefox without major stumbling stones?
Not until Sailfishâs compositor is updated.
Just so that I understand correctly, that means updating Qt and lipstick, right? Or am I thinking something else here? ![]()
Answering kind of to my own question, here was good summary of current situation and plans for future: Sailfish Community News, 13th November 2025 - xdg-shell. Still I am not quite sure if only updating Qt and lipstick would improve situation, my guess is there would be additional steps also to do
Can a normal user update the compositor manually by CLI without waiting for Jolla?
A normal user? What is a normal user? I asked the question and here is Jollaâs answer: Sailfish Community News, 13th November 2025 - xdg-shell
If you program it first then yes. (It doesnât exist yet!)
Itâs quite a unique experience to buy a brand new software licence and endup with a merely abandonware that struggles to break through internet⌠even to display the official customer care after-sale service forum.
I have plenty good feedback to write about my recent switch to SailfishOS, but this point is hard to believe if youâre not experiencing it yourself.
The Delta-Chat client allows to decide to use a fancy background or a distraction-less solid color.
I was scouting through the settings about a way to disable the âtransparencyâ of menus in SailfishOS. I would rather get rid of the proprietary compositor. One more reason if its the obstacle before an updated web browser.
\[Edit thanks to answers\] just non obvious UI
I would have like to rant about the search feature, because it is locked with GAFAM engines breaking the Jollaâs promise of privacy⌠I pay for Kagi search, I pay for Jolla licence, and all Iâm left with is a closed list of ad-driven search engines. Isnât it surprising ?
My last expectation regarding the browser would be to have support for WebExtensions (specifically uBlock origin) and not only because Iâm a WebExtension developper ![]()
(ah eh, the mandatory white background of a new tab, even in dark ambiance, that wakes up mates at night, it can wait an updated version ^_^).
What are GAFAM engines? You can use any search you want with the browser. Visit the website you want to search with and you can add it to the search engines. Apart from this, yes, the browser is unfortunately somewhat crippled.
