@tekaeren unfortunately i'm on the road now and don't have access to my router at the moment (should be back over the weekend)...
regarding mt7615.1/2 and APCli/AP ... IIRC for each (physical) interface (ie, ra0 and rai0) we get 3 "interfaces"... (off the top of my head: ra0 => ra0 + rax0 + apcli0)... where ra0 is 5ghz, rax0 is 2.4ghz and honestly i have no idea what apcli0 is (but what you say in your message makes sense)... similarly for rai0 (the 2nd physical interface)
in response to your question of "how the use of bands on these interfaces" etc... I tried to say something about it in my previous posts, but you seem to have arrived at the same conclusions: we need to disable one of the frequencies (2.4ghz/5ghz) for each physical card. hence my script (which is pretty basic) turns off (IIRC) ra0 (5ghz on 1st chip), ray0 (2.4ghz on 2nd chip) and (i think) apcli0 (again for first chip)... as you seem to have seen, you end up with a very weak 5ghz signal on mt7615.1.5 if you don't disable it.
as for luci and interfaces... yeah it's pretty annoying how that works. the real thing we need to figure out is how to configure those *.dat files ... maybe someone who has pandorabox can take a look at what their configuration files are like (or something)
as for disabling interfaces (after making changes with luci)... you can just do it manually (see also /etc/init.d/mtkwifi ... i'm writing the following off the top of my head)
BAD_IFS="ra0 ray0 apcli0"
for i in $BAD_IFS
do
/sbin/ifconfig $i down
done
my goal so far has been to bring up wifi/openwrt on R3P ... obviously there are more "nits" that need to be cleaned up (like you're pointing out wrt luci etc)
@tekaeren thanks for the testing... you should be able to recover from the bootloop, although maybe because you didn't set the nvram flags just plugging in a USB stick won't work.
you'll know more once you connect to the uart, but if you're bootlooping openwrt (and not stock), press '4' on the bootloder menu and then set the 'flag_try_sys2_failed' (IIRC) to 1 and 'flag_try_sys1_failed' to 0 and saveenv and reset. that should boot you into stock recovery mode.
let me know how it goes.
thanks for testing
PS: @tekaeren my /etc/init.d script brings up mt7615 at boot-up, but obviously if you've made configuration changes that cause it to panic you're going to get stuck in a boot-loop (like you have). in the future, when making (untested) configuration changes, disable /etc/init.d/mtkwifi first. that way at least you'll be able to boot.
