I've hooked up my 1gb 64 board to my Tv through a three way HDMI adapter and an Android OS card. When it boots I either get an "out of range" error from the TV or I get a huge grey image of an analogue clock. Any ideas?

Hi all, 
I have just received my 2GB board. I tried this OS as first. All great (wifi module, keyboard)!! I have a fluid interface of the system but when I start Kodi it lags. 
In particular I have a very low reactivity of the mouse (that works great outside Kodi)

Is it a known issue? Can I solve it?

Thank in advance

I've tried New Ubuntu ML-Anderal 4-20-16.img and the xubuntu-xenial-20160502-longsleep-pine64.img so far.  I'm going to try android-rooted-ver5.1.1-20160505-pine64 next. 

I don't see where the kernel even sees the module.  I assume there is something that has to be added into the install for this.

I am  noob, so I might be overlooking something.

I ordered a Pine64 A+ 2gb ram version with a 7 inch lcd, I would like to prepare by purchasing/scavenging materials for my case.
This left me with a few questions;
What formfactor is the lcd?(Flat with overhanging glass, short/long ribbon cable?) 
Does it have a front plate? 
How does it mount?
Are there screw holes already on the lcd?
 

A 3D model or some pictureswith dimensions would help a lot.

P.S. Got my tracking number today,hence the post, finally the wait is coming to an end ^o^

Hi,

I'm looking for a freeware IDE and some instructions on how to create a simple and basic image of my own.

I'd like to control the GPIO pins and maybe experiment a bit with some UART communication.

I'm a hardware engineering student and have a bit of experience with MCUs. I just got my PINE last week, but had no luck in finding a proper tutorial or guide on how to fully control all the of the cool PINE features.

I saw that it may be possible using an eclipse based platform for ARM devices called DS-5, but once installed it didn't offer anything more than a empty editor and no explanations.

Any advice at all would be great!

Thanks!

DietPi for Pine A64: Give your Pine A64 some lightweight justice.
http://DietPi.com

DietPi for Pine A64 is currently based on longsleeps's excellent simpleImage (U-boot + BSP kernel) with Debian Jessie (arm64) debootstrap (according to these instructions: https://wiki.debian.org/Arm64Port#Debootstrap_arm64 ).  The DietPi also make use of longsleep's u-boot and kernel update scripts to keep in sync with his ongoing development work.

As we still have some issues to iron out with Kodi and VNC and the kernel is still in development, DietPi for Pine A64 is currently in Alpha. Please report all bugs/issues on these forums or via a Git Ticket: https://github.com/Fourdee/DietPi/issues. 

ALPHA notes:

• DietPi will release updates and patches on a regular basis which can be applied by running dietpi-update. This will allow you to instantly patch your system without having to writing a new image each time.
  
• Kernel and U-Boot updates are automatically applied with dietpi-config and utilize longsleep's update scripts.
  
• All non-GPU related software appears fully functional in the DietPi-Software catalogue: http://dietpi.com/software. So server based installations should not experience any issues.
  

• Kodi: Not working at this time
  
• LXDE: Requires 16/24 bit to function (use 24bit for both LXDE and Kodi).
  
• BlueTooth: the bluetooth portion of the wifi/bluetooth board has not been tested yet.  This is on my ToDo list.
  

Attached Files

Thumbnail(s)
   

Hi.
I've needed to set it up so why not to write about it. 

Tested on Debian Linux Jessie with Mate GUI Image [20160508] by lenny.raposo with Longsleep kernel

0. ssh debian@pine64pro
1. sudo su -
2. apt-get install libjpeg8-dev imagemagick libv4l-dev cmake
3. git clone https://github.com/jacksonliam/mjpg-streamer
4. cd mjpg-streamer/mjpg-streamer-experimental
5. make
6. ./mjpg_streamer ./mjpg_streamer -o "output_http.so -w ./www" -i "input_uvc.so"

This needs to be run by root (for testing purpose). In other cases You can get: ERROR opening V4L interface: Permission denied.
To fix this You need to add  any other user You use (debian is there) to video group. You can do this like this: sudo usermod -a -G video  <username>
To make it work please logout and login.

I've come up with a 3D printable design for a case for the Pine64.
This case design has a bottom half with feet and with pegs that
stick up to match the mounting holes in the board.  The top half
has matching receptacles that fit over the pegs for tool-less
assembly.  Vent slots are provided top and bottom, and access
holes are cut out along the sides for electrical connections.
The one I had printed fits the board perfectly and looks sharp!


You can download the design, including an ".stl" file for immediate
printing and the OpenSCAD source code by going to:
"https://spideroak.com/browse/share/brf_public/Pine64_Case"
See the included "Readme" file for more information.

I hope folks find this useful.

Attached Files

Thumbnail(s)
   

Ok this is now my second thread about this and I still have no solution. I have tried everything on the forum to try to get this thing to boot and nothing works. So I tried to contact the official Support people, they then told me to come to the forum. WTF!!!  I have read more things and have spent well over the $15 this thing was supposed to cost and I still can't use it. All I want is to return this DOA board and get one that works. If anyone can help please let me know 

Thanks 
Matt

When the Android 05/05/2016 image was released, I downloaded and used a 16GB unrooted DD image on to my SD card with the hope that, I will then be able to do a OTA update of the future releases. But unfortunately, I had issues with my Play Store and decided to do a 'Factory reset' (Settings --> Backup and Reset --> Factory data reset) to resolve it.

The Playstore issue is now resolved, however upon reset it looks like I have got a rooted version with SuperSU installed and also I confirmed that it was a rooted by switching on the root explored in ES File explorer.

Can anyone see a reason on why this would have happened?