Looks like there is a good possibility of more/better video player supports coming. the FFmpeg video library of which almost all video players use for decoding (including kodi,vlc,RKMC etc) has just recently added support for the Rockchip Media Process Platform. So that should mean it should be able to use the MPP for hardware decoding support by default as long the ffmpeg library is compiled with the support enabled.

Congrats to LongChair for his hard work in getting it added!!

Does the Rock64 have the connection for the LCD? I didn't see a place for it in the product page.

Hi,

I'm working on a Rock64 NAS project, now I want to know which USB to SATA cable I can use best?

Thx in advance

So Pine64 Support had promised me a replacement for the faulty Pinebook keyboard.

Many weeks ago, they assured me a new bottom case with keys and connectors would be shipped "soon".

Yesterday the postman thrust into my hands a large very well packaged item from China.

Surprising, as I hadn't received any tracking details by email - so I wasn't even expecting the parcel yet.

The label on the outside stated "From vickyzhu, Pine64" and declared the contents to be "Pinebook keybook [sic] with bottom case".

I very, very carefully opened the padded parcel and found a hardened plastic case just like the complete Pinebooks themselves ship in.

Inside that was another padded parcel in which there was ....

A top case LCD panel!

Nice, but not what was required for a faulty keyboard replacement!

Anyone else experienced this?

Pine64 Support have so far not responded.

• artful-minimal-rock64-0.5.10-118-arm64.img.xz
  
  
• [/url][url=https://github.com/ayufan-rock64/linux-build/releases/download/0.5.10/artful-minimal-rock64-0.5.10-118-armhf.img.xz]artful-minimal-rock64-0.5.10-118-armhf.img.xz
  

I have a P2Gb Pine, but havent been able to boot it up yet. 
I have tried different images ( Armbian, Android 5 and 7) on different SD cards ( all SanDisk Ultra 16Gb).
Power supply is 5.1V with 2.5A.
The green led lights up when power is on but nothing else happens. 
Hopped up Serial/UART converter and the log I get is the following:

HELLO! BOOT0 is starting!
boot0 commit : 045061a8bb2580cb3fa02e301f52a015040c158f

boot0 version : 4.0.0
set pll start
set pll end
rtc[0] value = 0x00000000
rtc[1] value = 0x00000000
rtc[2] value = 0x00000000
rtc[3] value = 0x00000000
rtc[4] value = 0x00000000
rtc[5] value = 0x00000000
DRAM driver version: V1.1
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1500 mv
DRAM Type = 3 (2DR2,3DR3,6:LPDDR2,7:LPDDR3)
DRAM clk = 672 MHz
DRAM zq value: 003b3bdd
DRAM error status 0
DRAM init error!
initializing SDRAM Fail.


Just wondering if there is something I can do or is this a faulty board.

Ive seen some other posts with pretty much the same symptoms and the same log but havent seen any answers or what has solved the problem. 
Ive also put in a ticket with Pine but havent heard back from them. 
Starting to be a bit disappointed , not with the board so much, mistakes happen and faulty boards do get sent out even with the best manufacturers, but more so with the client relations and help availabe for the board. 

If anyone could point me to the right direction of what could be wrong, Id be very grateful.

/proc/version

Linux version 4.4.77-rockchip-ayufan-118 (root@e4248ef129ba) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #1 SMP Thu Sep 14 21:59:24 UTC 2017

Sort of looks very much like debian but seems to just freeze as a desktop.
Anyone else tried it?

I've a ROCK64 4 GB, but didn't order the WiFi adapter from Pine64 website assuming that I'll use my existing WiFi adapter. 

I'm using this build android-7.1-rock-64-rock64_atv-v0.3.4-r86-update.zip

I tried using the following, but none of them worked:

1. Edimax EW-7811UN
   
2. Edimax EW-7811UTC
   
3. Belkins N150
   
4. Netgear A6200
   

I have a ROCK64 4 GB Model with 64 GB eMMC

I installed the android-7.1-rock-64-rock64_atv-v0.3.4-r86-update.zip using Android Tool from a Windows machine.

I'm using a 128 GB USB 3.0 Flash drive connected to the USB 3.0 port but it doesn't seem to detect the flash drive.

I started experimenting with other android images using 64 GB micro SD and one version recognized the disk, but want to reformat to be able use the same.

Has anyone tried connecting a USB 3 flash drive and had this working? Please help

Can't seem to get by this problem on Linux Xenial Mate 104 build. Have had problems on others too. Hoping some Linux experts can point me in the right direction.
1. Etcher image to SD (Samsung EVO Plus 32GB).
2. Boot in Rock64. No changes to the build.
3. Firefox - click icon.
4. Sorry - Firefox has a problem, quit or send message to Mozilla.
5. Applications - Internet - Chromium Browser
6. "Oh snap" window displays. No browsing for you.
7. Terminal - ping google.com, ping pine64.org, ping yahoo.com, ping my router, ping 8.8.8.8, ping 8.8.4.4 - all work till the cows come home.
8. Terminal - apt-get install midori.
9. Terminal - midori - can browse per usual.
10. Run the Firefox and Chromium browsers from the terminal - same error messages but lots of terminal messages. Here they are;

rock64@rock64:~$ chromium-browser
[3638:3695:0926/155950.439223:ERROR:zygote_host_impl_linux.cc(254)] Failed to adjust OOM score of renderer with pid 3754: Permission denied
chromium-browser --type=renderer --disable-low-res-tiling --disable-smooth-scrolling --enable-pinch --profiler-timing=0 --disable-composited-antialiasing --enable-low-end-device-mode --field-trial-handle=5542932056560533048,11580150603792406925,131072 --service-pipe-token=87FCC150BA3552182A1880C4D31CB7BA --lang=en-US --instant-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=4 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553 --disable-accelerated-video-decode --disable-gpu-compositing --enable-gpu-async-worker-context --service-request-channel-token=87FCC150BA3552182A1880C4D31CB7BA --renderer-client-id=3 --shared-files=v8_natives_data:100,v8_snapshot_data:101: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed.
rock64@rock64:~$ 

rock64@rock64:~$ firefox
ExceptionHandler::GenerateDump cloned child 3973
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
rock64@rock64:~$