asked 2018-11-09 22:22:26 +0300
Hi everyone,
my Xperia X F5121 offered me an update to 3.0.0.8 Lemmenjoki. Until now I had 2.2.1.18 Nurmonjoki.
My question for people who already updated Xperia X F5121 - should I update now or wait few weeks? I read that on XA2 are some major problems and jolla recommends to wait.
Is everything working correctly on F5121 after update to 3.0.0.8? Are there any problems I should know?
Thanks for replies :)
Malakay
answered 2018-11-11 20:05:43 +0300
Don't upgrade ... unless you feel ok with banana software (riping at the customers).
Sailfish 3.0.0.8 is by no means or any quality standards a safe, well tested version for productive use, even if Jolla claims it's a final release. Read the posts about 3.0.0.X and you will find many annoyances and serious issues.
Of course, many things work, so it may be enough for you, but if you're relying on some special functionalities, then better wait one or two iterations more. And no worries, there haven't been any "revolutionary" improvements on the user side (not to mention the more or less failed new top menu).
Good luck anyway - with upgrading as well as with waiting...!
answered 2018-11-11 23:15:39 +0300
So, I decided to update. I found few problems:
1) new reworked top menu is something I dont like. It looks very similar to Android and that is thing I really dont like. That old fullscreen half-transparent top menu colored according ambience was much better. And fullscreen top menu was better to. But this is something I can live with.
2) update deleted my own ambiances, no big deal, but it surprised me in negative way
3) I really HATE that stupid lock on top of top-menu. It is only taking place which could be used for more shortcuts. Definitely would be needed option to remove it.
4) my favourite patches dont work, but I suppose it is not a big deal, just waiting few days until patches authors make an update :) (namely "always show close icon", "hide recent contacts")
5) one more negative thing was that update reset top-menu icon settings, so I had to set it again.
When I find more, I will write here.
Have to say, I very much agree on 3. To me, it feels both archaic and redundant, considering the power button serves the same purpose. There may be some rare use cases (like using your phone while lying flat on the table, etc.) where such a button might serve a purpose, allowing one to lock the phone while not having to pick it up, but for met at least, any potential benefit is outweighed by the loss of otherwise usable menu space.
An option to remove that lock would be a welcome addition for me. Alternatively, the menu could be set-up as to not show the lock button during the initial swipe down, giving people more menu options, then allowing a secondary drag down to select the lock, similar to how Sailfish handles context menus in apps. By going that way, we'd have the best of both worlds combined.
So, one drag down would lead to a now larger menu, two drags (or perhaps one prolonged drag) would lead to the "Lock button".
ChrisX ( 2018-11-12 00:16:36 +0300 )editI use the lock button on the top menu all the time. Having had devices where the physical button broke through overuse I use it as seldom as possible. And I think the whole top menu is a big improvement.
Now - can we get rid of pulley menus altogether? From reading here I get the impression they're mainly for use one-handed. Which I just never do.
Which just shows that everybody is different and everything should be configurable.
DaveRo ( 2018-11-12 09:13:40 +0300 )editSee my proposal for removal of the lock button: https://together.jolla.com/question/191645/feature-request-lock-phone-immediately-when-swiping-down-from-corner/
Giacomo Di Giacomo ( 2018-11-12 16:58:10 +0300 )editanswered 2018-11-11 19:47:45 +0300
Don't update. USB tethering doesn't work anymore. My computer does not connect to my Xperia X hotspot either.
I really don't have any use for a phone that can't even function as a source of an internet connection.
Edit: And after the update, I can't even fucking find the folder for Android apps... How the fuck can one update make things so hard?
Well, USB tethering was my fucking lifeline and worked flawlessly. I got Wlan working to some extent, but it disconnects all the fucking time. I can't do my schoolwork, I can't listen to music, I can't play dem vidya gaymes... I can only do things 10 minutes at a time until it disconnects for another 10.
Mukaparska ( 2018-11-12 14:09:13 +0300 )editWell, I believe the Wifi issue is with my PC and the USB wlan receiver thing, and not my phone. Still doesn't really change the issue anywhere.
Mukaparska ( 2018-11-12 15:40:08 +0300 )editanswered 2018-11-12 17:49:25 +0300
Three examples of useful screens that are no longer available with 3.0.0.8. Compare with what you get after "upgrade". I think it's self explaining.
(Pardon my French...)
Having an extreme use case (this looks like >150 apps) and a high level of customization by open-repos apps you naturally risk suffering from changes, at least much more than the average target audience of the developers. Don't know if you can blame them for it.
Spark ( 2018-11-12 20:42:56 +0300 )editIf I understand you correctly, you suggest that SFOS is not for those silly users who want to install native applications.
objectifnul ( 2018-11-12 20:53:08 +0300 )edit@objectifnul I think you understood well but decided to unneccessarily exaggerate the statement thus perverting it.
Maybe a car comparison helps: You customized your front lights and the manufacturer made a facelift. You buy the facelifted car, but sadly your customized front lights don't fit anymore, because the company designed towards what they thought the target group's taste would be...and couldn't consider the needs of customizers.
Spark ( 2018-11-12 22:13:39 +0300 )editI understand. However, an operating system is not a car: it's supposed to evolve and to last much more. That's why backward and forward compatibility are so important.
objectifnul ( 2018-11-12 23:58:30 +0300 )editanswered 2018-11-13 18:15:16 +0300
I really love SFOS3. I watched a local icehockey game when the update notification popped up and i decided to try an ota update right away. It took me 20 minutes to download the package, but the process worked perfectly, if you read the manual carefully. It took a couple of days to get used to the new UI, but in the end, it works fine. I have no issues, i hadn't before with SFOS 2. Like many others, i miss swipe gestures on app tiles, but the buttons work for me. The important thing is, i can control my apps without going to full screen.
If i got the changelog right, changes affected the OS-Core and not UI. This new core/plattform is the first step Jolla will build more changes on and i'm really looking forward to the next release
My Baikal-sync(CardDAV/CalDAV) is perfectly working (my own server on raspi in home network), all of my Android-Apps(threema, local traffic company apps, here maps) are running and the UI feels way more responsive than before. Battery life is neither better nor worse.
Wifi-Hotspot seeems to work for me as well.
The new top-menu is an element u have to get used to. I still swipe to left or right to access settings/top-menu from It makes access to e.g. bluetooth-settings access pretty fast by long-pressing the top menu icon and i need that, because my headphones connect automatically but work only, if diconnected and reconnected again manually. The top-menu ui elements can be choosen from settings and i'm now using the same menu as in SFOS2, but i can get it anywhere
Virgin SFOS user here, on XA2.
After quickly learning the ropes, this is a pleasant system to use. A keeper really!
Only gripe is the browser, which I think is very mediocre in performance. I use browser a lot commuting, so I hope it gets developed more actively, or at least I can get a better one after the paid version Android supported is live for XA2.
MyShipMyRulez ( 2018-11-13 21:35:05 +0300 )edit@MyShipMyRulez Even though I also hope the default Sailfish OS browser gets updated (BTW, the browser is open source, so contributions are possible), I can confirm Android Firefox works fine with the built in emulation layer on my Xperia X, so should work as well on XA2 once Androied emulation is enabled.
BTW, there is also a community developed native web browser called Webcat: https://openrepos.net/content/llelectronics/webcat
MartinK ( 2018-11-14 03:02:20 +0300 )editanswered 2018-11-09 22:33:36 +0300
I use 3.0.0.x since day one and I haven't noticed any problem.
You should just search if your patch work in 3.0
answered 2018-11-12 10:03:07 +0300
It's not a bad update. The performace is much improved especially on Xperia X. I encountered no serious bugs. The configmenu from the top is a mixed bag. Personally, I would have chosen a different road but I guess the customers (not you and I, the big investors in Russia and China) probably prefer a more Anrdoid approach so I guess we will see more in this direction. If you can swallow this, the rest is a solid release.
actually it's better than the android top menu because in SFOS it can be triggered from anywhere in the screen, not just the top edge (unless you are inside an app). In Sailfish OS 2.0 it might have looked better with the ambience style but you had to swipe at least twice to find it, which I hated. I guess you can't please everyone...
thisisme ( 2018-11-12 14:24:51 +0300 )editUpdated Xperia X from 3.0.0.5 to 3.0.0.8 and noticed that when I pull the top menu and try to swipe it back up there is a lag (like the whole image moving in a frame) and I need a second swipe to hide it back up. That was not an issue with 3.0.0.5 on Xperia X. So two swipes up to close the top menu back up... Not intuitive. I don't like it! Had to delete the brightness to shorten the top menu so I can use one swipe back up to close it.
777 ( 2018-11-12 21:21:48 +0300 )editanswered 2018-12-24 09:30:43 +0300
So, did anyone found some solution to remove that stupid lock icon from top menu? I was doing some research, but found nothing :(
Though I like the quick access top menu, I have not figured out the sense of the lock, either. This one, I never ever use.
Kopekenscheich ( 2018-12-24 17:12:19 +0300 )editanswered 2018-11-11 22:48:02 +0300
I had no issues with my F5121 in a technical way. If you want to see the new UI features and you are not reliant on USB tethering, then update. Some other minor glitches, e.g. ambience sound settings, in the early access 3.0.0.5 were resolved. The bootloop issue of the XA2 installation package under windows doesn't occur on the Xperia X to my knowledge.
If you're not keen to see the updated UI, waiting is also not wrong and probably never a wrong choice for new main versions of software. But your (muscle) memory will have to learn the new top menu one day anyway ;)
Asked: 2018-11-09 22:22:26 +0300
Seen: 3,837 times
Last updated: Dec 24 '18
imho u should update. It's noticeably faster, nice UI improvements. Only downside i've experienced is that scrolling through long lists of images is not really fluid now. But it's minor
virgi26 ( 2018-11-09 22:29:09 +0300 )editI have that same model and upgrade with the early release and the 3.0.0.8 release and think it is worth it. The XA2 is new hardware so yeah some bugs to work out the X F5121 is worth the upgrade its like a new phone again :)
marxistvegan ( 2018-11-09 22:48:17 +0300 )editOkay, how long does update take? Will it keep my messages, gallery and data on internal memory and SD card? Do I need to backup something? and what about enabled repos etc. ? will it keep everything on its place?
Malakay ( 2018-11-10 00:02:45 +0300 )editand one more thing - I have 1 very important android app for checking service intervals on my car. Will the app stay installed and with all data it has before update?
Malakay ( 2018-11-10 00:10:54 +0300 )editAfaik, since 3.0.0.8, my phone gets really hot and the accu is draining.
Moo-Crumpus ( 2018-11-12 12:23:41 +0300 )edit