yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] housry23:
I just want to ask you one question. Why do you even care what anyone else does with their phones. I mean really, why does it matter to you that I want SBC? Why do you waste space in your head about what anyone else is doing with their phones? Yes their should be a warning on SBC kernels on what can happen for noobs, but hopefully people are reading about SBC kernels before just flashing them. i would say that most people that are flashing kernels pretty much know how to read and most probably even do research before flashing them. This may come as a shock to you, but you are not smarter than everyone here and you have absolutely no control over anyone else but yourself. I am glad that you don't like SBC and don't think people should use it. That's you opinion and you don't have to post it in every thread that mentions SBC. Get a life and stop calling people on here names and get over the fact that a lot of people like SBC despite hearing the horror stories. Why? Because it fully charges out extended batteries and helps us get the most out of them. Why else? Because we hate to see that the full potential on our already short battery life is not being used. Rant Over!
[EVO 4G Android Development] HondaCop:
+1000

PS. My name is HondaCop and I approve this message.
[EVO 4G Android Development] Just_s:
+++1 and an AMEN!
[EVO 4G Android Development] aimbdd:
hey guys lets be nice to everyone. We don;t want another thread like this on. There is plenty of other threads to debate this on. Also it has been decided that their will be warnings on all these mods. So no need for anymore comments really. Let everyone make their own decision.
[EVO 4G Android Development] thedarksavant:
OK, I'll try to say this one last time as clearly as possible. Even if it's not a coincidence, it's not causation. If SBC caused your battery to espload, everyones battery would espload.

Thank you for the warning. Yes, we need to be aware of what we are getting into, but please please please read up on the difference between correlation and causation. There is only a correlation between SBC and battery fires. There's also a correlation between global temperature and the number of pirates. It doesn't mean that global temperature changes cause pirate extinction.

http://en.wikipedia.org/wiki/Correlation_does_not_imply_causation

http://www.slideshare.net/carmean/correlation-vs-causation

http://www.statistics-help-online.com/node50.html

http://www.associatedcontent.com/article/704479/correlation_vs_causation_differences.html
[EVO 4G Android Development] HondaCop:
My head is about to "espload".

PS. My name is HondaCop and I approve this message.
[EVO 4G Android Development] xlGmanlx:
Jew talkkin to me'?
[EVO 4G Android Development] Justin.G11:
Ironically, while you did a wonderful job in defining causation, you linked nothing that would rule it out.

It's a theory at this time, one that's going through a real life testing cycle as it were. In time the back and forth bickering will make way to common knowledge and people will just be linking a wiki page and calling those who ask n00bs ... but we are a long way from that yet.
[EVO 4G Android Development] thedarksavant:
I'm not trying to rule it out, I'm trying to bring science to the discussion. One guy posts about an overheated battery and all of a sudden people want SBC kernels banned. Its a candidate for the problem, but I don't think we can call it the cause yet.
[EVO 4G Android Development] defjef123:
how come it wont let me download? after i click on it,goes to the blank page and when click to download nothing happenes?
[EVO 4G Android Development] Crossrocker:
You really shouldn't use this unless you know what SBC is.. but whatare you trying to download?

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
[EVO 4G Android Development] defjef123:
The link wasn't working for some reason but I got it now. And I understand about sbc
[EVO 4G Android Development] BlueHarford:
All Future Kernels will be in http://xdaforums.com/showthread.php?p=10678747

Please do no discuss old Savage or Zendroid in that thread.
[EVO 4G Android Development] :
I think everyone is aware of your stance on SBC by now. Lets all move to the new thread, be civil, and leave the SBC discussions in the SBC threads.
[EVO 4G Android Development] Anon9mouz:
Do these have sbc lookin for another aosp kernel with sbc any help thanks
[EVO 4G Android Development] eventer289:
Accidental post
[EVO 4G Android Development] xhazyx:
Lol anything can happen at 4am
[EVO 4G Android Development] doeboy711:
I have tried using the Kernel twice and both times it makes my SMS text's show that they were received about 10 hours prior. Has this happened to anyone else. My texts say i received them at 4am when I received them at 2pm.
[EVO 4G Android Development] Androidious:
I'm trying to confirm whether or not the latest 1.10 kernel version has SBC or not. I want a kernel without SBC for AOSP. Thanks to whomever answers :-)
[EVO 4G Android Development] xhazyx:
Try savaged-zen... extremely smooth
[EVO 4G Android Development] dgstidham:
this is a very smooth kernel, but i don't get the FPS that i got with SBC-net4.2.2-less-havs-v7.

I was using the SBC kernel with MIUI but they didn't play well together... so I am now using this kernel (Zendroid) which is working great but the quadrant FPS rates are significantly lower than with the SBC-net-4.2.2 kernel which i was almost hitting 1500 in quadrant...

any thoughts or recommendations on other kernels to use. the zendroid has yet to make my phone restart :) i've read that some phones don't play well with HAVS.
[EVO 4G Android Development] eman3316@optonline.net:
Who cares about quadrant scores. If your phone is running well and is not lagging, what difference does it make quadrant score it has? I have used kernels that score lower but run things better then faster scoring kernels.

I actually stopped testing kernels. My everyday use with the kernel is the true test whether it works well or not.
[EVO 4G Android Development] BlueHarford:
Some older kernels on here were all about them. People got used to using them as Gospel
[EVO 4G Android Development] h20wakebum:
Notifications not displaying

I am noticing that after flashing to 1.1.0 CFS, I can no longer get my notifications drop down to display.

I see the status bar, but that's it.

I've cleared Cache and Dalvik.

Any thoughts?

-RR
[EVO 4G Android Development] globen:
Do any of these kernel support a2sd? Thanks
[EVO 4G Android Development] kingjuice:
Still no 4g?... ever?
[EVO 4G Android Development] mwielgosz:
These kernels are no longer under development. The developer of this kernel joined the Savage team who is now known as Savaged-Zen
[EVO 4G Android Development] xHausx:
Anyone know where I can find a no sbc build of 1.02?
[EVO 4G Android Development] mwielgosz:
These kernels are quite outdated now, but I have all of the 1.6 versions if you would like them.
[EVO 4G Android Development] xHausx:
1.02 is reported to get along well with the Gingerbread Sense 2.1 ports and one in particular is still 2.3.2, so I wasn't sure if any based on the newer kernels would work as well. If you're interested we could really use someone familiar with kernels to help out.

The thread for it is here.
[EVO 4G Android Development] bbedward:
You can build one from http://git.zen-kernel.org/zendroid/ :D
[EVO 4G Android Development] xHausx:
That's a lot of work if there is already one compiled somewhere.

Well, not really, but for me it is because I'm not set up for it atm. :)
[EVO 4G Android Development] xhazyx:
For some reason WiFi didn't work for me.... I tried the BFS build

Hazed out Supersonic
[EVO 4G Android Development] LifeInTheGrey:
0.3 or 0.3.1? Because I'm on WiFi right now with BFS on 0.3.1.
[EVO 4G Android Development] dkelle4:
Just flashed BFS version...seems incredibly stable so far. I'm enjoying the speed coming out of these .35 kernels.
[EVO 4G Android Development] wrich73:
wow, This is the first BFS build I've used that I have liked...stable and super fast...wifi and bluetooth work flawlessly too.
[EVO 4G Android Development] jcallaway77:
I flashed 0.3.1 and it seems to be running great at stock speeds... wifi and bt are working.... linpack arround 35 and quadrant 1700 +.... when i oc above 1036 mhz, it becomes unstable... and performance drops significantly... when in performance mode@ 1190 mhz i get a linpack of arround 18 mflops.... at stock speeds this is one of the fastest kernels ive tryed, thanks for the kernel and your hard work. Its nice to see some more aosp choices for the evo.
[EVO 4G Android Development] halorin:
Running the latest BFS kernel. VERY snappy so far. I've had a couple of instances where the screen had a hard time coming on after being off for a while. Holding the power button longer fixed this. Using the smartass governor set to 248/998 on SetCPU. Cm6 RC1.
[EVO 4G Android Development] xhazyx:
My bad, now I'm pretty sure I flashed the older version. Gonna try 0.3.1 and report back

Hazed out Supersonic
[EVO 4G Android Development] krazyflipj:
Which governer ru guys using?

Sent from my CM6 powered device
[EVO 4G Android Development] Igotsanevo4g:
3.1 bfs is great. Thanks :D
[EVO 4G Android Development] blackroseMD1:
Haven't flashed 0.3.1 yet, but with 0.3 BFS, I wasn't able to connect to my computer via USB. I'll flash 0.3.1 and see if I'm still having the issue.
[EVO 4G Android Development] xhazyx:
I just flashed .3.1 and wifi is working... so far a pretty good kernel

Hazed out Supersonic
[EVO 4G Android Development] juancaperez2000:
conservative here so far so good
[EVO 4G Android Development] wrich73:
hmm, using MultiTouch Visualizer 2 I am only getting 2 touch points with this ROM, was getting 5 with the toast test kernel..on that subject, what difference does it make to have more than 2 in the first place? Using it as a game pad?
[EVO 4G Android Development] bbedward:
if you're referring to the toast test1 kernel, he updated the touch screen driver since then in git and it may not have incorporated the fix for some reason, i'll look into it ;) I'll probably temporarily revert to the older driver version
[EVO 4G Android Development] LifeInTheGrey:
On BFS .3.1 with smartass, getting around 1712 (high of 1746) quadrant with 245 min / 1103 max. Super snappy.
[EVO 4G Android Development] alcangel64:
can someone please tell me why the headset mic does not work when i flash this kernal
[EVO 4G Android Development] jcallaway77:
I dunno if im the only one seeing this but after running the bfs 0.3.1 for a few hours i started noticing some lag comming back from screen off and swiching between apps... i flashed the cfs build and its running much more stable but a little slower.... my phone doesnt usually like bfs so it might just be my phone.
[EVO 4G Android Development] tritron777:
I wonder how to fix this

drivers/input/misc/capella_cm3602.c: In function 'capella_cm3602_irq_handler':

drivers/input/misc/capella_cm3602.c:57: warning: unused variable 'val'

drivers/input/misc/capella_cm3602.c: In function 'capella_cm3602_enable':

drivers/input/misc/capella_cm3602.c:67: error: too few arguments to function 'data->pdata->power'

drivers/input/misc/capella_cm3602.c: In function 'capella_cm3602_disable':

drivers/input/misc/capella_cm3602.c:78: error: too few arguments to function 'data->pdata->power'

make[3]: *** [drivers/input/misc/capella_cm3602.o] Error 1

make[2]: *** [drivers/input/misc] Error 2

make[1]: *** [drivers/input] Error 2

If understand this correctly we need capella_cm3602 for evo
[EVO 4G Android Development] LifeInTheGrey:
What were your max/min settings? I got bad lag if I dropped down to 128 or overclocked past 1075. Settings at 245/1075 and getting quadrant scores of 1746. Just saying give her another try, cuz this is the first bfs kernel that's worked for me :).

Ride that evo train
[EVO 4G Android Development] skydeaner:
Hello I run tthe evobenchers kernel testsite. I am going to be putting results up tonight or tomorrow for this batch. I just wanted to let you know you set a new record for the full idle screen off test. Came in at an average 46ma with dips frequently down to 44ma. Congrats and whatever you did don't change it. Lol
[EVO 4G Android Development] OgremustCrush:
Unfortunately this appears to have the Bluetooth wake lock bug that recently got fixed in cm6 stock kernel. Toast's 2.6.35 kernel doesn't appear to have this problem. Sadness :-(

Posted by my rooted EVO 4G
[EVO 4G Android Development] dkelle4:
Can you elaborate on exactly what this means?
[EVO 4G Android Development] lcars123:
I would love A2SD support in this kernel.
[EVO 4G Android Development] wuclan48:
Lowest power consumption in that scenario.

Sent from the void...
[EVO 4G Android Development] jcallaway77:
I tried this and it seems to be working... thanks for the help.
[EVO 4G Android Development] krazyflipj:
I loved this kernel but after a reboot, my phone keeps getting stuck on the CM splash screen even after wiping dalvik and cache. Anyone else getting this?
[EVO 4G Android Development] bbedward:
This kernel loses significant performance when overclocking for me, i'm probably going to slightly overvolt the higher frequencies next release
[EVO 4G Android Development] sph33r:
My phone rebooted itself last ngiht and then got stuck at the white screen and refused to boot any further. Tried to wipe cache, same thing. Had to flash back to stock to get the phone working.
[EVO 4G Android Development] kthejoker20:
This is actually turning out to be a good kernel.

BT problems at first, but not on the 3.1 build.

Running HBOOT 2.02 CM6.1 zend aplha

QS scores of 1600+ not overclocked.
[EVO 4G Android Development] akarol:
Any chance of you making a Sense kernel?
[EVO 4G Android Development] juancaperez2000:
same issue here, hopefully toast test 2 or new zendroid realease fix this problem because, so far i dont have chance to clean batt stats
[EVO 4G Android Development] dadoc04:
same thing here as well.....
[EVO 4G Android Development] Kraenesk:
Tried bfs and cfs getting betterluck from cfs. With cm6.1. Seems this kernal gets its best performance and is most stable at 1.15ghz and below. It seems to actually slow phone down above that. And there is no real noticeable performance increase above 1.13ghz I'm guessing it has to do with CPU voltage levels not being optimized for that range yet?

I know its alpha so i ain't complaining. If you ignore quadrant scores this actually seems snappier set at 998mhz than stock cm6.1 kernal set at 1.13ghz or snap at 1.19ghz.
[EVO 4G Android Development] Kraenesk:
If you came from snap Turbo before flashing this. You need to completely whipe factory defaults. Reinstall cm6.1 and gapps from scratch. Then flash kernal or it will lock up at white HTC screen
[EVO 4G Android Development] Dozenboy0012:
Really great kernel especially for alpha Im runnin cm6 shook and recooked but I tried cfs and I seem to get more stability from bfs but better battery life from cfs so I gotta roll with the stability cuz the battery difference wasnt a large margin. Really like tho keep up the good work!
[EVO 4G Android Development] juancaperez2000:
just flashing new CFS 0.4 reporting later, hopefully no more problems stucking at splash screen, thanks for keep developing for us
[EVO 4G Android Development] wrich73:
Using the .4 BFS on CM nightly 158 I am getting 1797 quadrant stock--no set cpu. This kernel really seems to work best performance wise if you just leave it alone stock clocked and let smartass do the governing hehe
[EVO 4G Android Development] dadoc04:
i came from ava's rom with stock kernal and was having the issue.

I was using Amon RA and was getting stuck at the HTC screen. I ended up flashing to Clockwork and havent had the lock up since. Not sure if thats whats causing it or not, but I have been able to turn the phone off and reboot, as well as boot into recovery and reboot without problem now.
[EVO 4G Android Development] jcallaway77:
I just flashed 0.4 bfs and its running great... overall, it seems more responsive and im seeing the highest and most consistant benchmarks out of the zendroid kernels yet.... i dunno if you made any changes to the voltage table at oc speeds but this kernel seems to handle oc a little better but still unstable with anything above 1075 mhz.
[EVO 4G Android Development] rain91:
Using 0.4-CFS. Feels much more responsive than 0.3.1-CFS. I'll run this the rest of the day to feel it out. Thanks dev!
[EVO 4G Android Development] LifeInTheGrey:
Just flashed 0.4 BFS ... ZD keeps getting better and better. Settings still at 245/1075, feels even more responsive and smooth, and got quadrant of 1711 on 3G, 1803 on Wifi. I just hope the battery life is as good ... I unplugged 5.5 hours ago at 93, after flashing this kernel and playing around with it for a few minutes, I'm still at 81. :)

Edit: Oh, forgot to mention ... with 0.3.1 and Super Power on Night mode, this baby dropped only 1% when I slept (did a quick recharge while getting ready, in case anyone questions the unplugging mentioned above). Great job man, truly well done.

Edit 2:Okay so based on my tests of different maxes, I have interesting results. On 3G at 1036 I got a peak of 1720, with the lowest score at 1697 (very small standard deviation over 5 tests). With 1075, my peak was slightly lower, but also had a much larger standard deviation (lowest score of 1596). I also tested stock, and found the standard deviation just barely higher than that of 1036, with a high score of 1611. Based on this, I believe 1036 max not only provides the best performance, but greatest level of consistency as well.

And in case you were wondering ... yes, I really am THAT bored at work.
[EVO 4G Android Development] xhazyx:
Hows superpower working for u, i just recently found out about the app, and really dont know if it's making a significant difference for battery life

thanks in advance
[EVO 4G Android Development] LifeInTheGrey:
It works great! The only thing that sucks about it is that it doesn't apply on every boot. To apply you just need to reopen the app, so not a huge problem imo. But in terms of better life, awesome.
[EVO 4G Android Development] xhazyx:
thanks for the quick response man, gonna try it out and see how it goes, anything that improves the battery life on this EVO is welcomed.... as long as it doesnt affect performance
[EVO 4G Android Development] LifeInTheGrey:
No problem ... if you check my post you originally quoted, I actually found that 1036 provided best performance and consistency based on quadrant scores (and I imagine battery life is better compared to 1075, where I had it). I'm getting consistent 1700s on 3G with Super Power on, good enough performance for me. ;)
[EVO 4G Android Development] luisrcastillo:
Great performance so far. I hope battery life is as good
[EVO 4G Android Development] luisrcastillo:
If you have problems with camera not taking pics, not responsive and freezing, clear data for cam. Just happened to me on 0.4 bfs
[EVO 4G Android Development] tpdtopcop:
Is this superpower from market place?
[EVO 4G Android Development] paranoid android85:
Thanks for the new kernel. Working great on my evo

Sent from the belly of the beast
[EVO 4G Android Development] LifeInTheGrey:
Yeah, you can snag it in the market.

Ride that evo train
[EVO 4G Android Development] Lento10:
Is anyone still getting stuck in the splash screen after rebooting? I was able to flash the kernel with no problems, i try cfs/bfs and both recoveries.

Thanks
[EVO 4G Android Development] loveact:
mine still got stuck on evo's white screen

i'm using the 0.4 bfs

any idea??
[EVO 4G Android Development] stangdriverdoug:
Just figured I would chime in.running this kernel starting last night until snap gets done with his. I'll keep you guys posted on performance. So far so good.

CM Powered
[EVO 4G Android Development] pardonmyownage:
Still didn't work. Tried a full wipe and data wipe. No matter what I do always gets stuck at white screen. Tried wiping cache and dalvik nothing helps

same for both .4 cfs and bfs
[EVO 4G Android Development] luisrcastillo:
How long are you waiting? took about 3 minutes for me on first boot
[EVO 4G Android Development] pardonmyownage:
I thought quiet a long time. I'll try again and make sure
[EVO 4G Android Development] pastert33:
So no one is running this kernel over 1252?
[EVO 4G Android Development] LifeInTheGrey:
It only goes to 1190 max...

Ride that evo train
[EVO 4G Android Development] pastert33:
ahh gotcha, thought I read that it went higher.
[EVO 4G Android Development] k4p741nkrunch:
What exactly are you flashing and in what order?

Here's what I did and it's working fantastic.

Full Wipe (data, cache, dalvik)/ Install CM6.1 nightly #159/ Flash GApps (10252010)/ Install Zen kernel.

If you install 1 more zip than this in the same session you will get boot loops :P

Save the theme for a reboot!
[EVO 4G Android Development] Kraenesk:
Try the .31 kernel I think some phones don't play well with .4 mine being one of em. The. 31 kernel works great for me. Higher version number only means newer. Not always better
[EVO 4G Android Development] xhazyx:
^^^^^^^^^^^^^^^^^^^^

+1 agree with every letter
[EVO 4G Android Development] Kraenesk:
Null null null
[EVO 4G Android Development] pardonmyownage:
did exactly that, but i installed one other zip. will redo and split it up.

fyi-also tried installing just the kernel. waited over 10 mins on white screen. still no go, will try complete wipe.
[EVO 4G Android Development] BlueHarford:
.04 version of this is deadly slow. quadrant will barley run, 1st image test was getting 5fps... was using the bfs with 158
[EVO 4G Android Development] Kraenesk:
.31 seems fast and stable though. Long as you don't clock it faster than 1.13
[EVO 4G Android Development] EndlessDissent:
Wow. I can't believe so many people are having problems with 0.4. I guess it's true that every phone is different.

My phone didn't like 0.3.1 at all (super laggy and terrible framerate), but 0.4 runs flawlessly for me on both CM and MIUI, even better than Toast's test kernel, and until I tried Zendroid, Toast's kernel was the only one (besides the HTC kernels) that didn't tear like crazy when I scrolled or played games.
[EVO 4G Android Development] rain91:
Been running .4 CFS with no trouble the past 2 days on CM6.1-RC1.
[EVO 4G Android Development] spiicytuna:
.4 gives funky output:

<3>[ 868.081909] cpufreq: invalid target_freq: 245000

<3>[ 868.125091] cpufreq: invalid target_freq: 140250

<3>[ 868.325286] cpufreq: invalid target_freq: 152500

<3>[ 868.525482] cpufreq: invalid target_freq: 164750

<3>[ 868.694122] cpufreq: invalid target_freq: 245000

<3>[ 868.725738] cpufreq: invalid target_freq: 177000

<3>[ 868.925933] cpufreq: invalid target_freq: 189250

<3>[ 869.126068] cpufreq: invalid target_freq: 201500

<3>[ 869.326232] cpufreq: invalid target_freq: 213750

<3>[ 869.526428] cpufreq: invalid target_freq: 226000

<3>[ 869.726593] cpufreq: invalid target_freq: 238250

<3>[ 869.926818] cpufreq: invalid target_freq: 245000

<3>[ 878.619049] cpufreq: invalid target_freq: 245000

<3>[ 878.630889] cpufreq: invalid target_freq: 245000

<3>[ 878.635467] cpufreq: invalid target_freq: 245000

etc., etc., etc.
[EVO 4G Android Development] LifeInTheGrey:
I never had reboot issues, however I was curious about the overvolting added for overclocking, so I flashed 0.5.

I did a basic step-down analysis (running 3 quadrants at 1190, then stepping down to the next maximum frequency setting). Based on a very quick test, 1036 once again yields the greatest and most consistent performance. It seems that for the higher OC settings, there is a visual hiccup that occurs; the average fps drops by over 20% in each of the GPU tests. But at 1136, quadrant scores are pretty much the same (slightly lower, but not statistically significant).

Other than that, haven't played with it too much. Will report again if it starts eating children or something.
[EVO 4G Android Development] LifeInTheGrey:
I know... my phone has never been smoother than on .4 bfs. Zero tearing, lag, and battery life is great (around 26 hours on average).

Ride that evo train