I have received two replies to my request for testing, while at the same time I can see that people are happily using the experimental repository to enjoy new features. I worked pretty much all the spare time of this week to finally resolve the CPU issues that some people (including you) reported through various channels. I am offering a total of four installation methods (that's three more than the original project). I am working hard to resolve issues that arise with the challenge of making this available in a more standardized, simplified manner. If you refuse to communicate, and instead just once again cite the old project, this is a dead end for both of us. Just throwing errors on here with the expectation that somebody makes them disappear is of no help.
I cannot help you, or advance the documentation, if I cannot understand problems. It is still major limitation for the project right now, since many people (including you) dig it up and attempt to apply outdated information.
In my opinion, theĀ old Wiki, and the mentality of just collecting as much documentation as possible, was a major limitation of the project. There is a certain chance of finding exactly what you need, but most likely your combination of hardware and distribution would not be listed, or the instructions would be outdated (most of them are by now, anyway). A collection of more or less complete instructions, compiled by individuals who happened to succeed at one particular combination. Hello Redy, in my opinion that old wiki was a pretty big mess. Some basic comands (that have been on this list before): sudo systemctl start openwebrx sudo systemctl stop openwebrx sudo systemctl restart openwebrx will start / stop / restart the OpenWebRX service running in the background sudo systemctl enable openwebrx sudo systemctl disable openwebrx will enable / disable automatic startup of OpenWebRX at boot time sudo journalctl -u openwebrx sudo journalctl -u openwebrx > log.txt will show you the output, or in the latter case, redirect the output to a file so you can output it to a file. I can't cover all its features here, nor do I intend to duplicate its documentation. All that is beyond of what OpenWebRX is, systemd has become the standard for pretty much any major linux distribution.
systemd changed a lot), you're still better off learning how to inspect the output that way, so you don't need to stop it. So even if you can shut down the background service (it's no longer a daemon. In the end, you're not supposed to be running OpenWebRX on the shell as it is right now, because unfortunately it is leaking background processes, which will cause you more issues if you don't know what to do. That is why I am inquiring about Redy's intentions instead of answering questions that haven't been asked. But I am also sensing that there's some other problem that has happened on the way here, but there is no mention of it, so I'm unable to work on it. In the case given, Redy may be perfectly happy once he opens up his browser and sees that it's already up and running. But if you're just posting that you did something that's not on the instructions, don't give me the reasoning behind it, and ended in an error, I'm going to tell you that that's simply not the way it works. If you tell me: it didn't work, you went here and there and you want to analyze this and that, I'll gladly give you the tools you'll need.