"RK3399 needs some catching up and things are known to be a bit broken in the master branch at the moment"
^ this is the English habit of understating things a little to be polite. I'm not expecting RK3399 hardware to boot at all, and I wouldn't bother building images again until a load of pending Rockchip fixes are merged (and no, there is no timescale for this).
RPi v2 cannot boot from USB, it must always boot from SD card (the /storage partition can be relocated to a USB drive but the boot files must be on the SD card). Newer RPi hardware is different; RPi v3 can boot from USB once a config option is toggled in the firmware to enable it. RPi 3B+ firmware supports USB boot without needing the toggle.
Install the multimedia tools addon from the LE repo and then use "alsamixer" from the SSH console to change values.
Update to the 8.90.003 alpha release and retest. Even if we manage to guess what the issue is/was in 8.2.5 it will never be fixed in that release and the alpha codebase is 12+ months newer.
obexd is completely missing in 8.90.003 but the fix was already committed so it should be resolved in the next release
Maxime is an independent developer (not working for Bootlin) and we've been helping him find bugs in the decoder for 4-5 months already and as part of our long-term effort to bring Amlogic into the modern world with a mainline Linux kernel partnered with the next-generation Kodi (on Linux) video pipeline.
It won't make any difference to CPU consumption because it's a hardware (not software) decoder. I'm not aware of CPU usage being an issue with Amlogic hardware; other than some Amlogic SoC's being cost engineered and a little slower and weaker than others.
Developer focus has been on RK3328/3268 for a while and RK3399 needs some catching up and things are known to be a bit broken in the master branch at the moment. Not sure why the file is truncated at 21MB but we'll get that cleared.
Can you share "lspci" output.
what does "bluetoothctl" show?
It looks like the kernel finds the BT device and loads firmware. If this is a clean install did you enable the BT service?
The later doesn't exist in our numbering scheme and the former is someone else's codebase, so not our problem.
Odroid C2 and RPi are using completely different kernels (3.14 and 4.11/4.14 depending on whether it's an 8.2 or 9.0 LE image) so that's where the difference will be.
I had a hunch there was an issue with the eMMC device as some mainline testing with the sdio/emmc drivers showed errors with modules from a specific manufacturer (which translates to different colours that have been shipped). Good to hear it's resolved though 
ISTR there is something unusual about Kangaroo devices, but right now the details escape me. If you can install Ubuntu, perhaps try using an Ubuntu Live USB to manually install. Basically you need to create two partitions; one 512MB and the second for the remaining space, both ext4 and install grub as the bootloader (same as Ubuntu). Now copy the contents of the first partition of the LE installer USB to the 512MB partition and translate the contents of the extlinux.conf file to grub's format. I'm a little light on details here, but creating two partitions, copy the files, configure the bootloader is all our own installer script does.
Have a look at root's crontab to see if anything has been set. Another possibility on pi hardware is some heavy load function is done (some kind of housekeeping routine) and the CPU load causes the PSU to reset. Both are random guesses not hunches.
I'm bored of repeating myself so this thread is locked.
That location contains whatever Jenkins built the previous day (sometimes a few days, sometimes longer). If nothing built, for whatever reasons things sometimes fail to build, nothing (or nothing new) will be there.
I don't recall anyone posting about OTG support before so I'd assume (at best) it's untested.
