A kickstarter backer in the comments section over there is claiming that when she tries to boot Android, she is presented with a black screen with white text saying 'AB Login:'

Has anyone else experienced something similar, or can someone shed some light on why and/or how this might be happening?

Just asking if I should be worried.
Backer number 23,241 and no information of shipment.

Look forward to hearing from you.

Where do we get our Kickstarter backer number?  I backed in January and have an order "ready to ship".
I need it to submit a question regarding shipping.

Just received the kit today; LCD ribbons attached to DSI and TP (metal side down, a little awkward without the yet-to-be-shipped enclosure), and the red LED powers on, but it does not appear to boot.  I checked the connections, same result.  I removed the LCD and tried the board alone with a good HDMI cable; same result: black screen.

I attempted to verify the image on the "Pre-loaded Micro SD card" with both a Windows 8 and a Macbook, but both state that the "disk is not readable"???   WTF?  

What next?  Any suggestions would be greatly appreciated!


------------------------------------
(Reward Level):

"The PINE A64+ Box w/ Touch Screen

You will get the PINE A64+ 1GB unit along with 64GB MicroSD Pre-Loaded with Android 5.1 OS, 802.11N Wifi + Bluetooth 4.0, PINE64 Power Supply, 7" LCD touchscreen panel, the PINE64 Enclosure. 2GB upgrade available for $10 later. "

Despite my best efforts, I cannot get the Play Store functional.  Every time I try to install an app, no matter how simple it is, I get an "Auth error."  I get this error, despite ensuring that I'm logged into my Google accounts; that the time is correct; that WiFi is enabled so that location is found.

What the hell?  Hardware is only as good as its' software.  Is this a Jide or Pine issue?


-MMB

I'm trying to compile a "hello world" assembly program written for 32-bit ARM. I was told this would work:

gcc -o hello -m32 hello.S

But I get this error:

gcc: error: unrecognized command line option '-m32'

I installed build-essential but nothing else. Am I just missing some component that allows this switch, or am I out of luck? Sorry if this is a stupid question, but I'm just another one of the newbs having fun crawling through the dark trying to make things work.

Hi all. Not sure how many of you have tried to SSH into your pine64 (using debian image) from outside of the LAN. I am unable to do so. Here are some things I have discovered to help.

1. I have a Raspberry Pi that I can SSH into from the outside. I have a router/modem combo from COX and can SSH from the outside and inside the LAN just fine. And strange enough, I don't even have to forward any ports to do this.
2. I tried to open the port on the router and looks like that doesn't matter one way or another.
3. When the RPi is plugged in to the router/modem, when I check the port 22 on a website, I enter my outside LAN IP and scan port 22 opens. When I remove the RPi and scan again port 22 closes.
4. With the pine64, I have the SSH setup. I can ssh to it from inside my lan network. Can't access outside my LAN.
5. Ran nmap

I've emailed support AT LEAST 3 times since I got my "Your Package has shipped". I have yet to hear back from them about ANYTHING. 

I got the email on May 27th. That's almost 3 weeks ago. 

It came with a tracking number. I emailed them a few days later to let them know the tracking number would not work. Then about a week ago I got the Kickstarter email saying that some packages didn't get "scanned" or whatever. Now I see that MANY other people are in the same boat. 

I tried my tracking number again... Still, nothing. It just says "Pending" like it did since May 27th. 

Why am I being ignored by support? Why hasn't my package gotten here yet? Why hasn't my tracking number been updated? Why haven't I received any information other than the Kickstarter update that blamed the shipping company? 

This is my tracking number... As if it would help.

LS888455638CN

Boots when just wifi/Bluetooth, and boots when just LCD/ Touchscreen. I'm running the android lcd version. When both are in the red light turns off then on and and nothing happens

Hi, I was playing a bit with the bluetooth part on the RTL8723bs. What I gather from the documentation and the web it's just a normal serial interface and needs to be initialized correctly. I used a small program from https://github.com/lwfinger/rtl8723bs_bt and was able to talk to the BT module on /dev/ttyS1 (physical UART is UART1 on Port G of the A64) and it seems it was able to initialize the BT and hook it up to the Linux BT subsystem. (see http://pastebin.com/Z3RUS9kc for output and dmesg). Now I have to see if it actually works :-)

Edit: while the initialization seems to work, the Linux BT stack doesnt register any new adapters, I have to look into how to debug that....