I was tripped up in the beginning, too. Then I realized that the gestures and actions in phosh (phone shell, the mobile-adaptive version of PureOS), are different from Android and iOS. It gets easier quickly.
In addition to the entire Tips & Tricks wiki that @Caliga linked, you may also want to take a look at:
Here are some apps that work reasonably well, most of which are not yet in the short, curated list in the store:
Edit: BTW, most of the Tips & Tricks were written with the previous amber repository apps in mind. Your phone is probably already on byzantium repo, so a few things might be slightly different now.
First I could hardly see anything when trying to take pictures indoor (much gain needed, took a while until I found the slider ), and all that I managed to see had fancy colors. Then (trying outdoors) I had trouble getting a clear focus, and in the end all that I achieved looked very grainy (on a rainy day that is).
Using the sliders was also of limited use, because what I saw while adjusting sliders did not really correspond to the resulting picture (the latter was significantly brighter).
Please take all this with a grain of salt, as I realize that the effect of ‘wow what a brilliant picture’ can only be achieved if all parameters are about perfectly tuned.
Actually the Tips&Tricks wiki page looks like smth worth mentioning more prominently, perhaps even in the quick start guide (which needs an update for the encrypted disk anyway …).
My videos open in mpv if I tap them in files.
When I tapped an mp4, no suitable program was found but I was offered to install something from a long list of matching applications. I selected dragon player and it does the job, even though not adapted for the small screen. Apparently on this workflow (starting from nautilus) the filter for mobile optimized applications is not active.
On the camera, I’d say Gain is the most important setting.
Right, raising this a lot lets me see something at least
On the earlier version of the camera app, I have to crank the phone’s brightness to max to see an image in the camera app, even before adjusting the gain in the app. Not sure if this has been improved in your version of the app.
(Just to clarify, the phone’s brightness has nothing to do with taking a photo or the photographic results, only improving the ability to view the camera app’s screen.)
Stephan, check out https://social.librem.one/tags/shotonlibrem5 to view lots of cool photos made with the Librem 5, including @dos’s most excellent collection of…“kittycisms”…er, “catechisms” … er… Well, you’ll see.
(Dos, feel free to use one of those for the title of the book I hope you publish one day. On me! )
That’s how it works at the moment anyway. The Librem 5 gets the raw image and post-processes it, producing ultimately a JPEG. So the only real difference is the available horsepower. Do it on the Librem 5. Or do it on your desktop / laptop.
Did you use default driver with RGBG8888 data or do you have some experimental 12-bpp per component driver/setup? Because I expect that there is significant potential for future improvement of the quality and high exposition rage photos. I understand that full driver support takes time and can be work for year or two and basic 8-bit functionality is enough for now. So it is my curiosity, because main camera sensor seems quit capable.
Interestingly, it did work for me a few times: in rare occasions, a long press followed by release kept the menu open, and with a second press I could select an option.
I don’t know which layer translates the long press into smth like a right click, but if that layer would just wait a little (200ms?) after sending the right click, then it could understand the release just as part of the right-click gesture, not as a separate release event, and the menu should reliably remain open. I.e., you’d have to wait until the menu pops up and then quickly release within the threshold. Or the release could even be ignored completely.
Alright, I found that xev only sees one button, no matter how long I press. So it doesn’t seem to be a low lever driver thing. Which module then translates a long press into a right click or anything that triggers the context menu? I might give it a shot to tweak that module, if only I knew which
The latter is said to be a gtk bug, but it’s unknown if it ever has been filed on their side.
QUESTION: Is it only me thinking that context menus are a must have? To me it feels like about every app is crippled by the lack of them. Are all apps using context menus being re-written to use different ways of interaction? How do you open a link in a new browser tab? How do you invoke CCP in just every app? …
I would be willing to help debug the issue, but since this is not my area of expertise I would at least need some pointers to the code involved. As of now I wouldn’t even know how to describe the problem to gtk folks so they could look into it.
Working context menus would be great. For example, it currently is really difficult to delete a file using touch input. The terminal keyboard does not supply a ‘del’ button, or am I missing something?
), and all that I managed to see had fancy colors. Then (trying outdoors) I had trouble getting a clear focus, and in the end all that I achieved looked very grainy (on a rainy day that is).
)