I got Dokuwiki running on PHP7 and Nginx, and it rocks. I have my main wiki running on a RasPi2 and page loads take a second or two and page saves take 2-3. On the Pine64 2GB it is under a second. What a difference!
If anyone is interested, I can post the instructions.
twice now the lay store says I need to authenticate when I try to install something, and then it doesn't. all other google sign in stuff seems to work fine, just the play store. only a reboot fixes it and then the thing installs fine.
arg! now it's sucessfully installing one thing, then nothing else!
I'm also now getting a generic error with a link to a web page that tells me how how ot make sure my network connection is OK. a web page. on the internet. that loads fine. thinks my network isn't connected.
I realize that one is all google's fault, but damned. this is nuts.
I ran the Stagefright Detector app against my Android install and I got back vulnerable to CVE-2015-3876, CVE-2015-3864, and CVE-2015-6602. CVE-2015-6602 in particular makes the system vulnerable to malicious MP3 and MP4 files!
Stagefright patches are freely and publicly available. Not applying them is dangerous. Will these vulnerabilities be addressed any time soon?
Hey guys, I received my Pine in the mail yesterday only to discover that I've misplaced my wondrously important 8GB card. Only one I have on hand until my Amazon order comes in is a 2GB one, and I'm curious if there's an OS image out there yet small enough to run on it.
Doesn't have to be anything special, even just a command line to tinker with would be fine. Preferably Linux based.
my Pine doesn't boot as soon as I connect the Wifi/BT module.
Linux does a cold reboot when starting the kernel module for Wifi/BT (~15..20 after power on).
I tested different Images (Arch, Debian, Android) with different Pine A64 (1GB and 2GB).
Did I miss something or is the Wifi/BT module defective?
Hi! I've tried Remix OS, Android and Ubuntu on my Pine 1GB. Every OS has only one trouble: display settings. I've tested 2 TVs. 1st one (Samsung) got error in every case (unavaliable mode), 2nd one (NONAME) shows every OS, but the resolution is very hi for it and picture is not very good.
Samsung have supported every mode before it, and I was looking for a reason. I've conected my nootebook and started to try every mode. Resolution doesn't depends on it, TV keeps every resolution good. Problem was in frequency rate, in low resolutions high frequency rate was good, but for high resolutions max frequency is 30. If set frequency >30, TV sets off and shows message: Unavaliable mode.
Sorry for my english.
Is it possible to solve this problem? How can I change resolution or frequency of HDMI on PINE?
Quite a few people have reported problems and been unable to determine if their Pine was functional or not. The easisest way to monitor your pine is with a USB to TTL serial adapter. There are many types of these for PC's on MAC I am unsure but if someone has knowledge in that are please post and we will try to get a Mod to sticky this.
Things you will need. A PC. A terminal program able to access COM ports and a USB to TTL adapter for 3.3V. Cables and wires needed to hook it all up.
I have also in the past used a FTDI232RL ( http://www.ebay.com/itm/FT232RL-3-3V-5-5...SwrklVMjIp ) which also has lots of drivers available. There a many adapters out there that only support XP through Windows 7 so pay attention to what others you buy. If unsure ask here and hopefully someone will know if it will work.
Connect your serial adapter of choice to your pc and get the drivers setup. When you are done you should be able to find the device in device manager and it will tell you what COM port it is associated with.
Whatever solution you choose you need to make 3 connections to the pine. These are hooked up in this manner. RX on FTDI/CH340 to pin 7 on EXP connector TX on FTDI/CH340 to pin 8 on EXP connector Gnd on FTDI/CH340 to pin 6 on EXP connector
I use Putty for a terminal program I set it to connect to COM4 and set the baud rate to 115200 and connect.
Then power up the Pine, you should be watching text fly by. If you are troubleshooting after the boot stops read through the scrollback and find where it mentions errors, you can copy/paste them here or if you are grabbing more than say 20 lines use http://pastebin.com and post the link here along with your issue.
I am attaching a boot log to show you what the output is like.
Sorry if this is a bit rough but wanted to get it posted during my lunch hour. I am thick skinned and open to any comments, suggestions, additions, criticisms etc. So speak up. As far as I am concerned we are always learning, there is nobody who knows it all in tech.
