So I finally fixed my computer problems so I could burn the image. So now my LCD touch pad turns on when I plug it it. But the screen is blank. Does that mean one of the ribbons isn't hooked up right? If so which one? or is it a different problem?


Edit::So I unhooked all the cables and rehooked them and I am getting the same results. Thoughts?

Hello,
I want to add GPIO support to android, so I have to rebuild the kernel with appropriate config. As the whole android image takes a long time to build/copy to sdcard I plan to only recompile the kernel but I don't find the zImage/ramdisk within the 12 (seriously?) partitions, actually most of them are not even mountable (wrong fs type).
So where is the kernel image stored ?
Thanks

Now as I am able to test (I "forgot" to buy a remote and still the case was missing)... I have on questioN.

I have Android 5.1.1. running with an alternative TV start page...

Runs well, but how can I sent the PINE64 with Android into a standby mode?

If using the original PINE64 Remote and press the "off" button, the system shuts down. And no way to restart it using the remote, nor by clicking on my hardware power-button.
I need to unplug und replug the power cord.. and then the whole system is rebooting.

Is there any remote code to set the system into a standby or display-off mode (like on a standard Android tablet or smartphone)?

Hope anyone can help!

Many thanks and best regards from Germany

Dietmar

Should I be able to plug in  Navio 2 https://emlid.com/introducing-navio2/ in to the 2G pine64?

it is made to plug into the Raspberry Pi IO bus

Roger

Hi guys im wondering it is posible to get on working third party remotes.???
i have some laying arround and i would like to use them
thanks!
i have tried by connecting the ir receiver and open the port receiver like a pine64 remote but no codes recveived i have check the ir and is working fine
any ideas thanks again

I recently purchased a 7" touchscreen that uses HDMI for video and a USB connection for touch input. This is the specific product I purchased. Will this work with the P64+ board running Android? How would I set it up?

There used to be two different android images one for the touch pad and the regular one. What happened to the touch pad one?

I'm curious if anyone has evaluated the Johnny-Five JavaScript Robotics and IoT programming framework at https://github.com/rwaldron/johnny-five? At first glance it seems quite robust and straightforward to use. It was developed for Arduino, but uses a plugin system to work with other platforms. An Rpi plugin already exists which may (?) work out of the box for Pine, but it appears to me that a Pine64 specific plugin could be developed by a JS guru. 

I went a little nuts ordering breadboards, jumper wires, LEDs, switches and buttons, sensors, motors, servos, drivers, relays and other assorted do-dads, but they have not yet arrived from China, so I haven't tried it myself and honestly don't yet have the experience to evaluate the utility of Johnny-Five, so I wonder if anyone thinks it is a worthwhile endeavor for Pine64 powered projects?

Is there any assembly instructions for the playbox enclosure and LCD?
Not in a hurry to get the ribbons back to front and fry my pine after waiting so long.

   

A Cat5 ethernet cable has four twisted pairs of high quality telephone wire (24 AWG) which may be used to connect the uart ports of two pine boards very effectively ( or between a pine board and a PC using a cp2102 based adapter similar to the one in the following pic. In the pic above I have four colored pairs (blue, orange, green, and brown). Each pair has a solid ie [B (blue)] and its partner the white wire with the stripe ie [Bw].  So we have [ B:Bw, G:Gw, and BR:BRw ]. I am ignoring the orange pair. 

   

The idea is to connect the uart3 of PineA to the uart0 (serial console) of PineB;  and to connect the uart3 of PineB to the uart0 (serial console) of PineA. The uart(s) of each pine board are cross-wired so that each machine (on ttyS3) may monitor the other machines boot progress on serial console uart0;  not at the same time, of course. 

The machine pictured above is machine PineB. The cable has been constructed so that all of the cross-wiring happens within the cable, so that the yellow and orange jumpers of each end of the cable plugs into uart3 (ttyS3) on the euler bus,  and the green and white jumpers plug into the serial console of each board at uart0 on the EXP header. Orange yellow is crossed with green white,  also G:Gw is crossed with Gw:G, and B:Bw is crossed with Bw:B-- this so that it does not matter which wires plug where on either board as long as both boards are plugged the same way -- they must be consistent !

   

In the pic above machine PineA is shown.  I have debian mate running on PineA, and ubuntu mate running on PineB. On each board I have the green jumper plugged into uart0 Tx, and the white jumper plugged into Rx.  Again, because the cable is constructed as a cross-over both boards are plugged the same--as long as they are consistent it does not matter.  I have the yellow jumper of each board plugged into uart3 Tx on the euler bus, and the orange jumper of each board plugged into the uart3 Rx on the euler bus for each board.

With this setup I can now monitor the bootup of either board, from the other board; of course, not at the same time. Or, from either board I may signon to the other board without a network connection using the serial console. I am using the screen program to access the ttyS3 (uart3) of each machine with :