And after correcting the bug audio of Nexus 5 and lags software of LG G3, I return this time with a bugfix against glitches and metallic sounds on music players in CM 12 roms.
The team cyano did a bad job on the kernel of CM12, since it was discovered that the cause of the glitchs was the non use of hotplugg with two cores always active in standby. Even Franco with his kernel solved the problem with the latest release r37, but the kernel has bad performance compared to stock kernel.
With this short guide you can activate the two cores for ever, to eliminate audio glitches on CM12 base roms!
1) Download from playstore the app called "CPU Performance Control Free" of mugich (requires root).
2) Open the app and in profiles select "add new profile" that provides:
Core 0 in "Core always enabled" (Min 300 Max 2457 MHz) and set it as Interactive
Core 1 in "Dynamic core hotplug" (Min 300 Max 2457 MHz)
Core 2 in "Dynamic core hotplug" (Min 300 Max 2457 MHz)
Core 3 in "Core always enabled" (Min 300 Max 2457 MHz) and set it as Conservative (because you can t change this value)
Now save your rule with a name, and after re edit the saved profile and change Core 3 from Conservative to Interactive (now you can change the value, it s a bug of app!); resave the rule.
Now select the profile saved and go in settings and check "apply active profile on boot".
Reboot the phone and enjoy your music glitchs free !!!
Could disable offload for audio in build.prop as an alternative.
I don't like that there is always icon for root access visible.
Sent from my A0001 using XDA Free mobile app
Is this the glitch that sounds like a sample of the audio gets repeated for a fraction of a second when screen is off at random times? I've noticed this with almost every player, only Apollo and the player that comes with CM12 don't have this issue, and it never happens when screen is on.
fards said:
Could disable offload for audio in build.prop as an alternative.
Click to expand...
Click to collapse
That dont remove all the glitches
gonna try this out, thanks!
My question is, why does 2 cores need to be on always to stop audio glitches? It worked fine with one core on kk. Why is it different on lollipop?
Sent from my A0001 using Tapatalk
That's a bit outdated. Not sure when this was done but I see two cores staying online. The CPU cores aren't related. Cyanogen is working on improving audio and getting it to work with nuplayer and enable offloading. There will be issues in the porting process.
Don't compare nightlies of cm12 to a stable near last build of cm11s. That's like apples to oranges. Their builds use hotplugging - mpdecision - not sure where your info is from.
worked for me
Worked for me too. Thank you!!
I cannot set to Min 300 mhz. any issues keeping as it is the default value? thanks
Going to try this .....Thanks for sharing..
In my case the audio shuttering while playing on my car stereo still remains although the duration between them is now long.
Sent from my A0001 using XDA Free mobile app
This seems to help quite a bit but doesnt solve all the issues when using with Bluetooth.
Here's my situation, using todays Nightly and stock CM12 kernel (or any for that matter):
wired headphones - everything works great.
bluetooth with screen on - stutters/laggy/distortion
bluetooth with screen off - everything works great.
I dove a bit deeper and also found this:
Bluetooth with car strereo (Subaru Impreza 2013 Sport Limited) -- stutters like crazy when screen is on.
Bluetooth with stereo headset - works great all the time.
Bluetooth with wireless speaker (Tango TRX) - works great all the time.
Bluetooth with Belkin BT stereo adapter - works great all the time.
So, my current conclusion is that this only has issues when using with my car stereo. This happens to be the only paired device that displays song/artist/album info on display. The others do not have this feature. I also have BT drops when using my car stereo answer phone calls.
danieldmm said:
That dont remove all the glitches
Click to expand...
Click to collapse
I've had this problem on a Galaxy S4 GPE Lollipop ROM, in that ROM's changelog:
-Turn off experimental NuPlayer by default - Should help fix some audio stuttering issues once and for all.
Worked for me. You can change this in developer settings. In my experience it's a combination of kernel issues and this setting.
This actually made things a hell of a lot worse for me!
Before I had pops every couple of seconds, enough to make me stop listening to music and only listen to podcasts and audiobooks.
After following your instructions to a tee I now get some bizarre time-stretching effect on bluetooth: everything gets pitched up with tons of audio 'holes' to make up for the contraction of the sound. Just tried to listen to Simon Mayo interview Colin Firth - it was like listening to Pinky and Perky MCing over breakcore.
I wonder if audio is ever going to work on lollipop on this damn phone...
nuplayer is the culprit
just disable nuplayer in developer options and no audio glitches
eViLsTieFel said:
nuPlayer is definatelly not the cause of the issue for me.
Disabling it on 20150131 nightly and the glitches are the same.
Click to expand...
Click to collapse
Use the latest temasek linaro build it works for me
nuPlayer is definatelly not the cause of the issue for me.
Disabling it on 20150131 nightly and the glitches are the same.
nikhil18 said:
Use the latest temasek linaro build it works for me
Click to expand...
Click to collapse
Wow, back-in-time-quoting, this sure as hell won't be confusing to anybody .
I just ended up installing franko's kernel r37 yesterday, fixed the issue for me.
Besides disabling nuplayer kills the ability to play web based videos entirely...
Sent from my A0001 using Tapatalk
Related
I'm having a small issue with my sound. I'm running CM7.0.0 with the stock kernel. I'm trying to play videos from internet sources (Netflix, Youtube app, and in browser videos) and I keep having the sound skip or stutter. Sometimes it's not real bad like once every 30 or 45 seconds and sometimes it's every 5 or 10. I'm pretty sure it's not just my internet connection cause it did it at home when I was on my home network (whatever the Verizon fiber optic one is called). Any one have ideas on what I can do to fix it or is it a normal expected problem that I just have to deal with?
p.s. I don't have any experience using my own videos so I don't know if they would have the same problem.
FatherSauce said:
I'm having a small issue with my sound. I'm running CM7.0.0 with the stock kernel. I'm trying to play videos from internet sources (Netflix, Youtube app, and in browser videos) and I keep having the sound skip or stutter. Sometimes it's not real bad like once every 30 or 45 seconds and sometimes it's every 5 or 10. I'm pretty sure it's not just my internet connection cause it did it at home when I was on my home network (whatever the Verizon fiber optic one is called). Any one have ideas on what I can do to fix it or is it a normal expected problem that I just have to deal with?
p.s. I don't have any experience using my own videos so I don't know if they would have the same problem.
Click to expand...
Click to collapse
It is entirely possible that using an OC (overclocked) kernel would fix your audio stumbling issues, however there is a lot of confusion with kernels right now as our developer is working on a .32 kernel and your version of CM7 requires a .29 kernel. (last updated .29 OC kernel was from 4/24). If you're not entirely sure of what you're doing with switching kernels, just don't do it. Something else you could try instead would be to set your governor on performance while watching video...It will keep your CPU revved up to the max the whole time. Governors are under settings/cyanogenmod settings/performance/cpu settings.
Thanks. I've always used the stock kernels and been fine so I don't really want to mess with that if I don't have to. I'll give the governor settings a try and see if that helps.
Well, that didn't seem to help and then I screwed up something else so it'll be a couple of days til I can really try to fix it. Guess I'll get back to this once it's fixed.
Hey guys. There's been something bugging me for ages about samsungs music player - a situation where the cpu locks at 800mhz during playback and screen off. When the screen is on it utilises normal cpu (mostly 100mhz). I use cpuspy to measure the stats in case anyone was wondering.
I didn't really do any scientific testing but at first I thought the bug was related to the kernel, but now I think it is a bug in samsung's music apk (in its handling of certain music files. The reason for this is that (on the latest JW6 + stock kernel), I can replicate the bug and isolate it to only certain music tracks.
So far I have not determined the reason certain tracks trigger the bug, but I have considered a few things
1. Filetype:
I have flacs and mp3s that trigger the bug and others that don't. However, this does not necessarily rule out the way/quality in which they are coded. Further testing needed.
2. Album art:
The presence of album art does not seem to cause the bug. I have tracks without album art that cause the bug.
3. Corrupted files/filesystem:
Unknown. All seem to play fine with other music players. I think this is an unlikely cause.
But anyways, I have some proposed solutions for others like me who want to enjoy the stock music player (on gingerbread of course).
Solutions:
1. Kernel tweaks:
Semaphore kernel has a function that locks cpu max to 400mhz during screen off music playback. This appears to work well (400mhz will save more power than 800mhz), but is still not ideal as the cpu will still lock at max (400mhz) for 100% of the playback time instead of changing as needed (which is most of the time 100mhz). The cpu max could be lowered to 100mhz or 200mhz, but this will cause slow wake from sleep and maybe other bugs (SOD?).
2. Screenstate profile script.
This seems like a simple solution for any kernel that supports init.d scripts. make a screen off profile that sets the max cpu to 100mhz (or changes governor to powersave). But I found that this doesn't work as desired with all governors - e.g. the music lock somehow overrides the powersave governor and continues to stick at 800mhz, and with ondemand/performance it will work well at 100mhz, but will cause SOD's when deep sleep begins.
3. Convert all music files into a format the will fix the bug.
Difficult/impossible as I have not found out what cause the bug.
4. Mod music.apk to fix the bug
May be difficult/impossible to do. However, there might be a music.apk from an old rom that doesn't have this bug (I don't know if this bug was introduced in a certain firmware or not).
5. Get a new music player
the obvious solution. Other players work well but I like samsung's the most due to the UI and battery life .
Other notes:
1. I am assuming that one will save battery by avoiding this lock. This may be a flawed assumption.
2. This could be an imaginary problem - cpu stats reporting bug? but I don't really believe this as it only happens with some music files not the music player in general.
3. I found another post in the Galaxy Player forum here that mentioned a similar bug - do a search or i can dig the link up again later.
I recently got a Galaxy S5 about a month ago and have been using LG Tones hbs730. While listening to music, whether it's streaming or on my device, it cuts out for a second or so. Sometimes it happens a lot at once and really kills the vibe. It almost sounds as if I was listening to music with aux headphones and I unplugged half way then plugged back in.. I have replaced the bluetooth with the HBS800's and the problem still persists. My Galaxy S4 did NOT do this. Any suggestions? I have tried just about everything. Thanks!!
Same problem with LG Tones HBS-750 fixed - sort of
jljones06 said:
I recently got a Galaxy S5 about a month ago and have been using LG Tones hbs730. While listening to music, whether it's streaming or on my device, it cuts out for a second or so. Sometimes it happens a lot at once and really kills the vibe. It almost sounds as if I was listening to music with aux headphones and I unplugged half way then plugged back in.. I have replaced the bluetooth with the HBS800's and the problem still persists. My Galaxy S4 did NOT do this. Any suggestions? I have tried just about everything. Thanks!!
Click to expand...
Click to collapse
I had the same issue with my AT&T S5 GM-900A and an LG HBS-750 bluetooth headset. Found the problem starts when the screen goes to sleep. I installed ScreenON just now and set it to the dimmest level. No more skipping. Unfortunately the screen does stay on, but it's a workaround. :fingers-crossed:
Just search the Google Play store for Screen ON
jljones06 said:
I recently got a Galaxy S5 about a month ago and have been using LG Tones hbs730. While listening to music, whether it's streaming or on my device, it cuts out for a second or so. Sometimes it happens a lot at once and really kills the vibe. It almost sounds as if I was listening to music with aux headphones and I unplugged half way then plugged back in.. I have replaced the bluetooth with the HBS800's and the problem still persists. My Galaxy S4 did NOT do this. Any suggestions? I have tried just about everything. Thanks!!
Click to expand...
Click to collapse
Yeah it's a common s5 problem. Put your phone in recovery and clear your cache that should fix it.
Sent from my SM-G900F using Xparent Cyan Tapatalk 2
No Joy
mrnovanova said:
Yeah it's a common s5 problem. Put your phone in recovery and clear your cache that should fix it.
Sent from my SM-G900F using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I just cleared the cache on my phone and rebooted. Using the stock music player, the music plays fine through the headset until the screen goes to sleep. Then it starts cutting out almost instantly. If I enable ScreenOn so it doesn't go to sleep or have it in daydream mode while charging, the music plays fine. Do you know of anything else we could try?
exet2 said:
I just cleared the cache on my phone and rebooted. Using the stock music player, the music plays fine through the headset until the screen goes to sleep. Then it starts cutting out almost instantly. If I enable ScreenOn so it doesn't go to sleep or have it in daydream mode while charging, the music plays fine. Do you know of anything else we could try?
Click to expand...
Click to collapse
If you're rooted you can try installing Viper4Android, I think it has an option to disable Bluetooth low power mode which might be the problem.
Tapped It!
According to the update's bug fix list, this bug was supposedly fixed in the 4.4.4 update. But since that update, my bluetooth audio cuts out just as much, if not more. Wiping the cache partition doesn't help at all.
Is there another thread that discusses this that's more recent and has more than three people addressing it? (i.e. since the 4.4.4 update)
fzdolfan said:
According to the update's bug fix list, this bug was supposedly fixed in the 4.4.4 update. But since that update, my bluetooth audio cuts out just as much, if not more. Wiping the cache partition doesn't help at all.
Is there another thread that discusses this that's more recent and has more than three people addressing it? (i.e. since the 4.4.4 update)
Click to expand...
Click to collapse
I've just switched from a sony Z1 to the s5 and noticed this issue with bluetooth in my car.
The Z1 was rock solid in the same car via bluetooth.
It seems the s5 gets drop outs when then screen is off for a while and i presume it turns some of the CPU cores off or something?
I have a g900F, there isn't a 4.4.4 firmware out for it yet? The Z1 was running 4.4.4 though and was OK.
i'm so happy that i'm not aline, not for you of course. Did someone find a solution? i also have the lg 730, and i also have sony z1, but i really can't use the 730 with z1, it was awful, and also have problem with the screen, so my phone company give me the s5, and i was happy , but i still have problems with bluetooth. Some tied another headhones?.
It is confime that the problem is because Bluetooth power?
potter3390 said:
i'm so happy that i'm not aline, not for you of course. Did someone find a solution? i also have the lg 730, and i also have sony z1, but i really can't use the 730 with z1, it was awful, and also have problem with the screen, so my phone company give me the s5, and i was happy , but i still have problems with bluetooth. Some tied another headhones?.
It is confime that the problem is because Bluetooth power?
Click to expand...
Click to collapse
I've got no idea what's the cause of this behaviour. However I pretty much tried every solution attempt that I could find on the net, except for rooting or custom ROM. Nothing has brought a solution for me, not even close actually. All actions taken seem to have no effect at all on the audio stuttering. Meanwhile my two brothers can play their music my home theater (which is what I'm trying to do) without a single hiccup for hours. It makes me think it must have something to do with a deeper problem. Bluetooth low power seems at least more likely to me than any other possibility, although that's highly speculative on my part.
I have been trying to get bluetooth audio from my phone to my home theater to work ever since I got this phone. It seems such a mundane task to me, yet Samsung seems to fail to fix this issue and I'm actually getting seriously pissed off at that.
When I contact Samsung support they seem to think this is a problem that is just on my phone and actually suggest to hard reset my phone and all that nonsense.
Meanwhile I updated to Android 5, the official version, but no change in this stuttering behaviour what so ever. And actually, audio to my home theater is one of the main purposes of this phone for me. The fact that I haven't been able to do that for many months now, well... That's a f**** sad situation.
And on top of all that, with the 5.0 update, I now get about 5 hours on a full charge (was getting at least 15 hours on 4.4.4). But that's another thread, I know.
FML
Sent from my Nexus 7 using Tapatalk
i came here with good news for me, at least. After triying lots of things, installing programas and unintalling them and Reading a lot i read somo post with the same problem of us. But in that post they focus the problem not in the bluetooth but in the cpu. They claim that the worst (because may be more tan one) proble is the cpu profiles to save battery. So tire with the bluetooth path i follow this new one. After some test (with tasker) i change my cpu governor from interactive to performance and almost solve the problem, i have a little jump now and them, but nothing too anoying. I need more testin because having the cpu governor in performance all the time kill my battery too fast. But at least i can hear music again with my belove LG-730.
potter3390 said:
i came here with good news for me, at least. After triying lots of things, installing programas and unintalling them and Reading a lot i read somo post with the same problem of us. But in that post they focus the problem not in the bluetooth but in the cpu. They claim that the worst (because may be more tan one) proble is the cpu profiles to save battery. So tire with the bluetooth path i follow this new one. After some test (with tasker) i change my cpu governor from interactive to performance and almost solve the problem, i have a little jump now and them, but nothing too anoying. I need more testin because having the cpu governor in performance all the time kill my battery too fast. But at least i can hear music again with my belove LG-730.
Click to expand...
Click to collapse
Well.. There's no changing the cpu governor without rooting.
A little jump now and then is still unacceptable for me. This phone is a cpu powerhouse so regardless of cpu governance or scheduling, this should work without any jump or cut out at all.
Are you sure it's not a coincidence that your situation has improved? I mean, with the cpu in power saving mode, normal audio playback without bluetooth should be pretty much equally problematic as playback with bluetooth. I've never had an issue with music cutting out without bluetooth usage.
I'm not sure of anything, at this moment i'm testing this, and without doing any other change i improve the quality to a level where i can use bluetooth again. Before i have between 3 and 5 jumps per song, and not little ones. Now one every hours or more and i thinks this ones are from other things, like gps and some programas that affect or bluettoth o music. From hear i'm not sure what to test next beside cpu, this one was my last bet before leaving bluettoth for ever. So any advice are welcome.
potter3390 said:
I'm not sure of anything, at this moment i'm testing this, and without doing any other change i improve the quality to a level where i can use bluetooth again. Before i have between 3 and 5 jumps per song, and not little ones. Now one every hours or more and i thinks this ones are from other things, like gps and some programas that affect or bluettoth o music. From hear i'm not sure what to test next beside cpu, this one was my last bet before leaving bluettoth for ever. So any advice are welcome.
Click to expand...
Click to collapse
You shouldn't hear any jump at all, even when you are using the phone for other actions as well. Quad core CPU and 2gb memory really is far more than you should need to do all those things. For example, one of my brothers has a Samsung Galaxy S3 mini. When he connects his phone to my home theater he can play music, lookup soccer results, read the news, ... All that without any jump what so ever. Obviously that's the way it should work.
I still got a laptop with a Pentium 3 550Mhz, 512mb memory, win2000, .... It's able to do all these things and it's almost 15 years old. There simply is no excuse.
For what i read is not a hardware problem it's the saving battery profile for the cpu. So you have the hardware but android tell the cpu to go veryyyyyy slow so you save battery
potter3390 said:
For what i read is not a hardware problem it's the saving battery profile for the cpu. So you have the hardware but android tell the cpu to go veryyyyyy slow so you save battery
Click to expand...
Click to collapse
Yah, you're probably right about the cause. But does that really matter, we're speculating anyway. The fact that ancient devices do this better than this modern device I'm using now is just pathetic.
yep you are right, its pathetic.
Enviado desde mi SGP511 mediante Tapatalk
Mine does it even with the battery saver turned off. Makes no difference.
Sent from my Nexus 7 using Tapatalk
SO... in regards to the KT-SGS4 KitKat 4.4 TouchWiz kernel, the vast majority of users seem to have no problems with it, but there ARE KNOWN issues that appear to be caused by this kernel for some users, with varying degrees of rarity. WHY certain users have these issues when others do not is not currently known, but it would be great if we could figure this out. I am HOPING this thread (and it will only be a THREAD with input from others) will help us find cures for the issues we face with this kernel.
KNOWN ISSUES:
#1. Sound skipping - This seems to be the most common issue experienced with the kernel and I actually would not call it rare. Some possible fixes for this are to: A) increase the Media/Music Min Mhz and Bluetooth Profile Mhz to around 702 Mhz or so, B) try using a different I/O Scheduler and try adjusting the Internal and External Read Ahead Buffers, C) change disable_hotplug_media from a 0 to 1.
#2. Phone freezes/locks up while charging
#3. Screen flickers when a window is open over the desktop
#4. Mobile connection/data (and possibly also GPS) loss a while after booting phone - this may be the rarest issue, but it is OBVIOUSLY the most serious. I have suffered from it personally. I contacted Ktoonsez regarding this and he denies it being a known issue since many thousands of users use his kernels and don't have this issue... I have confirmed multiple other users who DO have this issue and the only thing I see we have in common is the KT-SGS4 kernel. It appears that this issue MAY be fixable by using the "right" choice of governor and settings. The problem is that what the "right" choice of governor and settings are MAY be determined by your ROM. On stock rooted NAE with MF9 bootloader, using largely the kernel default settings, including the interactive governor, APPEARS to have cured this issue for me (as well as the freeze while charging), while using the ktoonserativeq governor or the pegasuq governor appear to have caused this issue (I am still in the process of investigating this...).
This is not meant to be in any way negative towards Ktoonsez and I certainly appreciate all the work he does to provide us kernels, but there ARE issues that some of experience and I hope this thread can help us work TOGETHER to solve them! If there are any other issue that you believe should be listed, please post them. If you have any possible cures, please post them. If you need any help, please ask. If you have any input, please post! :highfive:
I can't get his kernel to run on my phone for the life of me so I stuck with Negalite NAE Stock Kernel, but I use his kernel religiously on my wife's s3. Even using basically the same setup I still get skipping on music, phone goes unresponsive after charging a few hours. And a few others.
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)? I think the governor and adjustments are also critical in solving this problem. I've been using ondemand and somebody said interactive is also helpful. The other thing here is that it could be an issue of I/o scheduler. I've been using sio. I'm getting minimal skipping at this point. You're right that ktoonservativeq caused MAJOR skipping, even with tons of governor tweaks.
After switching to ondemand, my phone hasn't locked up while charging, but it has randomly locked up at other times. Weird.
On issue #4, I've lost data less with ondemand but it hasn't completely solved the problem. Sometimes I can toggle Airplane Mode on and off and get going again, but mostly that toggle won't even work and I have to reboot.
JesseAaronSafir said:
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)?
Click to expand...
Click to collapse
That is an interesting question, now that you mention it. I had been using ViPER4Android, probably while I was having the skipping issue, but I stopped using it in the long process of attempting to cure my mobile connection issue (I read something that made me think it could be related) and I'm actually not sure if I ever had the skipping issue without it.
Of all the issues though, this one is very common in the KT-SGS4 kernel thread, so I DOUBT (but don't know) that everyone experiencing it is using
ViPER4Android.
(Also, I THINK it skipped for me without Convolver turned on).
I haven't used v4a since I was on Negalites
elwood said:
I haven't used v4a since I was on Negalites
Click to expand...
Click to collapse
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
rsngfrce said:
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
Click to expand...
Click to collapse
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
arikdahn said:
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
Click to expand...
Click to collapse
I didn't forget it, it is issue #2!
#2. Phone freezes/locks up while charging
In my experience, the phone does NOT have to be off while it is charging to have this issue, it would happen to me when I was charging my phone with it on. Fortunately, on NAE stock rooted with MF9 bootloader, using the mostly default kernel settings with the interactive governor seems to have fixed this issue for me, as well as the mobile connection/GPS issue (knock on wood still...). I mainly just adjusted the I/0 Sceduler to noop and the Media/Music and Bluetooth Min Mhz to 702 Mhz from the stock settings. The only issue I am personally left with now is the screen flicker.
I don't think the screen being on or off relates THAT much to the music skipping issue, it skipped for me too with the screen on. Definitely I would say, using the ktoonservativeq governor with Ktoonsez' settings WILL result in music skipping... BUT, IMO, this MUST BE TAKEN INTO ACCOUNT, Ktoonsez DOES NOT HAVE OUR PHONE... how can his settings POSSIBLY be OPTIMAL for our phone? Think about that!
As far as your WiFi tethering issue, I am well aware of it personally, having read your other posts, but I don't know much about this (don't use it myself) and in another thread I was going to direct you to a link you are already aware of that didn't help. If anyone can help arikdahn with this, please jump in! :good:
I definitely had more problems with music skipping when the screen would turn off. Using ondemand or interactive with sio and 2048 read ahead caches seems to have almost completely resolved the issue for me. I'm still not sure which I/o scheduler is best.
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
rsngfrce said:
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
Click to expand...
Click to collapse
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
arikdahn said:
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
Click to expand...
Click to collapse
Hey, I'm not in any way disputing what you are saying, the point of this thread is to figure these things out! I'm certainly not presenting myself as the expert on these issues! I'm just a lucky one who seems to have mostly resolved the issues on MY phone. (BUT... I AM NO ANDROID EXPERT EITHER and will never claim to be, but I am not saying it is a limited-resources issues, what I am saying is that I believe the default settings will allow the governor to throttle down to below the level necessary to play music without skipping... I could be wrong, but that it what it looks like to me.)
Because SO MANY people APPARENTLY don't have MOST of the issues mentioned, I personally think this is highly related to which ROM you are using... though I don't know what ROM those other people are using...
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.