yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Dan330:
That was my understanding too.

I am 100% sure .. My phone is version 003.

Checked it out in 2 locations on the phone.

here is one: menu>settings>about phone>hardware info>

so.. if my 003 camera should work... then what am i messing?

my phone is almost perfect.. but this one issue!
[EVO 4G Android Development] flipper12:
I can confirm that my camera doesn't work with Netarchy's kernel either... and I have hardware version 003. Apparently, some 0003 version phones (the ones shipped out later) utilize the same new camera chip as the 004 versions so there are a handful of us that are in the same boat.
[EVO 4G Android Development] Dan330:
interesting ...

my phone was built in Oct 2010

I did not get the phone till last week in the mail.. shipped from sprint.
[EVO 4G Android Development] ageesm:
Yea, I remember reading that, just slipped my mind. Like I said it seems we are stuck until HTC releases the source. Everytime I switch and use a kernel and get used to some extra features, speed and battery life, I realize I need the camera for something. Good thing is I am on HTC #17 and it is still a really great kernel, haven't gotten around to checking out the #15 from the OTA, but have heard pretty good things too.
[EVO 4G Android Development] darkreign2049:
I believe that the 003 hardware with hboot 2.02 have the same camera as the 004. I'm not sure what the difference is between these versions, but I know they have the new camera.
[EVO 4G Android Development] ageesm:
I got my phone the end of Oct from a Sprint store, build date says 10/28/10. The switch obviously happened sometime in there, but clearly the new camera was implemented before the new hardware ID of 004. Interesting.
[EVO 4G Android Development] Rekna:
I can also confirm the same camera problems with HW 0003.
[EVO 4G Android Development] st0921:
For those who have problems with camera, which rom versions are you guys using?

I have HW0003, hboot 2.10 running EViO 1.7.1 with Net's 4.2.2 No Havs, no problem at all with camera...
[EVO 4G Android Development] Rekna:
I am using Azreal's 3.0. hboot is 2.02
[EVO 4G Android Development] darkreign2049:
The only one I have gotten the camera to work with is the HTC #17. I have tried multiple, I can't remember all of them off the top of my head.
[EVO 4G Android Development] flipper12:
I'm using Rick's TURBO Stock ROM, 3.70 version. It came with HTC's Stock #15.

I only discovered the camera issue when I tried flashing ms79723's 'Superior Battery Charging Kernel' http://xdaforums.com/showthread.php?t=876590, which is based on Netarchy's kernel.

I've tried every version of it, and have cleared cache, Dalvik cache and clearing data for all camera apps, but the camera still refuses to function when flashing Netarchy's kernel.
[EVO 4G Android Development] st0921:
I've never played with SBC modded kernel (but very tempting) as it seems like there are various user experiences based on what I read from that thread. Also Net mentioned that he's keeping his eye on it, so when he determines it's ready, he'll eventually add the mod in the future releases.

Maybe you can download other camera app from the market and try that? If a market camera app works, then the problem is with the stock camera apk. You can then re-install the stock camera apk...
[EVO 4G Android Development] flipper12:
Tried quite a few camera apps - Camera Zoom FX, Vignette, and PRO Zoom Camera - all with the same results. Unfortunately, it appears that it has to do with the camera chip itself.
[EVO 4G Android Development] darkreign2049:
I've come to the conclusion that we will have to wait for the source to be released before we can use anything but a stock kernel.
[EVO 4G Android Development] Dan330:
i posted my experimentation ..

My phone is 003 with HBoot.202, and is rooted. Running Sprint-Lover ROM.

I tried the following kernels with no success.

4.2.2 CFS havs more universal

4.2.2 cfs nohavs universal

4.2.1 cfs bfg have smartass universal

4.1.9.1 cfs havs universal

as you can see.. I tried that kernel too....

Maybe I have to wipe everything...

Reflash the SprintLover ROM from scratch on to a clean phone... and then flash that kernel...
[EVO 4G Android Development] Dan330:
Have you confirmed..

Flashing an updated ROM with sprint's kernel.. (ex: Sprint Lover)

will bring the Camera back??
[EVO 4G Android Development] Biggest Fro:
I cant get the download links for the universal downloads to work, any fix?
[EVO 4G Android Development] darkreign2049:
Yes, I was running MYN's ROM and tried a few different ROMS. Each time the camera would stop working. Once I flashed the HTC #17 the camera would start working again. I am currently running Virus Airbourne and used a couple of Netarchy kernels and the SBC kernel with the same outcome. Every time when I flash the HTC #17 kernel the camera works again.
[EVO 4G Android Development] flipper12:
The 003 and 004 EVOs with the new camera chips apparently also work with the most recent stock HTC #15 kernel that just came out with the last software update (3.70).
[EVO 4G Android Development] Mark_in_Tulsa:
Well you may first have to start her off on 1 or 2 fingers and then work your way up to 5. You don't want any tearing.
[EVO 4G Android Development] stevcha:
I have HW0004 and haven't had any camera issues while running nets kernels.
[EVO 4G Android Development] SSaxman:
Nice

Swyped from my HTC EVO 4G with Myn's Warm TwoPointTwo
[EVO 4G Android Development] flipper12:
Based on some rumors, the HTC source codes for the kernels will be released soon... (but I wouldn't hold my breath).

http://xdaforums.com/showthread.php?t=885082
[EVO 4G Android Development] mildlydisturbed:
Sprintlovers 12/16 I could flash any of the kernels no problem (used 4.1.9.? cfs, 4.2.2 cfs, 4.2.2 bfs more and less)

Sprintlovers 12/20-21 I can't flash any of them. Have asked over there if anyone successfully installed it on 12-21.

Seem to either have no-boot, instability, or no SD card access. Have re-re-flashed the phone a few times now.
[EVO 4G Android Development] smallba:
Here You Go
[EVO 4G Android Development] ro2themax:
4.1.7

does anybody have the old 4.1.7 kernels? please post if you do. thanks
[EVO 4G Android Development] Swede2008:
Are there going to be bfs versions for 4.2.2? I tried all of net's kernels (4.1.9.1,4.2.1,4.2.2/cfs, bfs/more,less,no havs) and got the best battery from 4.2.1 bfs, especially the no havs. I would love to try a 4.2.2 version of it. :-)

Sent from my HTC Evo! :-D
[EVO 4G Android Development] xlGmanlx:
I remember net saying life was pretty hectic and that he didn't have the time to put into the Kernel right now, could be wrong
[EVO 4G Android Development] xlGmanlx:
NET, not sure if you have seen this but this looks interesting

linky
[EVO 4G Android Development] dcharleyultra:
SBC-net-4.1.9.1-more-havs-v7

I am running SBC-net-4.1.9.1-more-havs-v7 and have no issues. I am about to try a 4.2.2-based SBC kernel.

Are you overclocking?

My ROM is Sprint Lovers 12/20 - patched to 12/21. (I am also using setCPU 2.1.0.)
[EVO 4G Android Development] Swede2008:
Oh hah! Fair enough :-D

Sent from my HTC Evo! :-D
[EVO 4G Android Development] mildlydisturbed:
nope, turned setcpu to normal, turned to not set on boot.

most flashes of the rom just lock up on SL 12/21. When I can boot the SD card does not work. Tried most of the roms, all of which worked on 12/16 version and none of them worked properly.

I originally flashed his pc36img file and then re-flashed the upgrade later as I was locked up without a functioning kernel.

HW 003, no overclocking, cleaned dalvik and caches.

Evidently I'm not the only one with problems, but it lookslike it;s about 3 of us at the moment
[EVO 4G Android Development] dcharleyultra:
Are you clearing both caches before flashing the kernels?

Swyped from my Evo 4G using Tapatalk
[EVO 4G Android Development] xlGmanlx:
I always do
[EVO 4G Android Development] emeraldayotte:
I'm having problems with my Up Time equaling my Awake Time.

I flashed Caulk's format all zip since I'm using clockwork recovery and wasn't sure if my dalvik cache was being wiped correctly. I formatted all data and installed a clean ROM/4.1.9CFS-noHAVS kernel.

I also tried 4.2.1CFS-more-aggressive and the problems continue. I upgraded all my radios recently too.

Prior to the clean install, I checked spare parts for the partial wake and removed the top 2 offenders (Tango and TIKL) just to make sure. Now the top offender is the Android system

Help
[EVO 4G Android Development] mildlydisturbed:
I am, locks up since SL 12/21...

Cleaning dalvik with titanium backup, other with cachemate (which I assume does it correctly but I;m quite willing to believe I am doing something wrong if it is working for other people)
[EVO 4G Android Development] xlGmanlx:
Usual prescription is check spare parts awake time and system panel for the culprit as your experience seems somewhat isolated
[EVO 4G Android Development] emeraldayotte:
I edited my post prior to seeing your reply. My top spare parts offender is Android system now but haven't installed system panel.

I'll give that a shot.
[EVO 4G Android Development] xlGmanlx:
Could be an app, sometimes wiping caches again works
[EVO 4G Android Development] stylz3:
you got it work with fresh 1.0.1. I tried it and got stuck in a boot loop. What did you do and wha t kind of setup you got?
[EVO 4G Android Development] Djghost454:
the revert back to 3 point multitouch was for compatibility, there are 2 different versions of the touch sensor, one will read 5, the other, only 3. If you enable 5 on one of the phones that only support 3 you lose all screen response.
[EVO 4G Android Development] ao7996:
I've been running 3.5 for a day or so and have been really happy with it.

After tweaking my setcpu settings per netarchy's advice I'm running smooth, no stutter, nothing is broken AND I'm lucky enough to have 5 point multitouch (I love the novelty of it when dinking around with dotty... I'm just not sure how much value it have for me moving forward)

Thanks again netarchy for all your work man.
[EVO 4G Android Development] Rudementry:
3.6.1 seemed to work better than 3.6.2 for me, and I don't understand the need for a different kernel for the DC ROM. All of the kernels work fine with DC for me.
[EVO 4G Android Development] gman8966:
I'm running latest version of DC and using the regular, non DC version of the kernel and it runs for me fine as well.
[EVO 4G Android Development] st0921:
Stdev = Standard Deviation, basically it represents the degree of deviation from the normal range of FPS' as a result of sample testing. As you can see when you run the testing, the ball begins to move and the app starts getting the FPS data. You sometimes get 40 FPS or 70 FPS, but the FPS at the end of the test that you see is the average of all the FPS records during the test period. For stdev, easiest way to explain is, if you get 0, that means the FPS was always the average during the test time (which is almost impossible practically), if you get 10 , that means the FPS ranged from (for example) 35 to 65, so the lower stdev means the less outliers, which is the better than the higher stdev. You can lower the stdev by setting the CPU frequency higher than stock or setting it as performance instead of on-demand.

I'm not running DC, but it looks like there were some bugs (4g and wifi) that the OP fixed through this version specifically relating to the DC rom.
[EVO 4G Android Development] surferpr:
im using DC 3.2.3 and had to use 3.6.2b and nova switch. Other than that its working great! Every thing is working. Im netting 50fps! :)
[EVO 4G Android Development] DomSim:
hw 002 nova screen

fresh 1.0.1

radio 2.05.00.06.10

this kernal just makes my phone lag like crazy. tried the regular 3.6.2 and the dc

tried changing settings with evo switch to 365, 370 and 400. averaging lik 15-25 fps

setcpu is being used as well.

any ideas?
[EVO 4G Android Development] thenewguy821:
Thanks st0921, that really made it understandable...

as for the question about what differences would I see between 3.3 and 3.6.2b, I should have been a little more direct. I understand the 3.6.2b has specific fixes for DC users, I was more concerned with what differences are there between 3.3 and 3.6.2. Is it more for the ability to adjust the CPU freq? Does this really make a noticeable difference in performance, or is it more of a "I know it can be better" feature?
[EVO 4G Android Development] sd2649:
Hmmm.. This breaks my cameras fir some reason. If I reboot, camera works for a few seconds and then just closes. From then on, when I try to start the camera app, it just flashes the camera screen for a second and then goes back to the home screen. Any suggestions? It has done this with the last 3 kernels I downloaded from this thread.
[EVO 4G Android Development] st0921:
I've used all the test kernel versions, but I don't know details of the change logs. However, the CPU frequency range has been consistent. I think Netarchy changed the voltage setting in 3.5 (not exactly sure), and most changes were related to FPS, not the CPU frequency. But I can tell you based on my observance that 3.6 runs much more smoothly than 3.3.
[EVO 4G Android Development] sd2649:
Double tap to zoom stopped working too.... Weird
[EVO 4G Android Development] CyberRat:
Running DamageControl 3.2.3 with the Revision 3.6.2b Kernel and I had to use the EVO switch and set it to 400 to get 50 FPS.
[EVO 4G Android Development] sd2649:
Oops! Fixed it, the camera and screen responsiveness issues went away once I unplugged the phone... So it works, as long as its not plugged in. tearing on the screen is bad though.
[EVO 4G Android Development] Akulamenuri:
Im getting 55 FPS, man this is great. Just sent you a donation, keep up the good work :D (0002, Nova)
[EVO 4G Android Development] omegatyrant:
I don't know, this kernel doesn't feel as smooth as the previous nova kernel.

A weird problem I ran into (Running the latest DC and the DC kernel on post 1) is after receiving a text message, my lock screen disappeared. I had to pull the battery. Works so far right now.
[EVO 4G Android Development] acrh2:
Standard deviation can be easily understood in terms of confidence intervals.

You are confident that 68% of all tested values will fall in the range from (average - stdev) to (average + stdev). Or you can say the value is (average +- stdev) for 68% of all values.

95% confidence interval => (average +- 2 x stdev)

99.7% confidence interval=> (average +- 3 x stdev)
[EVO 4G Android Development] oreoOozZz:
Im on an 003 with a novatek, baked snack v9.6, 54fps constant. Camera works fine, everything seems to be working except overclock. no matter what setting i put it on it wont scale higher then 1113mhz and sometimes it gets stuck at 128mhz and lagggs up bad. anybody else havin this problem? trying to fix but nothing seems to be working and i can usually iron out a problem quick...

Edit: Anything over 1152000mhz as max and it wont scale, its like it goes into some kind of safe mode and locks at 128/128, lags horribly and wont budge.
[EVO 4G Android Development] :
This is running great on my 0.5.3. fresh rom. Hardware ver. 002. None of the other fixes have worked up until this point. Now I am hitting 55 fps. Everything seems much more fluid and smooth. Thanks a lot.
[EVO 4G Android Development] djfasil:
Using 3.6.2b

- DamageControl 3.2.3

- Novatek 002

- SetCPU 128/1152

- avg=56 stdev=5.21
[EVO 4G Android Development] emeraldayotte:
So far wiping cache hasn't worked. Working on the system monitor route.
[EVO 4G Android Development] emeraldayotte:
Well I'm even more confused with my Up Time = Wake Time issue. Spare Parts shows my top offender as being the Android System. System panel shows the Android internal system process as using the most CPU time.

Tango showed up as 2nd but uninstalling it isn't helping any other ideas.
[EVO 4G Android Development] mildlydisturbed:
Yay, got sprintlovers to work again

hrmm, got 4.2.1 bfs less to work with Sprintlovers finally by flashing SL and then flashing it before restoring my apps via titanium. Lost the sense for a bit, one reboot later and I'm back.

So, ignore any complaints I've posted - I've got some app that wants to hate on this kernel and I don't know what it is.
[EVO 4G Android Development] dcharleyultra:
I clean my caches from within Recovery (Amon _RA 1.8). Can you do it from within your Recovery?

Swyped from my Evo 4G using Tapatalk
[EVO 4G Android Development] mmfn520:
I put warm two point two on my friends evo anf used the recomended 4.2.1 smartass kernal and now when scrolling there is a noticeable line through the screen can see it well in the launcher as well as home screen. Anyone else seeing this and any thoughts maybe his phone doeant like the kernal?
[EVO 4G Android Development] Swede2008:
I'm using 4.2.2 with Ziggy's tweaks for screen off which I have set at 128 min and 245 max with the conservative gov. I noticed some lag when a phone call comes in, so, would it be better to increase the max to ~345 (cant remember the exact freq) or leave the max at 245 but switch to the smartass gov? Better as in for battery life w/o the lag, heh.
[EVO 4G Android Development] :
the min is whats giving you the lag - try to increase it to 245
[EVO 4G Android Development] Swede2008:
Really? Hmm ok :-)
[EVO 4G Android Development] :
whats your issue ?? are you having 100% up time and wake time . are they dead even ?
[EVO 4G Android Development] tprime76:
Same thing here... Seems like the 128 is just too slow. Made min and max on previous ROM set to 245 and everything wakes up nicely.
[EVO 4G Android Development] emeraldayotte:
I am having 100% up and wake time. I've tried the following:

Clean install of Caulk's ROM

Clean install of 4.2.1 kernel

Factory wipe, clear caches and reinstall both ROM and kernel

Tried different kernels (Ziggy's, 4.2.1-CFS-More aggressive, 4.1.9-CFS-noHAVS)

Factory wipe, clear caches and reinstall without Titanium restore

Removed top offenders using Spare Parts battery history as a reference

Installed System Monitor and removed top offenders (Tango)

I'm still having the same problem and when I review Spare Parts or System Monitor, the Android system is now the top offender.

Not sure what's causing the problem. I did install all of the new radios provided by Caulk as well.
[EVO 4G Android Development] xlGmanlx:
weird, try installing it with no apps and then slowing installing apps
[EVO 4G Android Development] sir_death:
Are you currently charging your phone when checking your uptime/wake time? I thought i was having the same issue till i checked with my phone unpluged.
[EVO 4G Android Development] :
also make sure your installing the rom - let it boot up - then when installing the kernel - wipe cache and dalvik - then install kernel and let it boot up. then reboot again just to make sure

1 app i like is the startup cleaner- makes reboots fast and no instant battery drain when loading up all the background apps
[EVO 4G Android Development] emeraldayotte:
My phone is unplugged when I'm checking.

I'll give this a shot next
[EVO 4G Android Development] emeraldayotte:
Well after a little playing, I installed warm 2pt2 with the exact same setup and the issue is resolved.

I'm guessing there is something running in the background of caulk's ROM that I couldn't find.

I'll ask in his thread....thanks everyone of helping.
[EVO 4G Android Development] netarchy:
I spy with my little eye... some updated kernel sources released by HTC...
[EVO 4G Android Development] datajosh:
I'm guessing it just went up, you're the first person besides myself that I've seen post about it :) I can't wait until some of the new stuff they've done makes it into this kernel!
[EVO 4G Android Development] mwielgosz:
What version of the source did they release?

Evolved into a higher form of communication
[EVO 4G Android Development] Beejis:
Love it!

10 char
[EVO 4G Android Development] d0cx:
New source code released based on latest ota. Go netarchy!
[EVO 4G Android Development] ageesm:
I have been waiting for this since I got my EVO in November. I loved some of the kernels I used, but always ended up needing the camera. Can't wait...:D
[EVO 4G Android Development] Dan330:
yes.. i have been waiting too...

I want to use your awesome kernel.. but dont want to loose my camera.

Please please..
[EVO 4G Android Development] danman132x:
So I'm using this kernal...

netarchy-toastmod-4.1.9.1-cfs-havs-universally compatible (Aggressive undervolting)*

I'm still pretty new to messing with Kernals, but I went ahead and flashed this kernal with my FreshROM 3.4.0.1 (not updating to lastest version as this one is working flawlessly for me)

Does it automatically lower voltage in the background? I don't have any cpu adjusting programs running. I'm guessing this kernal is better than stock, and I see nothing but mostly good reviews on it. So far I tested all my apps, and everything is working fine. Camera closed once the first time I turned it on, but no problems since. I don't see why people say they are having camera problems, unless I'm missing something. I'm also assuming that I will experience better battery life with this kernal, but it's my first day with it so I can't say anything yet. With stock kernal on Fresh 3.4, I used to get about 14-15 hrs of life with moderate usage.
[EVO 4G Android Development] ageesm:
It isn't problems. 0004 and late model 0003 EVOs contain a newer camera chip and because HTC hadn't released the source the drivers weren't present in any kernel besides stock. They released the source today so we are anxiously awaiting kernel updates everywhere. You must have the older camera chip which works just fine.
[EVO 4G Android Development] netarchy:
New build posted: 4.3

Notes for Revision 4.3

- Camera drivers updated to support phones with the newer camera sensors

- ms79723's SBC v7 mod integrated for enhanced battery charging

- Misc speed tweaks/optimizations
[EVO 4G Android Development] mwielgosz:
Awesome! Flashing now.

Evolved into a higher form of communication
[EVO 4G Android Development] sgt. slaughter:
Awsome!

Going through the source did you tell how HTC removed the FPS limit? Did they use the same method you guys did or no?
[EVO 4G Android Development] ageesm:
Quite excited for this. Thank you, will report back about 0004 camera.

EDIT: Camera 100% functional from what I can tell. 0004 EVO.
[EVO 4G Android Development] mwielgosz:
Is the default governor still conservative for this kernel?

Evolved into a higher form of communication
[EVO 4G Android Development] netarchy:
Yes they did
[EVO 4G Android Development] netarchy:
Yes it is, but you can change it with setcpu if you wish.
[EVO 4G Android Development] bignibb:
This may be a stupid question but is 4.2.3 a havs kernel in anyway, more, less, or not at all?
[EVO 4G Android Development] frifox:
Could be just me but this new build's Sense UI screen scrolling isnt as smooth as the previous one... Both were less-aggressive undervolting. Ill use this build a little more and will let you guys know if things get better or not

ps: both caches wiped after flashing
[EVO 4G Android Development] netarchy:
The builds are labelled

havs-less

havs-more

nohavs

nohavs-noUV
[EVO 4G Android Development] netarchy:
Epson or Nova panel?
[EVO 4G Android Development] mylasthope:
Will we need to wipe battery stats with this kernel? Ms says we don't have to in his thread. Thanks net! :)
[EVO 4G Android Development] sgt. slaughter:
haha sneaky guys there.

Take it that it will be a lil while before you get a full 2.6.34 based kernel out? Any other specific things you pulled/noticed in the new sources besides the fps fix and new camera drivers?
[EVO 4G Android Development] netarchy:
You shouldn't need to wipe battery stats afaik, it's the same sbc mod straight from ms's github.

I'm rather impressed with it on my phone so far.
[EVO 4G Android Development] xlGmanlx:
Net, great turn around, downloading now
[EVO 4G Android Development] d0cx:
Is this newer v4.2.3 based on the latest OTA?
[EVO 4G Android Development] apfrost:
Sweet! No screen tearing on the new version! Thanks!
[EVO 4G Android Development] mjohnson4580:
Is the 4.2.3 based off the source released today or still 2.6.32.27