Hi - I've noticed what I think is somewhat unusual behaviour in my 14 inch Pinebook.  When I plug the adapter in, the orange charging light doesn't light up to let me know that the machine is charging - at least not until I've done a couple of things.  

When the machine is shut down and I plug the adapter in, I get no orange led.

When I open the pinebook up, I get a brief flash of what looks like a battery charging icon but the LED stay unlit.

When I start the pinebook, the LED lights up orange and stays lit after I shut the machine down - until it is fully charged and the LED goes off.

Is this normal?  Has anybody else experienced this?

D.

I received my Pinebook a few weeks ago and have enjoyed playing with it, and of course pulling it apart. It's nice to pull apart something that humans can actually work with, pretty nicely made with no glue. All in all a great platform for hacking. Congrats to the builders and devs, well done. On the default Ubuntu Mate, I installed Misfit3D and Meshlab OK, a couple of 3D packages I use frequently, as well as Openshot and Audacity. Just for fun I installed Red Eclipse and managed to get 4 fps, though I didn't really expect it to even run at all. I tried a few other distros, including Bliss (misnamed in my opinion) and Android and the experience was still disappointing.

Then I remembered there was a Puppy Linux version for ARM. Barry Kauler, the developer of Puppy built an ARM version for the Raspberry Pi, Quirky, this is his post announcing it - http://barryk.org/news/?viewDetailed=00441 I have used this on the Pi and it works well so I tried to boot the Pinebook with the image, but without success. Would be interested if anyone else has had a try?  I looked in the Puppy forums and could only find a mention of of the Pine64 board but no post relating to running Quirky on the Pine platform.

Sorry if this has been answered (I did use the search feature)

I have loaded ubuntu-mate from 0.4.15-17 through 0.5.5 and have been seeing the same behavior with desktops. 

Initially everything is OK, I can open terminals, apps, etc... After some period of time, the screen will not respond to mouse click or allow focus (via mouse click). 

Moving the mouse causes the screen to wake (from powersave mode), and the mouse moves. Also The screen continues to redraw, i.e. if I have a sysm monitor on the screen I see it updates. I cannot click on an open terminal, or do anything except move the mouse around. 

The system is still responsive -- I can ssh into the rock64. 

Is this a know issue? Is there a fix?

Many thanks,
Scott.

P.S.> I always started with a minimal image, and used install-deskop to get mate up an running.

Anyone recommend a brand name micro SD Card that works with Android?

Can someone post changelog of rk3328_box_nougat_v1.10_170630.xml
and check if it is worthwhile to upgrade sdk from v1.09?

What is "xenial image"? Is it core update for ubuntu?

Greetings,

I ran into a small glitch while trying to manage wifi connection on my new xenial image using the i3wm  tiling window manager;  my ubuntu-mate image connected fine ( same hardware ) but I could not get the connection to work using the cli wpa_supplicant that I am used to.

The solution is really simple , as it turns out;  use the cli version of Network-Manager !

First, I reinstalled Network-Manager;  you may not need to do this step :

       sudo apt isntall network-manager --reinstall

Then bring up the wlan0 interface :

       sudo ip link set wlan0 up      (optional)

and lastly start the connection with the nmcli tool :

       nmcli d wifi connect <ssid> password <passphrase>

That's it.



use these commands to monitor the connections:

       nmcli -p d

       nmcli -p c

Notes:

       nmcli d wifi

The above command is similar to scanning; will show the available SSID in the area.

Once a connection is established the connection is persistent;  when you reboot the system it will attempt to establish that same connection again;  similar to the gui nm.

Greetings,

The purpose of this tutorial blog post is to describe how to setup LCD brightness keybindings in the i3wm tiling window manager , on your Pinebook.

Below I am providing a script which will be placed in /usr/local/sbin/lcd_bright.sh , which may be used to set the brightness of the LCD display in increments of +10 or -10.  I will describe the step(s) necessary to activate the script via /etc/sudoers.d so that the keybindings ( bindsym ) in the i3 config can run as sudo without needing to prompt for the password !

First, the scripts... the first one is the lcd_bright.sh ( which does the work ) and the second one is the source file for /etc/sudoers.d which allows the bindsym to call lcd_bright.sh without a password. 

lcd_bright.sh

Just got my new pinebook and played with it but ran out of system memory really quick. Now knowing I would I purchased the 64GB EMMC at the same time. My problem is that I followed all instructions and it says that there is no EMMC detected. The only info I can find on this in the forum is that not all are supported. I purchase mine when I ordered the pinebook. I opened a case about this a week ago and still haven't heard anything. Just wondering if there is a tip or trick I can use to get it up and running.

Sent from my SM-G955W using Tapatalk