Re: First thoughts about the (pre) Sailfish OS 2.0
 

I'm not an early adopter, just curious... does the phone not use the proximity sensor any more? I've never had a problem with the phone unlocking itself in a pocket up to v1.9, I wasn't aware it was something that needed improvement.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

It still uses the proximity sensor. I don't have any problems.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

This was practically never an issue before, or opening to lockscreen sometimes simply didn't cause much hassle. Now it's a bit different when you can open app launcher without unlocking, and the media player controls behave like buttons and are EASILY triggered in the pocked.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

Apple are renowned for introducing hidden gestures that normal people don't know about but it doesn't effect their day to day use. Eg. The 5 finger pinch to multitask or double tapping on the home button in iOS.

In OSX the right click on the mouse is off by default and I regularly come across Mac users that have never switched it on. My other favourite is windows users trying to cut and paste files between folders in a single finder window instead of using spring folders.

And if you want a really hidden feature that you'd have to know about before you used it you've only got to look at 3DTouch on the iPhone 6s. That pops up a context sensitive menu whose contents change depending on how hard you press. It makes covers actions seem positively intuitive.

This could be easily solved by Jolla. Keep multiple cover actions but make them work as buttons if pressed or gestures if dragged. They do that for actions on full screen modal dialogs already - you can either click a top corner or drag the screen. Then just make the home screen navigable by edge swipes or dragging outside of covers.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

You are the second person I hear mentioning this. I never thought this would be even possible, considering how fussy the double-tap unlock is. It usually takes me three to four tries to unlock it when I want to. Hitting just the right timing and all that jazz... And here we go, two members claiming that they managed to achieve such a feat by accident, one of them even multiple times per day. Miracles do happen, apparently.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

Hi,
Little question, is there a way to clean up the events the page as a whole? And not by type of events (email, sms, etc).

Re: First thoughts about the (pre) Sailfish OS 2.0
 

Actually I've had pocket doubletapping and interacting problem all the time with Jolla. It really depends on fabric and pocket looseness and how the phone moves or doesn't move in my pocket. No problems with new lockscreen for me though, and I suspect that it is only because the direction of lockscreen swipe has changed.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

There is a pulley menu visible when you are in the selection mode. It has (only) option to clear all events on a go. Probably not enabled in normal view to prevent accidentally triggering it, but I'd prefer it always visible.

Re: First thoughts about the (pre) Sailfish OS 2.0
 

I see I am not alone.
These are the things that got me off this boat.
http://abadcafe.pl/post/122926111638...ne-post-mortem

Re: First thoughts about the (pre) Sailfish OS 2.0
 

As a former colleague used to say, opinions are like bumholes. Everybody has one. I agree with most of that article except for this bit:

SFOS 2.0 is nothing but a glorified UI change. There are no major changes under the bonet, like e.g. 1.0.7 was with the Qt update. And the only UI change that has anything to do with multitasking is the ability to have more than 9 app covers on the home screen. So, in this regards, 2.0 is getting closer to proper multitasking, not "moving away from it". IOW, I have no idea what you are talking about.

To be honest, I was expecting more from 2.0. Not a different desktop, but a real change. For example, a complete refactoring with the primary focus on resource usage. For example I was expecting OOM disappearing completely or at least getting less frequent, not more.