No manual editing this time, but an automatic postprocessing script using darktable-cli and rudimentary lens corrections. Takes ~30 sec to develop on the phone - about ten times longer than the default script used by Millipixels, but with much better results. #shotonlibrem5#librem5#mobilelinux#linuxmobile#photography
Randomly stumbled upon Sean Moss-Pultz's short post about Openmoko, featuring some photos of a working prototype of GTA03/3D7K, the cancelled successor to the Neo Freerunner that was being worked on around 2009. So far I have only heard verbal descriptions of how it looked like (usually described as "a soap dish" 😂) and seen photos of some casing mock-ups and bare PCBs, but never a complete device.
Video confrencing time!
With the latest achievements from the community, Droidian will soon get support for camera over V4L2!
This means that now all apps can access and utilize the camera without any latency.
Thanks to @GranPC For taking this task off our hands and finishing it.
set page background color to match fenix_colors.css, fenix_one.css, and fenix_one-alt.css
Modified fenix_colors.css, fenix_one.css, and fenix_one-alt.css:
optimized colors to better support styles that do not hide the tab bar: desktop and mobile styles, as well as all styles while using larger screen (lapdock, monitor, or tv) including laptop and desktop computers
Modified install.sh:
optimized logic: only attempt to create backup on first run of install.sh script
added new user selection option for applying recommended preferences to user.js
fixed typo preventing dynamic_popups_max.css from being applied
Modified uninstall.sh:
optimized logic: only continue with uninstall if at least one chrome directory has been located in selected browser profiles
added logic to remove added preferences from user.js if present
Modified README.md:
added note to pre-install section about applying recommended preferences with install.sh script
5G data support, Latest Mobile Camera Tech in Linux, Modernizing Modem, Even faaaaaster App launches, Modern devices (ThinkPhone and Pixel 6) and as always Improved UI!
I have not tested Mobile-Friendly-Firefox with these browsers yet, as I am waiting for official arm64 releases before installing them onto my Librem 5. While I think that everything should work, anyone can share issues here on the fediverse, on my Mobile-Friendly-Firefox repo, or on my forum thread. I'll try to check all three from time to time so I don't miss anything.
Minor Update:
Added to install and uninstall scripts
Support for Librewolf flatpak
I have tested and confirmed that it works perfectly.
Okay, I think I am done updating files for a while now.
I have fixed all known issues, and everything works well. The only issue is a cosmetic one that doesn’t really matter and is unlikely to be noticed (the Tab Manager Menu in landscape mode doesn’t expand to use the full screen, but it works well and is very usable).
So I think it’s safe for everyone to save the files they need now.
For anyone that saw my post yesterday (November 11th), please check it again. There are additional updates from today, and I edited that post to include them.
Adjusted the following files to allow for vertical scrolling of extension popups:
extensions_menu.css
true_mobile_landscape-alt.css
true_mobile_landscape.css
dynamic_popups.css
dynamic_popups_plus.css
dynamic_popups_max.css
dynamic_popups_pro.css
dynamic_popups_pro_max.css
fenix_fox-alt.css
fenix_fox.css
fenix_one-alt.css
fenix_one.css
Adjusted userContent.css (fenix) to apply fenix colors to all about pages using regexp and selectively fix about pages to better fit display.
Updated on November 9th 2023:
Adjusted userContent.css (fenix) to fix a mistake that I had made. Sidebar size variable was in color section at top, being applied to all screen sizes; it is now properly set for smaller screens only, for the specific about pages that require it.
Updated on November 10th-12th 2023:
Added userContent.css (non-colorized).
Adjusted the following files to properly allow space for Tab Manager Menu button and toolbar items:
Added userContent.css (fenix) to fix Firefox about pages to be better fit for Librem 5 as well as a color theme to match Firefox for Android, code-named Fenix.
Added fenix_colors.css for a color theme to match Firefox for Android, (Fenix). If you do not want the Private Browsing Mode theme for the URL Bar and Nav Bar, comment out that section of code at the bottom of the file.
Added fenix.css as an alternative to true_mobile_mode.css that more closely resembles Firefox for Android (Fenix).
Added extensions_menu.css to fix the Unified Extensions Menu.
Added dynamic_popups.css and several variations so that extensions expand into a big enough popup which also supports horizontal scrolling. Works best with true_mobile_mode.css or fenix.css.
Added alt-browser-alt.css to be used with true_mobile_mode.css or fenix.css instead of browser.css. It can also be used with other styles like alt-single_tab_mode-alt.css to have the Tab Bar at the top of the screen and the Nav Bar at the bottom.
Added single_tab_mode-alt.css, true_mobile_mode-alt.css, and fenix-alt.css, to be used without alt-browser-alt.css or browser.css in order to have the Nav Bar at the top of the screen.
Added true_mobile_landscape.css and true_mobile_landscape-alt.css to have a nice landscape mode that maximizes usable space and fixes flickering popups.
Added fenix_fox.css to have a single standalone userChrome file containing all necessary code except fenix_colors.css. You can add dynamic_popups.css or another variation. fenix_fox-alt.css is the version that has the Nav Bar at the top of the screen. You will still need userContent.css (fenix).
Added fenix_one.css to have a single standalone userChrome file containing all necessary code, including fenix_colors.css. If you do not want the Private Browsing Mode theme for the URL Bar and Nav Bar, comment out that section of code at the bottom of the file. You can add dynamic_popups.css or another variation. fenix_one-alt.css is the version that has the Nav Bar at the top of the screen. You will still need userContent.css (fenix).
Added variables into many files so that they work in “Normal” and “Touch” density modes.
If you prefer having a single userChrome file, you can simply rename fenix_fox.css or fenix_one.css to userChrome.css. You can also copy and paste the contents of one of the dynamic_popups files to the bottom of the userChrome.css file. Whichever userChrome file or files you decide to use, you will still need userContent.css (fenix).
For practical reasons, photos that you #ShotOnLibrem5 are processed into JPEGs with lower quality than what the camera can do. There are some (complex) ways in which this processing could be made faster and therefore cram more pixels and algorithms that make things prettier, but meanwhile...
Each photo you take is stored as both raw DNG and processed JPG - so you can go back to raw data and retroactively gain quality. See https://dosowisko.net/l5/photos/ for an example.
That said, you don't need huge powerful but complex tools like #darktable or #rawtherapee to make your photos look better. Imagine a simple to use app that lets you do basic stuff on the phone, like white balance or contrast correction, which could then take its time exporting at full res with all the heavy noise reduction algos without annoying the user while taking photos.
Does that sound like something you'd like to work on? 😁