Re: sailfishOS Upgrade12 discussions
 

Okay, understood.

Re: sailfishOS Upgrade12 discussions
 

i wonder what was broken, been using this update for a few days with no noticeable issues

Re: sailfishOS Upgrade12 discussions
 

Well. Here is one developer who opted-in, but despite that NEVER get any notifications in any other way.

And yes, the update is faulty!

While one devices updates without issues, my other device always fail if it is not factory reset first.

Re: sailfishOS Upgrade12 discussions
 

Don't they have the opt-in program _exactly_ for this?

Ahh.. now I get it. So we need a new opt-in to the existing opt-in program... er.. wait a second.

Re: sailfishOS Upgrade12 discussions
 

On other hand it may help some people to learn and understand system better. I think most people learned linux that way, by testing and trying, and yes by making mistakes and fresh reinstall. Let's compare it to not official ppa's or beta releases for Ubuntu, some people can lock those and tell people to use only official repos as they might break system. But as we see information is public for everyone and its what makes community stronger with testers, people trying and learning on mistakes, who can after help others. If you think devs need separate opt-ins you are welcome to ask jolla, but to hide from others and make private groups is just unfair. And i'm pretty sure people who know about those updates shared it with less tech educated people, so why some are worth to know and others are not? Or we in hype of invite only elitism?
I think it's bad enough that jolla has no public roadmap and mostly things are developed behind doors.
You may disagree with me, but the fact is that maemo had strong community, where a lot of noobs became great devs just because people shared info, helped each other and not told you to "sit back and wait till you windows finish the installation". We already see that a lot of those devs abounded ship, because of elitism, closeness and lack of info from Jolla, now you want to prevent new generation from learning. If so, than stop asking why people want everything ready and out of box working and whine, coz the reason is that you force them to. Give the man fish or teach him how to go fishing...

Re: sailfishOS Upgrade12 discussions
 

Multiple levels of opting in?
1 Core software / patch developers
2 Userspace app developers
3 Really enthusiastic enthusiasts with cavalier attitudes
4 Chilled out enthusiasts
5 The paranoid-but-nosey
6 Dave999
7 Public release

And I don't want to prevent anyone trying anything, it's just sometimes people post the steps to switch update sources without any disclaimer, and not everyone understands that it's not finalised software to the level of testing that might be expected, and then they're forced to become a fisherman to fix their phone, and not everyone wants to spend the day smelling of fish. Hmm this analogy might be breaking down...

Re: sailfishOS Upgrade12 discussions
 

Not sure what's going on here.

1. Jolla leaked it via there official servers?
2. It's Available on the Web?

I might have missed something But why can't jolla just stop Rollin out the update? and limit their own mistake?

Re: sailfishOS Upgrade12 discussions
 

Same here. Other than a few patches from Coderus not working or applying, I haven't found any issues. It feels very stable and smooth and performance has improved once again. On my dad's Jolla it's the same: no noticeable issues, all running very stable.

Of course, there will always be exceptions. But for me and my dad, this 1.1.4 is running great so far for a few days now :)

Re: sailfishOS Upgrade12 discussions
 

Hello. Where can i install new OS file system,how can i update?

Re: sailfishOS Upgrade12 discussions
 

1. Not leaked, published. And, rolled out accidentially, causing half-updates for poor pple who did pkcon update in terminal.
2 Its available by 'hack' (=force version update)

And, I take my words back around coderus

This update can most likely break many things

Eespecially, but not limited to, if you use certain apps from warehouse, possibly even just by having warehouse installed.

This observation comes from installing it on my two devices.

1. will always break, and wont repair unless factory reset, after which it can update.
2. second device updated flawlessly - it never had the touch of any warehouse or openrepos stuff from there.

While I do think all should have the optione, I also strongly discourage new and inexperienced users to even think about this 'hack' update.

Re: sailfishOS Upgrade12 discussions
 

This has been discussed many times before, & in great detail by now, we're going in circles again...
We clearly need at least 2 levels of opt-in, the hardest core one should probably be via verification only.
Something roughly analogous to what vitaminj just outlined, I wish it was implemented by now, it should be piss-easy.

Re: sailfishOS Upgrade12 discussions
 

But according to the TJC thread, only if you have ssu release set to "latest", whereas using my massive sample size of 1 (me), people who've only ever done official updates have this set to the update they're on (i.e. "1.1.2.16") so won't get an update.

Am I right? Is this only going out to people who've used this same trick before?

Re: sailfishOS Upgrade12 discussions
 

You are right. Absolutely. And tada, this is how these update 'leaks'.

Re: sailfishOS Upgrade12 discussions
 

What? Rollin out software by mistake? LoooooL :D how is that even possible?

Re: sailfishOS Upgrade12 discussions
 

well.... by

MISTAKE

No (10 chars) badly configured update methods.
Which, like Jalyst have said. Could easily be 'fixed' :P

Re: sailfishOS Upgrade12 discussions
 

I don't think it's possible. I think peoples who "got new version just after using pkcon update" are just lying. If i'm wrong, then Jolla really did something really wrong :D

Re: sailfishOS Upgrade12 discussions
 

seems that some had ssu re response with 'latest' as opposed to specific version number.
I suppose this was somewhat intended for those who 'opted-in' but now seems like something went wrong at Jollas side when publishing pre-pre-releases before they were intended to ...

Re: sailfishOS Upgrade12 discussions
 

I haven't found any app in Warehouse that didn't work, every app that I use from Warehouse (quite a lot, TBH) still work correctly on 1.1.4.24 on my Jolla Phone. And a lot of patches still work too.

Haven't updated to 1.1.4.28 though so can't say anything about that yet.

(oh and btw: I'm an everyday user who likes early access to software versions, I'm no dev or anything)

Re: sailfishOS Upgrade12 discussions
 

So what is 1.1.4.24...The one that Jolla leaked? And then trying to fix their mistake with another leaked update 1.1.4.28?

Re: sailfishOS Upgrade12 discussions
 

i assume the opt in people got moved to latest when they opted in, but were never moved back to a stable release?

Re: sailfishOS Upgrade12 discussions
 

The different OS versions have different repositories. A "pkcon update" does not update anything of the OS unless you reconfigured ssu to point to "latest", which may be as the name suggests a symlink to the latest repo.

Release candidates are dangerous because they may still contain issues that brick devices (or at least require a reset to factory defaults, or some good Linux skills to fix).
For every release candidate that did not become a release, there is at least one critical known bug.

Release candidates generally do not get further update notifications, so you cannot update them through the UI.

Re: sailfishOS Upgrade12 discussions
 

Verification of what? Geek card?

The current opt-in is an extension in that it allows you to get updates even without enabling developer mode or 3rd party packages (which usually put your device into "you're on your own" mode regarding software). If you've already done either of these two, then why do you need to do any additional opt-ins? You could already fsck your boot by installing some packages, or even entire releases you just built yourself from sources..

Re: sailfishOS Upgrade12 discussions
 

This is unofficial pirate version with backdoors and a lot of bugs stealing your personal information and sending your private photos to china servers.

Re: sailfishOS Upgrade12 discussions
 

Read my post in the context of some posts just before it. This makes a fair amount of sense...
As does this....
One smaller opt-in or more, before a much broader opt-in for more general users/devs...
A group (or groupings) of users that have a different level of access (via Jolla acc'ts?), to one or more earlier opt-in channels.*
The next hop after that opt-in or opt-ins, could be open slather to as vitaminj says: "Really enthusiastic enthusiasts with cavalier attitudes"

*channel[s] that aren't just for anybody who happens to stumble across the right info.

Re: sailfishOS Upgrade12 discussions
 

Is there a way to see the changlog of 1.1.4.28?

Re: sailfishOS Upgrade12 discussions
 

The only one: wait for official release and announcement.

Re: sailfishOS Upgrade12 discussions
 

How and where can I see if the release is actually a real release or just another official leak? (version wise)

Re: sailfishOS Upgrade12 discussions
 

They will announce it on their twitter feed and on TJC, as per usual.

Whatever version they end up on will be up for a while while they test it, then when they are happy with it they will flip the switch (and upload the all-important lake image and release notes) to let opt-in users grab it through the normal sailfish update settings panel.

Re: sailfishOS Upgrade12 discussions
 

The ones you will receive in Settings - System - SailfishOS are official. Also a notification appear. All other are fakes or leaks, don't install it!

Re: sailfishOS Upgrade12 discussions
 

After the update was downloaded, but before it was installed, do
and have a good read, or wait for the official changelog on together.jolla.com. :)

Re: sailfishOS Upgrade12 discussions
 

The update lake of eastern was in release candidate phase one month ago. Now, one month later is still nowhere to be seen. Not even for opt-in. Marc said weeks, it's now months. To me it's always nice by Jolla to iron out bugs and issues but I wouldn't mind atleast update regarding progress like they did when they had issues while trying to improve the memory handling in previous upgrade The final sw would probably drop to my phone sometime in may at the same time as sail 2.0 will be available.

Re: sailfishOS Upgrade12 discussions
 

You are way too optimistic if you assume that Sail 2.0 will be available in May. At the current rate, the more realistic estimate is late August. Unless they take another well deserved break. In which case, October. Maybe.

I think the problem is they try to make monolitic releases. There is nothing to stop them releasing updates to e.g. Browser or Exchange independently from the core OS but for some reason they want to dump the whole shebang in one go. Smaller incremental releases would give a better illusion impression of progress and keep noisy and inpatient customers like Dave999 happy.

Re: sailfishOS Upgrade12 discussions
 

I totally agree, not particularly for new features but at least for bug fixes. The current status of the calendar and the synchronisation with Google, is this is pretty unusable. A shame for a smartphone. Some fixes are already commited upstream, so it's just up to Jolla to spread them.

Re: sailfishOS Upgrade12 discussions
 

Honestly, Jolla release is just a mess.
I also own a BQ device and moving to a developer channel is very easy and allow everyone to follow up to date progress.
So you can, either be on a developpers channel, a rc channel or a release channel.
It is up to you to choose the one you want.

I found this is something really great from Ubuntu and on which, Jolla should take example.

Re: sailfishOS Upgrade12 discussions
 

You know me. Always too optimistic until proven guilty.

Channel like a "branch" or like an IRC channel? But you still have to do manual updates?

Ok...you are talking about image channels.
https://developer.ubuntu.com/en/star...mage-channels/

Can you preselected channel and then automatically keep the phone update with that channel?

Ah ha. It looks quite nice...more like n900 updates...options.

Re: sailfishOS Upgrade12 discussions
 

Been there, asked that...
http://talk.maemo.org/showpost.php?p...&postcount=180
http://talk.maemo.org/showpost.php?p...&postcount=211
http://talk.maemo.org/showpost.php?p...&postcount=212
http://talk.maemo.org/showpost.php?p...&postcount=219
etc..

While I do concede making non-monolithic releases is HARD (TM), and virtually the only GNU/Linux distribution where this actually works is my beloved Gentoo*, I still think anything would be an improvement over the current "surprise mentality".

* Because API problems are slightly less common than ABI ones.

Re: sailfishOS Upgrade12 discussions
 

I think that monolithic releases are a good thing for an obvious reason - publicity. You keep users excited when they know they have something bigger to look forward to, than just random frequent small changes to default apps.

Press is much more likely going to notice bigger changes once per 1-2 months, rather than small changes scattered across time (and yes, there has been press coverage of SailfishOS upgrades, at least on some tech-focused sites).

Even regular users that are not excited from waiting for an upgrade will prefer reading a changelog once per month or two to finding out something has changed in the system every once in a while.

PS: I am saying that as a long time Archlinux user :)

Re: sailfishOS Upgrade12 discussions
 

@nodevel: I agree with you, but I also agree with pichlo. Therefore, I suggest something in between:

2 channels - fast and slow, kinda like the current 'rings' on Windows 10. People on the slow channel will get monolithic releases like you suggest while people on the fast channel will get regular app updates like pichlo suggest with small changes and stuff.

Re: sailfishOS Upgrade12 discussions
 

I'm talking about image channels. Once a channel is selected and flashed for the 1st, then you receive all updates from OTA :).
So everyday, my BQ phone receives an OTA update :D !!!!

Re: sailfishOS Upgrade12 discussions
 

Re this discussion (see the 8 posts before mine), I put it directly to Jolla:
https://twitter.com/JediTWang/status/588277949348057088