I am reposting this because the issue remains and when I first posted in July I received a single response from a user that was also experiencing this.
I can't seem to find an answer anywhere. Basically when listening to a podcast with the Podcast Addict player at ~1.9x or faster the audio stutters and produces a static sound distorting the audio. Waking the screen immediately stops the issue. The issue gets worse if you increase the speed or enable the "skip silence" feature.
I made sure to disable any battery saving options for the app and enabled any workaround options within the app. I even contacted the developer who pretty much just said that the phone is governing the processor too low with the screen off. I have tested other podcast apps and they seem to function fine even at faster playback speeds. For some reason, this only affects Podcast Addict.
Is anyone else experiencing this? Anybody have a suggestion for a fix? I am completely stock OOS version 4.5.14. I have the 8/128GB model if it makes a difference.
It seems to have issues even if the screen is on and the app is not in the foreground. Within ~5 seconds of being put into the background, it begins to stutter.
I have been working with OnePlus' own "bug hunter team" to fix this but I have not heard from them in over a month since I reported it to them. They asked me clear cache and reproduce the effect on my device and send them logs, which I did but I haven't heard anything.
Can anyone test this and tell me if they don't have an issue with screen off?
I also couldn't get rid of the static sound in Podcast Addict when playing back at fast speeds (for me, around 1.7x or faster). This was on a Galaxy S8+. I've been listening to a podcast audiobook Wildbow's "Worm" (which weighs in in at 6,680 pages) and the static sound was killing my ears. Gave up on Podcast Addict today, and switched to Pocket Casts and not having any static problems now when listening at faster speeds.
I think I found the problem with Podcast Addict stuttering... it's the logging.
I've gotten into the habit of pinning my CPU frequency to 299 MHz maximum to save battery, and PA would stutter, so I dug into ADB to figure out what was going on. After getting rid of the hidden adware that the phone's manufacturer kept running in the background, CPU usage dropped enough that I could run PA without much stutter, but if I opened the notifications or ran any other app, it'd start stuttering again. So I dug further.
And it seemed that as I increased maximum CPU speed from 299 MHz to 1.3 GHz, CPU utilization would increase, too, if Podcast Addict was running. That was strange behavior, so I knew something was going on.
Apparently the system is somehow hooking into PA and logging everything PA is logging internally. When I run:
adb logcat -D -v long > c:\test\logcat.log
... the logcat.log file swells up to 80 - 110 MB in a mere minute. Without PA running, it's generally around 113 KB / minute.
So I started killing logging processes.
I killed logcat, and CPU usage dropped dramatically, but logd started hogging the CPU.
So I killed logd. It restarted, but no longer hogged the CPU.
So CPU utilization dropped from ~83% for PA, utilizing 4 to 5 cores, to ~60% for PA, utilizing 3 cores. Even with the CPU pinned to a maximum 299 MHz, playback was smooth.
As for logcat, after killing it, if you run it from your computer:
adb logcat -D -v long > c:\test\logcat.log
it'll begin log-spamming again (its the AudioTrack thread which is spamming the log) and the phone's CPU usage spikes again, but now, after having killed logcat once, when I stop logcat logging via ADB, logcat stops spamming the log and the phone's CPU usage returns to using 3 cores.
Get the CPU usage info:
adb shell dumpsys cpuinfo
inside that info, you'll see the PID of the applications. Look for logcat and logd. There might be more than 1 logcat, kill them all.
Let's say logcat is running two instances, with PID 239 and PID 760, for example (it'll be different each time you boot the phone), and logd with PID 13020.
Then issue the following commands from a command prompt on your computer:
adb shell
su
kill 239
kill 760
kill 13020
exit
exit
On my computer, if I type the commands too fast, ADB can't keep up, and ADB will crash, so give it a few seconds in between each command.
The above-described log-spamming behavior reoccurs upon reboot, so you'd have to do this after each boot.
Now I can listen to podcasts (I usually listen at 2x, sometimes as high as 3x for podcasters who talk slowly) without stutter, with the octa-core CPU pinned to 299 MHz maximum.
Related
I've been using FreshToast for a few weeks now, the latest one.
I have it OC'ed with OC Widget as I was having issues with SetCPU as others are.
One thine I notice is that when I wake my phone up sometimes the CPU usage is very very high, for upto about a minute after waking the phone up. To the point where it is unusable.
I have been using "SeePU" for a while, which puts a nice CPU activity monitor at the taskbar. It uses VERY LITTLE to NO CPU usage (confirmed with the adb shell "TOP" command) never more than 2%.
The other issue I'm having is once or twice a day when I get a phone call, the screen comes on but to the HTC Lock screen. When I pull the lock screen down, its usually a blank screen with a FC dialog saying com.android.phone or something is busy. The ring tone keeps ringing and ringing and ringing. I have to do a battery pull.
I've even ran the phone with NO DOWNLOADED APPS to rule out any variables. Its definitely a bug in the ROM.
Are you getting any of the problems I've listed?
The symptoms you describe have been noticed by others using setCpu. Another cause that has been discovered is that when using OC Widget DO NOT enable a different setting when the screen is off as this has been proven to cause the wake-up and phone call problem you described.
system_server is being a real pain for me. I found it may have something to do with the location services.
I had too many problems so I installed the normal Fresh Rom
http://forum.xda-developers.com/showthread.php?t=681856
and then I flashed the OC kernel over that
http://forum.xda-developers.com/showthread.php?t=690238
That combo has been working great for me and is basically what Fresh Toast should be.
I have moved over to Fresh and have been extremely pleased. I think it actually runs faster than Fresh Toast even with correct overclocking(on fresh toast that is). Just remember not to put OC programs on, or it will actually underclock.
I've rebooted the Tab a few times, but in OS Monitor, the "Download" process is running all time time using at least 30% processor!
What's the deal; anyone know? I'm unrooted and running the latest Tw update.
Thanks!
Ended up being MediaServer running. I stopped in in Manage Applications->Running. I stopped it and my CPU went to normal levels. My home screen responses got alot better too.
I vaguely remember this issue on my Samsung Fascinate too.... MediaServer always got hung up on some type of sync'ing.
I'm having the same issue. So what is actually causing this? Any way to disable the mediaserver all together? It seems to keep re-starting itself eventually.
I haven't found a way. It doesn't affect battery life as far as I can see, but it lags my Netflix if its running because its already sapping up 50%+ CPU.
Yeah, I've noticed that the tab gets laggy when it's running, and it speeds up a lot when I kill it in OS Monitor. That's my main reason for wanting it closed. It doesn't seem to affect battery life while the screen is off, but when the screen is on (such as reading an ebook) it absolutely reduces battery life. I just tried freezing it in Titanium Backup but it resulted in all the gapps (such as Gmail) crashing and refusing to open after rebooting.
I also noticed that on some boots, it's DRM Protected Storage Content rather than Download Manager. I just froze that instead and haven't noticed any issues from it yet, but I won't know for sure until rebooting.
I'm having a very similar issue, though it's process.android.media that is causing the problems. I have to manually kill the Media Storage service several times per day. It's quite annoying.
funnelweaver said:
I'm having a very similar issue, though it's process.android.media that is causing the problems. I have to manually kill the Media Storage service several times per day. It's quite annoying.
Click to expand...
Click to collapse
This Media application is what calls the Download Manager service. Killing this app also kills the service that's using alot of CPU processing.
I've noticed that I get a lot of errors in logcat pertaining to the sdcard. They are usually right around the time that a media process starts up, but I have hundreds of them throughout the log:
E/Environment( 1250): getExternalStorageState/mnt/sdcard
E/Environment( 1695): getExternalStorageState/mnt/sdcard
See attached screenshot.
It appears something is wrong with reading the sdcard, and I'm guessing this is maybe causing the media process to hang eating all the cpu?
Hello.
I have an SM-N9005 Galaxy Note, running original KitKat 4.4.2 (N9005XXUENC3), rooted with Towelroot, with Xposed framework. I have a problem which consists in the CPU cores not becoming offline, when the load is marginal. All the cores run then at 300Mhz, but only one of them is really used and its load is marginal (<10%). Both process manager and the console top command show almost no activity. In a "good" state (after restart, for instance), 3 cores become offline, only the 0th one keeps working at 300MHz (which is good).
I'm not talking about the deep sleep, becouse the phone enters deep sleep without any problems - it simply doesn't turn off cores. It does not happen just after a restart, but some (random) time later.
The problem is, I cannot detect, what is causing such behavior. It seems that "something" is turning off the "offline capability". I have no idea, how to check it (and what). Has anyone noticed such weird behavior. Maybe the solution is known?
Seems that it's mpdecission process, that causes such behavior. Killing it from the terminal fixes the problem for a while.
Wytaptalkowane na notatniku
Need help... Intel Joying CPU Usage Spikes & Frequent Audio Dropouts on all apps...
It's especially prominent in Pandora. But also on Poweramp and Pulsar. Doesn't happen on iHeartRadio, however; what's happening is every 30 - 45 seconds I get a pause in the audio.. note when it pauses I notice the song time is still continuing so the actual song doesn't appear to be stopping, but I just lose audio. It lasts between 2 and 5 seconds. I tried disabling the stock music player but this seems not to have helped. I also disabled Bluetooth and it still didn't help. I do have a USB harddrive with several gigs of music but nothing is scanning from what I can tell. What could be causing this issue?
Edit: After some additional testing using the Trickster MOD, I am finding that the HU is running at 1040Mhz 99% of the time in a sample of 2 hours, however; when I lose audio I am noticing my CPU usage is SPIKING from 5 - 10% to 90% and higher for no apparent reason, then it drops back down and I regain audio... Temperatures remain between 40 and 45*C ... Any idea whats going on?
Looks like your HU is experiencing overheat problem when CPU has to throttle down.
I installed a heat sink and cooling fan on it already though and it solved my initial problem where my HU would lose GPS. How can I tell for sure because my new fans are definitely running yet my audio keeps skipping
Have you installed any CPU temperature measuring utility? Might give a clue.
ste2002 said:
Have you installed any CPU temperature measuring utility? Might give a clue.
Click to expand...
Click to collapse
what app would you recommend?
Also, Google Play downloads are EXTREMELY slow and take forever to install.
Need4Camaro said:
what app would you recommend?
Also, Google Play downloads are EXTREMELY slow and take forever to install.
Click to expand...
Click to collapse
I like CPU Temp Pure https://play.google.com/store/apps/details?id=com.yanyan.cputemppure - it was once free, now it is not. I like it because it is capable of outputting temp in the upper screen bar persistently (if this setting is enabled).
As to slow install, it can also mean CPU thottled down and if it is Intel, they say the app has to be compiled for x86 during install which takes additional time (I only repeat someone here, may be wrong).
ste2002 said:
I like CPU Temp Pure https://play.google.com/store/apps/details?id=com.yanyan.cputemppure - it was once free, now it is not. I like it because it is capable of outputting temp in the upper screen bar persistently (if this setting is enabled).
As to slow install, it can also mean CPU thottled down and if it is Intel, they say the app has to be compiled for x86 during install which takes additional time (I only repeat someone here, may be wrong).
Click to expand...
Click to collapse
I'll try that. If it comes to a point where I may need a new HU, what would you recommend? Not sure if I really like Joying, especially because their overheating issues.
As to me, I am not an expert at all: Joying is my first (and current) experience in Android HU. Keeping an eye on a HU market, I can not see anything that I would heavily wish to substitute Joying, which is just quite acceptable for my everyday usage.
-------------
You may want to search for CadillacMike posts - AFAIR he recently owned at least 3 different Chinese brand Android HUs, Joying included.
ste2002 said:
As to me, I am not an expert at all: Joying is my first (and current) experience in Android HU. Keeping an eye on a HU market, I can not see anything that I would heavily wish to substitute Joying, which is just quite acceptable for my everyday usage.
-------------
You may want to search for CadillacMike posts - AFAIR he recently owned at least 3 different Chinese brand Android HUs, Joying included.
Click to expand...
Click to collapse
Okay, I checked the CPU temp and its hovering between 37 and 41*C with poweramp running but poweramp is still skipping.
I notice my DEFAULT music app is still trying to locate music, is there any way to disable the default music app? I am believing it may be causing the problem.
Your temps are just ideal, very low for throttling, I believe. Mine are often around 80 - I still do not have any additional cooling. But I mostly tune to FM radio.
ste2002 said:
Your temps are just ideal, very low for throttling, I believe. Mine are often around 80 - I still do not have any additional cooling. But I mostly tune to FM radio.
Click to expand...
Click to collapse
Are there apps that can disable throttling and allow it to run at max CPU?
Look at GTX custom ROM thread as an alternative to Joying factory ROM - it may solve your issue. And gtxaspec himself did mention using some software to lock CPU on his HU to 1000 Mhz.
By the way: at some 80+C my CPU frequency shows 728? MHz.
ste2002 said:
Look at GTX custom ROM thread as an alternative to Joying factory ROM - it may solve your issue. And gtxaspec himself did mention using some software to lock CPU on his HU to 1000 Mhz.
By the way: at some 80+C my CPU frequency shows 728? MHz.
Click to expand...
Click to collapse
I was looking into that, looks like I would have to upgrade to Android 6. I did alot of mods to my 5.1.1 (Can use Google Voice Assistant, Audio works on all Navigation Apps instead of just the default one, Bluetooth mod) I'm assuming all that will go away..will I retain this features if I use his mod?
There is high probability that you'll have to reconfigure/install everything again. You may also encounter new issues you do not have now. Its not just a mod, but ROM.
Edited my first post:
After a bit more testing, I downloaded the Trickster Mod. My HU is becoming unbelievably slow. The trickster mod is showing my CPU temperature consistantly between 37*C and 44*C -- Never goes higher than 44*C. ...
CPU is running at 1040Mhz for the majority of the time, a sample of 2 hours showed it at 1040Mhz for 99% of the time... and at a much lower speed for 1% of the time. I can't remember the exact Mhz but what is happening is this..
I ran PowerAmp while watching Trickster and CPU usage remains between 6% and 15% for the majority of the time, and then when I get an audio drop-out, my CPU usage SPIKES to 90% or higher, I lose all audio, then it returns to about 5 to 10% and all audio returns...and it does this consistently where I lose audio during CPU usage spike. I do not know what is taxing my CPU so hard.
Any idea?
So I used an app to determine which apps were taking the most CPU usage, it turns out.. it was my Google App. I reinstalled my Google App and all seems to be well now.
After several factory resets I always got back high CPU usage, like AIDA showing all CPU cores maxed out. The tablet was connected to ADB and over a adb shell I did find with
adb shell
top -m 15
And it listed CNNS-daemon as continously using 30% load with all cores maxed out.
Eventually I found out what to do.
You have to uninstall: Google Device Health Service
https://play.google.com/store/apps/details?id=com.google.android.apps.turbo
After Uninstall mark it to not update or the all cores full high frequency bug will return.
You have to uninstall : Samsung Device Care
Device Care - Apps on Google Play
Device Care - optimize your Galaxy smartphone
play.google.com
Mark that one to not automatically update as well.
Another advice is to clean those two apps their storage and cache.
Use AIDA from playstore to see if your cpu cores are maxed out before and after.
This bug existed several firmwares ago, no factory reset worked since the bugs were coming from installing updates from Google Play.
The apps come both with your current firmware so you use the firmware default ones, especially the Samsung Device Care from factory firmware has more battery and CPU optional functions.
The battery consumption went from 13% an hour to 8% which is a lot improvement.
As of January 2023 this bug is sill not fixed. I found others with this bug. Only Samsung can fix it.
I have the same issue even after a reset and disabling these packages via ADB. Same process cnss-daemon using 2-3 cores all the time.
I have attached a screenshot of TOP via ADB. This is a stock, freshly reset tablet, in safe mode and airplane mode on and this is "settled" CPU usage. Another one is cdsprpcd which is somehow connected to Qualcomm DSP.
Notice how the CPU is only 660% idle, and sys is at 90%+.
TOP output for my Galaxy A70 with all my crap installed etc idles at 750%+, with the TOP command itself using the most CPU while it is running and sys making up less than 10%.
So yeah, something is wrong here, even on reset stock tablet.