I've got an email asking for a top up for FedEx shipping services.
I didn't see any info on this when I was making payment, so I'd like to confirm that that's the case and everyone is aware of this.

I just purchased a RockPro64 and eMMC module and am configuring it for the first time. Everything goes well with system installation and first boot, but upon running `reboot` command, the system does not come back online. Power LEDs stay lit, but the white LED stays off and there is no visual output or presence on the network.

I have tried a number of different distributions - Armbian Stretch and Bionic, Ayufan's Stretch and Bionic and OMV, mrfixit2001's Debian, DietPi. All have the same issue.

Have seen forum postings and GH issues dating back a few years, none of which with any resolution. Wondering if the board is faulty or if it has just remained an unresolved issue with all of these boards for the past few years.

Hi,
I am a noob here to the pines. Has anyone been able to install Android TV successfully on the pro board ? Anyone working on lineage OS instead of Android. I have this board on order to play with on a few projects. Spec look powerful. I cant wait for it to arrive. Thanks!

Is it possible to connect that classic usb wifi to rock64?
I see the Android 9 discovers the dongle (below) but wifi switch does not work under network configuration and there're no wlan interfaces. So this is another device not supported by that useless single board "computer" ?

08-01 19:28:56.603   402   530 D UsbHostManager: USB device attached: vidpid 0cf3:1002 mfg/product/ver/serial ATHER/USB2.0 W
LAN/1.06/12345 hasAudio/HID/Storage: false/false/false
08-01 19:28:56.530 32165 32200 W ServiceManagement: Waited one second for android.hardware.bluetooth@1.0::IBluetoothHci/defa
ult. Waiting another...
08-01 19:28:56.619   402   530 D UsbDeviceDescriptor:   1 configs
08-01 19:28:56.620   402   530 D UsbHostManager: Added device UsbDevice[mName=/dev/bus/usb/004/003,mVendorId=3315,mProductId
=4098,mClass=255,mSubclass=255,mProtocol=255,mManufacturerName=ATHER,mProductName=USB2.0 WLAN,mVersion=1.06,mSerialNumber=12
345,mConfigurations=[
08-01 19:28:56.620   402   530 D UsbHostManager: UsbConfiguration[mId=1,mName=null,mAttributes=128,mMaxPower=250,mInterfaces
=[
08-01 19:28:56.620   402   530 D UsbHostManager: UsbInterface[mId=0,mAlternateSetting=0,mName=null,mClass=255,mSubclass=0,mP
rotocol=0,mEndpoints=[
08-01 19:28:56.620   402   530 D UsbHostManager: UsbEndpoint[mAddress=1,mAttributes=2,mMaxPacketSize=512,mInterval=0]
08-01 19:28:56.620   402   530 D UsbHostManager: UsbEndpoint[mAddress=130,mAttributes=2,mMaxPacketSize=512,mInterval=0]
08-01 19:28:56.620   402   530 D UsbHostManager: UsbEndpoint[mAddress=131,mAttributes=3,mMaxPacketSize=64,mInterval=1]
08-01 19:28:56.620   402   530 D UsbHostManager: UsbEndpoint[mAddress=4,mAttributes=3,mMaxPacketSize=64,mInterval=1]]]]


rk3328_box:/ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
   inet6 ::1/128 scope host  
      valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
   link/ether 92:76:24:a3:13:52 brd ff:ff:ff:ff:ff:ff
   inet 192.168.8.126/24 brd 192.168.8.255 scope global eth0
      valid_lft forever preferred_lft forever
   inet6 2001:xxx/64 scope global temporary dynamic  
      valid_lft 520266sec preferred_lft 1266sec
   inet6 2001:xxx/64 scope global dynamic mngtmpaddr stable-privacy  
      valid_lft 2591995sec preferred_lft 604795sec
   inet6 fe80::67da:f400:a95b:cacc/64 scope link stable-privacy  
      valid_lft forever preferred_lft forever
3: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
   link/ipip 0.0.0.0 brd 0.0.0.0
4: ip6_vti0@NONE: <NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1
   link/tunnel6 :: brd ::
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
   link/sit 0.0.0.0 brd 0.0.0.0
6: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1
   link/tunnel6 :: brd ::

i got the android pie 9.0 SDK in the wiki pine64 web page
page link : https://wiki.pine64.org/index.php/PINE_H64_Main_Page

but i cann't compile it.
where do i get the compile manual?
or
how is it compile?

Has anyone tried splitting the output from the sata power cable https://store.pine64.org/?product=rockpr...ata-drives to use with 4 drives?

It's unclear to me whether the output is supposed to be 3A per module or 3A total (1.5A power module).

With drives that have low current startup like the barracuda 2.5" I feel like 3A would be plenty for 4 drives if it was 3A per module.

The one thing that I missed on my old Pinebook was the lack of a good communication application that integrates all the services like Hangouts, Facebook Messenger, Skype, Telegram, Discord, etc. into one application. Yes, I could open all those web services in a browser, but it is not convenient.

As I know, Franz and Rambox does not have Linux arm64 version. Is there something similar that run on Linux arm64?

Hello.
I need preempt-rt kernel but preempt-rt patches can applied only to stock kernels.
So i have downloaded 5.2 kernel applied the patches and compiled it on rockpro64(no crosscompiling).
How can i install the new kernel now ?

Greetings!

I saw a post a few days ago commenting that the preorder PBP's were being sold at-cost as a thank you to community members (or something to that effect).  This brought 2 questions to my mind:

1: Are you planning on raising the price of the PBP once you open it up to the general public?
2: If not, how is the Pine64 project sustained?  While I'm all for low prices, "don't be evil" philosophies, and philanthropic tendencies, I also recognize that you guys need to make SOME sort of money in order to sustain the project.  Where do those funds come from?