MIUI v0.5 (1.1.22.2)

[s197]

No need for SetCPU with Invisiblek's kernels. It uses the smartass gov and has the screen off profile baked in.

[Ads]

[jkhonea]

No need for SetCPU with Invisiblek's kernels. It uses the smartass gov and has the screen off profile baked in.

So no benefit at all using it?

[jkhonea]

Oh and I must say, I continue to be impressed by this iteration of the ROM. Snappy, the different screen animations to switch between, the customizations. Very nice. I think I'll enjoy this one again for awhile as long as nothing goes weird, knock on wood.

Is it bad to say I find it rather funny when the phone is booting up, after the HTC logo screen, it goes to the silver Apple logo. I'm easily amused, I guess.

[mjs31]

I have setcpu running, but not sure if it is a must. You are correct about this rom being apple related as well. I did forget my iPod also LMAO...oh well, what can ya say.

I am addicted to Omnifocus so all of these devices can utilize it no matter where I am.

[jkhonea]

Omnifocus does look pretty interesting. I'll have to take a closer look at that.

[mjs31]

Omnifocus does look pretty interesting. I'll have to take a closer look at that.

I recently got into GTD and this really works well with it. It has helped tremendously with the number of new projects I have running simultaneously while still keeping my other items in check. Not cheap by any means, but worth it IMHO.

[Medion]

Are you using the kernel straight up or using SetCPU profiles?

To interject, I still use SetCPU profiles even with kernels like that. I know the kernel has a screen-off profile, but your SetCPU profiles will override that if you don't set a screen-off profile of your own. My profiles are;

(priority) condition (everything is ondemand)
(100) screen-off 245/245
(95) temp > 50 (C), 245/245
(90) charging/full 998/245
(85) battery < 15% 384/245
(80) battery < 25% 576/245
(75) battery < 40% 768/245

Main profile is set same as charging, 998/245. On CM 6 I was setting the minimum to 128. CM7 is back up to 245 as the minimum, like most of the Sense ROMs/kernels I've played with.

Basically, while many kernels now have a screen-off profile, if you want OTHER profiles, you still need SetCPU. If you use Set CPU, these profile will override the kernel's screen-off profile, so you still have to set one with SetCPU. But, if you were only using SetCPU for screen-off, then it's useless with many kernels today.

[s197]

So no benefit at all using it?

The only benefit would be if you're going to overclock. SetCPU supposedly interferes with HAVS so if anything, it's a detriment to the kernel.

I've been running #28 on Ruby w/out SetCPU for a few weeks now with no issues so you should be alright.

Edit: Was writing this as Medion posted. If you want to do multiple profiles like he does then you would need SetCPU but as I said it will negate HAVS.

[jkhonea]

The only benefit would be if you're going to overclock. SetCPU supposedly interferes with HAVS so if anything, it's a detriment to the kernel.

I've been running #28 on Ruby w/out SetCPU for a few weeks now with no issues so you should be alright.

Edit: Was writing this as Medion posted. If you want to do multiple profiles like he does then you would need SetCPU but as I said it will negate HAVS.

OK, that was what I was wondering. I actually had a profile set up like Medion was talking about and have the screen off bottomed out. Around that, I tiered out my settings very similar to his.

Anyway, going to be interesting to get a good idea of the battery life on this tomorrow. I'll run several days with my SetCPU profile then several days without and see which average is coming up better.

[Marcismo55]

Anyone else having issues with contact pictures not syncing? Some of my contacts in my "Favorites" pictures are not showing up. I've tried to removing the contacts and adding them back to favorites and then adding the widget back with no avail.