So I ordered a push button switch (which I did not receive as an original backer) as well as the Wifi / Bluetooth module for my board and it finally arrived today. However, contrary to images and instructions I've found online, the holes for the switch seem to be soldered closed. Is this a manufacturing error, or is the 512M board different from the rest? The site indicates that it "does not need to be soldered on to the board. Legs can be inserted then bent to keep in place".

The button is pretty optional (and cheap) for the most part, but it's still very frustrating that I can't use something I ordered and waited on.

Would Windows 10 IoT allow me to run an app like Hyperspin on it and operate it as Windows 10 does?

I tried using Ubuntu build initially but ran into problems getting wifi and bluetooth to work.  Being impatient I swithched over to Debian to give that a try.  Wifi started immediately  but blue tooth was still a problem.
It will find my devices but will not pair.  The bluetooth icon in the top panel changes color for about 3 seconds like it is connected but then goes back to black.  Sometimes I get a banner travel accross the screen telling me to enter the key for the blurtooth keyboard.  I enter it but it does not help.

I tried a few things I found in threads:
 sudo /etc/init.d/bluetooth restart

[ ok ] Restarting bluetooth (via systemctl): bluetooth.service.
debian@pine64:~$ sudo hcitool dev
Devices:
hci0 34:C32:BF:85:78

debian@pine64:~$ hcitool scan

Scanning ...
00:10:61:00:AB:2F GT BT-Receiver
34:88:5D:5C:30:F0 Keyboard K380

I have tried to pair both devices but no deal.
Yes my gray cable is connected and wifi works using it now.

Would appreciate some help
Thanks

Hi,
I put together my PINE with the LCD Touchpanel and everything works great. However now I have the enclosure and the original power ribbon is to short.... Does anyone know where I can get a longer power ribbon? I tried eBay and got a new one but now the Pine doesn't power on with it. I switched it out to the old ribbon and it powers on fine so I'm pretty sure I just got the wrong ribbon.

It says AWM 20624 80C 60V VW-1 on the ribbon. Any help would be appreciated.

I have burned the latest available Android 7.0 image (android-7.0-pine-a64-v1.7-r54.img) on my fresh Samsung EVO Plus 64GB SD card, and it boots fine and extends the 4th partition to the end of the available space nicely.

But there is one glitch, right after I get to the home screen: it says the SD card is corrupt. And I am afraid that's a lie, because it says to also with two other cards.

Attached are the screenshots (well, photos of projector images) with notification list and the Settings/Storage view.

I shutted the Android down properly (hold down the Power button, confirm by clicking on the menu item on the screen), but now it does not boot up anymore - it has a brief moment when it gives something out over the HDMI (black screen), but then it switches off immediately.

There are no devices attached to it, and the power should really be enough - it operated with no problems at first boot (except that notification about the corrupted SD card).

Is this anything known, or I alone am experiencing this?

Attached Files

Thumbnail(s)
       

I made simple C-application that reads DHT22 values using Pine's GPIOs.

You can find it here: https://github.com/ayufan-pine64/dht22-pine64.

Good luck

I have successfully got the Android 7.0 running on my Pine64, I am using Samsung EVO Plus 64GB card (Used another Class 10 card before but that was a disaster, so the random I/O speed really is essential).

But the Pine is installed in place where there is very poor WiFi, so it takes ages to get large files on it. Of course, I could move the Pine board itself around but I'd like to move just the SD card instead.

So, I plugged out the Pine board power supply (pretty brutal, I know, without shutdown, but I honestly don't know hot to shut down the Android when you don't have a power button), and popped out the SD card.

But, to my dismay, the card, when put in my laptop, is not recognized anymore - no partitions are visible in GParted, nothing is mounted. Also when it is put back in the Pine64 board, it does not boot anymore. Can it really be the result of not properly shutting the Android down? Do I have to burn a new image now again?

Hi All,

I've bought the Pine64 2GB and Z Wave module (EU version) to automate my home using OpenHAB.

As I am a total NOOB at this, I decided to first create a small Z Wave network using 2 Domitech Z Wave smart LED light bulbs only.
I immediately got stuck:
- I've installed OpenHAB on my Pine64.
- In Paper UI on Configureation->Things page, I see the Z Wave Serial Controller: 'online' (connected to /dev/ttyS2).
- I then try to get the controller to get into discovery mode by pressing the big '+', select Zwave binding.
- For 30 seconds it shows a rotating arrow, within that time I put one bulb in discovery mode.
- The bulb does not get 'discovered'.

Am I doing something wrong?
Is there any way to tell if the Z Wave device is really in discovery mode?

Need help here...

Domoticz is a very light weight home automation system that lets you monitor and configure miscellaneous devices, including lights, switches, various sensors/meters like temperature, rainfall, wind, ultraviolet (UV) radiation, electricity usage/production, gas consumption, water consumption and many more. Notifications/alerts can be sent to any mobile device.

Tested with PINE64 2GB(1GB and 512MB shall work well, anyone with this please help to test out), Debian Base

Remark:
If you flash new debian/ubuntu build, ensure your kernel/u-boot is up to date and also resize your root partition to max available space your SD card can provide
/usr/local/sbin/pine64_update_uboot.sh
/usr/local/sbin/pine64_update_kernel.sh
/usr/local/sbin/resize_rootfs.sh


1) First update your system:
sudo apt-get update
sudo apt-get upgrade


2) Install the development tools and libraries needed for compiling Domoticz: 
sudo apt-get install build-essential nano cmake git libboost-dev libboost-thread-dev libboost-system-dev libsqlite3-dev curl libcurl4-openssl-dev libssl-dev libusb-dev zlib1g-dev

3) Build & Install Boost Libraries
a) If this is a clean system, continue at Now build and install the Boost library.
Its recommended that you use the latest Boost libraries - as of 8th August 2016 that is version 1.61.0.
For this we need to compile/install them by issuing the following commands:
These instructions can also be used on a Linux system.
[This first step is necessary because you will get linking errors if you don't remove the old Boost library]
Instructions here are for removing boost 1.55, on your system this might be another version, so adopt these commands to your need. It could also be you never installed boost on your system, do not worry, just execute the commands

sudo apt-get remove libboost-dev libboost-thread-dev libboost-system-dev libboost-atomic-dev libboost-regex-dev
sudo apt-get remove libboost-date-time1.55-dev libboost-date-time1.55.0 libboost-atomic1.55.0 libboost-regex1.55.0 libboost-iostreams1.55.1
sudo apt-get remove libboost-iostreams1.55.0 libboost-iostreams1.55.0 libboost-iostreams1.55.0
sudo apt-get remove libboost-serialization1.55-dev libboost-serialization1.55.0 libboost-system1.55-dev
sudo apt-get remove libboost-system1.55.0 libboost-thread1.55-dev libboost-thread1.55.0 libboost1.55-dev
sudo apt-get autoremove

b) build and install the Boost library.
mkdir boost

cd boost
wget http://sourceforge.net/projects/boost/fi...z/download
tar xvfz download
rm download
cd boost_1_61_0/
./bootstrap.sh
./b2 stage threading=multi link=static --with-thread --with-date_time --with-system --with-atomic --with-regex
sudo ./b2 install threading=multi link=static --with-thread --with-date_time --with-system --with-atomic --with-regex
cd ../../
rm -Rf boost/

4) Build Support for OpenZWave

sudo apt-get install libudev-dev
git clone https://github.com/OpenZWave/open-zwave open-zwave-read-only

cd open-zwave-read-only
git pull
make -j 3

5) Compiling/building the Domoticz binaries

cd ~
git clone https://github.com/domoticz/domoticz.git domoticz
cd domoticz
cmake -DCMAKE_BUILD_TYPE=Release .
make

6) Starting Domoticz automatically when the system boots
a) Copy startup script into /etc/init.d

cd domoticz
sudo cp domoticz.sh /etc/init.d
sudo chmod +x /etc/init.d/domoticz.sh
sudo update-rc.d domoticz.sh defaults

b) Edit Startup Script
sudo nano /etc/init.d/domoticz.sh

The lines you usually need to change are USERNAME, DAEMON and DAEMON_ARGS

I ordered the LCD Kit, more than a week ago.
Still haven't received any notification about shipment. 
Emails got no response.

When will the order be shipped? What's the tracking id?

The service is puke (From the first day on kickstarter...).