maemo.org - Talk - SailfishOS Update11 discussions

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - SailfishOS Update11 discussions (https://talk.maemo.org/showthread.php?t=94331)

Re: SailfishOS Update11 discussions

Still no anwser from jolla when/how they plan to fix their maps bug. They should look at it asap and if they cant fix it atleast a Word that they are trying. Hope they release update very soon.

Vote here so we can use it
https://together.jolla.com/question/...-update-11127/

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by Dave999 (Post 1455431)

?

answered 5 hours ago

xfade gravatar image
xfade
701 ●6 ●8 ●11

You should now be able to install Maps on all released versions of SailfishOS on your Jolla again. There was a server side issue, which now has been worked around for Maps.

Please let us know if you still can't install it.

Re: SailfishOS Update11 discussions

Yes. Finally. Thank you very much!

Re: SailfishOS Update11 discussions

Published today. Jolla really listen to the community, as many new features were asked by the community :

Quote:

[SailfishDevel]Update on SailfishOS roadmap
Soumya Bijjal soumya.bijjal at jollamobile.com
Fri Jan 16 13:03:58 UTC 2015
Hi all,

We are keen to share our plans with you after our iteration planning day this week. This turns out to be quite a long post, but should provide a good overview on whats cooking.

2015 will see Sailfish OS evolve towards a display resolution and form factor independent operating system capable of running on a range of devices. It will also bring a renewed Sailfish UI. We plan to demo this evolution at the Mobile World Congress in March.

We have now started to work full speed on the new UI framework changes and are currently in the prototyping phase. Our main driver is to introduce changes that
1. enhance user experience on both the phone and tablet
2. strengthen the OS core
3. simplify implementation for a better managed code base

Here is a list of things we are trying out w.r.t the new UI framework:
* improved notifications system
* richer Events View with more widgets and actions
* separating lock screen from the home screen for simplified UX and technical architecture
* home screen interaction improvements with revamped navigation hierarchy

We have progressed quite well in the direction of Sailfish UI scalability already, for example we have the following implemented in our internal development branch:
* scalable icons
* home screen and application layouts take physical display dimensions into account, for example larger displays are able to show more content
* display-size optimised graphical effects

During this month we'll continue adapting ambience wallpapers to different display sizes and aspect ratios.

Our next big UI task is to enable landscape mode in apps, system dialogs, active covers, and optimise the design for the best use of the additional space.

On the platform level, in this iteration we are working towards the following goals:

* System update improvements (will be utilised for update 12 onward):
- run btrfs balance operation before installing OS update - Part of https://together.jolla.com/question/...of-filesystem/
- enablers to allow factory reset operation to reset the OS to the latest available public version instead of the age old factory image
provide an API to check the system update size
- enablers to allow store client to handle downloading the OS update in the background without interfering with the user
- upgrade to using latest upstream versions of libzypp and zypper to get new features (to allow us to later take them into use, namely better pattern support and conflict calculations)

* Adaptation work for the tablet:
- make Jolla tablet turn on promptly and give understandable progress/status information
- design and implement filesystem layout
- check power management functionality on the tablet
- bring bluetooth related fixes to tablet kernel
Sensor detection, USB and camera adaptation
- check stereo speakers functionality
- check iphb wakeups functionality on the tablet
- ensure USB charging works

* adapt middleware to modemless device i.e. tablet
* work towards Pulseaudio 6.0
* drop upower in favour of statefs - this has been in plans for a while and we are now on it as fixing issues on upower is not the best use of our efforts
* dual-stack implementation (ipv4 and ipv6) for cellular connectivity
* prototyping excrypted filesystem
* research SELinux as a solution for system security and application access control
* toolchain updates - we are working towards upgrading to GCC 4.8, binutils 2.25, switch to Thumb2+NEON for ARM by default, march=i686 and SSE2 minimum for X86

* Performance improvements:
- continue to analyze memory usage and chopping off bits wherever possible
- work on a benchmarking tool to measure progress <- this may not happen (yet or completely) due to priority shifts
- continue work on the QML engine and forking to save memory

As you may notice, there is lots to do in the lower levels and middleware to take the OS to the next stage. Nevertheless, we are keen to continue provide new features where and when bandwidth permits. In the next update we intend to release:
* renewed browser UI - simplified tab view, search for word on webpage, user friendly toolbar and URL field - https://together.jolla.com/question/...ch-in-browser/
* weather info integration to events view (Foreca) - https://together.jolla.com/question/...r-application/
* option to customise the highlight color of your favourite ambience in ambience settings (in Gallery app)
* notification to the user if there is insufficient disk space (< 500MB) while attempting to upgrade the OS
* allow editing of mobile data setting always (currently if the device is in roaming and data roaming is set to "Do not allow", mobile data settings are disabled)
In the spirit of supporting the community TOHkbd project, we have also implemented keyboard slide policy that will guide the display (un)blanking behaviour when sliding the hardware keyboard in/out.

During this month, we have planned to work on the following features:
* private browsing https://together.jolla.com/question/...n-web-browser/
* lock screen media player controls https://together.jolla.com/question/...e-lock-screen/
* enable USB tethering in the UI https://together.jolla.com/question/3798/usb-tethering/
* IMAP idle/push support https://together.jolla.com/question/...he-e-mail-app/

Not to mention that bug fixing is part of our daily work and will carry on in parallel with all of the above activities. Sailfish OS updates will continue to be delivered frequently.

Due to the nature of the tasks at hand, the gap between releases may vary. It does not imply that we are intentionally slowing down -- on the contrary, we are ramping up with extreme dedication in the next few months to deliver a scalable, refreshed and coherent platform, requiring time and focus to make things right. In order to better support our goals, our internal QA setup has been further enhanced to allow working on multiple releases in parallel and keep release instances longer for possible updates at a later point in time.

In a nutshell, we are excited to work towards the new horizon and will continue to share our progress with you. Cheers!

-Soumya

Re: SailfishOS Update11 discussions

Yeah sounds good :) i feeling we get a update in februar :P

Re: SailfishOS Update11 discussions

Roadmap looks good, two comments tho:
a) no mention of store and in particular paid apps support
b) improve quality of native apps

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by pagis (Post 1456910)

a) no mention of store and in particular paid apps support

Well, the store is not exactly part of the OS, usually mails about Harbour are sent out separately from what I've seen.

Quote:

Originally Posted by pagis (Post 1456910)

b) improve quality of native apps

That's a bit vague.

Re: SailfishOS Update11 discussions

where is the january update?

Re: SailfishOS Update11 discussions

Quote:

* research SELinux as a solution for system security and application access control

Hope this is not something that means rooting the device becomes important to make it usable like droids...

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by Dave999 (Post 1456920)

where is the january update?

Read the end of text posted above :

Quote:

Due to the nature of the tasks at hand, the gap between releases may vary. It does not imply that we are intentionally slowing down -- on the contrary, we are ramping up with extreme dedication in the next few months to deliver a scalable, refreshed and coherent platform, requiring time and focus to make things right. In order to better support our goals, our internal QA setup has been further enhanced to allow working on multiple releases in parallel and keep release instances longer for possible updates at a later point in time.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by rcolistete (Post 1456933)

Read the end of text posted above :

That's just words. Doesent say anything about their every month stratergy. We might have to wait until may and 2.0 for all I know. Then it would be like 2 releases in "almost" a year.

Re: SailfishOS Update11 discussions

https://twitter.com/bwachter/status/547747181944639488

Most U11RC1 preparations done, mostly waiting for builds now -- looks like QA can start after new year

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by pagis (Post 1456910)

b) improve quality of native apps

You mean like completely redo the UI for the Browser App? And adding extra protocol options to the mail client?

I consider that improving the quality of the native apps.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by thedead1440 (Post 1456926)

Hope this is not something that means rooting the device becomes important to make it usable like droids...

Don't worry, it's just created by the NSA (no joke!).

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by MisterMaster (Post 1456938)

https://twitter.com/bwachter/status/547747181944639488

Most U11RC1 preparations done, mostly waiting for builds now -- looks like QA can start after new year

Its soon end of january. Where is the update? QA for 3 weeks? Maybe they should do some more automation.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by Dave999 (Post 1458080)

Its soon end of january. Where is the update? QA for 3 weeks? Maybe they should do some more automation.

Well, it was the first rc, I guess it didn't pass the QA since it hasn't been published yet...

Re: SailfishOS Update11 discussions

Really, when was it ever said that there were to be monthly updates?

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by nthn (Post 1458107)

Really, when was it ever said that there were to be monthly updates?

Said or written. who care. Read jollas press releases and you Will find what you looking for. Anyhow...jollas updates are more and more rare from a user Point of View.

Re: SailfishOS Update11 discussions

You really need to give at least one (official) source stating that they will provide an update every month. The burden of proof is on you, not me. If you can't back up your statement with more than a vague "they said it", your claim is worthless.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by clovis86 (Post 1458147)

here you go :
http://i.imgur.com/IljT1tT.png

https://jolla.zendesk.com/hc/en-us/a...-new-features-

Yes. That is one of many places. Hope we will get it before end of January. If not before end of February. Do we have an opt in this month or is it only for some updates?

Re: SailfishOS Update11 discussions

Where is January Update fellas?!?!?!?!?!?!

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by Zoloo (Post 1458241)

Where is January Update fellas?!?!?!?!?!?!

That is a valid question Zoloo. I think it is in the black hole called Qa but I'm not sure. IT is trying to get to us but gravity of planet Jolla is simply to great at the moment.

Re: SailfishOS Update11 discussions

I repeat the same text from Jolla :
https://lists.sailfishos.org/piperma...ry/005512.html

Quote:

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by Dave999 (Post 1458305)

they prioretized tablet over OS updates. To me that means they intentially slowing down the updates for other things like building an not really needed tablet(except for the North Americans). Now I unlike this tablet even more. Its in between us and our software updates :D

Not really. The work they're doing on making Sailfish resolution independent will be important for future Jolla devices and licensing to other OEMs. So far it has been targeted at just one device, and there wouldn't be much future in that now, would there? The tablet just happens to be the first device to require a resolution-independent Sailfish.

Re: SailfishOS Update11 discussions

That's how I see the tablet. As a demonstration to OEMs that Sailfish can work on multiple screen resolution devices.

BUT!... Making it screen resolution independent? Isn't it a bit too late for that? I thought it was independent to start with. At least that's how I write software. Completely screen size and resolution agnostic (same applies to other parameters, not just the screen). If it is important for applications, it must be many folds more important for the OS.

So when I hear all this talk about "working on making Sailfish scalable", my first reaction is, "BS, surely it is scalable already!" All this talk must be either a language barrier or a smoke screen for the masses to buy Jolla some time to work on what they are really doing.

Either that or they have made some really, really terrible design choices at the beginning.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by pichlo (Post 1458340)

BUT!... Making it screen resolution independent? Isn't it a bit too late for that? I thought it was independent to start with.

I would imagine that was a pretty low priority requirement at launch, as they had one device with one resolution to support. Every app is full screen (until the split screen perk!). They could fix their icon sizes and layouts, which would have made development simpler and given better performance. What would have been the point of, for example, coding a wider browser toolbar with more buttons on it before now?

I think the timing is about right on their startup trajectory.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by pichlo (Post 1458340)

You may be right, however I think you may be underestimating how little forethought or preparation for the future was put in to Sailfish. I'd imagine a lot of stuff is as quick and dirty as it gets, and very device specific. When they lost their chipset partner early on (Ericsson NovaThor), there was probably very little likelihood of establishing a hardware ecosystem in a reasonable timeframe, and with it any third party devices and differing display sizes and resolutions. I don't think this is that unreasonable as they're small. However it is very worrying that they claim to be only doing this now .. that clearly demonstrates that they haven't been close to signing any partnerships with third parties, nor were they capable of doing so.

Oh, and there's no evidence of any (enabled) UI scaling ... don't think the Nexus 5 porters have been able to do anything, despite having a 5" 1920x1080 screen to play with.

Besides, only after the Qt update debacle did they decide to institute the ability to properly branch and roll forward / back the Sailfish development tree. Something you would have imagined that a company working on an OS would do from its founding days ... far more so than UI scaling and resolution / screen size independence. Lack of preparation in general seems to be a theme. It was a bit disconcerting to hear that the hardware adaption team were 'surprised' to recently learn that Intel use UEFI for their mobile products.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by bluefoot (Post 1458460)

Oh, and there's no evidence of any (enabled) UI scaling ... don't think the Nexus 5 porters have been able to do anything, despite having a 5" 1920x1080 screen to play with.

N7 - https://www.youtube.com/watch?v=yHuX6u9mYd8
N5 - https://www.youtube.com/watch?v=6zh3VBQqy94

Scales nicely out of the box, however performance, pixelation, standards for developers so they can port their existing or future icons to svg or other scalable format, checks in store and probably lots else could have been skipped to ship device on time in 2013 and not in Feb 2014 or later

Re: SailfishOS Update11 discussions

wow, the update-not-yet-here thread dropped out of last active threads
here is some fuel for discussion:
http://talk.maemo.org/showthread.php...31#post1459431
contrary to what it states anyone can opt-in, there are no developer checks

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by szopin (Post 1459451)

Great step in the right direction!!!

Re: SailfishOS Update11 discussions

Oh. And here I thought sailfish was dead. Good to see this thread come to life. ;)

I want this update last, even after the mainstream...fully functional with copy&paste, arrow in keyboard and a utility and simplicity when editing forms that would make the most hard-core apple fanboy impressed. Intact. I will probably not even update until sail 2.0!

Opt-out for now.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by szopin (Post 1459451)

The important assumption is that you *feel* to be like a developer, and accept the risk that your device may break after a RC upgrade.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by minimos (Post 1459482)

The important assumption is that you *feel* to be like a developer, and accept the risk that your device may break after a RC upgrade.

If you read announce carefully you can notice following:

Quote:

Originally Posted by Details about the early access update in short

Early access releases should be considered "stable". Issues found during that period will either be fixed, or added to "known issues" on the release notes

Re: SailfishOS Update11 discussions

So then...Jolla will need to:
1. Add the checkbox functionality.
2. Fix their update 11
3. Push it to the Opt-in
4. Handle the issues
5. Release the official update 11

We won't see that official update in a loooooonnnngggg time :D

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by Dave999 (Post 1459490)

I do not think so. There is an option to mention the problem in the release notes, and if the problem is minor enough, that is the right choice to make.

Everytime you fix a bug you have the chance to introduce another one, so many times it is better to chose the known problem instead of the unknown one.

Some fixes may still happen, for fixes that seem innocuous enough.

And of course there is the possibility the early adopters find a blocker, and in this case you would be right, the release will be put on hold.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by coderus (Post 1459484)

If you read announce carefully you can notice following: ...

Well, if you read carefully the text when you accept the opt-in, it also says this (bold enhancement is mine):

Quote:

The early releases are mainly intended for developers, and the screening of potential critical issues with new releases before publishing to the wider audience. Please make sure you backup your data (as you always should) before installing the early release, as we cannot with certainty say that you will not have any problems (such as data loss or corruption). Note that opting in to the early release program does not void your warranty.

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by minimos (Post 1459503)

Well, if you read carefully the text when you accept the opt-in, it also says this (bold enhancement is mine):

somebody should startle you for sure :)

Re: SailfishOS Update11 discussions

Quote:

Originally Posted by mikelima (Post 1459500)

Handle the issue doesn't mean fix. But even administrate, recreate, evaluation could take time. Nothing to worry about. Administration takes time and taking help from end-users with tasting is great. However it doesn't speed up the process but possibly the quality.