My PINE64 2GB+ Board is coming today, should have added the wifi mod but still excited!

I am curious about what the purpose of the LED next to the charge LED on the board is. On the pin-out diagram of the expansion connector it is identified as System LED.

I finally got android to boot it runs OK though the launcher crashes a lot, the major problem is the download speed through the ethernet port, it took an hour to download the youtube app (18mb) from the play store, I have a 75meg connection and all my other devices connected to the router are running fine? Anyone else having this problem? Any ideas?

Sent from my SM-G925F using Tapatalk

Hi, i just installed android 5 on a pineA64+ 1GB, and it works but daim it's so slow and not reactive, it freeze every time i try do something it took like 1 minute to open the parameters and then it crashed when i tried to open the "about device"section. I suggest it's the microSD that is daim slow (8MB/s write and 16 Read) but seriously even with a slow sd card it should not be this laggy and unstable, am i the only one?

Here is a Google Drive image anyone can download for Ubuntu with desktop environment.

https://drive.google.com/open?id=0BwrRh39nVNPsZE1TTjZ2R0ZhZ0U

Software installed:

Ubuntu Software portal
LibreOffice Suite
Gimp
Midori web browser
Geary email
VLC
Plank
and several others.

You can flash this in linux using all the regular methods or you can use Win32 Disk Image software or something simular.

Gparted is installed and allows you to re-size the rootfs partition to the rest of your drive if it is bigger than an 8GB drive. (I will have video on doing this and renaming and changing password for the Admin User.

I have 2 users already on the image

First user has plank installed and looks simular to a Mac or Elementary OS style look. 

Second user is more of a windows base look for desktop. Chose which ever suites you and delete the other.

User Name: Ubuntu
Password: ubuntu

User Name: Ubuntu2
Password: ubuntu2

(edit Updated version coming soon.... Here is some of the things I have fixed and are now working more acceptable. )

https://youtu.be/Bgy8h8ED2VI 

All,

Just to give you a brief summary of what we plan for the openHAB distribution:

We want to use Debian as a Linux distro together with Docker and deploy the openHAB 2 Docker container to it.
As a JVM, it will include OracleJDK 1.8 to have best stability and performance.

It should be noted that openHAB 2 is not yet final and as such there can be bugs and there is a very quick evolution of the code base.
Nonetheless, with all the new features that openHAB 2 brings, I am convinced that this is the better choice. I am planning to release a beta3 by end of April, which will then be the version for a first SD card image for the Pine64.

Best regards,
Kai

Anyone else with the 2GB module experiencing issues with an endless boot loop whenever Ethernet is plugged in.  I am using a 5v 2amp DC power supply and everything works fine until I plug in ethernet.  I also tried Remix OS / Android Lollipop with the exact same symptoms.  Any help is appreciated as I would be disappointed if I am unable to use the full potential of the board

OK got it to boot now into Remix OS but all the menu bars and that are on the outside of the TV edge. I have managed to right click and get display settings but there is no option to change resolution, refresh rate etc . How can I get it to change those now ?

I know this will work with USA customers, other countries may have similar systems but i'm not sure.

Sign up for a MyUSPS here. If you get past the long (but thorough) signup process, you should be able to get text or email alerts for any package coming to your address, no tracking number required. This way, you won't have to rely on Backerkit or the overloaded Pine64 team to give you your tracking number, you can just get a notification straight from the mail carrier.

I've signed up, and i've got it showing a couple eBay orders i have coming in, but no Pine shipment (yet!) Hope this helps someone. You may see that your Pine is already on its way!

The order of the reasons is not intentional, it's just the order things come to my mind based on Forum posts:

1. The official Android and RemixOS images can't be burned the usual way to an SD card (dd, Rufus, WinDiskimager) but need Phoenix Card instead (Windows only and causing all sorts of troubles for users that do not use this strange operating system). Burning an Android image the wrong way will result in the Pine64 waiting endlessly while showing already a red led lighting. PhoenixCard images can only be burned with the PhoenixCard software. DD images can be burned using the dd command (Linux/Mac) Rufus, Win32DiskImager (Windows), Etcher, ApplePi Baker (Mac). Attempting to burn a DD image in PhoenixCard will result in a 'script not found' error. Likewise attempting to burn a PhoenixCard image with one of the above-named DD processes/applications will not work either.
   
2. Data written to SD card got corrupted either because you unfortunately bought a counterfeit SD card or the card is faulty. Another common problem are SD card readers that start to overheat when used with a fast card and corrupt data 'on the fly'. Checking for both problems is simple: Never use any flash based media without verifying it before.
   
3. Insufficient power supply: unfortunately Pine64 uses Micro USB for DC-IN, many USB cables have a resistance way to high (leading to severe voltage drops) and this combined with crappy PSUs (the old phone charger you found in the drawer) will lead to the Pine64 crashing in early boot stage
   
4. HDMI issues: You connected a screen but Pine64 and display disagree about settings (no idea whether EDID is implemented in Allwinner's 3.10.x Android kernel that is currently also used for all available Linux images)
   
5. The Pine64 boots fine but you don't notice still staring at the red led indicating 'error'
   
6. You use either the RemixOS or an Android image and have Ethernet connected at first boot. This will prevent the board from doing so, so please consider disconnecting Ethernet after burning an Android/RemixOS image and only connect it back when you already see the desktop.
   

• pre-production samples were equipped with a green led, the production batch replaced this with a red led. So red doesn't indicate failure but 'power available' instead. Unfortunately you get no other feedback whether the Pine64 actually boots or not. The red led will light even if the A64 waits patiently for a bootable OS available on a SD card an hour or endlessly.
  
• combining 'smart USB chargers' with devices that are 'dumb' on the other end of the cable might not work: If you use a 'charging hub' to power your Pine64 then chances are pretty high that the charger only provides 500mA (max. current defined by USB2.0 specs) which might be not enough to allow the Pine64 to boot (5.1V/2A!). Most 'smart chargers' will only provide more than 500mA if the device in question implements any of the USB power specifications (Pine64 implements none of them since it's just DC-IN)
  
• 2GB boards suffer from crashing or rebooting loops when Ethernet is connected since there's a integer overflow present in older kernel variants. Fixed by longsleep in early April, so Linux images can be updated using the instructions from "Linux Development" forum an a new RemixOS release should fix this also.