Just wanted to inform you that I have now repeatedly noticed the programme to use almost all of the CPU power, running constantly at or near 100%.
Strange, I've never had this problem...but I never used Someplayer (I don't know if this is the problem).
I cannot even see the program with "top" while playing music.
The program should use almost no cpu power, it just listen to some dbus events, doing nothing.
You can try to kill the background process, then launch in a terminal the daemon manually with
Code:
/usr/sbin/volumecontroldaemon -d
And post the output.
Edit: There's no need to reboot the device to stop the daemon, just kill its process...
If the volume for headphones (when they're really headphones) is too low for you, I suggest investing a little more in your headphones!
I use Sennheiser MX-80 (I think they can be called "headphones") but the volume is low at the normal 100% (88), mostly when listening to my favourite music ('60-'70).
I have no problem with recent recordings and I never listen at 100% (the volume of "modern" cds is far higher than old remasters), but a lot of my cds have a lower volume (and music volume cannot be raised a lot with normalizer due to clicks and distortion), so the only solution (at least for me) was to raise the volume.
Strange, I've never had this problem...but I never used Someplayer (I don't know if this is the problem).
I cannot even see the program with "top" while playing music.
The program should use almost no cpu power, it just listen to some dbus events, doing nothing.
You can try to kill the background process, then launch in a terminal the daemon manually with
Code:
/usr/sbin/volumecontroldaemon -d
And post the output.
Edit: There's no need to reboot the device to stop the daemon, just kill its process...
Code:
ps | grep volumecontroldaemon
get the pid and then
Code:
kill xxxx
where xxxx is the process pid.
Well, like you described, the daemon does not noticeably use CPU power almost all of the time.
However, there were a few occasions where CPU usage suddenly peaked and stayed constantly at or around 100%. I checked with Conky and it showed the daemon as the source for the heavy CPU usage.
Again, this is not something that occurs frequently, just a couple of times. Still, I thought it was worth mentioning. I will try to monitor if this only happens in connection with using someplayer.
Again, this is not something that occurs frequently, just a couple of times. Still, I thought it was worth mentioning. I will try to monitor if this only happens in connection with using someplayer.
Many thanks for your help.
I still cannot imagine how can this be possible (there's not a single loop in all the code, how could it take 100% of the CPU?), the only thing I can think is a sequence of a lot of dbus messages (but this doesn't seem a normal situation)...
Please let me now if you notice this again or you discover something.
the app is very usefull im using sennheiser mx470 headphones and it nearly acts like a speaker now very good job. .)
and...does this consumes more battery or not ? hope not coz i love listening music via headphones .)
