yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] jabbawalkee:
I'll DEFINITELY test it as well - email is mkaswell1@gmail.com let me know :)
[EVO 4G Android Development] timgt:
I will test for sure!!!
[EVO 4G Android Development] antiphon:
Sign me up!
[EVO 4G Android Development] kpkimmel:
Hit me with the test ffolks
[EVO 4G Android Development] warmthsound:
Not that you don't already have enough people willing to test, but if you need another, shoot me an email warmthsound@gmail.com

Thanks for all the hard work.
[EVO 4G Android Development] kpkimmel:
Low fps on test kernel anywhere from 28 to 37
[EVO 4G Android Development] justinisyoung:
i'm fairly sure this is because froyo isn't based on the 2.6.29 linux kernel. it's based off of the 2.6.32(?) or 34 kernel, i can't remember the number off the top of my head. obviously, there's differences between these kernels. toastcfh is working on forward porting our kernel to .34, however, so if he manages to get that done then we'll get camera by then. i'm actually quite amazed how well froyo is working on 2.6.29, i remember how badly 2.1 on the hero ran when it was on the 2.6.27 kernel. :P
[EVO 4G Android Development] jblazea50:
i will gladly test out the new experiment kernel

Justinisyoung, i believe froyo is based on .32 kernel (at least that was the kernel on my N1 when i installed the leaked froyo); i'm assuming camera won't work until it gets forward ported to at least .32 kernel
[EVO 4G Android Development] halorin:
Trying the test kernel. The camera works, which is great. Fps2d yielded an average of only 38.

In regular use, this is not as smooth as the last public release in other applications.
[EVO 4G Android Development] jabbawalkee:
Someone want to send me the test kernel please. I'd love to provide some feedback (mkaswell1@gmail.com). Thanks dudes
[EVO 4G Android Development] DomSim:
changing anything in setcpu reboots the phone for me as well. flashed kernal over fresh .3
[EVO 4G Android Development] codeman05:
Your the first I've heard with that problem on this kernel.

Does reverting back to the stock kernel fix it? If not, it may be your ROM or another issue.
[EVO 4G Android Development] codeman05:
Have you tried a smaller overclock? IE: 1100MHz?

My phone can't handle 1.2GHz with the supplied voltage, yours may not either. If I put SetCPU up to 1150 (or less), it works fine.

As with all cpu's, they are all different and will require different voltages to overclock to certain speeds.
[EVO 4G Android Development] c0mputerp0et:
003 w/ Nova DC 3.2.x w/ this new kernel. Excellent! sucks to the cam! I say. This thing is flying around. The real test is screen swype to another screen is SO much smoother. Also Google Earth pretty much moves around noticeably faster as well. KUDO's to the devs!
[EVO 4G Android Development] EtherealRemnant:
It only reboots on me if I try to set it higher than 1190 and the benches at 1190... wow if only we could get this going on froyo.
[EVO 4G Android Development] jayv1717:
Same here..1190 seems to be the sweet spot..for now anywayz
[EVO 4G Android Development] :
Yeah 1150 works for me, I just don't know how to over volt it. I read there was a tool somewhere... not sure.

Or a terminal command would be sufficient if anyone knows.
[EVO 4G Android Development] antiphon:
Yes, reverting to stock does stop the problem. I've had this problem on all 3 kernels and across different ROMs. I even tried switching flashing methods (Clockworkmod and Amon RA) but it didn't help. It might be a hardware issue, but there are a couple of people who have had similar problems after trying these kernels. It's really frustrating because this is the only thing that is preventing me from using it as a daily kernel.
[EVO 4G Android Development] Jykinturah:
I have this issue as well, for those who are wondering. I noted it before, but no one responded, so I didn't think anyone else had it.

It is a relief to know that it isn't just me.

I cannot use toast's kernel or derivatives thereof without getting this problem.

Hardware Rev 002.
[EVO 4G Android Development] shadowhawk2020:
I know this is a noob question, and if it should be in another thread I will delete it. But can someone point me to instructions on how to go back to stock after installing this? I want to mess with it, but I like having the cameras. Is it as simple as restoring a NAND backup? Or is there something else I need to download.
[EVO 4G Android Development] redsolar:
Works great on Rev 003 with Novatech, excellent work there
[EVO 4G Android Development] MILH0U5E:
Same here... I had it to, then did a Nandroid and the problem went away... Had to use my Hero battery to do the Nandroid cause I was so low.
[EVO 4G Android Development] Jykinturah:
You can restore NAND or flash the stock kernel, attached.
[EVO 4G Android Development] shadowhawk2020:
Seems easy enough... Cant wait to play.
[EVO 4G Android Development] regulator207:
Sorry but had to say that you guys are doing a great job. I've been glued to the screen and have been hammering xda for the past 3 days. I hit f5 about every 15 mins or so when i'm near my comp or on my phone. haha.

anyways i cant believe how much more responsive and "snappy" the phone becomes with just a 10fps boost! just wow.

If you were like me and were on the fence about flashing a custom kernel, then dont be afraid. The results are fantastic.
[EVO 4G Android Development] antiphon:
Can you clarify when you say you did a nandroid. Did you backup after you had installed the kernel then restored it again or did you restore a previous backup and reinstall the kernel again? I tried restoring from a fresh backup and reinstalling the kernel but that didn't help me.
[EVO 4G Android Development] roghaj:
That stock kernel doesn't work for me (the one posted a few posts back).

The test kernel seem to work very well. The screen seems more sensitive. The framerate displays as 50, but doesn't look like 50fps to me. Still has micro stutters.

-Roger
[EVO 4G Android Development] Tikerz:
This also happened to me on the original T2 kernel from Friday.
[EVO 4G Android Development] daneurysm:
It looks pretty 50fps to my naked eye, FWTW ;)

I especially notice stutters in video. I'd imagine that has a lot to do with the refresh rate not being easily divisible by 30. It's very smooth for a second or two then for a split second it stutters, which to me looks like it's 'catching up' to the actual clock after spitting everything out too fast.
[EVO 4G Android Development] Siberian_Khatru:
I also have this problem. When I plug phone in it initially charges and then, after about 5 seconds, it stops charging as if I disconnected the USB cable.

Rant:HTC is so irritating. There is no way this 30fps limit is accidental. If it isn't accidental we have to ask what was HTC's intent when creating this limit. Clearly the hardware is capable of 60fps. Clearly most customers want 60fps.
[EVO 4G Android Development] Geniusdog254:
@ffolkes

Forgive me if I've had a complete mental lapse and missed something obvious here... but where is your source?

I'd really like to see the source to incorporate it into my personal kernel I'm working on.

Don't make me play the card we played with HTC and remind you that you're legally required to release it :p

Lol thanks for all the work you've put into this man.

Regards
[EVO 4G Android Development] Android 17:
Does the new eclair or froyo kernel fix the video playback problems?
[EVO 4G Android Development] JordanClay2003:
This new one produces some tearing for me. In the very same spot every time. About 75% down the screen same line every time.
[EVO 4G Android Development] eduardmc:
I tried the v5 version 2.1. But i onky get 24fps. Pretty choppy and slow compare to stock speed version. V4. 2. Was running at 50fps. 0002 novatek
[EVO 4G Android Development] jblazea50:
experience the same screen tearing about the same place every time (about an inch from the bottom of the screen)

edit: setting the value to 437 (i'm on eclair) is great; get about 45fps with 4-6 std; wish the screen tearing wasn't occurring though
[EVO 4G Android Development] kpowr82:
Wow. By far the best kernel I've used. Baked snack v9 and this kernel rock.
[EVO 4G Android Development] kpkimmel:
Some st here to but ill take it over 30 fps cap
[EVO 4G Android Development] ttieder:
So I'm running the latest damage control with new radio if I use this kernel my WiFi will break ?
[EVO 4G Android Development] sniggle:
First time flashing any of these kernels and so far so good. Noticeable improvement in smoothness. stdev is all over the place in fps2d but that's to be expected and in practice doesn't really have much of an effect on the overall experience.

Thanks!
[EVO 4G Android Development] gman8966:
Kernel v5 seems pretty good, I'm getting 40-42 fps. nice to have camera working.
[EVO 4G Android Development] liquidkernel:
Great work! Since I have DamageControl's latest ROM, WiFi and 4G stopped working.. but Sense and games are CRAZY smooth. Scrolling through menus (like the all apps list) is still jerky, but it's getting there.

Great work!
[EVO 4G Android Development] kpkimmel:
I just nandroid back to damage 3.2.1 and all works great
[EVO 4G Android Development] antiphon:
Does your Wifi and 4G work after applying the V5 kernel? I installed BS V9 and everything worked fine, but as soon as I apply the V5 it breaks Wifi and 4G.
[EVO 4G Android Development] kpkimmel:
Nice work ffolkes...we just have to get wifi, 4g working and this screen tear issue worked out...nice though...shoot me a pm when your next beta kernal is ready
[EVO 4G Android Development] apollooff320:
Works good for me and my WiFi works. Don't see tearing like others see. Swiping between screens is smooth even at 40fps.
[EVO 4G Android Development] jblazea50:
I am on dc323 and have wifi working, not sure about 4g. I flashed the kernel, then flashed the wifi for the new ota and the 4g fix by trevE. Those does can be found in either the dc thread or another over I can't recall and can't really upload the files since I'm doing this from the phone.
[EVO 4G Android Development] jmxp69:
ffolkes,

1.47 stock, v5, 002/nova, t2=437, SetCPU 1.075/128 (I can go higher in SetCPU but don't see a point in it).

437 seems to work the best for me as well with ~ 45fps in gears, 44/12.43 in fps2d. Cameras work, charging/charging led works. I had to downgrade wireless to G which is waaaaay ok with me.

You're doing great work here man. You just made the EVO what it SHOULD have been out of the gate.

Thank you!
[EVO 4G Android Development] sherman901:
So much smoother! Works great but like everyone else I have no wifi. I'm running dc 3.2.2.1
[EVO 4G Android Development] sniggle:
Not totally sure but it seems that the battery is draining very quickly compared to the stock kernel. I am down by 30% after just a couple hours with little use when it would normAlly have gone down maybe 5%.

sent from an evo via tapatalk
[EVO 4G Android Development] kpowr82:
Man, just noticed WiFi wasn't working this morning :(

I'm sure that will get fixed soon enough. Not a deal breaker for me at the moment. Haven't tested 4G cause it's not available here, but judging by what others are saying you're not alone.
[EVO 4G Android Development] jblazea50:
I'm on DC3.2.3 with the V5 kernel and I have Wifi working, but not 4G.

You can flash the wifi update zip from the 1st post. That's what I did and wifi is working without any issues.
[EVO 4G Android Development] ffolkes:
i'll finally be forking this from toast's new kernel once i get some things worked out, like the tearing problem.

wifi and 4g WILL work with this kernel, but you need to have a stock rom (or more specifically, stock files in your /system/lib/modules directory). for people who have failed wifi, this is most likely because you're running a rom that has the new files from the ota update. in which case you can flash the stock wifi zip in the OP to make wifi work with this. although that will only fix wifi, the 4g .ko isn't included in that yet.
[EVO 4G Android Development] acrh2:
Perhaps you could add the necessary files to your kernel release.
[EVO 4G Android Development] ffolkes:
OP has been updated with a zip containing wifi and 4G that will work.
[EVO 4G Android Development] jblazea50:
ffolkes, thanks for the updated zip with wifi and 4g; seems to be working (not really in good 4g area to test)
[EVO 4G Android Development] KERKEDAGAIN:
May I say, with extreme delight, that this kernel is now fully functional. 4g, camera, n WiFi all work PERFECTLY! outstanding work!
[EVO 4G Android Development] kpowr82:
+1 Thanks ffolkes!
[EVO 4G Android Development] sniggle:
Follow up to my post last night - I forgot that the 4g widget tries to enable 4g on every boot. That's what was causing the extreme battery drain.
[EVO 4G Android Development] acrh2:
Since toast is busy combing through the entire source of the kernel, squishing bugs and optimizing,

could you guys please compile one for the epson panels with the fix?

Pretty please.
[EVO 4G Android Development] rldev:
God I hate to drop such noob question even though I am not. I flashed this kernel and have set cpu. I have no overclocking and undervolting options available to me. My min cpu freq is 245, not 128 or lower. What am I missing? Is there something I need to perform after flashing the kernel?
[EVO 4G Android Development] ortizdupri:
Using Fresh's latest 0.5.3, set screen frequency to 250 (for some reason, the 432/437 mentioned earlier only gives me around 24-28fps on fps2d), getting results of 41-44fps with an stdev of around 7.7 on fps2d. Great work here.

(plus, having a working camera, wifi, and 4g is immensely awesome.)
[EVO 4G Android Development] super-6-1:
so this works with 2.1? and is it stable?
[EVO 4G Android Development] jabbawalkee:
@FFOLKES: will you be posting the new version publicly today or are you keeping it private beta for a while? I tried getting you to send me the beta (mkaswell1@gmail.com) but no luck. I'd love to test it out and this kernel makes my Evo perfect :-) thanks
[EVO 4G Android Development] kpkimmel:
Flash and find out
[EVO 4G Android Development] jblazea50:
he posted the update.zip on page 38; it is v5; you'll need to download the wifi n/4g fix from 1st post to make wifi and 4g work
[EVO 4G Android Development] nonpointtruth:
EDIT: Nevermind my last post.. Haha.. So 4g and wifi work with the newest v5, or do we still have to flash the fix? Which one would work for the newest DC 3.2.3? It's running the new OTA update, so.. Wow, I sounded kinda n00bish there..
[EVO 4G Android Development] jblazea50:
here is v5 for those are can't just go back few pages to look for it; to get Wifi-n and 4G to work, you must download and flash the proper file from post #1
[EVO 4G Android Development] jayjay7411:
Hey I flashed V5 over .5.3 and my camera doesn't work that's odd. Any suggestions??
[EVO 4G Android Development] nonpointtruth:
Okay, so which wifi/4g fix do I need to use if I'm running DC 3.2.3 with the new OTA?
[EVO 4G Android Development] jblazea50:
1st post by OP
[EVO 4G Android Development] luisrcastillo:
Great work ffolkes and everyone working on this! Your efforts are appreciated.

On another note, the WiFi fix for the OTA does not work. I flashed it over V5 and it doesn't work.
[EVO 4G Android Development] Shinzul:
So I flashed this kernel to check it out, and it seems that I can only get up to 40 FPS max at a frequency of 500. The default of 400 only gets me 23 FPS, it's odd. I'm running OMJ's rom, does not have the OTA update.

Also, I have excessive screen tearing in the middle of the screen horizontally.
[EVO 4G Android Development] tyrnight:
Im running Baked Snack V9 with the OTA and I installed the v5 of this hack and this is the first time I've been able to run it past 2 minutes after booting.. it works great.. Im at 250 getting 43fps and OC'ed to 1152000 Using SetCPU app. Oh and Camera Works Fine..

I also installed the Wi-fi/4g fix.. and the wi-fi works.. I don't have 4g yet..

been stable for an hour now.. Ill post more info on battery as I go on about my day..
[EVO 4G Android Development] Shinzul:
How do I overclock my CPU easily?
[EVO 4G Android Development] eduardmc:
Im using bugless v3. And wifi, 4g works. But the cap is mow set to 41fps. I would like to have the cap at 50 it was much smoother.
[EVO 4G Android Development] ortizdupri:
I honestly have no idea. The only "aftermarket" (as it were) stuff I have installed on my phone are as follows:

- Fresh .5.3

- JIT compiler

- Amon-Ra Recovery

That's it. No OTA updates (past the initial SD card fix) or anything like that. I have no problem taking pictures with the regular camera app, Vignette, FXCamera, or Google Goggles.
[EVO 4G Android Development] jayjay7411:
Nevermind a reboot fixes it awesome!!!!!!!!!!! Heck yeah over clock with camera sweet
[EVO 4G Android Development] jblazea50:
those having issues with lower fps, you guys should try setting the T2 value to 437; that's probably the best; i get 45fps with 4-5 std

of course the tearing is present on this kernel, which is the only negative; but, i'm sure it'll be rectified soon enough
[EVO 4G Android Development] rldev:
So strange. I have 002 Evo. The higher the refresh rate the less FPS I get. The lower, the higher the FPS. 250 is as low as I can go and it yields 42fps. Why so different?
[EVO 4G Android Development] oOflyeyesOo:
So, with the release of the kernal, could alot of these problems be fixed now? Meaning the camera, mms n such.
[EVO 4G Android Development] acrh2:
No love for the epson owners here?
[EVO 4G Android Development] Jykinturah:
Just be patient a little. The HTC source is different from toast's original source, so all the changes are different. Devs are working to figure everything out. The cap will get removed eventually for all panels.

I've been reading through the code, too. I am next to useless though because I am reading the code simply to learn the syntax, not to change it.

Don't pressure the devs too much, they are working really hard and it is pretty selfless despite their request for donations, and sometimes it is a rather thankless task when people just post up their problems and disapprovals.
[EVO 4G Android Development] ffolkes:
this new version sets the t2 to 537 by default, and changes the fte location to fix the tearing. if you liked the results you had in v5.0, set the t2 to 250.

v5.1 - elcair
[EVO 4G Android Development] ffolkes:
it's because i don't have an epson panel to test on. but there's one thing i could try.
[EVO 4G Android Development] Philosuffer:
What was the t2 set to in kernel t2_v2? I was getting a pretty constant 50fps without any tearing on that kernel. Anyone know?
[EVO 4G Android Development] timgt:
250 still works best for me, at 537 I am getting around 37fps with tearing.

1. Why is it the higher we set this number the MORE tearing we get (I get 0 tearing at 250 and get 41fps)

2. How come we could get 50fps on the previous kernels but this won't get that high anymore?

3. If the source is out shouldn't we be finding the real cause of the problem? I thought this was just a hack until the source was released?
[EVO 4G Android Development] timgt:
It was set at 400 but that doesnt work with these new kernels.
[EVO 4G Android Development] ffolkes:
not sure why you're still getting tearing. :/ can you do this and tell me what it says?

cat /sys/devices/platform/mddi_c_b9f6_5582.1/fte

1 & 2. no one really knows exactly why...the rational, scientific equations don't seem to apply to the lcd timing, even though they should. kind of like when you scratch that spot on a dog, and it starts twitching lol. something must be different with the official kernel that's made that spot move slightly.

3. the makeshift kernel source still suffered from this problem too, and we weren't able to find it. not even the supergeniuses like toast and maejrep can track down the ultimate cause. there may be an underlying hardware cause for it, but even so, there is likely a way to counter it with software.
[EVO 4G Android Development] kpkimmel:
Im capping at 40 fps with the last two kernals...ffolkes i think u need a break...,and we should look for the source of the cap instead
[EVO 4G Android Development] Krandor311:
If you want a test dummy for Epson fixes I can offer up my 0003
[EVO 4G Android Development] luisrcastillo:
The new version got me less FPS and more screen tearing. I set mine back to 246 and average 42 and almost no screen tearing. Great job!
[EVO 4G Android Development] Shinzul:
Tried v5.1 and my data connection stopped working. Also, I got way more stdev than v5.0 running at 437. 437 at 5.0 gave me 45 FPS with ~5 stdev and no tearing.
[EVO 4G Android Development] timgt:
you sure its cat /sys/devices/platform/mddi_c_b9f6_5582.1/fte you want me to type? when I type that in adb shell I get no such file or directory

EDIT: by the way I manually changed it to 537 in V5, thats why I am getting tearing
[EVO 4G Android Development] jblazea50:
thanks for the update; yeah the tearing is gone; that's awesome;

when i tried 250, i get about 37fps with 3-5std; i tried 437 and i get similar results as from v5 (45fps 4-6std) so i'm going to stick with t2 set at 437

Edit: minor tearing at 437 (can see it while using camera); it's about 1/5 of an inch at the bottom of the screen; other T2 settings (below 437) doesn't result in tearing
[EVO 4G Android Development] super-6-1:
I dont see mire then 2 pointer multi touch on my. Evo but other then that this is awesome
[EVO 4G Android Development] ffolkes:
i checked, that's it. are you sure you're booted? this can't be done from recovery. alternatively, you can just do:

./adb shell cat /sys/devices/platform/mddi_c_b9f6_5582.1/fte

(without the ./ for windows)
[EVO 4G Android Development] ffolkes:
that's because your hardware doesn't seem to support it, so it reverts back to 2. if you want, in a bit i'll make you a kernel to see if the new source has helped this issue any for those that are affected (you).
[EVO 4G Android Development] ffolkes:
for those seeing tearing, where is it happening? the "old" place was about 1" up from the bottom. do you still see it there? or higher?
[EVO 4G Android Development] luisrcastillo:
When using the default 537, I saw it about 1.5 to 1.8 inches from the top of the screen.
[EVO 4G Android Development] super-6-1:
Sounds good to me. Pm. Me the new kernal to test and illl test it. Im installing 5.1 now and tearing? That means what
[EVO 4G Android Development] KERKEDAGAIN:
only 2 points here, as well...will defly try a test kernel
[EVO 4G Android Development] timgt:
ffolkes, just to clarify. I am not getting tearing on v5.1 anymore. I was manually setting the T2 to 537 in V5 and was getting tearing in gears for android.

That said, I am still getting smoother gears animation when set to 250 with xda switch. I hope this helps some

FTE: d35, 0x0023h is what that cat output shows you wanted to see with 5.1
[EVO 4G Android Development] ffolkes:
for those having problems with tearing on 5.1, try this if you're handy with shell.

** do this with the display on. changes are immediate. **

step 1.

--------

./adb shell cat /sys/devices/platform/mddi_c_b9f6_5582.1/fte

it should say d35.

step 2.

--------

./adb shell echo 45 > /sys/devices/platform/mddi_c_b9f6_5582.1/fte

verify if you'd like, by doing step 1 again to make sure the change was applied.

scroll something and see if the tearline has moved. repeat with different values until it's gone.
[EVO 4G Android Development] ffolkes:
oh okay, i think i misunderstood you then. how is battery life at 250?
[EVO 4G Android Development] timgt:
can't really comment on the battery life, seems normal to me. I don't see any extra drain over anything else I've ever run on here.