yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] bast525:
What I'm saying is, it doesn't run fine with setcpu. It's kind of a situation where I have to choose the lesser of two problems. Without setcpu installed, the phone generally just kind of chugs, a lot of lag here and there because the conservative governor ramps CPU speed up somewhat slowly. Sure, full load situations like benchmarking run great, but just navigating around the home screen is sluggish.

With setcpu installed and governor set to interactive, the overall performance is vastly improved... no profiles, no overlooking. BUT, several times a day, when I wake the phone out of sleep, it will run HORRIBLY, VERY slow, like its stuck at 245 mhz. If I then open setcpu (mind you, its already running in the background), it IMMEDIATELY goes back to running super fast and smooth. Setcpu is CAUSING the problem.

If the king kernel ran the interactive governor by default, there would be no need for setcpu. I had no issues at all with the Hydra kernel but the king kernel definitely gets better battery life.
[Droid Incredible Android Development] sanamkan:
+1 Having the same exact problems on BFS2, but never with the other kernel #3. My only solution was to navigate to setcpu and tell it to auto detect frequencies again. Sadly it's only a temporary fix. Occasionally, it'll reset and go into a boot loop about five times, each taking ~3 minutes. Frustrated me enough to flash to the custom kernel on the Virtuous ROM.
[Droid Incredible Android Development] Kauffman_c:
If bfs2 is giving you problems, flash back to stock or try bfs1. I seemed to have a lot more stability with bfs1, thinking about going back. (keeping my virtuous rom though)
[Droid Incredible Android Development] douger1957:
I'm what I'd call a light to medium user...my awake time is about the 15 hours or so that I'm awake. I usually put the phone down for the night anywhere from 50% to 65%. I charge with the phone off...bump once while I'm in the shower, and don't usually drop below 100% in less than 2 hours.
[Droid Incredible Android Development] zeke1988:
im still on BFS#1. im waiting for #3 but only if it got positive feedback.
[Droid Incredible Android Development] elborak:
Then you have something seriously wrong besides your kernel. I'm running BFS#2, uptime of 29 hours. SetCPU total CPU used? 0 seconds.
[Droid Incredible Android Development] M4gicM@:
Possible solution

I had the exact same problems as what has been said here with regard to the lagging and shuddering with BFS#2, i even had a post about it earlier. Anyway I went back to #1 and had some issues at the beginning but now everything is great. I have since come to the conclusion that 245 MHZ is TOO SLOW for the phone. Processes must be timing out and the phone starts to accumulate errors. I have changed all of my lowest clock settings to 422MHZ. It is stable with no jittering.

Phones have an upper limit on their clock frequency but the same goes for their lower bound as well. You need to not only find the highest clock that you are stable at but the lowest as well. Don't pick 245 just because setcpu lets you.

Try this out first. I will creep lower everyday until i find my phone having issues. I would like to stress that I did not verify this with BFS#2 as I switched back to #1. But i had the same issues on 1 when my lowest clock was 245.

Maybe this helps.
[Droid Incredible Android Development] zeke1988:
why creep lower when you can creep it higher haha. thanks for the info, im trying it now.
[Droid Incredible Android Development] smw420:
Dude, you just solved my sluggish wake-up issue, and the other misc glitching I've been having. You are absolutely right. Even setting my slowest speed to 384 solved it. Genius.

I also played around with higher settings up to 576, and even though the phone seemed to open up around 442, 384 seems to be where the magic starts to happen. Right now I have my min set to 460 just to see what it does to battery life while its sleeping, and I will report back the findings (System Panel is the bomb).

I feel dumb for not trying this before.

So right now I have a sleep profile set to 460/460 interactive, and default speed set at 460/998 interactive. Previously it was 245/245i and 245/998i. Night and day difference in performance - NO GLITCHING AT ALL. Hopefully battery usage isn't as noticeable. ;)

-M
[Droid Incredible Android Development] Hand76:
Guys the phone is made to work at 245. Obviously it can not do everything it needs to at this speed but you shouldn't have to manually force it up from there.

Setting your screen time out mode at 245/460 is much better than 460/460. You are forcing your phone to do more work even if it is not needed.
[Droid Incredible Android Development] muaddib20:
You should only use setcpu to oc, the battery savings are negligible
[Droid Incredible Android Development] smw420:
Hmmm, I don't know if I can go there with you.

-M
[Droid Incredible Android Development] hsj1906:
Because??????
[Droid Incredible Android Development] seanzer:
I second this. I've been testing screen off profile vs not, it seems that setcpu uses more CPU time when profiles are enabled.. I just set my main profile to something modest and still got the same usage time out of my phone.

The phone does a really good job sleeping and I don't think wasting processes each time you turn your screen on and off helps your battery life..

I can't say the same for wake locks though.. but I listen to music and the battery life doesn't seem to drain any faster since the clockspeed never jumps up anyway..
[Droid Incredible Android Development] blaksplash:
disclaimer: the following may or may not be true since i don't know exactly how HAVS works in conjuction with static voltage, but-

these kernels under volt by .1v when the cpu is @ 245Mhz. One CPU my run fine at .950v @ 245 while another my have some issues with only .950v. This may or may not cause some stability issues

at 384, the cpu is under volted by .075v which isn't quite as much of a drop. at 422 it's down by .05v
[Droid Incredible Android Development] digitalicecream:
Ok I just want to say, using BFS#2 I saw something for the first time ever. I unplugged my phone at 8am and while I had little to no use of the phone yesterday. I was at 81% battery last night when I hit the sack and put it in the charger. 81%!!

Virtuous ROM 2.6, BFS#2. 1500mAh battery.

Thanks in advance for testing out the Mhz profiles, I'll be following closely to see where the sweet spot is for performance/battery life. But I'm just floored. Today I'll use the phone extensively and see what happens.
[Droid Incredible Android Development] jlss:
Exactly. I (and others) have pointed out repeatedly here, and in other threads on XDA, that not every DINC is identical. Just like not every car is identical. To efficiently and effectively mass produce any product - particularly one sensitive to minor variations - the plant must keep the product (our DINCs in this case) within certain tolerances. In fact if you'll read your manual you'll note those tolerance ranges in the detailed specs.

That's why only some can OC to 1.19 and be stable.

That's why some can get better battery performance than others, taking all other variables out of it.

If Hon Hai made 10 phones by hand to a rigid tolerance (tightened range) those 10 would perform nearly identically. When we're talking about hundreds of thousands of devices no one should be surprised to see differences between my performance and someone else's (I can't OC above 1.13 without tears and reboots, but I do get exceptional battery life.) Welcome to mass manufacturing. :D
[Droid Incredible Android Development] blaksplash:
right on.

most are knocking the kernel for stability issues while overclocked. this kernel undervolts for every speed 998 and below. So some may have problems even when underclocked. I personally love these kernels, but if my DINC ran like crap with it, i'd swap i out. (still waiting for and AOSP version btw :D )

HTC has spec'd for 1.3v at 998. guess what, this kernel pushes 1.275v at 998.

Some MAY experience issues at ANY speed with this kernel including stock speeds of 998. I haven't checked hydras source, but i'd guess he hasn't cut the voltage quite as much since some experience better stability.

My car requires 91+ octane. If I don't follow that guideline and run 89 or heaven forbid 87, may car runs like crap and it's down on HP... pinging and valave clatter is not something you want on a forced induction engine :eek:
[Droid Incredible Android Development] rigman:
The operating system is event driven. Meaning when almost anything happens on the phone an event is fired. An application can be setup to be notified when a specific event occurs, like sleep mode or wake mode.

Not sure this is how setcpu works, but I bet it is. It doesn't have to poll the screen. It just sets idle until the event is fired and then it's notified.

On a side note, you can get app autostarts from the market and it shows you a list of all the system events and the apps that are notified when an event fires. (the apps main use is to block apps from running durning certain events.)

________________________________

Unrevoked forever

SkyRaider Sense 3.1 RC3

KiNgxKernel (#3)

Radio 2.15.00.09.01
[Droid Incredible Android Development] elborak:
I have two profiles enabled in SetCPU. After 29 hours of uptime, SetCPU has used 0 CPU (rounding down to the nearest second, of course).
[Droid Incredible Android Development] smw420:
OK, that makes sense. So now I'm wondering how long it takes that event to fire. If SetCPU is waiting on the event, and the event is delayed even the slightest, then that might explain the possible lag of SetCPU switching profiles if that's what really happening here. There is definately something strange going on and would like to figure it out, even if no fix/solution comes of it. Its just killing me not knowing why. ;-)

-M

P.S. - And I don't think its has anything to do with the kernel itself.
[Droid Incredible Android Development] rigman:
It should only take nanoseconds for an event to fire and an app to be notified.

________________________________

Unrevoked forever

SkyRaider Sense 3.1 RC3

KiNgxKernel (#3)

Radio 2.15.00.09.01
[Droid Incredible Android Development] xtremebrdr:
king - was wondering if you have any plans as to including the ps3freedom/psgroove module into one of your kernals by any chance. I know the evo4g is done so the port shouldnt be that intensive.
[Droid Incredible Android Development] tcberg2010:
I may be wrong but I believe all SetCPU does is set the phones min/max and governer. The actual work is done by android system. As long as you do not open SetCPU the app will remain asleep.
[Droid Incredible Android Development] bast525:
Ok for the poster(s) who suggested upping the minimum speed from 245 is a genius. I upped it only one step, to 384, and all my issues with choppiness and lag (especially on wake-up) have gone away. Even if I leave the governor set to conservative. I've also gone back to using a screen off profile, conservative governor, 384 to 499 speed range, phone is running fantastically.

HUGE THANKS to everyone who posted about upping the low end speed!
[Droid Incredible Android Development] elborak:
That is true if you are not using profiles. But clearly SetCPU has some work to do if you have, for example, a screen-off profile.

That being said, the battery consumption by SetCPU will still be too low to measure.
[Droid Incredible Android Development] kingklick:
Been working on a new kernel for some time.....
[Droid Incredible Android Development] M4gicM@:
I am excite!
[Droid Incredible Android Development] gmichaelow:
Maybe it's an AOSP-supported kernel...hmm, which WOULD explain why he's been working on it so long! :D
[Droid Incredible Android Development] M4gicM@:
:)

sent from my Incredible
[Droid Incredible Android Development] Pacifik:
I've been using the bfs #1 for awhile now and some times the gov'nor will lock the cpu at full throttle rendering the phone quite useless. I believe it is something to do with setcpu because to get back to norm w/o rebooting I can get superuser regrant access even though its granted full access. For now I am blocking setcpu and will see how it works with out it, but does anyone have any other ideas?

Other than that I like its performance boost at reg. clocked speeds
[Droid Incredible Android Development] Ianxcom:
Commenting on recent topic of the phone being slow on wakeup when using setcpu, i think i remember reading in the eris section that it happens to them only when they use the setcpu widget. im wondering if thats the case here.
[Droid Incredible Android Development] :
awesome, i know that OpenVPN works with the BFS kernel, but I can't get VPN Connections to work. My VPN won't work with Open for some reason. I know the hydra kernel works with VPN Connections app but I like this one a lot better :D
[Droid Incredible Android Development] elborak:
VPN Connections works fine for me with BFS #1 & #2.
[Droid Incredible Android Development] bast525:
Dammit.... so after the issue seemingly having been resolved for almost two days (after I upped the minimum allowed CPU speed to 384 mhz), it started occurring again. Bring phone out of sleep, and it would run very badly, very slow to respond. This time I opened up system panel, thinking the CPU must be stuck at a low speed..... quite the contrary, the CPU was pegged at 1.15 ghz and CPU load was at 98%. So I opened Setcpu, and IMMEDIATELY performance returns to normal. An hour later, wake phone from sleep and it happens again.

This was with my primary setting being min 384/max 1.15 running the on demand governor, with a profile set for screen off to run min 384/max 499 on conservative. Ran perfectly fine like that for almost two days, no reboots, then started f'ing up every 2-3 times phone was brought out of sleep. On Hydra Kernel and no Setcpu I can go a week without rebooting and have NO issue..... but get about 20% less battery life and quadrant scores go from 1600 to 1400 :(
[Droid Incredible Android Development] Pacifik:
try blocking setcpu in superuser. I've been using the stock governor with out any problems still saves power. I never bothered to overclock though, 1 gigahertz is enough for me.
[Droid Incredible Android Development] thatdudebutch:
I have noticed it has stopped since I quit using the widget, I also upped my minimum clock up to 384 at the same time, but either way I don't experience the slowness on wake anymore and the governon doesnt throttle the clock at max either
[Droid Incredible Android Development] bast525:
I've never used the widget :(
[Droid Incredible Android Development] dnoyeb:
One could only hope... I love cm6 but the charge time is horrible! (And battery life in Gen)
[Droid Incredible Android Development] kingklick:
New BFS Kernel #3 is live!

Let me know what you think

:D
[Droid Incredible Android Development] thatdudebutch:
Awesome bro... Trying to download but there is no link at your site for #3, just some random letters..
[Droid Incredible Android Development] slickster2005:
What he said.
[Droid Incredible Android Development] kingklick:
Oops fixing it now... please stand by
[Droid Incredible Android Development] thatdudebutch:
You got it bro.. Can't wait
[Droid Incredible Android Development] kingklick:
ok link is fixed
[Droid Incredible Android Development] KGBxxx:
Sweet!

Sent from XDA App

Unrevoked Root and Sucked-off

2.0.5 Baseband

SkyRaider 3.0 Vanilla

#1 King Bad F*cking **** Kernel OC to 1.13
[Droid Incredible Android Development] slickster2005:
Excellent. Downloading now.
[Droid Incredible Android Development] thatdudebutch:
So far so good, will test battery tomorrow.. Be prepared for a long boot. Quadrant impressive as always.. King noticed you mentioned

245.. No lag at that minimal speed?
[Droid Incredible Android Development] KGBxxx:
I flashed the kernel, booted up, set overclock and my phone shot into space. Wtf. Where did my phone go? Where ever it is, at least the battery will last.

Sent from XDA App

Unrevoked Root and Sucked-off

2.0.5 Baseband

SkyRaider 3.0 Vanilla

#1 King Bad F*cking **** Kernel OC to 1.13
[Droid Incredible Android Development] SLOflatlander:
something weird happened (pretty unrelated to this kernel, but i noticed it when trying to clear dalvik cache for it). so i was searching around in clockwork to find where i could clear dalvik cache (as i have never done if before) and randomely somewhere along the line, this came up in the clockworkmod log thing:

E: Can't mount /dev/block/mmcblk1p2 (File exists)

then after clearing dalvik cache and flashing bfs kernel 3, im in a boot loop. could it be because i selected wipe in clockworkmod but used the power button to go back instead of selecting no (when i was looking around im cwm)? im nand restoring now, so hopefully that works alright and fixes my problem
[Droid Incredible Android Development] thatdudebutch:
Wtf?
[Droid Incredible Android Development] smw420:
King, does this kernel fix the bump charging issue? (please say yes, please say yes, please say yes;)) Although its probably not a kernel issue anyway.

Installed the kernel and so far so good. Big fat thanks for hooking us up!

-M
[Droid Incredible Android Development] smw420:
FWIW, I cleared Dalvik cache in CWM, then installed the zip in the same CWM session and rebooted. Phone hung on the red eye for about 5 to 10 minutes, but finally came all the way up and is perfectly fine so far. Probably building new cache.

-M
[Droid Incredible Android Development] kingklick:
Slow charging issues are fixed
[Droid Incredible Android Development] slickster2005:
Installed with zero problems. Long first boot, but I was patient. I fully expected it, anyway. Currently OC'd at 1152 and hit a quadrant score of 1622. Pretty awesome so far. I'll test the battery out tomorrow. Awesome job!
[Droid Incredible Android Development] thatdudebutch:
That would be great.. What do you recommend as far as profiles and clock speeds??
[Droid Incredible Android Development] smw420:
One curious question, why is the default governor Powersave?

-M
[Droid Incredible Android Development] silverxbv2:
I get this same error. Is the cache still getting cleared or does something have to be mounted first?
[Droid Incredible Android Development] thatdudebutch:
phone very snappy so far.. Had a reboot right after install but good since then
[Droid Incredible Android Development] bhazard451:
Sweeeeeeet. I'm loving Ruby but I def need to test this out. An AOSP version would blow my mind, but its also considerably a lot more work. If you're that close to getting your evo, I may just give ya another little donation to get ya closer (and lobby for some aosp love).
[Droid Incredible Android Development] Berzerker7:
I suggest changing the stock profile back to interactive governor. Defaulting on powersave makes boot-up veeery slow.
[Droid Incredible Android Development] adrynalyne:
Wow...nothing like a cap of 245mhz.

King...what was the thoughts behind this change?
[Droid Incredible Android Development] bokajay@gmail.com:
the boot animation frame rate was so slow... def change back.
[Droid Incredible Android Development] kingklick:
it can still be overclocked.

However I will be changing the governor tomorrow.

Feel free to change it in set cpu for now
[Droid Incredible Android Development] Berzerker7:
He's talking about powersave. When you're in powersave mode, the phone doesn't clock it higher than your minimum speed. So the phone is booting up at a 245MHz clock without overclocking to stock. And considering SetCPU doesn't work until the system boots up, it takes a very long time. But it's good to see you're going to change it.
[Droid Incredible Android Development] kingklick:
ahhh I see now

I misunderstood =)
[Droid Incredible Android Development] bast525:
Yes pleeeeeease set the default governor to interactive or even on demand.... this way we can have perfect performance without HAVING to resort to setcpu. Even conservative is just too laggy in some situations.
[Droid Incredible Android Development] kingklick:
You got it. Ill do this tomorrow
[Droid Incredible Android Development] elborak:
While you're pushing out another update, could you update your kernel to the more recent source drop from HTC? I see you're still on the older one.
[Droid Incredible Android Development] bullah:
Been at the red eye boot screen for about an hour. Rooted, 2.15 radio, Virtuous 2.6, BFS kernal #2, S-Off, and I wiped dalvik cache before I applied zip through clockwork. Any suggestions?

After about an hour and a half stuck at the eye, I pulled the battery. I know this is not the right thing to do, but I did it. Everything was fine after that. I rebooted and BFS #3 was installed. I've done this hundreds of times and never had the reboot after a flash take more than 6 or 7 minutes. I'm just glad no brick.
[Droid Incredible Android Development] kingklick:
there is no new source code.....
[Droid Incredible Android Development] Ianxcom:
Initial impressions are it works same as bfs#2. Benchmarks seem the same or lower, but i recently changed roms.
[Droid Incredible Android Development] 2019801:
Does BFS #3 can use in CM6.0.2?
[Droid Incredible Android Development] quepaso:
Do pineapples smell?
[Droid Incredible Android Development] adrynalyne:
Yes there is.

http://member.america.htc.com/downl...inaries/incrediblec-2.6.32.15-gb7b01d1.tar.gz

Newer than the original MR source they released.

It is also newer than the date of this thread.

As well, its newer than your github commit.

Lastly, there are more files that are present in the newer source, that are not present in the older source, and also are not on your github commit.

HTH.
[Droid Incredible Android Development] DeaconBoogie:
I'd like to know an answer to this as well...

Insofar as the phone goes, I don't see any operational problems. However, I don't recall ever NOT seeing that error when I attempt to clear the dalvik cache.

Can someone more enlightened explain what's going on with this error?
[Droid Incredible Android Development] oldman_58:
For those curious what NEON may be in #3

Follow the link,,,

http://www.arm.com/products/processors/technologies/neon.php

#3 looks like a good choice, I just went to #2 yesterday after a while I may take the plunge to #3.

Thanks for the good work King....
[Droid Incredible Android Development] rigman:
I thought slowing down the charging rate was an intentional change by HTC to improve battery performance? Faster charge means more heat. More heat means less efficient charge. Or so I've been told. (I think that's also why it's better to charge with the phone off. Less heat).

I know from my mechanic days years ago that a slow charge on a car battery is a lot better than a fast charge. Not sure if that applies to lithium batteries though.

________________________________

Unrevoked forever

SkyRaider Sense 3.1 RC3

KiNgxKernel (#3)

Radio 2.15.00.09.01
[Droid Incredible Android Development] oldman_58:
Back to BFS#1

Tried BFS#2 without Setcpu battery was always warm and drained phone rapidly Quadrant 1200+

Loaded BFS#3 without Setcpu it was slow and jumpy Quadrant dropped to 400 range.

I am back at BFS#1 this time without Setcpu..
[Droid Incredible Android Development] seanzer:
nevermind...
[Droid Incredible Android Development] ardax:
Ooh, if only there were an AOSP build of this. I've got Ruby running like butter, but having a BFS OC/UV Kernel w/ Interactive Scheduler would be sweet.

Once the new build is up that's not using powersave at boot, I might jump back to Virtuous and play.
[Droid Incredible Android Development] elborak:
As adrynalyne already pointed out in detail, there is.

However it's not a big task to incorporate the changes. Only 8 files have changed, plus a modest number (~20-30) of new files.
[Droid Incredible Android Development] bhazard451:
This kernel on Ruby or CM6 would be unreal. Even if we have to sacrifice something to get it working, like BFS, it would still be perfect. Hope it can be done. Patiently waiting, and donating. lol
[Droid Incredible Android Development] thatdudebutch:
Didn't you read the post you quoted? He said he was changing it tomorrow
[Droid Incredible Android Development] fortesquieu:
Gotta love the fast charging!