Will there be hardware acceleration possible? Pine64 still does not have proper support...

SADIE - Simple Android Download and Install Executable
====================================

SADIE is a script designed to make it painless and easy to install Android (specifically ayufan's A7.1 images) to a Rock64 board.

It does the all of the following for you:

- Installs all required utilities (if you are on a system with apt or dnf package manager)
- Downloads the Android image of your choosing
- Prepares image for use (unzip)
- Guides you through how to put your Rock64 into the required "Loader Mode"
- Flashes the image on to your Rock64

Github repo

Direct Download (Linux)

Windows version is in the works!


How to use:

1. Unzip the downloaded zip file from above.
2. Run this in a terminal: sudo chmod +x sadie.sh
3. Run SADIE and follow the instructions!

This is a short tutorial on tweaking SMplayer to perform at its optimum. You can expect smooth 1080p playback of most formats that VDPAU supports using these settings. 

Open SMplayer and press Ctrl+p 

Under general -> video 

• make sure to have vdpau as output driver 
  
• toggle Double Buffering 
  

• toggle Allow Framedrop
  
• Set treads for decoding to 4
  
• Set loop filter to enable
  

Dear all,
my order (Pinebook 14") has been stopped at customs in Russia (Moscow). Shipment option was FedEx.

Customs says that Sender's customs declaration doesn't conform to Russian customs regulations.

They say that there is no somewhat "product notification from Russain FSS".

Customs clearance and further shipment is not possible. The order will be returned to Sender.

Questions:

1. Please, tell me if it is possible to cancel the order and get money back. If it is possible, please tell me how much money I'll lost.
   
2. Please tell me if there is alternative way of shipment, such as mail forwarder.
   
   

1. Please, as soon as possible, inform all falks from Russia that no shipment via FedEx will reach the Recipient.
   
2. Dear Pine64.org officials! Please consult with Russian Customs office to solve the bureaucratic  problem.
   

Another question about something on the board. What does the recovery button do?

is paypal not accepting pine64 orders? it works except when a buy is attempted.

does anyone know if the ir receiver setup now on sale for the rock64 actually works?  has it even been tested? reason i ask is i have not read any mention of it in reference to rock64 and wonder if that old habit of pine64 in selling things before they have actually been tested is back. thanks.

   

The Rock64 uses a serial console with a baud rate of 1.5M !  This can be a challenge especially if you're used to the 115200 baud rate of the PineA64, or the RPi3. Some of the bridges ( cp2102, ch340g, pl2303hx ) will work at 1.5M but many will not (some ch340g, pl2303ta, cp2104).

In this post I am highlighting the PineA64 as a great serial console monitor for the Rock64, using a modified cat5 ethernet cable. In the pic above you can see the serial console cable plugged into the P-2 bus [brown-gnd pin(6), orange-Tx pin(8), and yellow-Rx pin(10)].  Also visible is the .95m transmission cable that I have been experimenting with:  the solid blue and brown wires are the Tx--Rx  Rx--Tx data lines, and the striped blue|brown are the ground returns;  the ground returns are tied together and each data line is twisted with its corresponding ground.  While this increases the capacitance of the transmission cable it is very quiet and still short enough that the cable is quite effective at 1.5M !

   

On the other end of the cable is my PineA64 desk machine cabled to the Rock64 on uart(3), /dev/ttyS3;  again the striped ground returns are tied to sold blue (ground) and the solid brown is tied to Tx, while the solid white is tied to Rx  ( see foreground of pic above ) .  I have found that most 'screen' implementations do not support 1.5M, although there is a debian patch to correct this. Minicom and 'cu' are the standard(s) that continue to work time and again, and in this case I am running minicom in a terminal as my serial console software. In addition to setting 1500000 baud rate (ctrl-A o e aaaaaa) I also set flow control OFF (both) and set line wrap (ctrl-A w) and set off cr (ctrl-A a) and set off local echo (ctrl-A e).  The terminal is quite stable and works very well even after being up for several days.

   

The pic above is my PineA64 desk which I have used as primary computer desk since last November.  Visible is the terminal running minicom over the uart(3) /dev/ttyS3 connected via the modified cat5 transmission cable to the Rock64 prototype board;  cased in the C4Labs Zebra case from Dustin!

The image is ayufan's  gnu+linux ubuntu minimal 0.2.1 running the python suite. Displayed is the AGM PI routine output (taken from "Projects in Scientific Computation" Crandall ; 1994  pp. 11-12) which shows 1010 digits of PI with accuracy of +|- (1) in the last two digits!  Typically the Rock64 will compute this result in an average time of about 460ms. 

Note:   I disassembled a standard cat5 ethernet cable for this project. The other two pairs (orange and green) were used for hook-up wire on my DSKY replica ca. 1967.  I discarded the sheath to make the cable liter and easier to manage around the crap on my desktop. Obviously if you can place the two units next to one another the cable is not necessary; on the other hand, if your lab is spread out across multiple desks (as mine is) this transmission cable is a serial data saver.

I see a discrepancy between the schematic, and the pin assignment pdf, not sure which one has the correct label

Schematic: http://files.pine64.org/doc/SOPINE-A64/S...er-0.9.pdf shows 

PIN 9: MIC2N
PIN 11: MIC2P

Pin assignment pdf: http://files.pine64.org/doc/SOPINE-A64/S...er-1.0.pdf

PIN 9: MIC2P
PIN 11: MIC2N

I am working right now on the basis that the schematic is correct and the pin assignment doc is incorrect; however, looking for clarification.

Hi, apologies if this has been answered somewhere but I couldn't find it otherwise.

How does one disable the onboard LEDs on the Pine64? I'd like to turn off the power LED, ethernet LED, and anything else that lights up after the system boots. There are various ways of doing this on other ARM boards but none of them appear to work on the Pine64. 

To be clear, I'm looking for a post-boot configuration option likely to be added to an /etc/rc.local script, or a pre-boot option passed as an option to the booting kernel. 

Something like this article describes for the RPi:
https://www.jeffgeerling.com/blogs/jeff-...spberry-pi

Thanks!