yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Previous builds I had conservative governor freq step set from 5% to 20%, (100% would be more like the ondemand governor), but it seemed it was to aggressive, so as of right now seems stock settings gives best performance.

Sent from my Captivate
[Captivate Android Development] cumanzor:
I have rel 48 running awesomely @ 1300Mhz. Gonna try 49 now. Awesome kernel man...

Has anybody tried the new PS emulator? How is it working for you?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] seanzscreams:
in your extensive testing have you snapped a photo , then switch to video , take a small vid clip, then swith to camera and see if it will take another photo without locking up with uv that high
[Captivate Android Development] RonH54:
I have just went from 48 to 49. I used the 100hz for both 48 and 49 with the same States but I did UV more on each State on #49. The only thing I did notice is my NeoCore Test went down from 55fps to 48 fps when I changed to #49 is the increase in UV which I did with #49 causing this drop?
[Captivate Android Development] wonner:
I'm not sure if this is the right place for this, but is the Voltage Control app different? I specifically remember a pull-up menu "States" where you ticked the states you wanted.
[Captivate Android Development] existz:
Its probably from adjusting the gpu refresh rate from 60 to 72hz, a higher refresh rate makes it smoother, it may lower fps, though it will be very minimal, but it will give a smoother experience ...its another one of those "don't pay to much attention to benchmark scores" kinda thing ..

Sent from my Captivate
[Captivate Android Development] existz:
Download the one in the OP, its the latest, as far as I know...but yes there should be a states menu

Sent from my Captivate
[Captivate Android Development] opcow:
I get lower quadrant scores on #49 vs #48 and it may be due to lower 3D graphics score. I normally peg at 56fps (sometimes it shows 57 briefly) planet/moon thing and also hit 56 on the one prior to that. On #49 I seem to have a 50 fps ceiling.
[Captivate Android Development] existz:
In real game play you will never see the difference with the small fps drop, if anything it will be smoother with the higher refresh rate... im going to go ahead and knock this one down before we start seeing pages and pages of lower fps in benchmarks...

To all of you about to post about lower fps or benchmark scores..

Don't worry so much about benchmark scores, in testing it has shown to improve things, about 8 testers confirm, even though it "can" possibly lower fps, the higher refresh rate (60-->72hz) gives a smoother experience. However, if its proved to be a problem, I don't care at all to revert it back, but just don't go by benchmark scores. This is all ill say on the subject, im not trying to win the highest scoring kernel award, im trying to give the best possible user experience while saving as much battery as possible...but again, if its proven to be a problem ill revert it back..

Sent from my Captivate
[Captivate Android Development] seanzscreams:
In regards to the benchmark running 49 1000 xt cpu1200 the rotating planet WOW solid 65fps wtf I've never seen that

Sucker punch FTW
[Captivate Android Development] shaolin95:
Neocore for me is giving me 65s or so instead of the usual 55.7
[Captivate Android Development] existz:
Perfect example as to why you shouldn't worry about benchmark scores that much, some will show a decrease, some will show an improvement ..it just depends on what and how it calculates things...what's important is how it does in a real life situation.

EDIT

Im not directing this towards you, just saying to those that worry about benchmark scores that they are not 100% accurate and not to go by them, as it will vary from benchmark to benchmark and to real life experience ..I personally do not use them, except for linpack to get a general idea, so if something shows an improvement in a real life situation, ill use it

Sent from my Captivate
[Captivate Android Development] IStern:
With build #49 I actually get much better 3D performance, benchmark and general gaming.

I'm not sure how the cpu clock and the gpu clock are tied together, but 1.2ghz gives better 3D numbers than 1.3ghz.
[Captivate Android Development] Auridran:
Did that without even breaking a sweat. Did it several more times with no problems.
[Captivate Android Development] RonH54:
Scores don't bother me especially since I don't game much I just like run them and if there is a difference what might be the cause just for my own info.
[Captivate Android Development] shaolin95:
From what I recall from Setirons thread....only at 1200 , 1400 and 1600 the GPU is running stock speed so that could very well be that the GPU is running slower at 1300 than at 1200.
[Captivate Android Development] existz:
I didn't mean for that to sound directed to a certain person, I just wanted to cut down on the "I scored 5 points lower, this kernel sucks..h@x3r 4life" kind of post

Sent from my Captivate
[Captivate Android Development] Auridran:
Well, to be fair, there are bad benchmarks and there are good benchmarks. Quadrant is a bad benchmark and its scores shouldn't matter. SmartBench 2010 is pretty good, and Neocore is also good (though strictly on a 3D basis, processor speed means just about nothing in it).

I'm also getting lower performance in this kernel. It's weird how some get higher and some get lower than last kernel... It should be relatively the same. It's not like UVing, where every chip is different. Every chip is the same from a performance standpoint. The only variations would be slight variations from background processes.

I'm in the camp that's getting lower benchmarks, and not just lower benchmarks but lower performance in general. FFVII no longer plays smoothly in FPse at 1.2GHz.
[Captivate Android Development] shaolin95:
Rom related maybe?
[Captivate Android Development] existz:
Oh i agree 100%, some are better than others, some just suck, i was just trying to say, dont rely 100% on benchmarks, as they do not matter compared to real life, as i have a feeling alot of people will just scan through these last few post, not reading, and see a drop in quadrant and start posting, relying on nothing but quadrant scores...id rather score 100 points lower in something if it was going to give me better performance, but if real world game play is proven to be worse, after all other factors have been proved not to be the issue, i dont care to revert it... So far, most of my testers have reported an improvement, but if more keep saying its hurt performance (after making sure nothing else could be causing the performance drop), ill revert it back
[Captivate Android Development] Auridran:
I agree with that as well but to me it sounded as if you were writing them off entirely. It's good to see that you're not.

I wouldn't be so hasty as to get rid of it, because some people are getting better results. We just have to find out what's causing the lower/higher scores. I'm going to flash back to #48 to rule out something other than the kernel, or something that the kernel is doing.

EDIT: How did you flash it, shaolin95? CWM or kernel flasher?
[Captivate Android Development] existz:
The main reason I say dont rely on benchmarks, is you might be able to score higher, say in linpack for example, than what you did before, but then you can run quadrant and have a lower score than you did before...they all vary, they all calculate different things, different ways..
[Captivate Android Development] shaolin95:
This kernel is proving rock solid at 1.4Ghz on my phone so far...I am impressed!
[Captivate Android Development] existz:
I always recommend to flash via CWM, ive seen alot of issues come from flashing with kernel flasher, (ie. the flash did not take even though it said it did, there was one tester that flashed with kernel flasher and it ended up booting into safe mode on every boot, but flashing with CWM fixed it...)so just to be safe, always use CWM...which im not putting down kernel flasher, its an awesome app, just needs a few bugs ironed out..which im sure theres people thats never had a problem with it, but things can still go wrong....even with CWM. But IMO CWM is more reliable...but thats just my opinion and what i recommend, to each his own, if you have never had a problem, then by all means keep using it..but if something weird happens after flashing, try flashing with CWM
[Captivate Android Development] shaolin95:
Yeah I never use Kernel Flasher.
[Captivate Android Development] Auridran:
So far I can say the following:

The results do not change with different methods of flashing, it doesn't seem to be related to filesystems or the safe/faster mount options, doesn't seem to be a scheduler issue, and isn't related to 100/1000Hz.

Not a clue where to go from here.
[Captivate Android Development] opcow:
I'm not worried about it so much as curious because it looks like I'm vsyncing @ 50Hz. (I saw periods of sustained 50fps but never even a blip over.)
[Captivate Android Development] opcow:
This?

-increased refresh rate of gpu (freq=60-->72)​

Edit: Ok strange, but I went back and forth between #48 and #49 and got the 50fps lock every time on #49. Just flashed #49 again and I hit 65 fps on the planet. <shrug>
[Captivate Android Development] itdiestoday:
Currently running the 1000hz and really enjoying it. I don't think that I've had a better experience than this when it comes to right out of the box no oc performance. Think I'm going to stick to regular settings for a while, especially if your future releases are this smooth.

Sent from my Captivate
[Captivate Android Development] RonH54:
If you go from the 100hz to the 1000 hz version will the UV one is using on the 100 version probably need to be changed once 1000 hz is up and running?
[Captivate Android Development] elghouchd:
Just one thing, in the future will there be different versions with different governer settings? Cause i like the OnDemand governor a lot. If there isnt gonna be or you dont feel like doing it THATS OK! Im just wondering. Anyway, this is still the best kernel ever!

Edit: off topic but i wanna post this....came out today....

http://xdaforums.com/showthread.php?t=955471
[Captivate Android Development] froli13:
Try to UV less on higher states. Maybe it just needs a little more juice ;)
[Captivate Android Development] cumanzor:
Confirming 65 fps in NeoCore as well. Haven't played any 3D game yet but Ill do it as soon as I have a chance.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] shaolin95:
Yeah I mentioned Neocore before too but then realized it is a bad example as it was always capped by the framerate so we cannot compare the 3D performance with it unfortunately. :-)
[Captivate Android Development] froli13:
By the way, I flashed #48 100hz this morning and I love it so far! First time trying a 100hz kernel and battery life is even better than what I thought. I'm at 60% after 10 hours. Usually it's 45-50%

Didn't noticed any difference in performance in daily use so far. I think I'll stick with the 100hz version for a while!

Downloading #49 now ;)
[Captivate Android Development] froli13:
Just tried some benchmarks with #48 :

Neocore:48.7

Linpack: ~16.5

Quadrant: 1686

And with #49 :

Neocore: 49.0

Linpack: ~16.5

Quadrant: 1784

As you can see, not much changes for me...

Both tested with the 100hz version.
[Captivate Android Development] s2h2golf:
Seems the Quadrant oddity is only related to 1ghz and 1200mhz. I get the 65fps (and 70 something spikes) at those clock speeds, but the 50fps cap at 1300mhz. Nenamark shows 49.6fps consistent across all three speeds.
[Captivate Android Development] slider2828:
Anyone know what HRTICK is? Just readiong from the change log.
[Captivate Android Development] ilsm:
screen timeout

hey, i have problem of screen timeout after installing 48 version, its go automatically to 1 sec, and when i go to the menu to choose the time of timeout it didn't show any choice in the menu, and I need to choose again one of the options.

after some time it begin again to blank screen after 1 sec.
[Captivate Android Development] Grandelama:
I tried to use the switching button in the camera as a UV stability test to set up a stable configuration.

I discovered that if I start tapping the photo/video switching button (continuously, like 2 taps per second), I always end up with a freeze in less than a minute, even with no UV at all.

I guess there is no really stable configuration for me
[Captivate Android Development] shaolin95:
Shouldnt you at least be getting 55.7 or around there in Neocore?
[Captivate Android Development] itdiestoday:
Definitely interesting numbers. I just ran neocore at 1ghz no oc or uv and got 64.6.

Getting around 13.3 in linpack. Haven't tried quadrant yet though.

Edit: just got 1567 in quadrant.

Ex man. This kernel is cheese.

Sent from my Captivate
[Captivate Android Development] slaman:
Blah sleep death with NO UV... I've now disabled all OC as well. If I get more sleep deaths, looks like I'll have to stick to another kernel.

Sent from my Samsung Captivate SGH-I896
[Captivate Android Development] existz:
Been messing around with some memory management, more like the nexus s settings, lowmemorykiller is more aggressive , and also been messing with compcache (ramzswap) , which you can disable with a script, i will try to include both in the next release, not counting bug fix releases (if any)..

Sent from my Captivate
[Captivate Android Development] elghouchd:
How do you disable the notification mod?
[Captivate Android Development] slaman:
BLN in recovery

Sent from my Samsung Captivate SGH-I896
[Captivate Android Development] elghouchd:
Oops i meant the clear notification THEME mod form the serendipity website..probably should have made that clearer :)
[Captivate Android Development] froli13:
Interesting... Just ran Neocore with media volume to 0 and got 63.7

EDIT: Just re-ran with sound and got 64.1 :confused:

I guess this is why I (and many others) don't rely on benchmarks...
[Captivate Android Development] Auridran:
That is extremely odd. I just had the same thing. Reduced media volume to 0, now at 64.7FPS, even after turning it back up.

I'll have to test out FPse later, as I'm at work right now.
[Captivate Android Development] existz:
Yea that's pretty weird, ill look into it and see if I can find what's causing it...if I can ...

Sent from my Captivate
[Captivate Android Development] bullseye8877:
Loving it, but should I uninstall setcpu and instead just use the voltage control app to change my clock settings?
[Captivate Android Development] froli13:
Even if you can't, I don't think it's a real issue. This kernel is still awesome ;)
[Captivate Android Development] froli13:
Just read the OP
[Captivate Android Development] sixstringsg:
Not a kernel problem, its with the rom.
[Captivate Android Development] johan8:
I feel #48 is a bit smoother than #49

but benchmark in #49 is higher.
[Captivate Android Development] xreflection:
So then go for 48. The higher score probably isn't that much of a difference to make any real impact on real world performance..I would go for the smoother experience imo.
[Captivate Android Development] xbeamelite:
i have the exact opposite. #49 is def smoother but with lower benchmarks (16.5 linpack, 48.6 neocore compared to 16.7, 55.6) and imo it does feel just a tad slower than #48. I'm liking the smoothness, so ill stay on #49 for now.
[Captivate Android Development] slaman:
I have now gotten a sleep death without any UV or OC.

Will try a new kernel to see if the problem is specific to this kernel or it's a hardware issue.
[Captivate Android Development] Grandelama:
+1

#49 feels smoother imho
[Captivate Android Development] Kionic:
what the hell...i got 62.7 on neocore. Mind blown.
[Captivate Android Development] shaolin95:
Neocore has always been limited to 55s or so due to the FPS cap so yes it looks nice but is nothing more than we are finally able to see the real score without the frame rate cap. ;)
[Captivate Android Development] Kionic:
Oh ok. Its awesome seeing that score though.
[Captivate Android Development] ksimilie:
using this (49) with Andromeda and my screen goes black everytime i plug it in to my computer or unplug it from the computer.
[Captivate Android Development] opcow:
I'm using #49 100Hz with Andromeda 1.1. No problems here.
[Captivate Android Development] Grandelama:
If it doesn't wake up when you press the power button, you are undervolting too much
[Captivate Android Development] ksimilie:
I haven't touched the voltage app so i dont think thats the problem. Im using the 500hz one. Ill try it again after work today.

Is this what they call the sleep death thingny cause i thought that was when the battery fully charged
[Captivate Android Development] existz:
There's a sleep death and a charge death, even with no UV, the OC/UV patch still alters the cpu voltage table in the source code, so it can technically still happen, as of right now I don't have a fix for it but im looking into it. Actually OC/UVing can actually fix it sometimes, since all phones are different, some have a sweet spot when adjusting the voltage lower, but some don't like it all...just have to mess with different settings to see how yours responds

Sent from my Captivate
[Captivate Android Development] Grandelama:
From my experience, charge of death is almost independent from the charge level, while it's very sensible to the type of charger you are using.

500mA or less sources (like pc usb ports) seems to be the safest.

It never happened to me with no UV, though..
[Captivate Android Development] AReynante:
I suppose I'm just lucky then. I've never had any charge issues, regardless of kernel or OC/UV level :/

Of course now that I said that, it will probably happen :(
[Captivate Android Development] slider2828:
Has anyone experienced battery drain with #49 100mhz version? I am draining like crazy when compared to #48?
[Captivate Android Development] ccdoggy:
I was thinking the same myself but last night i had charge death for the first time ever. I am UVing allot and will tone it down a little to see what happens tonight.
[Captivate Android Development] existz:
you need to give it longer to tell about battery life, give it a few full drain/charges so the battery can recalibrate itself, usually after a few flashes my calibration is way off and battery sucks, then after 4-5 full drain/charges it goes back to normal, im getting the best battery life with #49 than ive had yet, if you wipe batt stats, then you will have to start over with giving it a few drains/charge..but give it a few before deciding.. (this goes with any kernel/rom)
[Captivate Android Development] slider2828:
Kewl thanks for confirming. I didn't have this issue with any of the kernels prior to this. Like from 38-48 it was all smooth, but I will keep draining and charging. I do charging also with the phone off then on, etc.... I did delete the batt info also....
[Captivate Android Development] sjavvaji:
ohh...speedmod seems to have made some nice upgrades on k13b...when can u bring it over?...im personally looking forward to mounting the internal sd in recovery mode :D
[Captivate Android Development] RonH54:
I know this been asked but I just missed but what is the meaning in a 100 hz version vs the 1000 hz? What do these different hz refer to?

Thanks
[Captivate Android Development] existz:
As soon as he releases sources, last time I checked k13a sources was still up... im not sure if I will do his lowmemorykiller tweak or not, I've actually been working on a few of my own memory management tweaks, but ill check his settings, worst case ill add his lmk settings till I finish up on my tweaks ...also working on some VM and I/O tweaks, already working on build #50

Sent from my Captivate
[Captivate Android Development] existz:
The 100hz version has a system/kernel hz value of 100hz and a user space hz value if 100hz, eliminating hz--hz conversion... the 1000hz has a system/kernel hz value of 1000hz and a user space hz value of 200hz.. if the hz value is to high, it will start to cause issues, drivers will start to fail (camera not working, wifi not working...etc..etc)

HZ is an internal timer value used by the Android/Linux kernel. It affects the timer granularity of some kernel functions.

"The timer interrupt is at the heart of the system. Everything lives and dies based on it. Its period is basically the granularity of the system: timers hit on 10ms intervals, timeslices come due at 10ms intervals, etc."

From the linux/android source ...

"CONFIG_HZ

The frequency the system timer interrupt pops. Higher tick values provide improved granularity of timers, improved select() and poll() performance, and lower scheduling latency. Higher values, however, increase interrupt overhead and will allow jiffie wraparound sooner. For compatibility, the tick count is always exported as if HZ=100.

The default value, which was the value for all of eternity, is 100. If you are looking to provide better timer granularity or increased desktop performance, try 500 or 1000. In unsure, go with the default of 100."

Its explained in more detail here.. http://kerneltrap.org/node/464

Sent from my Captivate
[Captivate Android Development] Vivified:
I flashed SuckerPunch over a fresh flash of Precision and all I can say is.... WOW! So smooth and fast!
[Captivate Android Development] pizz0wn3d:
Hays im actually about to do the sane thing. Just gotta go flash this kernel. :P
[Captivate Android Development] capita:
Running precision and suckerpunch combo as well. Like it a lot.
[Captivate Android Development] Vivified:
You won't be disappointed :)
[Captivate Android Development] existz:
Should have the random reboot/freezes on boot actually fixed in the next release for those who experience it... also made some VM and IO tweaks, should help things...release in a day or so

Sent from my Captivate
[Captivate Android Development] pizz0wn3d:
Indeed, its very nice. I don't know if my captivate has ever been this responsive.

Herp Derp Captivate XDA
[Captivate Android Development] existz:
To those of you who dont UV and have sleep death, I need some testers that suffer from it (your phone goes to sleep, when you try to wake it, it doesn't come on, u have to do a battery pull to revive it..) this happens when its UNPLUGGED from charger, not charge death (just yet) .. I've got a fix from Morfic and coolbho3k in the Vibrant forum, which is for JPX sources, so it should fix it. Im going to work on it tonite and will have a test build up tomorrow with this fix, so either send me a PM on here or join my IRC channel (link in the OP)..I pop in and out all day/night long, so if I don't respond, ill be back on soon

Sent from my Captivate
[Captivate Android Development] danimmal:
i dont know if its the ROM im using or this kernal but i have been getting some bad scores and i do not know why, ive been using suckerpunch since the beginning and i have always been getting amazing scores off of linpack and quadrant, but for some reason i have been getting 11 to 13 on my scores on linpack and i cannot figure out why. i have the states enabled and everything.

anyone have any suggestions?
[Captivate Android Development] froli13:
To those who didn't know, you can hold vol+up for 15 seconds to reboot the phone when it freezes instead of pulling the battery ;)
[Captivate Android Development] slider2828:
What freq are you running at? Maybe try lowering hte freq?
[Captivate Android Development] pizz0wn3d:
Setcpu can cause that. if you have it installed, unintstall it and reboot.

Other than that.. make sure the states are enabled?

If all else fails, reflash :P

Herp Derp Captivate XDA
[Captivate Android Development] sjavvaji:
lol...i've always used this and it is so much easier than physically pulling that battery
[Captivate Android Development] danimmal:
All else did fail including reflashing just the kernal haha so I just redid everything and now.its working quite well. Thank you both for the tips. :D
[Captivate Android Development] pizz0wn3d:
Any time :D

Herp Derp Captivate XDA
[Captivate Android Development] LimaI896:
I have never seen such battery life on my phone.

Id rate moderate use for me.