yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] dmbtimmyb21:
Beta 8

Beta 8 was boot-looping on OMFGB 1.2.0 for me...still love your work tho Chad :)

Note: I flashed the kernel right after flashing the ROM, not sure if that makes a difference?
[Droid Incredible Android Development] mrsmith35sg:
I know it's a bit late to the party, but did you hear any issues with random reboots on your 12/23 +25 kernel Chad?

I really didn't see anything in this thread, and randomly it keeps happening on my g/f's phone. Stock rom, stock 7.28 radio btw.
[Droid Incredible Android Development] chad0989:
omfgb seems to boot loop on all of them. Not sure what the problem is but its the only ROM that does it, so I'm under the assumption its a rom issue of some sort. Someone said they were going to file a bug report with them but I'm not sure if anything came of it.
[Droid Incredible Android Development] k_nivesout:
For those such as myself that had reboot and bootloop problems, double check any voltage tweaks you may have done! I thought that flashing a different kernel would negate the voltage tweaks I was using, but no. Flashed beta 8 earlier and got a bootloop, booted into recovery and flashed the voltage mod reset zip and it booted just fine. Kinda feel like a dumbass now, thought something was funky with the latest beta kernels but it was just me being dumb :)
[Droid Incredible Android Development] chad0989:
Its possible that even with the +25 the voltages are a bit too low for her phone. Unfortunately I never added the HAVS sysfs interface to that kernel so the voltages can't be easily adjusted. I don't have access to my build machine right now but send me a message sometime this week and I'll build one with adjusted voltages or without HAVS.
[Droid Incredible Android Development] :
I will confirm, at least on my phone, that beta 8 works great with OMFGB 1.3. I flashed the rom, gapps, and then beta 8 all at the same time. No bootloop. Runs great!
[Droid Incredible Android Development] dmbtimmyb21:
Typo? I just went to the devs site and only see 1.2.0 available??
[Droid Incredible Android Development] dmbtimmyb21:
I actually have a means of contacting the dev for that ROM...will let him know Chad. Keep up the great work it's greatly appreciated. :D
[Droid Incredible Android Development] chad0989:
The users that reported it all had SLCDs. Not sure if that's the root cause though.
[Droid Incredible Android Development] EnixLHQ:
Beta 8 is wonderful.

No freezing, no reboots, no stuttering, nothing. I flashed the moment it was posted and haven't had an issue.
[Droid Incredible Android Development] SteveG12543:
He released a beta link for 1.3 on his Twitter on the 28th I believe.

Sent from my Droid Incredible running CM7.0.3.
[Droid Incredible Android Development] Testingchip:
What's his twitter id?

Sent from my cm7 vipermodded dinc with a Chad engine!
[Droid Incredible Android Development] mamarley:
Does it not have some sort of "Resume after power failure" option in the BIOS?
[Droid Incredible Android Development] chad0989:
It does. But I don't want it flicking on and off three or four times if the power is sketchy for a bit.

It's not expensive hardware, but if it died I'd have no means of replacing it for awhile.
[Droid Incredible Android Development] rlacrossjr:
Ginger Sense kernel?

I know this is off subject with the 2.6.38 beta's, but was trying the sense leak and GingerSense ReMix beta4 and wanted a better kernel. Tried both 12/23/2010 - Sense versions and booted up but menu/home buttons did not work and screen did not recognize touch. Should your kernel work or is it because ROM's are in beta phaze?
[Droid Incredible Android Development] thisguy23:
Chad is your server down? I've been trying to download any of your kernels and the links wont load.
[Droid Incredible Android Development] chad0989:
Try one of the newer ones. They might work with ginger sense. No idea. I haven't tried it yet or had time to play with it. Give it a shot and report back.
[Droid Incredible Android Development] Matt Devo:
sadly I'm still having A2DP hiccups with beta8, probably once every 45-60 sec, regardless of governor or speed. With Tiamat's kernels 4.0x I get a hiccup once every 4-5 min.
[Droid Incredible Android Development] rlacrossjr:
With the leak version rmk-rom-dinc_gingerbread the beta8 just does a splash loop The 041811 and Lou's#8 boots but screen touch works but menu/home buttons do not. restoring to CM7N90 with your beta8. Just don't like the performance of the stock kernels.
[Droid Incredible Android Development] tiny4579:
For kicks and giggles I thought I'd try it out:

Well, your latest stable boots with Uber Gingersense but the latest beta (beta8) does not boot. If I try to logcat, it exits and reboots it with no information.

Using the 4/19/11 kernel has noticable artifacting still and the soft buttons at the bottom don't respond.
[Droid Incredible Android Development] Gorilla*:
Waiting waiting on the chad to drop a stable...
[Droid Incredible Android Development] poontab:
Light use beta8. 245/998 ingenious gov. No reboots.
[Droid Incredible Android Development] BarackMitzvah:
Dang what's your secret? That's really good
[Droid Incredible Android Development] RustyNailz:
Which battery are you using?
[Droid Incredible Android Development] chad0989:
Server is back up.
[Droid Incredible Android Development] poontab:
Stock. 10char
[Droid Incredible Android Development] d08speed3:
What battery meter is that and where can I find it? Is it a theme?
[Droid Incredible Android Development] JetBomber117:
Settings, about, battery usage
[Droid Incredible Android Development] d08speed3:
Huh??? How does this answer my question?

I mean the actual icon battery meter
[Droid Incredible Android Development] yopete525:
They're instructions, the battery meter is built into Gingerbread.
[Droid Incredible Android Development] d08speed3:
I know how to get to that lol I meant the battery icon
[Droid Incredible Android Development] dmbtimmyb21:
OMFGB

@r2DoesInc
[Droid Incredible Android Development] yopete525:
Gotcha, yeah it looks like it's part of his theme.
[Droid Incredible Android Development] dmbtimmyb21:
Cheers and Thank You. :cool:
[Droid Incredible Android Development] dmbtimmyb21:
He means the icon with 57 percent left indicated...Is it a mod you flashed or built into the ROM itself?
[Droid Incredible Android Development] poontab:
BS Theme's Linear http://market.android.com/details?id=com.bsthemes_donate.theme.linear
[Droid Incredible Android Development] Gorilla*:
Ok, fine im trying your beta 8 kernel Chad...

What can u tell me about your new In genius Kernel?

Are u axing the old Smartass gov?

It seems your 4/19 Kernel is the problem with my screen wake issues... Im running 128/1113 Ingenius Governor and now when i boot into the OS,

My phone doesnt lock up when i try to unlock the screen 50 % of the time.
[Droid Incredible Android Development] EnixLHQ:
Just had a freeze on beta 8.

I had just left the game Zenonia 2 after playing it for about half an hour. When I was done, I exited out of it and moved to the main screen (Zenonia is on the far left screen in Launcher Pro). I then set down the phone.

I looked at it a few minutes later and saw that the home, menu, back LED's were still lit. I picked up the phone and saw that the screen had dimmed as it does before it goes to sleep on its own, but it had frozen there.

Nothing I pressed would do anything. Had to pull the battery.
[Droid Incredible Android Development] mikeymop:
Whenever I use one of the Beta kernels, by battery drains extremely fast. I had to jump back to 4/19 again. I went from 75%-23% in 30 minutes, just sitting idle on a freshly wiped Nightly 90 of CM7.

When I get that, almost all the time the three finger salute works (power, vol -, and the trackpad) have you tried that before?
[Droid Incredible Android Development] chad0989:
You always have to run a kernel for at least a charge cycle before the.battery indicator is accurate again. Your battery didn't drain that fast, your indicator is just lying to you.
[Droid Incredible Android Development] dmbtimmyb21:
Wow

over 50% drained on standby in 30 mins?? I was asked for a screenshot in earlier posts and must admit these numbers are puzzling. Maybe you had high-consuming apps running in background?? (like Google Maps, etc.)

the only time I've ever had anything remotely close to that was on the stock ROM Verizon bloated on my Dinc. something just ain't right.

@dmbtimmyb21

OMFGB running invisiblek's latest
[Droid Incredible Android Development] EnixLHQ:
I didn't know you could do that...
[Droid Incredible Android Development] TheWhiteBandito:
What is this wizardry? So glad you taught me this, I can't believe I didn't know about this before. Thank you.
[Droid Incredible Android Development] mikeymop:
Works for most HTC phones too, Moto Droid/Droid 2 have power, delete and home (or something like that, i need a phone to remember it)
[Droid Incredible Android Development] ArcaneMagus:
I've noticed two things on the beta 8 kernel set at 128/998 Mhz:

Sitting on the desktop I have only seen the phone go down to 245 Mhz, will it only use the 128 Mhz clock rate when in sleep mode, or is that a bug?

The other thing I've noticed is the phone performs slightly better when on battery vs. when plugged in. I'm not entirely sure if this is a kernel issue, or something to do with my ROM (CM7 Nightly #90). I tested this using Linpack, the raw data can be found here:

https://spreadsheets.google.com/spreadsheet/pub?hl=en_US&hl=en_US&key=0AgNHIQX2XG-ldEtxckM2VjlaeGE2OFdFenVaekI3Ymc&single=true&gid=0&output=html

Am I just imagining this, is this even a kernel issue, or something else?

(Sorry about the link, apparently you need 8 posts to actually use url tags here)
[Droid Incredible Android Development] EnixLHQ:
Alright, now I have something interesting happening, but I can't determine if it's a ROM issue or the kernel.

Running CM90 and beta8, for the entire first day it is smooth and personally I didn't notice any battery issues.

On the morning of the second day I had a ton of random FC issues, programs wouldn't open, I wasn't receiving notifications anymore, the whole phone just stopped working correctly. I wiped the cache and reinstalled CM90 but that didn't solve any issues. I restored to a fresh CM90 install and that cleared up the issue.

I didn't report this because I thought I had done something, or it was a ROM issue. This was yesterday.

For the entire rest of yesterday I've been running my stable CM90 with beta 8 and all day it was fine. This morning my alarm didn't go off, I had no no mail notifications, the Gingerbread colored icons indicating you're connected to Google were all white, FCs left and right....same as the last time.

Restored to that stable CM90 again and all is fine. I will run this CM with 419 to see if it was beta 8 causing the issue, but I've never experienced anything like this before.
[Droid Incredible Android Development] zeke1988:
I got this problem too after running beta8 for 2 days. Everything started to fc. I reboot and hope it will be gone, but i stuck in boot loop.
[Droid Incredible Android Development] itch808:
My battery is getting absolutely murdered with beta8 and CM7. I tried both ingenious and smartass. Neither changed it. Back to stock CM7 kernel for me

:confused::confused:
[Droid Incredible Android Development] FramCire:
Do you reboot or clear cache every 24 hours or so? I used to have more problems until I started rebooting every day.

This is with cm and any kernel
[Droid Incredible Android Development] BurningHell:
Battery gets murdered for me as well, sometimes drains 5% or so in like a minute beta8/#90
[Droid Incredible Android Development] EnixLHQ:
For me it doesn't take two days, only one. The issues appear overnight. After I notice the issue clearing both the standard and dalvik caches don't help. In fact, reflashing CM90 over itself doesn't help. I have to restore.

Rebooting the phone daily, or going into recovery every day to clear your caches, seems a little excessive. I suppose that's better than having things degrade, but why are they degrading in the first place?

Honestly, I'm stumped as to why this is happening. When I had my earlier issue that I determined was a Mixzing issue, it was basically this sort of problem just starting to rear its head. If I had not noticed it for my love of music it might have degraded into exactly what's going on now. Seems logical since I haven't had a chance to listen to music on my phone the last couple of days.

The only change, other than various app updates, is the kernel betas.

So, trying 419 on Smartass for now to see if things degrade.
[Droid Incredible Android Development] chad0989:
Again on the batteries...

You absolutely 100% CANNOT change kernels and expect your battery indicator to be even REMOTELY accurate without running it for at MINIMUM a full charge cycle. By full charge cycle I mean: you flash the kernel, run until it drains down to low (not completely, you'll wear your battery out that way), you charge it to 100%, wait until it drains down again, and you charge to 100% again.

The first time you run it after flashing, your battery indicator will go all over the place, I've even looked at the long term battery stats and it claims it charged itself magically in my pocket during the day. This is because other kernels contain different changes to the voltage regulator and battery drivers (this includes the stock CM kernel and anything based on it e.g. the recovery kernel).

My kernel uses 100% the battery driver from HTC and the only modifications to the regulator are for HAVS. Because the differences in the way the battery is handled, every single time you flash a kernel, you HAVE to run it for a charge cycle or more before the indicator straightens its self out.

Not to mention, this also goes for all kernels. If you clear your caches especially, during that long boot, your phone is sitting at 100% rebuilding the dalvik cache during boot. When you finally get booted, your battery indicator is going to drop like a rock. Changing kernels only exacerbates this effect because the indicator doesn't even have a reasonable start point.
[Droid Incredible Android Development] chad0989:
The minimum with screen on is set to 245. You can change it in /sys/devices/system/cpu/cpufreq/ingenious/

As for those numbers, they're so minimally different it could be just from whatever is going on in the background during charging (e.g. animating the battery icon).
[Droid Incredible Android Development] chad0989:
The fact that the only thing that helps once it occurs is a clean install leads me to believe its probably not a kernel issue (but you never know). Issues with the kernel are generally, it happens with this one (e.g. camera doesn't work, or it locks every single time I do this), but then I flash another and everything is just peachy, then I flash this one again and it comes right back. It is possible to have performance degradation over time if there is a memory leak or something, but performance would be fine after a reboot for awhile and flashing another kernel would immediately solve the issue.

It makes me wonder if it could be a nightly 90 issue and that might be why we haven't seen another nightly since if they're trying to fix the problem.

With that said, you never know. Anything is possible. We still can't figure out why the recovery affects multi touch, when it shouldn't. Haha.
[Droid Incredible Android Development] Adam.h.ogle:
I have been running beta 8 since you posted it. My battery life isn't much better, but definitely isn't worse. I have 12 hours on battery and I am at 60ish percent. During the day at work, I only have one bar of signal, and at night, I tend to play with my phone for a few hours. I usually dock the phone after 17 hours with 15%.
[Droid Incredible Android Development] EnixLHQ:
I completely agree. I did the stupid thing and accidentally deleted a recovery that was absolutely stable and wonderful. Nightly 60 something, I think. Since then I've been trying to find the next best stable nightly (I know, that's ironic on more than one level). 90 seemed like it fit the bill, but then this happened. It confused me, though, because I have been running 90 for a while and this issue only started this weekend.

Hmm... but then againt his weekend has been the only span of a few days I haven't been flashing one of your new betas. So, sitting there with no reboots probably let the issue appear.

At any rate, before anyone asks, 7.0.3 is not where I want to stay because for me and my phone it wasn't stable at all. Nightly 69, I think...whatever the one BEFORE sound profiles was the last rock-solid version I had.
[Droid Incredible Android Development] jesssiii:
Yeah, I'm not liking the Ingenius either. 4/19 & Beta 2 both are great. Right now sporting 4/19 Froyo on Ruby ROM.

Always use 128/768 Smartass.

DInc + Zeam Launcher

Chad's Incredikernel
[Droid Incredible Android Development] itch808:
I've flashed other kernels in the past and never ran my battery to complete dead and was still able to notice an improvement in battery life. Flashing back to stock kernel included with CM7 nightly showed immediate improvement without a battery cycle for me.

Either way, I ran my battery down to complete shutdown dead twice and back up again with beta8. Things still haven't improved my battery. Realize I know absolutely ZILCH about coding a kernel. I'm just contributing my experience :)

Don't get me wrong, I appreciate the work chad! I'm sure the kernel's working for some people. I'll come back and try a future kernel of yours again.
[Droid Incredible Android Development] FramCire:
I use cachemate (the widget) to clear cache regularly. I reboot every morning. Just simple reboot while in the shower. Not excessive to me.
[Droid Incredible Android Development] Gorilla*:
Chadwick, im running nightly 81 and everything is fine with uour kernel accept... i was listening to slacker radio today and when tbe screen goes off i get skips in my music..... 128/1113 ingenius....
[Droid Incredible Android Development] runagt2:
Cool trick Chad. I tried changing my screen on min freq to 128. Seems like everything is a little laggy now, e.g. keypresses take a moment to register. I don't really know how the Ingenious governer works and I'm sure that you have it finely tweaked, so I'm going to change it back.

What I don't understand is that if the CPU can scale from (now) 128 to 768, why won't it scale up if my keyboard or launcher are lagging? Not complaining here, just want your input.

Re: battery, I've been running b8 since you posted it here and my phone makes it through the whole day, can't ask for more than that.
[Droid Incredible Android Development] TheWhiteBandito:
Been running beta 8 on latest miui with ingenious governor set at 245/998 ans haven't had a lockup, or anything weird to report. Running well so far!

Sent from my HTC Incredible
[Droid Incredible Android Development] Testingchip:
I'm having no issues at all with beta8. Cm7 flashing nightly when available. Ingenious and insanely undervolted. As good a battery life as I could hope for.

Had one reboot but it was only because I was playing with the undervolt and went too far. :)

Thanks for your work.

Sent from my cm7 vipermodded dinc with a Chad engine!
[Droid Incredible Android Development] dmbtimmyb21:
Now that is one heck of a thorough reply. Thanks for explaining it so well Chad.
[Droid Incredible Android Development] dmbtimmyb21:
Market Issue Persists

Clear data and cache in Titanium Backup under "Manage Applications"? For both the pro key and app itself?
[Droid Incredible Android Development] dmbtimmyb21:
That's a good combo right there. Had that running on my Dinc for a bit until I solely ran Gingerbread.
[Droid Incredible Android Development] csseale:
Same here

..running amazing
[Droid Incredible Android Development] stevefxp:
Define insanely undervolted for us newbies. What CPU speeds are you running?

For everyone....are you using stock CPU speeds or are you pushing it? I am running 128/1113 and battery life is terrible. I was using a sip dialer(csipsimple) but even stopped that. I am trying to find a combination that gets me through the day. Wife is tired of hearing my battery ran out....lol!
[Droid Incredible Android Development] SomeGuyDude:
Undervolted, not underclocked. My guess is he's running viper's mod with the InsaneMOD settings.
[Droid Incredible Android Development] rlacrossjr:
Kernel GingerSense

Chad, I was playing around with the new GingerSense 2.1/3.0 and wanted to see about a better kernel.

2.6.38.6b8 splash screen loop

2.6.37.6 screen touch works but home/menu buttons doen't work and graphic lines

2.6.35.10-gb-inc2 everything worked but got the graphic lines

HeyItsLou#9 everything worked great no issue 3 hours

HydraKernel overclocked 1152 everything works great will use this one for longer test.

Ok weird I over clocked but after screen turns of it goes back to 998?? ROM must have something in it to override setcpu.
[Droid Incredible Android Development] Testingchip:
Exactly. Clock stays at 245/883.

Sent from my cm7 vipermodded dinc with a Chad engine!
[Droid Incredible Android Development] hazell222:
Just had issues waking my device from sleep. Pressed lock button for 1min then screen came up. Beta 8 128/998
[Droid Incredible Android Development] chad0989:
http://chad0989.dyndns.org/2.6.38.6-incredikernel-beta9.zip

glhf

The tunable you need to fix any issues like screen off music tearing should be there now. The default settings I have are working fine for me with Pandora while using DSP manager. If you do find you have tearing and want to tinker, mess with some of the sleep settings and let me know what works for you.

/sys/devices/system/cpu/cpufreq/ingenious/sleep_scale_up_load
[Droid Incredible Android Development] byrong:
Fastest kernel yet; it's giving me 9,999,999,999,999 on Quadrant! :D:D:D

In all seriousness, I see there's a test file on your server that is newer than Beta8, but in keeping with previous advice you have given, I'm not going to touch it since you haven't directly linked to it.
[Droid Incredible Android Development] bengals1975:
In running Beta 8 I seemed to have some faster than normal battery drain running Ingenious (I haven't tried to tweak any of the user configurable items to see if that would help). I tried to switch to smartass within Beta 8, unchecked/rechecked set on boot and rebooted. I ended up in a boot loop. to stop it I jumped into CM settings>performance>CPU before it all finished booting to see what was up there and that was about it - no reboot. However, in doing so I noticed it had changed my governor back to Ingenious and didn't keep the smartass setting. I went from Beta 4 to Beta 8 and don't recall the bootloop issue in Beta 4.

It may be worth noting that I think the automatic reboot would occur when the screen timed out and the device hadn't finished loading everything yet. Perhaps the screen off setting was more than it could bear. In hindsight I wish I would have kept the screen awake to see what happened. I'll reflash Beta 8 and try that later to see what happens.

UPDATE: flashed 4/19 then back to B8 (with standard wiping), no issues. No boot loops, battery drain with screen off for a few hours appears normal. Not sure what happened to mess it up before.
[Droid Incredible Android Development] chad0989:
Ended up with a music tear after about 45 minutes of listening to Pandora... so I made a quick change.

http://chad0989.dyndns.org/2.6.38.6-incredikernel-beta10.zip

Again, mess with the sleep_scale_up_load tunable.

and see how high you can get it without any issues. That's where we want to be for a default.
[Droid Incredible Android Development] runagt2:
Chad, what is the scale up load? I guess it's some nominal value where the system realizes it needs to step up the clock speed. Is it on a scale of 100?

Where should I be messing with these numbers? Root Explorer force closes and nano in term isn't working for me. When I reboot, values for all of the entries in the ingenious/ folder reset to default.