So I have the US Z-Wave module (Sigma) version without an adapter. 

Initially, it was working with the OpenHAB image from the wiki, but after adding the 4th device all devices stopped communicating.
I was getting some of them discovered as "Unknown Device" but once the module was reset completely they simply do not communicate at all. 

I have tried using a different build with OpenHAB as well as built the OpenZWave console. In either case I have no problem communicating with the module and getting it initialized but No communication from the devices is received. 
I see no communications error messages in the log either, I simply see no evidence of any communication from any device being received at all.

Is it possible the Z-Wave module itself is bad? I'm not sure how to test it at this point. 
Any suggestions would be greatly appreciated.

Hello,

I tried to compile the v4l-dvb (DVB-T) drivers for PINE64 (ARM64 running Debian jessie with custom kernel 3.10.104-1-pine64-longsleep #103). Currently the PINE64 kernel is still at 3.10 kernel, because of the SoC compatibility. I did follow the manual explanation for ubuntu at https://help.ubuntu.com/community/DVB-T_%28USB%29

PINE64 board specifications are:
http://linux-sunxi.org/Pine64
- SoC A64 @ 1152MHz
- DRAM 2GiB DDR3L @ 672MHz
- USB   2 x USB 2.0
- HDMI port
My storage is on a 64 GB micro-SD card.

The DVB-T USB dongle is a "RTL-SDR Blog R820T2 RTL2832U 1PPM TCXO SMA Software Defined Radio" from
http://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/

After I compiled all drivers, I tried to load them with modprobe (I also tried to optionally rmmod all the other ir_* modules, which might be interfering) :
# modprobe rtl2832
# modprobe dvb_usb_rtl28xxu

# dmesg report is:

[59570.134994] usbcore: registered new interface driver dvb_usb_rtl28xxu
[59995.218466] lirc_dev: module unloaded
[60052.126759] usbcore: deregistering interface driver dvb_usb_rtl28xxu
[60070.533355] usb 1-1: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
[60070.598372] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[60070.608807] dvbdev: DVB: registering new adapter (Realtek RTL2832U reference design)
[60070.621918] rtl2832 2-0010: Range 0: selector for 0 in window
[60070.628377] rtl2832: probe of 2-0010 failed with error -22
[60070.644011] usbcore: registered new interface driver dvb_usb_rtl28xxu
[60249.342718] usbcore: deregistering interface driver dvb_usb_rtl28xxu
[60304.611609] WARNING: You are using an experimental version of the media stack.
       As the driver is backported to an older kernel, it doesn't offer
       enough quality for its usage in production.
       Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
       bd676c0c04ec94bd830b9192e2c33f2c4532278d [media] v4l2-flash-led-class: remove a now unused var
       079933dbcb02132cc48ba052882fe0a9e3b0b762 [media] v4l: flash led class: Fix of_node release in probe() error path
       c762ff1f7e3b09293c22ce62135ef550c1b3327c [media] coda: fix the error path in coda_probe()
[60304.702195] dvb_usb_rtl28xxu: `' invalid for parameter `rtl2832'
[60364.122409] usb 1-1: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
[60364.192481] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[60364.209402] dvbdev: DVB: registering new adapter (Realtek RTL2832U reference design)
[60364.228000] rtl2832 2-0010: Range 0: selector for 0 in window
[60364.240827] rtl2832: probe of 2-0010 failed with error -22
[60364.262389] usbcore: registered new interface driver dvb_usb_rtl28xxu
[60681.746137] ehci_irq: highspeed device disconnect
[60681.756537] usb 1-1: USB disconnect, device number 3
[60688.754716] ehci_irq: highspeed device connect
[60688.981979] usb 2-1: new high-speed USB device number 2 using sunxi-ehci
[60689.158238] usb 2-1: dvb_usb_v2: found a 'Realtek RTL2832U reference design' in warm state
[60689.228550] usb 2-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[60689.244639] dvbdev: DVB: registering new adapter (Realtek RTL2832U reference design)
[60689.262071] rtl2832 2-0010: Range 0: selector for 0 in window
[60689.274417] rtl2832: probe of 2-0010 failed with error -22

# lsusb -v
Bus 002 Device 002: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Device Descriptor:
 bLength                18
 bDescriptorType         1
 bcdUSB               2.00
 bDeviceClass            0 (Defined at Interface level)
 bDeviceSubClass         0
 bDeviceProtocol         0
 bMaxPacketSize0        64
 idVendor           0x0bda Realtek Semiconductor Corp.
 idProduct          0x2838 RTL2838 DVB-T
 bcdDevice            1.00
 iManufacturer           1 Realtek
 iProduct                2 RTL2838UHIDIR
 iSerial                 3 00000001
 bNumConfigurations      1
 Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength           34
   bNumInterfaces          2
   bConfigurationValue     1
   iConfiguration          4 USB2.0-Bulk&Iso
   bmAttributes         0x80
     (Bus Powered)
   MaxPower              500mA
  Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           1
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass    255 Vendor Specific Subclass
     bInterfaceProtocol    255 Vendor Specific Protocol
     iInterface              5 Bulk-In, Interface
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x81  EP 1 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0200  1x 512 bytes
       bInterval               0
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        1
     bAlternateSetting       0
     bNumEndpoints           0
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass    255 Vendor Specific Subclass
     bInterfaceProtocol    255 Vendor Specific Protocol
     iInterface              5 Bulk-In, Interface
Device Qualifier (for other device speed):
 bLength                10
 bDescriptorType         6
 bcdUSB               2.00
 bDeviceClass            0 (Defined at Interface level)
 bDeviceSubClass         0
 bDeviceProtocol         0
 bMaxPacketSize0        64
 bNumConfigurations      2
Device Status:     0x0000
 (Bus Powered)

# lsmod
Module                  Size  Used by
dvb_usb_rtl28xxu       25651  0
rtl2832                17781  0
dvb_usb_v2             17915  1 dvb_usb_rtl28xxu
dvb_core               90288  2 rtl2832,dvb_usb_v2
w1_gpio                12739  0
wire                   23744  1 w1_gpio
cedar_ve               17368  0
ss                     33083  0
mali                  199851  0
8723bs               1365012  0
cfg80211              374207  1 8723bs

The end result is that the DVB-T device doesn't get successfully recognised, it has also failed running w_scan and exits with the error main:3916: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****

This error has also been submited to Linux kernel bugtracker - https://bugzilla.kernel.org/show_bug.cgi?id=183501

Regards,
Jan

Hello,
lately I found that I could really use the Wifi module for the Pine and checked the shop. Fair enough, 10$ seems reasonable.
But then I found that the shipping costs would double that, being a flat 12$.
If that is the cost to ship stuff to Europe, it would also be ok. But how can it be that a 5 gram little Wifi module has the exact shipping cost as a complete kit including enclosure and every plug adapter you can imagine?

I understand, that it probably makes it easier on your part of the supply chain, but I can't accept that and refrain from ordering from the shop on these conditions.
Could you explain the reasoning behind the flat shipping fee? I would really like to give you more of my money, but this just feels like extending the profit margin.

Best wishes
Jens

I have a usb webcam connected to the pine64 device. I installed a camera app called 'open camera' from play store which recognises the camera and i can take pictures with the camera.

But none of the chat app (like hangout, skype, etc.,) recognize the webcam. I get an error message that camera is not present or being used by another app. There is no other app running at that time.

Is there a way to make these apps use the usb webcam?

Hi all,
While I'm reasonably savvy in the tech and Windows worlds, I'm probably best described as a newbie in the maker and linux and Android areas, so I'm hoping I can impose on you folks for some advice...

I bought 4x PINE64 units (2GB A64+) to build as media boxes for family, along with the official IR (non-air) remotes. Primarily what I'd like to get running is a box that can:
- play/stream from Netflix
- have a USB hard drive/stick plugged into it
- play music and movies from the drive/stick
- be controlled with a remote
- be an 'appliance' (i.e. have a friendly UI that is non-technical-looking for most common functions)

There seems to be a lot of different options for getting the above working, in various states of readiness, e.g. Android 5.1.1/6/7, Kodi, Linux, OpenElec, RemixOS, SPMC, other...

As much as I'd love to have the luxury of just playing with this stuff and experimenting myself, at the moment I'd just like to jump straight to a good and working solution.

Any thoughts or recommendations from your experiences?

I have few questions regarding Pine 64

1. Is Pine-64 capable of advertising Bluetooth Beacons?
2.Does Pine-64 come with official Android OS and which version does it support?
3.which type of Beacon advertisement does pine 64 support ? which android app is used to locate the beacons?
4.which format of beacons that pine a 64 advertises- altbeacon,ibeacon,edystone beacon or any other formats?

kindly help me with these questions

Hey everyone,
  Most of the "Start-up" instructions for the Pine say that you should be connected to the internet.
Is this absolutely necessary?
  I'm asking because I do not have internet access at home,(where I would be starting up my Pine64).

Thanks

I have a monitor that I can use with Raspberry Pi with a HDMI (at side of RPi) to DVI (at side of monitor) cable. However, with PINE64 with longsleep's Ubuntu, this does not work. No image appears. Should this work? if so, how do I debug this?

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?