Title.


I would like to post Tab Porn there.

Please correct me if this has been discussed elsewhere, but has Brave Heart edition Pinephones been through FCC och CE testing? Just curious

Edit: or I'll just wait for the phone to arrive and I can just look at the back of the phone for a mark

This may be a n00b question but I am slightly puzzled about this:

I assume - in my naivety - that the Linux kernel abstracts away all hardware details from a distributions system services and applications. Thus, if there already is a kernel for the Rockchip 3399 platform, why is it that there are competing efforts (default mrfixit Debian 9 vs. ayufan Ubuntu 18) where the hardware support is not identical?

I would assume every distribution is supposed to work exactly the same in terms of hardware support as long as you put the same kernel underneath. Where am I going wrong?


Also, what is the main challenge to port the up-to-date arm64 Linux kernel to the rk3399 platform? I would have assumed the vanilla kernel is missing device drivers that are specific to the rk3399 board or the Pinebook Pro as a whole but could not these be added (either right into the kernel or as modules)?

Please understand this is not critique but simply me trying to get a better insight. So far I have only used Linux distributions but never worried about kernel versions etc...

Hi Everyone,

I did a one of these casual updates last month and thought that it would be a good idea to do one this month too. I won't be writing them every single month, but when there is something noteworthy happening - like now - I feel they serve a purpose.

Speaking of updates, the December update will be the last one of the year (obviously) and I'll run a poll a week prior to it being posted asking about how we did this year and what you'd like us to improve on in 2020. Keep a lookout for that, because we really like to hear back from you on this.

Pinebook Pro

We have the firmware for the Pinebook Pro trackpad & keyboard. I am running a little update thread here for those interested. Long story short, the process of flashing the new firmware is currently quite involved and we're thinking of ways to make it relatively painless. Both @xalius and @ayufan have been instrumental in working these things out - thanks guys! Ayufan is currently rewriting the flashing software based on the source, so the flashing process will either be fully or partly automated when end-users get it in their hands. Future PBPs will ship with this firmware already flashed.

[edit 26/11/2019] Trackpad fix is out and available here.

PinePhone

The Brave Heart edition is up for per-order right now. [sarcasm] The launch went smoothly without incidents Those of you who waited up / woke up to be there at zero-hour are sworn to secrecy and required to hold the line that it all went flawlessly [/sarcasm]. Congrats on getting your pre-orders in.  

Approximately half of all PinePhones have now sold so I expect that all will be gone by the end of this week.
Developer's phones keep shipping and are going out steadily albeit slower than we'd (and probably developers) hoped. A large portion of the dev phones will go out this week.

Behind the scenes a lot of debugging, testing and tweaking is going on to make sure that we can deliver the best early-adopter's phone possible. I'll leave the details for next months update. I should have my PinePhone (still pre-production rather than Brave Heart Edition) at the end of the month, and intend to record a video about it. If there are some things you'd like to see in this video - leave it in the comment below.

PineTab

In this month's update I asked if you'd like us to run an early adopters batch for the PineTab. The response to my query was very positive and the number of requests for making this happen was surprisingly large. As a result, its happening. The production of and early adopters batch of PineTabs has now began. I don't really have any other details to offer at this time; we probably going to wait until all the Brave Heart PinePhones ship before making arrangements for the PineTab. We still need a suitable OS to accompany this batch ... so it may yet take some time.  


PineTime

PineTime development has taken off and I've been super impressed by the progress. In recent weeks we've seen some spectacular write-ups too, like this one by Lup Yuen Lee. What makes so many of these write-ups interesting is that people don't always use the PineTime 'the way we envisaged', which frankly speaking is great and exciting.

As I have already indicated in the past on the forum, blog, chats and elsewhere - we were considering making the PineTime dev kits widely available, but were unsure of how many people would actually want one. As it turns out, a lot of people do. And this is good news, since this is a truly experimental side-kick community project.  So in the coming days we'll be making PineTime kits available for purchase from the Pine Store.

i can't seem to find any information about the boot/bios 
mainly what key to press at boot to enter the bios
but also if there is a "factory restore" image that i can easily flash
and if not how would i go about doing a "factory restore"?

Hello to all

I have a Rock64 2GB and I need Real VNC server on it.
My installation is Armbian Debian Stretch Desktop [microSD / eMMC Boot] [5.90].
Is the Real VNC Deb x64 package ok?
How can I install and configure Real VNC headless, just over SSH?

Thank you!

*  I do not see any Ubuntu Touch OS mentioned is the OS choices,
  I would have thought it would be in the top 5 or so.  ?
   The list appears to be closed  ?

---------------------

Posted from my New PBP

I am a big fan, of Pine, and there efforts...   As one of the Braveheart's customers, and a recent (1 year and counting) convert to Linux (Arch/KDE) I have tried various device combinations in the effort to  get to a  place  where the  Phone is the enabler to the Laptop equivalent experience.   so playing with Samsung's Dex efforts,  and Asus's ZenPhone / laptop like dock etc.    though none of those really had the software to make the  hardware work in the right alignment.

The Pine Phone on the other hand has the exact right hardware alignment to be a  plugin to a PineTab like case, which would give a portable slate with keyboard experience,  or maybe even a Pinebook Shell that the phone plugs into to provide a Laptop experience.

These would be considered accessories,  so they are dumb devices without say the phone or other Pine SoC board (with adapter board for common insertion).

The key is that it needs to insert into the shell of the device, unlike the Nexdock2 etc,  if not inserted into, maybe a recess that the phone has a magnetic case that locks into position etc this method would provide better long term support.

The Dock essentially would provide  the Screen, Typing and Battery extension aspects.

So I'm still running Bionic-Mate on my PBP off SD. 

Last night I noticed there was a red icon in the top menu bar (or whatever it's called) that said something about not being able to run updates (it wouldn't let me cut and paste what it read).  I ignored it because I was busy using the PBP for other things, and did not want to risk breaking anything.  Then it went away on its own. 

This afternoon I ran the updater.  After the update, I had two WiFi indicator icons.  So I tried to remove one.  Unfortunately, it also removed the battery indicator.  After restarting the computer, I now have zero WiFi indicator icons.  I also do not have a battery or sound indicator.  It still shows processor speed, "EN" (for an English keyboard), weather, and date & time.

How do I get the missing menu items back?

Hi,

after some initial shipment problems, I finally managed to assemble my NAS setup:

RockPro64 4GB
2x 4TB Seagate IronWolf 3.5" HDD
PCI-e to Dual SATA-II Interface Card
NAS case with fan and Pine64 power supply (5A)

I successfully installed ayufans openmediavault builds (version 0.9.14, tried both armhf and arm64), updated all packages using the web OMV web frontend, enabled SSH access and configured email notifications and SMART monitoring. Then I tried to configure a mdadm RAID1 via the OMV web frontend. During the sync process, at varying times (0.4%, 6%, ...), the setup crashes: timeouts when accessing the web interface, SSH connection not possible/hangs after entering the password, ICMP ping sometimes works, sometimes doesn't (I tried multiple times). Only a reboot reset (power cycle) helps, after which the RAID is in "sync pending" state. I really don't know what to try anymore.

Does anyone know what could be the problem? Could it maybe be the power supply? According to Seagate specs, each disk consumes max. 1.6A. How could I debug the issue? What log files should I look at?

Thanks