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?
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?
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.
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.
Hi,
I got my Pine A64+ 1GB with a Wi-Fi add on card. I bought an INR 300 worth duplicate Samsung power adapter rated 5V 2.0A. I also bought an 8GB Sandisk Micro SD Card Class 4.
I am having following issues:
1. The default image for an 8GB SD Card on the Pine64 downloads link is not getting written on the SD Card. I tried with Win32 Disk Writer tool and it kept saying that the image size is more than the SD Card size. The SD Card when formatted under Windows 7 shows usable space of 7.2 GB. I then had to use the Phoenix Image and used the Phoenix Card utility to do the Android 5.1 image burn. It was successful. Kindly clarify why it didnt work the normal way ?
2. After the first boot into Android the board, I configured my Wi-Fi and connected to the internet. I connected a wired mouse and keyboard. Downloaded Youtube. As soon I clicked to play the YouTube app the screen went blank. The HDMI signal for still there but nothing was happening. I re-booted the device by powering off and on. This time it showed me a message that Android apps are being optimized during boot. Few minuted after the boot the device turned off automatically. No mouse or keyboard was connected. I re-did the SD card with a fresh Android image but now I am having random screen going blank or the power LED itself going off after few minutes into the boot. I touched and realized that the chips on the board were very hot.
Kindly provide me inputs in solving this, as I am already considering this as a failed investment. Also can you give details of the adapter that you are using Make, Model, Link to Buy and Price in India/Mumbai. This may be a power issue, but I am not sure.
Please help. PS: It was dumb of me to buy the 1GB version, since later while searching the images I read that the Remix OS is suited for the 2GB version and will lag in performance on the 1GB model. Damn shame. Also attaching the image of the power supply being used. It doesn't have option to change cables.
I have such a issue. I have pine64+ with 2GB DRAM memory. I download Debian Mate (3.10.102 BSP 2) image from pine64.pro site and flashed it on my SD card. Everything boots up fine and I can login into OS. However, when I want to mount root fs via NFS protocol it does not work correctly.
For NFS root fs mounting, I created boot script (boot.scr kept in mmcblk0p1 boot partition) which is required ,otherwise u-boot sets default environment which mounts root fs from mmcblk0p2. boot environment (bootargs) I set and saved to uboot.env also stored in boot partition.
From boot progress I can see that booting process reads bootargs, I can also see 5 attempts to wait for root /dev/nfs what is set in my bootargs which countdown. I can also see ethernet interface activation. However, the kernel always mount root fs from SD card.
What is the problem? I have installed and activated nfs kernel server on my host workstation, configured /etc/exports config files for accepting requests from NFS client (development board). I even checked syslog on my workstation if there is some activity for NFS dedicated daemons and service, even traced xinetd whether it is activated. But nothing, any activity?
What can be wrong please?
Thank you very much for your help in advance Martin
Is there a way to connect only a microphone (not a headset) to the pine and keep the audio output directed to HDMI on android?
This would be nice to be able to use Ok google and other voice commands. If I connect a microphone on the audio jack, it thinks that a headset is connected and present no audio output.
Hello,everyone. I am looking forward to using Pine64 for a virtual machine host. And I have some questions about the kernel config.
1. The config CONFIG_ANDROID is set to y. Will it have problems for ordinary users (uid !=0) on networking? Or any user can use tools like ping/netstat/nslookup and bind to a port?
2. The namespace config is not complete in the config file. It is described in a systemd-nspawn document that
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
should be set. Will it be possible to add these lines?
Thanks.
Martin