Hello all,

I am quite a bit frustrated. Just received my Pine64 and began to study how to put it to work. Got two different MicroSD card (16GB and 64GB) and downloaded the images of Android OS and Remix OS. But when I went to burn the images, the things started to get out of the tracks.
In both cards, and using different OS, I was not able to burn any of the images until now (after two days trying). In all cases the error that occurs is related to the size of the image, that does not match with the size of the card. I searched for help on the web and I found that it is possible to shrink the image file. But I must confess that its not something simple for newbies and for windows users, that it's my case. 
Can anyone help me with this issue? 

Sincerely

Hbtr

I can't help but notice that Debian images get updated with desktop of choice and utility packages, while it seems Ubuntu users install their own. I will admit a preference for Ubuntu (I suspect there are some firmware/ drivers that play better with my USB equipment), and while I can add my own desktop and Gparted and all that, It would certainly be handy to have all of that pre-installed...

Hello!
This is the first test version of the manual writing in two languages. If you have any comments and suggestions please send them to me by e-mail blademoon@yandex.ru. 
I sincerely hope that it will help you.

Attached Files

  Codeblocks.pdf (Size: 770.18 KB / Downloads: 793)

hello,
 i was doing some reading earlier today and found this site which generates sources lists for debian (also has a link to a site that does the same for ubuntu) and decided to post it for some who may find it useful.

https://debgen.simplylinux.ch/index.php

it work well for me.

Hi,

I have a class 10 4GB microSD card that I would like to use with pine 64 1GB RAM. However, on the downloads section I can only find ROMs for 8/16/32 GB cards. Can I create a 4GB ROM by myself? How?

Thanks

I received my board and LCD screen last week. All went great until I went to connect the LCD touch screen cable to the DC1 connection on the board, the grey locking bar was missing, a quick rummage into the waste bin to recover the packaging and there it was loose in the box. I tried to reinstall the bar but it just snapped in half when I tried to curve it enough to get the two ends located, I have tried holding the cable in with insulating tape, the first couple of times I did get a faint glow out of the screen if I put gentle pressure on the connection with my finger but get nothing now. Any idea's would be appreciated?

Hey guys,

Sorry if this question has been asked before, but for playing android games from the play store (angry birds, jet pack and the likes) is it better to use an air mouse or a bluetooth controller? I have neither so i was wondering which i should buy?

Thanks in advance,

How can i make straight boot without password and choose user ?
 ihave:
xubuntu-xenial-mate-20160528-longsleep-pine64-8GB

My PineA64 LCD and Android are officially mobile this morning, with this card-board home-brew mobile power enclosure 

   

The simple solution while waiting for the official "Play Box" is to mount our fabulous and famous tablet guts in the ready-made enclosure the LCD was shipped in !

The packing foam cradle and support feet were glued to the top of the box with SIG-Bond craft glue. The PineA64 board hangs from the top of the box from steel supports and screws, while the battery rests on the bottom of the box. Power and reset switches have easy access through a trap-door cut in the bottom of the box, with a scapulae blade. At the moment the LCD just rests gently in the foam cradle (which was made of the LCD packing materials).  The tablet is 22.86cm x 14.29cm x 4.45cm , and weighs 492g (including the battery).

   

The PineA64 board hangs from the lid of the card-board boxed enclosure from four steel posts and mounting screws. You can see the FFC connectors in this pic (above) as well the famous glow of our little red power LED. Great care and finesse must be used when installing the cables into the FFC connectors. Gently (and I mean VERY gently) lift up on the black bar, and insert the cable with the connector pads facing towards the board. Notice that the primary 30 pin connector has an extension which is supplied with the LCD (both the extension cable and the extender clips board, are very delicate and easily broken).  Use caution.

   

Fabulous... now I can have my PineA64 board with me on-the-go, fits great in my man bag... and you know what, it looks great too, right Emily ?

(Emily: right !)    

marcushh777

@Emily is a trademark of LordCanti; although, no relevance to any person living or dead may be presumed.  

I've been trying to build Android for several days now without success.  I can build the kernel and I can build Android. What I can't do is assemble an image that will boot.  Does anyone have a script that will assemble the parts into a DD image? Currently I am using the Allwinner pack command with PhoenixCard and that is not making an image that will boot. There is something wrong with the ext2 partitions. Kernel starts but user space fails.

Also - could the Pine64 people please take a new snapshot of their Android source and this time use tar.gz on it instead of zip so that it preserves the files permissions? I had to hunt around and find a hundred files and set +x back on them. Get rid of those zip files and replace them with tar.gz.

Building Android would be so much easier if we just has access to delta repositories that overlay ASOP.
Remember this thread: http://forum.pine64.org/showthread.php?tid=1188

Or push a working build up to www.gitlab.com (not GitHub). GitLab will accept repos the size of Android. Heck, just do this to get rid of the bandwidth load on your own servers. Or I can push it up once I have working build. I uploaded the RK3128 tree a while ago. https://gitlab.com/jonsmirl/fireprime

No one is going to work on this code if it is impossible to build it.