Hi, first off I am brand new to this. I just got my Pine64 this week. Also, I have a Mac and I have tried putting RemixOS and Android on the SD card with the Mac using Apple Pi Baker. Both times, I see the logo (either android or pine64) and then it shows a box that looks very pixelated. It tries to reboot once and then after that it shuts itself off. 

I just want to make sure I don't have any other problem. I am currently downloading RemixOS on my Windows laptop and I am going to try PhoenixCard. It is a really slow computer so it is taking a much longer time than my Mac did. I just wanted to see if anyone had any quick thoughts about what could be going on.

I'll try to answer as many questions as I can and I am really trying to learn all of this. I'm not new to computers, but I am new to Pine and I am not a developer.

Thank you!

I got my order 2 days ago and first thing I did was to try if everything works right. 
I got 4 Pines (2GGB version).

After I successfully created 3 Sandisk 16GB (uhs-1 uU3) android sd cards with the latest build, I started testing them
All 4 booted flawlessly within seconds. However, only 2 of them can browse the internet and connect to Play Store.

They do get an IP assigned while date and time get also synchronized, nevertheless it is like if they are not connected to the internet at all! I'm unable to browse any site (not even Google) and Play Store displays connection error.

After I saw this behaviour by 2 of my Pines, I decided I will run all 4 under the same circumstances (same 20awg usb lead, Anker 2.4A PSU, connected to my Gigabit switch with a specific 50cm Cat7 Ethernet cable, same microSD)

The same 2 that initially had problems, persisted the same behaviour (got IP and date/time but no internet)

I subsequently tried the Wifi/BT module with those 2 and successfully connected to the internet.

At this point, I started believing there is a problem with their Gigabit chip. It was then that I thought I had to try another OS. I burnt an image with xbuntu (latest longsleep's version). The 2 specific Pines booted within seconds and connected to the internet successfully. I browsed the internet with Pidora and they were quite responsive.

However, when I tried a speed test (speedtest.net) I got only 0.5/5 and 5/5 respectively while my usual speeds are 74/5.

That said, upload speed doesn't seem to be affected. Download is hammered though!

I have seen some users recommending one should push the Gigabit network to 100Mbit in order to achieve decent download speeds. Despite I don't know how am I supposed to be doing this, I am willing to try.

The question is why 2 of my Pines perform excellent within my Gigabt network while the other 2 don't?
Is there a possibility those 2 being faulty? With just 30 days of warranty I don't have much time to experiment or wait for updates. If there is no solution soon I'll have to send those 2 back as they clearly underperform under pretty much all conditions.

ANY RECOMMENDATIONS BEFORE I PRONOUNCE THEM FAULTY?

Has anybody found a way to mount a network share using either NFS or CIFS under Android?

I have a NAS with various shares on which I'd like to make accessible to my Pine64. This would give me far greater storage capacity than an SD Card, plus it makes sharing files between other devices easier. I realise that apps such as ES Explorer can access network shares, however mounting is preferable since it would then mean the data is accessible immediately without having to ES Explorer to upload/download first.

I have Android rooted and I've installed the Termux terminal emulator app. Normally I would be able to use the following mount command but it fails with a "No such device" error:

mount -t nfs [ip address]:/[share] /mnt/nfs

I suspect this is because the kernel does not have NFS or CIFS support, since running "cat /proc/filesystems" does not include either nfs or cifs in the list. Are these available for download as kernel modules somewhere?

Been horsing around with my Pine64 for about a week.  Spent several hours on it at home and a few at work too.  After getting an image to finally boot fully, I worked backwards and determined what some of my problems were.

CLIFF NOTES

1) HDMI Display: It was only after my 4th or 5th trip to these forums that I realized that you have to have a 1080p (or better maybe?) display.  My TV at home is old and only does 720.  You may occasionally see digital garbage on the screen but you will never see a proper image, like that white Pine A64 screen you have been waiting for

2) The power supply thing has been beat to death, and my hang up ended up being the cable.  I went to the store and specifically bought a larger gauge cable they said was better for charging, high power etc.  In actuality, it was worse.  If you think your power supply should be up to snuff, start swapping the charging cable.  The one that eventually worked for me is the one that came with my old Samsung S2 five or so years ago.

3) If you are really stuck on the power supply, go to the Dollar Tree and buy a $3-$5 USB battery booster (backup? whatever) that they make for plugging into a cell phone. A battery has the ability to provide the necessary current (even for a short time) that many power supplies do not have.  I ran the board a good 30 minutes off one of these and it wasn't even fully charged.

So... symptoms...

The majority of my time was wasted at home with the insufficient display.  I am confident that at least one of my configurations would have booted early on if I had the proper display.  What you will most likely see is your red light coming on and staying on as if the board is properly powered and working.  On the 720 monitor, 99.9% of the time I just saw a black screen.  I kept trudging along because of that .1% of the time when the screen showed digital garbage, as if it was trying to boot the display or something.  It was mostly green blotches like you see when your satellite starts to go out in bad weather.

After getting past that and bringing the board to work with a shiny new 1080p monitor, every attempt at least brought me as far as the Pine A64 screen (when using RemixOS), or to the Allwinner Powered by Android screen (when using the Android 5.1 image).  Sometimes, the board would shut off (red LED and all) after a few seconds, others it would just hang.  These could both be signs of insufficient power.  During my week of frustration, I went to the store and bought a dual 2.1A power supply made for charging old Ipads.  The discount electronic store still had these despite the fact that it comes with the old 30 pin connector.  It has USB of course, so I just tossed the iphone wire and used the "supposedly" beefy wire I bought at the same time.  My first hint that my problem could have been either of these items was when it took twice as long to charge my blackberry with this combo than it does with my old Huawei android phone charger.  If you bought new equipment to play with this, test it out with your devices and see how long it takes to charge your phone, tablet or whatever.

Day two at work I decided to bring the battery booster thingy.  I continued to use it with my 'new' wire, and the board would stay powered instead of shutting off after 10-20 seconds.  However it would hang at either of the splash screens mentioned above or get to a blank white screen on Remix.  Once it started writing the word remix (which is what its supposed to do if you haven't seen it go that far yet) and then died during that.  I read somewhere that if you are flat out stuck, load a Linux distro on to the SD card and try that.  I downloaded Debian (the first one in the Wiki download page I think) and rather than a splash screen, it goes right to a running stream of text like Linux often does during boot.  It shut off once during this and permanently froze a second time. 

It was at this point that I went out to my car and grabbed my old samsung wire for something different. Using this and the battery, the board booted up on first attempt.  It did stop during boot at the same point in the stream of text, but them went on to a black screen and finally the login screen.  After successfully playing around in Debian, I fetched my other SD card with Remix on it and popped it in.  This also loaded first attempt.  From there I worked backwards and swapped out the battery for the ipad charger I bought.  Success there as well. 

The moral of the story is that any one little thing can make these boards grind to a halt.  I think the things you want to look for in order are the red light staying on rather than shutting off, then make sure at least you see the corresponding splash screen for the OS you chose.  This should come up on screen within 2-3 seconds.  If it does not, either your write to the card is wrong somehow or possibly you need to play with another TV or monitor.

Hoe this gives a couple of extra hints that I didn't see elsewhere.

Hi together!

I just tried to create an automated system with Android for navigation.

Model: Samsung Galaxy S4 Mini
ROM: I9195XXUCNE6 (Android 4.4.2)
Rooted: Yes (needed for AutomateIt Pro)

The device will boot on charge (I had to edit the file /system/lib/lpm) and if booting is done, AutomateIt Pro will activate Bluetooth, GPS and HERE Maps (in drive mode).
The device will also shutdown automatically after disconnect the power charger.



What is the "Drive mode" in HERE Maps?
- Normally you will just see your position in HERE Maps after starting the app.
- Starting the "Drive mode" will show you your speed, elapsed time and more.
- Usually you have to start this mode for yourself, but don't use your fingers on your phone if you drive!
- So, I found a way to start the app (via intent) in "drive mode" per default with AutomateIt

How to find out a way to start apps in specific modes? You need the "intents" of the app!
- Download .apk file of the app (I created a backup of the app and copied it to my pc).
- Rename the .apk to .zip.
- Unpack the archive and take a look into manifest.xml.
- Search there for the "intents".
- Find the correct intent (just trys & error).

It was a little bit difficult, but not impossible


I'll try to create a tutorial for Pine64 also, if you're interested in my solution.
Please let me know your feedback and questions!


Best regards
Julian

Hi,

I got the backed pine64 512, pretty exited tried to boot using the Debian image provided but no success with all the attempts
1. Used 5V 2amp adapator with cable the Red led goes of after some time
2. Changed cables as per the support from luke and bought 24 AWG cable the board keeps rebooting for couple of times and shuts down completely
3. The power management IC heats up like its going to blow up, but good it has the functionality of shutting down crossing certain temperature ..
4. Strongly feel there is an hardware issue with the 512 what I have received and nothing to do with the power when it is able to boot up Pi3 with the same adaptor
5. tried with 65 and 101 images, no results even after multiple booting
6. no other peripherals connected, still no success
7. Connected only ethernet, but still no success with same results
8. Have checked the serial output during boot it stops at cooling the cpu and shuts down with RED LED going off

can somebody suggest or help here to resolve the issue

using the devboard as a interface board and the pine64 as the brain to controll the ptt/sql and optional interface inputs and outputs allow you to control multi vhf/uhf/hf radios as a repeater unitand a radio beacon unit.

I compiled the usb wifi driver for system,but make filed,information of error is 

make ARCH=aarch64 CROSS_COMPILE= -C /lib/modules/3.10.101-3-pine64-longsleep/build M=/home/pine64user/Downloads/rtl8192eu  modules
make[1]: *** /lib/modules/3.10.101-3-pine64-longsleep/build: No such file or directory.  Stop.
Makefile:1335: recipe for target 'modules' failed
make: *** [modules] Error 2

Can someone help me please？

THanks

This is a very simple use and in no way original, but I thought I'd share it anyhow since it doesn't require very complex setup. You'll need one or more Android phones/tablets to control the setup, too.

Starting with any Debian image, SSH in and install deluge, deluged, and deluge-web:

Hi guys,

I'm trying to stream H264 video off of a USB webcam to my computer from my PINE64. 
I'm on longsleep's ubuntu and video packages (https://launchpad.net/~longsleep/+archiv...our-makers).

I've tried using gstreamer1.0-vaapi plugins, as well as this https://github.com/ebutera/gst-plugin-cedar, 
but I've been having trouble getting the encoding element to work properly.