Just curious,  Could the speakers be reversed to point up instead of down  ? (They are mounted within the palm rest)
 From the pictures I have seen they do appear to be held in place by the edges of the speakers.  (?)
  Being slightly hard of hearing myself,
        I do appreciate my current laptops that have the speakers pointed up.
IF you have your laptop sitting on a soft surface, like the bed, or the couch, or your lap,
         it very effectively mutes the sound of speakers on the bottom of the case.

Hi.  Recently I acquired several Rock64 and among them a 4GB board that turns out to be a V2, the problem is when it comes to flashing and starting the board since it freezes and stops working within a few seconds.  I have searched for information on the forum but I can't find a solution.  I need help before resorting to product return.  thanks, sorry for the Google translation ...

Hi. I am trying to install ArchLinuxARM on the emmc module to boot Rock64 v2.0 board. When i'm trying the following happens.

1. I flash three u-boot images, as in tutorial. It seems working, because...

2. When i power up the Rock64, it writes some usuall messages to the UART on the. So, as i understand, u-boot images are being loaded successfully, partition table is being read successfully, so the Linux Kernel starts and writes a lot of info to the UART.

3. But when the kernel attempts to mount root file system, it can't do this and throws me to the emergency shell. Where i try to read from emmc, e.g., using the command

I couldn't find any info on the forum so i figured i might as well start a new thread so other can find it easily. 
I see that the PBP is out of stock at the moment. I was hesitant at first, as customs are insanely expensive here in the EU. It would cost me about 270€ to get a 180€ laptop across the border, so I didn't order it. Silly me now regrets it. Can silly me expect another batch or is the Pinebook Pro gone forever?
Thanks,
Luka

Hi everyone,


I have installed Lakka on my Rockpro64 and I have a Roshambo case, when I start the system, fan, on/off, reset and led don’t work, the OS starts normally but I have to plug/unplug the cord. Also don’t see the system reading the Roshambo cartridge, it only reads it if I use an adapter to the usb. Any idea how could I get the case working fine? also would be possible to use a generic Wi-Fi dongle as I don’t have the dedicated module? 

do I need to add a script? I found this online 

https://github.com/mrfixit2001/KintaroSnes-Rock64

Thanks in advance

Hi,

With the recent manjaro releases I'm getting more into using my pinebook and realizing the EU charger feels a little bit cheap and cheerful, especially with the need for an adapter for the UK.

Does anyone have a recommendation for something a bit more solid and with a UK plug on it?

Does the pinephone have modem isolation? I saw renders of the PCB, but not any wiring diagrams. Is there anything available showing the isolation?

Hi folks,

I lurk on here more or less. I bought the original pinebook. It worked for about two weeks and then I couldn't ever get it to boot up again after the battery died while running. But that's a different story for a different day.

I am a rare type of consumer who was an early and eager adopter of smartphones and pda's and now see them with disgust. For PDAs, I am still a loyal palm pilot user. On the phone end I used a variety of palm treos. Jumped over to the palm pre (what a disaster that was). Followed that horse for a few years and jumped to android at the galaxy s2 > s4 > s7 > grand prime > blackberry keyone (best smartphone i ever had) > j2

A year ago, my growing disdain for where the industry has gone (along with the internet) has driven me to abandon smartphones for a flip phone. It runs a locked down android that has a hotspot feature. Thing even comes with a media player and a radio tuner (internal fm hardware). While I find myself not missing the smartphone one iota, one thing I dislike on the flip phone is the old style texting. Most people I know prefer to text over talk and I often find myself going days without actually talking on the phone but will send/receive hundreds of sms/mms messages. Sometimes, if the conversation is complicated, I'll email my phone the message and forward it to the person I'm talking to because it's easier to use a keyboard.

Which brings me to this post. I'm brainstorming methods in which I can create a mms/sms-only device complete with a qwerty hardware keyboard, a small non-touch screen with a high enough resolution to display images, software for decoding video and software for playing them (received via text), usb-c for file transfer/storage/charging. Virtual keyboards suck hard. I don't really care how cheaply it's built either. The case can be 3d printed for all I care.

It should be easy enough to start with stock android and trim it down to only the basic sms/mms, carrier (3g/4g/etc), power management components (like my flip phone). 

I am considering the pinephone and adapting the hardware to make it appear somewhat like my old peek. I could tear apart my old peek and jam in pinephone guts. Problem is, last I checked the pinephone won't work with my one major constraint which is the carrier (Sprint). I'm on a family plan so, that's the one static requirement. I considered doing a pairing situation but that would require a phone everywhere I go to make that possible.

Ultimately, this project would simply be a fun endeavor and, if successful, would yield a device that fits my lifestyle.

I thought I understood Docker, but maybe not. I'm running ayufan's Ubuntu on my ROCK64; uname identifies it as aarch64. When I run Docker (via Kubernetes) and ask for a multi-architecture image, I get this error:

    no matching manifest for linux/arm/v8 in the manifest list entries

But Docker Hub lists the image (rook/ceph:v1.1.2) as built for both amd64 and arm64 architectures. I thought aarch64 and arm64 meant the same thing, with userland calling the architecture aarch64 and kernel calling it arm64. Is that not true? How are these names related to linux/arm/v8?

If this machine pulled an arm64 image, would it be able to run it? Maybe my Docker is just misconfigured so it doesn't recognize what it can run.

SBC:    Rockpro64 v2.1 4Gb
OS:     ubuntu 18.04 minimal w / Mate' DE     
        Linux rockpro64 4.4.190-1233-rockchip-ayufan-gd3f1be0ed310 #1 SMP Wed Aug 28 08:59:34 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

While performing an apt update && apt upgrade, the following messages occur:

W: http://ppa.launchpad.net/ayufan/rock64-0.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ports.ubuntu.com/ubuntu-ports/dis.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ppa.launchpad.net/ayufan/rock64-0.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ports.ubuntu.com/ubuntu-ports/dis.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://ports.ubuntu.com/ubuntu-ports/dis.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.
W: http://deb.ayufan.eu/orgs/ayufan-rock64/.../InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ayufan.key.chroot.gpg are ignored as the file has an unsupported filetype.

Any explainations? Concerns?

TIA,
/Faradn
~ Rockpro64 ~ Odroid N2 ~ Odroid XU4 ~ Pi 3B ~