May Update: Worth The Wait

Lukasz Erecinski May 31. 2022 23

Hello everyone! This month we’re announcing production of the Pinebook Pro resuming and introduction of Quartz64 model-B. I had an opportunity to meet with TL earlier this month, and got some ear-on time with the Pinebuds, so I dedicated a section to my early impressions from the time spent with the prototype. This update also brings news of SOQuartz Blade hostboard production, camera enablement on the PinePhone Pro and a guest write-up by dsimic addressing issues some users have been experiencing with their PinePhone (Pro) keyboards. There is truly a lot to get to this month, so let’s get into 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, Dylan, dsimic, 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


  • Housekeeping
    • Update moved to 28th of the month
    • PINE64 in-person meeting
    • Pinebook donation to school with kids in need of laptops
    • We’re going though QuartzPro64 dev pre-orders
    • PINE64 EU store; addressing delay 
  • Quartz64 & SOQuartz
    • Model-B released – available for $60
    • SOQuartz Blade hostboard enters production 
  • Pinebook Pro
    • Pinebook Pro is making a return after months of absence
    • Expected in Pine Store late June early July
    • Price stays the same as do most specs 
    • Highlight of selected new released for the Pinebook Pro
  • PinePhone (Pro)
    • PinePhone Pro restock expected late June early July
    • PinePhone Pro camera enablement underway; look at first pictures
    • Mobile Linux has gained support for Bluetooth HFP
    • User-made script to easily install Waydroid
  • PinePhone (Pro) keyboard
    • Dsimic writes at length about PP KB issues identified by community and developers 
  • PineSound
    • First PineSound dev boards allocated to devs
    • PineBuds prototype early impressions 
  • PineTime
    • InfiniTime development progress 
    • New InfiniTime fork exposes high frequency accelerometer data; fork receives a dedicated companion app


Let me start by addressing the delay in the publication of this month’s community update. I’ve been really busy with the EU store this past month (more on this later) and ill for the better part of last week, which left me with very little spare time to do the write-up. As a result, for the first time in years, this update is published at the end of the month rather than on the 15th. I have given some thought to the situation and arrived at the conclusion that we’ll make the 28th of the month the new update publication date. So be on the lookout for the next update on June 28th. Consider this publication tentative – in two-three months I will reevaluate if changing the publication date to the end of the month was a good decision.  

Earlier this month we held our first in-person meeting since FOSDEM 2020. It was a small get-together, primarily aimed at discussing the PINE64 progress and PINE64 EU’s launch. It was a pleasure to see the people who make the cogs turn in person again. Thank you guys for paying me a visit!  

From the left: Lukasz, Gamiee, Lynx, TL and Ayufan

As some of you may recall, last year we made a pledge to donate Pinebooks to a charitable cause. It may come as a surprise but, as it turns out, donating hardware is actually not simple. One would think that it is a case of establishing a suitable cause and shipping the hardware, but nothing could be further from the truth. I’ll spare you the detail of the hurdles we had to overcome, but suffice to say finding a suitable recipient of the Pinebooks proved difficult. It is therefore with great pleasure that I bring you news that the first batch of Pinebooks have found a new home at a school where kids were in need of a laptop. I would like to take this opportunity to sincerely thank One Laptop Per Child (OLPC) for helping us in finding the right recipients of the laptops. May the Pinebooks serve their new owners well.  

We are looking forward to dispatching more Pinebooks to schools and charities this year

We have started going through developer pre-orders for the QuartzPro64. Allocation of the boards was initially delayed (in part due to my absence this past month), but with units now rolling off the factory floor we’ll move swiftly to issue first coupons. We have decided to send the boards out in smaller batches rather than all at one time – this will allow us to monitor progress and developer engagement. So if you filed an application to pick up a QuartzPro64 at a reduced developer price of $150, and won’t hear from us in the coming weeks then don’t worry, we’ll send out units for the months to come. At the same time, I’d like to remind you that the developer pre-orders are still open and that there is still time to file a coupon request. To learn more about QuartzPro64, I invite you to read the March community update where I detailed the board’s specs and explain our decision to subsidize the initial production run. 

Final QuartzPro64 PCBA

Lastly, I wish to address the PINE64 EU store’s launch delay. For the past month I’ve been cutting through layers upon layers of red tape – as it turns out, it is one thing to ship to the EU and a whole different thing to have permanent representation here. Since the situation is ongoing I will refrain from discussing the specifics at this time – what I will say is that I have now gotten a lawyer to help the process along. I hope that all outstanding legal paperwork can be sorted out in the next 2-3 weeks. As always, I’ll keep you posted on the PINE64 EU’s Twitter and Mastodon.

Quartz64 & SOQuartz

Earlier this month we released the Quartz64 model-B that sports the same RK3566 SOC found on its larger sibling as well as the SOQuartz compute module. Model-B comes in a familiar form factor and is available in a 4GB LPDDR4 RAM configuration for $60. While the model-A is geared more towards the development community, the model-B is meant as an easy-to-integrate option for industry partners and regular end-users. It does offer fewer IO options than the model-A but still manages to deliver a solid connectivity selection including 2x USB, 1x USB 3.0, and Gigabit Ethernet with PoE. You also get AC WiFi, Bluetooth 5.0, MIPI CSI, and DSI as well as a mini PCIe slot.

Quartz64 model-B top and bottom

I had the opportunity to try out the new board earlier this month, and I was very happy with both how well it is supported and with how well it performs. I tried Manjaro with Plasma and, to my surprise, the board performed really well running at my monitor’s native 4K resolution. Running the desktop under Wayland I would describe the experience as perfectly smooth; it is clear that Plasma Desktop benefits from Panfrost (FOSS GPU driver) acceleration at 4K resolution. I will go as far as to say that the model-B would be a great candidate for a 4K kiosk running a dedicated application or a browser-based app. As someone who enjoys playing retro games, I also think it would make for a great small emulation box. I hope we’ll get a LAKKA image for it eventually. 

I’ve spoken briefly with pgwipeout, one of the contributors who laid the software foundations for the Quartz64 device lineup, and asked about software progress. He told me that model-A and B, as well as the SOQuartz, have found their way into kernel 5.19. He added that the VOP2 driver was accepted into kernel 5.19 for HDMI output, but the DTS changes will first find their way into kernel 5.20. Now that we’ve got a solid software foundation in place, we need the board to offer a wide diversity of OS choices. Manjaro has done a great job, and their OS images are really well maintained, but I am well aware that many need a Debian-based or specialized (e.g. LAKKA) operating system to meet their requirements. So, If you are associated with a project who would like to support the Quartz64 devices, make sure to reach out to me or one of the admins.   

SOQuartz and SSD in the Blade hostboard

The SOQuartz compute module, which is based on the same hardware configuration as the model-A and model-B, has already been released for some time, and the first pre-release OS images for the module are now available. With the software taking shape fast, the SOQuartz host boards have entered production and should be available in the Pine store soon. Aside from the model-A type host board – which is basically an IO breakout board – we will soon also be offering the Blade hostboard. The Blade has been designed for clustering, and fits inside a standard 1U server rack: 12 or more Blade hostboards can fit into a single rack. I wrote at length about the Blade in November last year, but here is a short recap of the IO the Blade exposes: Gigabit Ethernet, a micro SD card slot, 1x USB 2.0 header, digital video output, 40x GPIO header, UART output, power barrel jack port and an M.2 PCIe slot for storage. The Blade has been designed to have IO located at the short leading edges, allowing for easy access and cable management as well as tight stacking inside a server rack. More information about the Blade and SOQuartz model-A host board will be coming soon. 

Pinebook Pro

It has been a year since we were able to ship the Pinebook Pro, and ever since the last batch sold out we have been continually asked to bring it back. Today I am pleased to let you know that the Pinebook Pro has now re-entered production and will be available for purchase at some point in late June or early July. You will surely also be happy to learn that we are re-introducing the laptop at an unchanged price of $219 – the price it sold at prior to all the disasters which at first made production difficult and eventually impossible. The hardware remains largely unchanged from the 2021 version of the laptop. This includes the PCBs, keyboards, metal and plastic parts, etc. For those who haven’t followed the Pinebook Pro production hurdles over the past months: the main reason for production stalling was our inability to acquire reasonably priced and vendor-insured high-grade IPS panels. We did, however, already have much of the remaining parts lined up and ready to go. The new panel ought to deliver identical performance to those used previously. The only other change concerns the battery – the new battery is marginally smaller at 9600mAh, which is 400mAh less than in previous iterations.

Kali Linux on Pinebook Pro – image via Kali Linux

I feel like it is a great time to pick up a Pinebook Pro – those of you looking to get a unit should know that the laptop is now a very mature platform, with many available OS options and a thriving community. It is also a platform that benefits from developments on the PinePhone Pro. I’ve seen an array of updates to Pinebook Pro OS images over the time that the laptop was unavailable – this includes the default Manjaro with Plasma desktop, which I’ve been using for the past 3 years on my laptop. The excellent postmarketOS with GNOME build has just received an update this past week; if you are partial to the GNOME desktop and enjoy Alpine Linux then you absolutely should give it a go. One other OS I’d like to mention is Kali Linux, since a popular application for the Pinebook Pro is using it as a dedicated pen-testing device. Kali Linux has recently made it possible to use the Kali kernel and u-boot instead of compiling your own, thereby greatly simplifying the installation process. Those of you seeking Debian and Fedora installations will be happy that these are also available. All OSes and documentation for the Pinebook Pro can be found on the PINE64 Wiki – information relevant to the new panel and battery will be uploaded to Pinebook Pro’s Wiki next month. 

Keep a lookout for more information on the Pinebook Pro in the coming weeks. 

PinePhone (Pro) [by Lukasz, Dylan and Brian]

Before we get into the software news, I want to quickly touch upon PinePhone Pro’s availability. The PinePhone Pro is currently out of stock, but it won’t be long before more units arrive. The next batch is expected to land in the Pine Store sometime in late June or early July and should last for months to come. I will notify the community as soon as more units become available, so keep an eye on our social media and news channels.  

Let’s dive into software. Earlier this month a breakthrough was achieved in getting the cameras to work on the PinePhone Pro. Megi brought up support for the rear (main) camera, forward-ported the BSP driver for the front-facing selfie camera, and integrated it into the kernel tree along with device tree changes. For those of you interested in the details, details of the process can be found in his recent blog post which I obviously encourage you to read. As he writes, this is just the beginning of the journey, and developers will now need to integrate userspace support of the cameras in applications such as Megapixels. For the time being, to snap a photo you’ll need to open CLI and jump through numerous hoops. While it may take some time before capturing photos on the Pro will become convenient, the recent development brings us one step closer to reaching parity with the original PinePhone’s functionality. I can only hope that implementing Megi’s work into userspace applications will proceed at a good pace and won’t get bogged down with any major obstacles. I am including pictures from both the front and rear camera below; please note that both images are completely raw without any post-processing applied. I’m not an expert in mobile photography, but those pictures look pretty darn good to me. 

Picture taken using PinePhone Pro’s selfie (front) camera – image from Megi

Picture taken using PinePhone Pro’s main (rear) camera – image from Megi


Mobile Linux has gained support for Bluetooth HFP (Hands-Free Profile) – a Bluetooth specification that allows you to make hands-free phone calls. This specification has already existed for a decade and is supported by all kinds of phones. I submitted a series of patches to PulseAudio to support Bluetooth HFP in ModemManager, which will allow you to manage calls through

Bluetooth HFP devices. This includes accepting, rejecting, hanging up calls. Some devices can also display the current network operator, service status, phone battery level, etc. This is also implemented by this patch series. postmarketOS users will soon benefit from my patches. A detailed explanation can be found on my blog.

Bluetooth HFP demo – via Dylan


Lastly, but certainly useful to many of you who may not know or have struggled to setup Waydroid, a community member – Cara (FOSSsingularity) – has recently created an easy to use script for configuring and managing Waydroid. This script includes the ability to set up a custom rom to run in the container, and the ability to enable or disable gapps support. In a similar vein, the same contributor has also created a Maui Shell installer script for Manjaro, for those of you who wish to test out the Alpha of the new shell without having to manually configure it to launch. Awesome stuff!

PinePhone (Pro) Keyboard [by dsimic]

[NB: This is a community blog and we are always delighted to host content by members of the community, especially when said written material is submitted by noteworthy contributors. We never alter or edit written material submitted to us (unless necessary – e.g. for clarity, typos, composition, structure, etc). Please consider the following as an opinion piece, which does not necessarily reflect the position of the Pine Store Ltd. or PINE64 community’s management team.]

Let’s face it, there are a few well-known issues with the PinePhone (Pro) Keyboard Add-On (PPKB) that have been identified since its launch. Even more importantly, there have also been a few complaints about the lack of official transparency and openness regarding these issues, which this write-up will attempt to remedy by providing a long-overdue official summary of the issues. Perhaps this write-up will be a bit long and filled with more technical stuff than is usual in the community updates, but in this case, there is no point in oversimplifying things or in beating around the bush. If you do not have the time to read this section in its entirety, here is a TL;DR – when the PPKB is attached to a PinePhone (Pro), please treat the phone’s USB port as if it did not exist.

In this write-up I’ll refer to both the PinePhone and the PinePhone Pro collectively as ‘the phone’, where the same applies to both variants, for the sake of brevity. Using ‘PPKB’ as the abbreviation for ‘PinePhone (Pro) Keyboard Add-On’ has already been established. It is also good to point out that the PPKB is internally made of two independent parts, the charging part, and the keyboard part. As visible in the PPKB schematic, the former is based on the IP5209 which charges the PPKB battery and provides the 5V boost output to power the phone, and the latter is based on the EM85F684A, powered independently by the phone.

Alright, let’s get into more details. There are three primary issues with the charging part of the PPKB, which were both identified very early during the development of the PPKB, but the issues were partially dismissed because the limited testing that was possible during the development was unable to prove that the issues are real and capable of inflicting actual damage to the equipment. However, putting the PPKB into the hands of so many people effectively resulted in lots of testing, with wildly different environments, which unfortunately resulted in two issues surfacing as real issues and capable of damaging the equipment. An unfortunate side issue is that, for a yet unknown reason, no printed manuals were included in the retail cardboard boxes in the first PPKB batch, which caused unnecessary confusion among the owners.

The first issue with the charging part of the PPKB comes from the fact that the PPKB is connected to the phone in a way that makes it act as some kind of an invisible USB charger that is plugged into the phone’s USB port all the time when the PPKB is attached. Of course, it does not look like that from the outside, but that is the way one of the pogo pins found under the back cover of the phone is wired internally. That pogo pin is electrically the same as the 5 V pins found inside the phone’s USB Type-C port, to which an external USB charger connects to. Thus, connecting a USB charger to the phone’s USB port while the PPKB is attached is effectively the same as splicing two USB chargers together, which usually does not result in anything bad due to the construction of the chargers, but it also sometimes causes damage to the chargers (let’s remember once again that the PPKB is an invisible charger). Unfortunately, a few PPKB owners had to discover all that on their own, and we had a few PPKBs releasing the magic smoke.

To be fair, it is possible to turn the PPKB’s 5 V boost output off, both in software that talks to the battery charging IC inside the PPKB and by using the physical button on the PPKB itself, but it was concluded empirically that the inactive status of the charging part of the PPKB achieved that way simply cannot be trusted, because the charging part may become active again unexpectedly. Moreover, nothing gets electrically disconnected that way, which still ends up in a USB charger plugged into the phone’s USB port feeding power into the charging part of the PPKB, which in this case may be even worse for the health of the charging part, because there is now no power coming out of the PPKB to “fight against” the power coming in from the USB charger. Not good at all.

To sum it up so far, you must never use the phone’s USB port for charging when a PPKB is attached to it. As we know, the official PPKB manual already says that a USB charger must never be connected to the phone’s USB port when the PPKB is hanging off its back, so it has all been about old news so far, but with the additional, hopefully helpful, descriptions of how it all works together.

The second issue with the charging part of the PPKB comes from the fact that the phone, among other things, acts as a 5V source for the bus-powered USB devices connected to its USB port; in the USB Power Delivery (PD) lingo, the phone can act as a PD power source. The 5V boost regulator inside the phone, which provides that 5 V power source when needed, may also be seen as another invisible USB “charger” connected to the same point where the PPKB and the external USB charger are connected — the 5 V pins found inside the phone’s USB Type-C port. Of course, appropriate mechanisms exist to prevent the phone’s 5 V power source from becoming turned on while a USB charger or a self-powered USB device is plugged into the phone’s USB port, but those mechanisms are unfortunately not perfect, and the existence of the PPKB as another power source throws all that off.

In particular, the internal 5 V power source in the PinePhone is controlled at the hardware level by the closed-source firmware blob that runs inside the ANX7688, which handles some of the functions of the PinePhone’s USB Type-C port. As a result, relying on the ANX7688 firmware to keep the PinePhone’s internal 5 V power source turned off is simply impossible when a bus-powered USB device is plugged into the PinePhone’s USB port. Moreover, it’s possible for the battery voltage to become present as the power supply for bus-powered USB devices, instead of the boosted 5 V voltage, which may actually put the circuitry inside the PinePhone at even higher risk of damage. On the bright side, the internal 5 V power source is controlled entirely by software in the BraveHeart revision of the PinePhone, which puts BraveHeart owners in a much better position, but I’m not aware of the required software support actually being available. As the final result, we can effectively again have two ‘invisible USB chargers’ spliced together when a bus-powered USB device is plugged into the PinePhone’s USB port. Again, not good at all.

When it comes to the PinePhone Pro’s internal 5 V power source, things are luckily a bit better. The internal 5 V power source is controlled by the RK818 PMIC, which according to its datasheet should react properly whenever externally supplied 5 V is detected, turning the PinePhone Pro’s internal 5 V power source off.  Though, some issues may still be present, such as not knowing for sure what happens when the PPKB’s boost output is turned off while a bus-powered USB device is plugged into the PinePhone Pro’s USB port, at which point the internal 5 V power source should become turned on automatically, possibly glitching the connected USB device and effectively starting to feed power into the PPKB, etc. In a few words, things can quickly become exactly the same as having two “invisible USB chargers” spliced together, as described above. None of this has been tested or confirmed yet, which means that the PinePhone Pro is getting the same treatment as the PinePhone in this regard, at least for now. Not good, once again.

The third issue with the charging part of the PPKB, which is completely independent of the first two issues, is that a bus-powered USB device plugged into the phone’s USB port can draw power directly from the PPKB’s 5V boost output, with no additional current limiting in place. As a result, a misbehaving USB device can end up drawing up to 2.4 A from the PPKB, through the phone’s USB port, regardless of the actual power negotiation that took place. In general, this should not cause any permanent damage to the phone or the PPKB, because they were both designed to handle such currents during regular charging. However, it may end up causing damage to a misbehaving bus-powered USB device, because it may not be designed to withstand up to 12 W going into it in case of some failure. To be fair, this scenario with a misbehaving USB device that draws a lot of power and burns itself down should be very rare, at least in theory. These are hopefully not the famous last words. 🙂

Finally, to sum it all up, it is not only that the phone’s USB port must not be used for charging, but it must also not be used to connect bus-powered USB devices. To put it differently, when a PPKB is attached to your phone, please treat the phone’s USB port as if it did not exist at all.

I will also create a couple of new pages in the PINE64 Wiki that will provide even more details about the PPKB issues, together with the relevant excerpts from the PinePhone and PinePhone Pro schematics, etc. Those Wiki pages will provide further explanations, so please feel free to check them out once they become available.


The first PineSound development boards have already been allocated, and I got some hands-on time with both the board and PineBuds prototype earlier this month. There isn’t much I can say about the PineSound dev board that I haven’t already said in last month’s update, but I wanted to share my experience with the PineBuds. Consider this a first look. Before I get into it, I want to make it clear that it will take (yet undetermined) time before the buds become available, and much will change between now and then. I also won’t write about the feel of the plastic, since this prototype was CNCd (yeah, I didn’t know you can CNC plastic either), and in all likelihood, the final version will end up feeling nothing like this. The buds themselves are nice, really small, and light. They are not the smallest buds I’ve ever seen, but they are certainly among the smaller ones I’ve tried (and I’ve tried quite a few – I’m a bit of a connoisseur). The default tuning sounds good, offering a pleasant V-shaped curve. I wanted to underline this because the V sound signature isn’t something I particularly enjoy. Obviously, a major draw of the PineBuds is that you’ll be able to flash the internal EQ with any sound signature, and I’m certain someone will create a ‘flat’ sound signature for the Buds. 

We’ve gone through a few iterations of renders, trying to figure out how we want the PineBuds to look. I am sharing some ideas below – there is no guarantee they will look like this, these are just some ideas.

PineBuds concept renders

The carrying case has some way to go before it reaches a production-ready status. The prototype case we’ve shown last month has no charging or battery LED status indicators, and it is something we’ll want to change. We’ve also decided on a sliding rather than a hinged mechanism for the lid. At present the mechanism leaves much to be desired. Obviously, it is still very early and this unit is just a proof of concept, but even at this stage, it’s clear that refining will be needed to deliver a good experience of opening and closing the case. We also haven’t zeroed in on a suitable battery to use inside the case – obviously, the bigger the battery we can squeeze in the better. As I mentioned, the current prototype was CNC milled, so I can’t speak to the feel of the shell, but the shape and size of the case are good if a little bit large. I think that the larger size of the case will be justified by the battery capacity. That’s all I have for the time being – as new prototypes are created I’ll make sure to update you on this project’s progress. 


The InfiniTime team is still working steadily on the project! A few improvements have already been merged since the last release. I won’t go into much detail as they are not released yet, but you can see the overview of what has already been done and what we are working on for the next version by going to the next milestone page.

Features and fixes already merged for the next release of InfiniTime

Among other things, we are actively working on leveraging the external flash memory of the watch to store pictures and fonts. This will allow us to free up quite a lot of space in the memory of the PineTime. I’ve recently done a few performance tests of various implementations. I took a lot of inspiration from PineTimeLite. In this fork of InfiniTime, Joaquim has already done a lot of experimentation with loading resources from this external memory, and I hope that we’ll be able to achieve similar results in InfiniTime soon!

ITD, the InfiniTime daemon and GUI application written in Go has recently released a new version 0.0.5. This new version adds a new whitelist feature that is very useful when you have multiple PineTimes laying on your desk. It also implements all new functionalities from InfiniTime like the filesystem and weather APIs. Even if those APIs are not usable by the end-users yet, their integrations in companion apps make the lives of the developers easier. For example, I use the filesystem functionality quite extensively right now to implement the resource loading from the external flash memory!

FS API integration in ITD

StarGate01, who has already contributed to InfiniTime, has created a new fork of InfiniTime specifically designed to expose high-frequency data from the accelerometer. They also built a companion app to display this data in real time. Those projects will certainly be useful to developers who want to develop advanced algorithms and signal processing based on the PineTime accelerometer!

High frequency data from PineTime’s accelerometer

That is all for this month. Remember, next community update is scheduled for June 28th. See you then!

23 responses to “May Update: Worth The Wait”

Your email address will not be published.

I accept the Privacy Policy

    Is it possible that the PineBuds might be adapted for use as hearing aids?

    If a user can “flash the internal EQ with any sound signature” then why not an EQ shaped to compensate for unique losses of segments of spectrum?

    The PineBuds contain a very sensitive microphone and a ‘speaker’ – so functioning as a hearing aid would seem a natural feature.

    Am I missing something?

    I believe in a previous announcement, perhaps the first announcement of the Pine Buds on April 1st, or the subsequent announcement with further details, it was suggested that one application for the Pine Buds might be hearing aids. They said this was not an intentional feature, but they drew the same conclusion you did, that the hardware itself certainly seems to have the prerequisites. It would, of course, be up to developers to develop software for this use case, if they wanted to.

    Ah, yeah, you can see this mentioned in the previous mid-April update, in the section about the Pine Buds 🙂

    Piotr Masłowski says:

    It seems the mentioned PPKB charging issues don’t really have much to do with the keyboard itself, but rather with how the 5V pogo pin is wired up inside the phone.

    Is it possible that a future revision of the PinePhone (Pro) or maybe some PinePhone 2 (Pro) could change that while still maintaining compatibility with all of the current accessories?

    Multiboot says:

    I’m thinking the same way. There was no mention of whether this will affect the Qi wireless changing case back accessory. Will wireless charging with a device connected to USB cause damage as well?

    Will there be a new version of just the mainboard be released for spare parts?

    Dragan Simic says:

    I’ll explain it all further in the already mentioned new pages in PINE64 wiki, which will provide more in-depth coverage of the issues, and will propose a hardware fix that requires improvements to both the PP(P) and PPKB.

    Please note that some issues with the wireless charging add-on case have also been discovered a couple of days ago, and, as a result, it was removed from Pine Store.

    Rodolfo Robles says:

    I’m kind of curious, will this hardware fix be possible to perform by not extremely experienced users or fixed in future productions?, because I just ordered the pro version and I’m kind of worried about the keyboard situation, in case I would not be able to fix it myself

    Same here, just bought the pinephone pro, the usb docking and the keyboard.
    I need to plug an external wifi adapter, this means that the keyboard is useless.

    Is there any refund anticipated because of theses issues ?

    Ryan Raymond says:

    Perhaps. Pine64 has made huge and ambitious hardware moves, but at this point what else could they do? They moved up to the biggest SBC as soon as it was available. More interesting and niche devices would probably have too small a market and put pressure on their finances.

    Have you guys considered making an analogue to Tile or AirTags? I have a dying TrackR and I won’t buy a Tile because I resent them keeping historical data behind a paywall (never mind voluntarily letting a corporation keep such detailed records of my location.)

    This is what I keep wishing for, too. When I first got a TrackR and later a Tile, I LOVED them for how convenient they were and how often they saved me major headaches from losing my keys / wallet etc. Eventually though I had to ditch them as both platforms slowly became super privacy invasive. Originally you could just use bluetooth to sense how close your device was and play a sound. By the time I stopped using them you basically had to have location tracking turned on all the time, also sharing your info with their network of users and having them permanently record where you and your devices are at all times. No thanks.

    I really wish there was just something simple that let me see how strong a bluetooth connection is and play a sound. Bonus points for a button I can press to locate my PinePhone (Pro).

    Will the Pinebook non pro come back in one or both sizes? I thought it was a good cheap computer. There is an alternative on Aliexpress but it doesn’t come with the same parts availability and open source documentation.

    Glad to see the Pinebook Pro is coming back.. hoping for an upgrade/refresh/something, with some more ram. (rather willing to pay the extra $ for it)

    Dragan Simic says:

    The RK3399 used in the Pinebook Pro is already “maxed out” when it comes to the amount of RAM, and there are currently no usable options for an objectively better SoC.

    Then I shall wait until something different happens with the PBP (perhaps that mythical RK3588??), or not. Tho here’s to hoping for a bit more of a bump in specs overall, by then (At double the price? Sure).

    Hi, the idea behind the Pinebuds is brilliant. Finally we can flee from the proprietary licensed decoders that Sony, Qualcomm, Fraunhofer, Samsung forced upon us.But my question is what kind of codecs will the buds use. Will we be able to flash whatever we want? Will SBC HD/XQ/HQ be supported? Theoretical BT codec that can be used is OPUS, FFmpeg, vorbis.

    Is there any link where I can pre order pinebook pro ? the store claims that we can pre-order late june, but link on the product is still out of stock.

    Have you thought about building an around-ear adapter (something like the Powerbeats Pro) for the pinebuds?

    I currently own a set of JBL wireless earbuds and ended up learning the hard way that it doesn’t do well on a run. So I ended up buying a separate pair of wireless earphones with around-ear support.

    Just a question about the ppkb, mine stopped charging through the ppkb, so I would have to charge the phone separately, then re-attach the ppkb after charging. It worked like that for a while, but now will not even communicate with the phone at all. So, all I’ve ended up with in the long run is a 6000mAh phone case that neither accepts, nor gives charge, or even works as a keyboard anymore. Do I need to re-flash something, or does it sound like a deeper issue?

    Just wanted to say you guys rock, found this randomly, searching for a preconfig secure anon and privacy rights oriented, Noob Linux type system; you even have opensource and proprietary hardware IP is something ive been searching for and pretty cool. What made me check out your video and site was the fact you guys are doing humanity especially the kids in need for school etc. a great honor – rarely see this so I had to comment maybe learn more or help. And in my 20 years developing in various proprietary, cybersec, sysops, counterintelligence, behavioral human interaction between exploits online systems, wargames, finding ways for my teams to break our systems and I infiltrated groups to warn companies during work and beyond; as recent as Apple, March 2021 (I didn’t want any bounty) just for them to believe my proof and warnings 7 months in advance which I had literally been laughed at several times and ignored… the exact things and the time of events I warned of became a reality. Costing countless millions and putting billions of clients at risk. This wasn’t my 100th rodeo.

    I think the main thing all cybersecurity companies and most orgs never understand and or believe is that [faulty] “AI” and their systems could ever be vulnerable, so they get lazy or think automation can make people like me and us obsolete is laughable at best, but diligence and human bodies creating, adapting being proactive in fintech systech and cyberspace industries must be on watch 24/7/365 it has be done in tandem with our technology. Humans are the ones abusing systems with tools and humans who invent and protect have to do the same “its not just the what and the how, but the who and the why.” One of many terms I coined, in my explaining to management what is important, teams that wondered why our departments were inundated with alerts and complaints often due to false positives/negatives due to their hubris and their faulty toys. It effected our users and I was infuriated.

    Working for and with most of the AAAs and startups, including various domestic US, Canadian and international law enforcement as my career and oaths I swore and renew daily starting when I was a young adult who used to exploit and scam on BBS, dialup and we called AOL cds frisbees to the advent of major MMOs and e-commerce … I got to a point where I realized I was hurting others and needed to use my skills for good and since – half my life I dedicated myself to protect everyones online security, privacy and liberties especially our youth- which you guys are having to deal with red tape for actually doing the things we need most; so maybe you understand my plight because people should be throwing funding and legal passes your way rather hinder it THAT is what we fight now – pushback for giving and doing good things, then being buss tossed for being incorruptible or not selling out.

    I had my life destroyed for doing my duty: what I was underpaid for, unappreciated and a usually thankless career while I met some of the top people in our industries who got rich of people for stealing or taking credit for work of others and take overs of good orgs; regardless if I or you saved them billions and resolved millions of investigations for recovery of victims and gave things to loyal clients or ones in need sometimes.

    I caught some really bad people and protect(ed) everyone online with my inventions and policies, training others even getting good people positions in the door; who are now producers or part of executive level teams…

    Unfortunately for me, I made and continue to make some corrupt people in high places very angry for exposing them or attempting to but its near impossible to do it alone. I have been discredited, framed even falsely under lies, arrested and “gitmoed” while my home was trashed, all my devices and online accounts my identity leaked and along with evidence/proof gone, the irony isnt lost on me to the extent that for 3 years now when I need help, I am ignored, called some outlandish lies and slanderous things, not a single avenue or someone has helped.

    Prior to recent events, my developments were reversed and used by orgs and those in power to gain off the trust and suffering of others – they are supposed to protect and give back to but instead destroyed what I had helped create as a standard for numerous orgs who are now monstrosities. I handed them the keys to the kingdom unwittingly years prior… my goal was to do something to unite, progress and provide safety; good, for humanity…

    So for these last 2 decades these top orgs I worked with have undone and even caused all the worst current events. I was originally pushed out and blacklisted for not listening to some exec who wanted to frame a 13 yr old kid for fraud, was told to look the other way and i responded with making it a priority investigation which I knew would likely end me, but for the interim led to finding out the youngster had take overs on his premium gaming / accounts his life was being ruined. He, had tens of thousands of dollars in VC and tradable VIs syphoned, his accounts and info then used as a mule as he was popular and a good kid in his online circles with lots of friends and online connections, his father was a wealthy District Attorney and let him have fun while he was away for work often. I found out his dad had served my org at the time for damages, instead my execs countered (hence my order to rub brush; they wanted the large sum of legal winnings).

    This led me down a 74 hour straight rabbit hole of coffee and to finding hundreds of other associated friends and other accounts all stripped and banned by multple orgs due to a criminal group who were stealing and laundering millions via mine, destroying victims lives and enjoyment. I was able to find the illegal accounts and freeze them all who were just about to dump everything on the grey/blackmarkets. And made sure to alert authorities and the client departments of additional ecomm/cc theft & fraud.

    After not leaving work over that 3 day event which would have been an average bulk investigation for my team usually my work as it was indepth and I was Lead, I had to make sure these things were done properly and gave tasks based on expertise so most of the dirty work and reports were on me, tediousness would be an understatement, but It was my responsibility and passion to fix these things; I reinstated the boy’s account and compensated him above the policies I created because he and all of them deserved better. Then i put the entire investigation on blast and said we don’t brush our users under the rug for internal gain- we protect them as they pay our bills and because its the right thing to do.

    His father dropped suit, my friend/colleague and another manager from our client relations department came several floors down across the building as he did at least once a week and he told me that the client’s were thankful and ecstatic ( 4 months the main kid and father who had been dedicated to us had been banned by the systems, and 1 day was too long imo)I rarely heard “thank you” but the client manager thanked me and seemed to know I had sacrificed my position to do what was right and hired years back to do. But I wont be in the history books, someone had hid the high profile case and knew id find it eventually but this made me realize not many orgs or authority can be trusted with user data our even have access to what they don’t need or use presently to sell and buy us like commodities…sorry for the novel.

    You guys are heroes and will be in our history books. Thanks for your hard work and being the last good few. Thank you for what you do.

Subscribe to the PINE64 blog