I just had a thought that might address the wget issue, but I am unsure if it is workable. The response when sox attempts to use the BusyBox wget is:
Code:
wget: unrecognized option '--no-check-certificate'
BusyBox v1.17.1 (2018-11-27 03:29:06 PST) multi-call binary.
Usage: wget [-csq] [-O FILE] [-Y on/off] [-P DIR] [-U AGENT] URL
Retrieve files via HTTP or FTP
Options:
-s Spider mode - only check file existence
-c Continue retrieval of aborted transfer
-q Quiet
-P Set directory prefix to DIR
-O FILE Save to FILE ('-' for stdout)
-U STR Use STR for User-Agent header
-Y Use proxy ('on' or 'off')
This appears to indicate that it is unhappy with that one parameter. Looking around it appears that command line comes from a null delimited string in libsox.so.2 of <wget --no-check-certificate -q -O- "%s"> which leads me to wonder if this could be patched to remove the unsupported parameter. Issuing the command without the unsupported parameter works on my pw4, so it is possible that this patch would allow using the BusyBox wget with sox.
Is such a patch possible? I would think at a minimum replacing the bogus parameter with spaces would work, unless some sort of signature check of the binary would result in it becoming unusable.
Dave