Hey guys,
Just recently updated to DLo0 Superclean and ever since my audio is a little crackly when playing either native music or pandora. Obviously the rom is suspect, but I am confused why it would matter as the kernel is the same as stock, and it shouldn't be affecting processing. Anyone have experience with this?
Use the search button. download Setcpu and set min to 200. You're welcome.
I had audio popping on DJ05 and DL09 but using set CPU and setting min to 200mhz fixed it.
Sent from my SCH-I500 using XDA App
woolster22 said:
Use the search button. download Setcpu and set min to 200. You're welcome.
Click to expand...
Click to collapse
I see. Thank you, and my apologies
Out of curiosity why does this present only with the superclean ROM? This seems like strictly a kernel issue, something that wasnt modified.
for anyone who needs it: SetCPU
Out of curiosity, does anybody know WHY changing the min CPU speed to 200 helps? Is it because the default min CPU is 100Mhz, and isn't fast enough to keep up with audio processing?
kent1146 said:
Out of curiosity, does anybody know WHY changing the min CPU speed to 200 helps? Is it because the default min CPU is 100Mhz, and isn't fast enough to keep up with audio processing?
Click to expand...
Click to collapse
Almost def, thats why im wondering if the new kernel is more aggressive in its clock settings.
I would say that it's due to 100mhz being to low and the scaling being setup so that it doesn't cross the threshold to be bumped up to 200mhz. That, or it's going just up to the threshold, then lowering some, and constantly going back and forth between 100/200mhz.
Yay my first post. Anyways, were you using the Adrynalyn kernel? I'm new to all this rooting and stuff since last night. I tried the Adrynalyn + superclean dl09 and I got some crackling and popping.
I was a bit stumped but I tried a different kernel and the popping is gone. Right now i'm using Stupidfast. so far so good
Thanks for the explanation w/o extra sarcasm. Much appreciated!!
Good info. Having the same problem here
Related
Is it safe to install SetCPU on the MyTouch4G now that we have permaroot? If so, what are the settings we should use with it? Just not sure if the current kernel has been tested with SetCPU or not, and if it works what version of SetCPU... 2.0.3 or 2.0.4?
Thanks.
I am running 2.0 4 with autodetect. Set at 1024mhz performance. No issues and been running 3 days now.
Sent from my HTC Glacier using XDA App
Mr Bill Florida said:
I am running 2.0 4 with autodetect. Set at 1024mhz performance. No issues and been running 3 days now.
Click to expand...
Click to collapse
So you're not overclocking it then, correct? What is your setting for the minimum frequency?
I have it at 245mhz.
Sent from a rooted myTouch4g Glacier.
set up a profile under screen off and set max down to 3000 and minimum at 2000...saves me ton of battery power now
also download auto killer memory in market and set to optimum for even better battery life
I thought that over clocking required a custom kernel?
Sent from my anti titanic
thelamacmdr said:
I thought that over clocking required a custom kernel?
Sent from my anti titanic
Click to expand...
Click to collapse
You do.
Sent from my HTC Glacier using Tapatalk
Were not overclocking... simply managing the CPU more efficiently at its existing speed set
Sent from my HTC Glacier using XDA App
awdlexusis said:
set up a profile under screen off and set max down to 3000 and minimum at 2000...saves me ton of battery power now
Click to expand...
Click to collapse
The closest options for this are the following:
368640 max
245760 min
What did you use for the scaling and priority settings?
EDIT - Added a screenshot to this post. I've tried both 2.0.3 and 2.0.4, and no matter what I set for the minimum setting it stays at 245 (not what I defined). Does it not work then on this stock kernel?
I was going to say the same thing, from what I have seen on my phone setcpu is not doing anything. It won't change any of the clock speeds whether boosting the low end or limiting the high end.
I have tried a few things like setting profiles for less than 75% battery to lower the max clock speed and that doesn't work either. Am I crazy or are others experiencing a placebo effect on profiles lowering clock speed when screen is off?
Sent from my HTC Glacier using XDA App
slowestcivic said:
I was going to say the same thing, from what I have seen on my phone setcpu is not doing anything. It won't change any of the clock speeds whether boosting the low end or limiting the high end.
I have tried a few things like setting profiles for less than 75% battery to lower the max clock speed and that doesn't work either. Am I crazy or are others experiencing a placebo effect on profiles lowering clock speed when screen is off?
Click to expand...
Click to collapse
For HTC phones need to be rooted and also disable perflock. In setcpu: menu->perflock disabler. I set my perflock to disable on boot.
vels13 said:
For HTC phones need to be rooted and also disable perflock. In setcpu: menu->perflock disabler. I set my perflock to disable on boot.
Click to expand...
Click to collapse
Hot damn, that fixed it! Now to test it out further to see how well it works here. I'm not looking to overclock, just underclock when I'm not using the phone. Thanks for the tip!
dustrho said:
The closest options for this are the following:
368640 max
245760 min
What did you use for the scaling and priority settings?
EDIT - Added a screenshot to this post. I've tried both 2.0.3 and 2.0.4, and no matter what I set for the minimum setting it stays at 245 (not what I defined). Does it not work then on this stock kernel?
Click to expand...
Click to collapse
yes thats the correct setting i didnt know off hand the exact.will stay at minimum untill needed,im on on demand
Best settings for battery life?
Here are my settings and have worked very well. Almost adding 24 hours of battery life.
CBConsultation said:
Here are my settings and have worked very well. Almost adding 24 hours of battery life.
Click to expand...
Click to collapse
wow... what kind of use are you putting on it? Also are you having any issues with lag or slow response?
Daguse said:
wow... what kind of use are you putting on it? Also are you having any issues with lag or slow response?
Click to expand...
Click to collapse
Just an average power-user. I email and text a lot as I own a consulting business. I am constantly on the go and need my battery to stretch as long as possible.
That is why I kept the stock kernel and didn't over-clock. I simply removed all the bloatware and non-essential apk's that I didn't need and set up a few profiles in SetCPU and now I can get an easy 2 days of power use out of it.
As I still employ the stock kernel and stock ROM I have no lag what-so-ever. Response is perfect IMHO.
CBConsultation said:
Just an average power-user. I email and text a lot as I own a consulting business. I am constantly on the go and need my battery to stretch as long as possible.
That is why I kept the stock kernel and didn't over-clock. I simply removed all the bloatware and non-essential apk's that I didn't need and set up a few profiles in SetCPU and now I can get an easy 2 days of power use out of it.
As I still employ the stock kernel and stock ROM I have no lag what-so-ever. Response is perfect IMHO.
Click to expand...
Click to collapse
SO I am new to this... I used your same settings and my bat shows 56%. On the my screen it still shows that its jumping from 1024-245. Am I missing something?
EDIT: N/M I am just dumb and forgot to preflock!
So I set my profile to have
Screen Off Pri 75 Max 3K Min 2K
Bat 75% Pri 50 Max 7K Min 2K
Bat 50% Pri 50 Max 3K Mn 2K
I will let you know how it goes but I am hoping for some good bust in bat life.
Had some issues when waking the phone, so I changed the settings on the screen off to Max 768. Going to test.
I also moved the 50 Bat to 30 and still getting good life out of it.
Well I have been experimenting with some profiles in setcpu and I have noticed a great increase in battery life especially when in standby a lot.
So i have done this according to what works for everyone else. But... my battery still drops from 100 down to 40 in about 5hours and it has been this way since the 2.2.1 smh. I dont kno what to do. I do text alot and get on facebook mobile semi frequently but mainly text and omg the phone gets up to 104 degreez wen using or charging. Any suggestions ? Or anythjng i may be doing wrong
Sent from my HTC Glacier using XDA App
I wanted to explain black screen issue many folks are encountering with overclocked kernels. The root cause is that voltages at higher clock speeds are not high enough to get the screen to turn on. In other words, if your screen is off and your phone scales beyond 800Mhz, the phone does not have enough power to turn the screen on. You'll almost always scale to the max the moment you hit that power button.
There are a few ways to prevent this from happening (from best to worst):
Create a "screen off" profile in SetCPU to restrict the clock to 800Mhz or below when the screen is off. I think it's obvious why this works. At the same time, a lot of people already do this, which explains why everyone hasn't been having the problem.
Use the conservative governor. Because it scales more gradually, it won't immediately jump past 800Mhz when you attempt to power the screen. There is still a chance of encountering the issue if you attempt to turn on the screen if the device has been busy for a while.
Increase voltages in the kernel. I started experimenting with this before I decided to come here and recommend the first two options. To get the screen to reliably turn on at higher clock speeds, we'd have to raise the voltages substantially. So we'd end up with more risk of damaging components, degraded battery performance and so on. Once the screen is on, the cpu does not actually need more power than it's being given in today's frequency tables. Thus, we'd effectively be increasing power consumption all the time to deal with a need for more power at screen on. Clearly a bad idea.
Unless you're using SetCPU profiles (or equivalent) or the conservative frequency governor, you're going to get black screens. Cyanogen, Pershoot, Evil's and my kernels all use roughly the same voltages, so you're going to need to apply this solution regardless.
There you have it.
*Applauds*
I bow down to your wisdom, sir!
Can you explain why this doesn't happen to me when I'm on CM 6.1.1 ROM?
With setcpu settings at 1209/368 (ondemand scaling, no profiles) I have black screens on Virtuous but neveron Cyanogen's mods.
rgl12miami said:
Can you explain why this doesn't happens to me when I'm on CM 6.1.1 ROM?
With setcpu settings at 1200/300 I have black screens on Virtuous but never
on Cyanogen's mods.
Click to expand...
Click to collapse
I'd have to do more testing to confirm but I would guess more load is generated (events triggered) with Sense ROMs at the time of wake, causing the ondemand governor to scale up to nearly max more rapidly than CM.
There's a simple way to see if it'll ever happen on CM. Set your governor to "performance", with clock speed above 1Ghz. Turn off the screen and see if it fails to turn after a few attempts at toggling it on and off.
I did what you suggested about 30 times and no one has failed. It's a shame,
because I do really love your ROM: speed is incredible. But what bothers me
the most is when the alarm sounds or I receive a call and the screen refuse to
lighten up. I will keep an eye on your rom and for sure I will be back on it soon.
Great job! The best sense rom i've ever seen.
Thanks for this. Works perfectly on my Stock SenseUI ROM with virtuous kernel
Thanks! That explains why the issue hasn't been happening since I set my profile to conservative. That was probably the most annoying issue since I got my G2.
I bet the fact that every cpu is different would also explain why it happens to some and not others.
Again every cpu is different, but here is my settings for screen off. Min 245 max 245. I started min 245 max 368, dropped max down and no adverse effects and great bat life. I have no blackscreen/wakeup issuses. I've been using setcpu to save battery since before the first oc module/kernel.
Would def test kernel that drops below 245 and/or uv it greatly.
fastludeh22 said:
I bet the fact that every cpu is different would also explain why it happens to some and not others.
Again every cpu is different, but here is my settings for screen off. Min 245 max 245. I started min 245 max 368, dropped max down and no adverse effects and great bat life. I have no blackscreen/wakeup issuses. I've been using setcpu to save battery since before the first oc module/kernel.
Would def test kernel that drops below 245 and/or uv it greatly.
Click to expand...
Click to collapse
What do you mean that every CPU is different? At the hardware, firmware, software level?
gee one said:
What do you mean that every CPU is different? At the hardware, firmware, software level?
Click to expand...
Click to collapse
I think he means every cpu handle overclocking differently, for example ive been very unlucky and my cpu cant handle anything above 1.1 Ghz and it crashes if i set it up any higher but lots of people running theirs at 1.8 and they are stable
its just like overclocking PCs every cpu handle overclocking differently even if they have the exact same spec.
I'm bumping this due to how useful this information is and how often the issue still comes up.
Sent from my HTC Vision using XDA App
rmk40 said:
I wanted to explain black screen issue many folks are encountering with overclocked kernels. The root cause is that voltages at higher clock speeds are not high enough to get the screen to turn on. In other words, if your screen is off and your phone scales beyond 800Mhz, the phone does not have enough power to turn the screen on. You'll almost always scale to the max the moment you hit that power button.
Click to expand...
Click to collapse
I don't understand why I don't encounter this issue at all with AOSP ROMs. Is there an obvious reason I'm missing?
poochie2 said:
I don't understand why I don't encounter this issue at all with AOSP ROMs. Is there an obvious reason I'm missing?
Click to expand...
Click to collapse
This was the first question asked (see the fourth post). Here's the OP's theory...
rmk40 said:
I'd have to do more testing to confirm but I would guess more load is generated (events triggered) with Sense ROMs at the time of wake, causing the ondemand governor to scale up to nearly max more rapidly than CM.
Click to expand...
Click to collapse
I haven't seen this issue before either.
ianmcquinn said:
This was the first question asked (see the fourth post).
Click to expand...
Click to collapse
My bad, I missed that.
My number one audio usage is listening to podcasts with Google Listen. Unfortunately, I keep getting audio popping whenever I am doing something else while listening to a podcast. The popping seems to lessen considerably when I turn the screen off.
I'm currently using Adrenalyne's 12/30 kernel. I believe that Stupidfast test kernels fixed the problem but they messed up my phone in other ways... low battery, lockups, pauses, etc.
So what's the best kernel for this issue?
Sent from my SCH-I500 using XDA App
Skyeclad said:
My number one audio usage is listening to podcasts with Google Listen. Unfortunately, I keep getting audio popping whenever I am doing something else while listening to a podcast. The popping seems to lessen considerably when I turn the screen off.
I'm currently using Adrenalyne's 12/30 kernel. I believe that Stupidfast test kernels fixed the problem but they messed up my phone in other ways... low battery, lockups, pauses, etc.
So what's the best kernel for this issue?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I have found that turning the screen off helps too, I haven't found a kernel that works for me.
Sent from my SCH-I500 using XDA App
Use SetCPU and change the min clock speed from 100mhz to 200mhz. Everyone that I've seen that has the audio issue has had it stop when changing the min clock speed.
When you're having audio issues, are your softkey backlights on at the bottom? If so, that's a known hardware issue - if you're using backlight notifications, need to clear the notification, or, if you're on a newer update that leaves the backlight on while the screen is on, you'll need to turn off the screen. The key backlights generate a signifigant amount of electrical noise that is picked in the audio.
Actually the problem lies on how much stuff you have going on in the background. If you have many widgets, LWP, apps, etc your cpu will stutter with 100mhz. You should raise it to 200mhz and the problem will be gone. You won't feel the battery consumption difference by doing this, so try it.
deaffob said:
Actually the problem lies on how much stuff you have going on in the background. If you have many widgets, LWP, apps, etc your cpu will stutter with 100mhz. You should raise it to 200mhz and the problem will be gone. You won't feel the battery consumption difference by doing this, so try it.
Click to expand...
Click to collapse
I find that I have to raise it to 400-800 minimum at times.
Sent from my Galaxy S.
I can confirm that changing the minimum clock speed to 200mhz works. I've been doing that for a number of weeks now and it's never failed to work.
I had the popping too. The screen off helped but I couldn't take it. Jumped on the voodoo Train and haven't looked back. No pops plus its so smooth and fast I can't believe I ever went without it.
Thanks all, I'm going to try raising the min cpu and see if that helps.
I'm interested in voodoo sound and what that has to offer. Does anyone know if that is being porter to the Fascinate?
Sent from my SCH-I500 using XDA App
As per the title, I have started experiencing random system lockups since yesterday. I have had to perform two battery pulls and I'm starting to worry that my ext partition won't be so lucky next time...
I have no idea what is causing the lockups, though both have occurred while using Swype. Coincidence?
For now I'm going to set my system clock back to 600Mhz and use the default input method for a while and see if I still get lockups, at which point I will probably flash another ROM unless I can find a solution, which is where you guys (hopefully) come in. Is there anything else I can do to diagnose and/or solve the problem?
- Typed from my rooted HTC Legend -
It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version
Try interactive governor or flash latest kernel from the other thread.
TheGrammarFreak said:
It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version
Click to expand...
Click to collapse
That's peculiar, as I've had the processor on 768Mhz for a while now and I've had no problems at all before now.
As for Swype... it could be. ;P
BlaY0 said:
Try interactive governor or flash latest kernel from the other thread.
Click to expand...
Click to collapse
I'll try that, but what exactly does each governor do?
segphault said:
I'll try that, but what exactly does each governor do?
Click to expand...
Click to collapse
It manages when the processor speeds up. It doesn;t run at 768MHz all the time, that's just the highest you allow. Ondemand scales the frequency up when it's needed, and lowers it again afterward. It seems to be a little bugged in our kernels though, and causes crashes.
Interactive does a similar thing, but without polling the CPU. It also ramps the frequency up a little more quickly. I use it, it makes the phone more responsive (IMO), and also eliminates the need for profiles in setCPU (to a degree)
Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.
segphault said:
Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.
Click to expand...
Click to collapse
You'd have to mess around with kernel source code. I wouldn't know where to begin, sorry
Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App
MaBlo said:
Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
That did cross my mind but other users have reported success with it, so I figured I might as well give it some investigation.
I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows
TheGrammarFreak said:
I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows
Click to expand...
Click to collapse
Maybe not quite 19Mhz, then.
Perhaps we should do some testing to see how much processing power is needed to wake the phone quickly? Is there any way to test that?
Back on topic, I just had another lockup while using the interactive governor. This time I froze up while loading Fruit Ninja.
Now I'm at a total loss for what could be causing the lockups.
- Swyped from my rooted HTC Legend -
Seeing as nobody can seem to pin-point the problem, I'm moving to CM7 permanently as soon as it's released as stable.
This is a guide I have typed up on how to get the best display , sound, and battery out of your phone...
First you need to set up voodoo color with the voodoo control application on the market.
The way I did this was turn each setting all the way up and turned down gradually until the color went away. Now my display has never looked better.
Voodoo color settings differ from phone to phone due to screen use and the fact that different colors are different on certain phones. My phone is less blue than others, so I recommend that you follow that technique and do it yourself.
Voodoo profile v1
225
254
365
-15
-18
-11
My next thing I am going to talk about is sound.
In some kernels the drivers for voodoo are currently built into the kernel but not accessible via the UI.In cm7, voodoo sound doesn't exist at all. I purchased the payed version of voodoo control and the loading of the driver via that works without squealing. If you need voodoo sound, buy it. To get optimal sound, you need to tweak according to headphones. Plug in your headphones and play a song that you like with good quality audio. Now tweak the bass boost and equalizer (if your media player has one). Left side is bass(background stuff and shake), right is treble (clear voice). I usually keep the middle low and sides high.
If you have a phone that can go to 1.5ghz with ease, these are the settings I recommend.
Min: 100
Max: 1000
100 -150
200 -125
400-800 -75
Remove 900
1000 -100
Next, speed and battery. Get the voltage control app for this. Use ondemand for voltage testing it gets a wide range of frequencies. At the lower frequencies, undervolt starting at -150. Lock the phone, let it sit for a minute, if it froze, bump the voltage up to, -125. After the lowest step is set up good, change the other steps starting at the last voltage slide around the voltage control application and then idle a bit, if it freezes, move the voltage up... do the same for the next steps, starting with the voltage of the last.
Now you can test speed with governor and schedulers. I use ondemand and sio but most like lagfree and vr.
Overclocking is an option for speed but I advise against it due to.horrible, the risk of data corruption, and the decreased ability and life of your phone.
Boxer briefs.
Sent from my SPH-D700 using Tapatalk
philowneus said:
Boxer briefs.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I have a feeling he used swiftkey x. It changed overclocking to overclothing for me lol
sent from my touchwiz 4.5-ed epic
Damn spell cheek.
*check
Sent from my SPH-D700 using XDA App
Ive been wondering what do all the different governors do in tegrak/ voltage control? searched around, couldnt find anything
j00manji said:
Ive been wondering what do all the different governors do in tegrak/ voltage control? searched around, couldnt find anything
Click to expand...
Click to collapse
Governers tell the processor when to go to certain speeds. Comservitive keeps it lazy and not moving around much. Lagfree keeps it high when the screen is on. Performance keeps it always at the highest. Ondemand keeps it at a mix of speed and performance. Smartass and savagedzen make it low when the screen is off and scales according to demand.
Sent from my SPH-D700 using XDA App
Thanks for a great explaination and a good starting point for frequencies.
Sent from my Samurai TW.MTD Katana Clean GB Epic
Marcusant, I've been thinking about this a bunch lately. When people use profiles in something like SetCPU aren't they setting up redundant commands? In theory a well programmed governor would notice the state the phone was in and adjust according to the governor's master settings. By setting a profile would it be like having a governor running within other governors?
Profiles really **** **** up... the processor will go wherever it needs to go.
Sent from my SPH-D700 using XDA App
Thanks for this guide man. Just what I was looking for.
Sent from my SPH-D700 using XDA App
Well thanks for such a useful piece of guide and i can say information...i really wanted to know this.This is so helpful of you.Now i can get the best display , sound, and battery out of my phone trying this..I will let you know.
Thanks mate. This is working really well.
Really appreciate the guide Marc. I've never knew enough about voodoo and ocing stuff to do any good with them.
Sent from my SPH-D700 using XDA Premium App
Indeed, Marcusant, this was really helpful.
seems like you were right about the overclocking, tried these settings, plus 1200 mhz, and it was stable for a while, then the phone started rebooting on me. maybe i just need to keep messing with the voltage. anyway, what are the differences in schedulers?