Good news for openHAB on pine64.  The raspberry pi automated install has been updated to support the pine64.

This means a complete image including Ubuntu and all openHAB prerequisites.  Only takes a few minutes now to get things running.

Details here:  http://docs.openhab.org/installation/pine.html

And here:  https://community.openhab.org/t/openhabi.../13379/737

Hello All,

I have seen the SOC had hardware support for IS7816 Smart Card Reader. How can we connect a Smart Card/Sim Card and how can we succeed to communicate whit SC.

Are there any drivers to use this hardware directly ? 

I emailed the company earlier this week and haven't gotten a reply. What is the expectations from the company about being able to supply in bulk for product integration? I likely won't need a lot of supply; maybe 2000-5000 per year. But I do want to know this before I proceed down the road of using the Pine.

Hi,

   This is a copy of a thread that I posted on the Slimdevices forums.

For those of you who don't already know, the Squeezebox Touch was part of a family of devices developed by Slimdevices and later bought by Logitech.

The provided high audio quality output at very reasonable price and could play a large number of formats from a number of sources, including local archives and online streaming services and were highly configurable.

Unfortunately the line was discontinued by Logitech in 2012.

The Squeezebox Touch was introduced in 2010 and could output high bit-rate digital streams in audiophile quality, over COAX, optical fibre or USB, in addition to its own, builtin DAC, which could handle standard bit-rate and output stereo analogue in high quality.

The server-side "Logitech Media Server" and much of the player software was open-sourced when the products were discontinued and there is a lively community effort, keeping the project alive. Code exists to clone the squeezebox touch functionality to a number of devices, including a range of "Pi"s.  The Pine64 has not been supported up to now.

The Pine64 hardware is well suited as it has ample processing and RAM headroom and dedicated USB ports , directly hardwired to the SoC and an independent bus dedicated to the Gb Ethernet port (if we discount the LCD screen).  It is also much cheaper than competing products.

I'm sharing my work here, in the hope that someone might find it useful and that others will join me in making the Pine64 one of the best choices for a Squeezebox-Touch replacement.

Although my system will output to a USB DAC and connect to Ethernet network only, it would be relatively easy to connect a DAC HAT for analogue output and include wifi.

• glued screen into front bezel
  
• countersunk m3, flathead bolts
  
• ordered custom aluminium stand to hold device in "alarm-clock" position (not yet delivered/mounted)
  
• 5v Power supply through EULER connection pins
  

• Implement power filter as described at:
  http://forum.pine64.org/attachment.php?aid=439
  

• apt installed:
  libsdl2-dev libsdl1.2-dev liblua5.1-dev liblua5.2-dev libluajit-5.1-dev libsdl-image1.2-dev libsdl-ttf2.0-dev libsdl-gfx1.2-dev libexpat1-dev libtool libtool-bin liblua5.4-dev liblua5.3-dev
  

• apt removed:
  blueman bluez bluex-obexd bluez-tools bluetooth libreoffice* openoffice.org-hyphenation firefox:armhf
  

• built and installed ARM64 luajit from:
  https://github.com/sindrom91/LuaJIT
  

• built and installed jivelite from
  https://github.com/ralph-irving/jivelite
  

• dpkg installed tslib-X11 packages from:
  https://github.com/avafinger/pine64-touchscreen
  
• configured xorg.conf to use tslib
  

• Built minimal  kernel, with performance governor default, removed builtin snd_usb_audio and hid and compiled as loadable modules (necessary for DAC detection).
  
• Much removed: including Wifi, Bluetooth, Filesystems and network protocols that I will not used.
  
• dpkg installed using technique described at:
  https://www.armbian.com/pine64/ > Kernels > Default
  

• turned-up LCD backlight to 100% using technique described at:
  http://forum.pine64.org/showthread.php?tid=2896
  

• Modified /etc/default/nodm to disable mouse cursor:
  # Options for the X serverNODM_X_OPTIONS='-nolisten tcp -nocursor'

• edit /etc/rc.local -
  #allow squeezer user to set screen brightnesecho 362 > /sys/class/gpio/export && chgrp squeezer /sys/class/gpio/export && chmod 220  /sys/class/gpio/exportsleep 1echo out > /sys/class/gpio/gpio362/direction && chgrp squeezer /sys/devices/soc.0/1f02c00.pinctrl/gpio/gpio362/direction && chmod 664 /sys/devices/soc.0/1f02c00.pinctrl/gpio/gpio362/directionsleep 1chgrp squeezer /sys/devices/soc.0/1f02c00.pinctrl/gpio/gpio362/value && chmod 664 /sys/devices/soc.0/1f02c00.pinctrl/gpio/gpio362/valueexit 0

• Created ~/.xsessionrc for autologin user:
  #!/bin/shsleep 2 && exec /opt/jivelite/bin/jivelite #sleep to allow LCD backlight settings to take effect

• resized some wallpapers to 1024x600 resolution and modified wallpaper loader
  

• Included LCD screen backlight off/on to:
  BlankScreenSaverApplet.lua
  

• Tuned text scrolling by changing refresh rate and scrolling values, for smoother scroll.
  

• System boots
  
• Squezelite loads
  
• Jivelite loads
  
• 1024x600 skins mostly look nice (much work done by Ralphy since this thread was first announced).  Thanks to Ralphy
  
• Connects to LMS running in local network
  
• "Plays" local and streaming content.
  
• Blank screensaver works well and turns off LCD backlight
  
• Touchscheen works well if jivelite runnning in context of autologin user
  
• Gb ethernet works well and correctly.
  
• PCM playback tested and working up to 24b@384k
  

• USB audio out tweaks as discussed at:
  
• https://ubuntuforums.org/showthread.php?t=1608913
  
• working, fully patched RT kernel (reverted to standard, low latency kernel)
  
• 3.13 USB improvements patch backported to 3.10.104
  
• PWM management of LCD backlight brightness
  

• Jivelite scrolling text is still slightly jumpy.
  
• Some screensavers (analog clock) not optimised for 1024x600 resolution.
  
• Some graphics not positioned correctly on 1024x600 resolution
  
• Can't get touchscreen to work if loading jivelite as root (even with tslib_test behaving correctly and loading with tslib environment variables)
  
• Jivelite splashscreen not correctly centered when running in context of autologin user (looks better when loading from root shell).
  
• Top LH "stop" button in jivelite UI works, but if a "stop" screensaver is configured, touch does not wake the screen  
  
• DSD (native) playback is being silently converted to PCM on my system due to non-XMOS dac and (probably) kernel 3.10  It still sounds good, but this is not native DSD. I have ordered a XMOS DAC and will look at ways to backport the native DSD support from a later kernel if Armbian can't supoort the LCD on 4.x before I'm done.
  

Does anyone know how I can start helping and sorry for posting this the website is confusing.

I just installed the latest armbian release  ( the desktop xenial I think). I can't get the touchscreen to work. The touchscreen I have is the one from the kickstarter ( i don't the specs right now). I added the gt9.. to the text file and I still get nothing. Is there another way?

In case anyone is searching for a way to emulate GB/GBA games on longsleep's Ubuntu, I can confirm that VisualBoyAdvance works fairly flawlessly. Because I'm using the 512MB board, I noticed a bit of a performance hit when emulating with a full Desktop Environment. To combat this, I'm using the very bare-bones XDE Windows Manager. The only issue I'm having currently is that it's not very convenient to use in a living room environment, as a keyboard (or SSH) is pretty much required to get everything setup (Mostly, selecting the ROMs). I'm sure a combination of a lightweight DE and some startup scripts can get it all working together without the need for keyboard input, though. 

If anyone knows any methods to navigate a GUI-less Ubuntu environment with an x-input device, I'd appreciate the input. The ideal setup would involve a startup script that could read the contents of a folder, select wanted ROM with the x-input device, and pass the selection to the pre-configured VBA emulator. 

Please let me know if I can provide any help or additional information.

https://learn.adafruit.com/adafruit-ulti...spberry-pi
since the pine 64 uses the pi2 pinout, would this work with my pine64 2gb?
Im looking to make a cheap but reliable NTP server to provide accurate ime to other ntp servers on my network.
Thanks

http://wiki.pine64.org/index.php/Main_Page#Android_6.0

It now has a "Android 6.0.1 Image (LCD and HDMI Video Output) Release 20170209 [ver 2.0.1]" (below the 6.0 Image

I am trying the DD image for 32GB microSD Card. 

Resolution looks somehow low to me, even after changing to 1080p, when I connect via VNC it also looks low. Not sure... Will try some more...

Looking forward to other user's experiences with this OS image!

When attempting to develop via QEMU I get this error.     

I am currently using the Tianocore UEFI boot for my OSX Sierra VM and was wondering if I could also use it for this VM? I am looking to continue longsleep's kernel development work and create an up to date image for Arch Linux using the latest kernel. This is my only hangup so far so I can develop at full speed on my main Linux workstation.