5 ms·
> This product family will never run Linux, as developers will need to develop a new firmware from scratch. This is obviously not a problem for the earbuds, but
by bArray 4y ago
> This product family will never run Linux, as developers will need to develop a new firmware from scratch. This is obviously not a problem for the earbuds, but a big limitation for the player
Perhaps not Linux, but I suspect there would be a place here for a Unix-like platform that feels familiar. If for example we could get wide-adoption of something like the JVM or wasm3 [0] on these platforms, code could become quite portable, despite wildly different architectures.
For example, Apache's NuttX [1] (that I first learned from Lupyuen [2], a guy making great progress working with Pine64 products).
> Processing wise, this chip is well sufficient for TWS headphones, but very inadequate for an audio player. It will not drive a good screen, it nor run high-resolution flacs or (probably?) support a high-quality, high-bandwidth codec. In fact, a first generation iPod Nano (retailing for $149 in 2006) had 16MB RAM, so over 16 times what the PinePod would offer. In fact, even the features of any custom firmware are limited from so little memory
I wouldn't call it time just yet. Displays can be interacted with intelligently (to reduce pixel bandwidth) and ultra high quality audio codecs offer diminishing returns, especially when you don't have a DAC or headphones to make the most of them.
My advice to Pine64 would be this:
1. Consolidate your product lines. The Pinebook is just a slower Pinebook Pro, just go with the Pinebook Pro. The PineTab is just a Pinebook without the keyboard, again I would consolidate this with the Pinebook Pro and just make the keyboard detachable.
2. The SBCs should just go straight into the device, thus creating a clear upgrade path for future products. If you want a PineBook Pro running Quartz, just swap the boards (of course with daughter boards for USB expansion, display driver, power, etc).
3. Don't be afraid to kill off products. The Pinebook and PineTab have never seen a new release. The PinePhone appears to be taking a back seat to the PinePhone Pro. The PineCube is basically DoA due to the processing power struggling to process the camera image.
More generally, try to do fewer things, but do them well.
[0] https://github.com/wasm3/wasm3 https://github.com/wasm3/wasm3
[1] https://nuttx.apache.org/docs/latest/ https://nuttx.apache.org/docs/latest/
[2] https://lupyuen.github.io/articles/sensor https://lupyuen.github.io/articles/sensor
- megous 4y agoPinephone is not taking backseat to Pinephone Pro. If they kill off Pinephone, they'll have no smartphone that actually works and will piss off anyone who did a lot of work on software thinking this device is LTS as they promised.
- bArray 4y ago> If they kill off Pinephone, they'll have no smartphone that actually works and will piss off anyone who did a lot of work on software thinking this device is LTS as they promised. It's not to say they will kill it, but the Pinephone Pro is clearly the device they will move forwards with and spend time to develop. The A64 is simply too slow.
- megous 4y agoThat's not clear at all. It may simply turn out that RK3399 (as a tablet and notebook SoC) will be impossible to make power efficient enough, and with much much smaller userbase than original Pinephone, noone will work on fixing it.
- nsajko 4y ago> Perhaps not Linux, but I suspect there would be a place here for a Unix-like platform that feels familiar. It's just a tiny microcontroller, how could it run a Unix-like?
- bArray 4y agoCheckout Apache's NuttX [1]. It's pretty impressive. [1] https://nuttx.apache.org/docs/latest/ https://nuttx.apache.org/docs/latest/