These are the issues holding me back from using my A64 2gb board full time.  I thought about making a post for each one but some are known and I thought putting it in one place would help get it on the radar faster.

Any help that you could give that I might have missed on the forum would be great.

*Note that I'm using the latest Android image as of this post (5.1.1 Image Release 20160428)

1. Ethernet needs to work at gigabit speeds (known bug)

2. Sound issue with headphone jack (have to unplug and plug in again to work).  HDMI audio works fine.

3. The last two apps I need to have working are buggy or not supported.

   -Google Play Music (tried using a different apk but didn't work).  It opens up and appears to run fine but will just skip songs over and over without playing anything.

   -MLB At Bat (shows as not compatible in the store and did not work with side-loaded apk).  Won't play video as it says the device is not supported.  Could this be fixed by spoofing as a different device?


Aside from those it's been working well for me.

Thanks.

I put in an eight letter password and it says put in at least an eight letter password. So I added one letter and it accepted it. FAIL

Hi
Is it possible, that i can't use the RasPi 7" Touchscreen? It seems that the ribbon cable is a millimeter too wide...

Has someone already made to work?

Thanks
Paara

Wacom driver should not rotate when screen rotates. It does anyway. Consequently it doesn't work, you can't click stuff at the "bottom" (right side) of the screen at all. According to Wacom this was supposed to be fixed in the Android 5 driver, http://forum.wacom.eu/viewtopic.php?f=9&t=13918

I'm using an iPad 3's "power brick" (rated output: 5V 2.1A) with a Blackberry's USB cable to power my Pine.

Power consumption (the max I saw so far is ~0.8A, just plain running, without any load / add-ons):


And here, it's when the unit was turned off:

Hi,

Having problems with my first boot up.

Have tried Debian and Ubuntu boots on 8G and 16G SD Cards.

Monitoring the boot up on the serial port, I consistently get to the line 

[   13.858918] systemd[1]: Set hostname to <debianpine64>.

But at this point, the Red LED on the Power supply goes out and the boot process stops.  It seems like the power supply is shutting down for some reason - I am guessing.  I am using the same power supply that runs a Raspberry Pi 3, so the supply is pretty good.

Anybody else had this issue?  or is there anything else I should be looking for in the boot log?

Barry

Is there support to directly control the GPIO pins with C or assembly, directly?

I'm looking to control the GPIOs at 10Mhz to 100Mhz and i assume that is not possible using the Python GPIO interface.

I am pre-sales  order # 102224538.  Ordered in Feb.  Just plane $19 1 gig board, no extras.  When can I expect shipment?

Not a rant post, just an information post and hopefully Pine team can revamp the adapter design.

So, I bought the adapter along with the board.
I'm still exploring, but I find that the audio port on the VGA adapter is on the wrong side.
The awkward position resulted in the audio connector pushing on the ethernet and power cables.

 

Yes there's the onboard 3.5mm audio jack but for some applications (or OS), it seems to only want to output via the HDMI connector.

For example: on xubuntu image by long sleep updated by Pine (20160502), it only lists 1 output device: sndhdmi Analog Stereo, and that's via HDMI, so I'm left with no choice but to connect via the adapter. If only the port was on the other side (plus the markings on the adapter)...

Xposed Framework lets you fiddle with Android and change how things work by installing modules. It requires that you install a framework. Normally you do this with CWM or TWRP recovery but you can also do it by hand. Doing it by hand requires a Linux machine. You could do it on your Pine running Linux, on a PC running Linux, with a virtual machine running Linux... but you're gonna need Linux. You might actually be able to just do it with Android, but I haven't tried.

This is how I just installed Xposed on my Pine running Android 20160428.

Step 0, READ ENTIRE POST BEFORE DOING ANYTHING PLEASE THANK YOU
Step 1, visit XDA forum thread http://forum.xda-developers.com/showthre...?t=3034811
Step 2, download XposedInstaller_3.0-alpha4.apk from the thread and also for Android 5.1.1 on pine64, the latest sdk from http://dl-xda.xposed.info/framework/sdk22/arm64/ (currently xposed-v84-sdk22-arm64.zip)
Step 3, put your microsd card into a Linux machine. Windows can't read ext4 so you need Linux. If you don't have a linux machine, use a linux livecd with vmware player and connect the card reader to the virtual machine. Doing this is outside the scope of this howto, but I am actually going to use a debian livecd for my examples. The short, SHORT form is that you download the livecd ISO and vmware player, install vmware player, then create a new virtual machine using the iso. You don't need to install, just run live.
Step 4, get a root shell. e.g. sudo bash
Step 5, mount the partitions if this hasn't happened already. you can either just try to mount every partition on the microsd card until you find some ext4 parts, or use this handy-dandy code snip to locate them. First do something like "dmesg|grep sd" to find your devices, it will look like this

[ 1690.123504]  sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 sdb12 sdb13 >
[ 1690.158498] sd 4:0:0:0: [sdb] Attached SCSI removable disk

OK, so you want to look at /dev/sdb, so now do this:

( for i in /dev/sdb*; do echo -n "$i " ; head $i | file - ; done ) | grep ext

That will show you which partitions are formatted ext-something. now mount 'em.

for i in 1 10 13 7; do mkdir /mnt/sdb$i; mount /dev/sdb$i /mnt/sdb$i; done

Now you can see their contents. To figure out which is /system:

ls /mnt/sdb*/build.prop

which here returns /mnt/sdb7/build.prop, so sdb7 is /system. To simplify your life, make a symlink in the root

ln -sf /mnt/sdb7 /system

At this point you need the unpacked zip file for the framework. Just unzip it anywhere.

unzip xposed-v84-sdk22-arm64.zip

This will give you a META-INF and a system directory. Deep in the META-INF directory is a script, we will need to carve it up before we can use it. So we will make a copy.

cp META-INF/com/google/android/flash-script.sh .

Now we have to edit the script and make a change. I use vi, you might use nano, whatever. edit flash-script.sh

nano flash-script.sh

and remove these lines about halfway through:

echo "- Mounting /system and /vendor read-write"
mount /system >/dev/null 2>&1
mount /vendor >/dev/null 2>&1
mount -o remount,rw /system
mount -o remount,rw /vendor >/dev/null 2>&1

and these lines near the bottom:

if [ "$API" -ge "22" ]; then
  find /system /vendor -type f -name '*.odex.gz' 2>/dev/null | while read f; do mv "$f" "$f.xposed"; done
fi

Now you can just run the script to install!

sh flash-script.sh

Here's what it spit out for me

******************************
Xposed framework installer zip
******************************
- Checking environment
  Xposed version: 84
- Placing files
- Done

Now umount all the /dev/sdb stuff that you mounted:

for i in /mnt/sdb*; do umount $i; done

And you can take out the sd card, put it back in your pine, and reboot.

WHAT CAN GO WRONG

You could forget any step
You could get the wrong platform file

What happens next?

When you boot, Android will have to optimize all your apps all over again. It will do this automatically. There is no need to clear the cache. Android is smart enough to figure out that the old stuff in the cache is worthless.

The next thing you do is install the Xposed Installer APK. This is what actually lets you do stuff with the Xposed Framework. You can use the installer to get some modules. Then you have to reboot before you can use them.

My favorite modules are App Settings and GravityBox. iFont is also nifty. After downloading and installing modules under download, you must also activate them under modules.

I am using Reboot menu [no ads] by KitKelly for rebooting... good luck finding it. There's lots of similar apps though. The Xposed Installer should also offer to reboot for you.

If You Are Smart

You will do a test on a fresh install on a spare SD card before messing with an install you care about.

What You Should Know

Stuff may not work. I am having pretty mixed results. Still encouraged by getting it to install.