Develop Bugs

ext2 does help! score 2221 + NAND INTACT *EDITED 21AUG 2018HKT

I know that many people worry about frequent reads/writes will damage the NAND, so I began a new test days before without using the NAND
this time, I switched from rfs to ext2, with some mods to the kernel to load the ext2 partitions, no OC
note that this is only serve as a real case to show u ext2's performance and to prove that rfs is one of the problem areas. u guys can implement it your ways with further improvements, perhaps with ext3, ext4, yaffs, etc
EDIT: 21AUG 2018HKT
- some ppl said that it is easy to cheat the score obtained in quadrant by moving around the quadrant's data files. yes, i agree that. but it wil be much easier to edit it in photoshxp for even 30k score. and although some ppl said the score itself is meaningless, which i agree with it also, but it provides a mean to let u know how ur phone is performed. it is not an indicator for whether ur videos or sounds can be played smoothly since it depends on a lot of things as well
- also note that if u formatted the /sdcard in different file format, some of the recovery mode functions wont work since it will only mount rfs/vfat, so u have to modify the stock recovery or rom manager's recovery manually, or by mounting the partitions via shell
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

so this will lead to a whole new type of lagfix?

So this is the base for the ultimate lagfix?

daijirok said:
so this will lead to a whole new type of lagfix?
Click to expand...
Click to collapse
well, I dono. let you guys decide

Nice to see the score split up in the different parts. It shows that the inital I/O of GS wasn't really that bad. Also i guess we can expect about 750 points of CPU score with Froyo (looking at the Nexus), so maybe a 3000 score is within reach .

toca79 said:
So this is the base for the ultimate lagfix?
Click to expand...
Click to collapse
i dono think so, more to come i think

mbr01 said:
Nice to see the score split up in the different parts. It shows that the inital I/O of GS wasn't really that bad. Also i guess we can expect about 750 points of CPU score with Froyo (looking at the Nexus), so maybe a 3000 score is within reach .
Click to expand...
Click to collapse
right, i saw one with 27xx or something already with old tricks. so 3000 should not be a problem with 2.2

ykk_five said:
i dono think so, more to come i think
Click to expand...
Click to collapse
Great work anyway!!

ykk_five said:
right, i saw one with 27xx or something already with old tricks. so 3000 should not be a problem with 2.2
Click to expand...
Click to collapse
ykk_five, first, many thanks for the tip. The score of 2711 was done during your first initial suggestion, where the fix was temporary. In additional, I happen to have the overclock kernel (by raspdeep) installed. Hence, I just ran it to see how much mileage we can get from the SGS.
Having said that, RyanZA and Chainfire had implemented excellent lagfixes. With your latest test, I'm really not sure how much more improvement we can get. Many of us are now very happy with what they have, and I am not sure if there are anymore juice to be squeezed out from this.
Let's hear it from the more experienced users, and perhaps this latest discovery might be as exciting as your first.
Greetings from Singapore.

g00ndu said:
ykk_five, first, many thanks for the tip. The score of 2711 was done during your first initial suggestion, where the fix was temporary. In additional, I happen to have the overclock kernel (by raspdeep) installed. Hence, I just ran it to see how much mileage we can get from the SGS.
Having said that, RyanZA and Chainfire had implemented excellent lagfixes. With your latest test, I'm really not sure how much more improvement we can get. Many of us are now very happy with what they have, and I am not sure if there are anymore juice to be squeezed out from this.
Let's hear it from the more experienced users, and perhaps this latest discovery might be as exciting as your first.
Greetings from Singapore.
Click to expand...
Click to collapse
thx a lot, i really hope that u guys will enjoy it!

I have a consistent score of 990+ without any lag fix on a froyo ROM. Previously I used a lag fixed JM5 which score 2000+, however with everyday use the froyo ROM seems snappier. Good to see all efforts to speed things up and eliminate the lag, but I'm not sure higher benchmarks score translate to a better user experience.
What I'm hoping for now is a fix than enables smooth scrolling of contacts & call logs seen on the desire.
Good work though!

Frostfree said:
I have a consistent score of 990+ without any lag fix on a froyo ROM. Previously I used a lag fixed JM5 which score 2000+, however with everyday use the froyo ROM seems snappier. Good to see all efforts to speed things up and eliminate the lag, but I'm not sure higher benchmarks score translate to a better user experience.
What I'm hoping for now is a fix than enables smooth scrolling of contacts & call logs seen on the desire.
Good work though!
Click to expand...
Click to collapse
u can compare the IO stat, although it's a roughly comparison

g00ndu said:
ykk_five, first, many thanks for the tip. The score of 2711 was done during your first initial suggestion, where the fix was temporary. In additional, I happen to have the overclock kernel (by raspdeep) installed. Hence, I just ran it to see how much mileage we can get from the SGS.
Having said that, RyanZA and Chainfire had implemented excellent lagfixes. With your latest test, I'm really not sure how much more improvement we can get. Many of us are now very happy with what they have, and I am not sure if there are anymore juice to be squeezed out from this.
Let's hear it from the more experienced users, and perhaps this latest discovery might be as exciting as your first.
Greetings from Singapore.
Click to expand...
Click to collapse
This kind of solution should be a lot better as it doesn't use any space (or so i undertand).

pls read my newly added comments at the 1st page
EDITED 21AUG 2018HKT

So what exactly did you do to get these new scores? Did you format the /data partition as EXT2 to get these scores?

I understand someone may not like to spend time to answer noob's questions. But what is the point to show just the Quadrant score and then tell others you have done something in this Development board? Should it be presented in a more technical way?

Yes please give some more details on what exactly you did.
Sent from my GT-I9000 using Tapatalk

I wonder if Froyo will bump this score even higher.
I just performed a test on the HTC Desire, with newly installed Froyo (2.2). On the scale above, it scores between the Nexus and the Droid, but closer to the Droid. What intrigued me is that the reason the score was lower than the Nexus, was the CPU score. The other colours were about the same as the Nexus One. The CPU part was still bigger than anything else (up to the 1/4 of the green part on the droid below it) but about 4/5 that of the Nexus. Sorry I couldn't post a screenshot.
Which is really weird, since the two devices share the same CPU. (are the reference scores accurate?)
EDIT: I tried running it again, and I got a higher CPU score this time, so now it almost matches the Nexus (up to 1/2 of the green part on the Droid) Overall score 1301. So scratch the above comment, I guess the reference scores are the highest you can get.
Now in the picture of the Galaxy above, the biggest part is the IO score, which is logical because of the modification, but the CPU score is very small. So assuming that Froyo will bump up the cpu part like on the Nexus and the Desire, we'll be looking one hell of a record score, right?
Has anyone with a JP firmware tried this lagfix?

The better CPU scores on FROYO are due to the JIT Compiller! The JP firmwares Have JIT but it is not active still! Or atleast not to the point it is on the N1! I hope that the final firmware will have full speed.

@ykk_five - I'm not really sure what NEW point you're making, but I love that you're still working on this!
Didn't we pretty much already know that rfs was the appaent problem with the i/o? You proved that early on as far as I can tell. Paul O and mimocan assumed it was slow hardware with their fixes, but you showed that a different fs fixed it on the same memory space. Some of us have been clamoring for a reformat of the internal rom space as the solution since you first posted your findings.
What I find more interesting is that the i/o on the stock SGS in Quadrant isn't that bad - it appears comparable to most of the other phones, except the Motorola Droid X! I wonder why it's so fast on that one.
My own earlier READ-speed testing done with reading a 200mb data file from the command line with the dd command showed that read speeds on RFS internal /data partition vs ext4 on sdcard partition were pretty close. Seems like RFS can serve up the reads pretty darned fast (Class 6 speeds or better). Well over 13Mb/s from my post over on Modaco:
Code:
BEST SPEED ON EXTERNAL SDCARD EXT 4 = 15.79 MB/S
BEST SPEED ON EXTERNAL SDCARD FAT32 = 15.6 MB/S
BEST SPEED ON INTERNAL SDCARD FAT32 = 13.1 MB/S
BEST SPEED ON INTERNAL ROM AREA = 13.6 MB/S
Since we're now doing the loop mount ext2 on top of RFS fix, I thought I should test the read speeds there. I ran four tests, they ranged from 1.1MB/s to 8.1MB/s:
Code:
BEST SPEED ON LOOP MOUNTED EXT2 /DATA/DATA = 8.1MB/S
That's right, it's 50% SLOWER to read files off the ext 2 /data/data partition (with RyanZ's 2-3 method) than just raw RFS on the best read, 1/13th of the speed in some cases!
Seems hard to imagine how this fix speeds things up other than cacheing writes, which shouldn't impact the opening of files, unless the lag in the first place was some sort of delay reading the files while other things were written to the disk.
With that in mind, apparently the Quadrant speedup is in the WRITE part of the i/o tests, wouldn't you agree? That would be because of the cached writes ext2 does vs RFS?
If this is the case, then high Quadrant scores aside, none of these fixes should really do much to improve the normal look and feel of using the phone, as you alluded to with your comment about playing back videos/music. RFS or ext will serve up the data at more than we need it.
It makes me wonder why so many of us assert that the phone is indeed much snappier on opening apps and stuff. I'm sure it's not a placebo for me, the phone definitely feels faster with any of the lag fixes we use.
What we really need is to see a breakdown in Quadrant's i/o benchmark that distinguishes between the read and writes.
I really don't like that with all these fixes, no one really knows why they speed the phone up.
I'm tempted to go back to just stock JM5 and see what happens.

60 fps frame rate cap

If I remember correctly the Evo had a frame rate lock. Even if it didn't does any one know if its being looked into as a mod to have it removed? The quadrent scores will probably be greatly effected since almost all the videos stay right at 60fps. Lets uncork this bad boy and let it run free any info on it I would live to hear. Mahalo, Wayne

bluefire808 said:
If I remember correctly the Evo had a frame rate lock. Even if it didn't does any one know if its being looked into as a mod to have it removed? The quadrent scores will probably be greatly effected since almost all the videos stay right at 60fps. Lets uncork this bad boy and let it run free any info on it I would live to hear. Mahalo, Wayne
Click to expand...
Click to collapse
I don't think it is locked in the same sense that the Evo4G was actually capped. While my FPS2D scores are typically dead-on at 60 it bursts as high as 65 at times, the EVO4G did no such thing.
God, thanks for reminding me of that...that was so frustrating. Especially HTC's response.

daneurysm said:
I don't think it is locked in the same sense that the Evo4G was actually capped. While my FPS2D scores are typically dead-on at 60 it bursts as high as 65 at times, the EVO4G did no such thing.
God, thanks for reminding me of that...that was so frustrating. Especially HTC's response.
Click to expand...
Click to collapse
what made the response so funny was as they were claiming it couldnt be done, it was already done and made them look STUPID(er)!!!

It's more than likely software capped much like the original Epic.

So that means that in theory it can be uncorked by a a dev some how I hope

It was done on the mesmerize/fascinate with the Glitch kernel. Upped the fps cap to 65 from 60. It might be worth investigating...
Sent from my SPH-D710 using XDA App

phones looking better and better.
heat issues
iffy battery
Crummy radio/wifi range
apps/games closing out bug
screen on delay
now a frame rate lock?
dayum, might wait a lil longer before i upgrade...

malibu_23 said:
phones looking better and better.
heat issues
iffy battery
Crummy radio/wifi range
apps/games closing out bug
screen on delay
now a frame rate lock?
dayum, might wait a lil longer before i upgrade...
Click to expand...
Click to collapse
A critical eye viewing in from the outside might see this as some sort of disaster of a phone...but I don't experience any of this at all, and for some of those items quite the opposite. There are always issues to be worked out when you get a phone on/right after release...that is ALWAYS to be expected...and always remember that the vast majority who are pleased and not having problems typically won't say anything at all...
Personally I don't know about this frame-rate lock...if we can go faster, by all means...but...60 is pretty damned good, though ~65 solid (with a low stdev) would be phenomenal. Someone always crawls out of the woodwork to point out that the human eye isn't capable blah blah blah much above 24fps anyway....but....when I flashed netarchy's kernel on my NS4G and my FPS went from ~60 to ~65 I noticed it right away and it was amazing....so, I won't say so much that it is capped as much as it could be tweaked to go higher. 60fps really is pretty damned good.

daneurysm said:
A critical eye viewing in from the outside might see this as some sort of disaster of a phone...but I don't experience any of this at all, and for some of those items quite the opposite. There are always issues to be worked out when you get a phone on/right after release...that is ALWAYS to be expected...and always remember that the vast majority who are pleased and not having problems typically won't say anything at all...
Personally I don't know about this frame-rate lock...if we can go faster, by all means...but...60 is pretty damned good, though ~65 solid (with a low stdev) would be phenomenal. Someone always crawls out of the woodwork to point out that the human eye isn't capable blah blah blah much above 24fps anyway....but....when I flashed netarchy's kernel on my NS4G and my FPS went from ~60 to ~65 I noticed it right away and it was amazing....so, I won't say so much that it is capped as much as it could be tweaked to go higher. 60fps really is pretty damned good.
Click to expand...
Click to collapse
In the history of cell phones no phone has ever been perfect. There are always have been and always will be something to complain about with each and every new phone that comes out. They are made by humans and used by humans. That means some problems may be build / design / software / or user error.
That being said this the GSII is the number one phone in the world as of right now.
Samsung Galaxy S II

stangdriverdoug said:
In the history of cell phones no phone has ever been perfect. There are always have been and always will be something to complain about with each and every new phone that comes out. They are made by humans and used by humans. That means some problems may be build / design / software / or user error.
That being said this the GSII is the number one phone in the world as of right now.
Samsung Galaxy S II
Click to expand...
Click to collapse
Amen!
Nothing is and will ever be perfect. That's just the way it is. This happens with cars , houses, other electronics and software and so on...There is always something what "could have been better" or different. Especially when they first come out.
I understand it can be frustrating, however we sometimes need to understand that the complexity of devices nowadays inevitably lead to some flaws. Hopefully they will fix this soon.
As far as the framerate cap goes...I hope no dev is going to take time to change this especially when we have other more important things they could invest their time in.
60fps is BUTTERY SMOOTH and the GS2 does a very good job of hitting that mark most of the time in most apps and games as opposed to 99% of the devices out there that can't. Why waste time on lifting it? So you can score higher Quadrant scores? Completely pointless!

We need apps that utilize the dual cores and gpu, efficiently.
I don't think we are capped because I have seen a few bursts of 70 in quadrant. I think we need to utilize the hardware we have fully, then worry about what may or may not be limited.

malibu_23 said:
phones looking better and better.
heat issues
iffy battery
Crummy radio/wifi range
apps/games closing out bug
screen on delay
now a frame rate lock?
dayum, might wait a lil longer before i upgrade...
Click to expand...
Click to collapse
The door is over here troll -> http://****off.com

When you superhuman eye can see more than 60fps, lemme know. FYI, movies in the theater play at 24.

I just think it would be nice to have the cap removed ... we are all here to tweak our phones and mod them which is really fun to do! Just something fun that I would like to see happen. Perdormance is amazing and butter already and this is the best phone out right now. I don't actually have a single complaint about it! Just like modding and tweaking

bondosho said:
When you superhuman eye can see more than 60fps, lemme know. FYI, movies in the theater play at 24.
Click to expand...
Click to collapse
you ever look at and old school crt monitor at 60Hz?
i do agree with you that on such a small screen, more that 60fps is more for epeen benches than actual performance.

madsquabbles said:
you ever look at and old school crt monitor at 60Hz?
i do agree with you that on such a small screen, more that 60fps is more for epeen benches than actual performance.
Click to expand...
Click to collapse
Bwhahahahaha your name made me lol!
Tbh I had a glimpse of "training day" run through my head when I seen your screen name
(carry on with the useless benchmark improvements)
Sent from my SPH-D710 using XDA App

comeatmebro said:
The door is over here troll -> http://****off.com
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
am i lying? are those not the top issues with this phone?
daneurysm said:
A critical eye viewing in from the outside might see this as some sort of disaster of a phone...but I don't experience any of this at all, and for some of those items quite the opposite. There are always issues to be worked out when you get a phone on/right after release...that is ALWAYS to be expected...and always remember that the vast majority who are pleased and not having problems typically won't say anything at all...
Click to expand...
Click to collapse
Im rocking the OG evo, and this isnt my 1st phone, so im well aware of "new phone" bugs, (see sig) but these top bugs/annoyances im seeing seem really bad to me. Cuz its stuff that would affect me daily, but everyone's usage varies. Im sure its an awesome phone as a whole thats y i lurk here to see whats the latest with mods to fix it or actually updates pushed by sammy. y'all too sensitive with peoples opinions on phones.

malibu_23 said:
am i lying? are those not the top issues with this phone?
Im rocking the OG evo, and this isnt my 1st phone, so im well aware of "new phone" bugs, (see sig) but these top bugs/annoyances im seeing seem really bad to me. Cuz its stuff that would affect me daily, but everyone's usage varies. Im sure its an awesome phone as a whole thats y i lurk here to see whats the latest with mods to fix it or actually updates pushed by sammy. y'all too sensitive with peoples opinions on phones.
Click to expand...
Click to collapse
Excellent point... The only bug that's serious to me is the random loss of service. That's potentially life-threatening. All the other bugs are just annoyances.

malibu_23 said:
am i lying? are those not the top issues with this phone?
Im rocking the OG evo, and this isnt my 1st phone, so im well aware of "new phone" bugs, (see sig) but these top bugs/annoyances im seeing seem really bad to me. Cuz its stuff that would affect me daily, but everyone's usage varies. Im sure its an awesome phone as a whole thats y i lurk here to see whats the latest with mods to fix it or actually updates pushed by sammy. y'all too sensitive with peoples opinions on phones.
Click to expand...
Click to collapse
No, I'm not mad, and no you're not right:
heat issues
iffy battery
Crummy radio/wifi range
apps/games closing out bug
screen on delay
now a frame rate lock?
Click to expand...
Click to collapse
heat issues = It's not really an issue at all. It gets barely hot, unless you're device is malfunctioned in which case you should return it
iffy battery = where the hell did you read this? If you're talking about the OS consumption at 50%+ then thats a lemon and needs to be returned. hence why only a very small percentage of people are having this problem
crummy radio/wifi = it's not on par with photon for example, but it's good enough, and not a deal breaker at all. I get 2-3 bars of 4g everywhere I go. As for as wifi I have no use for because like I said, i get 4g everywhere so I have no need for wifi.
apps/games = again, most likely a lemon, and needs to be returned
screen on delay = caused by sd card, and even though its annoying at times, its still not a deal breaker
fps lock = pretty sure it's not an fps lock. afaik most if not all android phones are stuck at 60fps. Also i'm pretty sure your og evo was locked at 30fps and you still bought it.
most of the things you described are bugs, and need to be returned to sprint. Phones are mass assembled and some of them will have these bugs, thats why you have a 14 day window to return the phone if you experience any problems.

comeatmebro said:
No, I'm not mad, and no you're not right:
heat issues = It's not really an issue at all. It gets barely hot, unless you're device is malfunctioned in which case you should return it
iffy battery = where the hell did you read this? If you're talking about the OS consumption at 50%+ then thats a lemon and needs to be returned. hence why only a very small percentage of people are having this problem
crummy radio/wifi = it's not on par with photon for example, but it's good enough, and not a deal breaker at all. I get 2-3 bars of 4g everywhere I go. As for as wifi I have no use for because like I said, i get 4g everywhere so I have no need for wifi.
apps/games = again, most likely a lemon, and needs to be returned
screen on delay = caused by sd card, and even though its annoying at times, its still not a deal breaker
fps lock = pretty sure it's not an fps lock. afaik most if not all android phones are stuck at 60fps. Also i'm pretty sure your og evo was locked at 30fps and you still bought it.
most of the things you described are bugs, and need to be returned to sprint. Phones are mass assembled and some of them will have these bugs, thats why you have a 14 day window to return the phone if you experience any problems.
Click to expand...
Click to collapse
This is exactly what I would've said, except the game/apps closing out thing is a legit problem (just not a big one). my gameboid emulator drops out randomly, but my snesoid emulator works just fine. I have a feeling that's a compatibility issue, but i'm also known for blowing smoke up people's asses
malibu, you need to understand that we on xda represent a minority of phone owners. Therefore, if it's a "hot topic" here, I can guarantee you that more than 50% of the owners of this phone have no freaking idea what you're talking about. Therefore, you cannot call any of these issues "hot issues" except LOS because LOS is like puberty...it'll eventually happen to everyone unless they're freaks.
If you don't wanna upgrade to this phone, that's fine, but please go bother the people in the forum of the phone you do plan on buying. Thanks!
As for this 60 fps lock....hmmmm
I don't think so

ROM Benchmark Scores

I got bored tonight and tested a few of the popular and recent ROM's for this phone. Below is the method of testing and the results.
I took these steps for -every- ROM tested.
Plugged phone in via USB to my computer and left it plugged in.
Factory reset using clockwork
format /system as well (i've seen a few rom's suggest this)
Installed ROM
Booted into ROM and let sit for 5 minutes without touching it
Stepped through the initial setup without setting up a google account (if applicable to the ROM)
Reboot
Let sit for 1 min
Installed AnTuTu Benchmark v2.6 from sdcard.
Ran AnTuTu Benchmark using default settings and selecting /sdcard/external_sd as the sdcard
This is NOT ment to imply one ROM is better than another. It's only intention is to share datapoints. Some of the ROM's are beta as well, so their final release may be different.
My intention is to show how ROMs perform based on the AnTuTu benchmark. I wish to use a ROM that is quick and efficient. Others may appreciate more eye-candy at the cost of performance. To each his own. So I hope some find this data useful.
Android Zombie v4.0 (7272)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Foxstar beta v1.0 (5689)
Revenge Of Macnut (5778)
Tuesday|Medieval|Midnight| (7136)
DARKSIDE:IGITAL::WARFARE v2.1 (5771)
Dewizzed-V2.5.2 (7045)
And just for kicks, here's my phone, running normally, fully loaded.
* Long time lurker, first time poster since I figured this may be a way to contribute to the forum.
* Also not here to promote any ROM. I'm unaffilliated.

Thanks!
Sent from my SGH-T989 using xda premium

Uh you know foxstar is the only one you ran at stock speeds? The rest are at 1700. Might want to re run that one.
Also you would have to run each test three to five times to get any sort of meaningful results bc the scores will fluctuate.
Sent from my SGH-T989 using XDA App

About the clock speeds, I did that on purpose. The purpose was to show the performance of the ROM as the creators intended.
Do you think running it multiple times will make a huge difference? I figured so long as I did the same steps for all ROMs it should reflect a decent standard.
Sent from my SGH-T989 using XDA App

matthewdavis said:
About the clock speeds, I did that on purpose. The purpose was to show the performance of the ROM as the creators intended.
Do you think running it multiple times will make a huge difference? I figured so long as I did the same steps for all ROMs it should reflect a decent standard.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
You did that on purpose? Interesting. You might want to put in bold the speeds you are running each test on. Seemed like a mistake if you ask me. All of those other roms do not come with default cpu max at 1700MHz.
Also, yes running them multiple times will make a HUGE difference. I have done it when bench marking graphics cards, cpu overclocks and with my phone. Try it....you will be very surprised.

G1ForFun said:
You did that on purpose? Interesting. You might want to put in bold the speeds you are running each test on. Seemed like a mistake if you ask me. All of those other roms do not come with default cpu max at 1700MHz.
Also, yes running them multiple times will make a HUGE difference. I have done it when bench marking graphics cards, cpu overclocks and with my phone. Try it....you will be very surprised.
Click to expand...
Click to collapse
Echoing this, Even if it's defaulted to a lower clock speed, you can't leave it that to provide an accurate data set. You also need a large spread, run hem 5 or 10 times and average them.
Even if benchmarks are a little silly in my book, still some interesting data.

G1ForFun said:
Uh you know foxstar is the only one you ran at stock speeds? The rest are at 1700. Might want to re run that one.
Also you would have to run each test three to five times to get any sort of meaningful results bc the scores will fluctuate.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Not true. Darkside Warfare was run at 1350.

IMO I think it's pointless unless you clock them at the same speed I mean you have digital warfare under clocked at 1.3 -_- might also want to mention which kernel each 1 is using and at the end of the day it's not about how each 1 scores but how it does in real life use I remember when I used the jugs kernel clocked at 1.89 I believe it scores over 8k easy but would lag on scrolling and other things but faux kernel would score a little over 7k and would run like butter clocked at 1.7. Now I'm using digital warfare with the kernel it comes with and I think it run incredible with speed, smoothness, and battery with good scores
Sent from my SGH-T989 using Tapatalk

mavblues said:
Not true. Darkside Warfare was run at 1350.
Click to expand...
Click to collapse
Mistake...
I was checking the screens from xda app. Your right.
Regardless...the roms should all be ran at one uniform speed for the best comparison.
Sent from my SGH-T989 using XDA App

avarize said:
Echoing this, Even if it's defaulted to a lower clock speed, you can't leave it that to provide an accurate data set. You also need a large spread, run hem 5 or 10 times and average them.
Even if benchmarks are a little silly in my book, still some interesting data.
Click to expand...
Click to collapse
This is true, however with an asterisk. Running them subsequently will 100% boost scores, mostly because of CPU stepping. Continually running them keeps them clocked at full speeds more often, especially in the beginning.
Also, same clocks please? Use setCPU or something to ensure it. Stock clocks would be appreciated.
Also, run Vellamo benchmark too please. Linpack too lol. And NOT quadrant.
That said, Darkside is the best performer here so far.

2hvy4grvty said:
Also, run Vellamo benchmark too please. Linpack too lol. And NOT quadrant.
Click to expand...
Click to collapse
Sorry, that's not going to happen. While I'm still debating how I feel about stock vs a standard clock speeds, I can tell you that I'm not willing to try different benchmarking tools. I feel AnTuTu is modern enough. And I agree with the quadrant comment.

Why not? What else tests browsing performance as thoroughly?
Can we at least agree that despite all the little games and gadgets this phone runs, almost everyone primarily uses the phone to browse the Internet? Antutu does none of that.

Not to defend myself or anything but...
a) for the 10000th time benchmarks are useless
b) benchmarks are useless
c) you ran them after different clock speeds.
d) benchmarks are better for Kernel tests, not rom tests.
e) Australia.

For clarity, the goal wasn't to try to get the highest score. It was to try to put all ROM's (and their included kernels) at the same baseline and see how they perform relative to one another. Not trying to put one over another.
Finding the right ROM can sometimes be a daunting task. Many offer roughly the same features, but just have different appearance. When people don't care about how the ROM looks (with all the different launchers and mods that can be changed after the fact), knowing how it performs out of the box may be the deciding factor.
I know clock speeds are different. Some ROMs opt for lower clock speeds to get better better life. So I thought it would be good to know how that effects its performance.
With that said, would this be useful? Would anyone appreciate seeing how one ROM performs relative to the others?

But what I don't get is you claim that the goal of the thread was to put all ROMs at the same baseline. That didn't happen. Just pointing that out.
matthewdavis said:
For clarity, the goal wasn't to try to get the highest score. It was to try to put all ROM's (and their included kernels) at the same baseline and see how they perform relative to one another. Not trying to put one over another.
Finding the right ROM can sometimes be a daunting task. Many offer roughly the same features, but just have different appearance. When people don't care about how the ROM looks (with all the different launchers and mods that can be changed after the fact), knowing how it performs out of the box may be the deciding factor.
I know clock speeds are different. Some ROMs opt for lower clock speeds to get better better life. So I thought it would be good to know how that effects its performance.
With that said, would this be useful? Would anyone appreciate seeing how one ROM performs relative to the others?
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App

I think he means baseline as in the performance you get from untouched roms as the dev intended them to be. This is probably more useful for people that are scared to mess around with overclocking apps..
G1ForFun said:
But what I don't get is you claim that the goal of the thread was to put all ROMs at the same baseline. That didn't happen. Just pointing that out.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse

mixedguy said:
I think he means baseline as in the performance you get from untouched roms as the dev intended them to be. This is probably more useful for people that are scared to mess around with overclocking apps..
Click to expand...
Click to collapse
That is correct. The baseline as defined by the authors of the ROMs. If a ROM author decides to underclock it out of the box, I'm not going to modify that.

Would Love to overclock My T989 but...

Hey folks, I've been using various Roms/Kernels from this awesome board ever since I got My T-Mobile Galaxy S2 (T989).
Right out of the box, my phone has been a bit laggy and I didn't like Touchwiz too much. So I started flashing and been using various Gingerbread builds that were very overclockable and ran very well on my phone!!
However, I miss ICS big time so I've been using the leaked AT&T ports and despite the minor bugs, I love ICS!! What I don't love is the fact that I've been spending weeks trying several kernels to try to Overclock my T989 with this ICS port and Every time it fails (boot loop).
Of course I use Darkside superwipe and kernel clenser B4 trying any and all roms/kernels and never ran into this issue b4.
So I think I am at the point of accepting that currently for the T989, there are NO overclock kernels that support the ICS port. Am I mistaken? Anyone else have any luck where I've been failing? If so, could you point me in the right direction?
By the way, my phone runs much smoother/faster on this AT&T ICS port than any gingerbread Rom I've tried (this includes overclocked kernels). For example, in Quadrant I'm getting over 800 points higher than I've scored on ANY of the gingerbread Roms with overclocked kernels. Not too shabby. Go ICS!
Thanks everyone!!!

wrong section ? >_> ?

What are you developing?
.

You posted in the wrong section to start, and without kernel source for the leaks there won't be overclocking, however they run plenty fast without overclocking. I have never needed to overclock a dual core so you may want to try other roms mainly the newest ics leak is really smooth. Next time pay attention where you post as this is not development good luck.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

blacksheep242 said:
For example, in Quadrant I'm getting over 800 points higher than I've scored on ANY of the gingerbread Roms with overclocked kernels. Not too shabby. Go ICS!
Click to expand...
Click to collapse
Of course you scored higher on ICS, the under the hood optimization's within ICS are what makes it such an upgrade.

There aren't any oc kernels yet we do not have source. And the ics we do have is not even for our phone.....lol be patient

main_shoby said:
wrong section ? >_> ?
Click to expand...
Click to collapse
omg lets kill him for not knowing..and not teach ignore him..but no oc for ics

goodfellajay said:
omg lets kill him for not knowing..and not teach ignore him..but no oc for ics
Click to expand...
Click to collapse
There's a Q&A section for a reason. And this section is called "DEVELOPMENT" because it's meant for DEVELOPERS, not people who don't bother to read just a little bit, and inform themse that our phone hasn't had an ICS leak, therefore there will be several cons and drawbacks to flashing an AT&T ROM. You have questions, go to the Q&A section, simple as that, he posted it here because he knew he would get a response here. Whether good or not.

Yikes
Wow, message boards sure have changed quite a bit since I've been deeply involved in them back in the 90's. I recall them being a place where folks with similar interests either discussed various topics, got questions/concerns addressed, or just did some friendly browsing. Key term here is "friendly."
My point is that I've posted in the wrong section. There was a question mark in my original post and I should have caught this . But although THIS section is, apparently, ONLY for DEVELOPERS, am I NOT allowed to browse various Roms, run them, and post my personal experiences and thoughts on them?
And IRIE4PIER, your sarcastic remark of "...not people who don't bother to read just a little bit..." was unnecessary. I read a LOT in this section and found various Roms, kernels, and kind advice to those with questions and/or problems running these various Roms.... Sooo, I figured this would be a great board to post my ICS overclock issue.
So to everyone pointing out my folly by posting in here, I thank you and will be sure it doesn't happen again, And to those who's feelings evidently got hurt...well will get over it, I hope.

He simply pointed out that you posted in the wrong section, I don't think he was rude even though he didn't answer your question. You made the mistake of putting your question in the wrong section, now I've posted in the wrong section before as well by posting a question about accessories in the accessories section and a mod moved it to the q and a. That's a simple mistake I assumed because it was about accessories it was the right section. You on the other hand, as you say you read about roms and kernels in this section you might have noticed that people tend to create threads when they have a mod/kernel/rom. The people that ask questions in this section ask them within the threads about the corresponding rom/kernel/mod so idk why you would create a thread as your obviously intelligent enough to know where it goes. Your not hurting no one but it is annoying none the less, it happens often and forums run better when they are organized and people follow the rules as that is why they exist. Your hostility is silly people are just trying to point out your mistake and some also answered your question as well.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

I always under clock ALWAYS. What is the big deal with oc for u is it just to get higher quadrant scores? This phone flys at 1.35 and the battery life is 4 million times better when under clocked. Quadrant scores don't mean jack **** I go by real life feel
Sent from my SGH-T989 using Tapatalk

bbobarino said:
I always under clock ALWAYS. What is the big deal with oc for u is it just to get higher quadrant scores? This phone flys at 1.35 and the battery life is 4 million times better when under clocked. Quadrant scores don't mean jack **** I go by real life feel
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I for one will never understand why people underclock this phone... if its to save an hour or so while running it at 1, 1.2, or 1.3 why not just get an atrix or mt4g slide? Could even stick with the sensation or mt4g... I overclock it at 1.83 and still get 16-18 hours with on screen time usually of 4-5 hours with moderate use running dw 2.5.1..... and its not about quadrant scores, I just want to make sure I'm using my beast to its fullest potential that I paid for.
Sent from my SGH-T989 using Tapatalk 2

foreverloco said:
I for one will never understand why people underclock this phone... if its to save an hour or so while running it at 1, 1.2, or 1.3 why not just get an atrix or mt4g slide? Could even stick with the sensation or mt4g... I overclock it at 1.83 and still get 16-18 hours with on screen time usually of 4-5 hours with moderate use running dw 2.5.1..... and its not about quadrant scores, I just want to make sure I'm using my beast to its fullest potential that I paid for.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
well, for one, the other phones kinda suck and phones like sensation have terrible battery life compared to this. do you really notice a diff between 1.35 and 1.83Ghz? i sure dont. i might as well try to save battery then. its also easier on your hardware to run at lower clock speeds.
i have my ics set at 192 to 1.35ghz and screen off at 192/192. i also have a setting for 192/1000 when its below a battery threshold.

IRIE4IPIER said:
There's a Q&A section for a reason. And this section is called "DEVELOPMENT" because it's meant for DEVELOPERS, not people who don't bother to read just a little bit, and inform themse that our phone hasn't had an ICS leak, therefore there will be several cons and drawbacks to flashing an AT&T ROM. You have questions, go to the Q&A section, simple as that, he posted it here because he knew he would get a response here. Whether good or not.
Click to expand...
Click to collapse
u nerds freak out...its funny..u cant post here..cry

It was an honest mistake, but as someone who's moderated boards before (and one that didn't have nearly as much traffic as this one) it does get annoying to constantly be moderating/moving/merging threads together.
I'm sure the OP didn't mean to cause any trouble and he'll look more closely where he's posting next time so problem solved.
As for the actual issue, I never felt a need to overclock the T989, and especially don't see a need with ICS installed. But to each their own

minotauri said:
well, for one, the other phones kinda suck and phones like sensation have terrible battery life compared to this. do you really notice a diff between 1.35 and 1.83Ghz? i sure dont. i might as well try to save battery then. its also easier on your hardware to run at lower clock speeds.
i have my ics set at 192 to 1.35ghz and screen off at 192/192. i also have a setting for 192/1000 when its below a battery threshold.
Click to expand...
Click to collapse
For regular use might not see much difference but when I multi task from text to emails, calls, web ect. There is lag if I underclock compared to stock speed or over clocking. My min is set at 384 if I set it lower I get a lag on wake which annoys me and I don't use any different off screen settings or any other profiles, only other thing I do is under volt by 50 globally, but every phone is different and not everyone uses their phone the same..
Opps more like under volted by 25, forgot that dw is already lowered by 25.... That's another thing for the op to watch out for, make sure your phone can handle the over clock with the voltage that's preset.. If not increase it little by little til its good and you get no boot loops.. The way I test it real quick is I run cf benchmark and antutu benchmark, not for the scores but to make sure the phone doesn't reboot in the middle. Now that's just a quick test if you do get a reboot through the day try increasing it a little more to check.
Sent from my SGH-T989 using Tapatalk 2

Here's some quick screens before I set it to charge.. Running at 1.83 and min at 384 under volted by 25 on dw which means under volted by 50 from stock if I'm not mistaken...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-T989 using Tapatalk 2

High benchmark, what set up?

I eventually ran a benchmark on my CarbonROM install on my Sprint Galaxy Nexus, clocked at a max of 1.6
But, I saw that my device compared to others is just super super low, I don't have the numbers on me as I don't have my phone, but if you're one of those people who have a high benchmark score, what's your setup?
I know it's said that benchmarks aren't important, but they at least have to mean something with performance.
So, what are you running?

Try flashing franco.Kernel. Makes a huge difference!
Before franco: 2204
After franco: 2932 (Quadrant Standard)
ROM: PACman ROM, 1.2 GHz

Seriously, there should be a thread stickied for the bench freaks, all in the same place. *sigh*
Sent from my Nexus

bk201doesntexist said:
Seriously, there should be a thread stickied for the bench freaks, all in the same place. *sigh*
Sent from my Nexus
Click to expand...
Click to collapse
There is one. Just needs sticky-ing.

Beauenheim said:
I know it's said that benchmarks aren't important, but they at least have to mean something with performance.
So, what are you running?
Click to expand...
Click to collapse
See, the thing is, benchmarks really do mean nothing. Benchmarks don't affect how well your device performs. If it runs fast, it runs fast-- you don't need the benchmark to know that.
Sent from my Mahjong Nexus

Beauenheim said:
I know it's said that benchmarks aren't important, but they at least have to mean something with performance.
So, what are you running?
Click to expand...
Click to collapse
Yeah. Because being able to crunch 110,000,000 triangles vs 90,000,000 has real world implications.

Yay! It's been a while since we've had a thread to remind us how useless benchmarks are and offer us all an opportunity to debate about it, yet again.:good:

I make my words what Chainfire said, but globaly.
If you trust benchmark results, you'll know that running naked in the garden for 5mins will affects performance by 20%

Neat, alright.
So absolutely nothing?
That really doesn't make any sense to me. Those 90,000,000 triangles being processed will at least show me how well it will do in a game, to a degree, right?

Not in any way you could actually notice. That was also an extreme hyperbole as far as differences go. To be totally honest, the only real value of benchmarks is stress testing an OC but even then there are better ways.

063_XOBX said:
Not in any way you could actually notice. That was also an extreme hyperbole as far as differences go. To be totally honest, the only real value of benchmarks is stress testing an OC but even then there are better ways.
Click to expand...
Click to collapse
Well alright, thanks for your insight. I've been in the android game for awhile but I don't know a lot of these things.