Anyone out there have any ideas for a back plate for the LCD touchscreen? Mine came without a back (don't know if that is intended or not), so I'd like to have something to enclose the screen in something.

After building kernel 3.10.102 based on longsheep's sources I now have working iSCSI support on my Pine64, however, I can't figure out the correct arguments to put into uEnv.txt to actually boot off iSCSI - has anyone gotten this working and if so, what does your uEnv.txt look like?

Thanks!

Hey y'all. So I purchased a preloaded sd card with Android. It works just fine, but after seeing a friend use remix os, I've decided to switch.

On this wiki page there what look to be a bunch of images I can burn to using dd on linux. Last I had looked we have to use this phoenix tool on windows.

Am I able to use these dd images safely?

Hello all,

So I've tried using the airmouse that comes with the kick starter backer kit and cannot seem to get the thing to do anything. The sparse instruction sheet that came with it is no help so I figured I would reach out to you guys to see if anyone else has had issue or can help me.

I'll relay what I've done to try and use it with me dell laptop. I plug in the wifi dongle and it shows in my devices as "airmouse". Then I try to pair it to the receiver and from what the instruction sheet says it looks like it pairs correctly, but when I try to use it to move the mouse around, nothing. To pair, I press down vol - and vol + until the green light goes solid, let go and then wait till the light goes off before I try using it.

What am I doing wrong here?

Hey everybody,

I was very exited when I received my pine. First impressions were really good! But I discovered that one of my USB ports was dead. There Is not even 5V(I tested an sub fan). I contacted the support but I didn't get a response yet... So I hope I will get contact to someone of the support team this way...

I came across several hints on other Allwinner SoCs like the H3 (which has similar peripherals to the A64, just 32bit cores) where to enable better inter-operability with DVI-HDMI adapters a certain device tree option has to be set:

I imagine I'm not the only person who has encountered this, but I recently picked up a few microSD cards that I wanted to use with the Pine.  The problem I'm having is when I try to use the DD images for a 32GB card, it says that the image is too big, not enough sectors available (using Win32DiskImager).

I purchased three of the same card, SanDisk Ultra 32GB class 10, UHS-1.  All three show the exact same size of 29.8GB.  I know companies do the 1000 instead of 1024 thing for how they calculate GB, and if you do that for KB, MB, and GB, you're looking at 29.8GB actual, so that makes sense.

But I would think the image for a 32Gb card should fit on a "32GB" card.  Is anyone else having this same issue?  Am I missing something?  Do I need to format the cards first in a different way?  I tried to format, I think it was exFAT32.  I could also select sector size (it was at 512).  What are the correct settings to format the card to?  Or, should I use the 16GB image on the 32Gb card in order to have some storage space available?  Thanks for the help.

Using the new Debian Base image: pine64-image-debianbase-310102bsp.img

Got following error when install Dstat. Any help?? This is the first distro i encounter that cannot install dstat.

root@pine64:/home/debian# apt-get install dstat
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  dstat
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 50.5 kB of archives.
After this operation, 351 kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian/ jessie/main dstat all 0.7.2-4 [50.5 kB]
Fetched 50.5 kB in 1s (31.1 kB/s)
Selecting previously unselected package dstat.
(Reading database ... 88108 files and directories currently installed.)
Preparing to unpack .../archives/dstat_0.7.2-4_all.deb ...
Unpacking dstat (0.7.2-4) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up dstat (0.7.2-4) ...
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 35, in <module>
    from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 1
SyntaxError: Non-ASCII character '\xdb' in file /usr/share/python/debpython/version.py on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
dpkg: error processing package dstat (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dstat
E: Sub-process /usr/bin/dpkg returned an error code (1)

Hello Team,

Is it possible to anyone from PINE64 Team to give me an update on order id #8162148  as I am seeing no communication from sales and shipping?.

@Sales Team, We are into Energy meters and Energy management System, Pine64 is suitable for our new product development, however,
I discussed with Jonny Vu from sales team over the email and after that placed order for demo piece but is taking lots of time to ship. looking at your current situation are you sure to provide us in product delivery in a timely manner.

I have found some *.conf files at my at my Remix installation at root/etc e.g. files controlling the audio setup.
It would indeed be interesting to be able to modify some af these files, it might e.g. solve the issue related to default audio output.
But they are all write protected. 

I suppose I shall use at terminal emulator and there change the access level to read/write but I haven't used Linux for 30 years and can't remember many commands any more.
Furthermore do I not know which will work in in Remix / Android.