yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] acrh2:
2 things remain to be fixed:

1) Tweak the camera for proper default exposure in daylight and better quality 720p recording.

2) Tweak the microphone input for better quality in recording and calls.

If you guys can do that, the phone will be perfect.
[EVO 4G Android Development] robl45:
no it aint, the camera doesn't work. thats half the phone.
[EVO 4G Android Development] acrh2:
Bah, I'll take screen tearing any day over choppy screen and touch lag.

But yes, better vsync is better.
[EVO 4G Android Development] bcnice20:
I think once the Droid x source is released we need to compare the displays and hdmi code maybe that will provide us with more insight on where the cap is screens aren't exactly the same but there similar
[EVO 4G Android Development] aaron130:
Is there anywhere to get the stock kernal in case you wanna go back to stock? Ive been looking but cant find it anywhere.
[EVO 4G Android Development] thenewguy821:
So, the only problem that remains with this kernel, is the screen tearing? Nothing "Breaks" with this? (Camera, Wifi, Bluetooth, etc.)

I am running Damage Control 3.2.3, with the Aloysious theme.

What is "Screen tearing"? Is there a video or screenshot somewhere, to see this, before I flash, so I can decide if it is something I am willing to deal with?
[EVO 4G Android Development] abiezer:
I am flashing this on Fresh 0.5.3 and am getting infinite boot loops. Have any idea why? I am using Amon RA.
[EVO 4G Android Development] tatnai:
+1, searching for a definition
[EVO 4G Android Development] p-slim:
can anybody confirm if this works with froyo roms or not? OP said he is unsure.
[EVO 4G Android Development] abiezer:
I've tried both versions and both result in a bootloop. Anyone having a similar problem? Running latest fresh.
[EVO 4G Android Development] fecht:
nice man!

Thanks!!!

fecht
[EVO 4G Android Development] Android Believer:
The FPS fix seems to be consistent, but while it's always there as far as FPS2d is concerned, you can flip through the 7 home screens and it feels like you have it applied for a few swipes. But after a few swipes, it seems to start the touch lag again and slows down when swiping. It seems you can resume the quickness by opening an app and then coming back to the home screen. But like before, it goes back to having the touch lag after a few seconds; almost like something in the kernel kicked into action, like a governor on the fps. The slow down also occurs in the app list as well.

I hate to criticize, especially considering the camera actually WORKS on the kernel, but another note is when you record video on the camera, the screen tearing appears in the video itself, even when watching what you had recorded you can see the tearing. I will say though, the tearing in this fix is definitely less noticable. In the very first one, it was pretty bad, and the camera didn't even work.
[EVO 4G Android Development] p-slim:
this kernal did not work on froyo avaV9. screen was unresponsive with 1st kernal. 2nd kernal unresponsive screen and no signal.
[EVO 4G Android Development] krazyflipj:
I can't reproduce it as well (It happened twice last night). Must of been a coincidence or something. FYI using with latest Fresh rom and works perfect. I will definitely keep my phone on this kernel. Thanks again for modifying this kernel for us Epson folks
[EVO 4G Android Development] abiezer:
You can find the stock kernel here:

http://outboundlink.us/anxo/dr_ta_1...ww.4shared.com/file/3Urm5V15/stockkernel.html
[EVO 4G Android Development] markus_del_marko:
so this kernel has an audio boost? can anybody confirm it makes a difference in sound? if so id like to see an update zip made of just that!

i have a nova hardware V3
[EVO 4G Android Development] kevincognito:
Manually setting T2

Edit: Nevermind... the frame rate is fine without switch.
[EVO 4G Android Development] :
Flashed Nonsense 1.5, flashed this kernel, and then the JIT file for Nonsense. This is balls to the walls fast. I'm getting a consistent 55fps average and an STDev of 3.89, and 12mflops in Linpack. Not bad at all. :)

~Jasecloud4
[EVO 4G Android Development] DomSim:
this fixed it for me too! getting 55fps with stdev around 4.1 with evo switch set to 361
[EVO 4G Android Development] paulg1981:
Kernel works great (Nova HW003) speedy and works well with BakedSnack .96

Does anybody else show that awake time = up time in battery info?

That is my only concern for battery life....we shall see I suppose :-)

Thanks for the hard work!

EARLY MORNING EDIT: Disregard battery comments I was checking while charging...brain fart my apologies :-)
[EVO 4G Android Development] Geniusdog254:
The actual speaker boost isn't that noticeable if it's even there, but the in call volume is MUCH louder as are headphones.

I don't know why my code doesn't change the actual speaker too, it should, but oh well. In call was it's main purpose

EDIT: Totally forgot the main reason i posted this lol, it requires a custom kernel since it is a kernel change. This is the best way to get it. Any custom kernel based off Toast's source will have it since he pulled my Github
[EVO 4G Android Development] Ceger:
For clarification, and since I don't want to run any such CPU setting software/widget... Does the undervolting/underclocking work automatically or do you need to run SetCPU or similar to get the CPU variances?

Also, to get HDMI working, couldn't you just use EVOSwitch to set the framerate back to stock temporarily?

Ceger
[EVO 4G Android Development] FluShot:
Post Stats...

Glad to hear everyone with novo's are averaging 50+ fps. Most of you are listing your setups but not telling us what # you are using for Switch? 365? 370? I am using DC 3.2.3. Running 0002 Nova. Please share with the community your stats that are netting you 56 fps. Great work btw!
[EVO 4G Android Development] Geniusdog254:
You shouldn't have to change the T2 values in Evo Switch with this kernel. That's the main draw to it, it just works
[EVO 4G Android Development] sracercelica:
Getting an average of of 50 fps with stdev of 4.17, getting average of a steady 49 on gears, and getting 15.782 mflops. AWESOME!

Using T2 setting of 410, with JIT on fresh 0.5

I just changed T2 to 411, not once did it hit the red. GEtting 50 fps with stdev of 3.77!!!!!!
[EVO 4G Android Development] Medic1013:
How are you guys measuring stdev? I've downloaded fps2d from the market and from pics posted up it looks just like fps2d is being used to measure this but I can't seem to find that option or program for that matter.

Sent from my Evo :)
[EVO 4G Android Development] djfasil:
Just run it and let it finish. It'll tell you when it's finished testing it.
[EVO 4G Android Development] thenewguy821:
When you run the fps2d program, after it is done testing, it gives you the average fps and the stdev, example... Done avg=52 stdev=12.94
[EVO 4G Android Development] FluShot:
Hm with no changes I only get 28 FPS. 425 T2 seems to work best for me, giving me 48 FPS with ~7 StdDv. Thanks anyway!
[EVO 4G Android Development] RickBaller:
So is this Kernel a no-go with Froyo ROMs?
[EVO 4G Android Development] Medic1013:
Gracias señor, I wasn't running it long enough and kept on touching the screen.

Sent from my Evo :)
[EVO 4G Android Development] AssassinsLament:
You guys shouldn't even have to use Evo Switch. Just wait till the device is done fully loading after booting and you should be seeing 54+ and 4-8 stdev. If after 10 minutes and you're not seeing 50+, then by all means use Evo Switch. But also don't forget to try cycling the screen on and off, although you shouldn't need to.

Good luck!

-

Also, if someone who has an HDMI cord, please try HDMI at default kernel (364 setting), HDMI shouldn't work. Then try using evo switch to set it back to stock (340 is htc/sprint stock) and test HDMI again, let us know if it works?
[EVO 4G Android Development] SteveDusa:
Just tested the latest built for DC roms.

With no Evo Switch used, avg=45 and stdev=13.97.

Hardware 0002 with Nova panel running on DC 3.2.3, after testing Evo Switch reported setting is 364.

---------------

After Evo Switch set to 400 resulted with avg = 49, stdev = 8.18.
[EVO 4G Android Development] protocol6v:
Best FPS fix. 54 avg FPS in gears on my Nova Evo.

Thank you so much!
[EVO 4G Android Development] warmthsound:
I apologize if this has been asked 100 times before, but any plans to support Froyo? I just can't go back to 2.1 after using 2.2 for some time.
[EVO 4G Android Development] HondaCop:
Just wanted to let you guys know that I've had the new 4.3 sbc colonel installed for the past few days and it's been running great. No issues whatsoever. Great job, net.

Sent via my EVO from the back seat of your Mommy's SUV.
[EVO 4G Android Development] squick:
We're doing nothing different than before changing kernels. All of a sudden this keeps happening. This is the third time. Kind of a coincidence to me. And I tried everything else to fix the card. When it came up scan and fix did that and it didn't work.
[EVO 4G Android Development] netarchy:
I never said they took a step back, I said I see no reason for myself to take a step back. The original HTC kernel sources for froyo used a 2.6.32.15 base, I updated the base myself to 2.6.32.27.
[EVO 4G Android Development] netarchy:
Hrmm, I'm hearing a number of reports of weird things happening with the SBC mod with some people. Try moving over to one of 4.3 builds without SBC.
[EVO 4G Android Development] squick:
I just really like what that kernel can do.
[EVO 4G Android Development] ejc1214:
I have tried a few different kernels and right now using netarchy-toastmod-4.3-cfs-nohavs-noUV-sbc-universal-signed to see if that would give me better battery life but it does not seem to be helping out much. Have I tried SBC havs nohavs and my battery monitor still shows from -106 to -610 in the history. How are you all getting positive numbers? I am wiping cache and delvik before flashing on hardware 3 running Mifroyo 4.2.

Negative numbers mean too much battery drain right?

Would I be better off with 4.1.9.1 and which version should I try?
[EVO 4G Android Development] brol1k:
I'm getting weird behaviour with the 4.3 SBC more havs kernel while phone is on the charger such as screen doesn't respond the way its supposed to.

Tapatalk'd on Evo
[EVO 4G Android Development] netarchy:
You realize of course that negative numbers simply mean the phone is running on the battery right?

Positive numbers = charging, negative numbers = running on battery.
[EVO 4G Android Development] BuddaBelly:
I went back to 4.2.2 for the same reason as everyone else. Battery life on 4.3 was terrible for me. I would

personally like to see a 4.2.2 bfs sbc no havs build. Doesn't hurt to ask right???

I'm using Calks 1.7.5 Rom with all the latest radios with 003 hardware on .76 hboot.
[EVO 4G Android Development] gpz1100:
BuddaBelly , 4.2.2 right?
[EVO 4G Android Development] BuddaBelly:
Yes 4.2.2. I changed my post to reflect that. I use the smart ass governor. My phone runs best on BFS but we didn't see one on 4.2.2 or I would be running it. On 4.3 it seemed as if I could watch the phone drain when using. It slept fine but when used just dropped.
[EVO 4G Android Development] ejc1214:
I do get positive numbers when charging but I thought that negative numbers were bad reading the other posts. Darn! I misunderstood the posts. Well, I was still coming off pretty fast off the 100% charge. I think this last one is doing better for me.
[EVO 4G Android Development] xHausx:
Mine does that too, especially when using swype. I think it is caused by the phone itself though, some of the older evos had screens that weren't grounded properly.
[EVO 4G Android Development] w84mike:
I've been running the new 4.3 cfs sbc havs more aggressive for a couple of days now and I am loving the way this thing works. Prior to this, my phone's favorite kernel was the 4.2.1 cfs havs more, but this new one has far surpassed that - phone runs smooth as silk and battery life has really been extended. This kernel is like Ben & Jerry's ice cream to my phone - it loves it!;)

Running this with Myn's newest beta and I'm really happy with this combo.

Thanks!
[EVO 4G Android Development] sgt. slaughter:
I have noticed a few times that even after setting the govenor in setcpu to conservative it gets changed back automatically to powersave and really bogs down the phone overall. On 4.3cfs-less. I had a profile checked but did NOT have profiles enabled so it shouldn't of triggered the profile checked anyway.

Unchecked it to see if it changes again.
[EVO 4G Android Development] dkdude36:
ok, i am having a problem and cant seem to fix it. my battery is messed up. it is powering off at 0% while there is still 3500 mV left in the battery. there are only 4200 mV total, so this is pretty huge drain. i have tried fully charging the bettery, letting it die, then trying to reboot until it couldnt any more (more than 50 times) and finally charging to full agian, but i am having the same problem. can anybody help? thanks

myns rls5 beta (12-30-10) and net's 4.3 cfs sbc more havs.
[EVO 4G Android Development] gpz1100:
I was still getting poor battery life with the netarchy-toastmod-4.3-cfs-havs-more-nosbc-universal (More Aggressive Undervolting) build. I installed cpuset and just set up one profile - for when the screen was off

min: 128

max: 245

scaling: conservative

priority: Still trying to figure out what this slider is actually setting? Anyone??

Anyways, 4-5 hrs testing has shown current consumption in the 40-60 mA range when the screen is off. Prior, there'd be times when it was also like this, but also many times when it's in the 200-300 mA range. Something tripping the cpu to a higher speed and not releasing.

I have background sync disabled, but mobile data always on. 3G enabled, and nothing else. I'm sure if I disable mobile data always on, it'll drop even more.

No issues turning the screen on. I do have the main setcpu speed set at 128-998 range with smartass scaler.
[EVO 4G Android Development] BuddaBelly:
I ran everything almost the same as you on 4.3 with the exception to the screen off profile. I ran it at 245/384 smart ass 100%. My phone just doesn't like the 128 and lags hard on wake up. Even with the profile set it still would tank the battery when I started using the phone which might not mean anything. Performance seemed good though.
[EVO 4G Android Development] netarchy:
The problem with smartass (and why it's not the default governor) is that it rapes battery life during active use, despite the excellent idle.
[EVO 4G Android Development] netarchy:
BFS builds are coming, I promise! I've just been a bit sidetracked (though if you take a look at my github you'll see I have been working on the bfs branches today ;D)
[EVO 4G Android Development] BuddaBelly:
I figured you were busy with the holiday. Hey I'm in no hurry. I noticed you stated that the smart ass governor was a battery hog. Would on demand perform better? I get zero lag when using smart ass but conservative I always seem to get screen lag.
[EVO 4G Android Development] gpz1100:
Net, thanks for the clarification.

Since i'm only using setcpu for the idle/screen off profile, would setting the main setcpu to conservative be the same as using your 4.3 conservative parameters then?

Btw, can you enlighten what the priority slider affects in the setcpu profiles section?
[EVO 4G Android Development] netarchy:
I seem to do pretty well with conservative using

Sampling: 50000

Up Threshold: 50

Down Threshold: 30

Ignore Nice: 0

Freq Step: 20

Ondemand is a bit of a battery hog as well.

Eventually I'll have a chance to really tweak the hell out of smartass. I'm fairly sure it can be made to behave better.
[EVO 4G Android Development] stricklerjosh:
Anyone suggest a kernel for mikfroyo with the new 004 hardware so it wont break my camera. I want a stable kernel with good battery life. Running the stock kernel now.

Thanks!

mikfroyo evo, with a side of aloysius 5 !
[EVO 4G Android Development] BuddaBelly:
Thanks and I will be sure to give that a try.
[EVO 4G Android Development] bmark34:
I had the same issue when flashing the newest radios while on 3.30...downgrade the pri and your awake issue will be gone...hope this helps

- from my battery sucking vampire Evo
[EVO 4G Android Development] brol1k:
Yes especially with swype, so your saying the newer evos don't have this issue?

Tapatalk'd on Evo
[EVO 4G Android Development] netarchy:
BFS builds of 4.3 posted, knock yourselves out.
[EVO 4G Android Development] parousia15:
Net,

Now that HTC has finally released the source code, does that mean the long teased 5.0 kernel can be completed? Or was that held up/abandoned for other reasons?
[EVO 4G Android Development] bkrodgers:
Net,

Is the Bluetooth stack part of the kernel package, or is it something else? I ask because I'd really like to see the bitpool for A2DP increased to something that will sound OK. I know CM has it fixed, but nobody's done it on a sense rom yet. I believe someone asked myn, and he was under the impression it was a kernel thing. Have you ever looked into this?

-Brian
[EVO 4G Android Development] netarchy:
It's separate from the kernel. The sources have been released, though I haven't had much of a chance to go through it and see if I can do anything with it yet.
[EVO 4G Android Development] gpz1100:
Hey, if you do anything with the BT, maybe add a HID profile too. I got a wonderful BT keyboard that's recognizable, but fails when pairing.
[EVO 4G Android Development] flooberz:
Anybody try the static undervolting kernel?

I'm thinkin of switchin over from a HAVs more aggressive, just to get a more consistent battery life, just cuz that battery drop during use is noticable with the HAVS
[EVO 4G Android Development] mroneeyedboh:
How do you use your phone mostly? for me I browse the web and text. So there doesnt seem to be much use for a capped voltage to a certain CPU speed. Id like the HAVS to take over and give the CPU less juice to get the same task done...

I made a guide on kernels, link is in my sig.
[EVO 4G Android Development] gpz1100:
mroneeyedboh, if the phone is not used for anything involving heavy cpu, maybe it makes sense to cap it at 1/2 or 3/4 the max cpu freq as well? Assuming of course this doesn't impact normal functions such as voice or data/web browsing. In the PC world, we try to OC to get the most out of the cpu... here we're trying to get by with the least to conserve battery.
[EVO 4G Android Development] mwielgosz:
The only downside to this may be that by underclocking the cpu, it may take longer/more cpu cycles to complete the action...therefore causing more or equal battery drain than the originally settings caused. The thread on sbc by ms had a post on this (I believe by ms himself)

Evolved into a higher form of communication
[EVO 4G Android Development] netarchy:
That's not quite how static undervolting works.

Every speed that the cpu can hit has a specific voltage setting in the speed table. Static Undervolting uses lower values for each of those voltage settings. The cpu is still getting less juice to get the task done.

So quite literally, you're undervolting all the time.

HAVS is more flexible in that it can use a range of values for each speed. It isn't necessarily always lower than the static voltage setting, it *can* go higher if necessary.
[EVO 4G Android Development] frifox:
16 different builds for v4.3, are you serious? dude, you got to tone down on this fragmentation, K.I.S.S, lol... trying to please everyone usually doesnt work out in the long run ;)
[EVO 4G Android Development] netarchy:
4 variations: 2 schedulers (cfs/bfs), 2 options for battery charging (SBC/NoSBC)

Then 3 versions of undervolting (static, havs-less/more) and a failsafe with no undervolting.

Technically not that fragmented. ;D

Strictly speaking you make 2 major choices: BFS/CFS and SBC/NOSBC

Then you figure out what level of undervolting (or no undervolting) your phone can handle, and use that.

;D
[EVO 4G Android Development] jelive:
Excellent explanation...maybe put in 1st post right behind "To clear up some confusion that is apparently being spread around, build 4.3 does in fact work on all current evo models, not just the newest model." Still doubt many would read tho :D

Jim
[EVO 4G Android Development] sgt. slaughter:
Still dont understand why? Anyone thats flashing should know how changlogs work and know clearly stated it has updated mroe drivers to work on newer cameras too, which would be ontop of all the other stuff already in the older kernels change log.
[EVO 4G Android Development] sgt. slaughter:
Kinda lost as to why HTC is using .17 as there base in the latest OTA still though as you mentioned earlier....

I take it instead of taking HTC's source and putting in your tweaks, you are now taking your kernel and sifting through HTC's source and just pulling the updates to push into yours. Assuming there less updates/changes in there kernel than tweaks made by you already in turn meaning it takes u less time to port the changes rather than incorporating your own tweaks ontop of there source.

j/w what would cause you to build off there base in the future? Will it take them pushing out a 2.3 gingerbread kernel or no?
[EVO 4G Android Development] Brandito:
so is it a smart idea to use setcpu with havs? i was reading to the contrary in another thread, but i see a lot of guys using both here.

i like having setcpu use profiles to lower my max clockspeed when the screen is off, or to get max speed all the time when it's plugged in. i was just concerned it actually wouldn't help battery life at all.
[EVO 4G Android Development] gingson:
Netarchy, I was using Fresh 3.5(using mikFroyo 4.2 right now) with netarchy 4.3 with the less agressive u/v and I was having boot issues and I was having network connection issues. My 3G connection was intermittent. Was 4.3 incompatible with Fresh 3.5? I believe some guys in this thread had the same issues.

Can you recommend a kernel for MikFroyo 4.2?

HW 0004

Hboot 2.10

software 3.70.561
[EVO 4G Android Development] jelive:
Agree, but unfortunately just look at all the posts that clearly show how many people do not bother to READ...and then blame the ROM, kernel, etc. for all their problems.

Jim
[EVO 4G Android Development] sgt. slaughter:
How could SetCPU cause problems with a Havs Kernel???

I've been running SetCPU with HAVS Kernels since the devs started pushing them out and had zero issues whatsoever.

I have however gotten away from using the profiles in SetCPU and typically stick with the conservative govenor. Will deff move back to Smartass once Net tweaks it more though.
[EVO 4G Android Development] Brandito:
that's what i was asking for. if you haven't ever used the kernel without setcpu, how do you know setcpu isn't having an adverse effect?

i realize that at its core setcpu really just adjusts max and minimum frequencies and governor. i'd still like someone more qualified than myself to give their stance. the kernel dev would seem like the best person.
[EVO 4G Android Development] gadean:
HAVS adjusts the voltage. SetCPU adjusts the clock speed (or governor, if you will) and governor type (smartass, performance, conservative (my favorite), etc)

This has been answered many times before.
[EVO 4G Android Development] sgt. slaughter:
I've not once read that HAVS kernels are bad to use with SetCPU. The only debate that was out which kinda makes sense to an extent is the usage of profiles with them. Example you when the batter is getting lower you force the cpu to run at lower clock speeds but with havs voltages you likely will have the cpu run harder to get the task done. Better to just use screen off profile and thats it if your going to use them at all.

Theres no way SetCPU has adverse effects on HAVS kernels if your just changing the default min/max clock speeds and the govenor used.
[EVO 4G Android Development] ejc1214:
I think I found the kernel that my phone likes! netarchy-toastmod-4.3-bfs-havs-less-sbc-universal (Less Aggressive Undervolting). Phone on for about 3 hours and just down 6%! Never had that happen before. Everything works as far as I can tell. Thanks.