futeko.com FORUM
Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: Leviathan99 on August 26, 2016, 04:02:07 PM
-
I hope this helps anyone interested in using the Q10/Q5 pro as an NZB downloader. I've recently setup NZBGet which in my opinion is one of the better downloaders out there and it works well!
Please see:
https://github.com/nzbget/nzbget/wiki/Installation-on-Android
Once you install and start the daemon from the apk listed above you can access the web front-end easily from port 6789. I previously had NZBGet running on my Netgear NAS and the Q10 pro gets about twice the speed so I am very happy. The one catch is you have to enter the IP address of the newsserver vs the domain name but this is only a one-time issue during newserver configuration.
Since my Q10 pro is the only media player I have that reads Bluray ISO's it made sense for me to download directly to my internal HD on the Q10 pro.
The only step I have not solved is how to get the daemon to run at startup. Currently after the Q10 pro powers on I have to start the daemon using the app.
-
The only step I have not solved is how to get the daemon to run at startup. Currently after the Q10 pro powers on I have to start the daemon using the app.
As per the FAQ on this forum:
How to make Kodi (or other app) launch on startup? Go to 'My Apps' from home screen, navigate to the app you want to auto-start, and press menu button on remote. The option to 'Default start' will appear over app icon.
-
The only step I have not solved is how to get the daemon to run at startup. Currently after the Q10 pro powers on I have to start the daemon using the app.
As per the FAQ on this forum:
How to make Kodi (or other app) launch on startup? Go to 'My Apps' from home screen, navigate to the app you want to auto-start, and press menu button on remote. The option to 'Default start' will appear over app icon.
In this case the NZB APK is simply a launcher that allows the user to either install, start, stop or remove the daemon. When I want to do is start the app and then have the "start daemon" option selected. In all likelihood this will involve editing some sort of init.d script to get the daemon to start at boot time.