Hi guys im wondering if the Raspberry pi 2 camera will work on the CSI port and work with android as i was thinking of getting the camera

IF it doesnt does the Pine A64 camera fit into the touch screen frame as i noticed thers a slot for a camera in the touch screen

Hello guys,
Before I'll buy Pine 64 I need to know if Horizon GO (from Liberty Global) is working on it.
Because some newer chips from Amlogic isn't supported by that app it shows error 6667.

I'am selling my Pine A64+ 2gb with plexi case and original adapter for sale in the Netherlands
 
I live in the netherlands so I prefer a dutch buyer.

Voor die dutch buyer.
Verzendkosten 8,50 
Je kan ook langskomen hij draait nu remix os als je hem werkend wilt zien.

http://link.marktplaats.nl/m1055065359

Hi, I ordered the pine64 512 mb version. I received my order and proceeded to download debian, the initial boot went flawlessly. But, I cant seam to get Wi-Fi to work AT ALL. I purchased the add-on "on board" Wi-Fi chip from the pine64 kickstarter page. And now that I have it booted up and all I can't even find how I am supposed to access Wi-Fi on the pine64 . Please help. Thank you in advance for any help ya'll can provide.

Just want to report my small success (thanks to the ubuntu kernel updates from longsleep)

I got a MIDI Sprout connected to pine64, fully functional.
https://www.kickstarter.com/projects/dat...ion-device

Which is better to run Kodi,Android or Remix OS?

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.