April update: no more unicorns

Lukasz Erecinski Apr 15. 2022 30

This month’s update is packed to the brink with news: the product team is negotiating restarting Pinebook Pro production, QuartzPro64 will be heavily subsidized and developer sign-ups are now open, we’re introducing the PineSound project, and PinePower power supplies will be making a return to the Pine Store soon. I cannot recall the last time I had so many positive things to report on, so let’s get to it. 

You can watch the synopsis of this month’s community update on YouTube (embedded below) as well as on Odysee and PeerTube. To stay up-to-date with PINE64 news make sure to subscribe to this blog (subscription widget at the bottom of the webpage), follow the PINE64 Telegram News channel, the announcements channel in Discord as well as our Twitter and Mastodon.

I’d like to thank JF, Peter (LinMob), Alex (clover), Brian (33YN2), and PizzaLovingNerd for their contributions to this community update.

N.B. Comments on the blog post need to be in English and follow our Community Rules and Code of Conduct.

Video synopsis of the April community update

TL;DR

  • Housekeeping
    • Go back and read the April fool’s post prior to continuing with the update
    • Quarterly community Q&A April 15th, join in and ask your question
    • PINE64 EU launches on May 10th
    • Product team negotiates resuming Pinebook Pro production
  • QuartzPro64
    • QuartzPro64 is now in production 
    • Dev order system open for those who want to get their hands on the device early
    • We subsidize the QuartzPro64 for devs – selling it for $150
    • Dev boards do not have CE or FCC 
  • PineSound
    • Introducing the PineSound community driven project 
    • PineSound dev board soon to be allocated to devs; will be available broadly at a later point in time
    • PineBuds are the first product based on the dev board; prototype exists and works
    • PineBuds include many common high-end wireless earphone features and allow end-users to flash their own firmware easily
  • PinePhone (Pro)
    • Next production run on the PinePhone (Pro) keyboard on the way
    • Many improvements to keyboard driver, particularly with respect to charging
    • postmarketOS and Mobian decide to use Tow-boot
    • Elementary OS is considering porting to the PinePhone Pro (and Pinebook Pro?)
    • PinePhone Pro Wiki documentation gets a major overhaul thanks to multiple contributors
    • Linuxphoneapps.org quietly launched late March; works well when using Firefox on the PinePhone
    • Many tweaks and improvements are landing PlasmaMobile in the coming weeks and moths
  • PineTime
    • InfiniTime 1.9 launched with many improvements, fixes and a new watchface. 
    • InfiniSim, now a part of the project, and in sync with InfiniTime 
    • InfiniTime merge requests discussed
    • InfiniLink for iOS is no longer maintained – someone willing to step up and maintain the project? 
  • PineDio
    • Improvements to the USB and PinePhone PineDio LoRa case drivers
    • InfiniTime ported to PineDio STACK – a good starting point for further exploration
    • Documentation underway 
  • PinePower
    • PinePower desktop and mobile will be making a return to the store shortly
    • PinePower desktop improvement: USB grounding as requested by many Pinecil users
    • Portable PinePower receives a substantial redesign meant to help with staying put in North American main socket 

Housekeeping

In case you missed it, we ran a little April fool’s spoof at the beginning of the month. I must admit that I am not a fan of the April fool’s tradition and we, as a project, haven’t really dabbled in pranks before. So, then, why did we publish the post and why am I mentioning it now? – because, as with any good joke, the April fools post contained an element of truth to it. More on this later on the update, seriously. 

It is time for the second community quarterly Q&A. If you’re reading this on the day of the community update’s publication, then make sure to stick around and join in later today/ tonight on Youtube, Discord or PeerTube. We’ll be going live at 19:00 GMT/ 12:00 PT. The point of the Q&A is for us to take questions live and answer them then and there. I’ll be taking questions live from the chats – you have a choice of Discord, IRC and Telegram. From previous experience I know that the chat will more than likely turn into a wall of text in a matter of minutes – I therefore ask that you ‘at’ me (@lukasz) before writing your question, otherwise I will more than likely miss it. I will likely bring in developers to answer questions too – make sure to ping people you direct questions to. Once the Q&A is over we’ll head over to one of the casual voice chats and hang out for the rest of the evening. I hope to see you there.

In the event you missed it, we held the first quarterly Q&A we held in January

We have upgraded the main PINE64 and PinePhone Matrix channels. Both of them previously ran version 1 of the Matrix protocol and this caused us all sorts of headaches, including moderators randomly losing their powers and people who left being forced back into the home server. Needless to say, an upgrade had to happen sooner or later. The new rooms now run version 6 of the Matrix protocol which will alleviate all the aforementioned problems. An unfortunate side-effect of the upgrade is that everyone who was part of the original channels will need to manually rejoin. An invite link is present in the original groups. 

As some of you noticed, there was no new PineTalk episode last month. Those involved in the production of the podcast were busy with real-life things and simply didn’t get the chance to record. I’ve spoken to Brian and Justin and they both confirmed that a new episode will be coming later this month. If you haven’t done so yet, make sure to subscribe to PineTalk’s RSS feed

The product team is in advanced talks with a factory regarding resuming production of the Pinebook Pro. As I’ve promised countless times in the past, I’ll keep you updated on the progress regarding restarting the laptop’s production. I’m told the team is etching closer to strike a deal and that the production circumstances will require some alterations to parts of the hardware – keep an eye on our social media and news channels in the coming weeks.

Yes, there will be bundles

Lastly, I am thrilled to let you know that PINE64 EU will be going live on May 10, 2022. By the time you read this, the Polish state should already have listed PINE64 EU as a registered company and all required paperwork should be in place to start sales. The website and logistics are also all ready to go. However, I am still awaiting approval from the debit/credit card payment gate, which takes a long time. I am also waiting for the hardware itself. With less than a month to go, I’ll be posting frequent updates on the store’s Twitter and the newly set-up Telegram news channel. I don’t foresee any issues at this stage, but should any problems arise (I am thinking about customs in particular) I will make sure to communicate it publicly via social media. Telegram and Twitter is where you will find all future communication from PINE64 EU.

QuartzPro64

Last month we outlined our plans for the next generation of Pro-grade PINE64 hardware – the QuartzPro64. In case you missed the original announcement, the QuartzPro64 is a powerful development board featuring an 8 core SoC which comes paired with 16GB of RAM and 64GB of expandable eMMC flash storage as well as an impressive array of IO options. I’m not going to repeat the entire spec list below since it was covered in detail last month – if this is news to you, then I suggest you go back and read the March update and pick up reading this section after.

Unpopulated PCB of the QuartzPro64

Today I am happy to let you know that the QuartzPro64 will soon be available for order via our developer pre-order system. To get your hands on a unit you’ll need to fill in a short questionnaire, similar to the one PinePhone Pro developers submitted at the end of 2021. This will help us determine if you’re the right person to receive the hardware prior to software running on the new platform. Conversely, it will help keep these development boards out of the hands of end-users and application developers. More on this in a bit later. So, then, if you are a developer with an interest in the RK3588 platform, and wish to get an early start on a board that exposes nearly all of the SoC’s available IO, then please make sure to head over to the developer sign-up page to register your interest

Now let me level with you – the BOM of the QuartzPro64 is north of $300. The price is dictated not only by the (rather pricey) SoC, RAM, and eMMC flash but also by the exhaustive list of the exposed IO. As I’ve explained in last month’s post, we didn’t want to compromise on the IO due to the assumed target audience; it is hard to debug and ultimately enable a feature if said feature isn’t physically present on the PCB. But at the same time, we do have a vested interest in a good uptake of the board among the development community. I’d go as far as to say that we hope for the QuartzPro64 to become the go-to board for RK3588 development. A decision has therefore been made to heavily subsidize QuartzPro64 so that the price of the board doesn’t prevent people who wish to be a part of the development process from getting one. After some deliberation, we decided to sell QuartzPro64 for $150 to developers who file an application. Needless to say, we hope to see many applications in the coming days.

RK3588 block diagram

Please note that it will take us time to review all applications and issue approvals. Once the first set of candidates has been determined we’ll then send out purchase coupons. Coupons are valid for a period of two days, then they expire. From previous experiences with the PinePhone Pro and the PineNote, I expect that we’ll send out 2-3 rounds of coupons – so if you do not receive one initially then don’t fret, there is a chance you’ll be included in the second or third round of coupon dispatches. Application rejections will be issued after all applications are reviewed and all QuartzPro64 boards have been allocated. 

Before I wrap this section up, I’d like to make it clear that these boards will not be FCC or CE certified. While, technically speaking, single board computers aren’t required to have such certifications in most places, we always make sure to certify our boards when moving into production. However, QuartzPro64 boards aren’t currently produced in a quantity that would warrant us to start such a certification process. They are meant for the development community and should be viewed as prototype hardware. In some countries you need to register with your local authority to receive uncertified prototypes, elsewhere there is no such registration requirement, and yet in other countries you outright cannot receive uncertified electronics equipment; please make sure to check your local regulatory guidelines prior to submitting your application. 

PineSound

At the end of last year, in the December community update, I teased the launch of (…) a cool small project into our lineup. Let me first clarify what ‘small’ means in this context: a small project is limited in scope and completely community-driven. Examples of such existing PINE64 projects include the Pinecil and PineTime“. As I’ve mentioned in the Housekeeping section, the April fool’s post from earlier this month did in fact include some real information. While we won’t be making plush unicorns with mics sticking out their heads anytime soon, we have been prototyping a set of end-user flashable wireless earbuds. But let me backup a bit. Today we’re introducing the PineSound board; a development platform for earbuds and a digital audio player, utilizing the Bestechnic BES2300 Bluetooth 5.0 audio chip. We will initially distribute the PineSound dev boards to developers whom we know are particularly interested in non-Linux projects such as this. In time, however, the PineSound dev board will be made available to anyone interested in developing on the platform or even using it in some DIY audio project. The board features 2x coaxial & optical input (left) and output (right), a standard 3.5mm headphone jack, 4.4mm and 2.5mm balanced jacks, an SMA connector, USB-C as well as touch and LCD ports. 

The PineSound dev board (v1.0)

Before we get into the specifics of the PineSound project I want to explain its placement in our lineup, and talk a bit about the importance of the development community’s interest in the hardware. The approach we’ll be taking is, in a sense, very similar to how we handled the PineTime and the Pinecil. This means that the success will largely depend on whether a community grows around the platform. As we did with PineTime, we will allow the development community to help set the course of the PineSound project. All important decisions, such as moving from development to production, the production itself, opening sales, etc, will be coordinated and discussed with the community. We recognize that working closely with developers and the community is critical in projects such as this – while the PineTime and Pinecil are now hallmarks of PINE64, we need to acknowledge that the PineCube has been largely a failure. The general lack of interest in the PineCube can, at least in some part, be ascribed to a failure on our part to facilitate community building around the device. We’ve learned from this experience and have done everything on our end to assure that PineSound as a whole is a success from the get-go. 

See, they’re real. Seriously.

The first device to be introduced based on the PineSound dev board will be the PineBuds wireless Bluetooth earbuds. What I wrote in the April fool’s post about the buds is accurate – they offer features found on high-end in-ear headphones, such as ambient and environment noise cancellation, and long battery life. They have 6 microphones total, 3 on each bud, as well as touch-based input situated on the external side of each bud. We designed the cradle which houses the earphones so that custom user-created firmware can be flashed. The cradle has built-in UART used for firmware flashing, which is automatically exposed when it is connected via USB to a computer. There will be a wide variety of things developers and (eventually) end-users will be able to do with the earbuds – flash custom sound signatures, determine touch controls, adjust resonance to fit the user’s ear canal resonance and even turn the PineBuds into hearing aids. The last application is particularly interesting – the BES2300 is one of just a handful of chips considered for use in ‘over the counter hearing aids’ by various regulatory bodies. 

A peak inside – picture of an early engineering prototype

Ben (Ralim), probably best known as the creator of IronOS, has had his hands on the prototype for some time. Here is what he had to say when I spoke to him earlier this week: 

“I think of the buds as (…) [a] good working device, that the community can hack on and tweak, [while of] the Dev board as the experimentation setup for exploring this chip and finding out just how powerful it is. [T]here are some binary blobs in the firmware around Bluetooth [and] some for voice assistants (but I don’t know if we would ship them). But it was in a compilable and runnable state with fairly complete hardware drivers. I see it a bit like the bl602, where we have a working SDK with some blobs, but the hardware is very good for hacking on. The main MCU so far is quite powerful and battery efficient. Flashing is easy over a UART serial port [too].” 

It is clear that the hardware has a lot of potential from both developers’ and end-users ‘ perspectives, and I hope that the project garners some interest from the community as a whole. More information about the PineSound will follow next month, so keep a lookout for news.

PinePhone (Pro) [by Lukasz, Peter & Brian]

A new production run of the PinePhone keyboard case is now underway and should be available soon. The keyboard case has proven to be a very popular accessory, and therefore the initial production run sold out quicker than other optional back cases currently offered for the PinePhone and the PinePhone Pro. We expect that the new batch will last us 2-3 months, so if you’ve been eagerly waiting to get your hands on a unit then there should be no problem in obtaining one. On the subject of the keyboard case, the IP5XXX_POWER (keyboard power) driver by the developer Samuel Holland has now been upstreamed. A handful of fixes are also coming (or have already arrived, depending on distribution) to improve battery operation and charging of the PinePhone (Pro) when paired with the keyboard case. When charging, the new algorithm will strive to charge the phone’s internal battery as fast as possible first, and only then start charging the keyboard case. During operation, the keyboard case will only start charging the phone’s internal battery when it is nearly depleted. It will try to maintain a 20% charge of the phone’s internal battery. The new driver will also provide a set of triggers to notify the user via the phone’s LEDs about the status of both batteries. I suggest you read the developer Megi’s blog post to learn all the details. 

Keyboard case production – a short video from the factory floor

PinePhone and PinePhone Pro with keyboard case charging – picture by Megi

In other news, postmarketOS and Mobian have made the decision to use Tow-boot as opposed to u-boot with their distributions. In the case of the PinePhone Pro, this means that end-users will be required to flash Tow-boot on their devices prior to using these OSes. I wrote at length about Tow-boot in last month’s update if you wish to learn more about it and its application on both the PinePhone and the PinePhone Pro. The Mobian team writes: “by letting users install the bootloader themselves, either on the SPI flash (…) or the eMMC’s boot partitions (…), we can stop embedding our own copy of the bootloader. (…) Both new and existing users should install Tow-Boot or a similar system to provide updates to their boot firmware. [Using Tow-boot] will be required on new installs using images generated after 2022-04-02.” 

elementary OS on the PinePhone Pro? yes please!

On the subject of mobile Linux OSes, many of you will be happy to learn that elementaryOS are exploring the possibility of bringing their OS to the Arm platform and, in the future, also the small screen of Linux smartphones. The development is currently targeting the PinePhone Pro – a sample unit was delivered to Danielle from elementaryOS earlier this month. It is worth noting that the team already has some experience with the RK3399 SoC and our platform as they have – in the past – attempted to bring elementaryOS to the Pinebook Pro. As a side-note, elementaryOS on the Pinebook Pro is something I’d still very much like to see – fingers crossed. I spoke to Danielle this week and she had this to say: “Mobile Linux is coming and the time is now to be planning and developing. PinePhone Pro is a really compelling developer platform and I’m excited to start working with a whole new world of open source apps and operating system.” I wish Danielle and elementaryOS contributors the best of luck with this endeavor; we’ll be keeping our fingers crossed for yet another mobile Linux OS option to see the light of day. 

In other news, the documentation of the PinePhone Pro on the PINE64 Wiki was growing steadily in the last couple of days thanks to the relentless work of multiple community members. In summary, the “State of the Software” section on top of the PinePhone Pro article now received a graphical overview table of the current software stability and functionality, which makes it easier for users to get an overview of the overall software state without having to collect the information from multiple locations such as bug trackers. The overview also contains notes regarding bugs or details, which might impact the functionality of a specific feature. Of course, this enumeration does not make a claim to be complete in any way but should ease the search for related information considerably. The table can be found under https://wiki.pine64.org/wiki/PinePhone_Pro#State_of_the_software.

A functionality matrix has been added to the PinePhone Pro Wiki section

The software section of the PinePhone Pro article, which was extended gradually, was rewritten as well to bring a more coherent information section with all relevant information. The section should now be considerably easier to read, especially in the parts, which were causing confusion in the previous instructions. Aside from a large number of improvements, the section now also received a dedicated troubleshooting subsection and numerous new information. The section can be found under https://wiki.pine64.org/wiki/PinePhone_Pro#Software. As it is often asked where bugs can be reported and how projects can be supported, new articles regarding where to report bugs and how to contribute to projects were started as well, which will be gradually improved and extended over time. In this context it can be noted that all community projects are happy about any form of contribution. Knowledge of coding is not required, instead there are various ways to contribute to projects, for example with designs, ideas, translations, documentation, through hardware or with creative work, or by simply being a positive member of the community. On this note, I want to thank everyone for their unremitting help. Without your contributions, the community would simply not be what it is today.

There is one more noteworthy piece of information concerning documentation of mobile Linux software: LinuxPhoneApps.org finally quietly launched at the end of March. It lists all the apps that were (and still are) listed on LINMOBapps. The list is presented in a way that is more friendly to PinePhone’s Firefox browser, preventing it from asking whether it should kill the script that slows things down. The list now has more apps, with more being added slowly but steadily. Note that not all apps are packaged for your distribution nor are they all to be considered feature-complete. If you want to follow, join or help out the further development of the site, check out the LinuxPhoneApps FAQ.

On a final note, Plasma Mobile will be seeing several bug fixes, lots of optimizations, and a few new features in the coming releases. The mobile data toggle has been fixed so that the setting is remembered across reboots, a virtual keyboard toggle has been added to the quicksettings panel, the ability to reorder the quicksettings menu has been added, there have been various animation fixes, shrink and grow animations have been added to the shell buttons and homescreen, work has been done to start implementation of custom homescreens (though this is not yet finished), the media widget in the quicksettings panel now supports multiple video/audio sources by swiping left or right, the lockscreen has received a new notification widget, the APN settings menu received several UI fixes, the panel’s opacity logic has been fixed, and spacebar has received several fixes to its UI alongside some bug fixes. Most notably work is planned for a lockscreen shell overlay that would handle incoming calls and alarms, and give users a nice fullscreen overlay to interact with, although this is still in the planning stages.

PineTime [by JF]

The InfiniTime team released a new version of the open-source firmware for the PineTime at the beginning of April. The first new feature you’ll notice in InfiniTime 1.9 “Limeberry” is the new Terminal watchface! This original watchface displays the date, time, battery level, steps, heart rate, and BLE status as if they were printed on a console terminal. It’ll more than likely please the geeks among us.

The new terminal watchface looks great

A new feature allowing to disable the BLE connectivity was also added. This feature was requested by many users as it saves a bit of battery and increases the privacy of the PineTime. When BLE is enabled, the watch continuously broadcasts “advertising” messages allowing devices to detect and connect to it. It also allows some kind of tracking; when BLE is disabled, those messages are not sent and the watch is then “invisible” to anyone trying to detect it.

Those of you who use the heart rate sensor will be happy to know that we improved the accuracy of measurements of the heart rate sensor. Thanks to the wasp-os team for their help with this! The heart rate monitor now displays more sensible and reliable values – it has been tested and approved by Nico!

The heart rate monitor is now much more accurate

InfiniSim, the InfiniTime simulator, is now also supported by the team and integrated into the CI. Each time a new PR is created and merged, the CI checks that the change builds in InfiniTime and also in the simulator. This will help maintain both projects in sync and ensure we don’t break anything when changing something in either InfiniTime or InfiniSim. The new InfiniTime release also brings many improvements to notifications (call notifications won’t vibrate forever when receiving a call) and to the Alarm app. The 12-hour time format is now better supported. You can read the whole release note and download the firmware on the project page.

InfiniTime receives a lot of contributions from many users and developers, and I’m really thankful for that! Unfortunately, for various reasons we cannot merge and integrate each and every one of these features as soon as they are published by their author. One of those reasons is memory usage. As you may know, the PineTime is based on a small-ish MCU with 64KB of RAM memory and 512KB of flash memory. From my experience, this is a very comfortable amount of memory when compared to many other microcontrollers. But still, we have to be very cautious to not hit the memory limit if we want to be able to add new features and improvements in the future. That said, here’s a highlight of some of those cool features I hope we’ll be able to merge at some point in time. A feature that is often requested is the support for other languages and alphabets. New languages require a lot of memory for storing new fonts, which we cannot afford right now. But InfiniTime is completely ready to handle these, and yehoshuapw proves it by maintaining a fork of InfiniTime that integrates Hebrew. A new version of this fork was released a very short time after the release of InfiniTime 1.9. Kudos to the maintainer!

Watchfaces also need quite a lot of memory. The Infineat watchface is one of them – it is a very neat and well-designed watchface that uses the Pine64 logo to display the battery level!

Infineat looks really neat!

I also like this QR Code application, which displays 4 QR codes specified by the user via a BLE API. Those QR codes can be links to web pages, online accounts, and even vaccination certificates for COVID-19! Very cool.

An example QR code displayed on the PineTime

Last piece of information for this month – I’ve learned that InfiniLink, the companion app for iOS is not maintained anymore. Here’s the message its author, xan-m, wrote in the last commit ‘Added localizations and goodbye message’:

“I’m sorry to say that this will be the last update to InfiniLink. I started a new job a couple of months ago and no longer have the spare time to continue development of this project. If anyone is interested in taking over, please let me know and I can transfer everything over. Thank you for all of your support and suggestions along the way!”

I would like to thank xan-m for their work on InfiniLink. Xan-m created the whole app from scratch and quickly proved that a companion app for iOS is definitely needed in the community and the PineTime ecosystem. Let’s wish xan-m good luck in their new job, and I hope we’ll meet again soon! So, who will take over the project to maintain the presence of our beloved open smart watch in the iOS world?

PineDio [by JF]

Lup and I are still actively working on the PineDio STACK with a double goal: check that the hardware is working as expected and to document our development environments. Lup is really good at documenting his experiments. He’s currently writing an extensive article about running the Apache NuttX RTOS on the PineDio STACK which I encourage you to read.

On my end, I’m working on porting InfiniTime to the STACK. This is quite easy as the display and touch panel are exactly the same as the one on the PineTime. I think InfiniTime will be a nice starting point to experiment with the STACK hardware: the RISC-V MCU (BL604), the LoRa radio, the GPS and secure module on the add-on board, etc. As you can see on the video below, the display driver is now functional and even works a bit faster than on the PineTime. It can go even faster when more memory is dedicated to the display driver.

InfiniTime now runs on the PineDio STACK – here’s a quick comparison to the PineTime

I’ve also upgraded my driver for the PineDio LoRa USB adapter and LoRa PinePhone back case. Some changes were needed to support kernels > 5.10. Note that the driver for the CH341 chip (USB to SPI converter) also needs an update to support kernel 5.16. I forked the driver to apply the changes until they eventually become approved in the upstream repo.

The PineDio USB dongle

PinePower

Both the desktop and portable PinePower PSUs will be making a return to the Pine Store next month. I am glad to report that since the original units were in stock some improvements have been made to both designs. The desktop unit, often ordered alongside the Pinecil, has now grounding on the USB ports. This is a feature that many users have asked for. Otherwise the desktop power supply looks and functions just as the original iteration. The portable 65W PinePower has seen a more substantial physical redesign – the PSU itself has been shrunk slightly, making it overall more compact, and the overall physical dimensions have been altered along with internal weight distribution. The new design solves a problem that people in the US, using those tiny rectangular prongs for the mains socket; the original portable PinePower would sometimes not stay in place due to its weight distribution when plugged into a wall socket, while the new design does. I’m sure that this is a welcome redesign. 

The USB ports on the desktop PinePower are now grounded

That’s all for this month, I’ll catch you all in May.

30 responses to “April update: no more unicorns”

Leave a Reply to Billbroswaggins Cancel reply

Your email address will not be published.

I accept the Privacy Policy

    Hey Lucas,

    great update as always! I’m glad to hear, that the earbud was no April’s fool and it will happen sooner or later! Great news indeed!

    However I also have a request to write about: as I’m reading the news about the RK3588 platform and I can’t help but think, that in two years there will be an announcement about a PinePhone Quartz in which case I will be thinking “Darn! That is some great hardware! But if I order one, what should I do with my original PP? :O” So what I’m asking for is to consider either some upgrade path to the PP already during the planning phase or—and it may be the better course—work out some refund or return policy like “send in your old phone and by a new one for 10USD less”. I don’t really care about the financial aspect of the return, I just want the peace of mind, that my working device does not go to waste. Maybe it can be sent out to people in need, or schools as DIY kit. I really have no idea what are the technical or administrative difficulties of solving such request but I think in the current situation of our world, it would be a most welcome option on the long run.

    Keep up the good work!
    Cheers
    Gergely

    Schtromar says:

    What i’d like to see is a breakout board/case which would allow you to use the motherboard as a regular SBC. Even if it’s not longer useful as a phone it should be more than good enough for a small home server/media pc/smart refrigarator….

    Schtromar says:

    Were there any imporovements to the international adapters on the portable PinePower? I currently use a thermoplastic polymer adhesive (hot glue) to hold a cheap eu to us adapter on mine. I would love a more integrated solution though.

    intrepid says:

    There were plenty of users on the forum reporting problems with the keyboard accessory. I expect software problems to be solved but some problems seem to be related to the pogo pins.

    How will that problems being solved?

    I consider buying the keyboard but want to be sure that it works on my PP as well as a later revision of the PPP.

    A PinePhone user says:

    Hi intrepid!

    Sorry for my bad english.
    I had also problem with keyboard addon, I reflashed OS twice times (PMOS and Mobian), then I search and found fix in wiki:
    https://freiburg.social/system/media_attachments/files/107/684/243/421/870/279/original/a5e9c68ff3510ec8.jpeg
    The little shim lift up pogo connectors, and keyboard work well.
    Somebody made a video about procedure:
    https://www.youtube.com/watch?v=4ixPjz6SPIA

    I hope, problem will fix in factory in next series, but I want also see an Official info about this.

    Tyler Irwin says:

    Not mentioned in this months update, but are you planning on making the rainbow pine logo available with the pinebuds? I think it looks great on the black case.
    I will be following the pinesound’s development. I’m going one of the more savvy persons in there community will be putting out a guide or development project for a pine pod. Very interested in an open source version to take some of the slack off my phone for audio duties.

    I’m also hoping they announce a PinePod. And luckily for them, there is already an excellent open source audio player firmware: Rockbox!

    Some Guy says:

    I like the idea of possibly being able to be certain about the control of the encryption keys used between a phone and a wireless headset, but I guess that’s only so you can communicate securely without looking like one of those “weirdos” who still uses wired headphones in 2022.

    And I have to point something out. While displaying QR codes of any sort on the pine time is useful and worth noting,
    Vaccination certificates are NOT cool.
    Listing them among other celebrated things the watch could display implies that it’s okay to mandate them.
    It’s not.
    Drugs are a consumer product like any other, people are normally free not to use consumer products or take different approaches with solving a problem and what’s good for one person can’t be presumed to be good for another. Especially when not using a product doesn’t hurt other people, which despite everything, is in fact the case here.

    I know almost no one thinks this way but me, I know everyone thinks the dust has settled and the world has moved on, and this comment will probably be deleted because it’s too “wrong”, or might start an argument that I don’t intend to participate in, but it’s still a problem and someone has to say it.

    stan423321 says:

    Well, if you don’t want to participate in the argument, it’s equally opaque to assert it’s a problem or it’s not a problem, you know…

    I don’t know where you are in the world and how exactly the things are there, so a problem may exist. I don’t find your explanation convincing, but that doesn’t mean I have a problem with you going with it. But if you are not fine with others’ actions in relation to that – here, article mentioning a thing you dislike – then an argument is the only fully honest way to affect this. If you won’t consider the other viewpoint, why should others consider yours?

    This may seem like a tangent, but guess what, this type of thing happens in software and hardware development too. Would I make the Pine64 products differently than Pine64 makes them? Yes, absolutely. Am I going to complain about it and then state that I don’t really want an argument? No, that would be ridiculous…

    > Drugs are a consumer product like any other, people are normally free not to use consumer products {…}

    …until the point where your freedom to choose to use or not a consumer product has an impact on other people around you (and potentially their own freedoms) like with lots of safety products.

    > Especially when not using a product doesn’t hurt other people, which despite everything, is in fact the case here.

    That entire class of products (vaccines that specifically target transmissible diseases) – even if it cannot magically guarantee 0% chances of catching a disease (0% nor 100% guarantees simply don’t exist in medicine and biology) – very certainly can contribute to the reduction of the circulation of the targeted disease in the general population. And that disease very often can include lethal or long-term very debilitating effect on some subset of the population.

    You, having been vaccinated against polio back when you were a kid, not only reduce your individual risk of catching the disease, but also reduce the risk of the virus circulating and causing paralysis in other people around you.

    Me deciding to get vaccinated against influenza not only reduces my personal risk of catching flu, but also reduces the risk that I accidentally transmit it to someone fragile and kill them.

    Countries mandating vaccines against yellow fever virus before you’re allowed to travel there not only reduce the risk that you catch the virus if you’re bitten by a mosquito while traveling the forest, but also reduce the risk that, once you’re back in the city, another mosquito loads up on yellow fever virus and then spreads it further in the city.

    And similarly, in addition to other spreading-prevention tools – like masking, air quality, etc. – vaccines against SARS-CoV-2 will not only reduce your own personal chances of you catching covid-19, of having bad outcomes (death, long-covid) if you got it, etc. it will also reduce the risk that you spread it around you.

    Your freedom to choose not to use these specific class of drugs comes at conflict with my personal freedom to not have virus blown at my face, specially in settings where other tools aren’t available (it’s hard to mask while eating).

    It’s basically like drunk driving: your personal freedom to choose to put whatever you want into your own body while behind a wheel, comes into conflict with the freedom of not dying in a car crash for everybody else sharing the same road as you.

    So yes, some countries have decided to put some restrictions to access some public spaces where your freedom might cause death and long-lasting debilitating outcomes in other people around you there.

    You might argue about peculiar forms that these restrictions and mandate have taken.
    You might argue that other individual contribution should be more emphasized (masking).
    You might argue that the state should put effort on the infrastructures (improving air quality in closed space can potentially have a huge impact on countless respiratory viruses).

    But you cannot argue that it’s entirely a personnal choice with zero impact on anybody around.

    Disclaimer: I work in research – more specifically in virus sequencing – and I am strongly biased toward any measure that would help reduce the virus circulation so that I could finally afford some rest after two years of extreme amount of work.

    David Bergman says:

    Your argument is absurd. You’re essentially arguing that the _chance_ of my spreading an infection is justification to _guarantee_ that you violate my bodily autonomy. You say that my right to refuse inoculation ends at your right to not have viruses blown in your face, but this is tantamount to saying that I must prioritize your health over mine. This applies _a fortiori_ given that one is only a chance and the other is a guarantee.

    According to your own logic, such vaccine mandates have an impact on others around you, and therefore you have no right to mandate them. Not to mention that your statement about lethal or long-term very debilitating effects caused by disease can also certainly be applied to vaccines as well, though it may differ by degree. Let’s modify a quote from your post to demonstrate that the exact logic you use to deconstruct vaccine skepticism attacks your own argument: “Your freedom to mandate the use of these specific class of drugs comes at conflict with my personal freedom to not have vaccines injected into my body.” Do you accept the implications of your own argument? Presumably not, given your selective application.

    I’m REALLY hoping that the combination of the PinePhone(Pro)+Pinebuds+PineAudio are leading in the direction of a Pine smartspeaker. If so, I would hope it would be with the more innovative and private Genie/Almond from Stanford University, instead of something privacy-washing like Mycroft (see their “privacy” policy and corporate governance for why I say that, if you’re not familiar).

    A Pine+Genie smart speaker that interfaced well with Home Assistant would be amazing, and take privacy deep into the heart of the most privacy destroying domain… digital assistants. Genie already has a Home Assitant extension.

    Imagine:
    Your Pinespeaker announces “There’s an incoming call from Mom/spouse/kid. Would you like to pick up?”. You reply “Hey Genie, pick up, thanks” and talk. You don’t need to dig around for your phone, as it’s hands free through the speaker. When you’re done you hang up by pushing a button on the PineTime on your wrist. The Pinespeaker could automatically connect to the PinePhone for the contact info and the phone network and then act as a hands free speaker/mic. The call is completely invisible to Amazon, Google and Apple. It could even have come in through Matrix or XMPP.

    I would buy one of those (well before the software was end user ready) for every major room in my home.

    In a heartbeat.

    Please check format and adapt the design so you can use custom molded shapes with the buds. Main issue is the charging location. Please check:
    https://youtu.be/mH9da4rpStg

    I have them and technically they are not good but because ofbthe fit I will accept that until something with similar fit comes along….

    An audio player, like shanling Q1, nanopod, based on for example pinedio stack (touch screen) and some decent DAC, 3.5jack, and uSD would be fun. May be possible to port Rockbox? Probably just to much for the BL604 platform but a minimise DIY tinker platform sounds fun.

    Billbroswaggins says:

    Hopefully you guys do over the ears. My right ear produces something that kills earbuds. The Samsung Pro lasted 3 days. The record holder is cheap Skullcandys that made it a month!

    I know the focus on the Quartz Pro developer board is on offering as much I/O as possible to help with development. Is there an intention to also make a QuartzPro64 board in your “A” form factor, like the RockPro64? It’s nice having consistent form factors available.

    If not, would it not make more sense to use the Mini-ITX form factor (170mm x 170mm)? If you’re making an SBC of this size, why not design it around an existing industry standard? It would open up a lot more off-the-shelf options for enclosures.

    Regardless, I’m looking forward to this powerhouse to get added to the pine64 lineup.

    thexder1 says:

    The pineSound and pine buds are particularly interesting to me, I have longed for the ability to create a programmable sound interface that is not as much of a black box as most off the shelf solutions and would really be interested in potentially using something like that to create a speaker setup that moves the analog interfaces as close to the speaker as possible, like powered speakers, with a digital interface, potentially wireless connection from the computer. I am not sure exactly how this would work, but I would assume some software setup to allow multiple boards like this to act as individual channels of a single audio interface.

    Will the new batch of keyboards have defective keys like the previous one or was that fixed? I want to buy one and I can live with the alpha software, but only if the hardware works properly.

    sad-ppkb-user says:

    I would be surprised if they fixed the keys and on top of that, the issue with the connections. Mostly because they’ve known the issue exists for close to 4 months at this point but have never actually stated that a good portion of their keyboards has hardware faults. Super scummy business practice and really disappointing for a company that tries to be transparent. They should pull them from production, offer refunds, or at the very least, state of the ppkb page that you might have to fix it yourself. It’s made me swear off of PINE64 devices until they at the very least admit that it’s a problem.

    That’s sad. There is no mention of any of this on the store page like you said. Did you ever manage to fix it?

    I’m definitely interested in the quartz pro – I like the lower cost of other boards but it looks like this will be very capable, and I try to get one of everything, so I’m looking forward to it being more mature. I’m no coder but an experienced system engineer so I can probably help bug test and maybe fix various configs once I can get a proper distro on it.

    Stoked about PineSound. I was a little disappointed that some of the add-on sound devices weren’t available by the time I checked, but this sounds much more promising. If both the earbuds and some kind of DAC peripheral came out, I’d love to set up a semi-DIY audiophile device on the hardware (I think I have an audio add-on I can stick to an A+ board but have been using mine for DNS and general local Linux stuff).

    Also really looking forward to PineDio. could be a big win for people looking to set up embedded low-power devices for monitoring things like soil conditions, environmental info, and other monitoring systems. I’m hoping to set something up eventually that will work on a modest farm or hiking to use for discreet communications over moderate distances, not reliant on power-hungry radio devices, cell, etc.

    I need to try some of the boot optinos as well as to update InfiniTime. Less boot fiddling is great and new features like that cool terminal mode for the PineTime are awesome too.

    Where is the May update, which was due out on 15 May.
    I understand the delays due to opening the new store, but it is now 30 May, with nary a peep; nary a “RSN” (“Real Soon Now”).

Subscribe to the PINE64 blog