ref: 709d530e02562604dc3af3dd209aba92068d3d14 jleightcap.srht.site/blog/openphone.html -rw-r--r-- 15.8 KiB
709d530ejleightcap Merge branch 'phone' into main 7 months ago
<html ><head ><meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<meta name="author" content="Jack Leightcap" />
<link rel="stylesheet" href="../style.css" />
</head><title >Smartphones are Shit: the Case for LineageOS and the Pinephone</title><h1 >Smartphones are Shit: the Case for LineageOS and the Pinephone</h1><p >◷ 20 min read</p><p >✏  published 2022-04-08</p><p ><a href="../index.html">Jack Leightcap</a></p>
<body ><h1 id="Contents">Contents</h1>
<p style="margin-left:0px">- <a href="#Intro"><i >Intro</i></a></p><p style="margin-left:30px">- <a href="#Longevity: Hardware"><i >Longevity: Hardware</i></a></p><p style="margin-left:30px">- <a href="#Longevity: Software"><i >Longevity: Software</i></a></p><p style="margin-left:0px">- <a href="#Open Source"><i >Open Source</i></a></p><p style="margin-left:0px">- <a href="#Open Source and Smartphones"><i >Open Source and Smartphones</i></a></p><p style="margin-left:30px">- <a href="#LineageOS"><i >LineageOS</i></a></p><p style="margin-left:30px">- <a href="#PinePhone"><i >PinePhone</i></a></p><p style="margin-left:0px">- <a href="#TL;DR: Where to Go From Here?"><i >TL;DR: Where to Go From Here?</i></a></p></body>
<p ></p><h1 id="Intro">Intro</h1>
<p ></p><p >Don&#39;t smartphones... kind of suck? How many times have you had to replace a phone in the past 10 years? Do you have a drawer of random crap with a growing pile of phones, or have you tried to absolve some regret and taken a few trips to an e-waste &quot;recycler&quot;? The battery no longer holds a charge; it gets way too hot; replacing a cracked screen costs more than just getting a new phone; new updates are unbearably slow; updates stop altogether; support stops altogether.</p><p ></p><h2 id="Longevity: Hardware">Longevity: Hardware</h2>
<p ></p><p >Compare your phone to a desktop computer: while not perfect by any means, most desktop computers are so modular they can be Ship of Theseus&#39;d many times over. Does a fan start making a horrible noise? You can probably find a replacement on eBay for pretty cheap if you know what to look for. Even if you&#39;re not tech-savvy, you can pay a premium to have a repair shop fix the fan for you.</p><p ></p><p >Bit of an unfair comparison considering you don&#39;t keep a desktop in your pocket — what about something like a laptop? Historically, laptops have been pretty repairable, but as time goes on less and less so. Spill a drink on your laptop keyboard, have fun,</p><p ></p><center ><img src="../static/openphone-macbook.png" alt="MacBook Keyboard Replacement" width=50%/></center><center > <a href="https://yewtu.be/watch?v=W1Purem1NF0"><i >Apple Really Doesn’t Want You To Fix This - MacBook Keyboard Replacement</i>, © 2022 Hugh Jeffreys via Invidious</a> </center><p ></p><p >If you can sacrifice some &#39;sleekness&#39; and a maybe a little bit more weight, laptops sold in bulk to companies or schools are becoming the last bastion of laptop repairability. I&#39;m writing this on a laptop from 2008 that&#39;s held up just fine with a battery replacement and some memory upgrades made easy by a very repairable design.</p><p ></p><center ><img src="../static/openphone-x220.png" alt="x200" width=50%/></center><center > <a href="https://www.xyte.ch/">Laptop Repairability: X230 Exploded View, © 2022 XY Tech</a> </center><p ></p><p >Smartphones? Repairability and modularity are actively <i >avoided</i> by manufacturers. Just taking apart a modern iPhone is a warranty-voiding, screen-cracking, glue-ripping operation. If your battery doesn&#39;t hold a charge, even if every other component of the phone is working <i >just fine</i>, the implicit (and even sometimes explicit) goal of smartphone manufactures is for you to just buy another phone.</p><p ></p><blockquote ><i >The issues this runs up against are <b >Circular Economy</b> and <b >Planned Obsolescence</b>, see <a href="https://sci-hub.se/https://doi.org/10.1017/pds.2021.422">M. Barros, E. Dimla: <b >From Planned Obsolescence to the Circular Economy in the Smartphone Industry: an Evolution of Strategies Embodied in Product Features</b> via sci-hub</a></i></blockquote><p ></p><h2 id="Longevity: Software">Longevity: Software</h2>
<p ></p><p >Hardware&#39;s lifespan is always finite; everything breaks eventually. The more frustrating source of turnover is <i >software obsolescence</i>. Apple has a very good <i >stated</i> support window of 5 years, but as developers engineer software targeting only the newest and most powerful phones, you start to notice updates making your apps <i >slower</i>. Eventually you stop getting updates all together. The same applies for the other major smartphone operating system Android.</p><p ></p><p >This is the tragedy of modern software: we&#39;ve built abstract software systems that can be replicated infinitely at no cost, don&#39;t inherently degrade, don&#39;t wear out with use; but ever-increasing demand for more complexity and novelty makes software &quot;rot&quot; just the same as hardware.</p><p ></p><h1 id="Open Source">Open Source</h1>
<p ></p><p >But... how can I get stuff done on my 2008 laptop while my 2018 smartphone struggles to open Slack? Like, installing Windows on this laptop is totally possible, but Microsoft has no financial incentive to support this hardware let alone test their products&#39; usability on it. This means, as far as Microsoft is concerned, I can either use something way too slow to be usable or something that stopped receiving security updates half a decade ago.</p><p ></p><p >A remedy is <i >Open Source</i>.</p><p ></p><p >&quot;What is <i >open source</i>?&quot; is easier to answer by describing what it is <i >not</i>. The code that runs on an iPhone, for example, is totally inaccessible to the end user. If you&#39;ve wondered why something was broken, even if you might have the skills to fix it, you have no power besides complaining to Apple and hoping they eventually bless you with a fix. While much less user-facing, the same applies to hardware design. Sure, this makes sense for Apple from a consumerist, hyper-capitalist perspective; Apple doesn&#39;t want other companies to freely benefit from their novel engineering efforts. From a longevity and sustainability perspective: this <i >closed source</i> model leads to repairability being at best a marketing feature rather than design principle. But plenty of incredible engineering work has been done totally opposite this philosophy: under <i >open source</i>! Even if you don&#39;t <i >personally</i> care about the internals of how some hardware or software works, imagine if repair shops or volunteers had access to hardware and software designs — these accessible designs would allow support for old phones far beyond what manufacturers intended!</p><p ></p><p >In contrast to releases of iOS (the very base software that makes up an iPhone), a fully open-source alternative — the Linux kernel — is cautious to the point of paranoia about both backwards compatibility and hardware support. The open-source internet browser Firefox has consistent releases and a community maintainers that make accessing the internet on weaker computer hardware easy. Plenty of older, more light-weight software and protocols like RSS or IRC — even email! — certainly aren&#39;t flashy but allow living in the modern digital age without overabundant resource use.</p><p ></p><p >This is the promise of open source. While profit-driven companies have little to no incentives to support end-of-life devices, open source builds on a collective commons of labor. The motivations for open source can seem totally counter-intuitive under a system of only closed source choices, but open source technology forms the backbone of the internet,  develops the tools used to build almost all software projects, and provides user-facing software like Firefox.</p><p ></p><blockquote ><i >I think a reasonable objection and unique challenge in open source is not environmental sustainability, but labor sustainability. With no corporate backing structure, is this something you can or should rely on? I&#39;d argue yes: see <a href="https://sci-hub.se/10.1017/dsi.2019.237">J.-F. Boujut, F. Pourroy, P. Marin, J. Dai, and G. Richardot, <b >Open Source Hardware Communities: Investigating Participation in Design Activities</b> via sci-hub</a></i></blockquote><p ></p><p >Open source technology, While no means a magic bullet and certainly having its own unique set of challenges, has proven itself more suitable for sustainable technology.</p><p ></p><h1 id="Open Source and Smartphones">Open Source and Smartphones</h1>
<h2 id="LineageOS">LineageOS</h2>
<p ></p><p >If this sounds promising, what&#39;s a solution that exists <i >now</i>, even if imperfect?</p><p ></p><p >A part of the common smartphone operating system <i >Android</i> is already open-source (the <i >Android Open Source Project</i>, AOSP). The functionality of AOSP, however, is only a very core piece of an Android smartphone. Google itself adds its own closed source software that allows access to the <i >Google Play Store</i>, the assumed default for downloading new Android apps. Different phones use different hardware, and phone manufacturers (Samsung, Motorola, Google) also have proprietary software specific to that hardware.</p><p ></p><p >A current solution, building on top of AOSP, is <i >LineageOS</i>. What LineageOS does, to oversimplify an incredible amount of effort, is reverse engineer and provide replacements for these closed source pieces of software. The result is an open source Android smartphone operating system with a <i >much</i> longer support window, allowing phone hardware to be useful long after intended.</p><p ></p><p >If this sounds promising, and you&#39;re at the point of needing a new phone, consider:</p><p ></p><ul ><li ><a href="https://wiki.lineageos.org/devices/">Finding a smartphone supported by LineageOS</a>. Buy one second hand! Maybe find a broken phone — otherwise e-waste — and see if it can be repaired. Other projects similar to LineageOS exists that support an ever wider set of hardware.</li></ul><p ></p><blockquote ><i >More in line with an overarching goal of hardware sustainability, an exciting project is the <b >Fairphone</b> which is close to a drop-in replacement for existing Android phones. See  <a href="https://sci-hub.se/10.1007/978-3-319-12142-0_3">T. Wernink, C. Strahl, <b >Fairphone: Sustainability from the Inside-Out and Outside-In</b> via sci-hub</a></i></blockquote><p ></p><ul ><li ><a href="https://wiki.lineageos.org/install_guides">Installing LineageOS</a>.  If you are somewhat tech-savvy, the instructions are very well written and easy to follow.  If not, consider finding a repair shop familiar with Android phones; or even some online vendors sell phones with LineageOS pre-installed.</li></ul><p ></p><p >This is what I use personally and would recommend to most people.</p><p ></p><center ><img src="../static/openphone-lineage.png" alt="LineageOS on a OnePlus" width=20%/></center><p ></p><center > my OnePlus phone showing the LineageOS logo </center><p ></p><p >If you have previously used an Android smartphone, LineageOS will feel very familiar. You can choose to use something like <a href="https://f-droid.org/en/">F-Droid</a> as an open-source equivalent of the <i >Google Play Store</i> or install proprietary software on top of LineageOS that allow access to the existing pool of Android apps if needed.</p><p ></p><p >But, there are some limits to this:</p><p ></p><ul ><li >The hardware that LineageOS runs on... is still proprietary! LineageOS alone doesn&#39;t solve problems like batteries being impossible to replace or no availability for replacement parts.</li><li >The software isn&#39;t even fully open source! The lingo for this is <i >binary blobs</i>, meaning there&#39;s some small closed-source &#39;blobs&#39; of code deep in LineageOS that control small pieces of hardware.</li></ul><p ></p><blockquote ><i >Of these <b >binary blobs</b>, the most fraught is the software used for the <i >modem</i>. The modem alone makes the goal of a totally open smartphone nearly impossible. <b >Qualcomm</b> has a legally-approved monopoly over effectively forcing use of proprietary software for any smartphone. See <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3893771">E. Hagemann, <b >Essential Facilities, Essential Patents, and the Essential Oversight of Qualcommm</b> via SSRN</a></i></blockquote><p ></p><h2 id="PinePhone">PinePhone</h2>
<p ></p><p >So, if you want a <i >true</i> open source phone, both hardware and software, what can you do? A promising project with a very active community is <a href="https://www.pine64.org/pinephone/">PINE64&#39;s <i >Pinephone</i></a>. The Pinephone doesn&#39;t build on AOSP and instead is a totally group-up approach using the Linux kernel directly. This is not something I&#39;d recommend unless you&#39;re truly dedicated to open source and want to be early to the first generation of open source telephony.</p><p ></p><center ><img src="../static/openphone-pinephone.jpg" alt="Pinephone with SXMO" width=50%/></center><p ></p><center > my Pinephone running a Linux distribution with <a href="https://sxmo.org/">SXMO</a> </center><p ></p><p >I&#39;ve used a Pinephone intermittently, and my experience is that</p><p ></p><ul ><li >Using the tools I&#39;m familiar with from desktop computers to do things on my phone is fantastic. My phone feels more like an extension of how I use computers already rather than being a walled-off monolith.</li><li >Being familiar with and preferring modest software on a very old computer is useful. RSS feeds, mpv+youtube-dl, IRC, email all work great right out of the box.</li><li >Transferring a phone number is ideally as easy as putting the SIM card in the phone. I had a lot of issues with this, but the issues were just a result of Verizon being a terrible company.</li><li >Software support is still early in development. A lot of what most smartphone users would consider required is not available. For example, alternatives to navigation apps like Google Maps are still very early in development. When you go to a bar you get to be the weirdo that doesn&#39;t have Venmo and can&#39;t scan the dumb QR code menus.</li></ul><p ></p><p >But... I really hope the Pinephone succeeds! It&#39;s one of the very few ongoing projects I&#39;m genuinely excited about. I would love to use the Pinephone as my daily use phone. I think the Pinephone gets as close as possible to the desktop computer idiom and makes smartphones feel like what they really are... just a really small computer!</p><p ></p><blockquote ><i >That modem issue I mentioned for LineageOS? The Pinephone community is actively working to reverse engineering and provide a replacement to the standard binary blob. It&#39;s an isolated effort and not going to be included in any stock installation — other projects don&#39;t want the legal culpability. This is an awesome example of a distributed open source community taking on an issue that would never be tackled otherwise. See: <a href="https://github.com/Biktorgj/pinephone_modem_sdk">pinephone-modem-sdk</a>, <a href="https://xnux.eu/devices/feature/modem-pp-reveng.html">EG25-G reverse engineering</a></i></blockquote><p ></p><h1 id="TL;DR: Where to Go From Here?">TL;DR: Where to Go From Here?</h1>
<p ></p><p >The next time you reach the end of an artificially short smartphone lifespan, I&#39;d encourage you to stop the cycle of predestined e-waste and refuse to support the companies that make it happen. Buy a phone second-hand.</p><p ></p><p >LineageOS is a mature, user-friendly software solution that exists <i >now</i>. But, it&#39;s a stop gap. I hope soon the Pinephone is a viable solution for the first smartphone — both hardware and software — that isn&#39;t shit.</p><footer ><p >read this on gemini: <a href="gemini://jleightcap.srht.site/blog/openphone.gmi">gemini://jleightcap.srht.site/blog/openphone.gmi</a></p>
<p >© copyright is cringe</p>