Is there a way to run Magisk on Rock64?

It seems it can't patch Rock64 boot.img correctly and fails.

It is needed for apps to pass Safetynet and Google Certification for some apps to work.

Hi all! 

For a long time I've wanted to make my own NAS, and it looks like the rockpro64 is just what I need. 

My idea is to use a PCIe card with a Marvell 88SE9215 or 
88SE9230 chipset, so I can have up to four drives connected. I don't want to do raid or anything, it's just that I rather have all my storage in the same device. 

Do you know if it should work straight away, or there will be issues with omv or the Linux kernel with the sata card?

Thanks for your time! 

/Xtract

Hello, I got my SOPINE board about 2 months ago and couldn't get it to boot then (same issue, blank screen upon power up). So as of this week I bought a high speed microSD, which before I assumed the reason for not booting was due to a slow SD card. But once again, blank screen  with the new card, and I'm staring to loose faith. Any help would be appreciated.
Thanks

Hello everyone.

I have a problem that I can not solve on my own. I've been trying for some days without success so I had no choice other than asking for help here.

The thing is that I can not set correctly a static IP on my rock64. I mean, I do can, but the device will ALSO maintain the previous DHCP assigned IP forever. My device does have two IP addresses on the same interface eth0 (not even eth0:1). The problem is that the behaviour is unpredictable.  I will explain myself:

For example, I can connect to it using TCP, and it works perfectly, on BOTH IPs.

But, if I use UDP, it will answer with the DHCP assigned IP, thus the source discards the connection.

I have tried everything I could think of. I installed three different ayufan's stable releases as well as non stable ones (jessie minimal 0.5.15, OMV3 0.6.31, OMV3 0.15.5, OMV4, now I have stretch 0.6.31).. And the problem persists.

No matter if I use omv web panel, or /etc/network/interfaces. I can set an IP, but the other one will be there as well forever.

The only thing that I can think of is the way I am installing the OSs, in case there is some problem.

I just use a SD-installed OS to boot, then I use a script that automatically downloads and writes the image to the emmc card. I am not "formatting" that emmc before. rock64_reset_emmc.sh does not work for me, nor does the jumper to boot on sd card. If I have both the sd and emmc, it will boot the sd, so I use it to write the emmc, then I take the sd off to boot from emmc. If I use the jumper, I will boot on SD as well, but the emmc will not be available, even if I take the jumper off, and use the reset script (which says device does not exist).

Thanks for your help. If you need any further information to help me I will provide it as soon as I can.

My battery was almost fully discharged yesterday. Today, after 2hours charge time, I get the Pinebook splash, a flicker, then nothing.

Any thoughts on how to recover form this? I'm in the process of prepping another SD to test the machine, but don't want to have to do a full re-install if I can avoid it. Can I access the update scripts from an SD boot and see if that brings things back to life?

*Interestingly Linux finger magic (Alt+SysRq with r, e, i, s, u, b) will still trigger a reboot from that blank screen, so there's some bit of OS in place to interact with…

Hi,
has anyone of you tried to run Nvidia drivers for "Linux-32bit ARM" for GeForce cards on Rock64 Pro?

Kind regards,
Grzegorz

I've tried to install both, android-7.1-rock-64-rock64_atv-v0.3.13-r115-taw.img.gz and android-7.1-rock-64-rockbox_atv-v0.3.13-r115-taw.img.gz but when I try to flash the SD card it says that these images are not bootable. Why does it say this and what do I do to fix this? Likewise when I click "continue" and it flashes to the card, it won't boot. What do I do?

Sent from my SM-G930V using Tapatalk

Hi everyone!
I'm excited to share that we have a release of Netrunner out for the pinebook now!

You can read more about it here : 

https://www.netrunner.com/netrunner-for-pinebook/
https://kshadeslayer.wordpress.com/2018/...-pinebook/

We'd love to hear your feedback over here in the comments section!

Just loaded my Rock 64 4G with Ayufan's Xenial desktop image and everything is working fine. I currently have it operating on a wired Ethernet connection. I plugged in my wifi dongle, an Edimax EW7318Ug but the Rock64 Xenial distribution does not appear to have a driver that supports it. On my PC version of Xenial I have in the past just added Linux Firmware Non Free to resolve this problem. This appears to be not possible in Xenial now.

I issued the lsusb command and this is the following output.

Bus 002 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter

The good news is the Rock64 recognises the dongle but I was wondering how I could go about adding a driver to support. I'd appreciate any help pointing me in the right direction here.

*I accidentally posted the original query in the Pine64 section but couldn't move it*

Hi All,

after have struggled for a while with this board I finally found the right way.

At the beginning I was convinced that Lakka image available for this board was able to perform easily the emulation task but it was a truly pain. The emulation was absolutely under the real potential of the board, indisputably there is some issue with the driver stack that is unable to take advantage of the GLES acceleration.

I have been very delusional, with a board I considered pretty useless for my initial scope, I tried the Android version and the Android TV image and I discovered the emulation provided through the Retorarch application on the playstore was absolutely better, beside a better selection of cores available for the android version, it played an important role the video drivers that Android brings to its. This version for Android is able to run flawless PSX with full resolution and N64 emulation (even Killer Instinct) out of the box. I was really impressed by this huge difference between Lakka and Retroarch Android, I had to change completely my opinion.

Between Android and Android tv, I consider the former the best option. By the way also this change was not completely painless; to begin I had to understand that Android expect to be managed through a touchscreen, I have wireless keyboard with touchpad that worked well with it, but my intention was to use a gamepad. To make a gamepad working as touchscreen I used a very nice application called button mapper, with this app I was able to use my PS2 clone pad on Android but not in Retroarch. I even tried to edit manually the retroarch.cfg file but unsuccessfully. To use a pad on Retroarch you need a gamepad that is recognized automatically by Android, fortunately I had a Saturn style pad that was recognized automatically by Android and I was able to use in Retroarch as well. Certainly the Linux kernel in Lakka has a bigger and better hardware compatibility than the Android kernel so my recommendation is to buy a Android Gamepad directly.

When you learned how to handle your R64-Android with your pad or your wireless keyboard, you can take advantage of the benefits to have a light OS on your TV. My suggestion is to install as first thing the F-droid repository in order to install alternative applications that better preserve your privacy and your data. Like using Chromium as default browser instead of Chrome or New Pipe instead of the Youtube standard app. Some apps aren't available because the incompatibility like Netflix, however you can download it from its website but the version I have available on my smart tv is actually better than the one for Android that is designed for a touch screen and is not very friendly to use through the gamepad as well as the keyboard.

Now I am pretty happy with my board the last thing I have to fix is the Retroarch resolution, even if the cores launch their game with the correct resolution the GUI as the resolution at 720 instead of 1080, I hope to fix this soon. I haven't tried yet if the shader work flawlessy on Retroarch however I can still use an overlay layer to safe some cpu/gpu workload. I'll let you know if I am able to use the shaders without losing frames per second.