Not sure this is new for JP2, though. Had this on C2 with VoLTE until I switched the SIM over to JP2 as well. Especially if reception is half-bad like in my office. Same carrier.
“switched sim” as in moved to slot #1? (i have it in slot #2 btw)
No both used the SIM-card in slot 1
dang. sounds like a reception issue; however the cell tower is like right next door.
Yes, most probably. For me it is like 2-3 dm between ok-ish and non-existent
The Jolla 2026 has been a pleasant experience for the 5 days I now have used the device. Snappy and no major issues. I was a bit skeptical reading the sub par experience with more recent Xperia devices. But this feels like a true successor to the Jolla 1. My last device, the Xperia XA2, has served me well, but SFOS 5.1 release caused me real battery drain issues. Hope to enjoy this devices for the years to come with more software updates to iron out small issues.
Interesting I installed the stock “media” player and I really love it. Yes it is simple but that’s what I love. It works great with my well annotated local music library, automatically sorted by albums and artists, showing the album cover art. When opening the album it shows the cover nice and large. It also works well when turning off the screen and offers controls with a locked screen. Not much to learn either.
For browsers, if you are not intimidated by its installation process, you can give Angelfish a try. I think it is the most capable browser that runs natively, even if the notch is a bit in the way.
I actually found music player that I like, harbour-unplayer from openrepos. I will check out that Anglefish browser, thanks.
Doesn’t Firefox (Android) work better than the native browser?
It seems like there are a lot of SFOS “quality of life” improvements that all the old users know about, but few of the new users have found. It would be really great if someone could make a list of all those (probably needs to be on a wiki), unless someone already has done so?
No, I think the problem is they expect it to exactly fit their needs straight away, with little to no effort on their part. In any new OS you need to spend time to work out how to make it do things differently, what are the options you have, how to customise it, learn to work different ways than before, etc. A new OS won’t feel comfortable or even usuable straight away. That may be especially true of SFOS, as it works quite differently to Android & iOS, and a lot of customisation options are hidden on the unofficial app stores…
And then the new Jolla 2 phone seems to have some rough edges (which personally I was expecting as an early adopter), which Jolla will hopefully fix sooner or later, e.g. some performance issues, and a few reliability issues. These don’t help of course, but just be patient, it should improve with time.
Also, in my mind part of the joy of Linux is that it may not do exactly what you want, but there’s usually a way to customise it how you want, sometimes with a little or a lot of effort. You are the root user, not Google or Apple or Microsoft! Just be careful when fiddling…
Maybe I should write a bug report, but before I do that, a quick question. For the third time in 10 days, J2 was unresponsive when trying to wake up the phone yesterday. Much to my surprise, I was able to ssh into the device, which then “woke up”. Has anyone else encountered something similar?
Yes, both IronFox and Brave work fine under aas.
I’ve had mine since the Day1, and only slightly similar occurrences I had with double tap waking up activating in my lap pocket when walking.
This lead to J2 to accumulate a lot of touch based interactions that started to unravel when I opened the device. After a second or two of panels opening and closing (toggles as well) this settled down.
If your problem is triggered by doubletap wakeup triggering too easily as well, you could try disabling it for a few days test.
Some experience taking a longer drive to the beach yesterday.
Navigation using Waze (AAS) was ok, not great, it was a little choppy with my location updating only after 5 to 10 seconds sometimes.
Then I used another AAS app for parking (EasyPark / ParkMobile, this didn’t work on older SFOS phones but now it does except finding my location).
Spent a few hours on the beach watching the eclipse. Then when I wanted to use the parking app again I had no connectivity inside AAS, so I restarted it. Then everything worked again.
Navigation on the way home seemed less choppy.
Where is the setting to deactivate double tap? I can’t fi d it. Thanks!
I guess there is not a setting for it…(?) ![]()
Maybe post a feature request about it?
(but do search before posting that there isn’t already a post about it)
Install mce-tools then:
mcetool --set-touchscreen-gesture-actions=doubletap
(to bring it back: mcetool --set-touchscreen-gesture-actions=doubletap,unblank)
Why did you erase usefull comment?
As user did already ssh to phone and he will know how to install ![]()
pkcon install mce-tool
And confirm with security code.