33 ms·
Why I left Pine64
- ocdtrekkie 4y agoOn one hand, I understand your frustration here, for sure. But on the other hand, Pine devices have severely lacked for being able to tell users what the best place to start is. I've wanted to back to my PinePhone a few times and had to ask, like, what is in the best state to use, and nobody could tell me. Updating my PineBook Pro took a ton of investigating because the simple explanation of how to get from what mine shipped with to what new ones shipped with was hard to find, discussion of what mine shipped with was nearly gone already, and the process for upgrading it also had since changed! As someone who doesn't build distros, your post is actually really nice for me, now I know I should just install Manjaro on my Pine devices! About time they picked something.
- spijdar 4y agoI don't think the author meant that the problem was Pine "standardizing" on a single distro, but standardizing on a distro which has done (comparatively, AFAIK) little in terms of active software and driver development. By diverting people to a distro which mostly siphons up the work done by others, they risk poisoning the well and driving away the developers actually writing device drivers and infrastructure.
- MartijnBraam 4y agoThis is exactly right. And also a distro that is just refusing to disagree with pine64 when decisions are made that impact all distributions negatively
- ddevault 4y agoEven supposing your premise is correct (and it's not: diversity is good), the question becomes if Manjaro is the right choice, and it is definitely not. Manjaro is a very poorly run Linux distribution with misaligned incentives, poor practices regarding stability and security, and a history of problems playing well with others -- and they don't even work on the software that still needs to be written to make Pine devices useful. This is not the right horse to back.
- ocdtrekkie 4y agoDiversity is good, but diversity is good once there's a baseline of support accomplished. From a user standpoint, PinePhone has felt like it's spinning it's wheels while each developer builds support for their favorite feature into their favorite distro, so you have one distro where the camera works and one distro where texting works. I am not qualified to have strong opinions about particular distros, but I think Pine is extremely overdue for a defined reference implementation.
- ddevault 4y agoI don't entirely disagree. In fact I wrote a blog post making similar arguments: https://drewdevault.com/2022/01/18/Pine64s-weird-priorities.html https://drewdevault.com/2022/01/18/Pine64s-weird-priorities.... Ideally Pine64 would be facilitating the development of a software stack which is then shared among the distributions. But, that's not what they're doing -- they're all-in on relying 100% on "the community" to produce the software. So, given this constraint, are they doing it well? The answer is "no". Choosing Manjaro alone is not going to get the software built. As explained in TFA, the previous solution encouraging diversity did more to get the software built and is largely attributable for the platform's initial success in building out basic software support. Manjaro does not have a monopoly on the software experts, in fact, they have none of the software experts. By throwing Pine64's entire lot in with Manjaro they are burning the people who actually work on solving these problems. That's not a productive way to build and maintain a community.
- detaro 4y agoHow do the steps taken lead them to a better reference implementation? "we officially focus on distro X" - sure, that helps maybe, and I don't think many people object to if its just that, although its annoying if before you loudly promoted diversity. But it also means they need to be the ones doing the work. But they implement it through "We make life hard for all the other people writing code for our system - including those whose code we want to put into our reference", and I don't see how that's helping anything. They seriously risk that instead of "camera works only in distro Y, so we need to port that from there to reference" they end up at "camera works nowhere, because people from Y gave up"
- betwixthewires 4y agoWhy should they pick something? I thought the whole point of this was to build open hardware and let me pick something? If you want a manufacturer to decide for you what you should run on your phone, maybe just buy a Samsung or apple device. They've already got it figured out also.
- MartijnBraam 4y agoPINE64 hardware is not open hardware and it has never been marketed as such.
- yjftsjthsd-h 4y agoOpen in the sense of letting the user run whatever they want, not open-sourcing the hardware itself.
- Klasiaster 4y agoMany Android phones are also open like this as shown by pmOS: someone somewhere has to work on mainline Linux support and normally mainline doesn't really work and there are still some downstream patches left, meaning you can't run what you want unless you have a patched kernel (the same it true for the PinePhone and PinePhone Pro).
- megous 4y agoThey're just picking the default SW. You can still run whatever, including any other bootloader or OS. It's not like it's locked like a typical Android phone.
- yjftsjthsd-h 4y ago> But on the other hand, Pine devices have severely lacked for being able to tell users what the best place to start is. I've wanted to back to my PinePhone a few times and had to ask, like, what is in the best state to use, and nobody could tell me. It's fine to have a default option. The problem is when you cut support for running anything else. > As someone who doesn't build distros, your post is actually really nice for me, now I know I should just install Manjaro on my Pine devices! About time they picked something. That's old news; if you buy a Pinephone/book, they've come with Manjaro pre-installed for a while now.
- dtx1 4y agoI totally understand the Frustration the author has here. But I'd rather have any working software version than 10 that don't work well at all and that has always been my pine64 experience. Great hardware, barely any documentation, important hardware and software features don't work at all or are locked behind a very old kernel version
- detaro 4y agoHow does making alternatives harder to boot and pissing of maintainers of software components they rely on improve their quality long-term?
- jovial_cavalier 4y agoIt's an entity that's in a position to make a design decision - "We will have one bootloader flashed onto the eMMC - the same for every device we produce." It creates a standard which users and developers alike can fix themselves to. It is definitely a good thing, if you are worried about productizing -- but perhaps not so great if you want a diverse community of hackers.
- mkesper 4y agoWell, with SPI it was the same bootloader too.
- e2le 4y ago> The solution to this is Tow-Boot: a distribution of U-Boot that can be put in that flash chip. With this the U-Boot firmware can just be treated like system firmware and be updated through fwupd independent of what distributions ship. This would work not only for the PinePhone Pro, but would also enable things like installing your preferred Linux distribution on a PineBook Pro by popping in a flash drive with a UEFI installer, much like you can on any other laptop. SPI + Tow-Boot would have standardized the boot process and made it more robust.
- jovial_cavalier 4y ago
- ajot 4y agoWell, Manjaro is in a path to make some money; they incorporated a few years back and made deals with developers of privative software like Vivaldi and Softmaker to make their software the default option. I can't blame them, everybody needs to bring food to the table, but after reading TFA I believe they're hurting the FLOSS ecosystem around them.
- sgbeal 4y agoAnecdote: i backed pine64's first-ever Kickstarter and got two of their A+ boards (i think they were called). They claimed high performance and full HD video. In the end i couldn't get a single Android game, no matter how primitive, to run at more than a couple of frames per second and Netflix was too jittery to watch. They've been on my poo-list ever since. About 18 months ago i pulled them back out and ran XFCE on one of them. It crashed with the X11 error (i kid you not): "event arrived before it was sent (your hardware is too slow!)" (going from memory - it might have been phrased differently). i ended up giving them away to someone who wanted to use one for a pihole server, and i was glad to be rid of them. Utter garbage, they were.
- HidyBush 4y agoSo you backed a developer-oriented project all about open source software and your test to see if it was garbage or not is to consume proprietary video content and play video games through virtualization?
- criddell 4y agoThese are things lots of people, even developers, do on their phones - play games and watch videos.
- HidyBush 4y agoDon't you think there's a difference between "it's annoying I can't watch full blown movies on this experimental phone" and "it's garbage because no Netflix"?
- criddell 4y agoIt depends on what you were expecting. On their A64 Kickstarter they said the graphics capabilities are higher than the original XBox's level of performance. That might lead a person to expect it to play games well. The screenshot included a Netflix icon. The Kickstarter FAQ says it can play UHD 4K video. That might lead you to believe you could watch Netflix on it. As I understand it, the phone is based on the A64 board. On top of all this, on the PinePhone page they link to a video titled something like "This $200 phone can do ANYTHING!".
- neilv 4y agoIt's good to see Martijn Braam fought the good fight on things like the PinePhone Pro bootloader in eMMC, and I'm sorry to hear the situation became untenable. After Pine64 went to all the trouble to make a series of branded early developer editions for various distros, and ongoing community goodwill outreaches, I didn't expect something like this to happen. IMHO, any handheld hardware right now wanting to be open and sustainable Linux should probably start by making sure it's solid with PostmarketOS configured with a mainline kernel, as a good test. (PostmarketOS is a litmus test for purity, and has had a bunch of work to make bringing it up easier than the usual server/desktop purity test of Debian.) Working Phosh and Plasma userlands running atop PostmarketOS are good further tests. Supporting additional distros, userlands, and hacking is also important. (Even if the hardware is something like the Purism Librem 5, which has invested heavily in lots of good distro work, if PostmarketOS with mainline kernel boots cleanly and runs solidly, that's a good sign.)
- MartijnBraam 4y agoWe've spend a lot of time optimizing the developer experience in postmarketOS by making easier tooling and writing more documentation, I'm glad it helps. While Debian has more strict policies on software licensing etc the musl component of postmarketOS pretty much makes sure that no closed source software will ever run in userspace. The main difference is that postmarketOS does deal with firmware for hardware while Debian doesn't. Hopefully we someday get at a point where even the firmware for these devices isn't problematic anymore.
- _chu1 4y agoWhy prevent closed source software from running in userspace? Even in Fedora Linux I find myself having to use closed source software a lot for daily tasks.
- MartijnBraam 4y agoThat just happens to be a side-effect of using Alpine as base distribution. If you really need something closed source it's still very easy to just use a flatpak for that.
- 3np 4y agoUnless PINE64 changes course hard, I think this will be the moment they died, so to say. They may keep making SBCs etc alongside other vendors but the phones/tablets/laptops/watches/etc would continue being novelties and realistically majority e-waste. Really quite sad. If I'd name one single person in the FLOSS community who's done the most good for mobile open source, it'd be OP. Thank you so much for your service, work, and patience up until now. I fail to understand the reasoning of PINE64 on stuff like this recently. It's like they became a spiritually fundamentally different company. Can't see how this is supposed to make them money either. > Now I can just focus on making postmarketOS work better. On the PINE64 hardware, and all the many other devices supported by postmarketOS ...Maybe not so terrible after all. For a while there I almost thought pmOS was
- MartijnBraam 4y agoI hope PINE64 doesn't fail, they did great before and I think they could continue being great. luckily postmarketOS existed before the PinePhone and can easily exist after, the pine devices isn't even the majority of devices we support.
- 3np 4y agoAs someone who's more familiar with PINE64 than the rest of us, are you as confused as I am? I've noticed minor red flags slowly building up over time and at least from here there are some major inconsistencies with their stated vision and where they seem to actively be going. I think I started seeing it somewhere around the PPP announcement. I really want them to succeed but I have a hard time making sense of them lately.
- bluGill 4y agoAFAIK the pine devices are the only ones you support that are not a big pain to install. I have a few old android phones that you "support", but when I looked at what I had to do to install I decided it was too much effort. Pine devices claimed to be easier because you just throw in a SD card and go (of course the fact that the new ones are not this is why you left)
- xrd 4y agoThank you for all your efforts, Martin. I'm left feeling like there is not a good way to align incentives for a world-changing project like Pine. It's really disappointing to read. I just yesterday setup my PinePhone with postmarketOS, and the sd card setup was so easy, and it is frustrating to hear there is absolute uncertainty about whether that be the case with future devices. As a customer with three Pine devices (tablet, phone and watch), I'll definitely be writing to Pine and asking them to clarify what they as a company say about this post. Thanks for writing it up.
- ddevault 4y ago> I'll definitely be writing to Pine and asking them to clarify what they as a company say about this post. Please let us know what they say.
- dcz_self 4y agoWith my Librem 5 developer hat on, I'm surprised that a SPI chip matters at all. The Librem 5 eMMC contains a hidden "partition", which is preferred by the CPU to boot from over the "data partition" where the OS boot loader resides. It should be possible to put Tow-boot into this hidden area, and the OS stored in the data area will have no say. No separate flash chip needed to have an independent boot loader. I wonder why the PinePhone needs a separate chip for this purpose. Is the CPU unaware of hidden areas on the eMMC?
- MartijnBraam 4y agoThat does work on the original pinephone, the A64 SoC can boot from the mmcblk0boot0 partition. The rk3399 in the pinephone pro is way more problematic which it is why it's important to have the SPI and also have the SPI flashed from the factory. The pinebook pro batch that has shipped now did not end up with Tow-Boot and instead has BSP u-boot on the eMMC which makes it unable to boot anything else than the shipped manjaro by default. Of course it's only the other distributions supporting this platform that have to deal with this
- sigmaris 4y agoThe boot ROM in the RK3399 in the PinePhone Pro has a hardcoded boot order, and doesn't use the special boot partition of the eMMC - it only looks for a bootloader on the data partition at a fixed sector (64).
- zozbot234 4y agoWould it be possible to flash Tow-Boot to that sector and only use the rest of the partition as actual data storage? It seems like it would effectively work the same as having a separate SPI hardware chip on-device, while also restoring distribution independence. The downside is that implementing this might require some special-case support though it could likely be implemented most conveniently by using, e.g. dm-linear, so only configuration changes would be needed, not new kernel code.
- MartijnBraam 4y ago
- readingnews 4y agoHrm, where is there another "open source/hardware" phone that is not more than a new iPhone (e.g. not a libre phone)? I was really thinking about getting the Pine phone pro, but now I am a bit shaken.
- MartijnBraam 4y agoI think that the situation is not that bad that you should skip the PinePhone Pro, these are definetly things that can be fixed. There's also a lot more platforms with varying degrees of linux-ness. There's the PinePhone and Librem 5 which are the most well known but on postmarketOS there's now also mainline linux on a bunch of qualcomm devices and I think the mainlining community for those qualcomm platforms is at the moment way healthier than the pinephone one.
- jancsika 4y ago> There's the PinePhone and Librem 5 Just an FYI to anyone reading this: Purism is actively making it difficult for its customers to receive a refund. Many of those customers have been waiting years for their phones. Here's just one example I found scrolling through a list of complaints on the purism subreddit: https://www.reddit.com/r/Purism/comments/syoydj/librem_5_refunded/ https://www.reddit.com/r/Purism/comments/syoydj/librem_5_ref... That's a rare case because the user reports receiving a refund (only after a year and filing a complaint with their AG). There are many more complaints of users being told they have to wait until an unspecified shipping date to get a refund. It is not ethical for a company to attempt to draw out or flat out refuse refunds to users who have been waiting years for a product. And while you are certainly free to hack away on their hardware, until/unless their business practices change you ought to be explicitly discouraging users from (attempting) to purchase a phone (or really, anything) from Purism.
- megous 4y agoYou can always boot/install whatever you want on the Pro, too. It's just one extra step. It's as open as it ever was.
- lizardactivist 4y agoI understand the author's disappointment, but despite the defeatist tone of the writing I am convinced that this will thankfully not be the end of PINE64.
- preisschild 4y agoSome more information about Manjaro: https://manjarno.snorlax.sh/ https://manjarno.snorlax.sh/ Sad to see Pine64 only listening to them.
- 3np 4y ago> Garuda, which aims to have a Manjaro-like experience without holding back packages and the problems Manjaro has. The rest of the point aside, is the author is this harsh on Manjaro I must assume they actually aren't that familiar with Garuda. They're a jolly bunch and it looks great but the quality is severely lacking. It can be fun to play around with in a VM for inspiration and snag some snippets to your dotfiles but I wouldn't recommend it for anything mission-critical. It's a cool experiment to push btrfs as the only root filesystem option but that's also something that's not for everyone.
- Linda703 4y ago[dead]
- criddell 4y ago> The original PinePhone was brought up on the existing Linux Mobile projects like Ubuntu Touch, postmarketOS, and Maemo Leste, and also spawned new Linux distributions like Mobian and Danctnix ARM. This grew until there were 25 different projects working on the PinePhone — an apparently thriving community. What you see as a thriving community, others might see as a fragmented market. I don't know if this makes sense, but it feels like the multiple distributions and overlapping projects trades off deep development for broad development. Maybe it's the inevitable result of everybody scratching their own itch and doing what they can do, or maybe it's a sign of a community that can't work together.
- v-yadli 4y agoWell I think at this stage we can hardly call it a market -- it's not 10 different android distros that stem off from a solid codebase, but different groups of developers that interact with each other to bring up the base. When you destroy the nest for these dev groups, there will be no more software for a fancy distro to package.
- ddevault 4y agoIt's not a market and it does not act like one. These are not a bunch of startups hoarding intellectual property, they're a group of open projects working together under different flags to build a single product. The work of each is incorporated into the rest.
- criddell 4y agoThat makes sense. I was thinking it was KDE vs Gnome all over again with a lot of duplicated effort.
- johnklos 4y ago> others might see as a fragmented market So uneducated outside views matter more than the communities themselves? > multiple distributions and overlapping projects trades off deep development for broad development So volunteers are supposed to - I don't know - know better, stop working on what they want to work on, and coordinate? And it's the fault of these volunteers that there's "fragmentation"? You think this is a zero-sum game, and that volunteers are the equivalent of workers at a business who're dividing their energy amongst competing projects instead of working together. That's both incredibly naive of you and also incredibly presumptuous. On the other hand, there is the problem that work in one project can and should be usable in another, but when that doesn't happen, that's just because that's how the Linux communities are sometimes.
- skymer 4y agoAt best, the Pinephone is buggy software on low priced but mediocre hardware. It has always been like this, and it is not going to change. There is nobody willing to spend the millions of dollars it would take to make it otherwise. Meanwhile, AOSP is fully working, open source Linux-based phone software that runs on lots of modern hardware from a variety of manufacturers. Distributions like GrapheneOS have put huge effort into de-googling, privacy and security. Cameras work. SMS works. Phone calls work. There are lots of apps. I hear there are even a few phones that can do wireless charging! Why waste any more mindshare on the Pinephone?
- ocdtrekkie 4y agoOn the contrary, AOSP is a largely nonexistent OS thrown over the wall by an evil adtech company so they can claim the proprietary malware-laden version they ship to 99.9% of consumers is open source. You cannot remove the stench of Google from Android and we should stop trying. We should use a scorched earth policy of avoiding any code that Google has written and assume it is harmful by default.
- zozbot234 4y agoAOSP has way too much churn for a sensible system. A Linux phone should just work, and share as much of its code as possible with Linux systems running on other device classes; distributions like pmOS and Mobian (and quite possibly Debian Mobile in the future) are working towards this goal.
- selfhoster11 4y ago> Why waste any more mindshare on the Pinephone? Android is a horrible platform to hack on. I'd much rather hack on something closer to base Linux - think Maemo or similar.
- dbeley 4y agoAOSP is still a google-controlled project that requires a ton of blobs, whereas the Pinephone (and other linux compatible smartphones like the Librem 5) has an entire ecosystem of healthy linux distros (from Mobian to Archlinux) running as close as possible to mainline linux. > GrapheneOS have put huge effort into de-googling They are doing great work but they're still depending on google for maintaining Android (Can GrapheneOS do anything against a feature pushed by Google in Android 13/14 and so on? Nope). > Cameras work You still lose all the post-processing stuff which account for a good portion of perceived picture quality.
- PragmaticPulp 4y agoWhile I’m sad to see the author leave such a project and grateful for his contributions, I have to say I think Pine64 is actually in the right here. One of the biggest challenges in running an open source hardware project like this is catering to two very different audiences: The majority of your customers (99.9% or more) just want the hardware to get up and running quickly so they can get to their specific need or application. They don’t want to have to read endless IRC or Discord backlogs to figure out the current best distribution to use or read potentially outdated half-finished Wiki articles describing the tradeoffs of various distros. They want it to work and to get started quickly. The open-source developers have an entirely different set of desires, preferring endless tinkering with the internals and actually enjoying the process of trying different distributions, building and testing bleeding-edge board support software themselves, playing in someone’s experimental fit branch to get one thing working, and other time-consuming activities relayed to the board itself. If you let a project cater too much to the developer community at the expense of the 99.9% customers, it starts to become a huge problem. For the best example, consider the huge success of the Raspberry Pi and their Raspberry Pi OS, while even the biggest competitors (such as PINE64) remain relegated to mostly obscurity. The hard truth is that if you want to make a product like this successful and mainstream, you need to narrow the focus and be ruthless about cutting costs, simplifying, and getting your users up and running with one easy, primary way to get started. I have several Pine64 products and they all suffer massively from the fragmentation and compromises they’ve made. Fun if you’re a kernel developer who spends tens of hours every week keeping up with your friends in the small developer community. Not fun at all if you just wanted to use the product for something and you realize you could spend weeks or months sorting through all of the disparate information sources and developer communities before you can have the product working enough to get started on that thing you actually wanted to build with it.
- detaro 4y agoHow does making booting alternatives harder and pissing of people developing software components they themselves want to use in their "get started quickly" distro help Pine64? Prioritizing their own efforts towards one distro doesn't have to mean harming the rest of the ecosystem they benefit from.
- 4oo4 4y agoI just wanted to say thanks to Martijn Braam for all the work he's put into PostmarketOS along with the other pmOS devs. I was lucky enough to snag a pinetab when the first batch was released, and I was blown away by the quality of pmOS. This was my first taste of mobile Linux, and pmOS was easily the best distro I used on it in terms of documentation, install tools, performance, and package selection. pmOS has the advantage of being more mature than other mobile Linux distros, but all the work they've put in over the years has really paid off and helped make the ecosystem more viable, so thank you! I'm really sad to learn about this with Pine64, I had a hint of this when I saw there has never been a second batch of pinetabs and no communication about it (at least that I saw). I had no idea it was this bad though and this makes zero sense why they would kill the ecosystem they spent so long building. It sounds like the decision was made purely based on reducing user support requests? Even though someone that buys one of these is likely to be a tinkerer/hacker with prior experience with *nix and distros already have their own community support channels and would already be doing most of that work for free?
- twiclo 4y agoMartin, if you're still around, could you tell us what phone you would recommend to someone if they were wanting to switch to daily driving PostmarketOS? Do you still see that as the pinephone or do you consider another device as having a more promising future/better hardware/better support?
- CameronNemo 4y agoHe mentioned the SHiFT 6mq elsewhere in the thread. And the SDM845 SoC as well.
- bioemerl 4y agoIf I want a phone locked to a single Linux distro controlled by the vendor I will buy an Android phone and it will beat the pine phone in about every single way.
- megous 4y agoIt's not locked to anything. You're interpreting the original article wrong.
- cycomanic 4y agoI am a big FOSS proponent (I almost exclusively use FOSS), but I find it difficult to not become disillusioned recently. It seems the large corporations like FANGs are largely pushing OSS to use volunteer work to make software a commodity, while trying to accumulate more and more data, which they consider their main value. At the same time we have companies like pine, who seem to support FOSS through relatively open hardware, but which to me seem increasingly more about a way to make a profit of the FOSS trend by using volunteer work without any investment from their end. I question if they are actually interested in their devices actually being functional for regular use. See also this article: https://news.ycombinator.com/item?id=32330043 https://news.ycombinator.com/item?id=32330043 Finally we have distributions like Manjaro who seem more interested in growing their slice of the pie at the cost of other distributions instead of growing the whole Linux ecosystem. https://www.reddit.com/r/linux/comments/hxpj87/change_in_manjaro_team_composition_announcements/ https://www.reddit.com/r/linux/comments/hxpj87/change_in_man...
- bruce511 4y agoI feel like you're inferring qualities in OSS that don't (explicitly) exist. This is not uncommon. Specifically; >> It seems the large corporations like FANGs are largely pushing OSS to use volunteer work to make software a commodity Why would you expect them to do anything different? Companies are driven by profit, not some sense of morality. OSS licenses allow them, even encourage them, to trade volunteer (aka free) labor in return for source code availability. >> which to me seem increasingly more about a way to make a profit of the FOSS trend by using volunteer work without any investment from their end. There's often serious investment from their end, but that's irrelevant. They absolutely want to leverage FOSS to make a profit. And that's explicitly allowed by OSS licenses. To put it another way, your disillusionment is because of a "bug" on your end, not on theirs. They are behaving exactly as OSS is designed. Your _expectation_ of their behavior is inaccurate, and so does not match reality. Not surpisingly this makes you sad :(
- cycomanic 4y ago> I feel like you're inferring qualities in OSS that don't (explicitly) exist. This is not uncommon. Specifically; > >> It seems the large corporations like FANGs are largely pushing OSS to use volunteer work to make software a commodity > Why would you expect them to do anything different? Companies are driven by profit, not some sense of morality. OSS licenses allow them, even encourage them, to trade volunteer (aka free) labor in return for source code availability. Apart from the fact that companies and corporations can act ethically despite driven by profits, I did not say I'm desillusioned with the corporations, but the FOSS community. Essentially it is us as users&developers who let this happen. > >> which to me seem increasingly more about a way to make a profit of the FOSS trend by using volunteer work without any investment from their end. > There's often serious investment from their end, but that's irrelevant. They absolutely want to leverage FOSS to make a profit. And that's explicitly allowed by OSS licenses. Again I don't say that companies shouldn't make a profit, but when OSS started to become more mainstream many (including myself) believed that it would be a way to break the stranglehold of large monopolistic corporations on the software world and create an ecosystem of relatively small software companies that would customise OSS software for specific needs on a relatively even playing field. Instead what happened is that OSS might have accelerated the concentration of the software world, by making small jobs essentially unviable. Regarding investment, I expect that FANGs still very much come out on top, just imagine what they had to pay in licencing cost for their datacentres if no oss operating systems existed. Also much of these investments are towards use cases with very little benefit for normal users. > To put it another way, your disillusionment is because of a "bug" on your end, not on theirs. They are behaving exactly as OSS is designed. Your _expectation_ of their behavior is inaccurate, and so does not match reality. Not surpisingly this makes you sad :( I think you misunderstand me, my disillusionment is with the idea what FOSS could have achieved (and people imagined) but didn't. I sometimes wonder if FOSS has made the world a better place, like many hoped it would. You might not care about it but I do.
- jokoon 4y agoI really want such project to succeed but I guess there is no market or enough money to make it happen. I've also asked repeatedly why those kind of projects are not using android forks instead of other things, and I never got an answer that made sense. Android is open source and has proven that it's a robust system, I don't understand why people want to use something else.
- colordrops 4y agoI use an Android fork, but I can understand why they'd want to use Linux. If they succeeded you'd start seeing more cross pollination of apps from the desktop, and perhaps more mobile focus from Linux devs. Also, has anyone really done anything more than just tweak AOSP? Honest question, I don't know. If say Google completely abandoned the AOSP and went full Fuschia (I know this isn't likely), is there any individual or group out there that knows enough about AOSP to take it over?
- yjftsjthsd-h 4y ago> is there any individual or group out there that knows enough about AOSP to take it over? Probably downstream vendors like Samsung have the technical capabilities. I seriously doubt that they'd be interested in continuing an open source project for wider use, but just maintaining their own fork would be totally doable.
- deleted 4y ago[deleted]
- matheusmoreira 4y agoIt's really unfortunate. I remember being excited about the pinephone. I had no idea this was happening behind the scenes. Why elevate Manjaro if others were doing the work? Why was that decision made? It doesn't make any sense to me. Thanks for all the work you've done!
- megous 4y agoWhy? Democarcy I guess. https://www.pine64.org/2022/01/31/pinephone-community-poll-results/ https://www.pine64.org/2022/01/31/pinephone-community-poll-r... (I don't know why, but it was the most popular distro in the pine64 poll)
- blendergeek 4y agoManjaro with Plasma Mobile had been the default for more than a year when that poll was conducted. If you look at the results, you will notice that Manjaro is not the most popular distro for people who use the phone as a daily driver. This indicates that people who keep Manjaro are less likely to actually use the Pine phone as a phone. So it seems that the reason it is the most popular is that is the default. If you look at what interface people like, the default (Plasma) only scores 21% in that poll and it falls to 18% amongst those who use the phone as a daily driver.
- megous 4y agoYeah, that's quite likely.
- goodpoint 4y agoPolls run on the fediverse showed different results, with manjaro not being the winner...
- linmob 4y agoIIRC it was something about personal and/or business relationships and commitment of resources. Actually, going with Manjaro was only half of what made me question the decision: At the time, when PINE64 introduced the "Beta Edition" Plasma Mobile was still quite bad (it improved a lot since).
- CivBase 4y agoAs an outsider, it sounds to me like Pine64 has failed to explicitly state how much support they are willing to offer each of the popular distro projects. The Community Edition releases implied a pretty high level of support for each of those projects at the time, but now that support has been dropped and the project developers feel lead on. I don't think it's too late for Pine64 to recover from this, though. IMO, they should define a few support tiers and make it very clear what will be supported at each tier. Then they should commit to a support tier for each of the popular distros for some period of time (eg 3 years). I think it's okay if some projects receive more support than others. But the PinePhone will live or die by the health of its development community. Those developers need to know they're working on solid ground. I understand that Pine64 is trying to position themselves for greater mass market appeal. I'm part of that market. Maybe Manjaro is best suited for appealing to that market. But regardless, Pine64 shouldn't loose site of what make the PinePhone so appealing to begin with. I haven't bought a PinePhone yet but I've been optimistic about its future and I've hoped to eventually get one. It's primary appeal to me is being able to easily setup whatever distro I want. Without that, I will be much less forgiving of its shortcomings next time I'm considering buying one.
- iuugh0098fghdf 4y agoI own one ( community edition ), am currently using one, and still am somewhat optimistic. I should disclose those that I am running PostmarketOS though ( and it makes me glad author will still contribute to that project ). I am not sure Pine was ever about mass appeal. It was supposed to be for people, who want control over the hardware they own. That seems a little different from mass appeal. Maybe I misunderstood their value proposition.
- monopoliessuck 4y agoI was burned pretty hard by Purism and no longer trust the company. Pine64 though I loved. I have an original PinePhone, the postmarketOs community edition unironically. I have been cheering Pine64 for a long time since, from the outside, they have been doing everything right. This is sobering and saddening. I have a Pinebook Pro too and Manjaro is pushed heavily. Manjaro is just not a very good distribution and their security awareness is wanting, but even if they were the best of the best, the fact that they get special preference flies in the face of a FOSS phone. I don't know why Pine doesn't see this, what they were doing with community editions was golden! I think Pine has their eyes on market capitalization at this point with Purism floundering, they probably think they can capture the niche. It's sad to see the shift. Hopefully they can course correct.
- shrimp_emoji 4y ago>Manjaro is just not a very good distribution Uh, excuse me? It's user-friendly Arch; i.e., the best distribution. >their security awareness is wanting Admittedly, I don't know what this refers to or compared to what distro. EDIT: https://news.ycombinator.com/item?id=32503090 https://news.ycombinator.com/item?id=32503090 Ah, lol. Anecdata for my weak defense: I used Manjaro for years, and none of the problems there affected me.
- nexthash 4y agoI think this is the inevitable outcome of any movement of Linux to the mainstream (Purism has done something similar). As Martijn said in the article, PinePhone devices were operable with 25 different projects. That's 25 different variations of Linux fighting over market share. As Pine enters a growth phase for their business, the consequences of this are going to manifest as paralysis. Improvements and advancements would stagnate due to the 25x duplicated effort, and resources would be lost in keeping those projects happy. Also, any potential user looking to switch would be deluged with options, which is what crippled desktop Linux. While I do not understand enough about Pine to know why they specifically made the business decision to gut their dev community and go with Manjaro Linux, my guess would be something along the lines of Manjaro's widespread dominance as a top Linux distro backed by a powerful foundation. Pine is pivoting to what they have decided is their future: a full-stack hardware to software open source offering that in their eyes would have a better shot at cracking open the phone market. They probably were aware of the consequences, but have bet on making it big and creating a new, streamlined ecosystem after extinguishing this one. It remains to be seen if they will succeed.
- zozbot234 4y ago> 25x duplicated effort People keep saying this, like too much effort is a bad thing. But OP makes it clear that there's very little duplication of effort in the Linux-on-phone/mobile/SBC community - most developments are shared community-wide. There are some technical divergences (Alpine/musl vs. glibc- and init-based systems for example) that can impact direct compatibility, but they're very minor.
- asdfasdf23r23r 4y agoCorrect. This is non-sense speak by non-developers. Greedy non-developers. they "sell" it as "25x duplicated effort" but in reality, there's 25x little tweaks to a build system, that give thousands of people zero effort to port their known platform right away. Now those thousands of people will have REAL effort to adapt their knowledge and existing ways to fit that one holy way enforced by the device true owners. In reality it is "25x places where i will have to hide my plan for monetize this". Just like most other projects, greed always destroy everything the community help build in good will.
- cat_plus_plus 4y agoGiven their niche business model, Pine64 is probably barely staying alive, especially in the age of COVID-19 and recession. I do hope they are able to offer open source range of devices, even with limitations. Stepping back from emotions, MicroSD booting is usually quite useless, tried that quite a bit on Chromebooks and everything keeps hanging waiting for I/O. Given limited resources, maybe they are hard pressed to just make what they ship with device not suck badly?
- axelthegerman 4y agoMicroSD booting is brilliant as it allows the OS to install itself onto eMMC. Also when you have an OS installed on eMMC but need to fix something or want to try something out, all you need is to pop in a micro SD and it will boot from it.
- LtWorf 4y ago> And in my role for the postmarketOS distribution, I developed the camera stack. So now i know whom to blame for the fact that the camera app crashes 90% of the times before I manage to take a photo.
- kop316 4y ago> So now i know whom to blame for the fact that the camera app crashes 90% of the times before I manage to take a photo. Heh, so every so often, I read an L5 or Pinephone review and they say "I had some weird problem with MMS and it never worked". Naturally, since none of my apps have any tracking with them, I have no idea what happened or what is wrong. Thus, I reach out to the author to file a bug or send me logs. If they respond, they go "sure, I will get around to it", but I have yet to have it happen. I tell that story because I wonder if you ever reached out to Martjin or any of the developers. It may be the first time they have ever seen the crash. You may have found an interesting corner case that they can fix for you.
- noname120 4y agoYou know whom to thank for the camera stack actually existing. Unpaid FOSS developers owe you absolutely nothing. This kind of self-entitled behavior and snarky comments are some of the major reasons why unpaid devs burn out and stop contributing. Don't be one of the people to blame for developer exodus away from FOSS.
- megous 4y agoHaha. Don't forget to blame me for the green tint of your face. ;-)
- shrimp_emoji 4y agoWho are you, Mannoroth?
- megous 4y agoI wrote the camera driver for the selfie camera, and parts of a sensor interface driver, and the driver gives you a green tint by default. So I'm blameable if the parent commenter dislikes the green tint. ;) Just a bit of a fun joke, for people who know the context.
- throwaway22032 4y agoThe idea that Pine64 would go with Manjaro of all possible projects is utterly hilarious. Essentially everyone I know thinks of it as being Arch in a gimp suit. Some sort of rlysmart teenager's pet project rather than an actually serious tool for a million different reasons that most people can't even be bothered to get into.
- ge96 4y agoHope Pine64 still continues. Recently topics such as "injecting ads into homescreen" make me fear for my phone.
- Fnoord 4y agoLack of warranty is the reason why I don't like this project. I still got some of their devices (PinePower is neat for its price, but again: without warranty).
- megous 4y agoThere's 2 year warranty if you buy from EU store.
- desertraven 4y agoI’ve read that in espionage, open source companies are disrupted from the inside. Is an open source, non trackable device with future potential to replace the current situation worth that level of action? Pure speculation!
- WhyNotHugo 4y agoWhat you're suggesting is not at all new, there's even a nice declassified manual on sabotage and how to carry it out: https://www.hsdl.org/?view&did=750070 https://www.hsdl.org/?view&did=750070 (or https://www.hsdl.org/?abstract&did=750070 https://www.hsdl.org/?abstract&did=750070 ) A lot of projects claim to be privacy-centric or love open source, but behave quite the opposite. After reading the above manual, I've been wondering if it's pure incompetence or someone deliberate pushing things that way.
- humanwhosits 4y agoI just want pine to provide hardware that can run a linux kernel without any binary blobs and leave the distros to whoever feels like working on that stack
- immibis 4y agoIt does this, except for the "without binary blobs" part, but at least the blobs are well-contained.
- mastazi 4y ago> Much of the original hardware bring-up was done by Ubuntu Touch. Mobian developers built the telephony stack via their eg25-manager project. And in my role for the postmarketOS distribution, I developed the camera stack. > Manjaro Linux has been largely absent from these efforts. > In some cases the Manjaro involvement actually causes extra workload for the developers by shipping known broken versions of software and pointing to the developers for support. Which is why https://dont-ship.it/ https://dont-ship.it/ was started. Other distributions like Mobian and Ubuntu Touch are miles ahead that broken thing that Pine chose to adopt as their default distro. When I got my PinePhone, nothing was working, not even the home screen! So I looked for help on the forums and people were like "LOL no one uses that, just install Mobian or Ubuntu Touch". I tried both, and they were actually pretty OK, I could more or less daily drive the PinePhone! I think the main reason people repeat that the PinePhone is not ready for use as a daily driver, is that the default distro is completely broken. Pine64 are shooting themselves in the foot in a spectacular way.
- hutzlibu 4y ago"Other distributions like Mobian and Ubuntu Touch are miles ahead that broken thing that Pine chose to adopt as their default distro." I really like Manjaro - on my desktop. So initially I was very happy that they went with it, but since manjaro is desktop focused - it is a great mystery WHY the choosed it at all and not indeed went with Mobian and co?
- mastazi 4y agooh yes, the problem is not Manjaro itself, it's the particular version of Manjaro that is used on PinePhone. I heard good things about Manjaro itself and I have no doubts that it's a good distro! yes, I really don't understand why they chose to ship that half-baked mess. I get it, PinePhone is for "techies" and the average user knows how to change distro, but the default should be functional. System 76 or Purism laptops don't come with broken distros ¯\_(ツ)_/¯
- noasaservice 4y agoAgreed. Pine the company is a bloody tirefire. I've tried to support them, and have gotten burnt again and again. Nope. Just no. Let them due so a different company can take the oxygen and run with the community.
- eschaton 4y agoThe ARM ecosystem is really hobbled by the lack of a standard boot loader and device tree mechanism, and the RISC-V ecosystem is heading down the same path. There are several good Open Source implementations of IEEE-1275 Open Firmware available now (see https://github.com/openbios https://github.com/openbios for some). Everyone should just use it instead of implementing their own solutions, to keep the boot loader independent of the operating system while still ensuring broad functionality.
- yjftsjthsd-h 4y agoOr UEFI, which works fine on ARM & RISC-V.
- eschaton 4y agoAnd which is also quite a bit more complex, compared to Open Firmware.
- yjftsjthsd-h 4y agoSure; I would have preferred a world where OF won, but that's not where the ecosystem went. And UEFI is... fine, and in this case I think the network effects are worth it.
- jvanveen 4y agoThanks for your hard work on the Pinephone Martijn! I really enjoyed reading your posts about the Pinephone, Megapixels and Tow Boot.
- jvanveen 4y agoResponse from Pine64: https://www.pine64.org/2022/08/18/a-response-to-martijns-blog/ https://www.pine64.org/2022/08/18/a-response-to-martijns-blo...
- pbronez 4y agoThanks for flagging. This should get its own post too. Maybe @dang can pin this to the top so it’s easy to find?
- greatgib 4y agoThere are already physical switch on the back of the phone. I don't understand why there couldn't be one to select the CPU boot drive: eMMC or sdcard?
- Roark66 4y agoIt is up to Pine64 to decide if, and who, they choose to support with cash for OS development. Is what they did a good choice? Probably not. Are they still the only modern hardware vendor that published (almost) all the driver's source code and register level documentation for the MCU. Yes! If I as an individual want to do something with a modern SBC that packaged in software doesn't do Pine64 is the only choice for hardware. Same in wearable tech space (pine watch). Good luck trying to get register level documentation for some parts of a raspberry pi's, or any other sbc's. I've spent last few weeks working on pine64's hardware at a very low level (mostly rewriting sony's imx219 sensor driver to fit my needs and trying to squeeze out the latency out of the image processor). Specifically I use Soquartz and Quartz64-A (they're very similar). I went from knowing nothing of the hw and the tool chain and finding every prebuilt image on the Internet as not booting to being able to rewrite the camera driver and tweak the rkISP drivers, generate my own os images etc in few weeks of spare time. This was possible only thanks to the rockchip documentation, the open source BSP kernel (that runs Linux 4.16) and someone at pine64 forums who published how to setup the tool chain. Without pine64 all I'm interested in would require significant reverse engineering effort. Also the mainline kernel support is progressing too. Is the documentation really good? No, the English versions, save few crucial docs, are quite bad. The Chinese versions are better, but still they leave a lot of important stuff out. Is pine64 making only good decisions as a business? No way. Is the community vibrant? If you can call 2 guys doing all replying to questions on the forum than maybe. Still, if we want truly hackable hardware to exist in future we should support their efforts. Let's explain what they do wrong, but let's not turn our backs on them completely.