Develop Bugs

Which kernel should I have if I just want OC?

My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?

legato89 said:
My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?
Click to expand...
Click to collapse
Baconbits, to my knowledge, is the only OCd kernel available for the stock ROM. Your screen issue might actually be caused by underclocking though, do you have a screen off profile or a minimum set?
Sent from my T-Mobile G2 using XDA App

I just have it set to 368-1497. Should I up the minimum?

legato89 said:
I just have it set to 368-1497. Should I up the minimum?
Click to expand...
Click to collapse
Give the overclock widget a try. Its available free on the market. In the advanced setting, set your screen off profile to 245 min and 806 max. Scroll down and hit "save" before you exit settings. That will keep your phone running at stock speeds while the screen is off and should stop the wake issue you're having. When you're using the phone you'll be at the higher speeds.

I already had the widget. Did what you said but it still occurs.

legato89 said:
I already had the widget. Did what you said but it still occurs.
Click to expand...
Click to collapse
245 is *way* too low, especially if you have things running in the background ... just start raising the lower end up until it stops happening.
Sent from my T-Mobile G2 using XDA App

Setting it to stay at 800 while the screen is off seemed to fix it. Any ideas about wifi calling bugging out? It usually doesn't happen very often, I think when my phone has been on for a while without a restart.

overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.

dietotherhythm said:
overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.
Click to expand...
Click to collapse
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App

EdKeys said:
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
set the off screen profile to the lowest speed 200/200mhz and 100% priority and he wont have anymore wake issues, don't know what I was reading hahaha

The screen on issue doesn't happen anymore but I'm not satisfied with my battery life. In the past something was causing my battery to drain insanely fast so I un installed a bunch of unused apps and started checking background tasks but when browsing the internet for 20 minutes on my way home I use 30% of the battery, bluetooth on.
Sent from my T-Mobile G2 using XDA App

Anyone know if it is possible to run Pershoot's kernel on the stock rom that comes with the device? Any side effects?

I don't know enough to say 100% one way or the other, but I read in a post I can't find right now that only BaconBits is made to work with the stock rom.
FWIW, I tried to flash the 1.8 GHz kernal on my stock G2 this morning, and got stuck in a boot loop.

On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.

legato89 said:
On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.
Click to expand...
Click to collapse
NO. The first thing you need to do is flash clockworkmod 3.0.0.5, which is totally different than ROM Manager. As of right now the latest clockworkmod available through ROM Manager is 2.5.1.3. If you haven't flashed that yet (2.5.1.3) do that first through ROM Manager. The best way to flash 3.0.0.5 is to find the .img file, place it on your sd card and run the commands from terminal emulator. After that just wipe data/factory reset, wipe davlik cache and flash the latest nightly .zip, reboot, then the latest gapps .zip. Go to the development forum and the first post in the nightly vendor vision thread has all the links you'll need.

Wake problems.

My phone sometimes doesn't wake when I try and turn it back on after a while when the screen goes off.
I am running CM7 7.1.
I am using default oc settings. (ONDEMAND, 300-ish min, 1110-ish max, no undervolting as far as I know)
I tried to press the button combo to get fastboot but it doesn't work either. I have to take the batteries out for the phone to restart and then it works again.
What gives?

convolution said:
My phone sometimes doesn't wake when I try and turn it back on after a while when the screen goes off.
I am running CM7 7.1.
I am using default oc settings. (ONDEMAND, 300-ish min, 1110-ish max, no undervolting as far as I know)
I tried to press the button combo to get fastboot but it doesn't work either. I have to take the batteries out for the phone to restart and then it works again.
What gives?
Click to expand...
Click to collapse
368 is the lowest you should go and, even then, you might run into wake issues. Additionally, if you have anything like SetCPU installed, be sure you don't have a screen off profile set with too low a speed.
Sent from my HTC Vision using XDA App

It seems to be mostly a cpu clocking issue. Raise your minimal clock for screen off profile if you have one and it should work.
Sent from my T-Mobile G2 using XDA App

I don't think that is the reason.
Back during CM6 6.0 RC1, I had set CPU with 256mhz off screen, and it was perfectly fine back then...

convolution said:
I don't think that is the reason.
Back during CM6 6.0 RC1, I had set CPU with 256mhz off screen, and it was perfectly fine back then...
Click to expand...
Click to collapse
Are you using SetCPU?
If you are (and it's really not needed anymore) make sure your max on the screen off isn't set low as well. You can sometimes get away with a low min but, if you have a 256min/256max, you're basically telling your device to stay at 256 whenever the screen is off and no amount of pushing the power button to wake it will change that.
Sent from my HTC Vision using XDA App

Not. I uninstalled SetCPU. Using the built in govenor now...

The problem you seem to be having is a bsod or black screen of death.
If you search that term in the forum you will find a few posts about it.
The only thing that i am aware of about the issue is that it is related to the use of your gps.
I have had trouble replicating the issue, it happens very randomly. I sent my phone to bell and they didn't fix it...

Same problem here i think its a cm7 problem
Sent from my HTC Vision using XDA App

tvdang7 said:
Same problem here i think its a cm7 problem
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
In my case it was a battery issue.
To be sure I tried the experience 3 times: OEM battery for a day, ebay one for an other.
At the end I had a black screen ( sleep of death) every time I turn off the screen on the ebay battery (galilio).
The voltage was alright, it was something else.
running virtuous unity 2.37

I've had problems with the screen-on and screen-off animations causing a black-screen-of-death.

[Q] Trinity Kernel settings

I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?

I had similar issues. Not flowing very well , reboots and crashes. Also even though I bought the trinity app changing the clock speeds made the phone very very unresponsive. Tried many times to install it but no luck. Swapped back to Franco / glados (tried air kernel which was nice for battery but a bit laggy)
Franco also has trinity settings you can play with
J
Sent from my Galaxy Nexus using xda app-developers app

Me personally had a better experience than Franco. But all the phone are different and some might like trinity and some might like Franco. Seems like yours like Franco more
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz

Personally I've had ridiculously good results with Trinity - with 384 GPU, not 512 (1536-384-Stable35). Absolute butter even when I have very resource heavy, multiple, tasks running - and havn't had a forced reboot, freeze or anything of the sort even once. Interactive/SIO, min 307, max 1190. Everything else on default (except screen colours/gamma which I changed to my liking).
That said, if the 384 GPU is also not working for you I suppose you can give Franco or the other kernels a try, every phone set probably responds a little differently to each kernel.

cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
What trinity kernel are you using? I am on trinity 384 Alpha 56 and it is butter smooth... even get great deep sleep with it.
Sent from my Galaxy Nexus using xda app-developers app

cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.

I have good flow with trinity kernels. No lag or unresponsivness
*Who needs a gs3 when you have a NEXUS*

simms22 said:
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
Click to expand...
Click to collapse
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2

cmstlist said:
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i like ondemand/deadline. overheating.. whats your cpu temperature? most think that their devices are overheating when it falls in the normal range. tkt comes with widgets(in the app drawer widget menu), put the no background cpu temp widget on your homescreen and youll also get a cpu temperature reading in your status bar. at 100C the thermal throttle will kick in to lower your cpu speed and cool down your device. the safety shutdown temperature is 110C, your cpu will automatically shut down at that point. 110C is only reachable if you turn off the thermal throttle in the tkt app and you are benching your phone at a high oc. otherwise, i wouldnt worry about overheating.

The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??

cmstlist said:
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
Click to expand...
Click to collapse
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.

Despite the fact that I disabled "Set On Boot" in Trinity Kernel Toolbox, it does seem I'm still set to interactive/sio on boot. And check out the logcat I captured over USB when I was doing a reboot and it locked up:
http://pastebin.com/sSe9eFXT
In particular to trim out just the TKT lines and the last few lines before lockup:
Code:
D/TKTBootHelper( 1853): TKT: Boot Completed
D/TKTBootHelper( 1853): TKT: Set file permissions.
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
D/TKTBootHelper( 1853): Current Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): Previous Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): TKT: Versions match, let's restore settings.
E/vpnapi ( 1672): Function: Connect File: AndroidIPCSocket.cpp Line: 172 failed
to connect fd=38: Connection refused
E/vpnapi ( 1672): Function: Run File: LocaleChangeMonitor.cpp Line: 140 Invoked
Function: AndroidIPCSocket::Connect Return Code: -26476533 (0xFE6C000B) Descrip
tion: ANDROIDIPCSOCKET_ERROR_CONNECT_FAILED
So it would seem that right after TKT says "let's restore settings" it locks up, if the screen is off, when set to interactive/sio. Huh?

simms22 said:
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Click to expand...
Click to collapse
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.

cmstlist said:
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
Click to expand...
Click to collapse
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.

simms22 said:
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
Click to expand...
Click to collapse
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2

cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
does your rom have its own cpu settings? maybe theres something enabled in there?
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
smart reflex is a built into stock, it controls your voltages. the thing about it is that it doesnt know overclock or undervolting, so if you overclock or undervolt, it restores voltages for stock cpu speeds. which causes freezes if youre trying to overclock by setting the voltages too low.

simms22 said:
does your rom have its own cpu settings? maybe theres something enabled in there?
Click to expand...
Click to collapse
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2

cmstlist said:
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?

cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2

simms22 said:
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
Click to expand...
Click to collapse
No I do not. I will try reinstalling now since I uninstalled it completely.
morfic said:
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Again, pure stock flashed straight from Google, except for Trinity.

Reporting some weird sh*t that went down

So I was running stock rooted with jamesbond kernel and voltage control. Everything was fine, then I swapped batteries and rebooted. Once rebooted I noticed a lot of lag, so i went into voltage control and somehow everything was all messed up. My normal setting was i/o-deadline with interactive, running at 1200. But for some reason it was i/o cfp with hotplug and a max freq of 350 (same as the low). obviously this was the problem so I went to change the max frequency back up to 1200 and the phone froze. I tried rebooting and couldnt get past the google screen.After some wipes and restores, I ended up having to restore back to codename (only one that didnt hang on google screen). Everything there seems to work other than stock email which wouldnt open (error) so I had to reinstall the app from one of the other roms I have on my sdcard. But things seem to be up and running at the moment, just wanted to post this in case others have come across the problem. I'm thinking its voltage control and maybe it doesnt play well with this phone, needless to say I wont be using it again. Guess I'll just stick to custom roms that have kernel controls built in.

Possibly battery. Change your voltage settings.
...

@rbiter said:
Possibly battery didn't your voltage settings.
...
Click to expand...
Click to collapse
My new sig.

:facepalm:

@rbiter said:
Possibly battery didn't your voltage settings.
...
Click to expand...
Click to collapse
That's why I never press the "Submit Reply" button without proofreading my post first.

063_XOBX said:
My new sig.
Click to expand...
Click to collapse
Hilarious. (MY new signature)
Sent from my Galaxy Nexus using xda premium

Soldier-2Point0 said:
Hilarious. (MY new signature)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
@rbiter Stole it from me.

Music skipping/freezing when screen is off

I notice that whenever I play music (Pandora or Google Music) with the screen off and a bunch of recent applications, the sound will skip and stutter. This only happens when the screen is off AND when I have a bunch of recent applications open. It sounds like an issue with how JB is handling RAM, but I have 80-90% ram usage at most when it happens; or perhaps is an issue with the wakelock under heavy RAM usage. If I clear all the recent applications by holding the home button down and clicking the trash icon, this problem goes away.
Phone Info:
- Teshxx's stock T-889 rom odexed (03-05-13) 4.1.2
- Baseband T889UVALK8
- Model: GT-N7105 (I could rename to T-889 but I believe this is relevant to the issue)
Attempts to resolve:
- Wiped dalvik cache and regular cache
- Installing newer versions of Teshxx's stock odexed rom
- Wiped app data from Google Music and Pandora
Potentially related:
- I deleted the stock music player and musicFX app
- I deleted some other miscellaneous apps
- I have some tasker profiles that address both Pandora and Google Music (one is a trigger to open Pandora, the other is to increase volume of Google Music)
- I have not tried and would like to avoid doing a full system wipe

Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.

IAmSixNine said:
Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.
Click to expand...
Click to collapse
Do you usually have the screen off and have a bunch of recent apps?

Same happens to me with LG O3D in every music player (only while screen off). Even If I Use only 70 % of ram
Sent from my LG-P920 using xda app-developers app

Jinra321 said:
Do you usually have the screen off and have a bunch of recent apps?
Click to expand...
Click to collapse
Screen is off when im driving.
Ive gone days with out rebooting my phone, and i dont go in and stop them. So yes recent apps has what ever has been opened in between reboots.

Probably a ROM issue. I am back onto stock with my gs3 (Waiting on note 2) and have never had those issues. O have had them on different ROMS though.
I can have tons of apps open and screen off and no issues on stock. Shouldn't be a RAM issue either as 2G is plenty.
Sent from a galaxy far away!

I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app

SIGMAxB said:
I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.

Jinra321 said:
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.
Click to expand...
Click to collapse
With a script
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Are you using voodoo sound?

Could be ROM, kernel, CPU settings, etc. This happened to me last week with the CM nightlies. I installed an update & my music started stuttering like crazy when the screen was off. Turns out I had the CPU settings customized for a special kernel but hadn't reinstalled that kernel, so the phone was trying to manage the stock CM kernel with settings for the custom kernel.

This used to happen to me before I switched to Perseus kernel. Since then I don't have the issue. Could you try that?
Sent from my SGH-T889 using xda app-developers app

I tried doing a full wipe and installed teshxx's N7105 t-mo rom (4/09/13) and did not use any throttling apps (everything else stock). The music was still skipping with the screen off, but I tried setting my minimum CPU speed to 400mhz (from 200mhz) and the skipping stopped (300mhz still skips). So I'm positive it's a problem with CPU throttling now. Since it's a full wipe and I'm still having this issue, I feel that it's a hardware issue. Perhaps I should just warranty my phone.

Changed governor to on demand and all is good.

Music skipping when screen turns off
Hey guys, I didn't realize how many other people were having this problem too....
My phone is rooted and I used ROM Toolbox Pro to turn up the min CPU value from 200mhz to 400mhz and it seems to work so far. So if you can find any type of app that can up your minimum value on your CPU it might do the trick. Because that stutter is super annoying....
I will keep you guys up to date if this doesn't work. But so far so good.

I noticed the same thing on my note 10.1 tab. Fully stock, first day i got it it did that with Google play music. Only noticed it that one time though. I'll report back if it happens again.