that’s 796,26 MB/s (mega-BYTES) x 8 = 6370,1 Mb/s so SATA III (6 gb/s) will be a little bottleneck …
Sorry you are correct, I wrote GB/s but meant Gb/s, so multiply it by 8 and you get close to what I calculated (I also just did 4000x2000 instead of 4096x2160). Most video applications measure bitrate in Mb/s rather than MB/s and I guess that’s also why it’s called bitrate rather than byterate.
My confusion was that the Raspberry Pi 3+ has only 1080p@30p hardware video encoding (H264).
Which is with the calculation mentioned here: 1920x1080 pixels x 3 bytes per pixel x 30 fps = 1.5 Gb/s
But in the picamera documentation:
https://picamera.readthedocs.io/en/release-1.13/fov.html#sensor-modes
there is also a mode to film with 3280 x 2464 @ 15 fps which is 2.9 Gb/s. Which is nearly twice the bitrate. What I missed was that this is only possible with the MJPEG format not with H264.
1 Like
and technically 4K UHD is 3840x2160 - but still very much in the same ballpark.
Do you still need links or are you happy enough as is?
Do you still need links or are you happy enough as is?
I meant that it works after switching the kernel module parameters - it still doesn’t work from GUI out-of-box without manual intervention, so if you found anything that says otherwise I’d be happy to see it 
1 Like
You are probably right - just chinese whispers at work. Anyway, the post (and topic) that I was thinking of are: Librem 5 & Tethering Update 2020
– 3840 × 2160 – 16∶9 (Ratio: 1.778) - consumer media and display industries,
– 4096 × 2160 – 256∶135 (≈19∶10) - digital cinema production.
Yes, but back to main camera, here is link to, for example, ultra-sharp 4K (2880×2160@24fps) AR0521: CMOS Image Sensor, 5.1 MP, 1/2.5" supports 1440p30 mode for 16:9 video (HDR included) with recording resolutions of 2160p (24 fps) / 1440p (30 fps) / 1080p (60 fps / 30 fps) / 720p (120 fps / 60fps) / WVGA / VGA, so i think that 2880×2160p24 is max. that we can expect from any 4K wide angle camera within smartphone to be processed (having only 30fps option operational/available on Samsung 13 Mpx Standard or 5Mpx S5K3L6 Wide Angle lens variants):
My main point/guess here is that encoding maximum for S5K3L6XX (ISOCELL 3LXX, 13MP with 4208 x 3120 usable pixels) is 1080p@30fps and 720p@30fps, but without having 720p@60fps support at all?
P.S. @amosbatto, if Replicant have relevant 60fps and 120fps support sources, I apologize! Thanks anyway!
1 Like
In case anyone is shopping for a Linux phone, I have created a table comparing the 12 models that can be bought with Linux preinstalled:
I didn’t bother to include phones like the Fairphone 2 and Nexus 5 in the table, because they require that the user install Linux, but the table would be much larger if it covered all the phones on which Ubuntu Touch, Sailfish OS and postmarketOS can be installed.
I also clarified the situation with RAM speeds on the PinePhone. The A64 supports a max of 3GB DDR3-1333 at 666.5MHz, but the max LPDDR3 clock is unspecified and the PinePhone distros are using RAM speeds between 552 and 624 MHz. In other words, the Librem 5 is using LPDDR4-3200, whereas the PinePhone is using between LPDDR3-1104 and LPDDR3-1248, so don’t just look at the 30% difference in CPU speeds to estimate the speed of the two phones.
10 Likes
I have to assume that Replicant has access to Samsung’s datasheet for the S5K3L6XX, since the data that Replicant posted about the S5K3L6XX is very specific, and they couldn’t have gotten that info through testing (since there is not yet support for the MIPI CSI-2 interface in the mainline i.MX 8M driver).
2 Likes
Good work on the spreadsheet. 
1 Like
Thank you for the great table!
I wish it had LibreOffice format and not proprietary Microsoft format.
2 Likes
The problem is that free accounts in Wordpress.com don’t allow uploading .ods files (but do allow .xlsx files). However, I have uploaded the file to one of my VPS’s, so you can download it now in an OpenDocument format:
http://80.255.11.219/amos/ComparingLinuxPhones.ods
(Technically, XLXS is an open format if you don’t mind MS corrupting the standardization process and using binary blobs. 
)
6 Likes
I noticed that too - but then if we want people to adopt Linux phones then we want to reach people for whom LibreOffice formats would not work out-of-the-box.
On that score, perhaps there should be an HTML version available on the web.
Yes, it has a documented standard.
I suspect what goes wrong though is that the standard is so complex that in many little corner cases the standard is open to interpretation and effectively in those scenarios Microsoft’s implementation defines the standard, not the standards document itself.
4 Likes
One of the noteworthy things that really stood out from the spreadsheet is the sheer number of Linux distributions using Phosh. Even if the Librem 5 crashes and burns, which I don’t believe it will do, Purism will have made a huge and lasting impact on the ecosystem and community with Phosh. Kudos!
15 Likes
…and Phoc and libhandy…
4 Likes
You are, of course, correct. Phosh is the “shiny thing”… and I was dazzled.
Librem 5 GPU can be clocked 800MHz at 0.9V and 1000MHz at 1.0V. We don’t have DVFS for GPU implemented yet, so right now it’s limited to 800MHz.
2 Likes
I’m betting that feedbackd also becomes a thing in other distros or hardware from other companies in the future too. Something as simple as a blinking indicator light can have a lot of appeal.
Maybe you could add manufactured units numbers to this table… Well… estimates…
UBports said in one of its monthly reports that there were 4000 to 4500 units shipped of the PinePhone CE: Ubports. In her CCC presentation last year, Nicole Faerber said that Purism’s goal was to produce 10k units of the Librem 5. We don’t have any other information about production numbers of the two phones.