Originally Posted by Sybregunne

Well said. But as a point of argument you would want to set a lower range for sleep state. hence the need for redundancy

In the end its still heavily dependent on the user.

Thanks. I was hoping you might read this and chip in. Are you talking about using the daemon to set a lower value for max sleep speed than is built in to the Smart/Smoothass governor? If so, that makes perfect sense and must be what ShadowPony was referring to above (which I missed at first, sorry). Thanks for clarifying, I've amended my post.

What's the default frequency range for Smartass/Smoothass in sleep state?

Originally Posted by preacher65

Long post ahead but I hope this might help some people. Please correct anything you think I've got wrong!

The way I think of it is like this. If you're using the Daemon, the CPU only has a couple of sleep frequencies to switch between, or three at max. So whether you're on Conservative or Smoothass/Smartass as your sleep governor, the only difference is the algorithms that decide how the kernel switches between those two frequencies. There's not going to be much noticeable difference because the CPU is still limited to the same min and max, and the gap between them is small - from 230400-384000 on most phones, or maybe 122000-384000.

Smartass and Smoothass have two real benefits - a built-in sleep/wake governor, and less aggressive CPU scaling further up the frequency table during normal phone use. The second one only really comes into effect if you have Smooth/Smartass as your wake governor. Smartass really shone when we didn't have daemons to control frequencies, and its built-in sleep/wake detection made a big difference to battery life by keeping the CPU throttled low when the screen was off. Now it seems a bit redundant if you're using a daemon to control the CPU when the screen is off.

But if you use the Daemon and Smooth/Smartass as your sleep governor, when your phone wakes two things happen. The Smooth/Smartass governor notices that the phone is awake, increases the maximum frequency the kernel can go up to, and begins to ramp up. But at the same time it does that, the daemon switches to a completely different governor (e.g. Ondemand), so that change is wasted. It's possible you might lose CPU cycles as Smooth/Smartass detects the wake state just as the daemon changes governor, although I imagine that would be slight.

But other than that it's really a bit like changing gear in a car at the exact time you switch into a different car. The benefit of changing gear in the first car is lost, and possibly you wasted time and effort doing it before you switched.

And if you have Smartass or Smoothass as both wake and sleep governors, then there's no point using the daemon. All the daemon will do is detect the phone has woken up and change the governor from Smartass to... Smartass. Like changing gear in your car from 3rd gear to 3rd gear - it does no harm but it's a waste of effort. There's nothing wrong with using Smartass for both wake and sleep, but then you might as well disable the daemon in Daemon Controller and let the kernel do everything.
Edit: As per Syb's post below, you could use Smartass/Smoothass as the governor and still use the daemon - to override Smartass and set a lower sleep range.

PS. I'm aware there are limitations to the car analogy, but it was the simplest I could think of.

Finaly a thorough and clear explanation...cause everybody till now only said that this governor has sleep estate built in, or is not good.to.use this one, but none really explained how the process works...since are a lot of non Dumb people here who realy want to understand this process , not just to "swallow it" (you pervert sick guys , you only think at that ..Think )

Send from my DHD using Monocytes, Macrophages and Natural Killer cells

Originally Posted by preacher65

Long post ahead but I hope this might help some people. Please correct anything you think I've got wrong!

The way I think of it is like this. If you're using the Daemon, the CPU only has a couple of sleep frequencies to switch between, or three at max. So whether you're on Conservative or Smoothass/Smartass as your sleep governor, the only difference is the algorithms that decide how the kernel switches between those two frequencies. There's not going to be much noticeable difference because the CPU is still limited to the same min and max, and the gap between them is small - from 230400-384000 on most phones, or maybe 122000-384000.

Smartass and Smoothass have two real benefits - a built-in sleep/wake governor, and less aggressive CPU scaling further up the frequency table during normal phone use. The second one only really comes into effect if you have Smooth/Smartass as your wake governor. Smartass really shone when we didn't have daemons to control frequencies, and its built-in sleep/wake detection made a big difference to battery life by keeping the CPU throttled low when the screen was off. Now it seems a bit redundant if you're using a daemon to control the CPU when the screen is off.

But if you use the Daemon and Smooth/Smartass as your sleep governor, when your phone wakes two things happen. The Smooth/Smartass governor notices that the phone is awake, increases the maximum frequency the kernel can go up to, and begins to ramp up. But at the same time it does that, the daemon switches to a completely different governor (e.g. Ondemand) and also sets a higher max freq, so that change is wasted. It's possible you might lose CPU cycles as Smooth/Smartass detects the wake state just as the daemon changes governor, although I imagine that would be slight.

But other than that it's really a bit like changing gear in a car at the exact time you switch into a different car. The benefit of changing gear in the first car is lost, and possibly you wasted time and effort doing it before you switched.

And if you have Smartass or Smoothass as both wake and sleep governors, then there's no point using the daemon. All the daemon will do is detect the phone has woken up and change the governor from Smartass to... Smartass. Like changing gear in your car from 3rd gear to 3rd gear - it does no harm but it's a waste of effort. There's nothing wrong with using Smartass for both wake and sleep, but then you might as well disable the daemon in Daemon Controller and let the kernel do everything.
Edit: As per Syb's post below, you could use Smartass/Smoothass as the governor and still get benefit from the daemon - to override Smartass and set a lower sleep range.

PS. I'm aware there are limitations to the car analogy, but it was the simplest I could think of.

Very good explanation worth linking here http://forum.xda-developers.com/show...ostcount=34279

Well guys that's me moved on to the HTC sensation ,,woohoo, once I get a chance I will ARHD it just like my ex desire hd. Keep up the good work on the desire hd and I will see you on the ARHD SENSATION thread for loads of goodies

Sent from my HTC Sensation Z710e using xda premium

Hey guys, I'd like to ask a question:

Is the market problem solved that some user were complaining about?
They said that some apps weren't shown in the market.

Thanks

Sent from my Desire HD using Tapatalk

IS there any way that kernel can include audio boosts, it would be really great ?

Originally Posted by zla.mas

IS there any way that kernel can include audio boosts, ...

i tryed volume+ and got a little bit more power on the speaker.

Originally Posted by crash_194

I see that really annoying audio pop has crept its way in to the kernel. Could somebody post v7 and 8 of the kernel so I can see when it crept in. Apologies as I find the kernel source on github very confusing lol.

Thankyou in advance!

Sent from my HTC Desire HD using xda premium

it's fine in Kernel v8 ... I have not had a chance to let them know about the Kernel 10 and beyond ... I have to create a new account for the forum which he belongs with ...

I just updated my phone to ARHD 6.1.5 and tried to reset battery stats when currentwidget showed me 0mA, but somehow i was not able to find that anymore in recovery mode...

was it moved or something?

Originally Posted by kedirakevo

Guys, Im having GPS problems, please kindly help me.

I have tried all methods but to no avail... I havent been using my GPS much so I didnt notice when did it died on me. I jumped from Lee's to ARHD from 6.1.1 then to 6.1.4 then to 6.1.5.... and i discovered it like just today.

I've tried flashing radios, RILs, different ROMS, wiping EFS, gps.conf patch, uninstalled GPS Status, changed NTP servers.... NOTHING WORKS!!!

If you guys are telling me about opening the GPS antenna, i just did it like 2 weeks ago...

Everything was perfect back then..

All right... I went ahead and reopen and readjust my antenna on my DHD cover... it works again... but my signal strength is quite low but @ least now theres GPS lock...

I think my 2 gold connectors are FKed so is there any other solution?