Wondered about the recommended method of powering down Rock64 running Android. Found a post in the Pine64 section from 2016. Here's what I experienced.
1. Short press of the power button on Rock64 = blanks the screen. Short press a second time brings up the screen.
2. Long press of the power button on Rock64 = displays power off / restart dialog box. Defaults to power off, press Enter, Rock64 powers off. Arrow down to Restart, then Enter, Rock64 says powering down, and then it restarts.
3. Restarting via the settings menu (Settings - About - Restart) also restarts but I couldn't find anything in settings about shutting down.
4. Pressing the reset button on Rock64 = resets (probably not recommended, doesn't correctly close first, just hard reset like pulling the power?).
5. If off - pressing the power button = powers it up, pressing the reset button = powers it up.
I assume my results are by design. If not, best method for powering down?  Don't want to corrupt the eMMC. Thanks.

NOTE: base Android, not Android TV build. Not sure if the results would be the same.

Is it ever possible to upgrade the RAM on a PineBook?

https://forum.libreelec.tv/thread/4248-l...?pageNo=10
No Rock yet so haven't tried.

Hi,

I'm about to order the Rock64 for a NAS project.
I'm going to build the Rock64 inside a 4bay case (like Chenbro SR30169 or similar).
I made a schematic how I thought to build it.

Here is my community build. Kernel is build as 64bit with 32bit Userspace. It means you can use 32bit armhf packages. I've been doing these builds for a while now for Odroid C2, WeTek.Hub and WeTek.Play2. The benefit in using 32bit packages with an aarch64 kernel is we can use retroplayer emulators that only compile for armhf and we can use precompiled libwidevine to play DRM protected content with Kodi through inputstream.adaptive.

Special thanks go to @peak3d for implementing the great inputstream plugin that makes DRM work with kodi.
Also special thanks to @Kwiboo, @longchair and @omegamoon for the great Rockchip work. These builds are based on kwiboo's LE tree.
And last but not least thanks to @tllim for providing me a Rock64 developer sample.


DISCLAIMER: This is a community build of LibreELEC. USE AT YOUR OWN RISK!

Tar upgrade from "pure" aarch64 builds might work. Use the following steps:

Hello,
I noticed that on Q4OS the touchpad is much less jumpy, and managed to find the config in question and copy it over to my own install.

unfortunately, this still does not solve 1 problem:
the bottom part of the touchpad, where the 2 buttons are, is also sensitive to touch and movement.
pressing a button, one always also moves the pointer a little.
so i would like to disable the bottom 1-2 cm of the touchpad.

is that possible?

afaiu the touchpad is NOT a synaptics device.
entering 'xinput list-props 8' i can see its properties.
anybody have an idea how to disable the bottom part of the touchpad?

also see: http://dt.iki.fi/pbhacks/

Hello, everyone.

I have two questions. I am using the Android Image 7.1.2 but it has only the patchlevel April 2017, is it planned to be updated?

Second question. I've seen that there's a linux kernel here:

https://github.com/ayufan-rock64

Do I have to install the firmware, as with the raspberry pi? If so, how?
Or is it enough to just take the current image?

Thank you very much!

So I've played with Ubuntu, I've played with Android and I've played with Bliss, and I'm just not feeling the value in my pinebook, I know it's a tinker device, I love the look and feel (Keyboard excluded...ugh) but the more I plug away at it, the more I think "Damn, This thing needs ChromeOS/ChromiumOS" Having run a Samsung ARM Chromebook for a while, I know the feel of ChromeOS on ARM, and I think it could be a good match for the Pinebook.

I had high hopes for Bliss though, while I was hoping for a good RemixOS port, with that dead in the water, Bliss is my only hope for a desktop based Android.

But yeah, A Chromium build on this beast would be awesome.

Hello everyone,

I just ordered a rock64 and I want to use the spdif port for audio out. As I have no need for the DAC or the 2nd eth port I don't want to use the DAC board.
Can I wire an fiber optic transmitter (like TOTX147) directly or do I need some buffer/driver like the inverters used
on the DAC board?

Thanks!

I've been toying around with my Pinebook now for a few weeks, off and on.

What I'm concerned about is the low level of activity on this forum. Unless I am missing something, this is the obvious hub for Pinebook news and discussion, yet it is not very popular.

I've tried most of the OS images available for Pinebook, including Android, Q4OS as well as the Ubuntu Mate and Armbian distros - various versions of each.

None have yet worked well enough to provide a reasonable desktop experience  - i.e. no GPU accelerated compositor... unless the very slow performance I was seeing when I did enable GPU composition was just how slow the Mali GPU really is??

I expected at or near RPi 3 performance - perhaps that was optimistic of me.

Maybe Pinebook is not for me. I'm not a hardcore Linux user, but I think I'm a step or two ahead of an average Ubuntu newbie. I've used Linux, if infrequently, for around 20 years. I don't get down an dirty with core OS development though.

I thought having an expectation of a well performing desktop environment would be easily met. Rough edges I'm used to - there's not been a Linux distro I've used that hasn't had a lot of rough edges, but 3D acceleration and fast 2D desktop composition have been reliable keystones for many years.

Am I really missing something that I should be doing? I must have read through 80% of all the forum posts.