Hello Community,

I've already opened a Thread, concerning my issues with the Rock64, however there are similar issues with my Pine A64-LTS aswell. Altough I've used the bsp-Kernel variants, everything is laggy and choppy, even though I expected at least the xenial MATE build to work properly. The intended use is inside a self-made Tablet and while this could bring up the conlusion, that I want it to have Android, I don’t. My preferred choice is Linux, even better if I could use GNOME 3 on it (also my touch screen wasnt supported by Android and it was slow for whatever reason aswell.). Like in my Rock64 Thread, GNOME 3 showed llvmpipe as graphics device (backchecking with the system-monitor confirmed that it was software rendering) so that was unusable. I really love this board for the fact, that it has battery support and decent perfomance on paper, that I couldn’t see in real life yet, so how can I improve this. Also a problem that is just as big, is the fact that I can’t change resolution propery. Most images provide 1080p. What I need for this screen is 1024x600. Trying to change that in the config file always resulted in black screen/weird distortion, same with 720p. Only Armbian provided an usable 720p config. I hope for help from you guys to at least finallize this project from the software side.

Greetings, Max

Hello community,

I've recently got my Rock64 (4GB). For now however, I'm rather disappointed.
I already tried out several Debian and Ubuntu images, hoping to get proper video performance out of it, so far all of them only gave me disappointment and frustration.
First of all, the Rock64's intended use is for both a lightweight server (apache, sftp) and as Addon to make my TV smart(Netflix, YouTube, web surfing in general, emulators for SNES etc.). I know that the TV part can be done by Android, but the server part can't. Also I prefer a direct Linux over Android. I'm wondering how I even get such bad performance (as example, YouTube was insanely choppy in the xenial MATE build, but it all felt somewhat sluggish anyway and Debian Jessie with GNOME3 on top was pure horror), considering that I've read about good support from the hardware vendors site. Both examples I've just mentionened made use of software rendering rather than hardware rendering(YouTube in both Chromium and Firefox pushed the CPU to 100%, the test of GNOME3 showed me llvmpipe as graphics device rather than any actual GPU and a look at the CPU usage caused by gnome-shell confirmed that it was software rendering) and that's where I wonder if there is a way to fix this. I mean if there is proper support for all of this on Android (which I'll probably test just for fun) and the hardware devs are (at least if I’ve read that correctly) open to provide their divers for Linux aswell, why can’t I then get proper h264 and openGL ES support (later at least for GNOME3, but interestingly enough, GLXGears on the other hand ran with 60FPS but looked choppy on display). I have similar issues for my Pine A64-LTS aswell, but that belongs into a different thread.
I really hope for support/information, as I bought this board with good expectations in the great hardware on paper and just hope it’s some software stuff I’m doing wrong. If there are questions remaining, I’d love to answer them.

Greetings, Max

Hi, i received my Rock64 and i installed Android TV, it's work very fine  but the google play, is unfairly empty because the "rock64" is not recognized by Google. My goal is to edit the build.prop to make it look like an Nvidia Shield TV so many applications will be available and the rock64 can be used to its full potential

But there is a problem, how can i root it, I was able to access the Recovery with ADB and my goal was to install the zip archive supersu but the SD card can not be found (the system is installed on the EMMC), likewise in Android TV, if I go in the storage options I can read "The SD card was ejected safely" while I did not ask to do this.

Do you have an idea to counter this problem?

(I already tried app like Kingroot, doesn't work at all)

Thank you

I've been trying to debug this all afternoon, for some reason there is no audio on the left channel on the headphone jack. Plugging the headphones in to my screen and listening to the audio through the hdmi output works fine. I've tried a bunch of different things, including uninstalling Pulseaudio (had to flash the OS on the SD card to restore it) that haven't worked.

Do you have any ideas? Is it possible that this is a hardware issue?

Hi

I finally managed to get SPI going, all the signals seem to be there but I see my clock signal (SPI_CLK_M2, pin23 on PI2 header) where the chip select (SPI_CSN0_M2, pin24 on PI2 header) should be and vice versa.

How to swap these around?

Also, is it possible to stop/start driving these pins at runtime? How?

Hi all.
I've been looking at buying an Odroid XU4 for having as home server (little bit of openHAB, little bit of Owncloud, maybe other stuff) and just today found the ROCK64 which seems like a very nice alternative. I got some initial questions though that I can't seem to find any obvious answers to.

I want to run this headless. I want a Debian Stretch image which least possible footprint, just so that I can SSH into it and install whatever I need. Obviously I'm going for the eMMC alternative. Is it just a question of downloading the Strech minimal image from http://wiki.pine64.org/index.php/ROCK64_...re_Release, flashing it to the card (using USB-eMMC adapter), booting up and SSH:ing in? Kinda confusing that some images on the wiki says "microSD Boot" and some says "microSD to eMMC", is there really any difference or do they all work on eMMC as well?

Also, since the form factor looks almost identical to rPI3, does it mean that it fits in rPI3 cases? Or do I need to buy the (bulky looking) "acrylic open enclosure"? The cases at c4labs.net looks really great but it's supposed to be in a closet out of way so I'd rather buy something that just cheap and effective :-)

/Daniel

Hi,

On 12th November I place my order and was shipped on 17th November, this is ok, but since 17th November has not arrived yet !!

Any problem with the mail packet ? 

 Order #53762
Tracking number LX595200079CN

Hi,

which HDCP version is supported by the ROCK64?

Android Project Treble simplifies building custom Android ROMs.

Providing an Android Project Treble Software Development Kit (Original vendor implementation) will make the ROCK64 much more attractive on the market!

Am new to the Rock64 board and have some questions.

I currently have 3 Raspberry Pi 3's, one running NextcloudPI, one running PiVPN/Pi-Hole, an one Running Netatalk.  I am looking to replace all three with Rock64 boards.

I just received my board, a 32GB eMMC module, and the serial console board.  I have already flashed the eMMC board with ayufan's Debian Stretch pre-release image (yes, I know it's experimental).

Now I need to boot up the board.  I plan on connecting it to a TV via the HDMI port so that I can set it up.  I am unclear in reading up on this, if that will actually work and I'll be able to see the boot up process.  Do I HAVE to use the serial board, or can I use the HDMI connection to view the boot up process?

In theory, I should be able to just boot right up into the OS as I've already written the image to the eMCC board, correct?  My plan is to hook up a USB keyboard and use the HDMI connection to a TV for the short term.  Once I'm comfortable with the OS, and have setup SSH, I'll just use that for managing the OS.  Should all that work properly?



What other OS's whould you recommend I try? Since I'm using all three Rock boards as infrastructure servers, I am just looking for a lightweight OS that I can run the service on.  Most familiar with Debian, so Stretch seemed like the best choice.

Any recommendations on cases?  This will be sitting on a shelf in my office, so I like to have a case.  With a fan if possible.  I see there are HeatSinks available so will probably go that route too.

Thank you all for any assistance.