August update: RISC and reward

This month we take a close look at the Star64, check out PineBuds (Pro) progress and discuss the Pinecil V2. I also come bearing good news concerning the PinePhone Pro, which has seen a small but significant hardware redesign and some important software updates.    

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 Alex (clover), Gamiee, JF 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 August community update


  •  Housekeeping
    • We’re sponsoring Akadamy; meet us there!
    • Community Q&A was held August 13, you can now watch it on YouTube
    • A call for sticker design – looking forward to seeing what you come up with
    • Blade hostboard for the SOQuartz is now in the PineStore
    • The PinePower in the Pine Store and EU store is grounded – cause for confusion outdated photographs 
  • PinePhone (Pro)
    • Spare parts for the PinePhone Pro are now in stock
    • Small hardware redesign – the PinePhone Pro now takes nano SIM
    • Megi’s patches bring improvements to sound on the PinePhone Pro
    • New releases from postmarketOS, DanctNIX, OpenSUSE and Manjaro; OpenSUSE shows off Qi Wireless charging
    • Work-around instructions for Mobian installer issues
  • Star64
    • Pictures of the first Star64 prototype 
    • Overview of the final Star64 IO layout, components (WiFi 6 & BT 5.2among them) and features
    • Debian and Fedora already being ported to the SoC; we trust many other OSes will follow
  • Pinecil
    • First batch of Pinecil V2 sold out in record time; next batch in EU store early September and Pine Store mid-September
    • Pinecil V1 vs V2 and tip comparison by end-user – very cool video
    • Pinecil V2 online authenticator; a walk-through of how to check whether if your unit is legit
    • Ships with newest IronOS firmware
  • PineTime
    • Watchmate: new companion app for desktop and Linux phones
    • Watchmate works with InfiniTime and incorporates key functionality
    • InfiniLink iOS companion app transferred to PINE64 community


We’re once again one of the sponsors of this year’s Akademy, which is taking place in Barcelona 1-7 October. For those of you who don’t know about Akademy – it is an annual non-commercial meetup organized by the KDE Community. From memory, this is the 5th time that we’re a part of and sponsoring the event. Since this year’s meetup is an in-person event we’ll be flying into Barcelona to attend. Keep an eye out for Marek, TL and myself during the weekend of 30 September and October 3rd. We’re taking this as an opportunity to meet and mingle with people, so it is unlikely that we’ll be holding any talks or the like.

If you live in Europe, are a fan of KDE and happen to like our products then drop-by Akademy in Barcelona this year

We held the quarterly Q&A on August 13. As usual, Marek and I answered questions from the chats and for the first time managed to answer nearly all the questions posed. This time around we also managed to stream the Q&A to both Youtube and Peertube, while simultaneously having people in the Discord stage. Kudos to Marek for getting it all working this time around. The recording of the full and uncut Q&A session is available on Youtube, and thanks to Pak0St there are chapters available so you can easily find the bits and pieces you’re particularly interested in. The next Q&A will be held sometime in November. 

Live recording of the third community Q&A held on August 15, 2022

In other community news – we’ll be printing PINE64 stickers for upcoming community events (I am keeping my fingers crossed FOSDEM 2023 is an in-person event). While we’ll surely be printing some fairly generic PINE64 branded stickers, we also want to reach out to you for submissions. So if you’re artistic and would like to submit a PINE64-centered sticker design, then we’re more than happy to receive it. Make sure to have the sticker design include your name or handle. As for design requirements, it needs to be a grayscale and read well in a small size. If we receive multiple submissions, then we’ll run some sort of community poll and have you select the ones you feel represent the project best. Please post your submissions on the forum or, if you prefer, in the #offtopic community chat; make sure to ping the mods to make them aware of the submission.   

The Blade hostboard for the SOQuartz is now available in the Pine Store. In case you missed it, I wrote about the Blade and other SOQuartz hostboards back in May. This hostboard has been designed for clustering and fits inside a standard 1U server rack. You can fit 12 or more Blade hostboards into a single rack. I had the opportunity to check out a Blade prototype in May and was really quite surprised by how slim it was and how much I/O was present in the tiny space that the PCB provides. If you’ve been interested in clusters and were waiting for a spiritual successor to the Clusterboard then here it is.

BLADE hostboard with 8GB SOQuartz installed

Lastly, I want to make it clear that the PinePower desktop currently sold in the Pine Store and EU store is grounded (and has 3 prong plug) as requested by the community. I wrote about this new hardware revision already in the April community update -I encourage you to read the blog entry in case you missed it. I am aware that the pictures in both stores were outdated for a couple of days when the new batch arrived, which led to some confusion as to whether the hardware is from the new revision. All PinePower desktop units currently on sale and produced in the future will be grounded. Apologies for the confusion caused by outdated pictures.

PinePhone (Pro)

Let’s start with some hardware news. Spare parts for the PinePhone and PinePhone Pro are now in stock. I know that many users with cracked screens or damaged back-cases have been waiting for these parts to return to the store. I am happy to let you know that spare PinePhone (Pro) keyboard PCBs are now also available for purchase. I am mentioning the availability of these parts explicitly at the start of this section because I’ve recently seen people question our commitment to creating repairable hardware. So, let me assure you that we’re as committed to making repairable hardware as we always have been. The reason why spare parts were out of stock for a period of time is simply due to them selling out from the last PinePhone (Pro) production batches – spare parts are usually only delivered with a new production run. The spare parts are basically unassembled PinePhone (Pro) units. Same goes for keyboards and other equipment. If there is a break in hardware deliveries then it is likely that spare parts will temporarily sell out too. However moving forward we’ll hold a larger stock of spare parts. 

In other hardware news, the most recent production run of the PinePhone Pro has seen a small but important redesign, at least for newcomers. One of the most common failure points on the PinePhone and PinePhone pro is the SIM slot. Users were required to use an adapter for their nano SIMs to fit into the micro SIM slot – some would insert the adapter without a SIM, pull it out, and damage the pins in the process. Others would insert a micro SD card into the SIM slot thereby damaging it. For this reason, the new production run of the PinePhone Pro incorporates a nano SIM slot instead. The slot has a clever design which prevents new users from accidentally inserting a micro SD inside too; to insert the SIM card you need to pull out a little tray (which doesn’t come all the way out), into which the SIM is inserted. We hope that this small improvement will result in fewer broken SIM and SD slots moving forward.

Nano SIM slot on the PinePhone Pro

There are a few software news I’d also like to cover this month. The most notable of which, and one which will eventually surely find its way into all OSes, concerns sound on the PinePhone Pro. Megi has recently released a set of patches that address some of the issues people have been experiencing: sound codec not working after boot (prior to an app playing audio), changing controls while headphone or speaker output is active breaks audio, sound stutter when serial console is enabled in CLI, OUTMIX and RECMIX drivers not matching the schematic and microphone quality. I invite you to read and follow megi’s development (b)log to learn of the details but, in short, the patches ought to improve the sound situation on the PinePhone Pro. I hope to see them make their way into individual OSes soon. 

As for the OSes, we’ve seen a few releases for the PinePhone and PinePhone Pro this past month. This includes (at least to my knowledge – there may be others) postmarketOS, Manjaro, OpenSUSE and DanctNIX (Arch). Most of the distributions shipping the Phosh mobile environment have now updated to the newest version which adds swiping motions; I haven’t had the opportunity to try the newest version of Phosh myself, but I hear very good things about it. I would also like to note that OpenSUSE shared an image of the PinePhone charging wirelessly using the Qi wireless charging case (currently out of stock), which is super cool to see. I am including a picture from the tweet below.

Wireless charging on the PinePhone running OpenSUSE – via Adrian Campos Garrido

There is one more thing I’d like to mention in this blog post that is distro-specific: I’ve seen reports that Mobian users have issues with the installer image. The problem it seems concerns the root partition not expanding properly during the installation process. I reached out to Mobian developers about a potential work-around and Undef was really helpful in emailing me comprehensive instructions. I should also note that Mobian’s dev team is aware of the problem and actively working to resolve it. 

Here’s the work-around:

Resize the primary partition using parted.

  • $ sudo apt install parted

Make sure to select the right storage device (exchange for x below); 2 will usually be eMMC while 0 is likely to be SD.   

  • $ sudo parted /dev/mmcblkX

Inside parted run print just to make sure you are using the proper 

device. You should see two primary partitions:

  • (parted) print

Enlarge the 2nd to 100% capacity:

  • (parted) resizepart 2 100%

Print to see if the partition expanded correctly and then quit the program:

  • (parted) print
  • (parted) quit

If you’re using an encrypted device run the following command – you will be asked for your encryption password: 

  • $ sudo cryptsetup resize calamares_crypt

Then proceed to resize the ext4 filesystem:

  •  $ sudo resize2fs /dev/mapper/calamares_crypt

Finally resize the btrfs filesystem and check results:

  • $ sudo btrfs filesystem resize max /
  • $ df -h

  Once again, many thanks to Undef for the detailed instructions. 


This month I come bearing good news about the Star64 RISC-V single board computer. Just three months after the board’s initial announcement today I get the privilege of unveiling the prototype – and I hope you’ll admit that it looks mighty cool. Star64 is the first true RISC-V SBC from us (I mean, unless you really consider the Pinecil a SBC), but as I wrote last month it certainly isn’t the last RISC-V piece of hardware you’ll be seeing from us. Just as a short recap: Star64 comes with a StarFive JH7110 64bit CPU sporting quad SiFive FU740 cores clocked at 1.5GHz. The SOC is equipped with BXE-4-32 from Imagination Technologies, which is said to be a solid mid-range GPU. Star64 will be available in two configurations – with 4Gb and 8GB of RAM, similarly to the Quartz64. Both hardware versions include USB 3.0 and a PCIe slot as well as two native Gigabit Ethernet NICs.

Star64 IO — left: dual Gigabit Ethernet, HDMI & power-in // right: 3X USB 2.0 & USB 3.0

The IO arrangement is very similar to what you’ve come to expect from one of our model-A type boards. Along the long leading edges you’ll find PCIe on one end and GPIO on the other. At one end of the board you’ll find a digital video output, a double-stacked Gigabit Ethernet port and a 12V barrel plug for power. On the opposite side, you’ll find 3x USB 2.0, 1x USB 3.0, an audio jack as well as a power button. There are also two U.FL ports for antennas – one for bluetooth and the other for WiFi.

Star64 — left: top view // right: bottom view

The onboard WiFi/BT module is RTL8852BU MIMO WiFi 6 with BT 5.2; it may already be supported in mainline Linux. The Star64 also has an MiPi display output complete with a touch panel (TP) input, a 12V power port, a CSI camera port and an eMMC slot. A micro SD card slot can be found at the bottom of the PCB. Similarly to the RockPro64 and Quartz64,  the 12V port on the Star64 can be used for powering other hardware directly from the board – a popular example is powering one or multiple SSDs connected to a PCIe SATA adapter. I’ll add that, at least in theory, the Star64 would make a great NAS because of its SoCs low thermals and idle power. I am looking forward to seeing NAS-focused Linux or BSD* OSes available for the board.

Speaking of software, efforts to support the SoC in Linux have already begun. I’ve been told that both Debian and Fedora are already being ported to the StarFive JH7110, which is great news. We are certain that many other OSes will follow swiftly – especially once we start delivering the Star64 to interested developers. On the subject of availability: the Star64 will be available in a few weeks time, and will initially be available to developers. Given the interest in the Star64’s and the SoC powering I hope to see functional distributions available for the board soon after launch. We will obviously be monitoring the Star64’s software progress in the months to come and keep you posted on how development proceeds.

PineBuds Pro

A quick foreword about PineBuds changing name to PineBuds Pro prior to release: the hardware stays the same, it’s just naming convention – or branding if you will – changes to include the ‘Pro’ suffix. We’re doing this to indicate the additional functionality that the earbuds are capable of – ANC in particular. That’s all.  

I am glad to report that development of the PineBuds Pro is proceeding well. In fact, CE/FCC testing is scheduled to start early September, so a mid-Q4 release is highly likely.  In July I shared pictures of the first moulded PineBuds carry case without the electronic guts – today I get to show pictures of the first moulded and working prototypes. This time around this includes the pods and the case, both of which arrived from the factory just the other day. As you can probably tell from the picture, the final mould of the carry case looks much more refined than the CNCd version shown in April. It is hard to make it out from the photos, but the case features a textured finish on the outside and a smooth finish on the inside. The buds themselves have a two-texture finish too, with the stems made out of shiny plastic and the body of the buds being matte. While none of the pictures below depict this, the case now also features a small row of LEDs on the front, used to indicate charging status and remaining battery. But let me stress this again – these are pictures of prototypes, and thus everything you see is subject to change.

PineBuds — left: buds in carry case // right: buds seen next to the casa

Since the last post discussing the PineBuds we received much feedback regarding our initial decision not to brand the buds. This is not the first time we receive feedback concerning branding from the community; as a rule of thumb, we usually try to keep branding to a minimum on our hardware. As was the case with the Pinebook Pro, PinePhone and PineTab – we always try to incorporate the PINE64 logo in some tasteful and non-intrusive way. But this is a bit hard to achieve on something as small as a pair of wireless earphones. However, it does seem people are keen on rocking buds with a PINE64 pine cone, so we’ll run some test prints in the next few weeks and see how they turn out. I am attaching some impressions for you to take a look at below. 

Lastly, the Pine Store commissioned development of an alternative SDK and firmware for the PineBuds. The hope is that the new SDK will make development of community customised and user-tailored firmware easier to achieve. The custom firmware and SDK builds are about 2 weeks away I am told – once delivered we’ll have developers evaluate the efforts. If this is the first time you’re hearing about the PineBuds I invite you to read the April and May community updates in which the hardware was introduced and discussed at some length. I am sure I’ll have more information about the PineBuds to report next month, so stay tuned. 

Proposed PineBuds branding – let us know what you think

Pinecil [by Gamiee]

The Pinecil V2 landed earlier this month and sold out almost instantly. The next production run of the ought to be available soon however – you can expect the next batch to land in PINE64 EU at the beginning of September and in the Pine Store a few weeks later. There will likely be a limit on how many units can be ordered by one person to make sure that everyone who wants one can get one (if they order within the first 72 hours or so). To be notified of availability, please follow PINE64 and PINE64 EU on Telegram, Mastodon and Twitter. We’ll make sure to give everyone a solid 24hrs heads-up before the next Pinecil batch becomes available again. 

Earlier this month I came across a very interesting comparison between Pinecil V1 and V2, which also includes a performance overview of the new tips. Spoiler alert, the V2 performs better when supplied enough power, but the new tips heat up much faster on both the V1 and V2. When combined with the right power source and fitted with the short 6.2 ohm tip the V2 heats up to a temperature of 300*C in under 3 seconds. It is a really interesting video by one of our community members, and I advise anyone interested in the Pinecil V2 to watch it. 

A comparison between Pinecil V1 and V2 as well as the new 6.2ohm tips – by River B.

As we mentioned in the previous community update, we have implemented a few anti-counterfeit measures into Pinecil V2. One of them is the possibility to verify that your Pinecil V2 is original. And you can do this on our authenticity verification page, which you can find on The process is quite simple: on your Pinecil enter the debug menu by holding down the minus (-) button, scroll down to the ID tab using plus (+) and enter the serial number (first row) into the online authenticator. You’ll be immediately informed whether your V2 is an authentic PINE64 product or a knock-off. 

Authenticity checked page

The Pinecil V2 is being shipped with IronOS v2.18, which is still up-to-date at the time of writing. There are no requirements to update the firmware, but if anyone wants to update their V2 then it is not currently possible. This is due to the new Bouffalo chip not using the DFU protocol for flashing and the flash tool, which supports the Bouffalo’s flashing protocol, is still a work in progress. It should, however, be available soon; stay tuned for more information in the coming weeks and months.

PineTime [by JF]

This month, we welcome a new companion app in the PineTime ecosystem: watchmate. The author announced it on Twitter and Mastodon a few days ago. Watchmate is a companion app which runs on desktop and mobile Linux and is compatible with PineTime running InfiniTime. Written in Rust and based on libadwaita and BlueR it already supports many features from InfiniTime, such as setting the time, reading battery level, recording the heart rate value, controlling media player and OTA firmware updates.

The UI is really nice and easy to use and a bit similar to Siglo: once connected, it displays various info, allows you to select the media player that will send info to the Music app and upgrade the firmware over the air (OTA). Watchmate will display a notification when it detects that a newer version of InfiniTime is available in the project’s repository, which is a very convenient feature!

Watchmate functionality

A few features like secure pairing and notifications are not implemented yet but they are already listed in the project roadmap. They waited to test watchmate and have enough time to maintain the project, and that they would transfer the project to anyone who would like to take over it. Since then the Github project has already been transferred to the InfiniTime organization and the application on the app store has been transferred to an account managed by Pine64 to ensure that it remains available on the Apple Store until it finds a new maintainer! Thanks again to xan-m for their work on InfiniLink!

Watchmate running on the PinePhone Pro and Pinebook Pro

Thats all for this month, I’ll catch you all in September.

33 responses to “August update: RISC and reward”

Your email address will not be published.

I accept the Privacy Policy

    paul janson says:

    I actually think the pinedio stack is a nice maker platform, and I am interested in lora myself.
    I think the pinedio stack can evolve to an alternative low power sbc for tinker projects. The Risc-V, IO, wifi, BT, touchscreen is interesting.
    And the lora option allows IOT applications.
    I hope to see a first version (with the screen and lora) somewhere next year, with the RT OS and SDK

    Hello, nice RISC-V board :). I have few questions:

    Will the final version of Star64 board have open ended PCIe slot?
    How many PCIe lanes of which generation are connected to the slot?
    How big PCI region space can be used for PCIe devices (ex. GPUs usually needs at least 256MiB + few more MiB)?
    Will there be a technical reference manual (starfive web doesn’t have it yet)?

    Once again, another update stating that the video summary can be watched on the Peertube channel that hasn’t been updated since April.

    Let’s see if my comment pointing this out gets deleted again, like previous months.

    Question about the repairability of Pinebuds:
    Plans to make the buds’ battery replaceable without needing to destroy completely the buds in the process? (i.e.: unlike AirPods)

    I too have asked about this in a previous post (and I see that you have replied to it), as well as alluded to it in the forum.

    I really do hope that repairability and sustainability will be real focus points.

    Is there any plan still in place to restart manufacturing pinetabs? I’ve been wanting to buy one since early 2020, and I haven’t seen any mention of them in several months. Do you still plan to start manufacturing them in 2022, particularly now that you’ve found a source for the LCD panels?

    Thanks for the Star64 update – have been waiting for it since VisionFive 2 was announced. Both boards look really similar spec-wise, which should speed up bringup by various distros. Nice to see the dual GMAC setup along with SPI flash on-board. Can’t wait to get my hands on one and make a router out of it!

    Is there any plan still in place to restart manufacturing pinetabs? I’ve been wanting to buy one since early 2020, and I haven’t seen any mention of them in several months. Do you still plan to start manufacturing them in 2022, particularly now that you’ve found a source for the LCD panels?

    Is the GPU BXE-4-32 or BXE-2-32? I’m asking because in the VisionFive 2 announcement, they said BXE-4-32, or are there two variants of the SoC?

    My Mobian Phosh got borked after the last updates some 2 weeks ago and now gnome-control-center and gnome-software are gone and I can’t reinstall them because the pinephone-support package is not updateable and somehow those packages depend on that. I’m currently in an impossible packages situation(according to apt)
    Any idea how to solve this? Or am I forced to reflash?

    Regarding the Star64: love that it has 2x gigabit ethernet ports and the PCIx slot. Don’t like the RAM having no ECC, specially for NAS applications: running NAS reliably requires ECC, and not having it basically negates the benefit of using reliable file systems like ZFS. Also, do not like it having a single USB3 but a bunch of USB2… all ports (or at least half) should be USB3, albeit this could be worked around with a multi-port USB3 adapter on the PCIx slot.

    A question regarding it taking 12VDC power: does it have to be regulated (ie, exactly 12V) or can it be more flexible, like 10.5-14.5VDC one gets from an automobile DC system?

    Thanks in advance.

    The number of USB3 ports and availability of ECC will be limited by what the CPU can do. The older JH7100 SoC only has one USB3 port and does not support ECC RAM.

    I am extremely disappointed to see Realtek WiFi on the Star64.

    I hope that at the very least it will be a modular component, so that we could replace it with something that actually deserves to be called a WiFi adapter (even the Ampack/Broadcom modules are acceptable, however you can easily find Qualcomm QCA9377/QCA1023 for cheap nowadays (the QCA1023 should be cheaper, as it is a regional variant of the QCA9377 meant for the Chinese market), even if you are an OEM.

    Also, going Qualcomm is currently one of the least problematic venues for open-source, even more so for products from the ath9k family, where you do not even need to load up additional firmware to get it to work, since the proprietary firmware is burned onto the chip (I would prefer being able to replace the onboard firmware, however even that is better than nothing), as well as having proper documentation for open-source driver development, so you do not have to deal with Realtek’s subpar coding practices, nor Broadcom’s firmware shenanigans, and at the same time it is one of the most performant solutions on the market.

    Even if you put a QCA9377/QCA1023, which is a 150/433Mbps on 2.4/5Ghz, it will still perform extremely well, draw less power, and you will be getting proper Bluetooth support (You should be able to easily support Bluetooth 5.2, if the open source stack already supports it, and 5.3 and newer will be far easier with Qualcomm than any other manufacturer, not to mention Bluetooth LE, APT-X support (client side, like with phones, tablets, laptops and desktops).

    The way I see it, going Realtek is only detrimental for Pine64’s operations, and I am fully aware that they have been using Realtek since the beginning, which is why WiFi is so bad on most of Pine64’s products.

    There are also other low-cost options, such as Espressif’s solutions, Mediatek, perhaps even some of the Chinese newcomers, pretty much anything that is not Realtek will give a huge boost, both in quality and in credibility, to the wireless networking aspect (and to limited degree, also wired) of Pine64’s development.

    There is a reason why Realtek has never amounted to more than a big flop when someone tried taking them seriously (see the origins of Killer networking, Vigor’s VigorNIC VDSL2 modem PCIe card, and more examples), and that is that Realtek has never even cared about stability from the get-go, pretty much all of Realtek’s issues that were solved or worked around on Linux was thanks to the community, since even the code that Realtek did open-source, was done so in such a broken and inefficient state, that it was initially unusable, and Realtek didn’t do anything to change that, it was all volunteers from the community.

    The Realtek adapter also supports Bluetooth 5.2, Bluetooth LE, and APT-X. Furthermore, the Realtek chip is WiFi 6 and the chips you listed are all WiFi 5. I also don’t think that there are any WiFi 6 products currently being sold by Qualcomm. Mediatek drivers are very hit or miss, and any chinese newcomer isn’t probably not making a good, let alone open source WiFi chip.

    Also, there are no WiFi 6 modules that work without firmware being loaded from the OS.

    Also most Pine64 products have mostly used Broadcom for WiFi iirc.

    I do agree though that Realtek is kind of bad.

    Realtek supporting APT-X is kind of a surprise, however regarding WiFi (where the most and greatest issues lie), it doesn’t really help that it supports WiFi 6 (and I am fully aware that there are no options for WiFi 6 without closed source blobs being loaded from the disk) when it handles WiFi so badly (stability at best is mediocre, performance is the lowest possible, while requiring many more system resources,as well the the significantly higher power draw). Qualcomm does already have WiFi 6 products on the market (including via SDIO), however LTS support for the open-source drivers is still lacking, and while Mediatek is hit-or-miss, it has proven itself to be much more reliable than Realtek has ever been, which is part of the reason why there are quite a few Mediatek-based products that can be relied upon, while there are none from Realtek.

    In short, it’s better to have reliable WiFi 5 over unreliable WiFi 6, and even with WiFi 6, there are already quite a few solutions, some of which are even drop-in replacements, for Pine64’s products, so as long as they rely upon Realtek for WiFi, their wireless networking is nothing short of a joke, and is not fit to be considered as a serious product regarding WiFi, which is really a shame, since Pine64’s portfolio is awesome, however they seem to rely on the worst possible solution for WiFi, which pretty much destroys all credibility for usecases that actually require it.

    Lukasz, can you please download latest sbc-bench version from and then run ‘sbc-bench’ and also ‘sbc-bench -G’ (Geekbench mode) and share the results (via a Github issue or here)?

    I know software support situation is far away from benchmarking time but just to get an idea (especially how badly Geekbench ‘scores’ look on RISC-V).

    Lukasz Erecinski says:

    Hey! I trust all is well. I would bench the board if I had it on hand — the pictured board is one of very few in existence. But I will pass on your request. I’ll assume your contact email is the same as years ago? if yes then I can CC you in the request to benchmark the board. If your email changed then please email me on l.erecinski at 🙂

    I’d rather see the PineBuds with a logo. It looks much better and valuable (instead of looking like cheapish unbranded copies). Also, an unfimiliar logo may be a good hook to start a conversation 🙂

    witchhunter says:

    The advice on a new slot for SIM card on PPP is somewhat misleading. The slot for nano SIM card is narrower than the width of MicroSD card, so it is impossible to put MicroSD card into nano SIM slot. Although the opposite can be done, there is engraved picture of correct placement just above slots. Therefore, the main purpose of the tray (which can be pulled out) is to pull out the nano SIM card itself, which would be quite difficult otherwise.

    Hi guys!
    My question is:
    When will the new operating systems for the new RISC-V CPU be ready?
    If they already exist is it possible to have a link?
    Thanks for reply.

Subscribe to the PINE64 blog