Sup all! I love my Hero. I use it as my primary music player on the go.
As most of us have encountered though, it happens sometimes that music starts stuttering after half a day of usage. The problem arises when the music stutters for about a tenth of a second on wakeup, and could start stuttering really badly and intermittently while the phone is asleep. It's frustrating when I can't listen to a complete song without interruption!
I figured, if the phone is silky smooth soon after boot, but starts degrading after a while, it's certainly a software bug that's causing the hiccups. Looking at logcat didn't yield much else than AudioFlinger warnings, but after connecting through SSH and looking at top, I noticed the process /system/bin/mediaserver was using up to 17% of the CPU all the time. I killed it, and the music stopped, but then the process restarted, and the music started again, though from the beginning of a different track.
But the music was smooth again, and the CPU usage of /system/bin/mediaserver dropped drastically.
That's all I have so far. Anyone have a clue why mediaserver would start eating CPU cycles like that? Could it be fixed in future custom ROM releases?
I'm hoping for the best.
YES!
This has pretty much been my biggest concern since I got the phone, but haven't looked into it at all.
I am glad someone else brought this up, I'd like to see some discussion on it, and once I get some free time AND get the IM.apk working, I would like to help in figuring this out.
Just briefly I took a look at the Android OS source, and mediaserver doesn't seem to be in there, so I'm going to make a guess and say that mediaserver is an HTC-specific service. (It's 2:30 in the morning here, I really won't have time until at least Sunday to put this theory to the test. )
If it IS HTC-specific, well, there are pros and cons. A pro is that this would mean that simply using a different music app could instantly fix the problem. Cons: The HTC apps are not open source, and we'd probably have to rely on HTC fixing the code, hopefully in the 2.1 update... and, I really like the HTC Music app, so I'd rather not switch to something else if I don't have to.
If it's NOT HTC-specific, then we'll probably have the same problem with every Music app... HOWEVER, this also means that the community has a better chance of fixing it without HTC's help.
One potential solution I've been thinking of is to use Linux's nice function to give mediaserver a higher priority. This means that other processes will run slower when music is playing, but the mediaserver process should constantly get all the CPU cycles it needs. If I'm listening to music on my phone, I'm more than willing to accept a bit of slow-down in everything else.
Sidenote: After disabling compcache and applying this (http://forum.xda-developers.com/showthread.php?t=622666) fix, the issue is much less noticeable, but it's still there. If I were to venture a guess, I would say that disabling compcache is where this improvement came from, since compcache uses some CPU power to compress the memory.
mediaserver is part of the AOSP. It's inside platform/frameworks/base.git, in /media/mediaserver/.
I'll try looking into it but I doubt I'll find anything. =\
In some cases a better SD card helped
ROM based
I seem to recall this being a ROM based issue. I think I had it for a couple of the early versions of Paul's MoDaCo, but in the newer versions it was fixed, and its never been an issue on any of the AOSP 2.1 ROMs i've been running.
I would guess its probably something from the original HTC release that was badly implemented, or un-optimised.
[I think it may have been sorted for MoDaCo when teknologist released his custom kernal?]
I have a Transcend Class 6 8GB, which I think is a well respected card around here. Besides, it doesn't explain why the process starts choking up after a few hours.
By the way, I run on MoDaCo 3.2 beta 5, with the OOM killer tweaked. It's definitely a software bug where the mediaserver gets stuck in a a strange processor-intensive mode.
as for me A-Data micro sdhc turbo class 6 run smooth/faster on music playback/transfer or backup/apply file in recovery.
I have BT audio in the car, what I have found is that when a new track starts the begining seems slower than normal but speeds up, but this doesn't happen when I listen through the phones speaker or headphones? I run on MoDaCo 3.1 and my micro sdhc is a Kingston 4gb.
Could it be it takes a while for the "waves" from the new track to be caught by the stereo, so it takes a while to catch up? (lol!)
Hopefully when andriod 2.1 comes out it will be sorted?
Don't know how it happened, sorry
as i know when u on wifi or BT it will consume more power eat up cpu & phone will surely laggy. if u using normal cable earphone it doesnt consume more power then BT & wifi & dont eat much cpu. BT is eat lot of battery & cpu if im not wrong.
i get this same problem. Its been there since the stock firmware, and is still apparent in MoDaCo 3.1. Even with a class 6 8gb SD card, its still there.
Now Im running a 2.1 variant, its gone, so it would suggest its a rom problem for sure
alexperkins said:
i get this same problem. Its been there since the stock firmware, and is still apparent in MoDaCo 3.1. Even with a class 6 8gb SD card, its still there.
Now Im running a 2.1 variant, its gone, so it would suggest its a rom problem for sure
Click to expand...
Click to collapse
are you sure u using bluetooth audio without lag?
my galaxy nexus has a problem since a few months.. the phone get stuck and the screen go weird (sometimes totally black, or "noisy"), nothing works, not even the power button, i have to remove the battery to make it work again.
this has happened most of the times while downloading and installing something from goole play or while i get emails notifications and im doing something else in the phone. it does not reboot, like i said, just totally dies till i remove the battery and turn it on again.
now i updated to stock jellybean and i had the same issue. is not all the time like i said, just happens once in a while.. but i do not think is normal..
could it be a hardware issue?? i've been thinking that maybe it could be that the internal storage has some demaged sector and when android tries to write or read from that area make the phone crash.
is there any app for android to find and isolate demaged sectors??? what else could it be??
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
rhed said:
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
Click to expand...
Click to collapse
it seems, it is a common issue called "sleep of death", i wanna think it is a software issue, because users of the nexus 7 are experiencing this too..
but i cant find a solution for this.. everyone seems to know this issue but i have not find a solution..
it is not an app, im sure because this has happened in stock, after a factory reset without any app installed.. i've tried wipe cache also..
in other forum a guy said that could be that the device cant support low voltages and when the cpu go to its minimum frequency it shuts down.. that sounds kind of logical to me, because when the phone crash the battery usage is in its minimum (saw it in the battery statistics)..
i wanna try uncreasing the voltage a little but i cant do it in stock.. if anyone found the solution to this weird and annoying issue please help!!!
Use a uv-capable kernel, disable smartreflex, increase voltages for core, mpu and iva by 10 mV.
Hi,
My HTC DesireZ is flashed with Andromadus Flinny b22, and I added the TURBO BOOST MOD. I do feel the heat when I first start my phone. But I noticed the heat cools down quickly in a few days.
The phone becomes so lag, I can't even type...I checked the memory usage, and I found this happens when the swap is almost used up. I google for a while and I found it is general Linux problem that the swap usage is never released. For desktop/server, Linux system may have gigabytes of swap, so they are unlikely to be used up. But on the phone, there are only a few hundreds MB of swap and can be quickly used up.
I know I can use the swapoff command to force release the swap. But it is really inconvenient.
Does anybody have the same issue as I do? How do you recommend to resolve this issue?
Thanks,
David
Well, i ad smilar problems with it but unfortunatly coundn't find an answer.
What causes the occasional lag on the Nexus 7? With its fast cpu and ram it still seems to have more episodes of lag than I would expect.
Is Is there a utility that would let the user see which app or background process is responsible for the overloading? Some apps may not be worth having if they overload Android.
Or, since lag occurs after using the tablet for a while, is overheating the problem?
Something else?
Trying to understand. Thanks.
It's always hard to pinpoint what causes lag. You could run low on available ram then when something needs it, the system cleans up some older stuff, causing a delay in the action requested. It could happen while waiting for a minimum CPU freq to get to a smoother one. It can also depend on how the selected governor/scheduler are handling things. That's just to name a few.
prshosting.org
I got my new LG G4 about four weeks ago, and recently I've been getting a problem that's become more frequent. Occasionally it will being to lag - animations will shutter, and soon after, multitasking becomes unusable to the point of sometimes killing the launcher. Process stats reports "Device memory is currently Critical", but proceed to list perfectly normal stats. Memory details looks completely normal too, and "Phone memory" reports a whole 1.2 GB of RAM free. Restarting seems to fix it. I also tried disabling xposed, but I still get the problem.
Hardware: Verizon variant, Rev 1.0
Software: 5.1, VS98611A, rooted with low effort root.