Catastrophic 'upgrade'

asked 2019-11-16 14:11:33 +0300

9370 ●150 ●203 ●224

updated 2019-11-16 19:07:14 +0300

The regressions I experienced (as well as many other users) with 3.2.0.12 Torronsuo are so countless I won't list them here. Nevertheless, I eventually 'upgraded' my Xperia X because the previous release (2.2.0.29 Mouhijoki), although satisfying, was highly weakened by repeated incidents due to unsolicited "ssu" mistakes (ssu release status wrongly and automatically changed to 3.x). The device was constantly threatened of self-bricking.

It's probably too late now to consider returning to 2.2.0.29 without serious damages. However, I'd like to ask Jolla:

Are you aware of the multiple problems with Torronsuo?
Are you considering (and able to) reverting to the best previous release? (probably Mouhijoki)
Are you considering assessing/improving your QA process to avoid deploying regressive releases in the future?

Sorry for this rant, but this is the first time I'm so disappointed by Jolla's lack of seriousness.

edit retag flag offensive close delete

Comments

You can try to start all over. Download the newest release from shop.jolla.com/downloads

Maybe alle these bugs are because you made such a huge upgrade at once.

Rudge79 ( 2019-11-16 14:33:05 +0300 )edit

I did so. Same fragility with 2.2.0.29 (after factory reset). Same regressions with 3.2.0.12 (after 3.2.0.12 install)

objectifnul ( 2019-11-16 14:41:55 +0300 )edit

3

Your original issue, "repeated incidents due to unsolicited "ssu" mistakes (ssu release status wrongly and automatically changed to 3.x)." is documented and can be easily resolved by https://together.jolla.com/question/206725/bug-usrlibexecsailfish-osupdateservice-osupdate-check-sets-ssu-re/

olf ( 2019-11-16 15:35:42 +0300 )edit

7

Just to mention, here everything works well and, imho, they made huge progress going from 2.x to 3.x. Now I'm waiting for encryption. One single time an update broke my Jolla 1; had to make a factory reset and applied all the many updates until v3 and it worked again. Maybe the same will help you? Calling them amateurs is a bit bad style imo, rant or not.

chappi ( 2019-11-16 16:00:28 +0300 )edit

2

Okay, I agree. I removed "amateurism".

The way you upgraded is the same I used for my Jolla (not my Xperia), with different outcome unfortunately.

I'm experiencing the same regressions on both devices.

objectifnul ( 2019-11-16 16:11:01 +0300 )edit

5

answered 2019-11-16 22:52:48 +0300

William
1289 ●27 ●37 ●44

I use no patches, and there are/were no regressions on my devices (Jolla C & XA2+). Many things are not perfect, but they haven't just been fixed/implemented yet. My two cents.

edit flag offensive delete publish link

Comments

3

Let's just take one example: what happens when you go to https://duckduckgo.com to search something?

objectifnul ( 2019-11-16 22:58:16 +0300 )edit

@objectifnul - Tried https://duckduckgo.com and the page comes up. ...but it isn't possible to type anything.

vattuvarg ( 2019-11-16 23:34:30 +0300 )edit

4

Ok. Is that acceptable? Wasn't it working fine with 2.2.0.29? Isn't that a regression?

I have so many other examples...

objectifnul ( 2019-11-16 23:37:49 +0300 )edit

1

I'll be happy to test some more. Stuff like that isn't acceptable.

vattuvarg ( 2019-11-16 23:44:22 +0300 )edit

2

Now go to settings->usb and.select "always ask" then connect your device to your laptop. Does it ask as requested?

objectifnul ( 2019-11-17 00:07:24 +0300 )edit

2

answered 2019-11-16 17:44:15 +0300

objectifnul

9370 ●150 ●203 ●224

updated 2019-11-16 21:55:12 +0300

Of course, I'm suspecting some of my installed apps/patches may be the source of the issues I'm encountering (although I'm usually careful on this regard). However, the user (I insist: I'm a user, not a dev or a beta tester) is definitely unable to analyze which apps/patches are poorly designed/maintained and/or which OS features/changes may cause this kind of problems. IMV Jolla should be definitely in charge of that before deploying a new OS release (except EA releases).

BTW I was expecting down votes, no surprise. I'm only interested in Jolla's reactions.

edit flag offensive delete publish link

Comments

1

Why should/how could Jolla be responsible for third-party patches? Patches modify the OS in a non-standard way and you must expect them to fail, possibly catastrophically, at any OS modification. For this reason, I don't use any patch in my systems.

Giacomo Di Giacomo ( 2019-11-19 11:42:40 +0300 )edit

1

answered 2019-11-16 19:48:08 +0300

tortoisedoc

11414 ●172 ●269 ●287

http://kastlunger.blogspo...

updated 2019-11-16 19:49:54 +0300

suggest for you to look for help from the patching community i doubt jolla can be hold responsible for your tweaks (if they are the problem) or for any third-party patches.

edit flag offensive delete publish link

Comments

4

I will. However I doubt patches or «tweaks» are the sources of regression of the stock web browser or android support, for example. Improvements were expected. Regressions were obtained instead.

objectifnul ( 2019-11-16 19:59:34 +0300 )edit

1

answered 2019-11-19 00:46:57 +0300

Mohjive

8581 ●166 ●226 ●250

http://www.y3k.se/

Did you go through 3.0.0.8 as required? There are some "Stop releases" when upgrading from an earlier release, see https://jolla.zendesk.com/hc/en-us/articles/201836347#4.

edit flag offensive delete publish link

Comments

Yes I did. But now this story is more or less over: while sleeping, round about 3am, the device went mysteriously crazy (according to SysMon data collection suddenly interrupted). When I woke up, many things were broken for good. The phone rang, but I couldn't answer. I couldn't send any sms, etc. Ofono was dead.

So I eventually decided to perform a factory reset and reflash the phone to 3.2.0.12 from the latest SailfishX image. Most bugs are still there of course, but the device looks stable.

objectifnul ( 2019-11-19 02:27:35 +0300 )edit

2

@objectifnul so... Your rant was based mostly on a borked installation or perhaps even hardware error?

Fuzzillogic ( 2019-11-19 10:30:03 +0300 )edit

I have two devices (Jolla and XperiaX) both showing same bugs after upgrade. For one of them (Sony), system stability (with bugs, though) was recovered only after fresh reflash. Forensic isn't easy of course, but you can't exclude that the issue is an imperfect port to Sony hardware/middleware.

objectifnul ( 2019-11-19 12:10:02 +0300 )edit

0

answered 2019-11-19 11:05:13 +0300

minojolla
798 ●24 ●43 ●39

https://www.minodesign.it...

What about re-flash from scratch, using the latest image on Download area? You should avoid eventual errors due to too many OTA updates ...

edit flag offensive delete publish link

Comments

See above.

objectifnul ( 2019-11-19 12:00:03 +0300 )edit

0

answered 2019-11-19 13:31:39 +0300

Raymaen

3463 ●49 ●78 ●67

Well i must say after 3.2 my xa2 is finaly usable! I had the O2 provider issues with apps and so on... So the most annoying bugs were solved. And i dont use open repos or patches. This "unoficial stuff" causes issues when not maintained... So now there should be the next step to a new factory restet version for the XA2. My X downgraded back to 2.x something... Well the next uodate will probably have some impact on the browser, and then maybe new factory reset version?

edit flag offensive delete publish link

Comments

afaik, the reset version is never changed! reset version is always the version you flashed. so if you want a newer reset version, just reflash.

misc11 ( 2019-11-19 13:56:44 +0300 )edit

Catastrophic 'upgrade'

Comments

6 Answers

Comments

Comments

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

Catastrophic 'upgrade'

Comments

6 Answers

Comments

Comments

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions