is there some library for pine64 like what Rpi has where you can read and write information to the io ports?  I believe there is I just couldn't find it.

Anyone got any tips for running a precompiled 32 bit app in 64bit environment?  Basically I can get it to install but it does  not see the file as a exectuable.  I have a feeling I am missing some libraries or something but can't seem to get any headway.  The app in question is Repetier Server https://www.repetier-server.com/.  I have been in contact with the developer and tried a few suggestions he had but no go.  Final suggestion was to run kvm but I cant imagine that would be very efficient.

You don't need a 18GB tarball for Android source. That is a truly awful way to distribute Android source code.

Odroid-C2 is a good example of an Android repository done right.

http://odroid.com/dokuwiki/doku.php?id=e...ng_android

NanoPi Android build is similar
http://wiki.friendlyarm.com/wiki/index.p...le_Android

The basic idea.... get the core Android source code from Google's servers using the repo tool. That will be 95% of the code. Then you make up another set of repositories with your A64 specific changes.  Those repositories will be small and will easily fit on Github where you can store them for free.  


I am not sure yet what was done in the 18GB dump. It looks like some use of the repo tool was made, but this is definitely not the right way to do it. You guys need to get this sorted out, it is very difficult to split this tarball back into repositories belonging to Google, Allwinner and Pine64.

When you get this setup right you will only need to do this....

mkdir android && cd android
repo init -u https://github.com/pine64/android_manifest.git -b pin64-lollipop
repo sync

The repo sync tool will download all of the source code, 95% will come from Google's servers and the rest will come from Github. 

Is Allwinner using the repo tool or are they dumping a tarball to you?

This is the key bit...

 <remote  name="aosp"
          fetch="https://android.googlesource.com" />

 <remote  name="origin"
          fetch="."
          revision="refs/heads/s5p4418-lollipop-mr1" />

 <default revision="refs/tags/android-5.1.1_r6"
          remote="aosp"
          sync-j="4" />

See how it is fetching most of the code from the public AOSP servers?

You have this, which must be some internal git server.

  <remote  name="exdroid"
           fetch="/git_repo/A64/5.1/android" />
  <default revision="develop"
           remote="exdroid"
           sync-j="4" />

So I've got a functional Android build already working, but I'd like to try a few different things as well.  I'd like to give Remix a shot, as well as some of the other images people have posted like TV64.  Rather than re-write my SD card each time, I was thinking of getting a few cards, and each one having different OS so I could swap between them .  I'm mainly wondering about size though.  I know that storage space is needed in addition to any OS images, but not sure how much.  Basically looking for advice on if I should buy 8GB cards, 32GB, or or go up to 64GB.  Obviously, there is a cost difference between these cards, which is why I'm asking for opinions on what size I really need.  Thanks for the input.

about twenty minutes ago.

I am backer #1238.

I had order the playbox kit with the LCD screen.  I added on an extra Pine64, both are 2gb.

Was promised late May and it is.

Can't wait for delivery.

I used Ubuntu for about one month. I was interested in learning Linux basics and have a Linux machine in my house. At this moment, playing a video on Ubuntu is difficult, as of lack of GPU support. Hardware acceleration helped, but not so much.
I am going to move on Android to use it as a MediaCenter and surf the net (using Ethernet). Before formatting my microSD, I ask you:"Is Android the real good choice to watch videos (from a USB key)? Are there issues with Ethernet connection?"
Thanks for your help.
P.S.: I saw a video of someone playing N64 games on Pine with Android: it could be really cool

Cancel my complete order #8161801.  Due to long led time before shipping, I have made other arrangements.  Do not build my order, do not charge my CC.  Please send cancellation confirmation to my e-mail on file.

Got my 2 x 2GB Pine 64 and 7" LCD on Tuesday (backer 31,000ish) - I've got Debian XFCE running over HDMI on one of them successfully. 

But - main question - I don't want to run Android to get touch-screen LCD support - I want to run "native" Linux.  

And from what I can see - the only way to use the Pine supplied LCD touchpanel is to run the Android image built for the touchscreen?  And I'm guessing it defaults to portrait (another thread somewhere else suggests the next build will include a DD image and rotate screen 180 degrees - thread was from last week, and it said "next week" - but haven't seen a new image for Android 5.1 touchscreen on the downloads via the wiki page)...
---------------------------------------------
Here : http://forum.pine64.org/showthread.php?t...5#pid10025

Lazy as I am, I started thinking about a way to power up the Pine from the comfort of my couch instead of getting up and pressing the power button.

And I got a solution! (A theoretical atleast, until I get all needed hardware)

I´m going to use a Wemos D1 Mini with its Relay shield.

And that is controlled via wifi with the Blynk app from my smartphone.

I can post some pictures when I got it working

Hi,
I've got my pine64 with 2G RAM , together with lcd. I can boot successfully with android img for lcd version, and it worked well. But it failed with Ubuntu img. The lcd doesn't light up. So I 'd like to know if the Ubuntu img support the lcd or if somebody would add the lcd driver?