GoogleCodeExporter
commented
9 years ago Actually, the cpu-usage doesnt go down even with xbmcremote in the background!Original comment by sop...@gmail.com on 20 Sep 2009 at 10:06
Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago Actually, the cpu-usage doesnt go down even with xbmcremote in the background!Original comment by sop...@gmail.com on 20 Sep 2009 at 10:06
GoogleCodeExporter
commented
9 years ago Playing a song where? Locally or on XBMC machine? Playing on XBMC should not
make any
difference since "playing a song" is just sending the play command and go back
to
idling.
I'll check how much CPU it uses here, but I never noticed any particular
problems.Original comment by phree...@gmail.com on 20 Sep 2009 at 3:34
GoogleCodeExporter
commented
9 years ago I was playing it in XBMC.
When starting the app again, I see that it starts out at 0% nice enough. But
then if
I browse mp3s it starts going up to ~50% and stays there whatever I do.Original comment by sop...@gmail.com on 20 Sep 2009 at 8:36
GoogleCodeExporter
commented
9 years ago Actually, not even choosing "exit" in the menus seems to help. That is very bad
:)Original comment by sop...@gmail.com on 20 Sep 2009 at 8:48
GoogleCodeExporter
commented
9 years ago This is the stack of the thread (MAIN) that seems to use too much CPU:
Object.wait(long, int) line: not available [native method]
MessageQueue(Object).wait(long) line: 326
MessageQueue.next() line: 144
Looper.loop() line: 110
ActivityThread.main(String[]) line: 3960
Method.invokeNative(Object, Object[], Class, Class[], Class, int, boolean)
line: not
available [native method]
Method.invoke(Object, Object...) line: 521
ZygoteInit$MethodAndArgsCaller.run() line: 782
ZygoteInit.main(String[]) line: 540
NativeStart.main(String[]) line: not available [native method]
Original comment by sop...@gmail.com on 20 Sep 2009 at 8:55
GoogleCodeExporter
commented
9 years ago This patch atleast points to what the problem is: some sort of never-ending
message
loop seemingly related to display updates? I don't know how to fix it.
Index: src/org/xbmc/android/remote/activity/NowPlayingActivity.java
===================================================================
--- src/org/xbmc/android/remote/activity/NowPlayingActivity.java (revision 85)
+++ src/org/xbmc/android/remote/activity/NowPlayingActivity.java (working copy)
@@ -48,6 +48,7 @@
import android.os.Handler;
import android.os.Message;
import android.os.Handler.Callback;
+import android.util.Log;
import android.view.Display;
import android.view.Menu;
import android.view.MenuItem;
@@ -130,6 +131,7 @@
Thread updateViewThread;
public boolean handleMessage(Message msg) {
+ Log.i("Mloop", "Got msg what: " + msg.what);
if (msg.what == 1) {
if (updateViewThread == null || !updateViewThread.isAlive()) {
updateViewThread = new Thread(this);
Original comment by sop...@gmail.com on 20 Sep 2009 at 9:13
GoogleCodeExporter
commented
9 years ago We have a thread which constantly updates the data in the NowPlaying activity
which
does a postback when new data has arrived, My bet is that this thread is taking
to
much CPU. And it's not stopped on minimize of XBMC Remote.Original comment by Tobias.A...@gmail.com on 25 Sep 2009 at 5:09
GoogleCodeExporter
commented
9 years ago Can you look at the issue Tobias? I'll reassign it to you.Original comment by phree...@gmail.com on 29 Sep 2009 at 9:13
GoogleCodeExporter
commented
9 years ago Sure will take a good look at itOriginal comment by Tobias.A...@gmail.com on 29 Sep 2009 at 11:28
GoogleCodeExporter
commented
9 years ago Fixed in r102 nice find sopues!Original comment by Tobias.A...@gmail.com on 29 Sep 2009 at 8:07
Original issue reported on code.google.com by
sop...@gmail.comon 20 Sep 2009 at 10:05