yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] EnixLHQ:
Test 2, 128/998 Ingenious, wiped cache and dalvik cache: Also made it through an hour and a half of navigation, texting and Mixzing while charging. No internet radio, though. The stuttering was less and the smoothness of homescreen transitions and scrolling was improved, but (as odd as this sounds) the response time was slower. As if upscaling isn't as aggressive.

Flashing back to Test 1 to give it a proper test. Leaving it overnight idle is the first moment of truth as it's in the morning that I notice most of my issues. After that I've got a full day planned for it. Assuming no freezes or reboots I'll stick with it until the evening.
[Droid Incredible Android Development] chad0989:
No, its definitely an issue. I fixed some things which definitely made it better, it just FCs now, but I think it might be partially a buggy app too. Are there other versions of the camera?

Also does anyone actually on MIUI have issues with it?
[Droid Incredible Android Development] jesssiii:
I'm on CM7 #99 w/Beta 2 kernel (ingenious not so good to me), and use that exact miui camera. Even taking multiple quick pics in a row, no fc.

DInc w/ ZEAM Launcher

Chad's Incredikernel

CM7 (latest nightly)
[Droid Incredible Android Development] SynisterWolf:
I have tried 3 different copies of it in the cm7 nightly thread. All 3 do the samething.

Sent from my sexy assistant. (HTC Incredible.)
[Droid Incredible Android Development] rlacrossjr:
MiuiCamera with playing pandora

Chad,

I have been going back and forth between your beta's and Tiamat. I have Tiamat 4.0.5(2.6.38.8) and ran pandora and used the MIUI camera with no issues. Maybe this will help:)

On CM7 Nightly100
[Droid Incredible Android Development] SynisterWolf:
This one so far hasn't done it yet.

http://xdaforums.com/showthread.php?t=984279

I'm going to keep trying though. I'm on test one fresh install.

And it just did it. so never mind.

Sent from my sexy assistant. (HTC Incredible.)
[Droid Incredible Android Development] TheWhiteBandito:
I'm running Test 1 and the latest MIUI, and the camera works.

Note to people with CM7 and MIUI Cam: there is a known bug for MIUI Incredible right now where if you have "Auto-Focus" turned on, it can freeze or crash. Try turning it off and seeing if that fixes anything? I know that it fixes it on MIUI.
[Droid Incredible Android Development] SynisterWolf:
O.o i didnt get the memo.... maybe that is whats causing it..... i will try and see. thank you.

do you have a link to the thread for miui?
[Droid Incredible Android Development] chad0989:
When does it freeze? Been playing for awhile now with no issues...
[Droid Incredible Android Development] chad0989:
Yep, that's it. Just took 10 pictures with Pandora running and auto focus off and it works fine.
[Droid Incredible Android Development] TheWhiteBandito:
Ah damn, I wish I saw your troubles with the MIUI cam earlier, this would have been solved earlier. Glad that was it though! :)
[Droid Incredible Android Development] SynisterWolf:
thanks again! i have lost most of my hair by me pulling it out because of this. everyone else said it worked. ((>.<))

@chad.

Thank you for working on it.
[Droid Incredible Android Development] SynisterWolf:
chad.

after 6 hours of playing Pandora music im starting to here it cut in and out with no signal change. this is on test 1

time for test 2

i feel like both test builds are favoring the 128-384 speed to much. even if im doing something that is calling for more cpu like running pandora and surfing the web. the UI of the phone seems to be sluggish. just my $.02

Kernel

Linux version 2.6.38.6-incredikernel-gb+ (chad@chadserver) (gcc version 4.4.0 (GCC) ) #98 PREEMPT Wed Jun 8 19:27:43 EDT 2011

Battery

Battery Temp: 39.3° C (102.7° F)

Battery Level: 63%

CPU

Frequency: 384000 kHz

Load Average: 5.60 5.19 3.60 1/492 2514

Processor	: ARMv7 Processor rev 2 (v7l)

BogoMIPS	: 254.77

Features	: swp half thumb fastmult vfp edsp thumbee neon

CPU implementer	: 0x51

CPU architecture: 7

CPU variant	: 0x0

CPU part	: 0x00f

CPU revision	: 2

Hardware	: incrediblec

Revision	: 0002

Serial	: 0000000000000000

Time in State

128000 | 739 | 0.77%

245000 | 41035 | 42.54%

384000 | 44808 | 46.45%

422400 | 0 | 0%

460800 | 0 | 0%

499200 | 465 | 0.48%

537600 | 2 | 0%

576000 | 0 | 0%

614400 | 0 | 0%

652800 | 0 | 0%

691200 | 0 | 0%

729600 | 873 | 0.91%

768000 | 0 | 0%

806400 | 6317 | 6.55%

844800 | 0 | 0%

883200 | 0 | 0%

921600 | 0 | 0%

960000 | 0 | 0%

998400 | 2217 | 2.3%

1036800 | 0 | 0%

1075200 | 0 | 0%

1113600 | 0 | 0%

Memory

MemTotal: 422652 kB

MemFree: 29812 kB

Buffers: 30884 kB

Cached: 140232 kB

SwapCached: 0 kB

Active: 271460 kB

Inactive: 88852 kB

Active(anon): 189408 kB

Inactive(anon): 448 kB

Active(file): 82052 kB

Inactive(file): 88404 kB

Unevictable: 144 kB

Mlocked: 0 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 189360 kB

Mapped: 47084 kB

Shmem: 516 kB

Slab: 13684 kB

SReclaimable: 8968 kB

SUnreclaim: 4716 kB

KernelStack: 3936 kB

PageTables: 10440 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 211324 kB

Committed_AS: 1805132 kB

VmallocTotal: 458752 kB

VmallocUsed: 112756 kB

VmallocChunk: 309252 kB

Running Pandora the whole time and surfing the net and it just sticks at 384
[Droid Incredible Android Development] bradm23:
I think I figured out what was happening with web surfing lately. I downgraded my dolphin HD browser to pre 5.0 release and now my web browsing doesn't stop mid loading. This update happened right around the time .38/ingenious came out.
[Droid Incredible Android Development] chad0989:
You're seeing that from the screen being off. Plus your phone couldn't have been used much with the screen on or 998 and 806 would be much higher. It will never go above 384 with the screen off.

Since for most people the screen is off more than its on those frequencies are always going to be used more. The highest frequency is used the most when you're doing anything with the screen on.

That's not a big deal though. I really have zero concern for the.performance aspect right now. All that stuff is easily changed and the user can change it as they see fit. Plus I might work on the way it scales some more later.

My primary concern right now is stability. Which is the real point of all these tests. The only reason I've tweaked some of the performance stuff is to satisfy people enough to use it so I can get feedback on stability. Plus feel free to tweak the tuneables and find what's good for you. With the two tests I just want all variables to be the same because I want to see one thing in particular.

We'll look for good default values later on.
[Droid Incredible Android Development] mikesincredible:
Test 2 seems to be doing good. 998/128 ingenious, Used the web, streamed Pandora for about 30mins...I did have the freeze issue with the miui cam..mine froze using the anti shake...phone idle overnight dropped only 2%...wifi on, the sleep policy is never..that's about it
[Droid Incredible Android Development] SynisterWolf:
oh ok. thank you for the explanation. i will keep testing but so far no reboots only pandora or music app will sputter from time to time.
[Droid Incredible Android Development] davwman:
havent tried test 1 but test 2 running great at 614mhz max and 128 min with zero stuttering from pandora.

Cm7 Nightly

Incredikernel

Radio v. 04.08
[Droid Incredible Android Development] mikesincredible:
chuck norris once punched a horse, now we have giraffes.
[Droid Incredible Android Development] Jinnai:
Sent in the last_kmsg for a crash I had today on test1. Well... one crash, there were fewer than usual, but more than one. This last_kmsg actually appears to have info at the end of it that might be useful. It was definitely more stable than b11 and seemed more responsive. I'll attempt to try out test2 tomorrow, but my day is going to be very different than my usual weekday so it may not get stressed per normal.

EDIT: Since the last crash the phone has become extremely erratic in responsiveness on test1. Everything moves smoothly on the phone and audio and video keep playing, but it stops responding to any touch for 10-20 seconds at a time then suddenly catches up playing back all the touches it hadn't responded to at first.
[Droid Incredible Android Development] EnixLHQ:
Test 1 made it through the night and lasted a total of 16 hours before I had a random freeze. I was playing Words With Friends for a couple games and then set the phone down. The screen turned off, but a handful of minutes later the phone rebooted.

It was not charging at the time, was on wireless, had a mostly-full battery (guessing in around the high 80's).

Flashing Test 2 now.
[Droid Incredible Android Development] chad0989:
Thanks. I did find an issue from it. Not sure its the source of the crash but I fixed it anyway.
[Droid Incredible Android Development] :
Does this kernel work with miui? Or the betas? Thanks cause I love this kernel :)
[Droid Incredible Android Development] poontab:
^	Yes 10char
[Droid Incredible Android Development] EnixLHQ:
Test 2 made it through the requisite hour and a half navigation stint with the internet radio streaming. Afterwards I played some more Words With Friends and sent a text or two. After that I left it idle for about 45 minutes.

I either received a text or some other event but while screen off and idle after that 45 minutes I had a reboot.
[Droid Incredible Android Development] chad0989:
Its odd that yours always seems to reboot when idle. Can you get a last_kmsg?
[Droid Incredible Android Development] burnmatoaka:
Re: MIUI cam... There is definitely a framework issue with CM7. The one pulled from the latest MIUI ROM won't even open on cm7. Works great in MIUI, but the two frameworks seem to have diverged significantly in a few weeks. Don't sweat it too much.

[I for one welcome our new Android overlords ::: DInc::SLDC::x.2.15.00.04.08::CWM3.0.0.8::CM7latest::Chad's latest]
[Droid Incredible Android Development] rlacrossjr:
Thats weird because im running cm7nightly100 with tiamat4.0.5 and newest 05.06 radio. No issues with playing pandora and autofocus miui cam.
[Droid Incredible Android Development] Pons:
Same here, no issues. Except I'm running incredikernel b11.
[Droid Incredible Android Development] EnixLHQ:
Here we are.
[Droid Incredible Android Development] usn.mustanger:
After just a few contracts. It's gotta be the kernel, because when I switch back to 4/19 stable, all is well. It's definitely reproducible for me. No worries though, just as before, I'm content with your 4/19 kernel. I'm sure you'll do a great job ironing out the wrinkles on these .38.6 kernels! :cool:
[Droid Incredible Android Development] k_nivesout:
So test 2 seems to not do as well with some apps as test 1, ingenious 128/998. Got a freeze trying to use Netflix (couldn't even start a video) and had to hard reboot, also got a fc before I could start playing chuzzle. Seemed to notice a bit more typing lag as well. Not sure what the difference is but test 1 seems to handle some situations better.
[Droid Incredible Android Development] EnixLHQ:
I'm noticing a lot of errors in my log even before the event that seems to kill it. Is there something else wrong? I should probably do a clean install, eh?

EDIT: I had some time, so I decided to install CM 7.0.3 clean. After a few hours of installing apps one-by-one and setting everything up by hand I've backed it up and am ready to get a kernel going.

Think I might hang on B11 until there's another release, though.
[Droid Incredible Android Development] user_error:
I don't know what version I'm using but Miui camera seems to be working fine for me with the latest CM7 nightly and b11 - have been running it a few days now and the only issue I've seen is Screenshot FC's now, though I think it just got an update and don't feel it is related to b11 - as it was working until tonight.

I'm trying test2 now and I'll let you know if I have any issues running that.

Edit: Without OC on T2 I got a 1500+ score on Quadrant, with OC a 1620. What ever you did, it sure did speed things up! Only a few minutes in use, though it seems stable and smooth so far.
[Droid Incredible Android Development] Jinnai:
My experience with test2 has not been very good. Very unstable and has the touch input lag I noticed on test1 on some programs, but far more often. The big difference is on test2 it at least catches up after only 1-5 seconds, where test1 would take 15-20 seconds.
[Droid Incredible Android Development] chad0989:
http://chad0989.dyndns.org/2.6.38.6-incredikernel-beta12.zip

Played contract killers for as long as I could--stupid energy requirements--with no freezes.

Then I played robo defense for 100 waves while streaming pandora in the background. Still no freezes.

I can't get it to lock.

With that said, I'm confident you guys will manage to figure out how to lock it within a few hours, if not within minutes, so I've added a bunch of added debugging so logs will be easier to read.

Have fun.
[Droid Incredible Android Development] RebelShadow:
Ummm, I don't know if it's a problem with my inc and never had this happen before but I just tried to flash in recovery the new beta12 kernel and my phone locks up at the CM7 robot with round circle screen and sits there for about 5 or 10 mins then just reboot and locks up again. I do not have any voltage mods loaded and using CM7 #101 and this is a AMOLED inc. I have re-downloaded the beta twice and both do the same thing. This is the first time I have had this happen for the betas. Is it me or is there something wrong with this build?
[Droid Incredible Android Development] Pons:
Build is working for me. Try manually clearing cache.
[Droid Incredible Android Development] csseale:
12=greatness mad Chad good job
[Droid Incredible Android Development] RebelShadow:
did that twice and nandroid back to when I had beta11 loaded and tried to flash on recovery console and same outcome. When I go back into recovery, clear cache and delvic and flash beta11 it fires right up.
[Droid Incredible Android Development] mamarley:
I have the same problem as RebelShadow. I flashed beta 12, and now my AMOLED DInc is a nice, big bowl of Boot-Loops®. Flashing back to beta 11 makes it work correctly again.
[Droid Incredible Android Development] gonzlobo:
Odd, this morning I backed up, wiped cache, wiped dalvik, wiped battery stats, then loaded CM7-101 with b11. Everything worked fine.

A few minutes ago, I did the same routine twice, except with CM7-101 & b12 and got book locks both times.

I then did the same routine, but just loaded CM7-101. It booted fine. I then rebooted into recovery and flashed b12, it locks up.

I don't overclock or tweak voltages. Looks like I'll restore my CM7-101 & b11 backup.
[Droid Incredible Android Development] EnixLHQ:
You sound a little stressed.

Well, at least this will be done on a fresh CM101 install and I know how to get the log immediately after a crash.

Will report back.

Sent from my Incredible with Tapatalk.
[Droid Incredible Android Development] spidey81:
Add myself to the B12 hard boot locks. Tried flashing twice, wiping cache and dalvik both times. Flashed B11 and all went well. Gonna try redownloading and flashing again.
[Droid Incredible Android Development] thisguy23:
Chad I love 12! Very very fast on latest miui. Thank you.
[Droid Incredible Android Development] dmbtimmyb21:
winner00's CM7 ROM

Recently flashed winner00's CM7 build and have had tremendous battery life (non-intensive-usage) with the 2.6.37.6-cyanogenmod+jistone@folkvangr#1 kernel. Assuming it's very similar to slayher's stock CM kernel. Here's a screenshot (21 hrs and 53% remaining!!):

<Relevant to this thread, chad's beta 11 has produced the best results for me. Seems like that is a common occurrence from our stellar testers. Cheers. :D>
[Droid Incredible Android Development] k_nivesout:
So beta 12 flashed fine for me, tried testing it with a few things (ingenious 128/998, N101). Netflix worked well, played my paper plane (free Amazon app today) successfully, tried chuzzle but that resulted in a freeze, had to hard reboot. Seems like typing lag might be better on b12 too. If I can get you some kind of log just let me know.

Edit: Not sure what the changes are from beta 11 to 12 but I noticed that using 12 on smartass I got stuttering on Netflix video, 11 is smooth.
[Droid Incredible Android Development] EnixLHQ:
Sorry Chad. Had a lockup while playing Words with Friends.

Had the kernel running for a while, I'd say about an hour and a half, and put it through its paces. I had watched a couple YouTube videos, played a lot of music, and did some websurfing. While all this was going on it was stable, but laggy. I know this is about stability so I accepted the lag. Eventually, though, it got pretty delayed.

So I fired up Words with Friends and decided to play a few games. Third game into it and when I go to place a letter I don't hear any sound. Then the movement of the letter froze mid-move. After that I couldn't get any input to register. The softkeys did nothing, the power button did nothing, and of course the touch screen did nothing. Although, it's not a true freeze because I did notice the clock in the status bar still counted off a couple of minutes.

Eventually the screen timed out and turned off, which didn't help. I couldn't get it to come back on at all.

I tried the "three finger salute" to power cycle it, and even that wouldn't respond. Had to battery pull.

128/998 Ingenious on a fresh CM7, Nightly 101 with all my apps installed and settings set naturally (not a restore).

I couldn't find a last_kmsg on this one. Is it because I had to battery pull? It didn't register as a crash?
[Droid Incredible Android Development] Matt.:
Would this kernel work on myns warm two point two?
[Droid Incredible Android Development] Gahh Its Lee:
It's sense so yea
[Droid Incredible Android Development] chad0989:
No, the minimum while awake is 384, and when the screen is off 245.
[Droid Incredible Android Development] morph3k:
So I decided to switch to a sense rom (myns warm 2.2) and this kernel is awesome. my battery life is superb now.
[Droid Incredible Android Development] M3RK:
I am running SkyRaider 3.3.4 have tried Ziggy's and King's kernels several times and kept going back to Hydra's due to crappy battery life and stuttering on the others. It looks like Hydra has finally been de-throned. So far this kernel is killer. Great battery life and smooth as glass. Going to try it with MIUI.
[Droid Incredible Android Development] invisiblek:
you'll need to use my kernel for miui as it is aosp
[Droid Incredible Android Development] Lexus One:
Just FYI, I liked the awake minimum better at 460. 384 adds just a tad too much lag for me. What if I just used SetCPU to bump this back up? Would that do the same thing as resetting this in the kernal?
[Droid Incredible Android Development] jprow507:
What is the maximum at screen off? I sometimes use my phone as a radio when going to sleep and I tried multiple apps the other night and the music would continuously "hiccup" or be on for a while then off for a while, then on .....

I was connected to WiFi so I was wondering if maybe this has something to do with CPU utilization when the screen is off? Or maybe it was just something completely unrelated to this kernel?

But GREAT work on your latest release!
[Droid Incredible Android Development] JaydenR:
How do you OC this? SetCPU won't allow OC.
[Droid Incredible Android Development] bast525:
Dang... I had another lock up on reboot today with the most recent kernel with HAVS. Right as the phone was done booting and I went to unlock it it froze completely. That's three. I wasn't having any issues with Chad's previous 11/26 kernel.

So either HAVS is causing me trouble, or the new lower screen-on-minimum-speed is. For what it's worth, I had uninstalled SetCPU yesterday, as I didn't see any use in OC'ing and I wasn't sure if SetCPU could be causing issues.

That being said, I really couldn't see that HAVS was giving me any better battery life, and OC'ing from 998 to 1113 only made a tiny bit of difference in Quadrant, less than 100 points, and no noticeable difference in usability. So I'm not gonna cry if I have to stay with the 11/26 build, which runs flawlessly.

Chad, giving some of the small issues a few of us are having, it might not be a bad idea bumping the screen on minimum back up to 460 or whatever it was before.
[Droid Incredible Android Development] byrong:
I'm not sure I ever saw a direct answer to this one. Anyone? Does SetCPU override the kernel's preferred min/max values, or does the kernel override your attempts to set in SetCPU?

For example:

In this case, why not just use SetCPU to provide a higher min value? That way people who aren't happy with the current kernel can bump up their mins manually, while those who are satisfied with its performance can enjoy better battery life.
[Droid Incredible Android Development] chad0989:
Likely HAVS. Anyone else have this issue?

Can anyone confirm this also?
[Droid Incredible Android Development] dscribe:
Not yet here. So far, so good.
[Droid Incredible Android Development] chad0989:
SetCPU will overrride
[Droid Incredible Android Development] byrong:
Thanks for the info: much appreciated
[Droid Incredible Android Development] s197:
Flashed yesterday and initial results are very good. Regarding sleep mode, I walk to work listening to pandora with the screen off. My 15 minute walk produced no problems w/ pandora.

Regarding lag, not experiencing it. It did lag upon first reboot (lockscreen) but that should be expected, since then everything runs smoothly. Great job Chad and thank you for all your hard work.

(I uninstalled SetCPU prior to flashing if this makes a difference)
[Droid Incredible Android Development] Riley1524:
From one Chad to another:), this kernel is the best as far as being stable and fast with the best battery life. I have tried all the others and this has been the best hands down. Good Job! Oh, I'm running the latest Myn's
[Droid Incredible Android Development] meekehleh:
Also running Myn's. Flashed the 11/28 and it's running like a dream. No lockups or slowdowns. Charges quickly and battery is among the better kernels I've tried. If I'm not mistaken, Myn's already had a custom Ziggy kernel cooked into it.

For what it's worth, I also listen to Pandora/music when the screen is off, and I haven't experienced any hiccups.

Thanks Chad.
[Droid Incredible Android Development] setexascustoms:
No problems here, it's been running flawlessly, thanks for all the hard work. :D
[Droid Incredible Android Development] parkson:
Phone has been running better since uninstalling setcpu last night. I don't think HAVS and setcpu play well together on my phone.
[Droid Incredible Android Development] cheez99:
Beta 12 works fine for me so far. Even overclocked it to 1.1 GHz and didn't have any lock ups yet. Only thing is, may be just me, but it doesn't feel as smooth as like Beta 8 did when scrolling through the UI. Have you changed anything that may have affected this or is it all in my head?
[Droid Incredible Android Development] BarackMitzvah:
Maybe I'm losing it, but this kernel isn't as reponsive as 11, ill run it throughout the day and get back to ya
[Droid Incredible Android Development] stevefxp:
Radio Has An Effect?

All,

One thing I noticed in reading these posts and seeing people's device information in their signature is that there are a few versions of the radio that people are running. Some have stayed on an older version, while others have upgraded to newer versions.

Does anyone know the battery load a radio puts on a device? I am wondering if a particular version gives us the best coverage and battery life. I don't want to take up valuable space in this thread, so please do not post your responses here, but I have opened a thread in the Q&A section for this. I would appreciate it if you could respond there. I would like to compile the responses and see which versions people are running. I am then going to test each version for a couple of days and see the implications of each version on battery life.

Thanks,

Steve