Hi there, 
I have an original Pine A64 (in fact I'm typing this from it) and I'm running the Android 7.1 community image, but at present I can only get it to work with an external display. (The LCD definately works as a android 5.1.1 (LCD Video Output) works fine.) 

Again according to the wiki, I should be able to use uEnv.txt to enable the LCD, however I cannot figure out where uEnv.txt is. I tried searching the file manager, but I couldn't see it. 
If someone could point me in the right direction, that would be great!

For the past few days I've been coding a webgui for the Rock64 based on Ayufan's stretch minimal image. Inspired in part by the rPi hostapd interface. 

Apart from common administration things, it also sets up wifi devices like the RTL8812AU to become wifi APs using HostAPD.

I've outlined how to do this on my github repository, or for those not able to, I've also put a complete router image on my website.

By default the wifi channel is 40, which is 802.11a/n/ac only and the ssid is Pine64.org and the password is "password", although this can all be changed in the webgui, using rock64/rock64 as the login credentials.

I'd like to get OpenVPN and TOR working and would welcome any help with this, as I'm a bit stumped on making this as easy as possible for people to get up and running without needing to setup key generation on client machines.

Hi, do anybody know when Pine H64 1Gb or Pine H64 2Gb will be available in stock?

Pine H64 1Gb "out of stock"
https://www.pine64.org/?product=pine-h64-1gb-board

Pine H64 2Gb "out of stock"
https://www.pine64.org/?product=pine-h64-2gb-board

This looks like an easy way to get some additional GPIOs and UART/I2C/SPI on a Pinebook (or any other laptop)...

https://www.cnx-software.com/2018/02/16/...-over-usb/

https://github.com/gschorcht/i2c-ch341-usb

Found a datasheet in English....

https://hannover.ccc.de/redmine/attachme...341DS1.pdf

There are also EEPROM programmers based on CH341:

https://github.com/setarcos/ch341prog

I managed to get a decent printout of the boot option document, but what I read is very confusing.
In booting from an sd card, a list of addresses and what goes where seems quite grossly at odds when totalled with a simple calculator.

For instance, the kernel image (I am assuming is vmlinux,) which in the version v4.14I.15-rt13 I just built, is 147871544 bytes, or 0x8D05738, and would extend quite some megabytes past the location that begins the file system image.

Do I have the wrong document, or what do I not understand?

Gene83

I just got my Rock 64, loaded ubuntu mate and it was working fine.  I was wanting to add storage (i boot from the micro sd).  I read a post that you could load u-boot onto a micro sd, put it into the Rock64, power it up, and wait for the lights to start blinking steadily.  Then you were to shut down, remove the sd card, and attached an ssd via usb.  I did so, but now it powers up and nothing whatsoever happens visually on the screen.  I tried loading the sd card with a fresh version of ubuntu mate and nothing happens.  I'm a total novice to this, but it seems that I've altered the firmware or something so that my machine won't work.  Can anyone help?  Can I restore the board to factory settings and pretend this never happened?  Have I ruined my board?

I've had my Rock64 4GB board about a week.  My primary use will be as an android TV box.  My problem is that my USB hard drive doesn't work when attached to any USB port.  

The drive is a western digital 3TB USB2.0 drive, model WDBAAU0030HBK.  It is externally powered and formatted in NTFS, so it shows up as 2TB.  
When I try to access it in ES explorer it says "Operation Failed".  It does not show up when I try to access it through VLC.  The drive works when attached to my windows PC, my smart TV and my Roku. 

I am using Android TV Image "android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img.gz"

Any suggestions are welcome, as this is one of the main reasons I bought the board, to play videos from my USB HD on my smart TV through the Rock64

How to get a loadable driver for the alpha RT3572?

I'm running jessie using the

  4.4.77-rockchip-ayufan-136

kernel.

It also has the

  linux-rock64-package

installed which I presume are the build tools.

I have an old alpha RT8187 I borrowed working

I write in nodejs exclusively and on RPI I use this library to control GPIOs
https://github.com/fivdi/pigpio
This module creates bindings to the excellent PIGPIO C library  here https://github.com/joan2937/pigpio
and with it and this i2c bus module https://github.com/fivdi/i2c-bus I can anything on the GPIO bus.

I am sure I can get the PIGPIO C library to compile but will it be compatible with the "Pi2" bus on the Pine64?
If so tada I can use my nodejs code directly from RPI to Pine64 without alteration (well except maybe for some pin number translations as pointed out in other posts????)

If PIGPIO C won't work the same dev has a library that uses EPOLL.
So the EPOLL C should compile but will it work with the PINE64 pi2 bus???
https://github.com/fivdi/epoll

I'd much rather use PIGPIO C library as I have discovered it's much more robust than the EPOLL

What are my options here? 
I understand I can just write sysfs calls directly in nodejs but I've discovered that's not very robust.
One thing I definitely do frequently on the Pi is use pins as interrupts and that is easy with PIGPIO or EPOLL.  As far as I understand if only using sysfs then you have to manually poll the pin state in your code continuously (in nodejs that would be setInterval) looking for a state change (which is really not robust at all).

Can I have the number of the sender, please? I am in China now, and I want to contact the sender, because the official website does not support sending it to China.