How do we construct the single .img file like the one that is distributed on the wiki after we build the Android ROM?

I found these steps for flashing:

rkdeveloptool is here: http://opensource.rock-chips.com/wiki_Rkdeveloptool
Get the board into bootrom mode. Short the two pins next to the LEDs and hit reset.

We have the following lunch selections:

While looking for a better way to get the kernel on my NVMe I ran across this guy who figured out the best way to load his system. Put the boot files on the boot device and the root files on the fastest device, NVMe.

I'm hoping someone here can put some flesh on these bones to make it work for us. Did I say I'm a linux/programmer novice, yes that is me. Eventually I could figure this out. Think I know how to proceed if no one else cares, but I would like expert advice too.


https://delightlylinux.wordpress.com/201...sing-nvme/

An NVMe SSD makes a superb system drive for a Linux installation, but an easy point to forget is how to make Linux boot on systems that do not support NVMe booting from the motherboard BIOS.
So, here is a quick reminder.

First, Use a secondary SSD that the motherboard BIOS does recognize
This is the key. In a recent Linux Mint 18.3 installation, I used the Samsung 960 EVO NVMe connected to the motherboard using a PCIe to NVMe adapter because the older motherboard lacked an M.2 slot.
The problem is that the motherboard did not recognize the Samsung 960 as a boot device. Sure, Linux Mint 18.3 would install to the NVMe drive fine from a LiveUSB, but there was no way to boot the system from it.
Was all lost?
Nope! Remember, this is Linux that we are talking about, and Linux offers flexible customization. When Linux boots, it first looks for the /boot directory to kickstart the process.
/boot can be located on any other boot device, so it does not have to reside on the same drive as root. We can install the main Linux system on the NVMe, but specify /boot on a different boot device that the motherboard BIOS will boot from.
I had an SSD installed in the system. The motherboard recognized the SSD as a valid boot drive, so I created a 4GB partition (more than necessary, but just in case). The rest of the drive was formatted as ext4 for regular data storage.
The system and swap partitions were located on the Samsung NVMe. The boot loader installation was set to the SSD, not the NVMe. Below is the Install dialog from a Linux Mint 18.3 installation that shows how the partitions were set up.

Linux Mint 18.3 Cinnamon installation showing how to arrange partitions so a system will boot Linux is the Linux has been installed onto an NVMe device that lacks NVMe booting.
/dev/nvme0n1 is the NVMe device divided into two partitions: btrfs for the Linux installation and all Linux directories except for /boot, and the swap space. btrfs was used here, but any other bootable filesystem is valid. Install Linux normally to the NVMe.

• /dev/nvme0n1p1     Linux root filesystem
  
  
• /dev/nvme0n1p2     Linux swap partition
  

• /dev/sda1   Regular storage space. Nothing special.
  
  
• /dev/sda2   /boot goes here. Small partition.
  

• /dev/sda   The boot loader. BIOS looks for this. Must be the SSD, not the NVMe.
  

Hi all,

@fire219 is working on getting the different chats properly bridged (IRC, Discord, Matrix and Telegram). This means that current bridges will  come down and a new and more elegant bridging solution will be implemented.

Expect possible short-term disruptions in the next couple of hours; this may extend to a day or two if there is some unforeseen trouble.

I made the following docker container based on another project that has the environment preconfigured for building:

https://cloud.docker.com/repository/dock...-rockpro64

It maps your current directory as the base directory for building.

You can launch it with the following:

Follow the steps on the repository here:

https://github.com/a9rock64/manifests

I know A72 is performant while A53 is energy efficient. But what about the Spectre vulnerability? A72 is vulnerable, while A53 is not. The vulnerability is somehow fixed in linux. Hence in recent linux we have pure A53 vs A72 + the fix overhead.

So is A72 + the Spectre fix overhead is still more performant than A53?

Hi!

Thanks so much Pine people for your great products! I can't wait to order the Pinebook Pro and PinePhone!

It looks like all these products just tick almost all the boxes of what is (and was since a looong time) necessary! It's not with the intention to complain about that one last box that's unticked: ethics... ; rather, I was wondering if there might not be an easy optional kind of solution for this: by proposing buyers to donate a certain amount that would go to some initiatives, or suitable organisation that deals with this... I know, it may feel hypocrite to some, to support it in a secondary way, while these products are (well, to my feeling very most likely not exactly ethically produced, which is to some extent fair enough, as almost all companies do so...), but I don't think it is absurd because you'd really support something that can have a significant effect, so that later the situation can be settled correctly hopefully at some point... Customers will feel it also as quite natural to donate at that moment, because otherwise it is a bit uncoupled and therefore mainly idealistic, to donate independently from a purchase. In fact, now there are no companies just honestly saying how people involved in the production chain are being treated, while there are many pretty questionable cases in there. I believe it may be a beautiful and courageous and very honest initiative to openly admit this to the customers, but also presenting an option to do something about it.
You could say: just buy a fairphone then... But to be honest, I would find this approach more fair, more realistic, less just idealistic and more down to earth, with a potentially greater effect. (Though, I also like Fairphone, don't get me wrong please :~) And it would make Pine64 the most revolutionary tech company (well, if it isn't already..?)

Curious to hear how you receive this idea...

Kurijn

Hi,

Please help in installation of drivers/firmware required to get RTL8812AU WiFi working on Rock64 running OpenMediaVault.
Went through so many threads and github tutorials but none of them are helping

Thanks!

kernel: https://github.com/dazza5000/android_ker...hip_rk3399


vendor common: https://github.com/dazza5000/android_ven...hip_common

vendor hardware: https://github.com/dazza5000/android_ven...p_hardware

device: https://github.com/darran-kelinske-fives...hip_rk3399