yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] fatttire:
Okay. Flashing light for 1/220 of a second is different than detecting changes in light, as is required for evaluating game or movies.

Also, your population sample is wrong. Air pilots have some of the best vision. If you want to prove a point for common folk, you have to look at common folk.

I actually agree with you about 30+ fps on games looking a bit better. Last I checked I think our vision tops at around 50 or so but I have to check that.

My point really is you have to look at the scientific data. I like your air force study but its not good enough for me
[Captivate Android Development] fatttire:
Also the air force study wasn't bad - just not appropriate for us.

They probably wanted to see if a flash happens on a blank background how short it can be for pilots to see it.

To take a good study like that and apply it to us when we want to ask a different question isn't a good idea.

Just saying BC you said I thought I was smarter than the air force and that confused me

Also shaolin has a good point that everyone is different. Avg might be 50somethibg but person X may top at 72 and person Y at 31. Human genetics displays variability
[Captivate Android Development] nkrick:
I agree that flashing light for 1/220 of a second over an otherwise blank background is completely different than fps which is about movement of objects in an image on a screen.

But, this really is not about vision or how good someones vision is. This is about how the brain interprets movement through the visual field. I am not a scientist, but my understanding is that 24 fps is about the minimum requirement for the brain to see a series of images and interpret smooth movement between those images. As fps increases it gives the brain more data and less interpretation to do.

Since movies are shot at 24 fps, there is a limit to the amount of camera movement (the point of view) before scenes look bad because there is too much movement between two images and the brain does not interpret that movement very well (this makes some people sick). That is why in action movies, even though there may be a lot of movement happening on the screen, there is not a lot of movement in the PoV.

In FPS games, there can be a lot of movement in the frame (screen), and the PoV can be moving very rapidly. In this case, a higher FPS can result in much smoother game play because the brain is not forced to interpret large amounts of movement between the frames (due to the items in the frame moving and the PoV moving).
[Captivate Android Development] slider2828:
Realistically guys, running froyo with overkill ext2/ext4/binds is crazy fast already on stock clock... I don't have any lag what so ever, I don't really see the point in stressing the hardware. But only time will tell.... as heat will be the major factor... I want to see them running stress test....

But I agree, I used to play CS competitively and its noticeable difference at 30-60-99 FPS.... anything about 70 was fine.... in terms of viewing, but affecting game play higher fps gave you a more connected feel....
[Captivate Android Development] wmwilker:
+1

Quadrant scores don't make me hard:D
[Captivate Android Development] shaolin95:
Just because you do not need the extra speed it does not mean others cannot have any use for it....lets not feel like the center of the universe now.

There things like Playstation emulator that could use the extra speed for sure (not to mention better coding but thats up to the dev).
[Captivate Android Development] sombionix:
I'm working on 2.2 right now.
[Captivate Android Development] sombionix:
I'm sitting right next to DG right now. ;)
[Captivate Android Development] DOAlaboratories:
Holy damn, that sounds amazinggggg
[Captivate Android Development] Kubernetes:
Even if there is some limit to human perception of FPS, you'd still want it as high as possible if playing games. When things get busy on screen, that 56fps starts to drop really quickly. It's not the upper limit that's important, but the floor.
[Captivate Android Development] Kubernetes:
Is there something in SLC that makes it attractive to Android devs?
[Captivate Android Development] cruiserbax:
reading this ramble about fps cap of our eyes almost made me sick lol seriously! ok this last one is the ebst explanation of it so far. The fact and bottom line! is that our eyes interpret the light reflected (sometimes refracted) off of objects or the remanding light when passing through objects. Light that our eyes catch is a CONTINUOUS! yes it is both unlogical and simply not tru that our eyes are caped as to how many fps we can see LOL wow.... reading this stuff was pretty funny. there is no cap on how many fps the human eye cap see because as already stated they interpret light and it is a continuous thing not frames! so imagine it like this. like the individual quoted above is explaining, games at higher fps seem smoother and more connected because the more fps the for CONTINUOUS! it seems. with all that said, everyone is different yes but having amazing of poor vision has to do with things such as the inability to interpret certain colors or the fucos of your vision (blury) and is not at all linked to how many fps one might "see"
[Captivate Android Development] Cezar`:
yupyyyy!!!!

Yeeeeeyyyy!!!!! Long Live Our Beloved Developers!!!!!!!!!!!!!!!!!!!!!!!!!
[Captivate Android Development] newter55:
Nice work sombionix....also nice rom you have for 2.1 there. I like the startup and shutdown sounds.....but my wife was like....wtf r u doing with your phone now...lol

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] topshelf95:
lol wish I'd paid more attention in school in stead of partying all the time. I would probably have a much higher chance of saying im sitting right next to someone like you or dg rather than being relegated to only rubbing shoulders in an online forum. :D Who knew I'd be into this stuff 10 years later? ;)
[Captivate Android Development] Dani897:
Finally some sense in this argument. Ive had similar arguments over pitch perception of the human ear.( im a guitar player) But in the end unless you are a medical researcher its all nonsense. Haveing a fastet gpu is always good becauge you have a buffer. Even if it is faster than nesesary 90% of the time he 5 -10% of the time tha things slow down is what will be noticed. Also it means games with better graphics will evenyually be developed. There faster phones on the way so this will help us keep up with the competition in the next two years before our cotracts are up.

I agree that the 120 and 240 hz tvs are more to do with the 3/2 pulldown and interlaced content. It helps reduce distortion. And ill bet the frame rate potential of the eye is greater than 30 fps but most people generally wont notice a lack of smoothness at 24 fps but some may notice a diference when a/b compared to a higher rate.

And im not sure that the increase they see in frame rates is beyond what we were already doing with prior overclocks. I havent yet to see a benchmark foe android that will continuously pull the framerates low enough. I think they may have removed the 56 fps cap and allowed the benchmarks to work properly. Some of the quadrant tests are good. The one with the planet and moon isnt. Nenamark had a bug but now they fixxed it and we can pull over 50 fps. I havent ran an overcloced benchmark in nena mark since before thebug fix but i done expect it to show the full potential. Neocore isnt intesive enouh. We really need a fare test with no fps cap on either. Run this kernel at stock clocks and then again at full speed. Not stock kernel vs this kernel. That or create a new open gl benchmark that call keep the fps down to about 40 for the entire duration.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Cezar`:
Sorry guys, I cant keep my mouth shut :D but do we have an ETA on the 1.6 GHz OC CoG?
[Captivate Android Development] newter55:
Dani,

Neocore gave me 78fps with the kernel, sombionix shows a screenshot in the original thread with higher results...in the low 80's..this I could not replicate but the other benchmarks I could...mflops, quadrant, etc

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] newter55:
Just flash the kernel and see if your phone will handle it, only minor issues with mapping buttons, etc,that have been posted here ;)

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] Kaik541:
odd, I don't remember saying anything about not seeing a difference between 30 and 60. I remember saying a difference between 60 and 78 means little to me. I never stated it as fact, either, just my understanding of it. also, the reason 60 FPS looks more vivid is because that's closer to how the human eye interprets things (and oddly, it looks fake because most broadcasts are shown at about 24 FPS, so we aren't used to it). also, I can't speak for 120 hz TV's (nor did I say anything about them) because I've never used one. on top of that, you can't just say "ignore interpolation" when that itself changes how the screen looks/acts. and to the best of my knowledge (again, limited because I don't give a damn about framerates above 60), the pulldown ratio also affects a lot of how our eyes interpret it, which isn't the same as FPS.
[Captivate Android Development] newter55:
Perhaps the op needs to rename this thread .. Everything you wanted to know about fps....;)

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] Johnzai:
Seriously

It's not a matter of where he grips it, it's more a matter of air/speed velocity!!! :rolleyes:
[Captivate Android Development] shep211:
I didn't even know designgears was from slc. I live 25 miles out of slc but grow up in slc.
[Captivate Android Development] Chief Beefalo:
What does "FPS" stand for?

/s
[Captivate Android Development] newter55:
http://tinyurl.com/2uo2vsg ;)

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] Athailias:
It must be fate. I was stationed at Hill afb in Utah!
[Captivate Android Development] fatttire:
Not to get side-tracked - well - okay this is side tracked and technical but saying vision is related to fps is entirely appropriate (not talking about lenses here). Your retina does an insane amount of data processing. For a little forlay into that, just Google "center surround receptive field" doesn't explain fps but lets u know how complicated your retina is and there is more research on that subject. Not just in your brain.

I agree with most of what peeps said above.
[Captivate Android Development] Dani897:
What's your afsc? Im not at hill but I might have friends there.

Edit: Also I still don't know where to download the kernel. Does someone have a link?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] drancid:
Frame

Per

Second
[Captivate Android Development] joeybear23:
lol

I wonder how many people cught that one...
[Captivate Android Development] opcow:
Only we cool people.
[Captivate Android Development] Cezar`:
anyone still has this kernel? wanted to see if my Captivate will burn
[Captivate Android Development] insaneturbo13:
*turns on tv*

"in other news several reports of people with 3rd degree burns around their waste but you will never guess what the cause is. the new galaxy s line of phones from samsung are reportedly exploding inside of peoples pockets, when asked about it they all agreed that they wanted a faster phone with a working gps and soft keys that work, and in the attempt for fix these with several modifications they will never have any children. what a turn of events... all we can gather out of this is that samsung had better try and fix these pretty soon"
[Captivate Android Development] Athailias:
AFSC is civilian. I used to be a 2A372. F-16 avionics. I was also stationed at Edwards as a cv-22 technician. South korea twice, Nellis AFB, Ft. Worth ARB, march ARB

As to the air speed velocity... What do you mean african or european?
[Captivate Android Development] bfgarzilla9k:
I second this %110!

I would love to see an OC Cog alternative, DesignGears!:o
[Captivate Android Development] JimmehDean:
lol, impressive that it's possible. but i'm with him.
[Captivate Android Development] Cezar`:
Oh man, we might see that pretty soon!! :))))))

This is hilarious ! Good job :D
[Captivate Android Development] TheTodFather:
So 1.6 is not happening. I kinda thought this was not right considering that unhelpful , raspdeep , and JAC have yet to stablize andthing of that caliber. Now that the truth comes it a little sad, i was def excited about it. Well at least we have another kernel developer/team that seem to be highly motivated so that is def a big plus!
[Captivate Android Development] heymanator:
Perhaps the Nexus S will be an oveclocked hummingbird. This would move it forward also hoping GPS is fixed.
[Captivate Android Development] stuff:
Only thing I don't understand is WHY do you all feel the need for an OC'd hummingbird proc? I mean geez, the 1ghz on it is quick enough.
[Captivate Android Development] newter55:
Same reason I wanted to put a chip in my car that was 335hp stock....because if it can go faster...why not. Don't need it all the time but hey its nice to know its there

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] sportedwood:
s4?..............
[Captivate Android Development] SeenNotScene:
Gaming FPS mostly. But yeah bragging rights are a part of it I'm sure.
[Captivate Android Development] DOAlaboratories:
Think about it. If e never had to push boundaries we'd never get anything developed. If we never tested the limits we wouldn't have CM, custom ROMS, or performance improvements. It's fun to see how far we can push the envelope and how much we can improve our phones. A little over a month ago, what did we have? Compare that to what we have now, and we've come a tremendous way in about 50 days (which is very short) by pushing the limits.

Sent from my Cappy using mental telepathy, *****ezz.
[Captivate Android Development] ULTIMA93:
Does Project Core have any plans of porting over to the Captivate like the Manhattan Project?
[Captivate Android Development] Ryukeima:
+1 to this, but apply to the entire world of science and technology.
[Captivate Android Development] shaolin95:
mmm by now I was expecting a ton of Roms at 1.6ghz ...oh well :-)
[Captivate Android Development] DemonWav:
What are you talking about? 1.6ghz OC works just fine, and it's stable.
[Captivate Android Development] TheTodFather:
it wasnt running at 1.6 it was a glitch in the readout. so they dropped that project and started another one. Project core
[Captivate Android Development] shep211:
Agenthex has a 1600 mhz kernel for fascinate. He says this is not the same method of overclocking as team whiskeys project. I do not have my new captivate yet but I will try his method out on Thursday when I get my captivate.

http://xdaforums.com/showthread.php?t=825414
[Captivate Android Development] DemonWav:
And who told you this? Cause Viralblack never said anything about that.
[Captivate Android Development] shaolin95:
plus a glitch wouldnt give you the benchmarks they were getting...something is not right.
[Captivate Android Development] DemonWav:
It's cause they did get it running at 1.6ghz, that's not a glitch or a lie.
[Captivate Android Development] newter55:
I ran it....it was definitely smoking fast and every benchmark, cpu monitor confirmed it was working....it was another problem they were having

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] Dani897:
I need to learn to edit the kernel. I understand the dividers and multipliers, I have a very basic grasp of code. But I don't have computer programming experience. I can program cnc machines for what that's worth.

I think I can learn to do this. Does anyone have any good books to read on developing or programming?

How dose someone edit the files in the kernel? Can they be extracted? Or must it be built from source?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Dani897:
Does anyone know if there is an over heat issue. There are reports that the phone slows. And my phone runs more stable at lower volts than stock. I figure the cpu is either getting too hot or the memory or other device can't keep up.

Id be willing to rig up a heat sink to test if its a heat issue. I just need a copy of the kernel.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] newter55:
Heat was not an issue while I was using the kernel. Uploading kernel now will post link in a bit.

Anything you do with this file, like flashing it to your phone, may have unintended consequences that you will have to deal with as you made the choice to download it and take the risks associated with modifying your phone. :D

Here is a link to the Kernel
[Captivate Android Development] shep211:
The dropped the project because the internal timing gets hosed. Making apps benchmark faster but the system was really slower and it also caused a few bugs.

List of some of the reported bugs.

High fps readings yet things look visually slow or laggy

Weak vibration occasionally

Animations out of sync or running slow
[Captivate Android Development] newter55:
Yeah it may have messed with some stuff but it was fast and was funny to show to my ipphone friends...lol

Sent telepathically using vulcan mind meld app.
[Captivate Android Development] TheTodFather:
Ta Da! THere you go guys sorry to bust your bubble. It was a glitch. If you would of read the Vibrant OP you would of got it. This is old news...

1.6 is only 1.2ghz. NEver was truly 1.6ghz. I know it hard to swallow but you got to do it and move on. :D
[Captivate Android Development] Dani897:
ok so no further development on faster over clocks then? disapointing. ill need to learn to do it myself. but by that time ill have the next greatest phone and a new contract.

thanks for posting, at least i can show it off.
[Captivate Android Development] TheTodFather:
What is interesting is what shep linked from the fascinate forums and their version of 1.6 ghz
[Captivate Android Development] Dani897:
i believe he is having a similar problem although his code is not identical it is similar. but his may run better overall.

its just dividers and multipliers. im not sure why it is not posible in unhelpfuls version. may have to do with some preset parameters he has, he gives you a table of clock speeds/volts to work with but it gets converted somehow into the divider/multipler tables

in unhelpfuls kernel it seems like after 1200 it doesnt change the multiplier but instead bumps up the front side bus because when i check the clocks that have been applied the gpu is also overclocked by the same additional percent as the cpu, and its why i cant get over 1248, the frontside bus doesnt like being overclocked but if the phone is at lower temperatures it will run.

i wish i knew more. and i wish the parameters could be editied through an app in real time like on my computer where i can set the front side bus clock and the cpu multipliers from amd overdrive. but i would also want access to the memory clocks like i can change in bios on a pc.
[Captivate Android Development] crazililazn:
"Edit 10/30 -

So, we are having distinct issues removing the timing error from the kernel while maintaining the integrity of the time system. So, being that the timing is much more important, we began rewriting it all from scratch. This is currently marked as Project Core in the same forums. Core is taking the best of the overclocking and fine tuning that this kernel has and combining it with energy effeciency and stability a daily driver phone needs.

So, we will be balencing the high end power thats desired and the low power use that is needed in this new project. With that being said, I dont believe that 1.6GHz (in my own humble opinion) is even remotely necessary for 99 percent of phone, let alone for daily use. This project is being succeeded by Core to make a power friendly daily driver kernel.

The kernel will still be available from the forums Alpha/Beta Download Section, but will not be supported as its being replaced by Core.

We found the redline Now we need to find the happy medium. If you enjoyed this release, youll love Core and Core with zMod."

quoted directly from Viralblacks OP. There was no mention about it being a glitch. you obviously have no fcking idea what you are talking about, so gtfo. People like you should be banned for having misinformed info and then acting like a jackass despite the fact that your info is not correct.

Just in case, if you are trying to troll, you suck. lol.
[Captivate Android Development] TheTodFather:
1.6 huh? well this is comming from the guy who built Manhattan project, morphic . Does this help any?

I hate to break it to you, you morficed your kernel.

you are running a stable 1.2GHz, if you have time drift or not i didn't even look, but the formula for Fout is MDIV * FIN / (PDIV * 2^1-SDIV)

if MDIV of 250 and PDIV of 6 gives is 1GHz, we can verify that FIN, the input frequency, is 24MHz.

So 24*400/(8*2^(1-1)) gives us 24*400/8 (2^0 is 1, so we do not change PDIV)

24/8 is 3 , 3*400 is 1200

So you like me, missed how they calculate FOUT, i got it finally right when unhelpful linked me to the samsung pdf on xda.

I can run 1.4GHZ (true 1.4GHz if i turn on the phone in the fridge) and a 1.2GHz that scores quadrants around 1050ish, (more than i hear King Klicks 1.3ghz does...)

The 1.6GHz "Manhattan Kernel" had all numbers ad up to a theoretical 1300 quadrant score, 12.x in linpack, so you did not do as bad as me but it is all in all only 1.2GHz.

What we need to see if if phones like 266, 4, 1 better than 400, 6, 1

I can run stuff stable at 1.2 or 1.3GHz that do not work at all on other phones.

Also interesting that they give us a G3D divider while they also show in the same document that 3D is in the MSYS domain, while 2D is in the DSYS domain.

Either way, i think there is room to tinker to get more out of the phones, but we don't have it yet. Also a phone with better linpack scores that does not better in quadrant should be of limited use, as our phones are smooth as silk at 1.0 and 1.2 GHz and only games would benefit from more performance......or if google gave us a 3D desktop...YUM!

Hope this info helps. I only read the OP after being linked to it and figured if someone had pointed out the 1.2GHz already, the OP would be fixed by now