I've spent several hours looking through the forum here, but I cannot find any word, (official or not), on the status of the 8000mAh batteries some of us have ordered. My question is simple, have they started shipping yet? I haven't seen anyone in the forums here or on Kickstarter mention that they have received their batteries. My understanding, according to what I could find in the updates, was that the Pine64 Team had the batteries and had worked out a solution to shipping them to backers here in the U.S..

Anyone have an idea of this? I already received my 2GB board, RTC battery case, LCD touchscreen, and the wifi/BT module. I'm simply waiting on the 8000mAh battery and the PlayBox Enclosure, (which I already know won't come until around August).

I am having fun  playing around with the board currently, and as everyone else probably knows, only the one version of Android, (designed for the LCD screen), works on the board.

Thanks everyone.

Received email May 27 
    "Your order for PINE A64, First $15 64-Bit Single Board Super Computer has shipped!"

Backer ID: 14,220
Tracking number: LS913212737CN  - This is not valid an has never worked.

Where is my board?  

Howdy. Thanks in advance to everyone who has contributed time and effort to the software for these boards, I'm excited to see where things go from here.

Bought the pine to replace my clunky HTPC, which is going in a closet to become a media server. After much wailing and gnashing of teeth, I got Android running on an old 32GB micro SD card (interestingly, I bought a 64GB Class 10 SD card but it was slow as hell and apps kept crashing. the 32gb "slow" card works fine). Did all my testing and setup plugged into a brand new LG 27" IPS monitor direct to HDMI. Then I went to plug the Pine into my home theater system, Pine -> Receiver/HDMI Switcher -> 5 year old Philips plasma TV. 

No signal. Then tried directly to the TV, HDMI-HDMI. No signal.

I know the card is good and the board is good, because I'm able to use Android on the LG monitor. What do I need to do to get it working on the TV? I'm not trying to buy a new TV just to get this board working.

Hi Gents!

Just received my PineA64+ 2GB in the mail with its screen and successfully booted it up with the Android 5 image from the site (Android 5.1.1 Image (LCD Panel Video Output) Release 20160603 - Non-Rooted DD Image).  I read that Android 5 has native support for USB sound cards, however on the PineA64, it doesn't seem to detect anything when it's plugged in.  Is there something special I have to do with this?  Is the Pine build of Android missing some drivers or something?  Any help or a point in the right direction would be appreciated!

Many thanks

Hello,

These guys are doing SBC (single board computer) popularity surveys every year: http://hackerboards.com/2016-survey-of-o...endly-sbcs
Here are the results from the previous year: http://hackerboards.com/raspberry-pi-sta...bc-survey/

And this time the Pine64 board is also participating If you managed to already receive your board and like it so far, please don't forget to vote for it here: https://www.surveymonkey.com/r/6DW7XC5

Hello folks,
I have one idea but I do not know if it can be done:
I have a tablet brand Prestigio PMP3270B.
It case is broken but still working 7" display and battery in good condition.
So my question is:

1. Can I use it display to connect to Pine64+ and/or what I need in order to make it fully functional on my upcoming Pine64+ ?
2. Can I use it battery to conenct to my Pine64+ also ?

Any suggestion is welcome.

Regards,

I have a 10 speed SD card 32gig.  I went to the Pine Wiki and tried to download the 32G version of remix.  That file appears to be larger than the usable space on a 32G card.  Should I therefor try the 16G version?  What is going on here, what good is a 32G memory card that is already filled with 32G of stuff?  Ofcourse I can download the file to my hard drive, though for some reason it isn't too thrilled with that process either.  Why is the image needed so big?  I thought android was an efficient OS?  If it is just mapping the card for 32 gigs worth, why is the file to do that so large?

I haven't installed software as an image file before, I guess I will google that to see what it means, but so far it seems like a far larger pain than the good old days of feeding in 12 floppies.  The file is slow to download, requires a 50 dollar program to uzip. is slow to unzip, and requires another program to burn the image.  Selling pre burned cards as raspberry did might have been ab additional income stream and saved a lot of time for the developers.

I am keeping in mind this is the Remix OS, not the Pine 64.  Have the hardware all ready to go, but the software is a pain.  And I haven't even run into the bugs phase yet.

One suggestion, use powered USB Hubs to connect external hard disks, if your external hard disk is USB powered of course...

I have a Seagate 1TB 2.5" external USB harddisk. It was very unreliable untill I used a powered USB hub, now I have no problem.

Same problem I had on the Raspberry Pi, same solution.

I am using xubuntu-xenial-mate-20160528-longsleep-pine64-8GB.
How to enable XDMCP remote connections on the Pine64? 

thanks!

I downloaded the ubuntu image from the downloads page for the pine64 (2gb ram version), and when I go to extract the iso file from the .rar download onto the sd card, I keep getting a error message, which basically says "the file 'xubuntu-xenial etc etc etc' is too large for the destination file system." I have absolutely no idea as to why I'm getting this message - I've re-formatted the sd card multiple times as a FAT32 file system, and as far as I know, the largest file size supported by that system is 4GB. The ubuntu iso is roughly 1.8gb, hence my confusion  .

I also haven't used any type of drive formatting program; I just right-clicked on the microSD card, hit format, and all of that jazz, so it could be that.
This may be some trivial fix that just slipped my mind, but any help is appreciated.

As a side note, when I try to open/mount the iso I get a message saying that it is corrupted and cannot be viewed, don't know if that has anything to do with this though.