Hello everyone, 

Boots and runs just fine, however the Linux Mate is a little heavy, runs slow, bogs down etc. I wanted to try a lighter O.S. I have three SD cards, used three installer types including the Etcher remix made for Pine64. Once I install the image on the SD card/s it will not boot. The power button symbol just flashes until I remove the card, then it continues to boot just fine into Mate. I have used all three of these sd cards to boot a live image of the android-for-pine but that too was sluggish and unresponsive.

TL;DR SDCards I have worked previously, they do not work when I image DietPi.

Is there a preboot screen, verbose, or a bios type screen to monitor the boot process?

This unit came pre-flashed from the factory.

i have a pine 64 2gb ram and 64gb sdcard(bought with pine64), and no sound with image Android 6.0 (HDMI Video Output) [20170112 v2.0.1]. with remix os or ubuntu or debian everything it's ok with sound.
how can i solve the problem with sound,

thanks with regards

I have the Pinea64 4GB with the LCD screen. Unfortunately, Ubuntu doens't work with LCD, so I'm wondering if I purchase a HDMI LCD screen for the raspberry pi, would this work with the Pine??

Can someone please point me to where theres a simple GPIO example in C?

Is the GPIO memory mapped somewhere?  I need to read/write the pins at very high speed, so I'd like access as close to the hardware as possible.
Thanks

I pledge my pine-A64 via the Kickstarter project
and got it almost a year ago.
it was the 2GB version
to be honest? i was really excited.
it came with the original power supply, the Bluetooth\ WiFi module, Air mouse keyboard and a HDMI to DVI adapter

BUT....

I build a 32 GB microSD (SanDisk class 10) card with one of the OS
connect everything to a computer screen (Xerox)
connect the Pine A64 to the power supply the red led switch on but nothing happened.
I install a new OS but still nothing..

I put everything aside and forgot from it.

few days ago I lookd for a Android OS system and try it again
this time with a smaller computer screen ASUS one
a HDMI to DVI new cable a new 32 microSD card (Kingston class 10)

and used the "PINE64 Installer" to build the mirror
I try few OS
Android 6, 7 , Remix

but It still does not work


so,
what do I do wrong??

is it possible that the board is damage?

thank you Uriel

My pinebook have issue with keyboard - to get a button pressed, I have to press it with sufficient force. If I pressed it lightly (heard click sound, surely), buttons didn't produce events at all.

Seems, I should press directly at the button center to achive keypress. When I pressed at the edges - button press is ignored almost everytime (i had to re-press every 3-4 character during typing this message).

Is this a problem just for mine pinebook?

Is it software driver issue or hardware design? Can I receive fixed keyboard for replacement?

Thank you.

Hello.

I'm using pinebook for a few weeks and stuck with unwelcome featue - pinch to zoom event during ordinary scrolling with to fingers.

Chrome resizes page (very slow on big webpages) and it's very annoying.

Can I disable this behaviour?

I disabled touch events in chrome, but it wasn't helps - pinch-to-zoom still active.

I can't find any appropriate utility to configure pinebook's touchpad. Looks like it isn't synaptic (synclient said - no synaptics driver loaded).

Hello all,

I'm developing my own PCB around the A64 and am currently using a Pine64 to develop my flashing procedure (want to have just eMMC on the board). For right now what I'm trying to do is flash a linux image to the blank SD card on the Pine64 using only the USB OTG port. It seemed like this was supported when I found Ayufan's USB Mass Storage, but I didn't get it to boot. The FEL interface becomes unresponsive, and the serial output shows us getting up to 'pmbus ready' I've got serial output from a few runs here: https://pastebin.com/tDve7G3t

After chatting with marcushh777 on the #Pine64 IRC channel, I decided to put that aside to try and better understand the boot process. The last couple of weeks I've been experimenting with different branches of u-boot/u-boot-sunxi and Longsleep's build-pine64-image repo, and was able to build that image, write it to RAM (over a period of hours) using u-boot over serial, and then write that image to the board. That's pretty exciting, and was a great learning experience, but I'm not quite sure what I should do next to get to achieve my single-port goal.

I was thinking about embedding an RNDIS driver into u-boot, but that would still require a second interface to initiate a TFTP transfer, though maybe another endpoint could be established to present the serial over USB as well. I'm not quite sure where to start with u-boot, either. I haven't managed to boot the mainline u-boot with ported H3 DRAM drivers, but a sunxi branch (20160126-wip-a64) with AW's libdram does boot.

It seems to me that I must be missing something, because this functionality seems like something that must have been implemented somewhere, even if it hasn't been ported to the A64. Does anyone have any suggestions for how I can proceed from here?

Thanks!

I havent seen any release os images posted for testing either for those who got pre-release boards or otherwise. I guess im just asking what os images will we see upon first shipment if we preorder?

Im interested in debian mostly, but im also interested in what else will be available. Given the price point these might replace several pi's for me.