just need to vent. have spent so many hours futzsing around with it. seriously hate this device. android on it has always been unstable for me. memory card fine. power supply fine. & buggy buggy buggy, constant crashes. always slow. always.

thanks, sure the mods can delete this as it contributes nothing. just had to vent. seriously what a piece of work. and the blasted images, what moron made them that way so they're more sectors than 90% of people's cards out there, so you can either futsz around with trying to resize a partition or you lose half your space by going to the image one size smaller. what a borked execution that is.. let alone the stability/reliability. sure it was $30 or so but what a cruddy card. it's like buying edison's first lightbulb, it lasts for 5hrs or some thing like that...

seriously this device could blow up. does anyone have a reliably stable, functional, non-hanging experience with it?

Hi Everyone,

What do you guys think about we add support to mbedOS from ARM ??

I was at ARM TEchcon and saw it. It would definitely great to have support for it. I'll request to create a forum entry and will start working on it. My first priority would be to add BSP, since then you can access the site and work from the cloud.


mbed OS Developer Site

bonjour, je suis un nouvel utilisateur de pine 64 je recherche ou branché un ventilateur sur le pine.
merci

Does anyone know if there have been any patches to the kernel Debian Jessie 3.10.102 for the "Dirty Cow" exploit?
I've done the usual "sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade" , but don't know if there has been a patch applied for this bug.

Hello all,

Bought the plus version a while back and now found a good use for the LCD, playbox and of course a Pine 64.  Was wondering if there are any add on microphone options?  Ideally something that will fit in the playbox.  I'm not opposed to doing a bit of drilling I need too.  I have a Dremel and not afraid to use it!

I did find this for the Adafruit, would this work?

https://www.amazon.com/Adafruit-Electret...microphone

Cheers!

Paul

I have developed a simple GStreamer application. Works on laptops, desktops and Raspberry Pis. On PINE64 it works too, but only with autovideosink under X, not glimagesink under X. The error is

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 23 requests (22 known processed) with 0 events remaining.

This application is fairly simple, hence that it is a good way to test support for GStreamer by a certain distribution. Source code can be found at https://github.com/z25/gstcam

Note that I have configured my system according to https://github.com/avafinger/guvcview_2.0.4/issues/1 and use that particular USB camera. The application works (only from terminal in X) with the -a option. :-) It does not work from a normal terminal (Error: Failed to conenect to X display server)

The error above occurs when (from X) this application tries to use glimagesink. What is the reason that this occurs? The application should switch automatically to autovideosink when there is no glimagesink. So there is support for GL but somehow barks runtime. Any thoughts?

Solving this will increase support for GL on PINE64.

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?