yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] durakbane:
Nice job, AgentHex. Its been interesting reading your progress on IRC and then see it released!
[Fascinate Android Development] mackeydesigns:
Yea, Not touchin this one till it's made for release, 1600 is a pretty serious speed to tinker with.
[Fascinate Android Development] saps:
What did you score?
[Fascinate Android Development] GoogleAndroid:
1172 and then 1128.
[Fascinate Android Development] saps:
Is that your 3D score?
[Fascinate Android Development] GoogleAndroid:
No, overall.
[Fascinate Android Development] phoenx06:
OH DEAR GOD BLAZING SPEEDS.

We need to get voodoo integrated with this bad boy and we'll be rockin!

Thanks for your work!
[Fascinate Android Development] phoenx06:
Btw, the FPS cap is blown off. I hit 80 FPS in Quadrant :)
[Fascinate Android Development] aroy002:
Does anyone know though, if this is the same as the Manhattan Project that was scrapped in the Vibrant forums for inaccurately blowing up the cpu/gpu scores, or is it actually working properly?
[Fascinate Android Development] GoogleAndroid:
Agreed. Lagfix, ColorFix(with all fixes), and BLN.
[Fascinate Android Development] phoenx06:
I could go without BLN. I must be the only one that doesn't want it. The kernels with it make a terrible buzzing noise while on the phone and having the button lights on all the time has to drain battery like crazy. But agreed on the others :)
[Fascinate Android Development] saps:
No, not at all. This is just the OP doing it on his own
[Fascinate Android Development] saps:
You're not the only one with the lack of care about BLN ;)
[Fascinate Android Development] Agenthex:
Yes.

Correct. IRC users report that this kernel will not work properly with voodoo. Since this is literally <10 lines of code to change in the source, I'm sure it will be included in future releases. (My kernel source is a branch of jt1134's with birdman's initramfs.)

SetCPU reports 1595.8 MIPS

Unfortunately, there's not much tweaking to be done by you guys. Aside from making changes to the source code and recompiling, there isn't yet a good way to insert extra CPU modes and allow such fine control.

I've heard about this "fps cap," and I'm wondering if maybe it's just consistent hardware performance. I was able to modify the GPU divider to increase its clock frequency, so it may have simply been a limitation of the stock frequency.

Not the same project. I got my Fascinate not more than two weeks ago. Long time linux user/hacker.
[Fascinate Android Development] devlp1213:
so did you have to up the voltage on this or where you able to get this on stock voltage. I'm sure it's been upped but figured I'd go ahead and ask
[Fascinate Android Development] bL33d:
Wow i just got my phone so im alittle gun shy but this is impressive!
[Fascinate Android Development] PhoenixPath:
Thank goodness. Thought I was the only one hating on BLN.

Last thing I need is more lights from my phone in the middle of the night. Finally killed the battery-full notification. No need to add stuff on top of that now.

Edit: 78 FPS in Quadrant. Damn.... (SetCPU not installed) Seems to hang forever on I/O 1/4 file system writes, though...Showed an 1123 total score and then errored out (internal error). Odd...
[Fascinate Android Development] ibegary:
+1 on the hate BLN.
[Fascinate Android Development] zachsx:
Finally decided to nut up and try it. And all I can say is amazing job! My fps was up to 84fps and quadrant was 1389 .
[Fascinate Android Development] mackeydesigns:
So the obvious next question is gonna be, how does this compare to 1.2 Voodoo as far as lag, overall speed and performance, battery life, etc.

I'm sure it's very much in a beta state, but a lot of us are either running JT's or Dirk's 1.2 Voodoo and will need hard convincing to test/try this out.
[Fascinate Android Development] namebrandon:
This should be a snap to merge into a voodoo kernel build. In fact, I'd be surprised if it isn't already done, and being tested. Check IRC.
[Fascinate Android Development] BakaUnchi:
w00t
[Fascinate Android Development] saps:
As of right now its not been done yet wickedbeav was going to give it a crack
[Fascinate Android Development] shep211:
This was tested by team whiskey and they said that when you are manipulating the internal clock speed you can get to 1600 but its not really running at 1600 mhz. They canceled the project and are now using 1.200 mhz kernel. Is this not doing the same thing they did?

http://xdaforums.com/showthread.php?t=821514
[Fascinate Android Development] saps:
Apparently not. Linpack from whiskey was 12's Hex's has been 13's and scaling as it should.
[Fascinate Android Development] zeroxg4:
You also linked to the Manhattan project, which he clearly stated was NOT the same thing on the previous page.
[Fascinate Android Development] phoenx06:
First bug! My vibrate function started acting erratically. It would be soft sometimes, normal sometimes and sometimes not vibrate at all. Was working fine at first, but after a couple hours of using it, it started doing this. Switched back to dirrk's and it working fine now.
[Fascinate Android Development] PhoenixPath:
I would never have noticed...haptic is off on mine. :p

Good catch... If you go back to Hex, can you reproduce it?
[Fascinate Android Development] Kubernetes:
Not sure if that means anything. I'd like to see confirmation that this OC isn't running into the same issues as Team Whiskey's Manhattan.
[Fascinate Android Development] wisconsinated:
nice but touchwiz actually seems to be choppier with this kernel than the 1200 interactive bfq kernel - also any idea on how high the temperature can get with the 1600 before it starts to do damage to the phone? I think its great somebody is working on the 1600 mhz, would definately like to run the galaxy s full time at it if its proven safe, also I could only decide between 1600 and 800, not 1ghz, is there a setting where I can step it down to 1400, or 1300 or even back to 1ghz, or am I stuck at either 800 or 1600 with this kernel atm?

edit: btw, quake 3 upper fps' were 70-85 at 1600
[Fascinate Android Development] Kubernetes:
Can you run a test and play Angry Birds, maybe on a level that's very busy?
[Fascinate Android Development] GoogleAndroid:
I just came to post this. After a little bit, the vibrator gets very weak. I almost thought it was breaking. I flashed back to a 1ghz kernel from JT that I got in the irc and the problem went away and hasn't happened since.
[Fascinate Android Development] android53:
Things to look out for:

High fps readings yet things look visually slow or laggy

Weak vibration occasionally

Animations out of sync or running slow

If these are present then this is a port (or chance recreation) of team whiskey's kernel.

Do some testing people! If you don't get these problems then it could be big news, I see one difference atleast, this lacks the large memory score inflation
[Fascinate Android Development] KellyLewis3985:
LoL this guy. All you did is copy someone elses work, which is not always bad but you could at least give credit where credit has been earned. Play a 3d game the graphics are slow and choppy. Manhattan project was shelved due to the internal clock not being able to keep up with the processor. Which in the long run will hurt your phone.
[Fascinate Android Development] adrynalyne:
LOL back at you. He has been working on this in Irc for quite a while with a lot of trial and error. Prove that work was copied or shut up. Do you really think that team whiskey is some special dev team that does things nobody else can? That's ludicrous at best.
[Fascinate Android Development] android53:
Need more information to determine if this is just a port, don't jump the gun people
[Fascinate Android Development] TheTodFather:
Dude, your such a troll. Nice picture by the way. Sorry stud muffin but this has nothing to do with team whiskey or should i say morphics code. Before you come in yelling try doing a little research their bub! Just cause a 3d game lags has nothing to do with morphic kernel. Probably cause you running something in the background like jersey shore. LOL j/k Its all good . Chill man...
[Fascinate Android Development] TheTodFather:
Man those dudes are such douche bags... always jumpin the gun!
[Fascinate Android Development] xan:
I doubt its legit. 99% its not.
[Fascinate Android Development] Kubernetes:
You have no idea if that's true or not. The OP could easily have developed this independently. What's important is whether this has the same flaws as Manhattan, because if it doesn't, that's good news for the entire Galaxy S community.
[Fascinate Android Development] KellyLewis3985:
Reguardless of what you may think or say, the op knows what I'm saying is true. Show respect to the creator thats all I'm saying.
[Fascinate Android Development] suppliesidejesus:
So, in the event that you are wrong, will you apologize to the OP for falsely accusing him?
[Fascinate Android Development] saps:
1600Mhz is real. This is from wickedbeav's test2 kernel over on the IRC:

Battery life seems pretty decent too. I benched it for an hour and used like 15% battery not bad.
[Fascinate Android Development] Diversion:
I'm seeing NO slowdown in gaming - the opposite.. Angry Birds is silky smooth... much smoother than stock kernal. However, I too am seeing some funkiness in the App drawer.. sometimes it's normal.. sometimes it's jerky.. nothing major tho.

Haven't had a FC yet either.. Although my particular Fascinate seems to overclock a lot better than my fiance's Fascinate.. She'll get FCs at 1200 or more.. but fine at 1100 and under.. whereas I was previously at 1250 and now this 1600 with no issues.
[Fascinate Android Development] krylon360:
Hey guys. Just thought I would swing by. This thread was tweeted to me.

I just talked with morf, to see if it was his code.

Though it is not, it is very similar, and he wanted to let you guys know, that the same mistake was made. Your phones will read 1.6 and will bench like it's 1.6, but the system will slow down.
[Fascinate Android Development] Kubernetes:
Well, that's poopy.
[Fascinate Android Development] saps:
Can you expand upon that statement / define slow down?
[Fascinate Android Development] Kubernetes:
Here's how Viralblack explained it in the Project Manhattan thread:
[Fascinate Android Development] morfic:
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 ;)
[Fascinate Android Development] TheTodFather:
sup morphic good to see two bright minds extrapolating on ideas in here... Look forward to seeing dev '.
[Fascinate Android Development] syaoran12:
Anyone else having an issue downloading from the link?
[Fascinate Android Development] Agenthex:
I did not know this, and I still have not seen the samsung whitepaper.
[Fascinate Android Development] zachsx:
Do it from your computer sir
[Fascinate Android Development] RacerXFD:
Anyone else have freezing issues with 1600 MHz?

I guess my phone doesn't like anything above 1GHz. :(
[Fascinate Android Development] morfic:
http://xdaforums.com/showthread.php?t=745877&highlight=s5pc110

sorry it took me so long, i grepped my logs, but forgot -i on unhelpful's nick, Unhelpful vs unhelpful w/o -i == fail

very interesting doc, i think i barely scraped the top of what's there, section 3 is what you want read how all the clocks relate.

based on some clocks not mentioned, we can only go by what the dividers are to get what clock they are derived from based on source.

also note how 100mhz is derived from mpll not apll, i tried pushing cortex more by dividing others more.

and always do a sanity check and get m, p, s right first, then see the dividers work out, and then once you love your kernel, make sure clock does not drift, i now use ntp client for that.

i have wondered what's possible if we use apll that is != arm

but that's all just hot steam for now. i'm pretty tied up with $wife, so i can't try every possibility i have in my head.

pushing to a real 1.4GHz like i said is working in a fridge, but if we could indeed lower gpu w/o taking cortex down with it, that would be sweet. could be used to clock 100mhz way down for more battery, more battery is how it all started.....
[Fascinate Android Development] saps:
Not at all

Sent from my 1.6Ghz voodoo fascinate
[Fascinate Android Development] cruiserbax:
What is your MOS if you don't mind me asking? ex-19D now 25U myself, looks like a hospital, no? IED?

EDIT: I only ask because I gather that last guy seemed to have misinterpreted your profile pic for a beach shot or something, who knows lol. In any case glad to see you're still alive and hopefully not permanently disabled or anything.
[Fascinate Android Development] adrynalyne:
I think you owe the op an apology
[Fascinate Android Development] KellyLewis3985:
11B anti tank grenade to my winshield. Medically retired in 2 weeks.
[Fascinate Android Development] KellyLewis3985:
You are correct good sir. To AgentHex, I apologize for jumping the gun here. Now lets get this figured out. LOL
[Fascinate Android Development] adrynalyne:
Preferably without refrigerators involved!
[Fascinate Android Development] KellyLewis3985:
LOL. +1
[Fascinate Android Development] morfic:
reads so familiar :(
[Fascinate Android Development] morfic:
maybe work across the derivative model boundaries will bring some good to all SGS.
[Fascinate Android Development] cruiserbax:
Sorry to hear that, at least you'll get your due benefits! I went through PEB/MMRB back in July but eventually was able to appeal the findings and remain on active duty. Sorry to get off topic folks! back on track now!

Airborne!
[Fascinate Android Development] morfic:
What do you have against refrigerators? ;P
[Fascinate Android Development] adrynalyne:
Nothing, I just can't find a power cord long enough!
[Fascinate Android Development] Agenthex:
I gave you the source code that I modified and told you exactly how I modified it. How, exactly, is that stealing someone else's work?

Just to make you happy, I want to thank all of the people who have ever contributed anything to the Linux kernel. Ever.

EDIT: Hadn't read where Kelly realized it wasn't a port or derivation. It is JT1134's source branch that I modified, though.
[Fascinate Android Development] phoenx06:
+1 :)

10chars
[Fascinate Android Development] zachsx:
Can you guys tell me how your running setcpu? What MHz and is it ondemand or conservative? Thanks

Z
[Fascinate Android Development] Daswolven:
Unless I missed something in this thread, SetCPU should be either autodetected, or custom set according to the indicated steps. Conservative is the only truly stable setting for us.
[Fascinate Android Development] zachsx:
Thanks you're a pal!
[Fascinate Android Development] Daswolven:
Okay, so I'm trying to keep up here. Is it then a good assumption that the over-clock on this is somewhat artificial beyond 1.2? If so, can this be reworked at 1.2 with the removal of the FPS cap, or is that also artificial? And if so, can this be compiled with Voodoo at a true OC without the FPS cap?

Pardon the questions if they're somewhat ignorant, just trying to feel the situation here out from a coding illiterate perspective.
[Fascinate Android Development] mackeydesigns:
+1 ^I'm with stupid. lol, just kidding das. <3
[Fascinate Android Development] kingsnap:
I just installed and did a Quadrant and got, 1346 in 3d, 466 in 2d, 858 I/O, 1937 Memory, 1228 CPU 1167 Total.

Running good right now, will let it run through the night.

I did the install via Rom Manager with out a hitch no clear cache or data.
[Fascinate Android Development] Mean Bro Greene:
I've been running this for about 6 hours with light to moderate use, and if anything it feels slower(to me) than the 1.2 ghz kernels. Quadrant returns 3045 with the ext2 lag fix in place, linpack also returns nice results at 13.33. However, anytime the CPU or GPU are genuinely pushed into a taxing scenario, I get noticeable lag. These are my personal experiences so far. I'm also experiencing the vibration problem that was mentioned early. Haptic works about half the time.
[Fascinate Android Development] RacerXFD:
if you have ever done overclocking you will know that the speed of the processor is equal to the multiplier set on the chip times the clock speed of the front side bus.

Anyways, the arguement is that a slowing FSB slows down all of the other components of your phone. Which is bad because it means that the ram and all other functions on the device that rely on the fsb slow down even when the processor is clocking at a high speed.

FSB slowdown is not a good thing...

Disclaimer, I am not an electrical engineer so take this with grain of salt.
[Fascinate Android Development] neyenlives:
Or..is it possible the actual data bus width on the mainboard cannot accomodate the bandwidth throughput. What about the memory? Can it keep up the same scaling as the CPU? What about the GPU? I dont know if there are any technical documents on the hardware in our devices, but there could be hardware limitations tied to the FSB or base clock that cannot keep up. What about memory timings and voltages? What about core temps? Number one rule in overclocking is to make sure you can get rid of excess heat. What's the thermal envelope of the hardware within the device? What is it running stock? What when overvolted and overclocked? All of these are items that are normally fairly well defined before people set out to overclock in the pc world. Where is all of this info on our devices? Or are we just jacking it up and hoping for the best?
[Fascinate Android Development] Mean Bro Greene:
Interesting. While this is by no means the first time I've overclocked a processor, I've never taken the time to actually look into the mechanics behind it. Thanks for your input. The scenario you laid out definitely seems to be what's occurring. Well, for me, anyway.
[Fascinate Android Development] morfic:
You have a input frequency with multipliers ans dividers to set the in this case 1.2GHz, from there, the posted array of numbers are all dividers.

the closest to fsb is likely the MSYS frequency as the cortex core runs in sync with that frequency, the exact terms for the bus you would have to get from the samsung pdf linked earlier.

Thinking of all frequencies as fsb*multiplier is how you easily end up setting incorrect frequencies.

There is a frequency Fout of 1.2GHz (multiplied and divided from 24MHz input frequency), all else is divided from that product.

Having said that, by not changing the msys divider, and increasing the bus speed, the cortex core (and 3D, and all else in MSYS domain) runs on, gives better overall scores.

It seems analog to how not all phones like 1.2GHz, even less like this MSYS OC.

I plan on creating sort of a matrix in the .config to easily build all of those, then it's up to the user to see which kernel they find is most stable.
[Fascinate Android Development] RacerXFD:
See, I told you to take what I was saying with grain if salt. :)
[Fascinate Android Development] jayfr76:
Ok, so i tried the kernel, indeed quadrant was amazing for non voodoo. What i would like to know is simply this. I have absolutely no luck with setcpu. Seems to kill the phone no matter which oc kernel i have used. I am not a dev by any means, just appreciate the work you all have done thus far. So the question is can the kernel be changed to a stock clock speed with the fps cap removed??????
[Fascinate Android Development] martian21:
I seem to recall the devs stating in IRC that SetCPU is NOT compatible with this kernel.
[Fascinate Android Development] zachsx:
I'm using it and it works fine :/
[Fascinate Android Development] pkopalek:
I'm getting 404 file not found. I'm anxious to try this.

When I go up a directory, it appears to not be there:

https://agenthex.com/users/hex/files/
[Fascinate Android Development] jayfr76:
Ok so then, if this is an artificial 1600 then how can it be used without setcpu? Or do i have it all wrong? I have been following this thread and have to give props to the dev for this work, but my question was not only about this kernel. It was also about the fps cap. Throughout this thread I keep seeing people using setcpu. So i had to ask.
[Fascinate Android Development] Agenthex:
I've edited the frequency table. There are five power modes. I replaced the 1GHz power mode with a mode that accidentally tricked the system into thinking it was running faster. I'm working on an actual real overclock, but a few of the testers in IRC got a taste of an unstable battery hog.
[Fascinate Android Development] jayfr76:
Awesome work so far Agenthex, wish I had some coding skills to help out. But A. I suck at math and B. dont know where I would find the time. The extent of my android knowledge is left at scripting and modding zip files to load what I need them to.
[Fascinate Android Development] marcviado:
is the link down?

i keep gettin error 404

not found

ami to late to try this?
[Fascinate Android Development] morfic:
the fps cap, if it's real or not, i don't know.

if the system clock skews to where a second on the phone takes longer than a second in reality, the phone still can manage the same amount of frames as it always could, so the benchmarks count more frames per that longer second and the fps go up proportionate

clock the chip correctly, you get a stable 1.2GHz and the correct scores.

about 30% of users might get lucky with a 1.3GHz kernel

about 1% might run 1.4GHz for a few minutes in their fridge

all room temp 1.4, 1.5 or 1.6GHz kernels are miscounts by a drifting clock (@Samsung: why put in a RTC clock source but be affected by changed bus speeds???)

at this point, no room temp 1.4GHz or above kernel is out, those that claim to be are innocent mistakes made while setting the dividers in the source

my Vibrant belongs to the lucky 30% category

if your phones benchmark in line with the expected 1.6x scores compared to 1GHz scores, install ntp client, check the offset, find numbers like 12 or 500 secs off, guess what? you got a drifter.

if your clock does not drift, i bet your scores are closer to 1.2x the 1GHz scores

I know this to be true for Vibrant (my own oops), Captivate (this thread) and Epic kernels.