You probably read about this problem several times. But i wanted to share with you what i could find out.

I got the 2GB Model of the Pine and I am using the Rooted Android 5.1.1 Image Release 20160428 [BETA]
I DON'T have the WiFi/Bluetooth Module.


After several tries of failure i decided to make a new clean installation and proceeded as follows:

- Install the Image
- Boot up the Pine with only the Power and HDMI connected
- Unplug the power after 10 minutes without doing anything else
- Wait another 10 minutes and hook up the Ethernet Cable and the Mouse and Keyboard
- The displayed time at the top right switch from 4 o'clock to the accurate time at that moment like there was a connection to a timeserver
- No Ethernet connection what so ever and the RJ45 Jack was blinking continiously
- The Pine is registered in the DHCP/DNS Services on the router. I knew clearly which IP it was since it was the only Android via LAN not WiFi. Also i checked it cmd ping while it was plugged in and out so i am 100% sure that it was the correct device.
- During the ping i noticed that i had a LOT of packet drops, since it was directly connected to the router where the pinging computer was also connected with a distance of 4 Meter cable. So there shouldnt have been even a single drop and i had about 25%-50%
- This lead me to believe that the Ethernet module might be busy trying to broadcast or something. But Wireshark gave me nothing. The only things i could see where my Pings and the registration when i plugged in the Ethernet Cable


And now comes another interesting observation

- My brother has the exact same Pine with the exact same configuration and the exact same SD card... BUT... he has the WiFi/Bluetooth module. And on his Pine64 the Ethernet connection worked after some time and pluggin it in and out.
- Same thing happened to another user on the Pine64 Chat

My conclusion: Either they downloaded some updates for Android before (unknowlingly) and this got it to work somehow  OR the Pine64 tries to find the not exisiting Wifimodule, even if it's deactivated. Just askin if it's there to go on with the program and use the Ethernet connection and thus getting stuck on that request.

Tomorrow my brother will bring his WiFi module and i am going to check it out and give you my results. I hope to help some people out with a bit deeper insight.

Kind regards

Martin aka. Apicalis

Hi,
There is a region enclosed by silkscreen lines on the front side, and there are also several connectors on the lines.
Does anyone know what are those for?

Hi Guys, 
quick question surrounding the writing Remix OS to the SD card. I have successfully completed both using Win32 and phoenix card but my Pine 64 has yet to boot past the Pine64 opening screen. I just wondered how I could check the image has successfully been written to the SD card... I've ordered a power cable with the correct amps but just wanted to make sure I am actually writing the image correctly. 
Thanks,

Just to confirm that the Go programming language runs on the Pine64.  This was announced in the Go forum a few days ago:  https://groups.google.com/forum/#!topic/...mY7IKVMMyE.  The person who posted thate announcement is running it under Debian Linux.  I'm running it under Ubuntu Linux.

Just to expand on that posting, Go doesn't work on the Arm64 out of the box.  To get started you need to create an intermediate version of Go using another machine that already has Go running.  (I used an Intel-based system running Ubuntu.  You could also use a Windows system.)  Use these instructions:  https://golang.org/doc/install/source, in particular the section "Optional Environment Variables".  When you build your intermediate system, specify the arm64 as the target architecture using GOARCH and specify the target operating as linux using GOOS:

export GOARCH=arm64
export GOOS=linux

Use GOROOT_FINAL to specify the location where you want the result to be stored on your Pine64. 

Once it's built, copy the resulting files onto your Pine64 and put the directory containing the go command into your path.  That gives you a working Go compiler.  For a quick test, run:

go version

which should display some information about the go compiler. That it runs at all is a good sign.

You could just use this version of the go compiler but it's nicer to download the source code of the Go system onto the Pine64 and compile it all over again.  The compilation process takes about ten minutes and gives you a Go system that was created from source on the Pine64.   It also acts as a fairly thorough check that the compiler is working OK.

You only need to go through that rigmarole once.  After that, when a new version of Go comes out, you can compile it from source code using your existing compiler.

The Go compiler will only work if it's stored in the directory that you specified using GOROOT_FINAL when you built it - you can't move it around later.  It's a very good idea to store the final version in /usr/local/go, so you may want to put the intermediate cross-compiled version somewhere else.

To find out more about Go, visit https://golang.org.  (There again, if you don't already know about Go, you are probably not reading this posting.)

Happy Going.

Simon

i ordered my pine on Feb 29th.  11 days ago received a email like this and  nothing has shipped according to the tracking number.  Is this anther thing where its vaporware?  I sent an email to both support and shipping email addresses and have not heard anything.

Great news! Your PINE64 is on its way!

Courier: USPS

Your tracking number is: xxxxxxxxx

Shipping Address:
xxxxxx
xxxxxx
xxxxxx

Line Items:
  1x PINE64 A64+ for $39.00 each
    2GB ($29)-Yes (+$10)

My 2GB A64+ arrived today, and after trying and failing to get the Phoenix image to work (it just sat at the "powered by Android" screen) I tried the rooted 32GB Android image and successfully got to the desktop. I'm using a standard 64GB SanDisk Ultra UHS-I card (Win32DiskImager claimed the 64GB image would not fit on it) and am pretty sure it's genuine. I have wireless USB receivers for keyboard and mouse connected and nothing else, and it's powered by a 2 Amp Samsung adapter, so that should all be OK I think.

The system is unbelievably slow. Just navigating the settings screens takes ages as the app freezes or locks up repeatedly. My mouse freezes at times for a few seconds, then comes back. Chrome gave me a black screen with the "this app is not responding" message, but eventually loaded. After some persistence I was able to activate Wi-Fi and add my Google account, but I've tried several times now to start Google Play, each time it causes the device to restart (back to the Pine logo screen) after a long attempt to load.

I'm not sure if I have a faulty unit here, a faulty setup in some way, or if perhaps my expectations were too high? This certainly isn't a usable system, that's for sure, I can barely load an app. I'm downloading Remix instead now to see if that's any better, but really I bought this as Pine claimed to support Android.

Hi all, according the shop site the 1 gig model has 10/100 ethernet port, the wiki and the kickstarter show that it should be 10/100/1000 port.

I hope that's mistake because otherwise I'm gonna regret my backing on the kickstarter project

Is there a C#.NET / Mono GPIO library available?

Thanks,

Arthur

I've tried several apps from the Google Play Store that, supposedly, will automatically start apps you define on OS boot. But none of these seem to work.

Kodi on RemixOS was able to play a 1080p x265 HEVC without any noticeable stuttering or screen artifacts. So, I'm trying to get Kodi to auto start on OS boot in attempt to start using this as my media center and replace my Pi.

I have tried many times to instal different android builds to work with my pine and the pine touch screen I have, and none have worked or even booted up. I installed linux to make sure it wasn't the pine it self, but I was able to boot into and have full functionality. Am I going around the android process wrong? Or is my lcd touch screen faulty? I am using a mac and have downloaded the DD root image for a 64 gb card, and DD to the card, then plug the card into my pine with the lcd touchscreen attached.