VPN issue on Pine64
I was trying to use OpenVPN client in the latest Android(04/28) build and the OpenVPN status shows as connected. However, I am not able to connect to the Internet with VPN 'ON' . I had the same issue with RemixOS. I am not sure if the VPN provider is blocking or is it something related to Pine64. Does anyone have this issue or is there away to find the root cause of this problem(probably a log or something).

Specifics:-
Pine 64 - 2GB
VPN provider - PIA VPN
OS - Android, 04/28/2016 image flashed using Phoenix card.

I noticed there was a new build of Xenial 20160502 but there wasn't a torrent available.  I've created xubuntu-xenial-20160502-longsleep-pine64-8GB.torrent for everyone.

Enjoy

Hi, 

I have installed the rooted android OS from the Wiki and while I was able to download 2 apps from the play store 90% of the things I try to download just crash the store (no error, just crashes).  

How can I debug?

Am I better off with the non-rooted version?

Happy to say it arrived today, along with a case and wifi board (I really don't like that wire antenna)

I honestly don't know why, but I thought this was going to be small board, smaller than a Raspberry Pi, boy was I wrong.

its a monster...
I can't understand why its so large, given every other SBC maker has made their boards small and compact?

Anyway, pleased its here at last, will go hunt for an image and boot it up.. It certainly looks cool in its big perspex case

Here it is compared to a Nano Pi M2

This is my first post on this forum. I received my PINE 64+ 1GB last week and I have installed Ubuntu Linux.
Today the Shop just launched and I found an HDMI to VGA adapter. It would be great to see my PINE working with my old VGA monitor.
I think that you should change the resolution via the settings of Ubuntu. But the only resolution avaible seems 1920x1080, which is unsupported on the VGA.
The VGA adapter on the Shop website, seems a classic passive adapter with no convertion/downscaling. It only has the "add on" of the Jack output.
So I think that any generic VGA adapter is the same to this.
So, I am asking...
Some of you have already tried to use a generic HDMI to VGA adapter? It works?
Here a photo of the adapter on the website.



Inviato dal mio CHC-U01 utilizzando Tapatalk

I see that the forum has been changed, have you migrated all the posts from the old forum?

Has anyone setup I2C on Ubuntu yet?
I'm not a Linux expert, so I'm sure I'm missing something simple.

I've installed i2c tools.
When I do i2cdetect -l, it doesn't find anything.

However, looking in /sys/class, I can see i2c-0 and i2c-1.

Do I need to comment i2c out from the blacklist?
Is there something else needed?

Thanks!

The store does not seem to currently have the IR peripheral as something I can buy. Is there something special about the device or is it possible to add a standard IR receiver? Is it planned to sell the official receiver in the store soon?

Was thinking of making something like this: http://www.instructables.com/id/Raspberr...tificatio/ with my new Pine.  Having the Android OS available is cool for this type of project as I can use a number of ready made widgets rather than doing lots of coding.  However, control seems to be the issue.  Most of these projects use simple buttons via GPIO which seems difficult with Android.

Here are some ideas I have for control:

1) Touch screen, this would be coolest, but anything even a decent size (say 18") is going to be really expensive.
2) BT mini keyboard - sort of awkward to mount.
3) Some type of mountable touchpad (not sure if one exists).

Regarding the monitor, do you think one like this would work? http://www.amazon.com/Dell-E2014T-Screen...00FE8MLY6/

Other ideas for how to deal with the input issue if I was to use Android?

using 20160501.  boot up with no ethernet, connect wifi, and connections all fail

reason is that eth0 is setup in interfaces and for some reason if creating a default route to nowhere, and the wifi adds another default route, and I'm guessing the kernel routing table prioritizes the wired.

solution:  comment out the eth0 lines in /etc/network/interfaces and let network-manager handle it, the it can be manually disabled if needed.