Database Info

[Q] MP3s Skipping/Stuttering Routinely

So yeah, just what the title says.
I'm running a T-Mobile NS with a CM7 nightly build (#212) and the stock kernel in said build. No matter what I do, my audio will briefly skip from time to time when playing MP3s with the screen off. I can't figure out why or how to stop it.
It doesn't seem to matter which governor I have set. It skips on ondemand. It skips on interactive. It skips on smartass. It skips on conservative. I haven't tried performance, because I need my phone to actually last the whole day. It doesn't seem to be related to clockspeed. It just skips no matter what I do.
Even with Voodoo Sound, there's no way the music player should need more than 1GHz to play audio. My last Samsung device, a Vibrant, and the phone I had before the NS, a mytouch 4G, never once had this problem.
So yeah, it's annoying. What gives? No matter what I do--short of reverting to stock (I haven't tried that yet, and I like CM7 too much to give it up)--it doesn't seem to help.

I can tell you I get the same issue with mine on 199. Which app do you use? I use mixzing

Same here with power amp, nexus nv rom.

What do you guys have set for your min cpu. I would guess 100. Change it to 200 and see if that helps. I am an avid runner and this is what I have found to help me.
Sent from my Nexus S 4G

I'll set it to 200 and see what changes I get. The skips are so brief and intermittent it may just get hung up at 100MHz and can't jump to the next frequency before it falls behind for just a split second.

synaesthetic said:
I'll set it to 200 and see what changes I get. The skips are so brief and intermittent it may just get hung up at 100MHz and can't jump to the next frequency before it falls behind for just a split second.
Click to expand...
Click to collapse
What governer are you guys using? I used to get this with smartass. Try ondemand /something else

Same issue with the Sirius app...
kinda weird.
Also tried all governors...
On NSCollab 1.0.42

bringonblink said:
What governer are you guys using? I used to get this with smartass. Try ondemand /something else
Click to expand...
Click to collapse
I've been using ondemand, 1000 max 100 min, 30000/85. Bumping it to 1000/200 seems to have solved the problem.
I'm guessing that the MP3 player can deal with running at 100MHz most of the time, but it's really close, and if CPU usage spikes a bit (due to background processes, updates, syncs, notifications) it can't bump up to the next step before the MP3 decoder falls behind.
Max clockspeed doesn't seem to affect it at all. As an experiment I capped my clockspeed at 400MHz (ondemand 400/100) and it didn't skip any more than usual, so it may end up working with smartass as long as the screen off max is set to 400 or higher.

2nd core clock speed

Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.

ggrammer said:
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
Click to expand...
Click to collapse
when it's needed, it goes to the required frequency...

sounds reasonable but I will notice some lag and stuttering while I am using the xoom, i will open os monitor and the second core is sitting at 216, i move it manually to 1.5Ghz and the tablet is more responsive...
Edit
Sorry I should have been more specific about the situation. When I say the 2nd core drops to 216 I mean the max frequency drops to 216 so the 2nd core does not clock up any higher unless I manually intervene.

same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.

okay i see wat u mean...i just checked and i'm getting the same results... it sits on the min freq, all laggy, then when i manually set the frequency, it's super responsive like it shud.... i'm over-clocking to 1.6 btw

burgi400 said:
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
Click to expand...
Click to collapse
I don't think that it strictly a SetCPU problem. I also have an Advent Vega and have used SetCPU to overclock it. Had almost the same problem, except both cores were stuck at 216Mhz.
Tried multiple overclocking apps and have had the same problem with all of them. Device fine until it goes into sleep mode, CPU stuck at 216Mhz when brought out of sleep. Even setting the minimum setting to 456Mhz still resulted in the CPU being stuck at 216Mhz on wakeup.

so i guess the big question is whether it is the kernels (I've tried a few) or in the way these apps OC a dualcore processor...It makes me wonder about the OC apps though, they were all built for single core originally and in each of them you only set 1 max and 1 min speed. OS monitor is the only app that displays both cores, at least that I have used, but it doesn't set an OC value at boot. Maybe if one of the smart devs on here could comment maybe even just to shed some light on this

Is there no solution to this issue yet?
Is it a tegra fault/problem?
Is it a Kernel issue?
Would flashing back to a stock kernel fix it? (if that is even possible...)

Ondemand vs Lazy Governor

Guys, can you help me out?
Something odd has been happening on my phone. I run Matrix kernel 9.5 on Lazy Governor and everything's fine, but when i turn it to Ondemand the phone starts to reboot randomly.
Does anybody know what can it be?
Thanks!

Try running different min and Max frequencies and see if that helps.
Sent from my Nexus S using Tapatalk

have you fiddled with the voltages

I tried different min and max frequencies and I also played a little bit with voltages. What i realized is that if the voltage is too low for a particular frequency my phone reboots. Do you know how can i teste how far i can get with OC?? If i OC to 1.2GHz for instance, and my phone reboots... Can i put a higher voltage to 1.2 frequency in order to get it working?
Thanks in advance!

Try to increase the voltage as small as possible until it not reboot
But be carefull! Increased voltage can damaged your cpu.
I prefer dont do OC, this device is fast enough on default freq.
Sent from my Nexus S using XDA App

[Q] Anyone use CPU Spy on their Skyrocket

Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?

Yeah I used it since yesterday. I've frozen a ton of bloatware via TB and it went into deep sleep for 7.5hrs last night while I was asleep. I'm seeing a crazy amount of different CPU speeds in there too though. Very odd.

I actually removed all the damn bloatware instead of freezing them. But then I added my own apps that I normally use. But I think I have finally weed out the damn app that is causing my deep sleep issues. it's either FriendCaster Pro or Google Music Beta...

I gave it a try yesterday when I first picked it up. Seems to either idle really high, or low depending on what your doing. Hardly ever used the mid range cpu frequencies.

yes! Once the source code can be.... had.... Kernel development would begin. As anyone have seen using CPU Spy, the governor either MAX out the CPU or just lower it to the minimal, it "rarely" stays in the middle. With some "tweeking" how the CPUFreq works we can probably save battery

mbze430 said:
Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?
Click to expand...
Click to collapse
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.

RAVEN6 said:
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.
Click to expand...
Click to collapse
Are you having any problems with Antutu keeping the setting at 192, after I reboot my phone Antutu keeps changing the low setting up to 384? Yes I have it set to apply on boot. I sent the Antutu devs an email a few days ago asking them about this, but no reply?
Sent from, The Eclectic Chair.

I thought this was the deep sleep issue that people have with certain chargers?? plug charger in and let screen turn off then turn screen on and unlock, then unplug charger. Check to see if it goes into deep sleep then or just reboot the phone after charging....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

[Q] Screen doesn't turn on

I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.

I have the same problem too. For awhile thought it was to an app I moved to sd card (walgreens). Wasn't as often moving app off sd card.
Sent from my MyTouch 4G Slide using Tapatalk

m3gz said:
I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
Click to expand...
Click to collapse
I've seen this happen as well with various roms as well (including 9.1). I currently am using tbalden's 10.1, and haven't seen it in forever. I don't know if he fixed it, or I've just been lucky.

I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?

m3gz said:
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
Click to expand...
Click to collapse
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz

I keep mine at 1512 too. Low at 192, going to try 384 for a bit. I have not had the problem for awhile though.
Sent from my MyTouch 4G Slide using Tapatalk

Ziida said:
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
Click to expand...
Click to collapse
Thanks for the advice.
I remember having my max frequency at 1512 MHz before so I thought that wasn't a problem.
So far 540 MHz minimum has kept my phone from going blank. I'll try 192 Mhz next

I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.

Saem persun said:
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Click to expand...
Click to collapse
192 MHz worked for me. You can try doing something extreme like what I did to see if it's the minimum frequency. It may decrease battery a bit but it's better than having the annoying black screen. I tried 540MHz as a test frequency.
Not all processors are the equal. So what may work for some may not work for others.

Same problem here. Black screen on Doubleshot with CM 10.1. Made me really concerned when it happened, as I was was reading the hardware maintenance thread earlier today (for fun) so I thought the LCD went.
This is the first time this has happened in the three weeks I had this phone, and I've been on 10.1 for almost a week now.
Because battery life[1] is an issue for me as well, I edged things up only slightly (from 96 MHz to 128), hopefully that will do to the trick. If not, I will try 192 MHz.
[1] Speaking of which, any tricks on keeping battery usage low? I use Deep Sleep Battery Saver which helps out a lot. And I'm selective about my apps (removed Songza because it was hanging around while closed, eating up battery life). GPS stays off, although I keep Wi-Fi and 3G on. It looks like the screen becomes the biggest draw at this point. Any advice would be appreciated.

Since the problem in March, I have upped the minimum frequency to 192mHz. For the longest while I haven't had any issues.
But since I installed my new Anker battery (was on a half-in-the-bag EZO Power 1900mAh), the problem came back, happened twice now, a week apart.
I'm trialing KitKatDS right now, but will probably go back in a week or less due to wakelock (Android OS) issues. Judging by above, when I do I will bump up the minimum even higher. Hard to see the correlation with how the battery will be causing it, but I see no other change.

Upping the lower end frequency seemed to work for a bit but i'm still getting the screen issues. I'm using a 3500mAh battery from China but I'm just doubting that the battery affects the screen.
The correlation of frequency to screen issues could also be coincidental.

m3gz said:
The correlation of frequency to screen issues could also be coincidental.
Click to expand...
Click to collapse
I wonder if the scheduler has anything to do with screen as well, that is, if CM uses a different one from stock?
Sent from my MyTouch 4G Slide using XDA Free mobile app