yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] MrDSL:
Haha the camera thing is so old..

Before I run my fps test I do set my setcpu to performance and I always get better results..especially in the stdev

Wifi seems to be working fine for me also on evo v9

I don't have a wifi network to connect to but it turns on fine and scans fine.
[EVO 4G Android Development] justinisyoung:
I made a different approach with the 3.6.4 kernel by adding the WiFi modules in too... but it still didn't work for me. I might need to justv reflash v9 anyways though...

But could either of you guys pull the contents in /system/lib/modules and put them in a zip file for me?
[EVO 4G Android Development] gammons:
Attempted to flash on top of a newly-flashed EVOlution v9, and got the following error:

E:Missing file:

system/xbin/12ping

E:Verification failed

Installation aborted.

Is there something I'm doing wrong? Thanks!
[EVO 4G Android Development] MrDSL:
Confirmed wifi works fine for me.. Well done :)
[EVO 4G Android Development] justinisyoung:
are you using clockworkmod recovery? it doesn't work on the Amon_RA recovery image.
[EVO 4G Android Development] scooter185:
yea, that's the error Amon RAs recovery shoots at you. I'd try it with CW but it doesn't want to flash from ROM manager :( i'll try again at home.
[EVO 4G Android Development] ao7996:
I was running 3.5 while on joeykrim's 1.0.8 ROM, switched to Ava's V9, flashed clockworkmod and flashed 3.6.4... 5 point multi-touch, 54fps and wifi all work... thanks OP!
[EVO 4G Android Development] MrDSL:
Is it safe for me to post those files on here? I mean they don't like have my wifi info right? lol I really wouldn't know..
[EVO 4G Android Development] justinisyoung:
i can guarantee that it won't have your wifi info. in fact, you can't even edit or hardly read those modules... try opening them in gedit(on linux) or notepad++/wordpad on windows. you get a whole bunch of random symbols lol.

but yeah it's totally safe posting them here :)
[EVO 4G Android Development] MrDSL:
here you go..
[EVO 4G Android Development] YACO:
this is exactly what i was looking for... hopefully it works.

-YACO
[EVO 4G Android Development] scooter185:
Wifi works, average FPS: 52 stdev: 7.14

and 5 touch points :D

Thanks a ton Justin, I was getting sad about not being able to run netarchys kernel with Avas 2.2 Sense rom.
[EVO 4G Android Development] Arrogant49:
i flash evolution v9 and it's all good. but when i try to flash a netarchy 3.6.4 i lose all touch screen responsiveness. is there something i'm missing? i've tried to search the forums and i can't find it. the kernel that i'm using before 3.6.4 froyo is 3.6.4 dc version. any help would be appreciated because i really want to try this rom at a decent fps. thanks!
[EVO 4G Android Development] justinisyoung:
...flash the kernel in the first post. this one enables the touchscreen for froyo.
[EVO 4G Android Development] Arrogant49:
i did... i'm using clockwork recovery. i def read the post and am using 3.6.4 froyo kernel. it works fine when i use the damage control 3.6.4. kernel but the fps is hitting 30 fps. when i flash 3.6.4 froyo using clockwork recovery i either get no touchscreen or stuck at htc evo 4g white screen. excuse my noobness lol but i'm not sure what i'm doing wrong. i appreciate your help very much!
[EVO 4G Android Development] justinisyoung:
ok, i'm assuming you want froyo with the fps fix, so here's just a quick step by step:

1. boot into clockworkmod recovery

2. wipe data/cache

3. flash EVOlutionv9, or a different ROM, as long as it's froyo. i recommend evolution, however.

4. flash netarchy-3.6.4-froyo.zip right after flashing EVOlution v9

5. you should be able to boot into froyo and everything should work
[EVO 4G Android Development] Arrogant49:
i'm still failing... i'll try the entire process using ra recovery perhaps this will work
[EVO 4G Android Development] justinisyoung:
Amon ra will definitely not work... but your explanation isn't making sense... I think you're flashing the wrong kernel if you lose touch response....
[EVO 4G Android Development] Arrogant49:
thanks for your help but i can't get it to work with 3.6.4 froyo i lose touch screen everytime no matter what
[EVO 4G Android Development] SteelH:
Thats the broadcom wifi driver.
[EVO 4G Android Development] Arrogant49:
here are my exact steps...

1. flashing evolutionv9(everything responds, getting 30 fps)

2. flashing the kernel from post 1(3.6.4)

3. no touch response
[EVO 4G Android Development] jabbawalkee:
I just did the same thing on EvolutionV9 and it worked perfectly fine for me...fast and smooth as hell, touch was fine. You must be doing something incorrectly - are you flashing the wrong kernel maybe from the other netarchy thread!?
[EVO 4G Android Development] blankd3ckskat3r:
Wow, got an average of 54 fps, and 43 mflops on linpack using froyo sense. Thanks OP!
[EVO 4G Android Development] Arrogant49:
thanks for your help guys but it just wont work. EVERYTIME i flash the kernel from post 1 i lose touchscreen... i really appreaciate the help tho
[EVO 4G Android Development] kwajr:
Maybe I'm stupid but where's the link

Sent from my Evo on on the Now network from Sprint

oh and duck Apple
[EVO 4G Android Development] Arrogant49:
so i got ffolkes 5.1.1 to work, it seems that every kernel but 3.6.4 froyo will work for my phone lol... it's all good tho, great ROM!!! and again thanks for all of the help guys
[EVO 4G Android Development] kdbrown5:
Absolutely perfect!!!

Running on avalaunch's evolution x2.

5 inputs w/ dotty, 54 avg fps stdev 6.58 with setcpu to 1.07 ghz. maxing out setcpu always crashes adw launcher and can send me into boot loops forcing me to do a rom reflash/nandroid flash

Thank you for your work OP!

edit: also wifi working when flashing over stock kernel!
[EVO 4G Android Development] VanillaIcee:
This works great on Ava-FroyoV1-Sense. Averaging 52FPS and mflops in the low 40s.
[EVO 4G Android Development] Rudementry:
Why do we have to have to use clockworkmod recovery? I can never get it to work, every time I try to flash it with ROM manager it always gives me an error, I've tried everything.
[EVO 4G Android Development] sjwaste:
Do cameras work with this kernel on Froyo?
[EVO 4G Android Development] troyboytn:
Clockwork is not required. I use Ra Recovery and never have any problems. I also delete Rom Manager from every rom that I use in which it is included.....way too buggy.
[EVO 4G Android Development] finsmaniac02:
I am on Ava-froyo v1 and when I flash this i don't have any touch response either. Using the OC Kernel that ava posted works but I lose wifi. Using clockwork recovery and full wipe everything. Any ideas?
[EVO 4G Android Development] Arrogant49:
the only kernel i can get to work with this is OC5.1.1 or netarchy 3.6.4 dc version... i can't get any of the newer kernels that allow you to break 50fps to work... i keep losing touchscreen also... what rom are you flashing from? maybe that has something to do with it.
[EVO 4G Android Development] finsmaniac02:
Coming from newest DC. Does the 3.6.4 dc version let u break 30 fps and keep wifi?
[EVO 4G Android Development] jayv1717:
i didn't use clockworkmod and it worked just fine
[EVO 4G Android Development] Arrogant49:
nope i can't break 30 fps, the only way i can is if i flash the OC5.1.1 kernel
[EVO 4G Android Development] finsmaniac02:
Can you keep wifi with the oc kernel?
[EVO 4G Android Development] Arrogant49:
yeah, my wifi works with that kernel. everything performs well. i get around 45 fps on average using the OC kernel
[EVO 4G Android Development] justinisyoung:
wifi on this kernel should work now, i added in the modules when i compiled the kernel for 3.6.4.

I think for those of you on ava-froyo can use netarchy's original kernel, because ava-froyo is not AOSP. this kernel only works with AOSP roms, i'll update the first post for that.
[EVO 4G Android Development] scooter185:
for the record, i'm using Ava's sense-froyo and your latest kernel works perfect.

Nova screen / 003
[EVO 4G Android Development] thekjlal:
Thank you for putting this together.
[EVO 4G Android Development] Harfainx:
Awesome. I'm using V9 from Ava and most everything works beautifully.

WiFi works just fine. Awesome work :D
[EVO 4G Android Development] Tyzing:
I was hoping this would fix the wireless tether problem (seems a lot of roms are getting problems)

but no :( I'm using Ava's Froyo Sense
[EVO 4G Android Development] justinisyoung:
wi-fi tether should work, as should wifi in general. try rebooting and reinstalling the app.

okay, so i did not know that it worked with ava-froyo sense ROMs. well apparently i was wrong. i re-edited the front post.
[EVO 4G Android Development] dglowe343:
I'm on the latest DC and the kernel works great for me. I avg 55 fps. Everything works. JIT greatly improves performance, but adds some instabilities. Do you have the latest radio and software?
[EVO 4G Android Development] Rudementry:
When I try to flash over ava X9 I get the error "E:Missing file: system/xbin/12ping E:Verification failed". I've redownloaded the file several times and I still get the same error. Whats up?
[EVO 4G Android Development] justinisyoung:
Amon_RA or clockworkmod?
[EVO 4G Android Development] Rudementry:
Amon_RA. I was told I could use it and didn't need clockworkmod.
[EVO 4G Android Development] kaokollaa:
finaly yaaayy!!!! now im gettin the whole potential of my evo i get 55fps on non epson screen thanks

just one more thing !!! we all need the camera fixx!!!! on 2.2 lol
[EVO 4G Android Development] spiicytuna:
Any chance of getting a 2.2. kernel compiles from the latest (3.7.1) netarchy release?
[EVO 4G Android Development] justinisyoung:
i don't have the time tonight, but i promise i'll have one by the end of tomorrow! sorry guys :((
[EVO 4G Android Development] spiicytuna:
No rush. Thanks whenever you can get to it!
[EVO 4G Android Development] halorin:
I'm getting some screen tearing using this with cyanogenmod.
[EVO 4G Android Development] justinisyoung:
honestly, with the new nightly cyanogenmod builds, there's not much more need for this kernel except for those who use Ava-Froyo sense ROMs. in fact, the CM nightlies already have the kernels for unlocked fps in them, so you'll get the 55-ish frames per second average and camera and hdmi and most other stuff.

but i'll keep updating this for those on ava-froyo and whoever else may want to use this.
[EVO 4G Android Development] seventyfive:
Flashed over Ava Froyo-V1 and it works perfectly!! Didn't even clear the cache. I have a 5-point screen.

Thanks!!!!
[EVO 4G Android Development] whoamanwtf:
I know you have already worked on getting it going at all and I thank yo ufor that but if you could make it signed. So that I can flash it with RA instead of clockwork ever since clockwork corrupted my memstick I have had a sour taste in my mouth for it and do not want to use it.
[EVO 4G Android Development] markus_del_marko:
did you expect anything less from xda?
[EVO 4G Android Development] justinisyoung:
yeah, i'll be sure to sign any new releases so that amon_ra can use it also. I'm surprised that the way this updates the kernel even works with amon_ra's kernel though :confused:
[EVO 4G Android Development] justpastfinish:
But I'm on the CM rom and although I'm getting ~50 FPS...the screen isn't as fast and smooth as I'd like. Not sure if he has implemented this as his kernel or what.

Sent from my HTC EVO
[EVO 4G Android Development] justinisyoung:
i updated the first post with the 3.7.1 kernel, still based off netarchy's kernel. I haven't been able to test it yet, but it *should* work.

please report back and tell me whether or not it works. it is signed so Amon_RA might work :)
[EVO 4G Android Development] rjmjr69:
this is 3.7.1a correct?
[EVO 4G Android Development] Tilde88:
justin fantastic work!

just thought i would inform you that there is now a 3.7.2a build with a wifi + 4g fix. just sayin :D:D
[EVO 4G Android Development] Fallen Spartan:
Glad to see a thick skinned OP not taking the bait from some idiots.

As for these idiots who flame and post rude comments. Any further and you'll receive a short vacation from XDA

If you have nothing of importance to say, best to say nothing at all ;)
[EVO 4G Android Development] Tilde88:
:( does not work with CyanogedMod froyo :(

android.acore and a bunch of other necessary bgp components FC + FC cycleon boot... Leaving it unusable... All you get is FC......

And with the regular 2.1 build of 3.7.2a nothin works lool
[EVO 4G Android Development] justinisyoung:
i don't think this kernel should be used with Cyanogen's froyo ROM guys. that one already has unlocked fps and camera working.

this kernel would be more for those using the froyo Sense ROM. i'll update to 3.7.2a later tonight.
[EVO 4G Android Development] mrmomoman:
I have tried this with avalaunch's v1 froyo with sense and it renders.the touch screen useless. Not responding to any touch. I have searched i promise :) some say they have done it and it works but i can't. More of curiosity now if it is.something.that i am missing.
[EVO 4G Android Development] netarchy:
That'd be because the cyanogenmod kernel already includes all the fixes from my kernel releases (in regards to unlocked fps), plus the various fixes and tweaks they've made for it to work with their aosp froyo.
[EVO 4G Android Development] Calkulin:
Hey Justin, when you update it to .3, can you please add this to the init.rc so I can run scripts from the init.d folder

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
[EVO 4G Android Development] Android 17:
Thanks for the work Justin. I feel a little bad that as soon as you update it, netarchy releases another update for his XD.

Great work though!
[EVO 4G Android Development] justinisyoung:
to tell the truth, i haven't been able to create a working boot.img from combining a ramdisk and kernel zImage. i followed the guide that cyanogen linked to on his wiki, and i've tried to combine them so many times in so many ways, but it never ends up working. my phone just stays at the white evo screen and there's never a thing in the log.

that's why i went with Koush's kernel updater. He made it a lot simpler because you only have to drag and drop the compiled kernel zimage into the zip file and it flashes that without altering the ramdisk. if you can get this working, that'd be awesome.

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

anyways, the 3.7.3c updated kernel should be posted within a few seconds from now. enjoy and please report back problems. :)
[EVO 4G Android Development] Android 17:
I just flashed the latest kernel and it made my touch screen completely unresponsive, nova screen, using Ava's EvolutionX2 rom.
[EVO 4G Android Development] justinisyoung:
I'm sorry, I haven't been able to test these cause of time constraints. I've been so busy lately. I'll try again tomorrow and see if/where I went wrong. Sorry for the troubles.
[EVO 4G Android Development] Android 17:
It's no problem, I'm just glad someone is taking the time to update the kernels for 2.2 :)

From what I've read, it seems CM produces somewhere between 40-50 fps atm, but I can get a steady 54 fps, about 5.50 stdev using the original kernel here, so this seem the best choice for now.
[EVO 4G Android Development] MrDSL:
All I know is that whatever fps hack is included with cm makes my screen jacked as far as having ghost touches. I can make it a little better using evolution switch but can't make it go away..

I was kinda hoping cm would first start without the fps hack since it isn't even finished yet but that doesn't seem to be the case..

I guess some of us are simply going to be screwed because not all our evo screens even the same Soviet don't see how this is going to work for everyone..

Something experimental should be added after the rom like these mods are not built into the kernel to cause more problems..

I guess ill have to wait for some other froyo rom.

Obviously I know cyanogen rom isn't done yet but the developmental fps hack is obviously being included.
[EVO 4G Android Development] AssassinsLament:
And you know that this is caused by the fps hack?
[EVO 4G Android Development] netarchy:
It would seem to me that it's more speculation. There are a lot of things being tweaked/worked on in cm, and the various issues that crop up are exactly why cm is still in nightly testing builds as opposed to an official "stable" release. If it were solely the fault of the fps fix, then the issue would theoretically also pop up in every kernel that uses the fps fixes used in my releases. As they do not all exhibit this same behavior, it's not really possible to conclude that the fps fix is the cause of said issues.
[EVO 4G Android Development] MrDSL:
I know its the fps hack because if I run say evolution v9 which doesn't have the fps hack my screen is fine and has been all day.

As soon as I flash this zip guess what? The ghost screen touches happen immediately. Wouldn't you come to the same conclusion?

Obviously I can't run cm without the hack but if I install evo switch and start messing with it I can instantly make the ghost screen start happening by changing the value.

I've been running these fps hacks since they came out. I know other users have experienced this also.

Having said all that you guys really don't think its the fps hack? Seriously?
[EVO 4G Android Development] MrDSL:
I can make this issue happen on evolution v9 simply by installing the fps hack attached to the first post.

I can make it go away by removing it. Isn't that enough proof?

If cm is going for stability then why include and experimental hack that can cause screen problems.

Why not skip it and then let users flash a zip and test it like in this very topic?

Just asking that's all.
[EVO 4G Android Development] AssassinsLament:
So then shouldn't this be happening to everybody? 100% of the time?

When you flash a kernel, it's not "just" the fps hack, there's plenty of other tweaks involved in the kernel and ramdisk. CPU tweaks, cache tweaks, etc. So to isolate it as the fps hack being involved is a bit of a rush to judgement. I'm not trying to defend it because it's partly my hack, but I am defending it because I don't have these symptoms. And I would assume we would see everyone bringing it up if it were the kernel/hack. Also, since I did the Novatek hack, I know that the fps hack itself is nothing more than 1) removing a sleep when vsync is called and 2) setting the default T2 to 380, instead of 340. There is absolutely no code other than those. I can not say much of the other tweaks that may be in the kernel, but as for the novatek panel tweaks, that's the extent of it. Basically if you set your T2 back to 340, you have stock (other than re-adding the 3ms sleep).
[EVO 4G Android Development] MrDSL:
You know LCD screens better than I so I wont argue knowledge there but aren't all LCD somewhat different in the sense of frequencies etc? Do they all react exactly the same? I mean they all don't even have the same LCD so is it that far of a stretch that some users may have problems with the frequencies or whatever being changed?

Now If I run a older fps hack like 3.6.4 I don't have the problem. The newer ones I do..I suppose you're right I could be rushing to a conclusion but it sure seems like it to me.

I guess I'm truely surprised you feel every single LCD screen in the evo should react the same way.

I was under the impression one of the main reasons evo switch was done was so we could make adjustments since users were always having different results.

I did tell you I can use evo switch to make it worse and better just not completely gone right?
[EVO 4G Android Development] AssassinsLament:
Well, of course there are slight differences between LCD's but not by much. Right now, there seems to be two different versions of clocks on the Novatek Panels. The majority react the same way mine does with my preferred settings, there is a small majority that needs those settings upped about 6 units above my preferred settings to get the same results. That's why we had to adjust a good average for both variations. There is no evidence that this fps hack doesn't work for everyone, if it's not working, there is some other issue such as rom/cache/etc. Most of it can be fixed by setting the cpu performance.

Now, for the Novatek panels, of course it's not an exact science, kind of like overclocking a cpu, some settings work for a user, it may not be the same for a different user. There are many variables as to why it works for some and not for others at a particular setting, including the actual hardware, kernel, ramdisk, rom, radio, etc. But they should all work the same, maybe just at different settings. With that being said, again, there should be no way the frequency of an lcd screen should be able to move your cursor and click buttons (there is nothing in the code telling it to do that). It has to be some code some where else. Could it be a lagged response to your own movements? Could be but I doubt it because you'd see the whole phone boggle down and be unresponsive during that time. I can't say for any apps you're running, if any. But I'd look at those too, because something has to be telling your phone to be clicking buttons.

Now the only difference between 3.6.4 and 3.7+ is that in 3.6.4, we put the lcd interface on dma channel p (primary). That works best as we can reach up to 57fps. But HDMI is using dma channel p, and it breaks hdmi. And since we'd rather have everything working and lose 2-3fps than to be at 55-57fps and not have working hdmi, we changed back the interface back to dma channel s (secondary). So we changed the default from 370 to 380. That's all that was changed, nothing else, atleast as far as the Novatek hack goes. Other things in the kernel, I don't know.
[EVO 4G Android Development] MrDSL:
I will do some more searching and testing and see what I can come up with..
[EVO 4G Android Development] AssassinsLament:
I ran CM6 second build from last night for a few hours, and didn't notice anything different. So I'm not sure what it could be other than some other software that's running. But, let me know if you find something.
[EVO 4G Android Development] MrDSL:
I have last nights build also and the only apps I have installed is gapps and root explorer.

It still happens but I can make it go away by turning the screen off and on a couple times.

So I've eliminated any of my apps doing it. Not sure what else to do.

It figures the one rom I actually want to run will give me problems :(
[EVO 4G Android Development] H1Vltg3:
Can someone please make the 3.7.5 update for froyo, specifically Ava-FroYoV2-RC? This sure would be appreciated to have FPS and GPU updates.
[EVO 4G Android Development] sracercelica:
+1 on this :)
[EVO 4G Android Development] xominous:
+1 on this again, since Ava released the official 2.2 rom.
[EVO 4G Android Development] djfasil:
using this with ava-froyoV3 broke the rear camera. everything else is working fine.
[EVO 4G Android Development] blakeboys:
dang!! i flashed this kernel earlier today and never used my camera. Just noticed its doesnt work. just a green scrambled screen. now we need a fix for this...
[EVO 4G Android Development] justinisyoung:
i'll try and get a 3.7.5 kernel out by later tonight... but since 2.2 is now pretty much official, this thread will probably be discontinued since netarchy is probably gonna make a froyo version on his thread. remember- this is all his kernel, with just a minor change to make it work with froyo.

anyways, can somebody try installing his 3.7.5 kernel on ava-froyo-v3 and tell me if touchscreen and all work?
[EVO 4G Android Development] mherald81:
Touchscreen doesn't work.
[EVO 4G Android Development] zone23:
Novatek

0003

AVA-FroyoV3

tested

3.6.4

3.7.1

3.7.3c

Touchscreen doesn't work at all so you can't unlock the phone. If I pull down nothing happens, the screen is unresponsive. I have to pull the battery and use recovery. Thanks
[EVO 4G Android Development] djfasil:
just reflash ava-froyoV3 over it, it'll go back to the stock kernel and fix the camera issue.