yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] KoopaT23:
Just wondering if I can clear the dalvik cache through Root Explorer. Does anyone know the directory for it?
[Droid Incredible Android Development] M4gicM@:
/data/dalvak-cache/ i believe. You can do that in recovery with Clockwork Mod.
[Droid Incredible Android Development] KoopaT23:
Thanks, I'll just do it through Clockwork just in case.
[Droid Incredible Android Development] fliptwister:
I'm very sluggish and getting 440 in Quadrant with BFS #3. I went back to BFS #2. All is good when I go back to #2. I thought I cleared dalvik cache properly. I went into root explorer, mounted r/w, then deleted all files in the data/dalvik-cache folder. Did I do something wrong? Anyone else run into this problem? Thanks!

edit: I'm running Virtuous v 2.6
[Droid Incredible Android Development] ardax:
See the previous posts about BFS #3's default governor being powersave. That means that the phone is locked at the minimum defined speed (in this case, 245 MHz). SetCPU will let you switch to the interactive governor, but booting will still be slow because SetCPU can't fix it until after the phone boots up.
[Droid Incredible Android Development] fliptwister:
Thanks, I missed that on changelog and recent posts. I do not understand why default governor is powersave though...

Something else I have noticed is that if I use root explorer to delete dalvik cache files, reboot, and then look in the cache directory, the files are there again. Should I not use root explorer to wipe cache? Is there a way to wipe dalvik cache in recovery mode?

Thanks!
[Droid Incredible Android Development] thatdudebutch:
yes, just hit advanced then wipe dalvik. only way ive ever done it
[Droid Incredible Android Development] fliptwister:
Thank you!
[Droid Incredible Android Development] thatdudebutch:
no prob! (10 chars)
[Droid Incredible Android Development] wowthatisrandom:
would love to see BFS #3 with the governor set to interactive :D
[Droid Incredible Android Development] DroidHam:
You may not be clearing anything, those files probably cant be whiped while the OS is booted, which is why you need to do it with recovery :)
[Droid Incredible Android Development] ardax:
That's where the other posts that he's going to change it come in. :)

Isn't that what's supposed to happen? I'd expect the OS to be regenerating cache files after rebooting.
[Droid Incredible Android Development] DroidHam:
Yea, I didn't see the "reboot" part. I bet it takes awhile to reboot too :)
[Droid Incredible Android Development] ardax:
So install SetCPU and change it? Booting will still be pretty painful though. :)
[Droid Incredible Android Development] jiggadroid:
Can anyone specify what the difference is between the Interactive Governor and the ondemand governor of setcpu? I took a look at the developer page and it had information on all the governors but didn't have anything listed for interactive.
[Droid Incredible Android Development] wowthatisrandom:
that and you still have to change it every single time u reboot. i went back to #2
[Droid Incredible Android Development] ardax:
See here. IME, it seemed to ramp up and back down more quickly than ondemand.

SetCPU can take care of that part for you though.
[Droid Incredible Android Development] jaba14:
yup, just rebooted with SetCPU "on boot" and it took the normal amount of time.
[Droid Incredible Android Development] Cheesejam:
Out of the three kernels, which one do you guys think has the best battery life?
[Droid Incredible Android Development] hawkye:
Mine has always been set "on boot". I updated to BFS#3 and it took a good 15mins to boot. I wanted to check how long it would take to reboot in case I OC too much and it reboots on me. It was up to 20mins and still trying to get service. It was way too painful so I am going back to #2. :(
[Droid Incredible Android Development] Berzerker7:
"on boot" just means it'll startup when the system actually gets into Android, you don't have to open the app. You'll still take forever to boot.
[Droid Incredible Android Development] spyd3r05:
I also agree.. boot takes way to long... For a min I thought I was on my old bb pearl.. Back to 2 til default is changed
[Droid Incredible Android Development] oldman_58:
Kernels --

BFS#1 has been the best for battery life so far, I suspect BFS#3 is going to kick backside once the slow boot issue is resolved.:cool:

But right now I am back at BFS#1 I can get 1200+ form Quadrant and around 35 with linpack. I have Setcu set to conservative ( reinstalled Setcpu after going back to BFS #1) and clock a 1GHz.

SkyRaider comes with BFS#1 -- Hope this helps
[Droid Incredible Android Development] Cheesejam:
Thank you! :)
[Droid Incredible Android Development] orcsbane13:
I'll take slow booting for now. I hardly ever reboot my phone. #3 charges fast. Almost as fast 2.1. I'm loving it atm. OC'd to 1.13 on virtuous 2.6 getting 1552 on quadrant. Very nice so far.

Sent from my Droid Incredible
[Droid Incredible Android Development] elborak:
Just to make things simple for you, here's the diff between the two 2.6.32.15 source trees that HTC posted. The first (incredilbec-2.6.32.15-7507bb0, their typo, not mine) corresponded to one of the earlier 2.2 leaks. The second (incrediblec-2.6.32.15-gb7b01d1) corresponds to the last leak and the final delivered version.

Your kernels are still based off the first leak and hence are missing several bug fixes from HTC.

I've cleaned up the diff slightly to eliminate some generated files that were included in the tarballs.

Hope this clears up the apparent confusion.
[Droid Incredible Android Development] hawkye:
Damn I am stuck in a boot loop after trying to go back to BFS#2 from #3. DOH! Anyone else having this issue?
[Droid Incredible Android Development] jlss:
No, but just pull your batt, boot into recovery, and flash BFS#2 (I assume you left it on your SD...) If not mount your /sdcard and push it.
[Droid Incredible Android Development] jlss:
No boot problem here so far. I'm running my main SetCPU profile using the interactive governor with min/max 245/1.113. Sleep profile still powersave 245/245 and same for a charging profile. Quadrant below. Anyone running into a better configuration? I see that SetCPU keeps wanting to revert to powersave.
[Droid Incredible Android Development] hawkye:
I tried reflashing all the damn kernels. All of them get stuck rebooting now. DOH! Time to go to a backup. I just wish I would have made one before I loaded #3. Lesson learned! :rolleyes:
[Droid Incredible Android Development] jlss:
DOH. Huge bummer. I've always been able to reflash :( Guess we'll see you in an hour.
[Droid Incredible Android Development] SLOflatlander:
does dalvik cache have to be cleared? what is the advatage to it?
[Droid Incredible Android Development] hawkye:
LOL! No doubt! I have a feeling my SD Card took a ****. I have a ton of crap on it though so it will take me hrs to get a new one up and running. Trying a restore first.
[Droid Incredible Android Development] oldman_58:
More than you asked for

I always clear Dalvik cache and if my phone still acts squirrelly i go back to recovery and wipe Partition cache and Dalvik cache again.

99% of the time issues go away...

All of the wipes are accomplished from Recovery:

Factory Wipe = remove all of your account and personal information

Partition Wipe = Cache partition wipes all stored program data

Dalvik Wipe (Advanced) = has to do with JIT I never was real clear on this, but always wiped when installing a new ROM.

you can start there

From

Backnblack over at http://www.droidforums.net/forum/dro...vik-cache.html

"Simple explanation:

When Android starts up, the DalvikVM looks thru all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimize the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimized bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's reoptimized and the cache is updated."
[Droid Incredible Android Development] kingklick:
Hey guys

Downloading fresh code per your requests. :)

I will be syncing it with my current code and cooking up a new one.

Been working on it all day so bear with me, when it is done, it will be worth it

:D

thank you all,

king
[Droid Incredible Android Development] jlss:
It's recommended in the OP/king's page.

Advantage is, I would assume, to force the dalvik vm to to rebuild after the kernel's flashed and you boot up.

EDIT: See post #1342 for a more complete explanation.
[Droid Incredible Android Development] jlss:
Woohoo! You rock. Another donation headed your way.
[Droid Incredible Android Development] oldman_58:
No Thank you, the EVO money should start rolling in and you deserve it.

Incredibly Rooted

ReVoked-Forever

SkyRaider RC3.1

KINgxKernel #1 - 1.0075GHz

My Hardware My way....Thanks Devs

http://www.eff.org
[Droid Incredible Android Development] kingklick:
no problem guys.

Had a few merge conflicts, but I cleaned them up

Ready to compile :D

for those who follow my code it is the test branch at the moment, because, well I do not know if it will compile :o
[Droid Incredible Android Development] gmichaelow:
Hey King, I know you're busy and whatnot, and I don't mean to be rude xD I do appreciate your work on these kernels! The battery savings are tremendous! =]

I was just wondering if an AOSP-supported kernel was in the works? =)

This + Ruby/ID = EPIC win! :D
[Droid Incredible Android Development] icedmayhem:
one thing i have noticed which puzzles me. using virtious 2.6. using a combo of froyo release radio and 9.01. i have read of peoples 3g connection dropping ramdomly. now this is the first king kernal that worked without random reboots or freezes is the bfs#3. with kings kernals i see the 3g dropout,overclocked to 1.113 or stock, now using virtuous custom kernal by adr, it never does as i was using it since i loaded the rom. Even when i ran stock htc kernal with release froyo, no dropouts. the speed difference is ridiculous with kings. i have seen the dropout using all of kings kernals. Even with hydra kernals, i never experienced the dropout. from what i have seen and experienced, could this 3g dropout just be kernal related ? anyone whose seen or experienced, or can replicate what ive noticed care to chime in..?
[Droid Incredible Android Development] kingklick:
New BFS kernel #4 based off fresh code is live!

:D
[Droid Incredible Android Development] gmichaelow:
gahhh, haha, I want this on AOSP so bad xD Haha, King, do you think it'll happen? :D That would be awesome =]
[Droid Incredible Android Development] seanzer:
Great work, but I don't see the interactive governor in #4.. I could be at fault but I swear its not there!

Otherwise, the kernel works great.

edit: my screen doesnt turn on after sleeping either...
[Droid Incredible Android Development] kingklick:
link is pulled while I look into the fricking interactive gov missing...
[Droid Incredible Android Development] WingHater:
I wiped dalvik then loaded up the new #4, boots fine but once the screen turns off and I hit the power burton to wake, all I get is a gray flickering screen with a yellow line at the top of the screen. I xan hear the phone unlock, I even heard a text come in but I cannot see anything, only fix is a battery pull. I tried twice more, same problem. I put adrynalynes new kernel back on and phone runs totally normal again. Did this just happen to me or did anyone else experience this? I'm using Frankenrom btw.
[Droid Incredible Android Development] GrimVII:
bug?

King, also, not sure if its just me but...if i try to boot phone when charger is plugged in or if phone goes into sleep, upon wake-up the screen stays black with the top of the screen showing a white line with all the command keys also lite-up (just went from BFS # 3 to # 4 and wiped dalvik)
[Droid Incredible Android Development] 338lapuaAI:
same issue here. loading #2 back on. using skyraider 3.0 vanilla RC2
[Droid Incredible Android Development] rock28:
same thing happened to me. gonna do a battery pull now and install a different kernel.
[Droid Incredible Android Development] kingklick:
ok I found the error.

It was another bad merge.

It's fixed and I am compiling as we speak
[Droid Incredible Android Development] Div033:
Yep, same here. Black screen, yellow line, and some red green and blue dots randomly twinkling in.

Wiped dalvik before flashing... now I'm back to #2.
[Droid Incredible Android Development] sirmims:
i have the custom kernel for virtuous 2.6. will the new BFS#4 give me better battery life than the virtuous kernel?
[Droid Incredible Android Development] bahill:
Woah, that black screen and green line was fun!! Yikes. Back to #2 for now...
[Droid Incredible Android Development] kingklick:
don't know what to tell you guys.

that's very strange.
[Droid Incredible Android Development] goldalex98:
I had the green line issue, also noticed that not all governors were showing up in setcpu. I'll test again once you post your newly recompiled script king. But your first compiling definitely was boinked...
[Droid Incredible Android Development] Nickster08:
I had the same problem with the black screen
[Droid Incredible Android Development] KGBxxx:
Same here

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] kingklick:
Ok link is back up and kernel is all fixed :)

same version number
[Droid Incredible Android Development] Stam2000:
Woohoo
[Droid Incredible Android Development] jdposhkus:
link to the DL?
[Droid Incredible Android Development] danman7:
Check the OP
[Droid Incredible Android Development] 338lapuaAI:
working fine now

BFS#4

Skyraider Vanilla RC2
[Droid Incredible Android Development] jdposhkus:
um..Nevermind.
[Droid Incredible Android Development] KGBxxx:
Wow. Great stuff.

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] gbishop18:
its working fine for me at 115, great job

incredible with Virtuous 2.6 and kings 4 bfs
[Droid Incredible Android Development] kingklick:
good good!

I was hoping higher clock speeds would be stable!

:D
[Droid Incredible Android Development] orcsbane13:
Works good for me but can only go up to 1.13. Anything higher crashes my browser.

Sent from my Droid Incredible
[Droid Incredible Android Development] elborak:
BFS kernel #2 had AVS but #4 doesn't seem to. Was this deliberate? I don't see it in the changelog.
[Droid Incredible Android Development] jaboswell:
Working real nice (#4)...very stable at 1.15...1.19 is stable only if I don't mess with the minimum in SetCPU...still playing with it...only had to do 1 battery pull..SetCPU was set to 998min/1.19max w Performance Governor...
[Droid Incredible Android Development] blaksplash:
could it be!?! AOSP soon?!? :D

http://github.com/kingklick/kk-incredible-kernel/commits/2.6.32.15-aosp-havs-bfs
[Droid Incredible Android Development] danman7:
Nice, just ran a 1610 Quadrant score at 1.190/Performance. Now to see how it works day to day. I generally don't overclock, but am more interested in the power savings.
[Droid Incredible Android Development] rmk40:
First, thanks for providing this kernel to us. It is nice to have a few options and it seems to be working well so far.

Curious, why did you change to CFQ in the latest release? I ask because CFQ is typically targeted for server-type workloads. Also, why change the governer? Were these changes the outcome of test results somewhere?
[Droid Incredible Android Development] oldman_58:
Just loaded #2

WOW

Quadrant 1411

LinPack still around 35 (not much change)

Thanks for the hard work.... Well done.
[Droid Incredible Android Development] :
How can I set this to the max speed on overclok widget?

sent from jdfroyo v2.0 EVO-lution
[Droid Incredible Android Development] oldman_58:
Blue Tooth

Just connected my hearing aids via Blue Tooth Streamer... Seems t be working fine.:D

Just did a voice dial seems to be in working order.

===================================

=Hearing Aid info: =

=Bernafon Verite with Sound Gate Streaming device... =

=if your interested http://www.berfnafon.com =

===================================

Thanks again
[Droid Incredible Android Development] s197:
This one is giving me issues, had both the stock and Dolphin HD browsers just close on me.
[Droid Incredible Android Development] Asterdroid:
That used to happen to me when I ran kernels that weren't over volted at max speed.

-Sent from your mom's phone.
[Droid Incredible Android Development] bigman420:
when i set it to max, 1.2ghz, and load doulphin hd, it reboots. kernel 1 seemed stable at 1.13.

hope this helps

skyraider 2.5.2, radio 2.15
[Droid Incredible Android Development] s197:
Yep was just going to post this, scaled back to 1.15 usng Set CPU and seems to be more stable now. Will keep testing. (Governor set to conservative)

8/1 Froyo ROM
[Droid Incredible Android Development] belkira:
When setting to max using setcpu and then opening a mapping program (maverick) got reported and stuck on boot. Had to pull battery to get it to boot up. Put it back to stock speed and all is well.
[Droid Incredible Android Development] SLOflatlander:
does this work with wireless tether in infrastructure ap mode? or only ad-hoc
[Droid Incredible Android Development] rmk40:
Also, would it be possible to get a version with absolutely no overclocking? I'm probably not alone in the category of people who are fine with the stock performance and just want optimized battery life.
[Droid Incredible Android Development] zeke1988:
this is nice, far better than the other OC kernel which gave me random reboot.
[Droid Incredible Android Development] mozetti:
Same thing with the xda app FCing happened to me today, too. Running Hydra ssuv 0.5, so it's not unique to this kernel.
[Droid Incredible Android Development] SLOflatlander:
i just installed the kernel #2, and the first thing i was planning on doing was check quadrant and linpack to compare to what i was running before. i slide the max bar in setcpu to full, but when i tried to switch to performance i got a reboot. now i cant get back into set cpu to switch back to ondemand :/

so after four or five reboots it kinda "restabilized" itself per se, and now it seems to be running good. also, wireless tether does work fine in ap mode if anyone was wondering :P
[Droid Incredible Android Development] spaceman4:
Having a lot of reboots using set CPU with this new kernal.
[Droid Incredible Android Development] fbrn:
This is working so much better for me. Looking at my speeds it is actually scaling. Every other one I have tried goes straight from min to max with nothing in between. Thank you so much.
[Droid Incredible Android Development] goldalex98:
It seems like everyone having a problem is trying to overclock to the max. I am running at stock speeds without an issue. It is very similar to overclocking a PC, many times you can't clock the CPU over a certain speed without overvolting the CPU. In this case, its very likely that the max overclock speed is not attainable on the Incredible without overvolting the cpu. I would suggest everyone avoiding the max overclock speed since it clearly is causing instability issues with the phone.
[Droid Incredible Android Development] seanzer:
Has anyone noticed that the extra heat generated when charging makes overclocking unstable? I can normally hit 1.15 fine, but when I'm charging it always restart. Im specifically taking about the wall charger..

Also, I like the idea of using conservative instead of ondemand. When gmail updates and I'm not using the phone, I really don't care how fast it the CPU runs, but ill take the lower voltage...

Running oc'd to 1.13 for stability.. I only got reboots at 1.19..

Also, to whoever that asked for a ss version.. this kernel comes at stock speed, you have to use set CPU or osmon to boost the max speed. So try it out!
[Droid Incredible Android Development] s197:
I could be wrong but I believe out of the box it's not overclocked, it's at the stock 1ghz.
[Droid Incredible Android Development] bigman420:
out of the box = no overclock

if setting to max causes reboots, set to 1.13, works for me.

also, kudos on fixing the scaling thing, nice to see something other than all or nothing.
[Droid Incredible Android Development] khanam:
I'm on virtuous 2.6 and would like to know which one would work best for me between Bfs 3 & 4. Mainly want better battery life and some performance gains but don't care too much about outrageous linpack scores etc. Stability would be of paramount importance though. Any users on virtuous 2.6 care to comment? Also what exactly is the difference between 3 & 4. I have read the OP but would appreciate a layman's interpretation please.
[Droid Incredible Android Development] Pacifik:
Bfs 2 had a much better nenamark Than 4. 16/13
[Droid Incredible Android Development] oldman_58:
Hope you have a great night out....

Just loaded #4 and the only thing that comes to mind

Wow, out of the box minimal tweaking with Setcpu and 1365 Quadrant at 1GHz.

Very nice work....

I am thinking there is some beer money in you near future..

Thanks
[Droid Incredible Android Development] 338lapuaAI:
You #4 it fixes the issues in #3 like the really long boot time.
[Droid Incredible Android Development] jwood:
Ditto! Interactive would rock..
[Droid Incredible Android Development] elborak:
:confused:
[Droid Incredible Android Development] oldman_58:
#4 has interactive set on boot

it is also the latest kernel code with fixes from HTC...

Please read KingKernels post....:rolleyes:

Load #4 and try it out, don't forget a nandroid backup then wipe the cache partition as well as the Dalvik cache...

Works like a charm....
[Droid Incredible Android Development] jasonb1985:
Battery just went from 52% to 69% in 40 minutes. So charging speed seems to be improved. so doing the math shows a 4 hour charge time from 0 to 100, if its linear from 0-100 of course.

Running bfs#4 at 1075/245 on conservative with a screen off profile of 384/245 on the interactive governer. I also wiped the dalvik cache before going from #3 to #4.
[Droid Incredible Android Development] rock28:
do you guys generally wipe the dalvik and battery stats before or after installing the new kernel?
[Droid Incredible Android Development] thatdudebutch:
Dalvik before stats after
[Droid Incredible Android Development] Stam2000:
I normally do the battery stats after running the battery down till the phone shuts down. Then charging to green. Then bump charging. Then wiping the stats while the phone is still plugged in
[Droid Incredible Android Development] crashdogy:
Well seems 1.9 is just not going to happen for me. It instantly reboots when set to 1.9 :(, but 1.5 is looking better :). And battery changing is much faster, was only able to get up to 1075 stable on all previous kernels.
[Droid Incredible Android Development] intersysx:
Tried #4 with Virtuous ROM - cleared Dalvik cache

After boot - screen goes black with a thin yellow bar across the top.

Reboot - same thing. Went back to BFS #2 and all is well.
[Droid Incredible Android Development] WingHater:
The update seemed to fix the problem for me. Are you sure you downloaded the updated bfs#4 intersysx?
[Droid Incredible Android Development] intersysx:
I downloaded it about 7pm pacific time - so I think it is the updated one - but I will try again,

Update - I had the older one....downloaded just before update.

Thank you @WingHater
[Droid Incredible Android Development] Berzerker7:
Running great at 1.19GHz
[Droid Incredible Android Development] adamant13247:
So what would be the better choice of kernels in the kings choice? #3/4
[Droid Incredible Android Development] kingklick:
#4 is getting great feedback
[Droid Incredible Android Development] elborak:
In case my post was lost in the forest, is AVS indeed gone from BFS #4?
[Droid Incredible Android Development] seanzer:
1309 using interactive governor..
[Droid Incredible Android Development] RYANIMOSITY:
Will #4 work well with CyanogenMod 6.0.2 or any of the Nightlys