Fairphone 6 wide camera experimental Linux support
helonaut
98 points
13 comments
July 22, 2026
Related Discussions
Found 5 related stories in 332.6ms across 14,736 title embeddings via pgvector HNSW
- Fairphone 6 with /e/OS 4.0 – Results, results, results speckx · 11 pts · July 22, 2026 · 54% similar
- Phyphox – Physical Experiments Using a Smartphone _Microft · 203 pts · April 12, 2026 · 48% similar
- Initial mainline video capture and camera support for Rockchip RK3588 mfilion · 80 pts · April 13, 2026 · 46% similar
- Celebrating seven years of the Fairphone 3 ravenical · 13 pts · June 16, 2026 · 44% similar
- FIM – Linux framebuffer image viewer Mr_Minderbinder · 140 pts · April 17, 2026 · 44% similar
Discussion Highlights (4 comments)
noIdeaTheSecond
Good to see this! Love Fairphone!
BraveOPotato
I wish one day I could do cool stuff like that. Kudos!
NooneAtAll3
have fairphone looked into supporting GrapheneOS? what exactly is missing there other than "it's not Pixel"?
Throwaway698514
Does the article seem AI-written/assisted to anyone else? Some parts that stood out to me: > A phone camera is not a single device. On Qualcomm SoCs, the capture path is a chain: > The bus register base moved from 0xa00 to 0x1800, and encapsulating that offset shift accounted for most of the work. > It gated the AHB register bus used by the whole camera complex, including the CCI. Without it, register accesses silently returned zero. > With the wrong numbering, CSIPHY programmed a lane mask with lane 0 missing, and the PHY never locked. > This was the main bug. Frames arrived at the right rate and size, and buf_done fired, but every pixel was zero. [...] The data path delivered frame timing, but not pixel data. > Changing the register value from PLAIN64 (0xa) to 0x0 turned the all-zero frames into real images: the maximum pixel value was 255, the full colour-bar pattern appeared, and the violations stopped. Sorry if not, but it seems like so much uses AI nowadays.