[Official announcement] Current status of Update10 [answered]

Hi Sailors, thanks for sharing information. What about other features. Is the list you gave the complete changelog for update 10?

Well, this update would calm lot of anxious users here . Thanks for the update and your efforts on Sailfish OS.

Thanks! Make the release rather more stable than sooner. :)

Thanks for the update, the main issue then, that blocks the release, is OOM problem, it seems that the available RAM resource is not enough?

Jolla team, thanks for the info. As you stated, it's best to have a proper and working update than some almost-ready update. We'll just have to be patient...

Thank you for the info, though it still came couple days late as the promise for the update was during november. And thank you for not making any promises of exact release date, this is the point I've been constantly trying to make.

Thanks for the update. To be honest, after reading this I kinda doubt the release will be out before years end.

Thanks for giving some information, we do appreciate it, even though it's not the kind of news we were hoping for.

BTW, what about zram ? It has been mentioned before but I don't see it on the list. :)

What is worrying me quite much is not to hear anything about CalDAV and CardDAV. I am 10 months without a working calendar on my phone now and these issues have been rated highest ever on the forum since beginning of the year. I seriously start to doubt, that this forum has any reasonable impact on what is going on at Jolla. So what should users do with a phone/tablet, where you cannot sync the calendar? (please nobody tell me now, that syncing with Google is possible, because people who want to sync with Google don't buy a Jolla!)

@Jolla: it is not important for us, when update 10 is coming, but will CalDAV and CardDAV be supported and when? Or do we have to buy another phone now?

@mousse04: Check the changelog of the opt-in update 9. This (coming update) should be a "combined update" (of 9 and 10).

@thomas: There is already support for CalDAV.

P.S. Thanks for the Update, Jolla.

@thomas the opt-in upgrade 9 works fine for me with caldav and carddav from an owncloud installation. Some tinkering is still required (the URL on the phone and server-side), but in if you face problems you can post them here and people that got it working will be able to help you out (if it is owncloud+nginx I can provide my config). Bottom line: this forum does work and Jolla does listen. :-)

@bijjal: Alright, let's dispense with the friendly banter. Nobody cares when this update's gonna be released. All we want to know is: Which lake will it be named after this time? :D

I'd like to know if it is possible to easily turn off the OOM killer if an user wants to do so.

I have been running 1.1.0.39 Uitukka since the beginning and I have not encountered any memory problems, and I'd like to keep things running when I start them, no "androidsky" automatic killing of applications for me please. :)

@torcida@sidv CalDAV is still NOTworking reliably (should I say "at all") with a number of servers, the popular fruux.com and mykolab.com in particular.

Being able to sync the phone contents IS one of the main reasons to own a "smartphone" as opposed to a feature phone and, being this technology mature and open-source, it is expected to be working almost flawlessly.

This and the spare batteries unavailability are in my view a big fiasco and the main reason why I still don't recommend Jolla to anyone, nerds or else.

@IZ1IVA no need to scream, I am reading you alright. :-) I do absolutely agree that those are vital services on a smartphone. However, I can only report that they work for me in my setup. So claiming that they do not work at all is wrong. I understand that this does not solve your problem with your services of course but is 1) a good sign and 2) @thomas did not specify which CalDAV/CardDAV server he is using or if he is on update 8 or 9 (which got things working for me).

I hope that "messages app isn't kept in memory when closed" doesn't affect how push messages work (even when the phone is locked, as it works now).

Like MartinK, I am also interested in knowing about Zram, will someone comment please!!

We warned about the RAM being too small, when the initial specs where released :P

Anyway, thank you Jolla, very much for, this time, giving us the information we needed, and desperately asked for! Thanks, and good work

Thanks to jolla team for the information. I hope the update 10 will be released in December, it would be an awesome gift for Christmas

Regarding CalDav, check: https://github.com/nemomobile/buteo-sync-plugin-caldav, all those fixes since Jun(update8) and Sep(update9) are coming for update10, please note that the list above is about memory fixes, many more fixes are coming.

I could care less about the timing, but what worries me are the measures taken to solve the bad memory situation. I do experience problems under 1.1.0.39, but I'd rather have laggy phone, than the system killing my apps. If I have too many apps running, that's my problem, not the system's problem.

The second thing is the browser tab killing - webOS had this "feature" and it was just terrible. You opened a website to read later (without an internet connection) or was in the middle of writing a blog post, when you suddenly found a blank tab instead of your web page.

PS: Damn you who turned @juiceme 's post into a comment. It was a valuable answer to Jolla!

@dsilveira The problem is not 1GB RAM - N900 had just 256MB and I was often running >8 apps without any lags.

@nodevel, I kind of wondered at that myself! :)

Well, probably this is one of those threads where an answer is not really expected... :O

I never ever had RAM-issues on the N9. Well, neither do I have issues now, actually, perhaps because I just don't keep many apps open at once. How come this is such a problem all of a sudden?..

@nodevel of course only 1GB is a problem. Sailfish is not Maemo5 and 2014 is not 2009. Things move on. However it is a shame Jolla seem to have not forseen the memory problems when updating Sailfish's core APIs and systems. I suspect preparation would have taken a fraction of the time that active triage has and is taking.

Thanks for the update. However, according to the information in this post, it may now be 6 months between stable updates; with further delays, perhaps even more. Can you share what you think has gone wrong with the development cycle in Q3 and Q4 of '14?

Whilst plenty of people complained about remaining bugs and absent features in Q1 & Q2 (me included), we did get regular updates which improved many things for end-users. Now, by contrast, the vast majority of end-users have been feature (and bug) locked since the middle of July, and this with a "monthly" release schedule having been committed to. There seems to have been a repeating pattern of woefully over-optimistic development schedules communicated by Jolla. When targets are missed again and again, usually it's a good idea to review the process and make changes or alter goals. Has there been any introspection of this kind, or is Jolla just forging on as best it can?

I fear with MWC coming up at the beginning of February, if some goals aren't met soon, the potential of winning new partners and collaborators shrinks exponentially and the business plan may effectively be shunted a year into the future.