Hello,
Does the Rock64 board boot when powered up?
I mean, when power is applied, does the board boot without pressing buttons or other manual intervention?

Regards,
  vicencb.

I'm using 4.4.132, because when I tried 4.4.154, dw-hdmi-i2s sound doesn't work correctly; it sounds like things play at 0.001x speed.

Anyway, I am aware that sdio0 is disabled because of pcie issues when both are enabled.
I want to be able to use the rockpro64 wifi module, and I have no need for the pcie slot.

If one disables pcie, could sdio0 be safely re-enabled?
I am great at compiling kernels, but not great at editing device tree files.

What are the edits to make to rk3399-rockpro64.dts to accomplish that (if it's safe) ?

I am working on writing some CPU, MEM, and file size monitoring functionality for the rock64 (Debian). I search the web and found this solution : stackoverflow information on monitoring. However, my coworker said that the value does not update the proc files. I am trying to replicate the issues, but would any of you have ideas?

Hi guys.

After multiple attempts to get a regular "tablet" Android version for Rock64 board I came across the ROC-RK3328-CC board from Libre computer which is very similar to Rock 64.

So I decided to create a hybrid rom using the Android 7.1.2 from Rock64 and ROC-RK3328-CC. However before trying this I would like to hear your opinions if this will work.

Here are the suggested steps
1. Download the Android 7.1.2 rom for  ROC-RK3328-CC  from here
2. Open Android Tool Firmware tab and load the rom as shown in the image


3.Take the original Rock64 7.1.2 Rom (EMMC version) and unpack it using the 3rd tab in Android Tool


4. Go to the first tab and check the following options Loader, Parameters and Resources


5. Select the checked files from the output folder where we unpacked the original Rock64 rom

6. Just to make sure that we get no errors, disconnect the device, wait 30 sec, reconnect it in Maskrom mode

7. Press Run.


What are the chances that this will work?
Any suggestions?

Hello,

Doest ROCKPRO64 board consists of the RK3399Pro chip with NPU?

Thanks,
Suren

i build the Android source 8.1,but not succcess boot from sd card,anybody know why ??
i just want to run the sdcard boot image for rock64 board by build it myself by http://files.pine64.org/os/sdk/ROCK64/RO...8.1.tar.gz source code.
rock64 img from (http://wiki.pine64.org/index.php/ROCK64_...d_8.x_eMMC) this is ok,
but why myself build is not work

any guy know why?
how  should i do , or change something?

I have a rock64  board(mem  1g),and i have download the ROCK64 Android Oreo ver8.1 SDK from link http://files.pine64.org/os/sdk/ROCK64/RO...8.1.tar.gz.
i have setup the android build environment for ubuntu16.04.1 LTS desktop,and build the source success
source build.sh

and i get the image in rockdev/Image-rk3328_box
vps@ubuntu:~/rk3328v81_box$ uname -r
4.15.0-39-generic
vps@ubuntu:~/rk3328v81_box$ uname -a
Linux ubuntu 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24 17:09:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
vps@ubuntu:~/rk3328v81_box$ ls -al rockdev/Image-rk3328_box/
total 2727264
drwxrwxr-x 2 vps vps       4096 Nov 23 07:49 .
drwxrwxr-x 3 vps vps       4096 Nov 23 07:47 ..
-rwxrwxr-x 1 vps vps    1048576 May 15  2018 baseparameter.img
-rw-rw-r-- 1 vps vps    1491516 Nov 23 07:47 boot.img
-rw-rw-r-- 1 vps vps   18970644 Nov 23 02:44 kernel.img
-rw-rw-r-- 1 vps vps     162126 Nov 23 02:31 MiniLoaderAll.bin
-rwxrwxr-x 1 vps vps      49152 May 15  2018 misc.img
-rw-rw-r-- 1 vps vps     168060 Nov 23 07:49 oem.img
-rwxrwxr-x 1 vps vps        981 May 15  2018 parameter.txt
-rw-rw-r-- 1 vps vps      49152 May 15  2018 pcba_small_misc.img
-rw-rw-r-- 1 vps vps      49152 May 15  2018 pcba_whole_misc.img
-rw-rw-r-- 1 vps vps    9260688 Nov 23 07:47 recovery.img
-rw-rw-r-- 1 vps vps      95232 Nov 23 02:50 resource.img
-rw-rw-r-- 1 vps vps 1201701108 Nov 23 07:48 system.img
-rw-rw-r-- 1 vps vps    4194304 Nov 23 02:31 trust.img
-rw-rw-r-- 1 vps vps    4194304 Nov 23 02:31 uboot.img
-rw-rw-r-- 1 vps vps 1396378072 Nov 23 07:49 update.img
-rw-rw-r-- 1 vps vps  154861692 Nov 23 07:49 vendor.img

but when i flash the update.img to sd card,
Win32DiskImager or SD_Firmware_Tool.

the board could note boot success!

Hi,

I am very interested in an ARM based laptop that I can tinker with (bare metal, osdev, etc). However, my primary machines use a 4K and 3200x1800 display, so going back to 1366x768 would be quite painful. 

Is the next batch of 11” Pinebooks expected to have the 1080p screens?

I have been trying to understand the trackpad in the pinebook, and this is an attempt to document what I've observed.
The wiki has a link to a trackpad datasheet.
I've setup wireshark's USB capture and attempted to replicate the gestures in the datasheet to understand what's going on.

First, there the USB descriptor.  The trackpad identifies its self as a USB mouse consisting of 5 buttons and 4 axes.  That's a 5 byte USB HID report consisting of 1 byte of buttons, and 1 byte each of X, Y, Z, and W axes.
Button 1 ("left click") can be activated by single tap or depressing the bottom left corner (there's a physical switch).
Button 2 ("right click") can be activated by double tap or depressing the bottom right corner (again, physical switch).
X and Y axes are the usual single finger drag in X and/or Y axis of the trackpad.
Z axis is two-finger drag up or down.
W axis is two-finger drag left or right.

Pinch-zoom is an interesting case because it first generates a keyboard event of the left control button being depressed, followed by + or - Z axis mouse events, ending with a left control button up keyboard event.

3 and 4 finger taps generate a null mouse report (a report is generated with all buttons up, no movement on any axis).  Given the datasheet and the zoom behavior, I would have expected these to generate a keyboard report.  IMO, it would be nice if these were buttons 3 and 4.
3 finger drag appears to report the same as 1 finger drag (X and Y axes reported).  Given the datasheet, I would have expected these to generate combination keyboard/mouse events as well.

The trackpad does not appear to ever report both buttons being down simultaneously.  A button 1 down, button 2 down, should generate a usb report with both buttons down, then button up events as each is released.  However, that does not seem to be the case.  This seems to make 2 button emulation of a 3rd button not work.  This seems like a bug.

Despite the USB descriptor reporting 5 buttons, I could only ever activate 2.

Hi everybody.
I try to watch Netflix on Firefox or Chromium in Kde Neon but not work.
Netflix Code error: F701-1003
Is it DRM issue?
Can we fix it?
Thanks!!!
Sorry my english.

Hi everybody.
I try todo install Telegram Desktop un Kdeneon.
But not work. Dependecie errors.
Is It posible fixing.
Sorry my enghish.