bockersjv | # 1161 | 2013-12-06, 22:52 | Report

I don't mind that too much, it's just the lack of scroll bars makes deletion quite painful.I do expect this to be addressed though.

att | # 1162 | 2013-12-06, 23:22 | Report

The first one seems to be CRAM with PCM audio, and the second one WMV2 with WMAV2 audio.

I might consider them more of legacy video formats. I doubt Jolla will support these in the future because licensing and bloat issues but let's see what MSameer has to say about them.

You might consider recoding them with more modern codecs.

---

Last edited by att; 2013-12-06 at 23:25.

droll | # 1163 | 2013-12-06, 23:29 | Report

so no chance of getting a bluetooth keyboard + mouse (or gamepad) to work?

MSameer | # 1164 | 2013-12-06, 23:40 | Report

This is an issue with how we extract information from media files. There is a fix in tracker which should fix the issue: https://github.com/nemomobile-packages/tracker/pull/12

An RPM can be built easily. We can then install it to your phone if you want or you can wait for an official update

The thing that surprises me is that those files do play fine in media player (audio only). They don't interrupt playing at all.

MSameer | # 1165 | 2013-12-06, 23:47 | Report

wmv/wma is unfortunately not supported.

The other file is pcm audio which should play (I hope). MS-CRAM video I have to check.

Jolla hat off:
We can always package the extra missing codecs and create a community repository for them (or push them to open repos ?). I can help with that if needed

If we need to support more media formats for the indexer then we rebuild libav and enable what we want.
If we want to support more media formats for playback then we package the missing GStreamer plugins.

---

Last edited by MSameer; 2013-12-06 at 23:50.

Makeclick | # 1166 | 2013-12-06, 23:58 | Report

Can you give as some hint? :P When?

Manatus | # 1167 | 2013-12-07, 00:22 | Report

I agree wholeheartedly.

In addition to this Android apps generally do not follow any guidelines of the operating system. It has always been a mess, and still is. It has been getting better lately, although not much.

While getting at least some sense in UX, Android has also degenerated in latest incarnations. I still feel that the double pull down menus on top of the screen is a bad move. There is zero clues about that, nor there is for pull up from the software app button on the bottom (which no-one uses because of that, but it confuses people when they constantly find the feature).
Old CyanogenMod-style setting icons on top of the one notification menu worked so much better. After a year I still haven't figured out why there has to be two top menus, as they haven't added anything there that would not have fitted in CM style notification menu.

Also on Android the swipes exist and are used very inconsistently between apps; Chrome has them, Astro File Manager has them, but most do not. It is probably for the best as they do completely different things.

So when I bitch below about my gripes with Sailfish, this is where I compare it to. Broadly speaking doing only three swipes out of ten potential use cases, and doing those three badly is much worse than doing ten out of ten, nailing seven and leaving three to be improved.
So many people think that mobiles are used comfortably on the sofa with two hands. They often hope for overly big screens for their phones too. Clearly they do not carry stuff in their hands any longer distances, or stand in the crowded erratically moving buses with only one hand free.

Sailfish is generally a bliss. For from the side swipes you actually have to start thinking the sides of the screen as buttons that always do same things; close application, multitasking screen, notifications screen.
Pulley menus and left-cancel, right-save swipe confirmation dialogs are the only really new things that take some time to get accustomed to. Maybe 12 hours of use, so yes, reviewers are lazy bunch of people, or just too time limited with their preview devices.

There are places where I can see where current Sailfish pulley menus do not work as well as hoped. Such as pages with long lists. Those enforce the user to scroll all the way top or bottom of the application page to reach the pulley menu. This problem is very easy to spot with (otherwise excellent) Tidings RSS feed reader or email app, as you may often have to do n. amount of swipes to reach the top. It is faster to quit the program and then go back, which is clearly wrong.
Some general workaround must be created for this type of UX problem. Long press to activate shine on top of the screen and marking the pulley menu to be pullable or something...

Long page syndrome happens also in UX main screen with long application list. With several pages of apps, to reach the multitasking screen you have to navigate back up with vertical movements instead of side swipes. One screen down it is still natural to pull back up, but two screens down you already start wishing for a shortcut. I suppose this should be easy to fix in coming versions. Design wise at least, if not technically.

Gallery app was very confusing until figuring out that pulls and swipes work only on upper half of the screen when additional non-pulley menu is present. This means that you have to tap on the picture to activate this extra menu, and then start swiping on upper half of the screen. Why not having all of the selections in a pulley already introduced? Or in the end I would be happy if one could just pull anywhere on the screen to go back to thumbnails screen, no matter whether it was the bottom half still showing parts of the picture or the upper half with the menu.

Inconsistency happens also in under settings save dialogs, where on some pages you can go left and you changes are saved, and on other ones you have to go right to save the settings before you get switched back to the general settings page part you started the wizard from. In latter cases you do get a visual cue of save on top right corner (saying 'Save', so it is quite clear), but _not_ having it and still saving any settings when going left is inconsistent.

But in the end I think these problems are minor, and can be devised around with some additional design. It is not that Sailfish has to be perfected on the first release version of UX.

kinggo | # 1168 | 2013-12-07, 00:51 | Report

that whole tracker thing is a disaster IMO. Even if you have some tool to configure it, it never works as intended. It doesn't work on my N900, it doesn't work on my ubuntu. While I don't care about the mess in N900 photo galery because I don't use it much and one can always select default camera folder I did remove that crap from my ubuntu because it was always running and scanning something over a whole hard drive although I set it up to scan only 3 folders.
And I don't see the point in it. Each player or photo viewer can manage library without it, so why do we need something system wide for all media types if each application can handle their own?
Not to mention that if tracker db get's corrupted one does not see any media files, at least on N900. And Average Joe should not need to reset tracker in terminal and probably doesn't even know how to.

MSameer | # 1169 | 2013-12-07, 00:59 | Report

Tracker is used by sailfish _only_ to store metadata AFAICT which can be easily regenerated. Text messages, contacts, ... etc are stored elsewhere.

It also crawls only a few directories + sd card to it should behave a bit better than N9/N900

att | # 1170 | 2013-12-07, 00:59 | Report

Tested Documents app with some files. PDFs and ODTs work. EPUB doesn't even get listed at Documents app. Rendering of PDFs seem fast except Linux Journal magazine that has ad pages which take long or very long to render. Scrolling also suffers on those ad pages. There doesn't seem to be a fast way to jump on 1000 page PDF. It takes forever to scroll through it or locate page at the end when you are at the beginnig.