Hi,
I've a Pine64+ 2GB, with RemixOS on board. It works well, but the WiFi Module does not receive any signal. I've inserted correctly the uFL connector to the WiFi Module, but nothing happend.
I have a Router on 2.4GHz, with a distance of 15mt. My Smartphone can reach the signal with quite-full power, but the Pine64 not.
I've bought another antenna with uFL connector:

2.4GHz Mini Flexible WiFi Antenna with uFL Connector

but I cannot get any signal. The only signal I can reach is the AP smartphone closer to about 1mt.

Somebody can help me?

Been using Ayufan's A6.1TV HDMI build for quite some time now. We use it primarily for Kodi and Netflix. Until last night. 

Last night I noticed the board was off. This was odd to me because we let it run continuously, 24/7. But the other half has been known to unplug it before, so I checked the power supply. Still plugged in to the wall with the OEM power supply. Hmm... Check the supply at the board. Yep, still plugged in. OK.... Let's power it on with the power button, holding the button down long enough for the red led to brighten slightly after initial power-up. Ok, Samsung TV seems to recognize incoming signal (1080/60p). After a few moments of no activity, the tv said "no signal." I looked at the pine, and the led power indicator was out.

What?????

Maybe retrying the previous process will do the trick.

Nope.

Hmm....

Maybe the PNY SD card went bad. Let's try the Samsung Evo SD card with WiKi's Rooted A5.1.1 LCD build burned on it.

Hey! The LCD still works! Booting hangs on the PINE A64 screen for a couple minutes, but A5.1.1 LCD eventually boots. Of course, still no HDMI display, but I know it's not meant to have HDMI & LCD outputs simultaneously.

Ok great, my pine didn't destroy itself or something.

Let's try the PNY SD card again with Ayufan's A6.1TV HDMI.

Same as before. Nothing and shut off on its own.

Ok, let's try the official Pine 64 SD card with Rasbian burned on it. Yep, that works. (I'm illiterate with that os, so I don't use it)

Ok...

Let's use Apple-pi Baker on OSX 10.12.4 to burn Auyfan's tried and true A6.1TV HDMI build on the official Pine 64 SD card.

After successfully "baking" my pi, I double checked the .uEnv file on the BOOT disk for uncommented 1080/60p (per my tv). Ok, that's good to go. Eject "BOOT" from MacBook.

This is it. It's going to work.

Nope. Exactly the same outcome as my original PNY SD card with the same, long-time working, A6.1TV HDMI build from Ayufan.

It's time for bed, let's ask the community tomorrow.


Does anybody have any ideas as to why my pine will not boot A6.1TV HDMI and even shut off shortly after powering on?

Sorry for the lengthy post, I just wanted to be as clear and accurate as possible while conveying my issue to you guys (and gals).

Thanks!

*ETA*


I just burned WiKi's Android 7.1 TV. Uncommented 1080p60 and booted. Kodi is up and running again. Still curious as to anybody else had the 6.1 issues I experienced and or solutions.

Thanks!

Android 7.1 (PINE A64(+)) v0.3.5-r61

Edit: This release includes Android 7.1 TV.

Anyone know what the reason was that MATE was chosen for the desktop environment?
I just installed LXDE and it looks like right off the bat it has a good 250-400 MB more RAM free after initial login. Seems like this would be a better choice for slim hardware like the Pinebook has.  I haven't used it for more than about 15 minutes so far, but seems to be much snappier.

Don't get me wrong...I'm not hating on MATE. I use it at work on my Dell desktop with full Compiz effects too.  Love it.

I spent some time playing with different browsers and exploring youtube playback options, and in this post I list my findings. Although Chromium is quicker than Firefox on the Pinebook - especially if you put in time to do some modifications - to my knowledge, it lacks a good plugin for easy playback of youtube (and other) videos using external player. I looked all over, read countless threads, but found just one plugin utility for chromium that kinda-sorta works.  However, it requires a lot of setup and is not a simple click-and-play solution because it requires you to have VLC launched in the background as well as a VLC server running at localhost:8080. I generally found it quite unreliable. 

So I moved onto Firefox. For starters, I did some tweaking to improve Firefox performance from terrible - to usable. Some things can be tweaked from the settings panel while others have to be enabled from a hidden options list. The very basics can be found in Preferences -> Advanced and:
In general: disable Smooth Scrolling
In Data Choices: disable Firefox Health Report

For the more advanced tweaks one needs to enter about:config in the URL bar. There is a search bar at the top so you can look for the settings I list below.

For starters you may want to make sure to prevent pinch-to-zoom behaviour by setting:
zoom.maxPercent to 100
zoom.minPercent to 100

Then find and set the following:
network.http.pipelining true
Network.http.proxy.pipelining true
network.http.pipelining.maxrequests 8

Its also worth adding the following integers by right clicking anywhere on the about:config page, selecting New -> integer:

content.notify.interval 500000
browser.cache.memory.capacity 65536

Lastly, similarly to Chromium, it’s a good idea to move cache to ram by setting the following:
Browser.cache.disk.enable false
Browser.cache.memory.enable true
Browser.cache.memory.capacity  -1

The last variable can be tweaked; value of 100000 = 100mb RAM. The -1 value, as I understand it, refers to dynamic allocation of RAM usage. I don't know what the optimal setting for this ought to be.  Also, you can find out more about how much ram is used and other options by entering about:cache in the browser bar. 

Now that faster Firefox performance is improved (subjectively, when running off of eMMC, it’s on par with Chromium in Mate DE) we can move onto enabling playback via VLC player.

The plugin needed to achieve this is called VLC Youtube Shortcut. Extensive instructions are not needed for getting this to work - after installing the plugin, you will be able to just right click the youtube (or other) video in Firefox and select Play Video from link from the drop-down menu. 

To get good playback in VLC some tinkering is needed … but that is a topic for a different post.

Enjoy.

Android 7.1 (Pinebook) v0.3.5-r61 (SDCard). Note that, this build is for SD Card boot.

Thanks to Ayufan for building this image. Please visit the GitHub for more details about this image.

Edit:
Special thanks to Icenowy, lennyraposo, longsleep, lukasz, tkaiser, Xalius and PINE64 community contributors.

MD5 (GZip file): d052aa92041e20858dd2a0947be4dd15

Hello everyone!

Loving my pinebook so far, q4OS runs beautifully and the hardware is surprisingly nice for the price point!

Unfortunately the keyboard now has 2 dead keys (a and s) days after my warranty has expired. 

Is it worth breaking open the pinebook to see if I can reseat the rubber dome or clean the connection or am I SOL?

Thanks.

EDIT: the keyboard actually has 3 dead keys, Caps, A, and S.

There was no trauma to the unit as far as I am aware.

Hey all

I purchased a 14" Pinebook and noticed there wasn't a plug type available for the UK (chose EU since it's the closest I could adapt). I was curious if anyone from the tea nation had bought a UK barrel power adapter that worked with their Pinebook?

I've had some pretty so-so experiences buying power adapters so wanted to see if anyone had any recommendations, preferably eBay or Amazon. Looking forward to its arrival!

Oh and anyone who did receive it, did you receive a DHL tracking code?

Sent from my ONEPLUS A3003 using Tapatalk

Anyone knows which images (both Android and Linux) can be booted from SDcard and which can only boot from eMMC?

I want to use i2c-0 as well as i2c-1 in my project. i2c-0 connects to the TP port for use with the touchpanel by default. On the baseboard are 2k pullups between the TWI0-{SCK,SDA} pins and VCC-CTP.

I found that with with the pull-ups installed (R96 and R97), external pull-ups to 3v3 just create a voltage divider and the TWI0 pins don't go high enough for the A64 to detect the i2c bus is idle. (I first tried removing the ferrite bead, FB3, attempting to sever the connection to VCC-CTP, but that didn't make a difference.) I suspect the problem is that VCC-CTP isn't enabled and is instead acting as a strong pull-down.

So here's what I did to make TWI0 functional from Linux on SO-Pine + Baseboard; I think the same should work on standard Pine64.

1. De-solder R96, R97, and FB3.
   
2. Solder wires to the center 2 test points on the group of 6 directly behind the TP connector on the bottom of the board
   
3. Connect your wires to external pullup resistors to 3v3. I used Pin 0 on the Pi2 bus for 3v3.
   

Attached Files

Thumbnail(s)