Are the two LEDs (white and red) that are connected to the RK805-1 out1 and out2 pins (which seem to be general purpose IO pins according to the data sheet) controllable from user space somehow? I have noticed that at least the u-boot-spi flash tool can blink the red LED and also at least one of the available images I tried turned off the red LED after successful boot. The image I am currently running leaves both LEDs turned on all the time.

Hi,

I've been following the news on the RockPro64, have you a date yet when we will be able to order?

Thanks Dazz

Greetings,


So, I am trying to add a RTC to the ROCK64 using the below (DS1307 RTC - I2C):
https://www.amazon.com/Raspberry-Pi-HAT-...ds=rtc+rpi, and using these instructions: https://www.raspberrypi.org/forums/viewt...hp?t=85683.

I seem to be missing the rtc-ds1307 module (I'm on Debian Stretch Mate Community). Is there a way to get this module without downloading and recompiling a new kernel?

Well, there's this thread by the moderator called Luke instructing how to boot Linux and "some" Android images from a USB device. The link to it is this: https://forum.pine64.org/showthread.php?tid=5610

I followed the instructions. I downloaded and burned ayufan's u-boot-flash-spi.img.xz image to my SD, waited for the Rock64 to start blinking, and then turned off to take the SD out. I then tried Pine64's own Android image AND Ayufan's TV version but none will boot off an externally powered HDD OR USB flash drive. The screen on my monitor doesn't even turn black or anything (no signal).

According to Luke's guide, I have to go to this link here: https://github.com/ayufan-rock64/ to check which images can be booted from SPI but I do not understand these hub pages at all. I've no idea where to even find a list of Android images that mention SPI.

I found this hub page titled "u-boot Android" or something but I have no clue what this page is even about: https://github.com/rock64-android/u-boot . I'm not Linux savvy to understand at all.

BTW, running Android through SD runs perfectly fine. But as we all know, SDs wear out -- especially for what I'll want to use the Rock64 for.

Hi another question I want to be able to power my rock64 by usb so I can plug direct into USB power supply. Will this adapter from store work or is there more to it? Also will 5v 2.4a be sufficient enough to power the rock64? Thanks.

https://www.pine64.org/?product=2-meters...ower-cable

Just picked up my Rock64-4GB from the mailbox and proceeded to boot up the latest Android OS.

When I plug it in, only the 2+1 LED lights come on and the display is dark.

The monitor(s) and television all do not detect a signal from the HDMI port of the unit.

Not much to the installation and cannot do too much without a display.

Is there a fix or is the board DOA? 

Hi There,

I have just received my Rock64 4GB board . I plan to use this as a OMV dedicated machine. Since this board will run headless using Ayufan's stable release of the OMV image which I plan to install on the 16GB eMMC module, I would like to have a 16x4 lcd screen to monitor basic status of the board. 

Would anyone know if the GPIO is enabled by default or would I need to install the RPi.GPIO python module? 

Any help or advise from the community would be greatly appreciated.

Hi what OS is dac from store compatible with? Can it work with android, LibreELEC etc or will I have to use volumio? Thanks. 

The Amazon Prime app just crashes and you can't play anything.
I see Beelink already released an update to fix it months ago for their RK3328 A1.
Any news?

Hello

I would like to use a touch screen I bought off aliexpress, but unfortunately, the input is rotated by 90 degrees. Rotating the image does not solve the issue - input rotates with it.
I have tried changing the build.props rotation to 90, but unfortunately it works just like regular rotation, input rotates as well.

In the android docs, I have found:

Quote:touch.orientationAware
Definition: touch.orientationAware = 0 | 1

Specifies whether the touch device should react to display orientation changes.

If the value is 1, touch positions reported by the touch device are rotated whenever the display orientation changes.

If the value is 0, touch positions reported by the touch device are immune to display orientation changes.

The default value is 1 if the device is a touch screen, 0 otherwise.