yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] mroneeyedboh:
TOast, since youre the MOd here, why not sticky my Kernel thread on the Dev forum or here.

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

Also if you want, add it in your first post for a dummy guide for some.
[EVO 4G Android Development] JSmurfy:
im having trouble finding the link for this kernel.. please help
[EVO 4G Android Development] dirkyd3rk:
Its like 6 post above you bro.
[EVO 4G Android Development] JSmurfy:
shockingly enough after going thru all the pages i found that.. and relized i paid for the kernel program..

-- im a douche.. totally forgot about that
[EVO 4G Android Development] dirkyd3rk:
Its all bueno! Hope that kernel PROGRAM is treating you great sargent ;-)
[EVO 4G Android Development] -shift-:
don't forget to update kernel manager pro. the latest will notify you of updates for your kernel.
[EVO 4G Android Development] JSmurfy:
wow this suxx. FC in my astro FC in my contact restore.. wtf and half my contacts are missing
[EVO 4G Android Development] Nondescript Van:
i second this. it really helped clear up some of the questions i had about some kernels and whatnot.

edit: well it appears it was stickied. that what i get for looking in the wrong forum.

anyway, I'm liking the kernel so far. good work.
[EVO 4G Android Development] funcrusher:
I've only experienced it not waking when I get a call once, but I've definitely experienced it not waking when pushing the power button. It acts as though it doesn't register the button push. Happens to me a few times a day.

This kernel has definitely improved my battery life.

7.0.2.1

GoDm0dE v5

Ondemand
[EVO 4G Android Development] JOEOZUNA4U:
do you have screen-on animations turned on? some people say turning them on fixes the issue
[EVO 4G Android Development] ViViDboarder:
Agrabren posted an updated GoDm0dE kernel on KernelManager under his name and the kernel name is PoonKang. This should enable sound for everyone.

I am also reposting it as TigerBlood by TeamWin so current TigerBlood users will get the update notification.

If you see this though... download PoonKang since it'll be easier for Agrabren to update you if he makes changes.
[EVO 4G Android Development] funcrusher:
Yeah, I do. It's not a delay in the screen coming on, it's like the device isn't registering the power button push -- it doesn't come on unless you push it again, even sometimes a third time.
[EVO 4G Android Development] :
For me, if I just touch the screen after pushing power it will turn on. Doesn't happen too often where it doesn't come on right away when pushing power button.
[EVO 4G Android Development] roids87:
Does it make any sense that a live wallpaper would make the phone respond better? I just tossed on the nexus wallpaper and my phone is responding better then ever. It just doesn't make sense haha
[EVO 4G Android Development] stolirocks:
Talk to me in a few hours, after you check battery life

Sent from my CM7 EVO Beast!
[EVO 4G Android Development] roids87:
Your gunna have to plug your phone in eventually....it just doesnt make sense how a live wallpaper makes the phone respond better. Before I put on the live wallpaper it responded great. It was the best setup I have found. Now its even better.
[EVO 4G Android Development] -viperboy-:
It makes your phone respond better because the CPU has to keep the processor clocked up to run it. So, instead of sleeping at 245mhz, for example, your phone might be sleeping at 384mhz.
[EVO 4G Android Development] EndlessDissent:
I doubt anyone uses USB tether besides me anymore, so I'm not surprised I haven't seen this reported, but USB tethering seems to be broken in the .38 kernels. When I turn on USB tether with any Tiamat kernel from 3.3.8 down, my computer running Crunchbang Linux connects automatically, but when I do it with Tiamat 4.0.0+ or the GoDm0dE v5 kernels, the computer doesn't respond at all even though the phone tells me tethering is turned on.

Like I said, I doubt many people use USB tethering, so this probably isn't a big deal to most of you (hence why it hasn't been mentioned yet), but it's the only Internet access for one of my computers at the moment, so I actually need it to work. I hope the fix is easy, because I would hate for toastcfh to bust his ass for a feature that only a couple people use.

Thanks for reading.
[EVO 4G Android Development] adamantypants:
^Good to know. When I tether my phone, it's almost exclusively corded. I hate wifi tether. I was about to flash and try this kernel again but I tether pretty frequently.
[EVO 4G Android Development] Stajdanley:
From OP: "-possible bug switching cams (needs tetsing and debugging works for some while some seem to have issues)"

I had the above issue after flashing this kernel. Cams would freeze when switching from front to rear, then need battery pull or reboot. My setup is in my sig (other than the kernel; back to stock CM). Cache/Dalvik wiped before and after flash. Thought I'd post my info in case it helps... no logcat this time, so I'm probably useless :/

Other than that, the kernel is great. Nice work, as always.
[EVO 4G Android Development] rombold:
What real differences are there between this and tiamat kernel?? also I am using Decks rom which i aosp and works awesome. gonna try godmode on it later.
[EVO 4G Android Development] toastcfh:
bumped on a minor version change
[EVO 4G Android Development] Rem3Dy:
Thanks for the hard work toast!
[EVO 4G Android Development] famouschris:
I'm having trouble on kernel manager downloading. If anybody has a mirror that would be great :)
[EVO 4G Android Development] toastcfh:
try going to settings>applications>manage applications>kernel manager and clearing the apps data. should resolve any issues u might have
[EVO 4G Android Development] ereinhart:
Fyi - HDMI sound is still not working on this newest update. It does work on the latest tigerblood kernel based off godmode.

Sent from my evo
[EVO 4G Android Development] ViViDboarder:
Agrabren is working on some more updates to fix and make HDMI even more robust. So when he's done I'll post it as TigerBlood, he'll update PoonKang and I'm sure toastcfh will merge in the changes too.

All in due time. :)
[EVO 4G Android Development] famouschris:
thank you sir!
[EVO 4G Android Development] wmdunn:
Any chance someone could post the kernel? Thanks!
[EVO 4G Android Development] dkelle4:
wowz0rz this kernel is t3h l337
[EVO 4G Android Development] -shift-:
*updates via kernel manager pro*

<3

*watches as the kang-bang begins*
[EVO 4G Android Development] Lento10:
Not everyone uses KM, it would be nice for someone to post the zip file.
[EVO 4G Android Development] awwbaw3:
Kernel Manager Pro "error unpacking boot image - please try again" every time. I have cleared app data to no avail. Help!
[EVO 4G Android Development] eyeballer:
Just use KM, faster than writing a post here.
[EVO 4G Android Development] mkeena0305:
Call for boycott
[EVO 4G Android Development] ViViDboarder:
Of... what? Why?
[EVO 4G Android Development] dirkyd3rk:
Yeah it almost killed me when I got this zip for you guys. If km is on my phone for more than 5 mins it will probably brick itself :-)

Here's the v6 kernel.

http://db.tt/PmMI3PD
[EVO 4G Android Development] CruzECO13:
v6 attached for those that have issues w/ kernel manager or do not use it for w/e reason.
[EVO 4G Android Development] ViViDboarder:
Niiiice... Redistributing someone else's work. ;)

KM works well and is convenient for developers to push their updates. It's a developers choice to use it.
[EVO 4G Android Development] -shift-:
reboot and flash again.

....sincerely hoping this is a joke post (for which i'm lol'ing). if not, i'm rolling my eyes at you.

a kernel flash almost killed you? a kernel flashing app bricking your phone based on elapsed time?? now that's impressive.
[EVO 4G Android Development] ViViDboarder:
I don't even have to reboot. I've had that before and I just click flash again... Usually works.
[EVO 4G Android Development] toastcfh:
http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler

edit lol nm everyone jumped on that question lol
[EVO 4G Android Development] toastcfh:
AOSP touch fix?!

@anyone

does this fix the aosp touch issue?

zImage.zip

this is not a update.zip. the zImage needs to be combined with the ramdisk from an aosp build to boot this
[EVO 4G Android Development] ffolkes:
yep, it works! what was changed? :D
[EVO 4G Android Development] Geniusdog254:
Damn I can't get this kernel to build. I have really bad luck with any kernel except an AOSP one apparently lol since my Nexus kernel builds fine, but I can't get the Evo kernel to build.

I've run my config and made my changes to source, but on compile I get this error:

geniusdog@Lappie:~/Desktop/supersonic-2.6.29-e1cabff5$ make arch=ARM cross_compile=~/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
scripts/kconfig/conf -s arch/arm/Kconfig
#
# configuration written to .config
#
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
arm-eabi-gcc: error trying to exec 'cc1': execvp: No such file or directory
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2

Is it a problem with my toolchain? I'm linking to the same toolchain as I use to build the Nexus kernel, so that seems unlikely, but I guess it's possible. I figured one of the more advanced people here could help me.

EDIT: Forgot to mention, I get this whether I'm compiling from Toast's GIT source or the source direct from HTC

EDIT: Never mind. Got it fixed
[EVO 4G Android Development] toastcfh:
UPDATE

updated github with AoSp touchscreen fix. see first post for info regarding it. ;)
[EVO 4G Android Development] Saturn2K:
So, if I compiled Froyo AOSP source and used this kernel, would everything magically work? I imagine 4G won't until it's kind of added to AOSP, but should the camera work? Really, I guess I'll just wait until someone comes out with a working Froyo rom.
[EVO 4G Android Development] Geniusdog254:
I doubt it, even with a stock kernel, FroYo doesn't have a working camera. And also, I'm pretty sure that FroYo added WiMax support to AOSP, but i could be wrong on that.

EDIT: Crap. Got the earlier error fixed. Stupid typo on my part, but now I hit this error:

CC arch/arm/mach-msm/devices.o
arch/arm/mach-msm/devices.c: In function 'msm_set_ums_device_id':
arch/arm/mach-msm/devices.c:452: error: 'usb_mass_storage_device' undeclared (first use in this function)
arch/arm/mach-msm/devices.c:452: error: (Each undeclared identifier is reported only once
arch/arm/mach-msm/devices.c:452: error: for each function it appears in.)
arch/arm/mach-msm/devices.c: In function 'msm_enable_car_kit_detect':
arch/arm/mach-msm/devices.c:463: error: 'struct msm_hsusb_platform_data' has no member named 'enable_car_kit_detect'
arch/arm/mach-msm/devices.c: In function 'msm_init_ums_lun':
arch/arm/mach-msm/devices.c:469: error: 'mass_storage_pdata' undeclared (first use in this function)
arch/arm/mach-msm/devices.c: In function 'msm_add_usb_id_pin_gpio':
arch/arm/mach-msm/devices.c:486: error: 'struct msm_hsusb_platform_data' has no member named 'usb_id_pin_gpio'
arch/arm/mach-msm/devices.c: At top level:
arch/arm/mach-msm/devices.c:490: warning: 'struct msm_hsusb_product' declared inside parameter list
arch/arm/mach-msm/devices.c:490: warning: its scope is only this definition or declaration, which is probably not what you want
arch/arm/mach-msm/devices.c: In function 'msm_hsusb_set_product':
arch/arm/mach-msm/devices.c:491: error: 'struct msm_hsusb_platform_data' has no member named 'products'
arch/arm/mach-msm/devices.c:492: error: 'struct msm_hsusb_platform_data' has no member named 'num_products'
make[1]: *** [arch/arm/mach-msm/devices.o] Error 1
make: *** [arch/arm/mach-msm] Error 2

Which is what I ran in to with the hacked kernel source as well. Obviously it's a problem with devices.c and the USB modes. Has no one else experience this issue?
[EVO 4G Android Development] joeykrim:
i just grabbed the source from htc's web site, cp arch/arm/configs/supersonic_config .config, ran make oldconfig, hit enter on all the defaults, used uClibc toolchain (already had it all setup, too lazy to switch to eabi atm) and it compiled just fine.

not sure why you're receiving any errors? unless i misread but if you're using completely stock kernel source, perhaps try un tar-gz it again. ive had odd issues like that when small files get even a tiny bit corrupted.

edit: disclaimer, i havent had a chance to grab toast's git version YET but i will be shortly. not sure if hes made any small tweaks which could cause this type of issue?
[EVO 4G Android Development] super-6-1:
I hope to see a OC/UC in this! Will we see this?

*Oc = overclock

*Uc = underclock
[EVO 4G Android Development] Geniusdog254:
I'll try it. I think it's strange that I get that error no matter what Evo kernel I try to build, I get that EXACT same set of errors with devices.c

I tried it with the old makeshift kernel, the direct HTC source, and Toast's GIT. The VZW Incredible kernel with that same devices.c file bit for bit will compile just fine.

:confused:

EDIT: That's hella strange. I erased my config and copied the default one, and I re-uncompressed it, and now it builds.
[EVO 4G Android Development] TrevE:
are you sure git isnt screwing you with converting linebreaks or something stupid? had that problem a few times :|
[EVO 4G Android Development] joeykrim:
ive had it happen before, not sure why but sometimes with ALL those files something gets a little off. glad my suggestion helped!
[EVO 4G Android Development] Geniusdog254:
Hmm now I just gotta figure out how to push my changes back to my github xD

Lol god git is a PITA but at least it builds now. I figured out how to push any new changes Toast makes to my fork, but I can't figure out how to make my local changes get pushed upsteam.
[EVO 4G Android Development] toastcfh:
u just make the changes to ur fork. then i can pull the "upstream" later. anyhow i got OC working and will be commiting that next. going to leave the stock setup as well for those who dont wanna use it
[EVO 4G Android Development] TrevE:
i was just diving into this. did you pull perflock off?
[EVO 4G Android Development] justinisyoung:
damn, beat me to it! :D
[EVO 4G Android Development] toastcfh:
yeah in the config and added the automagic setup for setcpu for the hell of it. also its undervolted also. i just nabbed pershoots nexus setup minus the crazy nexus stuff that we havent even began to tweak. i really just trying to kee the stuff clean at the moment. oh yeah i also played with getting FPS crap fixed and managed to get it like it was with the old source with epson panel(ie. tearing and such) so no commit on that just yet. err many bug to work out i feel in just getting the drivers right for awesomeness to take hold. i mean OC is cool but when u run neocore u still get a crappy 27.4 FPS even with the FPS hack :/ . erks me bad. idk ill commit here in a minute

Oc, UV, setcpu automagic, my config, and the stock files all commited
[EVO 4G Android Development] acrh2:
Would it be possible to release a compiled and flashable kernel with the fps fix, for testing?
[EVO 4G Android Development] chavonbravo:
does this kernel have netfilter?
[EVO 4G Android Development] l33tlinuxh4x0r:
Does this include the frame rate fix for the epson panels? Also will you be releasing binaries or just the source?
[EVO 4G Android Development] toastcfh:
added a direct link in the op. please use it thanx :)
[EVO 4G Android Development] -shift-:
hmm i'll pass on the info to shinzul when he's a bit more free then.
[EVO 4G Android Development] clshores:
Which Governor???

What governor should I use in CM7 with this kernel?

Thanks guys!
[EVO 4G Android Development] dirkyd3rk:
Obviously I was being sarcastic :rolls eyes: #flamer
[EVO 4G Android Development] Lento10:
Thank you
[EVO 4G Android Development] adamantypants:
Also, you can allow KM to download the kernel, then flash it manually. KM downloads into a folder on your SDcard called.... kernel manager. It's how I flashed this kernel when it was having the KM errors.
[EVO 4G Android Development] dkelle4:
Whatever one works best for you :)

I've personally always used conservative. I think other people use interactive too
[EVO 4G Android Development] -shift-:
as was i... but i guess it's more fun to sensationalize. flame on, johnny.

i prefer interactive, but it depends on how you use your phone and what works best for it. try them out and see!
[EVO 4G Android Development] :
I like interactive on the charger, and for short trips off the charger. When I'm going to be away from juice for more than a few hours I'll switch to conservative.
[EVO 4G Android Development] jefbal99:
I always got boot image errors when I was using CWM 3.0.0.5 recovery. I switched back to Amon_RA 2.3 and now KM is perfect.
[EVO 4G Android Development] dirkyd3rk:
Anyone else exp reboots/lockups? Using CM7 7.0.3.1 with v6; 2 lockups that caused reboots both using the browser. I opened a website and turned my phone to landscape and it locked up and rebooted twice. No random reboots prior to installation of v6. I wiped dalvik/cache and etc. Could the lockups be caused by the cpu not ramping up enough to transition the phone from portrait to landscape? (1113 max, 245 min interactive).
[EVO 4G Android Development] :
Please provide /proc/last_kmsg from the hardlocks (after reboot) and/or a logcat if it lets you.

FWIW, I did not experience these issues, but I also haven't ran V6 for very long.
[EVO 4G Android Development] CruzECO13:
I could not produce any reboots or lockups using the browser or phone since flashing v6 this morning. (7.0.3.1, 998max, 245min, ondemand)

So far it has been smooth for me.
[EVO 4G Android Development] mkeena0305:
Very much appreciate it
[EVO 4G Android Development] mkeena0305:
Kernel manager had caused problems with me flashing. So if I want a kernel off there I turn off automatic flash.

Back on topic. Kernel has major godspeed
[EVO 4G Android Development] dirkyd3rk:
Thanks dudes. My guess is that either the site was waaaaay to big and possibly flash plugin could have crashed but idk. I think that's about all I have on that subject and if it happens again I will get a logcat.
[EVO 4G Android Development] stolirocks:
Load km download the kernel, then uninstall km. Simple. And it gives you a warm fuzzy feeling knowing you can help yourself =)

Sent from my CM7 EVO Beast!
[EVO 4G Android Development] JSmurfy:
i think this kernel is causing my wifi not to work correctly.. conna load previous version of this kernel
[EVO 4G Android Development] Negrito:
This wasn't mentioned in he OP, or the last few pages....

1. Is this kernel Evo specific? (I ask cause I run CM7 on my Nook)

2. Is this ok to flash over nightlies, or is it only for stables? (I didn't see anywhere that said if this kernel is 2.3.3 or 2.3.4)

Tia!

Sent expeditiously from the free XDA app...
[EVO 4G Android Development] jefbal99:
I use it on the nightlies just fine
[EVO 4G Android Development] drdrewdown:
don't try to run it on the nook. kernels are very device specific.
[EVO 4G Android Development] Negrito:
Thank you both for the quick responses.

Sent expeditiously from the free XDA app...
[EVO 4G Android Development] awwbaw3:
Reboot and flash again - NO GO with KM Pro... I have contacted Shinzul via email. I think he is looking into it... Was able to flash toastcfh OP version from Clockwork Recovery 3.0.0.5 just fine.

Thank you all for your continued efforts (supporting and devving). You are awesome!!!
[EVO 4G Android Development] deathpod:
Fine kernel, Toast. Really helped my battery life.

However, I've noticed the sound quality over a2dp seems to have been degraded a bit. Do you know what the bluetooth bitpool is set to? If its low, like 32, could we get a version with it bumped up a bit?

Thanks for all the work you've done to make our Evo's awesome!
[EVO 4G Android Development] spartan1987:
Can we get HDMwIn support with this kernel? I loved using it until I needed to get audio out on CM7 with netflix. Thanks
[EVO 4G Android Development] :
HDMwIn is supported. Audio Fix for CM7 is in the works. You can use the PoonKang kernel in Kernel Manager for the time being if you want audio, however it is only beta quality right now. You are welcome to test it.
[EVO 4G Android Development] ViViDboarder:
Ah, thanks! It's nice to know someone reads my posts, haha.
[EVO 4G Android Development] roids87:
Has any1 noticed longpress issues? Sometimes my longpress works fine, and sometimes it doesn't work at all, but a regular touch still works. I'm also having real bad screen on problems with nightly 73. I'm not sure if its the ondemand governor or if its the 245mhz min clock speed. I'm currently on interactive at 384mhz min, and screen on seems to be responding much better but still has its moments when I have to hold down the power button for a second to get the screen on. Screen on/off doesn't seem to make any difference either way.
[EVO 4G Android Development] fiddy619:
Just wanted to say thanks for your great work sir.
[EVO 4G Android Development] Apo11on:
you can say it here
[EVO 4G Android Development] dkelle4:
toast - just wanted to say you are the greatest <3
[EVO 4G Android Development] -shift-:
+1 on this.

So far, not a hiccup in daily usage :D

YEAH TOAST!!!

Sent from my Transformer
[EVO 4G Android Development] jefbal99:
Having an oddity with GPS and I'm not sure if its Kernel or ROM related...

I'm running CM7 nightlies and as soon as I flash the nightly, I flash GoDm0dE from Kernel Manager. GPS will lock on and work once, then after it shuts down, GPS will never launch again until I reboot.

I'm trying tiamat's kernel to see if the same condition exists.

Edit in: After flashing Tiamat's kernel, GPS is working consistently. Are their any logs or data I can provide for this issue I'm seeing with the GoDm0de kernel. My phone has been great when using toast's kernel and I'd like to start using it again

Edit in2: Flashed N77 and left the CM7 kernel on for awhile and had no GPS issues. Used multiple apps, turned GPS on and off.
[EVO 4G Android Development] snowboarda42:
v6 is giving me even better battery life than v5, way to go!
[EVO 4G Android Development] THunDA:
Same here, Ive been on a flashing frenzy trying different roms and kernels lately but I ended up flashing back to CM and this kernel as its just smooth as butter and gives me the best battery life. I found my phone likes the interactive gov. the best.
[EVO 4G Android Development] dkelle4:
Oh the wh0rr0rz of not running this kernal!
[EVO 4G Android Development] jefbal99:
It appears that my GPS issues are ROM related as its started to show up in other kernels. I'm flashing a sense rom and going to try the GPS fix again.
[EVO 4G Android Development] IOInterrupt:
Does godmode use HAVS? I'm a long time Tiamat user that has been interested in the godmode kernel, but I don't see any information about the kernel's tweaks, so I've been reluctant to use it. I like to know what's going on in my little black box :D
[EVO 4G Android Development] -viperboy-:
Taking a quick look through his github, it doesn't look like it.
[EVO 4G Android Development] :
No it doesn't. This is kernel is made to be as stable/risk free as possible. No HAVS, no SBC, no other fluff.
[EVO 4G Android Development] suprano:
sweet kernel..one most stable kernel i've run without sbc. :D
[EVO 4G Android Development] deviouskater:
I've looked at opening post but just wanted to check if the HDMI audio out was corrected and working. Thanks
[EVO 4G Android Development] eniamg02:
I dont believe its been added yet.get poonkang from km
[EVO 4G Android Development] dkelle4:
ramCFH FTMFW
[EVO 4G Android Development] Apo11on:
The commits for HDMI audio in both, TigerBlood and Poon Kang kernels are not final. It's still being worked on.
[EVO 4G Android Development] toastcfh:
bumped for minor version change

v7
[EVO 4G Android Development] toastcfh:
v8 reverts edid code that was borking audio.