yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Holyrolla:
That was the make-shift kernel based on the Incredible source with the Supersonic board files that were "provided" to Toast. Because it was makeshift, the camera didn't function and there were other problems also.

EDIT: Oops! That is this thread isn't it. Welp...anyway...according to Toast, this is technically still not a fix as there is the tearing issue, and technically, the limit is still there, Vsync is just turned off.
[EVO 4G Android Development] peekb24:
new to android

like im so lost how do u uncap the evo 3fps step by step plz sumbody any body
[EVO 4G Android Development] jblazea50:
1. find out what screen panel your phone is using (Epson or Novatek)

you can easily find out by looking at this thread: http://xdaforums.com/showthread.php?t=720209

2a. Epson Kernel thread: http://xdaforums.com/showthread.php?t=719763

2b. Nova Kernel thread: http://xdaforums.com/showthread.php?t=711964

Whichever screen you have, go to the correct thread and download the kernel

3. Put the kernel on your SD card

4. Boot into recovery (you must be rooted)

5. Flash the kernel via option in recovery

6. You may have to flash the Wifi and 4G fix (also provided in the thread for Novatek panels)

7. Reboot

8. Test out by using the free market app FPS2D

9. Use SetCpu to overclock/underclock the kernel
[EVO 4G Android Development] dalex7777:
Combine thread with Novatek kernel

This is awesome!

I stopped following this thread, though, when I found out I had the original Novatek panel. Shouldn't this thread be merged now into the one with the kernel that was released with the actual HTC kernel? Here is that thread: ./showthread.php?t=711964

Since the kernels are there for 30+ FPS for Novatek and this one has the one for Epson's I would think all EVO users would want this info in one place. Mods do you agree?

Toast and all devs, thanks you all for all the hard work you do!
[EVO 4G Android Development] tarheelsmj12001:
Ok so i followed ur steps n im still getting 30 fps n stdev of 15.96. Do i need SetCpu to get the fps higher than 30 or is that just for processor?? Idk wat i did wrong.
[EVO 4G Android Development] phobia:
no setcpu needed...
[EVO 4G Android Development] roketteere:
Question

Hey peops i was trying to download the kernel but the link seems to be broken. Now If this is already answered dont mind me. I was wondering if this kernal will allow me to use MMS being on MetroPCS...Im guessing the U2nl will be the key to working here...If I use this kernel and push the u2nl and do the rest of my stuff will it allow it to work? Oh yeah and this is directly towards the new HBoot 2.02.0000 not the older verisons. Thanks!
[EVO 4G Android Development] jerdog:
This kernel is outdated. You'll want to look at something else that bases itself off of Toast's work - like Netarchy's
[EVO 4G Android Development] xlGmanlx:
wow, talk about resurection, but as the other poster stated, try NET's for sense or even better MS's thread that is based off of NET's which is based of this kernel and has the battery charging tweak
[EVO 4G Android Development] joeykrim:
I'm looking for the latest and greatest kernel for the HTC EVO 4G from Sprint. I purchased my wonderful EVO on June 4th 2010 and this kernel was the best thing known to man at the time.

Where can I get an updated version of this? I won't run anything on my phone except either HTC's kernel or ToAsTcFh kernel.

Please help me find ToAsTcFh's latest kernel thread?

Hi ToAsTcFh!
[EVO 4G Android Development] skydeaner:
Joeykrim... I have used something of yours on my wife's moment and it is good stuff, I haven't had to mess with it in a long time.

The closest thing you will get is netarchys kernels. He startd his kernels calling them netarchys toastmod because of toasts excellent work that he based his kernels off of. All of his kernels are 100 percent stable. Currently toast only helps make the aosp kernels that come with cyanogen. And way to necrobump lol.

If you need help picking a kernel based on raw data, check out the web page in my siggy.
[EVO 4G Android Development] bedoig:
I believe toast is largely responsible for the CM EVO kernels.
[EVO 4G Android Development] CruzECO13:
From toasts twitter:

v3 is now up. kernel manager doesnt seem to work for me at the moment so just incase it's attached below!
[EVO 4G Android Development] mmegalodon:
wow good look on the thread bump

took a couple tries but eventually successfully went through with kernel manager.

gonna see how stable it is with my device
[EVO 4G Android Development] CruzECO13:
I just flashed it and its running smooth so far :)

Also, I somehow missed there was already a thread for this over here :P
[EVO 4G Android Development] mmegalodon:
hah yeah seeing a couple threads for it, not sure if I did a disservice by bumping this one if the other is more current / up to date. somehow this kernel went undetected for myself from start to - well - here. saw a couple mentions in the last few hours so I figured I should check it. usually a kernel that doesn't play nice with my phone shows itself damn near immediately and at this point things seem fine enough ... gonna give it the long form bc test. :D
[EVO 4G Android Development] toastcfh:
yeah this was the first kernel for the evo (before htc released source). lots of team work went into this kernel by myself, maejrep, netarchy, AssassinsLament, and other key members of the evo kernel community. i didnt wanna taint it, because this was a wonderful time :)
[EVO 4G Android Development] knightwolf123:
Super fast, very responsive, can I get it with sbc ?
[EVO 4G Android Development] mmegalodon:
Dig it. You guys do amazing work all around, have to check it out. :)
[EVO 4G Android Development] asafegous:
What does cfh stand for?
[EVO 4G Android Development] cordell12:
Cowboys From Hell, where have you been?
[EVO 4G Android Development] alvintimothyjr:
Teamwin nonsense on the "twatter" cracking me up

cm7Evo
[EVO 4G Android Development] InSaNeO1488:
download link not working trying to search for a link on the net but cant find it. Also does this work with AOSP roms?
[EVO 4G Android Development] Hero_Over:
Re: {KERNEL-SOURCE} GoDmOdE-EVO-2.6.29 {Make Shift Kernel}

They probably wanted cheaper components. Aka screen
[EVO 4G Android Development] timgt:
That doesn't seem right. I have an I/O EVO and my sensors are not working with your overclocked kernel.
[EVO 4G Android Development] Hero_Over:
Re: {KERNEL-SOURCE} GoDmOdE-EVO-2.6.29 {Make Shift Kernel}

Haha I knew it. So the board specific files don't work at all. I figured that. That means a lot more work til we have a fully functioning kernel
[EVO 4G Android Development] timgt:
kinda curious now the differences between the novtec and the epson screens. Hmmm
[EVO 4G Android Development] ffolkes:
i got my evo at radioshack, and my hardware revision is 0002. i rebooted and checked dmesg, and that confirms

"<7>[ 0.000000] tag_panel_parsing: panel type = 1

...

<7>[ 4.028320] mddi_novtec_probe

...

<4>[ 0.253204] supersonic_init() revision=2"

i wonder if revision 2 or 3 is better. i guess only time will tell. did they replace an inferior component (lcd i guess) with a better one? or vice versa.
[EVO 4G Android Development] toastcfh:
Sensors should work and camera also. On the I/O devices at least. Most likely the ramdisk has issues or something along those lines. The main files/drivers for the I/O devices are in the source. It actually seems that only the rev.3/0003 devices have a different display or something and the actual code in the panel does not have support for the newer panel/display. But camera, sensors, and all other hardware drivers for the 0002 device are in the source and code is in the board files. In other words there is no reason the source shouldn't produce a fully functional kernel for the rev.2/0002 devices.
[EVO 4G Android Development] npace:
Hero_Over, how did you make your OC kernel boot?

Did you compile it from this source at all?
[EVO 4G Android Development] chuckhriczko:
Toast, my I/O Evo won't boot any kernel that i try to compile from your source. I even just cloned your source and compiled it straight up, no changes and it did not boot.
[EVO 4G Android Development] Hero_Over:
boot my kernel. it is made from toasts source. then tell me if sensors and whatnot work. and i am using a stock ramdisk which works with everything on a stock kernel. i can confirm the kernel does break things. both on rev2 and rev3
[EVO 4G Android Development] timgt:
It won't work, I already said I have an I/O EVO and no sensors work
[EVO 4G Android Development] Hero_Over:
i know thats what im trying to explain to them
[EVO 4G Android Development] toastcfh:
hmm try using the akmd and bma150 from nexus or incredible. it could be something small that needs to be fixed in the source to make it more evo like. anyhow i cant really test things out as me EVO is a 0003 device. but i do know that EVO uses akmd and bma150 for sensors as do a lot of other devices. the kernel source is based on the Incredible so it could be looking for the Incredible akmd or bma150 sensors setup. please let me know if this works for u guys.
[EVO 4G Android Development] timgt:
Anything anybody puts together I can try, I have an I/O device and im willing to try anything that can help. lol
[EVO 4G Android Development] maejrep:
Just means they made a change to the hardware and it's a different batch. So far, the most noticeable change is the LCD panel.. I/O (and other rev 2) phones have a novatec panel, and rev 3 phones have an epson panel. That does not mean that our novatec panel is flawed, or anything like that.. it's just inventory. They made one batch with what they had, ran out of novatec, then the next batch was made with epson. At least that's the hope ;)

I've already made as many reverse engineering changes to the panel code that I can determine based on the stock kernel binary. And it still doesn't boot on rev 3. I'm working with toast to see if we can at least get some kind of data from the panic or whatever is causing it to reboot.
[EVO 4G Android Development] maejrep:
Found some more differences in the kernel, making headway toward both fixing sensors (most of them actually *are* working, btw...) and hopefully booting on rev 3. Hopefully I'll be in a place to commit something this week, but working at it for 5 hours, after leaving my day job at midnight, isn't something I can do very often :(
[EVO 4G Android Development] joeykrim:
i compiled this kernel too but it was before i got my EVO ... nice to see this thread alive again!

not sure how much effort we want to put into organizing everything here, but it would seem helpful if we had a list of known bugs (if there are more issues outside of just the lcd panel? seems maejrep has fixed the sensor issues...). i feel bad seeing only a few ppl doing the majority of the work. maybe with the known bugs list, we could all start workin towards fixing them? either way, appreciate everybody's work here!!

to be honest, ive just been kickin back hoping HTC would release their source code SOON, but that might just be a bit too much wishing on my part..

from my experience, if the kernel doesnt boot, system never gets to the point to load adb and logcat can't be pulled...

as npace asked, i am curious, how people are pulling the dmesg errors from the kernel boot?
[EVO 4G Android Development] Vinny75:
new to android development... how do you build this? can you just untar and make? or does it need to be extracted over an existing android base?

I'm getting an arm-eabi-gcc error but i've managed to build eclair and froyo on my dev vm
[EVO 4G Android Development] joeykrim:
details details details!

arm-eabi-gcc is the toolchain, what kind of error are you getting? do you have the cross compiler linked up when you're compiling the kernel?

if you're managed to build eclair and froyo, you should be somewhat familiar with toolchains ... need more details before we can offer very accurate assistance!
[EVO 4G Android Development] Vinny75:
Sorry... arm-eabi-gcc not found

I just followed the instructions at source.android.com to set up the environment, git/repo, then make..

oh think i figured it out make ARCH=arm CROSS_COMPILE=~/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
[EVO 4G Android Development] Vinny75:
So these are the steps I've used to set up my VM for android development and build the zImage... am I right so far? Is there instructions on what do next to make the boot.img?

1) Install Virtual Box (www.virtualbox.org)

2) Create a new linux virtual machine with atleast 25GB dynamic drive

3) Install Ubuntu 10.04 32-bit version (http://www.ubuntu.com)

3a) Perform Ubuntu updatesInstall

3b) Virtual Box Guest Additions

4) Open Ubuntu Software Center

4a) Edit Menu => Software Sources

4b) Other Software tab and Add "deb http://cz.archive.ubuntu.com/ubuntu jaunty-updates main multiverse"

4c) Search for JDK, install Sun Java(TM) Development Kit (JDK) 5.0 sun-java5-jdk

5) Open System => Administration => Synaptic Package Manager

5a) Uninstall default-jdk, openjdk-6-jdk, openjdk-6-jre-lib, openjdk-6-jre-headless, icedtea-6-jre-cacao, ca-certificates-java

6) Open a terminal window, enter these commands:

$ sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev

$ cd ~

$ mkdir bin

$ curl http://android.git.kernel.org/repo >~/bin/repo

$ chmod a+x ~/bin/repo

$ mkdir android

$ ~/bin/repo init -u git://android.git.kernel.org/platform/manifest.git

$ ~/bin/repo sync

7) $ git clone http://github.com/toastcfh/HTC-Supersonic-Incredible-2.6.29.git

8) CD to ~/toastcfh-HTC-Supersonic-Incredible-2.6.29

9) make zImage ARCH=arm CROSS_COMPILE=~/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
[EVO 4G Android Development] npace:
You've got it!

Next step is to use something like this:

http://www.droidforums.net/forum/ko...troducing-any-kernel-update-zip-template.html

Personally, I havent been able to use this on the EVO. So what I've been doing is basically perform manually the steps that the updater-script would do.

1. Copy the files from Koush's anykernel/kernel dir to /sdcard/anykernel

2. Copy your new zImage to /sdcard/anykernel

3. Reboot into recovery and adb in.

4.

cp /sdcard/anykernel/* /tmp/
cd /tmp
./dump_image boot boot.img
./unpackbootimg boot.img /sdcard/anykernel/
./mkbootimg.sh
flash_image boot newboot.img

Reboot and your device will not be able to boot :) unless you've figured out how to make toast's kernel boot.
[EVO 4G Android Development] Vinny75:
I know they will release the source but figured it couldn't hurt to request it...
[EVO 4G Android Development] jerryparid:
Wow, did I see that right?

Droid Incredible's source got released on 4/30, launched on 4/29?

wtf
[EVO 4G Android Development] toastcfh:
u also have an engineering spl so u can fastboot the kernels u wanna test. much less work imo.

anyhow read the first post. the kernel only works on 0002 devices. not the ones that sprint released. only the I/O devices.
[EVO 4G Android Development] Cicatrize:
I have a launch day (Best Buy) 0002.
[EVO 4G Android Development] npace:
well... some people have been able to get it to boot from what I understand.

There are OC kernels out there based on your source and they boot on 003. I am extremely interested to find out how?!

As to the eng bootloader, thanks a lot for it! I didnt have it when I was flashing it this way :)
[EVO 4G Android Development] Vinny75:
Yeah I'm on a release day 002 device so hopefully it will work... going to give it a whirl a tonight hopefully
[EVO 4G Android Development] AssassinsLament:
Wow wow wow, thanks again toast. I'm a beginner at android, although not at developing. Anyhow, I compiled the zImage as is from toast's source, and I was able to boot. I do have a 0002 hardware version, but it's a retail and not specifically Google I/O, although probably the same batch/revision. But yes it definitely works on retail 0002.

I used fastboot to test out the kernel and confirmed it by checking the software version and also confirmed the camera as not working. I'm excited that it worked for me because that means endless play time for me! Gonna keep the EVO now, if anything, to fix what HTC can't! :D
[EVO 4G Android Development] joeykrim:
this is great to hear! always good to have kernel developers around!

i compiled a kernel before i had my EVO cuz toast released this a while ago but i haven't tested it yet.

could you share what you did for the ramdisk and the command/s you used to load it with fastboot?
[EVO 4G Android Development] AssassinsLament:
Basically all I did was just compile the zImage, reboot the phone into bootloader, download and run fastboot from my ubuntu:

fastboot flash zimage zImage

Didn't touch anything else, very simple. fastboot saves a lot of time. Just make sure you have the hardware revision 0002, as this source doesn't seem to work with revision 0003 phones.
[EVO 4G Android Development] Vinny75:
What command would back up the original zimage before flashing the new one? Given the track record with this one want to make sure I can put the original back
[EVO 4G Android Development] joeykrim:
im not an expert, but you can pull the boot.img out of any of the PC36IMG.zip files or the any of the rom.zip files from the RUU's.

also might be able to dd or cat the kernel partition on the phone into a file.
[EVO 4G Android Development] toastcfh:
http://htcpedia.com/forum/showthread.php?t=1404

loxdev is the man. thanx goes to him. but there is all u need to know about rom cooking, boot.img creation, and such to do the job
[EVO 4G Android Development] Cicatrize:
Toast, is the only thing you changed in this kernel the addition of the supersonic board files?
[EVO 4G Android Development] toastcfh:
yes in short. its incredible source. u could take those board files to any snapdragon devices .29 source and drop them in and compile. i did make changes to makefiles and kconfigs to allow for the supersonic to compile and also added the defconfig to configs. which is a basic stripped down config for the supersonic. lots not enabled and such. the .config is straight from the evo though
[EVO 4G Android Development] Cicatrize:
Ok perfect. That narrows down some issues with the framerate problem since it has to be in the configs or the board files because this kernel still exhibits the issue. Thanks.
[EVO 4G Android Development] Vinny75:
sweet, kernel worked for me. tried the audio hack for the nexus one... seems to make a difference...
[EVO 4G Android Development] AssassinsLament:
I didn't back mine up, I just used my nandroid backup when I was done messing with it.
[EVO 4G Android Development] Vinny75:
alright im just going to grab the stock kernel from here, pull the zImage and push it back... audio is nice... but no camera =\

http://xdaforums.com/showthread.php?t=701685
[EVO 4G Android Development] toastcfh:
Updated first post

maejrep has made a few commits to the source, fixing a few things for the 0002 devices and commiting changes made to (hopefully) get the panel code right for the 0003 devices. still no worky for 0003 devices. but me a maejrep have narrowed it down and are now just working to add the missing pannel/epson code for the 0003 devices.

for those who actually wanna help in reversing the changes for 0003 devices, we now know that the init is at least getting to board-supersonic-panel.c. supersonic_mddi_init() seems to be where the init process is going south. we found this out by using the same method maejrep used on the HeroC to reverse engineer the HeroC .27 kernel to GSM Hero .27 source. in that even were still doing this blind. what we did was take some code to reboot the device to recovery at a give point and moved that code through the init calls until we were not able to reboot to recovery. at that point were able to tell how far its getting (after a gang load of tries :P ).

so yeah thats the progress on development so far.

good news = 0002 devices have a few more things working and were finally narrowing the panic down on 0003 devices.

bad news = the kernel still hasnt made it to ramconsole yet and were stuck reverse engineering the panel code for 0003 devices. :/

awesome news = were making progress!!! ;)
[EVO 4G Android Development] maejrep:
Wow, they've come far in the past year or two, on how to respond to these requests ;) Glad to see them explaining it in at least better terms than "I don't know what that means"
[EVO 4G Android Development] maejrep:
best news = with toast and I going back and forth for the past couple weeks, we've finally figured out what was causing the panic, and fixed it :) It now boots on rev 0003 devices, but we're still not sure if video is really working "correctly" yet (toast says the image looks pretty screwed up, as of a couple commits ago).

Check out the latest github commits to see what we've fixed. A lot of stuff was done to bring the outdated epson code back into sync with 1) novatec code, and 2) what the disassembled stock kernel says it should be.

If video is still screwed up, it means we need to dive into mdp and msmfb code to figure that one out. But as of now, we at least have kmsg, and it boots!
[EVO 4G Android Development] maejrep:
FYI, a better (or at least safer and more convenient) way to do this is to actually rebuild a recovery.img, replacing just the kernel.

When you run the boot.img split script (whichever one you use), you'll end up with recovery.img-kernel and recovery.img-ramdisk.gz

Then when you compile the kernel, you'll end up with a new arch/arm/boot/zImage file (that's your new kernel). Just rebuild a new test image with:

mkbootimg --cmdline 'no_console_suspend=1' --kernel ./arch/arm/boot/zImage --ramdisk ~/path/to/recovery.img-ramdisk.gz --base 0x20000000 -o newboot.img

That will create newboot.img, which you can actually flash as a new recovery image, or you can simply boot it directly from fastboot and not risk writing a bad kernel into flash -- this means at least while testing new kernels, you won't be doing anything permanent, and you can just reboot to get back to where you were. Just do:

fastboot boot newboot.img

and off you go :)
[EVO 4G Android Development] maejrep:
toast has just confirmed the final fix for display issues :)

Still work to be done, but now it finally boots and works (and looks normal) on rev 0003 devices.
[EVO 4G Android Development] toastcfh:
hurray \o/ :D
[EVO 4G Android Development] spiicytuna:
WooHoo! Great news! Excellent work! Does this mean soon that we'll be able to overclock without breaking the camera, accelerometer, etc.?
[EVO 4G Android Development] AssassinsLament:
Thanks guys!
[EVO 4G Android Development] maejrep:
Soon, hopefully... we can now at least start fixing sensors one at a time. I haven't been able to tackle any of that yet, trying to get it booting on rev3, but now that it is, we can certainly dive into that.

Anyone else who wants to start working on a sensor, fork off mine or toast's github repo, and have at it. Be sure to let everyone know your progress and what you're working on. I'm always in #htc-linux on freenode, and there are other people there too who can help, if you get stuck.

FWIW, IDA and pouring over the working disassembled stock kernel have been invaluable in this work, so if you have some ARM asm experience, that's a good way (probably *the* best way) to verify differences and make fixes.

But of course, knowing HTC, they'll release the source tomorrow, and I would have just wasted another month of my life with little gained :(
[EVO 4G Android Development] bobdude5:
:eek: does this include the touch screen lag where the input spot lags behind your finger when swiping?