Jolla Phone : First Experiences, Pros and Cons

This idea is not so bad on second thought. I could put the phone in between my sword and my battle ax. Or on my ammunition belt. :wink:

That’s actually super cool. I thought of setting something like that up in Automagic but this is even better.

Just before someone asks, if mcetool is not installed (which is likely the default) you can install it from the terminal:

devel-su pkcon install mce-tools

Old gas mask bag has worked just fine for me so far. (True story, no sarcasm here)

To me as investing in the new Jolla Phone as my main driver I find these bluetooth problems very worrisome. I really want to love this phone, but as it got launched I find it a little difficult to compensate with things like the bad camera and also bluetooth now. Things I would had thought would work out of the box by now, also given the pricetag on this phone. I have a lot of bluetooth devices I use everyday, from car to earbuds. I would imagine getting pretty frustrated with it not working on a every day basis. I just thought we would had come a longer way. Since it’s their hardware and they have been going on since 2013. I got some thinking to do…

For what its worth, I haven’t had any issues with my earbus yet. I couldn’t connect them with the app yet (for updates), but the android bt support is still beta so I guess that could be fixed later on.

Those are mostly a software issues. So fixable in time. Better question is: ‘when?’.

You might have had wrong expectations. The camera hardware isn’t great but it isn’t bad either. The camera software was always going to be on the slim side. So rather light on the “computational photography” front. You know, iPhone and Co images look so great because the camera app is border line inventing stuff. You can really see that in edge cases where images start to deviate wildly from reality. You are pretty safe from that on the Jolla phone. On the other side, bad light and extreme dynamic range will lead to bad images. However, you can totally shoot beautiful pictures on the Jolla phone. It is pretty much like a good budget / okish entry mid segment phone camera. As expected.

Regarding bluetooth, this is a new feature so things are hioefully getting better soon. As a native user, bluetooth is working fine, but I understand that for Android app users that might nit be the case.

I feel you with the Bluetooth problem. But we are about the first 1000 person who have this device now. Jolla employees have been on summer brake. They have set ambitiuous goal for next year to sell 50-100k more Jolla phones. So rest assured, I’m sure Jolla will give love to the Jolla phone when they return from holiday and have really ramped up the production

I’m terribly sorry about spamming on this thread. I hesitated to make a separate thread spamming the whole forum.. :grimacing:
However, as enjoying my new Jolla Phone I’ve experimented a little bit with the camera.

Photo represents the Sea Quarters in city of Mariehamn in Åland islands. I have not manipulated photo much, a little bit added vibrance to colours but not much and that’s about it!

This photo with weird grey shade at the top is meant to be a background/ambience for the new Jolla Phone, so please feel free to try it out if you want :slightly_smiling_face:
It should work and play nicely both horisontally and vertically.
Resized for the Jolla Phone (2272*2272 pixels). Will most likely look weird in other phones than the new Jolla Phone.
Enjoy!
(If you want to try, just download the photo to your Jolla Phone and tap “ambience” symbol while the photo is opened in Gallery app)

And let’s put another here too:
This one is also with my Jolla Phone and is taken of a door of a boat house in Eckerö, also Åland islands. I have added quite a bit vibrancy to the orange tones, them I couldn’t get that vibrant with WB settings of course. But otherwise quite straight out of camera.

ps… @Jolla …sorry about putting Jolla logo there without asking first. I can remove it if it wasn’t ok. Thought about using Sailfish logo instead, but I just like the Jolla logo so much :slightly_smiling_face:

Place links on the map:
Mariehamn:

Eckerö:

I’ve been using the JP2 for about a week now so I’d like to share my first experiences as well.

Let me start off by saying I really like this phone. I’ve been very impressed that they managed to deliver it in the short time frame that they set out initially. I did not expect that.

I’ve been using Jolla phones since the first one in 2013 (but I have no experience with the Nokias that came before that). I’d say my best experiences were with the JP1, the initial Xperia X and the XA2 (except for the GPS).

I do switch to a GrapheneOS device now and then but spent most of my time on SFOS. I’ve also written some apps to scratch the itch of missing software and I did notice some of them are in dire need of updates :sweat_smile:

Anyway, the pros:

  • The phone looks really nice,
  • Getting GPS fixes with “High-accuracy positioning” is quick and navigation (mainly with Waze and Organic Maps, both Android apps) works fine,
  • The pictures taken with the camera are much improved compared to earlier phones, especially the late Xperia 10 line, and low-light performance is much better. It’s still not great but I do not feel the need to bring another phone or camera with me anymore,
  • Some Android apps that didn’t work in the past now work with the updated Android version,

The cons:

  • The camera is still too slow slow to start up and focus, especially the focusing is annoying,
  • Automatic brightness adjustment is too bright even at the lowest setting,
  • Sometimes apps (also native ones) don’t want to start up any more and I need to reboot, I’ve not looked too deep into this but killing the existing processes didn’t seem to help (this has happened about three or four times now),
  • Android connectivity seems flaky (I’ve only used “Treat mobile data as WLAN” so far) but it seems to be mainly with the Ironfox browser, so this might just be on me,
  • Connecting to WiFi captive portals is flaky (even with the CPH app),
  • I’ve never really liked the default browser and the current one still doesn’t really click with me. It is also laggy, it seems like one bad tab can affect the whole browser,

I might have more cons than pros but these are just the biggest things I run into. I couldn’t list all the things that I like and that work will :wink:

(I run without microG and Bluetooth.)

The bug of only being able to run one noarch app at a time plays a part here perhaps?

It’s just if you do a just a little research on the forum, I can see the bluetooth problem has been since the beginning of sailfishOS (as I read it) then the update came with the AAS bluetooth, and people where positive at first, but ever since the release though, nothing has worked properly. First the camera, then calls, now bluetooth. It’s just a big pile of compensations you are already doing by switching from the “big duopoly”, and people tend to forget how essentiel your phone is now-a-days to have a functional work/life. I have to be able to take calls, recieve sms’ etc, nomatter where I am in the world. (Because of work)

Now I am just afraid that this phone can’t handle my needs. And I am not talking about all the Android stuff here. I am just talking about proper phone usage.

I am also living in Denmark, so I also have to give up the application of MitID in favor of another hardware device I have to bring along with me every where, just to get away from google. And I hate it as much as everyone else. But to be fair, with this pricetag (6000dkk) I am especting my basic features of the phone to work. So, these first experiences people are having, makes me worried I made a bad deal.

Don’t understand me wrong, for me the AAS bluetooth has been great plus! And with Xperia bluetooth worked for me perfectly. I understand that there is problems with anything fancier than Oura ring and headphones, but at least basic things has worked smoothly and will work for sure soonish. Have people had problems with call with Jolla phone? I saw some 2g thread, but it sounded at least partly carrier thing. What do you mean with camera? Sure, it is not the best, but upgrade from Xperia 10 III for sure! Or do you mean the dust problem?

But yeah, people have different needs for phone. Everything I need work, expect the Bluetooth reliable and Here we go (well technically I also would like to have Microsoft authenticator working, but with 10 III it just started to send the popup notifications. I’m waiting same miracle). I assume, these two bugs are the reason: Jolla Phone (2026) Bluetooth crashes randomly - #15 by CLMA31 & [5_2_0_16] [JP2026] Graphics engine bug in AAS? for my two problems.

I can workaround through both, as I don’t mandatorily need Bluetooth as long as it still kind of works with Oura. It would be VERY nice to use headphones, but I can live for a while. For Here we go I replaced with comaps for now. I’m heavy phone user in traditional sense, I don’t tinker around or like it particularly. But I really need to have device outside the duopoly and I’m sure Sailfish will be much more polished in a year. For me the 500€ investment was more than good deal. When looking year back, Sailfish has taken major steps forward and I don’t think the phase will slow down :slight_smile:
If you feel like these current bugs annoy you too much, maybe switch for a sec back to old phone? Then when you see next version releases you can check if things have gotten better and hopefully bugs that bothered you are fixed

Ye, I hope you are right. It’s just a lot of things and Jolla is a small team. I ofc hope the community enters the development to speed things up. The reason why I change my S22 ultra, is because it’s battery is getting bad (can’t hold a day) and S21 stopped getting security/regular updates from this year, so I gues my phone will be next.

What’s the problem with HereWeGo and with Bluetooth? I had two small issues so far with HereWeGo (once while downloading offline maps, and once the the app got stuck immediately after launch when trying to get th position).

Also Bluetooth works, the connection problems with my car are gone compared to 10 III, so no restart of Bluetooth service via utilities before gettimg in the car.

MS Authenticator will be interesting as notifications don’t work on 10 III, I’ll just set it up on Jolla Phone.

HereWeGo just freezes for me quite often, lags a lot, can’t really use it for navigation. For bluetooth I can’t see anything at the setting page. So even if could connect to my headphones there is no GUI. But I assume it is just pretty broken currently as it crashes often and never after bluetooth restart I have been able to collect bluetooth beacons with Stumblefish. Maybe a little bit hit or miss currently? Don’t want to do factory reset just for fun when other have reported similar problems :smiley:

MS authenticator just started to fully work with my 10 III, don’t know what happened. I hope same miracle happens with the Jolla phone xD

I received my J2 today. So far I noticed the following problems:

  • using the Browser hard locked the phone several times (no response to taps, slides or buttons, had to hold down the power button until the phone reset) (edit: this was caused by a specific configuration of my own web server and a typo in the URL)
  • Here We Go stops updating the screen after it’s been running for a few minutes (it’s not locked up – if I slide from the side and back, the screen updates)

No other problems so far – bluetooth headset (Yealink BH-51) works, as does Aranet android app for connecting to the CO₂ sensors; Microsoft Authenticator works, however when I was registering work accounts, it always showed “Code already used”, as if I was trying to register each code twice; I did also have to update Aurora Store from F-Droid before I could log in.

How about dust in the camera lens?

Ah yes, perhaps. But it only starts acting up after a while.

Also, replying to another post, I do seem to also have dust build up in the selfie cam. (But I never use that so :person_shrugging:)