I received an email saying my computer shipped on May 16th to Niantic Connecticut. When I try to track the shipment it say it was delivered to Post Office on May 2 to Pullman WA. I have NOT received the unit. Does anyone know whats up with the tracking system

Hello, anyone know anything about the clock battery? Is it a rechargeable battery port? If so when does it recharge, with power to the board and board on or off. 
Thanks is someone knows.
Steve

I know that the May 2nd update on Kickstarter mentioned an email address dedicated to shipping questions, and I believe this email address is ignoring all emails. I would have gladly accepted an automated confirmation response clearly stating that my email had been received as a response, but I didn't even get this. I personally believe that customer service here needs a lot of work since most customers will get extremely agitated when completely ignored for more than a week. As a quick note, I sent the email on May 16th, and I personally would have been happy with a quick confirmation response ( even if it was automated ) that way I know that the team received my email, and would have responded to it when it had a chance.

Anyways, I am one of the many backers who are upset about the fact I got charged for my add-on items on march 10th, 2016. I have waited more than 75 days to create this post, and all I really want is some clear updates. As a quick note Some of the add-on Items I added are as follows...

• 6 additional Pine A64 boards
  
• 7" LCD touch Screen
  
• Lithium Battery
  
• 5 PINE64 ABS Enclosure ( standard)
  
• PINE64 PlayBox Enclosure
  
• basic IR Remotes
  
• RTC backup Batteries ( CR and AAA types)
  
• USB Keyboard
  
• Camera Module
  
• Power Supply
  

Not sure if this is the correct place to post, but I just received my two PINE64's.

This has been my first kickstarter experience and I really want to express my appreciation to the pine folks for running an excellent campaign. 

I was supposed to receive my order about 6 weeks ago, but frankly given the complexities involved in such a project I am thrilled to have it now!

I do have one suggestion: I would love it if the founders would do a postmortem on the whole experience. I think it would be fascinating to know the back story behind the design, sourcing, manufacturing and kickstarter processes.

Thanks again,
-Jake

Yesterday, I was overcome with excitement that my pine64 finally arrived.  As soon as I was done work for the day, I went on to install linux on the system.

Well, it wasn't as easy as it should have been.  Firstly, at my own fault, I was using `dd` from mac, and it wasn't writing the disk image properly, so I switched to my windows machine and used win32 disk imager, and finally had my SD card ready.  Just as a note, I am using the debian build.

My wife and I recently picked up a used 1080p tv, and it's set up but currently not in use, so I decided I'd use that as my test monitor until I figured out how to get the touch screen working (by the way, does anyone have some hardware install instructions for the 7 inch touch screen?  I'm not super familiar with this type of connector).

Well, the screen flickered and it looked like we were ready to go.  The boot text went scrolling by, and then my TV just went blank.  The power was still on, but nothing.  I decided I'd give it another few moments, since it was first boot.  Nothing.  So I plugged in my usb keyboard, and did Ctrl+Alt+F2 to try and get to a terminal screen.  Nothing.  So I thought this could be the TV, so I unplug the HDMI from the tv.  Well, the TV remains completely blank, and doesn't revert back to the "no signal" display.

The culmination of all these events left me a little spent, so I just decided to unplug everything and I'd take a look this morning before I dug into work today.

Today, I hook everything back up, and now I don't get a red power light on the pine64 when I try and boot it up.  I turned on the TV, and it has decided to revert back to working, so I plug in the Pine64, and it immediately goes black again.

So, now I don't know if it's even booting up since there is no LED indications on the board (or on my keyboard when I plug it in ie caps/num/scroll lock don't produce lights).  What's going on?  Is my Pine64 broken after my first attempt on getting it up and running?

running Ubuntu

In order to start working with midi signals, I follow this guide
http://tedfelix.com/linux/linux-midi.html

Under the title: Installing a Low Latency Kernel
I need to change the kernel config file:

A number of people have reported getting a 'script not found' error when trying to use PhoenixCard. This is because you are trying to burn an image that is not compatible with the PhoenixCard application (i.e. a 'dd' image).

On the Software/Image Download section of the Pine64 wiki, there are many images available, but only the images specifically labelled so are burnable with PhoenixCard.

The images labelled as being a 'DD image' are of a fixed size (typically 8GB, 16GB, 32GB, 64GB) and are intended for burning via the dd command in a terminal, with Win32DiskImager, or with Rufus or similar software (such as ApplePi Baker or Etcher on a Mac).

See also this similar thread.

Hello,

My tracking is https://track.aftership.com/RI068189945CN
But I mistakenly put the wrong address.

I think it is still at China Post, any way to resend it back to me?

regards,

Victor

Hi all,

I'm trying to burn a bootable SD for my Pine, but Phoenixcard AND etcher are not able to burn the image to the SD. I don't have a clue where I'm missing something, but it's starting to get anoying  .

Best regards,
Mischa

I'm using the latest Debian Mate image from https://www.pine64.pro/downloads/, and my TV is unfortunately cropping a bit off the edge of the entire screen. Even more unfortunately, the display settings on the TV do not include an option that fixes it (just a few that make it worse).

When I had this problem with my RPi, I went into raspi-config and set the overscan value and it was fixed right away. I've now spent a few hours trying to scour the internet for a solution to this, all to no avail. Most seem to suggest using xrandr, but that doesn't appear to be an option either (unless I'm missing something), since it gives me this output, and won't let me set any properties for the monitor: