31–40 of 109 posts
Earlier quoted context omitted.
The whole story has killed any interest I had in their products. I was interested in buying a Pinebook and Pinephone, but not anymore.
I had been looking at an electronic soldering iron they had produced. Not sure how I feel now.
Earlier quoted context omitted.
Well the issue with this happening in private telegram channels is that this will now turn into a "he said" "they said" situation, none of this happened publicly and neither side can provide sources. At the time the argument was definitely not that the chips weren't available. Instead of delaying the PPP production by one day to get U-Boot sorted they decided to not ship mainline U-Boot at all. Which was only possibl…
You have every right to leave, and obviously if you're feeling burnt out, you made the right call for yourself. But it is frustrating that it seems like a distro preference issue has expanded into what will probably end up selling more proprietary phones at the end of the day.
I'm a bit confused by the whole bootloader situation. Locking down a bootloader on an open device seems quite bad, but what's the issue here exactly? The user can install any bootloader they want, can't they? I know the ARM bootloader system isn't anything like the PC bootloader system, but even if the bootloader is loaded from eMMC, in what way is the user impeded? I would guess all the user should need to do to use…
The "bootloader" isn't just a bootloader, it's effectively a critical firmware component. If the "bootloader" is missing or garbled, the board is bricked and can only be recovered by removing the eMMC, which would be very difficult for most users. Such a thing should not be stored on a data partition and managed like any other distribution package. If they aren't going to ship a separate SPI chip, the eMMC should at least be repartitioned to include a separate "firmware" partition and the bootloader should be shipped there. Distributions should then boot via a chainload mechanism, just like on x86 hardware. (This mechanism can be UEFI based but need not be.)
Earlier quoted context omitted.
The whole story has killed any interest I had in their products. I was interested in buying a Pinebook and Pinephone, but not anymore.
I had been looking at an electronic soldering iron they had produced. Not sure how I feel now.
Earlier quoted context omitted.
You have every right to leave, and obviously if you're feeling burnt out, you made the right call for yourself. But it is frustrating that it seems like a distro preference issue has expanded into what will probably end up selling more proprietary phones at the end of the day.
It's not just "distro preference issue" the way it sounds, more like "Manjaro is shipping barely working hacks and calls it 'this feature works'".
Why does Pine64 favor Manjaro so much? What do they gain by doing so?
So they included all the hardware requested by Martijn. What remains the rub here?
[1] At least as of a couple of months ago. I'm talking basic functionality being broken, like for example trying to add an icon to the home screen and the phone crashes. I encountered multiple bugs in just the first few minutes of usage.
Earlier quoted context omitted.
The cameras are far from "the simple stuff", it's one of the more complicated systems in mobile devices with multiple high speed components from different vendors that have to work together and not very much documentation for the hardware existing.
Admittedly, that's doubly concerning. Pine chooses the BoM; we don't. And if they're choosing unsupported/unsupportable chips without doing the barest of legwork to get them functional (or hell, get docs public), then that's a huge problem. Pine should be showing on their pages a hardware matrix showing what works and what doesn't. The Pinephone Pro doesn't qualify for the definition "phone". If they were serious, th…
Earlier quoted context omitted.
Admittedly, that's doubly concerning. Pine chooses the BoM; we don't. And if they're choosing unsupported/unsupportable chips without doing the barest of legwork to get them functional (or hell, get docs public), then that's a huge problem. Pine should be showing on their pages a hardware matrix showing what works and what doesn't. The Pinephone Pro doesn't qualify for the definition "phone". If they were serious, th…
There is not really any good options for the sensors, it's all a few closed developers.