Database Users

Anyway the hummingbird will catch up to g2 processor

I know we have gotten to as high as 1.3 ghz but can our processors reach 1.4 or 1.5 ghz I know battery life would suck...but sometimes its cool to not have these other phones kick the crap out of us...haha
Sent from my SPH-D700 using XDA App

Aye aye aye....
Unless the G2 was running Android 2.1 (which it never has been) it's virtually impossible to compare the two. Ghz mean nothing...
Wait until the Epic is running Froyo and see who needs to catchup to whom.

xusxmarinesx said:
I know we have gotten to as high as 1.3 ghz but can our processors reach 1.4 or 1.5 ghz I know battery life would suck...but sometimes its cool to not have these other phones kick the crap out of us...haha
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
There was a 1.4ghz kernel but it want very stable. The extra 1ghz ain't much and is not needed unless your worried about how big your phones **** is
Sent from my Emotionless Beast of an Epic using the XDA App

Lol that was a good one.
Sent from my SPH-D700 using XDA App

Not to mention that not all g2s can even handle over 1ghz, they've got a much weaker gpu and the hummingbird has been successfully rooted up to 1.6ghz, but its nowhere near ready for prime time
Sent from my SPH-D700 using XDA App

The hummingbird can be clocked to 1.6hz and the gpu can achieve 75+fps on both neocore and nenamark (after having the fps cap removed.)
Is this not enough for you? We are still in 2010...

Team Whiskey has put out a Vibrant kernel (alpha) than can hit 1.6Ghz, and they're working on 1.8 and 2.0. Once they release the code (which should be soon), it shouldn't take long for an Epic version to surface.

Is stability not a problem with these high overclocks? I don't understand how someone can just put out a Xghz kernel for everyone to use. Aren't there hardware limits, ones that will be arbitrary device to device?

AndrewZorn said:
Is stability not a problem with these high overclocks? I don't understand how someone can just put out a Xghz kernel for everyone to use. Aren't there hardware limits, ones that will be arbitrary device to device?
Click to expand...
Click to collapse
Pretty much. Not everyone's phone can overclock. Just the luck of the draw.

Kubernetes said:
Pretty much. Not everyone's phone can overclock. Just the luck of the draw.
Click to expand...
Click to collapse
Not unlike desktop CPU overclocking then.

Well yes and no...every one can be overclocked...it boils down to how much..and how well of an over-clocker a chip is..then obviously it boils down to manufacture quality aka luck of the draw.
For example...the 1st gen snapdragon is a sub par overclocker...while the 550mhz chip in the original droid is an awesome overclocker....
It kinda boils down to the manufacturer limiting the frequency to a certain amount..sometimes for stability..but often times to charge you extra for more mhz...Intel has been doing it for years selling the same chip in 3 different clocks when in reality it is exactly the same chip.
I mean if samsung wanted to they could have easily released it at 1.3ghz..they just had no reason to...

just wait till the Epic is running 2.2 and u will see who the real winner is

the biggest issues for smartphone ocing are heat n battery, cuz unlike a desktop were u can keep uping the volts n if it gets to hot just add more cooling, a smartphone is all passive so you cant go much above stock voltage or it'll melt, plus wht good is 2ghz if u can only run it for an hour b4 ur battery dies

So then why is it such a big deal to make a ROM capable of a high clock? Someone could make a 5ghz ROM, but it would never work. If Hummingbird CAN go to 1.8ghz, I don't see why the current overclocked kernel's don't already reflect that.
In other words, I think we shouldn't hope for much over 1.2ghz, which is already pretty good.
Any stability testing programs for Android? Or is everyone saying "no crash = must be stable"?

OVERCLOCKING the HD2

Hey, i'm just curious as to why the HD2 cannot be overclocked higher than 1190(solid)
My brother in law just got the G2 which has the 800MHz processor, and he has it OC'd to 1.8GHz and is pushing over 3-4k Quadrants, and 55+ Linpack scores and the battery is still decent on it.
We have a 1GHz pcsr that can barely hit 1.2, ( i know MDJ has a 1460OC, but it is not ACTUALLY 1.4 it still reads the same as an overclock to 1.2)
Is there a hardware/software reason for this, any ideas?
Thanks!

G2 has the latest gen snapdragon processor, so i guess thats why, you will have to look up the specs of that processor to see whats new.

javolin13 said:
Hey, i'm just curious as to why the HD2 cannot be overclocked higher than 1190(solid)
My brother in law just got the G2 which has the 800MHz processor, and he has it OC'd to 1.8GHz and is pushing over 3-4k Quadrants, and 55+ Linpack scores and the battery is still decent on it.
We have a 1GHz pcsr that can barely hit 1.2, ( i know MDJ has a 1460OC, but it is not ACTUALLY 1.4 it still reads the same as an overclock to 1.2)
Is there a hardware/software reason for this, any ideas?
Thanks!
Click to expand...
Click to collapse
its because on the newer snapdragons (like the one in the g2) you can get to very high speeds at near stock voltages however on the last gen ones (like the ones in the hd2 and nexus one) you need to increase the voltages to get to the higher speeds which is risky so most kernel builders wont do it let alone release it to the public

Its a 45nm process. If you shrink the process than it takes less charge to charge up the gate. The paths get shorter for the current to travel and therefore the critical path between two registers can get smaller and you can crank up the frequency.

yea i get in linpack 40 not more
1.2ghz and 1.46ghz have the same score for me
so i cant get more but sometime the cpu is quality enuf to work with this voltage

My nenamark score, am I crazy?

Yesterday I installed nenamark on my nexus one and ran my first benchmark, and I swear I got 30.1 fps. I specifically noted that it was spot on with movie frame rates.
Every subsequent test I've run I only get around 16fps. Perhaps 30 is way too high for the nexus one's hardware. But did I just imagine my original score or did I actually get that high? What's the highest score we've seen on the nexus one?

Why not just open it again and on the main screen it says what the highest recorded score it...
That'll tell you what your best score it. Also i maxed out on 16.2FPS :-/

Yeah my best run says 17 so I guess I imagined it. But I could have sworn I saw it. Oh well...

It was allllll just a dream ;p

Share your drugs
Sent from my Nexus One using XDA App

42.8 fps nenamark
Galaxy S Captivate

Couldn't using one of these newer kernels with updated GPU drivers be helping?

I got 17.5 fps. Not bad for a year old 1 GHz superphone
Sent from my Nexus One using XDA App

I just got a 22f p s yesterday if you believe it. Same exact kernel and all and it shows up in my high score at least.

My one is 22.3fps, without any tweaks, cleans e.t.c
Miui + wildmonks kernel.

16.4 on the N1 (CM 6.1.1), 36.5 on the galaxy tab
Edit: Remembered I'd underclocked my CPU, ramped it up to 1113Mhz and got 22.9fps. (Which I can't duplicate, can only hit 22.3fps now)

Tell you what, 22 isn't too bad considering this hardware.
My question is how does windows phone 7 devices, that all use the same CPU combo as the nexus one, get silky smooth scrolling thru the entire OS, including very large web pages etc. Do they just use that much better drivers? It definitely shows its possible and the potential.

Lower Quadrant Score With New ROM

So I flashed Skyraider today, and my quadrant score dropped 100 points from stock sense. What the hell is going on here....

The Black Droid said:
So I flashed Skyraider today, and my quadrant score dropped 100 points from stock sense. What the hell is going on here....
Click to expand...
Click to collapse
Sitting at 1032. With the stock ROM, I was getting around 1120.
Why are these scores so low???

Q scores || ROMs
Quadrant scores vary by ROM and kernel, and by different kernels in the same ROM.
Those scores are expected to vary.

Quadrant scores, don't take those to heart... It's all about feel. I've run roms where they might score low, but feel and move quick.
Sent from my ADR6300 using XDA App

I just don't understand how some of these guys have anywhere from 2700-3300 as their quad score. I would imagine their phones are running insanely fast

Maybe, they are most likely overclocking. Some phones don't like going too high. Like on mine, I can't go over 1.113, or my phone slows to a crawl and locks up/reboots.
Sent from my ADR6300 using XDA App

The Black Droid said:
I just don't understand how some of these guys have anywhere from 2700-3300 as their quad score. I would imagine their phones are running insanely fast
Click to expand...
Click to collapse
Where have you seen people post these scores for their Inc?
I'm willing to bet good money that if you are seeing people post scores that high, they are either:
A. Not running Quadrant from an Inc but a much more powerful device (like an Android tablet)
B. Faking the results in Photoshop (or just lying about the number if no screenshot is provided)
C. Running a setup that doesn't actually run through the Quadrant test properly. For example, Quadrant didn't run properly on Gingerbread roms at first, and the scores that it would produce were extremely erratic. Sometimes they would be extremely low, sometimes they would be extremely high, but they weren't accurate or repeatable.
D. Running some sort of insane setup that is only stable enough to finish a Quadrant run, and will never actually be used for anything
Frankly, even D is far-fetched.
I would be inclined to call a 100 point fluctuation in Quadrant scores insignificant.
If you really want to chase the highest benchmark scores, you'll need to overclock your CPU and run the system as lean as possible. That means uninstalling or disabling a lot of the things that make your life easier day-to-day.
Also, in case you haven't already seen it in your own testing, Quadrant scores are always lowest on the first run. If you press the back button and immediately start a new Quadrant run, you'll get a much higher score.
Like any unit of measurement, Quadrant scores do serve a useful purpose. But as is often the case when the score itself is seen by some as the end-goal, it is often misapplied.
The same can be seen in digital cameras and the megapixel arms race. Everyone wants to brag about how many megapixels their camera is capable of. Everyone wants the highest number of megapixels, assuming that more MP = better image. Few people realize what it actually means, or why it matters very little these days.

A lot of those people are overclocking to get really high scores and for all the reasons listed above (nice post!).
You really should not be looking to get that high on the incredible, you'll end up draining your battery like crazy. Around the 1,000 mark is great for playing higher-end games on the market as long as you aren't running a bunch of things in the background. Just about anything else you can think up of doing on your phone should run well, you won't have a sluggish device and you won't be killing your battery either.
If you do end up trying to overclock your phone or using a ROM or kernel combination that will give you a much higher score I don't think you'll notice any difference when doing anything on your phone, but your battery will drop much quicker.
Like other people have said, Quad scores don't matter much- take them lightly as you see them.

There is a lot that goes into that score. The highest score I could get today is 1656 but it was consistently in the Upper 1500s, I ran 5 tests.
My setup:
CM7 RC2
Incredikernel 03/06 OC to 1113Mhz/Performance Govenor
16Gb Class 2 microSD card.
If someone is using a class 4 or a class 6 card their i/o scores could be much higher than mine which would result in a much higher overall score than mine. Also keep in mind with Linux Kernels can very alot and that there are different types of task schedulers in them such as BFS or CFS which can have dramatic affect on the quadrent scores. Quadrent tends to score BFS kernels higher. So yeah I can believe people are hitting most of the score they post up. However byrong is right about it not being a setup you'd want to use on a daily basis. For me it causes random reboots, my phone gets hot and the UI becomes laggy after a little while also the battery drops like a brick.
My normal setup that I run on a daily basis is the same kernel uc to 803Mhz/smartass governor. It is extremely stable and is smooth as butter but my quadrent scores are only only in the 1100s with my high being 1244.
Its really not all about the score, if your happy with the performance who cares about the score.

[Q] Just bought TF101, My Adventure in Rooting & Jelly Bean

So, nabbed an Asus Transformer TF101 off Craigslist for $225. With keyboard. Feeling good about that.
Next question for semi-geeky me. To leave a decent Ice Cream Sandwich -- the ASUS-approved version -- on the tablet or to venture into the unknown world of rooting and custom Jelly Bean ROMs? Sheesh. I tried to resist. But... just... could... NOT...
Did I mention I didn't have a Windows PC to make rooting a bit easier? That left me with the need to do it via an iMac. I've gone and lost that url, but think it is one of the pages on this site.
From there, how do I pick a ROM? All sorts of threads, all of 'em messy (at least to the noob in the room). So I noted EOS got a lot of uptalk and went that route. After more than few false starts (manually typing in command lines kept introducing unintentional HUMAN ERROR into the mix) I got lift-off.
Did I mention my wife owns a Nexus 7 (one of the nicest little bits of hardware/software I know of... no no, the Nexus, not her!! She's stellar, but I digress).
In light of the Nexus' buttery feel, I was hoping for similar from my Asus Transformer. Well, not quite. Maybe the dual vs quad core chip has something to do with that. But I do very much like my larger (10") screen vs. her 7" and the keyboard... and Jelly Bean seems pretty darn nice even on a dual core tegra chip. Still hoping for a little more butter as the EOS nightly people do their thing. (I thank and thank them!!)
Oh. EOS answered my next problem before I got to it. How to overclock? Right in the setup I can do it.... tried all sorts of settings there and ended up with backing it off to only 1.2 (from 1.0) ghz. Not a game-player, just a blogger. Downloaded all my favorite apps -- kindle reader, YouVersion Bible, Skype, and so on. Oh, and of course some board games so I can play 'em with my Dearling.
Last night EOS suddenly updates my gapps. Hmmm. No big change, except maybe things are slightly snappier?
Questions I still have:
I installed an older (I think) booter/recovery module (or whatever the heck it is called). "Team Rogue" "Rogue XM Recovery 1.5.0 (CWM-Based Recovery v5.0.2.8)"
This recovery does not let me write to my external SD card (or even read from it) but will write / read to a USB stick if I mount it of course via their menu. My question:
Is this the newest and best boot/recovery tool? And if not, how and to what tool should I upgrade/switch?
Really enjoying my toy.

I've come up with a few more questions of a semi-general nature... but perhaps overly technical. If wrongly posted here, please advise...
Why does the Tegra 2 chip in my TF101 apparently change speeds and therefore frequencies? Using the setup app in EOS's version of Jelly Bean, one can alter two frequency / speed settings -- minimum and maximum -- and I'm thinking that is one frequency per core?
The reason that matters is because I'm experiencing an occasional spontaneous reboot. My settings were at 216 MHz (minimum) and 1200 MHz (maximum). I'm in over my head at this point as far as knowing if the lower value in particular is too low.
Anyone else have any thoughts?
Thanks.

shonkin said:
I've come up with a few more questions of a semi-general nature... but perhaps overly technical. If wrongly posted here, please advise...
Why does the Tegra 2 chip in my TF101 apparently change speeds and therefore frequencies? Using the setup app in EOS's version of Jelly Bean, one can alter two frequency / speed settings -- minimum and maximum -- and I'm thinking that is one frequency per core?
The reason that matters is because I'm experiencing an occasional spontaneous reboot. My settings were at 216 MHz (minimum) and 1200 MHz (maximum). I'm in over my head at this point as far as knowing if the lower value in particular is too low.
Anyone else have any thoughts?
Thanks.
Click to expand...
Click to collapse
The 216mhz is the slowest speed your CPU will go on both cores. This could cause reboots if too low because the operating system crashes because it cannot get everything done it needs / wants to. Try to up it to 500 and play around with the value so you dont get reboots, low mhz is better for battery when in deep sleep etc but can become unstable.
The 1200 mhz could also cause reboots if too high, however I don't think that sounds high, some go as high as 1500 or 1600 so that is probably not the issue.
The mhz, either min or max, applies to both cores equally on tegra 2.
Your wife's nexus has 4 cores and a single ninja core for background activity, so on hers, you can set min and max for the 4 cores and the ninja core seperately.
Hope that helps!

gunswick said:
The 216mhz is the slowest speed your CPU will go on both cores. This could cause reboots if too low because the operating system crashes because it cannot get everything done it needs / wants to. Try to up it to 500 and play around with the value so you dont get reboots, low mhz is better for battery when in deep sleep etc but can become unstable.
The 1200 mhz could also cause reboots if too high, however I don't think that sounds high, some go as high as 1500 or 1600 so that is probably not the issue.
The mhz, either min or max, applies to both cores equally on tegra 2.
Your wife's nexus has 4 cores and a single ninja core for background activity, so on hers, you can set min and max for the 4 cores and the ninja core seperately.
Hope that helps!
Click to expand...
Click to collapse
The EOS (#79) Rom's latest update seems to have helped some... along with my using SETCPU (which may or may not be more effficient but was suggested to me by another poster here).
I'm running with the very low 216mhz still, but have upped the max all the way to 1600mhz. So far, no spontaneous reboots like before even when running angry bird, a browser, and other junk. I used an app (SETCPU) to create a battery charging profile that allows for the tablet to run between 1200 and 1600 when plugged in and charging. More to see if it worked than because I have any real need for it.... and it did work just fine.
But I appreciate the comment re 216 being really low. And if it does exhibit strange behavior again, I'll monkey with the low setting to see if it helps.