Database Users

G-2 vs Milestone 2

I know this might be a touchy topic to start, but I was seriously considering the Milestone 2 before the G-2 was announced. And when I heard that the G2 wasn't even 1GHz, I was pretty set on the Milestone 2. Then the benchmarks came out: http://www.gizmodo.com.au/2010/09/graphics-benchmark-for-g2-shows-it-should-be-blazin/
so now I am super confused.
Milestone 2 - Pros:
1GHz processor (if the Milestone can be OCed to 1GHz, who know what the Milestone2 could be OCed to?!)
Umm....that's all I think
Milestone 2 - Cons:
Locked bootloader (what does this mean exactly? no custom ROMs?)
MotoBLOATware (means slower Android updates)
Same camera as Milestone 1 (seriously...)
Motorola
G-2 - Pros:
HTC
Stock Android
Faster Android updates
Supposed to be good for Android Gingerbread as well
No locked bootloader (more custom ROMs?)
Not Motorola
G-2 - Cons:
800MHz Processor
Didn't perform as well as Droid 2 in stock benchmark tests
Less internal memory (4Gb vs 8Gb) - not a big deal I guess
Hinge design probably means it's easier to break
Does anybody think that the development for the G-2 would be larger than the Milestone 2? Because that would be a huge Pro for the G-2. The G-1 development has lasted for years, and the user base is huge...so I am just going to assume that it would be similar for the G-2.
I'm not going to mention aethetics, because this is very subjective so no point arguing on that front.
So here's my question: Which one should I get?!

Hmm, tough one really.
HTC Camera's are not much better than the ones motorola sticks in them to be honest! The droid has crapware on it and the HTC comes with stock sense.
It seems the processor performance is near identical, in real world application use atleast so thats a non-issue i.e. when one beomces outdated, so will the other.
In terms of mod community, the HTC phone is likely to get much more support on this website, simply because the majority of people here are HTC users or past HTC users.
The Milestone seems a bit more manly, rough and the HTC looks more refined IMHO.
Personally, I'd go the G2 if I wanted as much modding as possible. HTC has a much more open policy on the topic and no locked bootloaders (efuse etc).
At the end of the day, its your decision
Have a play with both phones and pick the one you feel looks better. A good question to ask is:
I know they both look nice now, but which one will look worse for wear (paint peeling, scratching etc)

yeah, I was leaning a little more towards the G-2 due to the massive potential of modding/custom ROMs available. And i'm also quite sure that the G-2 will become the new platform for development, much like the G-1 was.
The 800MHz still bugs me though...considering that Qualcomm has new chipsets that are supposed to be able to go up to 1.2/3GHz whilst also running a GPU chip. I wouldn't wait until dual-cores because apparently that won't happen until next year (probably late next year).
HTC are supposed to be doing a pretty major announcement in London on the 15th September (so we'll hear about it on the 16th)...so hopefully that might shed some light on it. Of course, if the G-2 is the only QWERTY option, then that would probably limit our choices.
...if only they had made that a 1GHz processor...

I wouldnt rate the 1ghz feature that highly. Perhaps 800 mhz is an underclock to enhance battery life. After all, the benchmarks say performance is on par with the top phones.

99.9999% guaranteed that you'll be able to overclock the G2 to at least 1ghz

IMO the onlything that the M2 has over the G2 is how far u can OC the processor. those A8's can go far.

I dunno. clock speed is overrated. you don't know what performs better in the real world until you see some benchmarks.

That's true. Apperantly I read that a 800mhz Droid 1 performs on par with a n1. The a8 can be oc to all hell.
I definately am a fan of TI chips. They are mighty strong and it always seemed that they always had a leg up on qualcomm. I hope qualcomm stomps everyone with some massive processor that'll make the hummingbird cry

The g2 is under-clocked according to the press release.

Mylenthes said:
The g2 is under-clocked according to the press release.
Click to expand...
Click to collapse
I heard. At the end of the day a underclocked processor that runs as fast as a snapdragon and wastes less power is a win in my book!

I have read that the ARM procs are better with GPUs and for overclocking - just look at the Milestone 1. The Droid 2 was still benchmarked as the best (but only just over the G-2) and it's potential for OCing was what swayed me that way.
But now that these new Qualcomm chipsets have a separate GPU that seem to be able to compete with the best in benchmarking - it's hard to say.
If the G-2 can be OCed, then that would be awesome...but then, the Milestone 2 is also about 99% sure to be OCed...as I'm sure previous Milestone 1 owners will be screaming for it as soon as they get their hands on the new one.

skulk3r said:
I have read that the ARM procs are better with GPUs and for overclocking - just look at the Milestone 1. The Droid 2 was still benchmarked as the best (but only just over the G-2) and it's potential for OCing was what swayed me that way.
But now that these new Qualcomm chipsets have a separate GPU that seem to be able to compete with the best in benchmarking - it's hard to say.
If the G-2 can be OCed, then that would be awesome...but then, the Milestone 2 is also about 99% sure to be OCed...as I'm sure previous Milestone 1 owners will be screaming for it as soon as they get their hands on the new one.
Click to expand...
Click to collapse
Im confused. I thought the nexus had a seperate gpu?

sheek360 said:
Im confused. I thought the nexus had a seperate gpu?
Click to expand...
Click to collapse
as far as I know, it does, but either the GPU isn't fully utilized in the use of Android or it's just a underpowered - just see the benchmarking results on the previous page that I posted, the Milestone 2 and G-2 smoke the N1 (which is expected, since the N1 is much older)

skulk3r said:
I know this might be a touchy topic to start, but I was seriously considering the Milestone 2 before the G-2 was announced. And when I heard that the G2 wasn't even 1GHz, I was pretty set on the Milestone 2. Then the benchmarks came out: http://www.gizmodo.com.au/2010/09/graphics-benchmark-for-g2-shows-it-should-be-blazin/
so now I am super confused.
Milestone 2 - Pros:
1GHz processor (if the Milestone can be OCed to 1GHz, who know what the Milestone2 could be OCed to?!)
Umm....that's all I think
Milestone 2 - Cons:
Locked bootloader (what does this mean exactly? no custom ROMs?)
MotoBLOATware (means slower Android updates)
Same camera as Milestone 1 (seriously...)
Motorola
G-2 - Pros:
HTC
Stock Android
Faster Android updates
Supposed to be good for Android Gingerbread as well
No locked bootloader (more custom ROMs?)
Not Motorola
G-2 - Cons:
800MHz Processor
Didn't perform as well as Droid 2 in stock benchmark tests
Less internal memory (4Gb vs 8Gb) - not a big deal I guess
Hinge design probably means it's easier to break
Does anybody think that the development for the G-2 would be larger than the Milestone 2? Because that would be a huge Pro for the G-2. The G-1 development has lasted for years, and the user base is huge...so I am just going to assume that it would be similar for the G-2.
I'm not going to mention aethetics, because this is very subjective so no point arguing on that front.
So here's my question: Which one should I get?!
Click to expand...
Click to collapse
Well If I made the list I would make it more like this:
Droid 2
Pro's:
-More high res screen (854*480 vs 800*480, both on a 3.7" screen)
-8 Gigs internal storage (4 gb more than G2)
-1 Ghz TI 45nm processor (likely to overclock fairly well)
-1 oz lighter
Con's:
-MotoCRAP software (look at the scrolling on any phone with blur from the cliq to droid x and tell me it doesn't feel slow)
-keyboard lacking comparing it to the G2
-locked bootloader (harder to develop roms for, root still possible though)
-CDMA (yeah it sucks.... that's why noone outside the US uses it...)
G2
Pro's:
-Better screen (S-TFT lcd vs regular lcd on the droid/2; brighter, more contrast, better power consumption)
-720P camcoder at 30FPS
-Adreno205 GPU(4X better graphics than previous snapdragons)
-800 Mhz MSM7230 45nm (this shows it was designed to run at 1 Ghz, but underclocked to save battery. Similar to the MSM7201A on the G1, designed for 528 Mhz but only runs at 385 Mhz unmodified; should at least be overclockable to 1.13 or more)
-better keyboard (WWW.\.COM BUTTON? HELL YEAH!)
-HSPA+ (who doesn't want 14 MB/s DL?)
-GSM (gsm is always better....)
-likely to receive updates rapidly (no promises though, look at the 3 months it took motorola to update to 2.1 on their "google experience" device)
-New sturdy Z-hinge design
Con's:
-ummm.......
Yeah so what if the droid 2 gets an extra 3 frames (58 vs 61)... Your eye can only detect 50FPS unless you're a combat pilot or a sniper with trained eyesight. Besides that both phone's have pretty identical specs, including 512 mb ram, 2.2, 10 hrs talk time, etc. My vote is definately towards the g2, but don't get me wrong both are beasts of a phone. Also I wouldn't expect to see any dual core's until maybe next summer. Think about it: Qualcomm released the original snapdragon in Nov 2008, but it wasn't until Dec 2009 that a phone implemented it (LG Expo). The dual core qualcomm chips come out next month, so it should be 6 months-a year before they come out.

mejorguille said:
Well If I made the list I would make it more like this:
Droid 2
Pro's:
-More high res screen (854*480 vs 800*480, both on a 3.7" screen)
-8 Gigs internal storage (4 gb more than G2)
-1 Ghz TI 45nm processor (likely to overclock fairly well)
-1 oz lighter
Con's:
-MotoCRAP software (look at the scrolling on any phone with blur from the cliq to droid x and tell me it doesn't feel slow)
-keyboard lacking comparing it to the G2
-locked bootloader (harder to develop roms for, root still possible though)
-CDMA (yeah it sucks.... that's why noone outside the US uses it...)
G2
Pro's:
-Better screen (S-TFT lcd vs regular lcd on the droid/2; brighter, more contrast, better power consumption)
-720P camcoder at 30FPS
-Adreno205 GPU(4X better graphics than previous snapdragons)
-800 Mhz MSM7230 45nm (this shows it was designed to run at 1 Ghz, but underclocked to save battery. Similar to the MSM7201A on the G1, designed for 528 Mhz but only runs at 385 Mhz unmodified; should at least be overclockable to 1.13 or more)
-better keyboard (WWW.\.COM BUTTON? HELL YEAH!)
-HSPA+ (who doesn't want 14 MB/s DL?)
-GSM (gsm is always better....)
-likely to receive updates rapidly (no promises though, look at the 3 months it took motorola to update to 2.1 on their "google experience" device)
-New sturdy Z-hinge design
Con's:
-ummm.......
Yeah so what if the droid 2 gets an extra 3 frames (58 vs 61)... Your eye can only detect 50FPS unless you're a combat pilot or a sniper with trained eyesight. Besides that both phone's have pretty identical specs, including 512 mb ram, 2.2, 10 hrs talk time, etc. My vote is definately towards the g2, but don't get me wrong both are beasts of a phone. Also I wouldn't expect to see any dual core's until maybe next summer. Think about it: Qualcomm released the original snapdragon in Nov 2008, but it wasn't until Dec 2009 that a phone implemented it (LG Expo). The dual core qualcomm chips come out next month, so it should be 6 months-a year before they come out.
Click to expand...
Click to collapse
Well technically the Milestone 2 is a GSM device, not CDMA, but the other points are quite good.
However, don't forget that the Milestone 2 can also OC...so the two are comparable in that sense.

Didn't I read somewhere that Android doesn't yet support hardware acceleration for it's UI? Meaning that that spiffy new GPU will only get used in games/video, etc? I'm no expert on this - perhaps someone could chip in and explain...
I too am facing the same decision soon. I love my Desire, but I will never buy a keyboardless phone again, and will chop it in for one of these two as soon as I can.
I was leaning more towards the Milestone 2 as it looks badass in my opinion, and there is no major difference in the specs. That was til I read up about locked bootloaders, and the fact that Milestone 1 owners are still on Android 2.1 and Motorola just doesn't give a sh*t about the numerous bugs the phone has.
Just a quick search around forums/Facebook Motorola Europe page etc, shows how unhappy Milestone 1 owners are with Motorola. Page after page of people saying "I will NEVER buy Motorola again" and literally begging Motorola to unlock the bootloader before abandoning the phone (all met with a deafening silence from Motorola) does turn me off of the Milestone 2. Motorola won't fix the phone and won't give their customers the tools to fix it themselves, so as far as I'm concerned I'm not going to spend £400-500 to put myself in that same position with the Milestone 2.
On the HTC side of things, they do make attempts to stop people modding their phones, but have not yet gone as far as locking the bootloader, and every HTC phone has been compromised. I fully expect this to be the case with the G2/Desire Z (Desire Z - what a sh*t name!), and the phone WILL get a lot of dev support, no question.
Ultimately, I believe there is no choice for me: pain with Motorola, or fun with HTC/XDA devs!
I'm still not sure about the hinge action, nor do I like the looks of the G2 particularly, I think it's going to turn out to be a bit of a fat chunker! Still, I go for personality and functionality in my phone rather than looks, otherwise I'd have an iPhone! It's also a crying shame that HTC went with a 4 row rather than 5 row keyboard.... And one final request please HTC - make sure that screen is full multitouch please! Oh, and I have heard this bad-boy is going to have stock Android with HTC Sense widgets - that's all well and good, but what I'm interested in is the Sense Dialer. And the Sense browser text selection please - I want that available everywhere on the phone, please!

Uh oh - just read the G2 has just 1300maH battery.
HTC, what is this twattery? I don't want to go backwards with battery size! Yes I know, more efficient processor, blah blah, lower clock speed, yadda yadda - but I don't give a monkey's!
A smaller battery in a bigger handset than the original Desire is not good enough in my mind. The G2 is going to be a brick anyway - why not add 5mm to the length and give us an extra 200-300maH? Or perhaps if you'd used a more standard slider action then you could've fitted a beefier battery in there :-(

setspeed said:
Didn't I read somewhere that Android doesn't yet support hardware acceleration for it's UI? Meaning that that spiffy new GPU will only get used in games/video, etc? I'm no expert on this - perhaps someone could chip in and explain...
Click to expand...
Click to collapse
It's true, but the next version Android Gingerbread adds it, which is where handsets with weaker gpus will begin to struggle. Running AOSP means that it will get updates at the same speed of the Nexus one.
However, the Clove spec for the Desire Z has it as a Sense device. This is backed up with the earlier screenshot of the Desire Z with the default sense wallpaper, and the name (why would they give it Desire branding if it didn't have Sense?). So there's a chance they'll put in the 8X55 which is the 1ghz of the same processor, but doesn't support HSPA+ (which isn't in the UK). So we'd gain 200mhz in return for Sense and an uglier handset colour scheme.
UK HTC event is tomorrow, so we should find out then.

Adreno205 GPU, 4X better graphics than previous snapdragons.
I think it's the only one that has hardware accelerated Adobe Flash support.
I remember seeing Milestone 2 and other android phones reviews, reviewers said phone would literally crawl when browsing flash enabled websites.
So maybe that feature will make a big difference?
I think I've decided: G2

setspeed said:
Didn't I read somewhere that Android doesn't yet support hardware acceleration for it's UI? Meaning that that spiffy new GPU will only get used in games/video, etc? I'm no expert on this - perhaps someone could chip in and explain...
I too am facing the same decision soon. I love my Desire, but I will never buy a keyboardless phone again, and will chop it in for one of these two as soon as I can.
I was leaning more towards the Milestone 2 as it looks badass in my opinion, and there is no major difference in the specs. That was til I read up about locked bootloaders, and the fact that Milestone 1 owners are still on Android 2.1 and Motorola just doesn't give a sh*t about the numerous bugs the phone has.
Just a quick search around forums/Facebook Motorola Europe page etc, shows how unhappy Milestone 1 owners are with Motorola. Page after page of people saying "I will NEVER buy Motorola again" and literally begging Motorola to unlock the bootloader before abandoning the phone (all met with a deafening silence from Motorola) does turn me off of the Milestone 2. Motorola won't fix the phone and won't give their customers the tools to fix it themselves, so as far as I'm concerned I'm not going to spend £400-500 to put myself in that same position with the Milestone 2.
On the HTC side of things, they do make attempts to stop people modding their phones, but have not yet gone as far as locking the bootloader, and every HTC phone has been compromised. I fully expect this to be the case with the G2/Desire Z (Desire Z - what a sh*t name!), and the phone WILL get a lot of dev support, no question.
Ultimately, I believe there is no choice for me: pain with Motorola, or fun with HTC/XDA devs!
I'm still not sure about the hinge action, nor do I like the looks of the G2 particularly, I think it's going to turn out to be a bit of a fat chunker! Still, I go for personality and functionality in my phone rather than looks, otherwise I'd have an iPhone! It's also a crying shame that HTC went with a 4 row rather than 5 row keyboard.... And one final request please HTC - make sure that screen is full multitouch please! Oh, and I have heard this bad-boy is going to have stock Android with HTC Sense widgets - that's all well and good, but what I'm interested in is the Sense Dialer. And the Sense browser text selection please - I want that available everywhere on the phone, please!
Click to expand...
Click to collapse
waiting to see what new things HTC has "dreamt" up for their announcement of the 15th (in London)...but I don't expect things to be any different than what we know now.
yes, the battery is a crying shame, but tbh I charge my phone every night ever since I got my blackstone...and I also have a car charger...but it would still be nice to have a phone that would last more than 2 days.
I'm not sure I fully understand the bootloader stuff...I've seen youtube videos of people running something called a "Bugless Beast" ROM on an OCed Milestone 1....but I agree, Motorola are pretty bad with customer service and post-sales support. HTC, on the other hand, are pretty happy to turn a blind eye to the modding community - as all Android manufacturers should..since Android is technically an opensource platform.
Oh..also...I don't really care about the name Desire Z, lol.....just a name. They could call it "The Loser Phone" and I'd still probably get it

[Q] Droid 2 performance question

Hello all, just a quick question about the general performance of the D2...
I currently have an Evo, and i seem to get fairly consistently decent Linpack scores (35-40) even in Sense roms (OC'd to 1152). I also typically have around 200mb free memory after running a task killer.
I have been considering switching to VZW for a variety reasons, so I went and tried out a D2 at the Verizon store. Ran Linpack a few times and got nothing better than 10-12, which came as quite a surprise to me. Also could barely eek out 120mb free memory after running task killer.
So what id like to know is...what kind of numbers are you seeing on your D2 (Linpack, Quadrant, free memory, etc). Additionally, are you getting these numbers with a blur rom or vanilla?
Thank you very much for your input.

theshade89 said:
Hello all, just a quick question about the general performance of the D2...
I currently have an Evo, and i seem to get fairly consistently decent Linpack scores (35-40) even in Sense roms (OC'd to 1152). I also typically have around 200mb free memory after running a task killer.
I have been considering switching to VZW for a variety reasons, so I went and tried out a D2 at the Verizon store. Ran Linpack a few times and got nothing better than 10-12, which came as quite a surprise to me. Also could barely eek out 120mb free memory after running task killer.
So what id like to know is...what kind of numbers are you seeing on your D2 (Linpack, Quadrant, free memory, etc). Additionally, are you getting these numbers with a blur rom or vanilla?
Thank you very much for your input.
Click to expand...
Click to collapse
Just remember that benchmarks are only just that... much of the performance is just everyday feel. But in my opinion, the Evo is the smoothest android out there right now

linpack is faster on snapdragon cores (evo 4g) because of a 128bit SIMD vs the droid 2's OMAP cores 64bit SIMD.
the two processors are pretty much the same, except the GPU is faster in the Droid 2 and the droid2 will have better battery life due to having a 45nm CPU vs the 65nm in the evo 4g snapdragon...
http://www.anandtech.com/show/3908/motorola-droid-2-review-rebooting-the-droid

droid2andyou said:
linpack is faster on snapdragon cores (evo 4g) because of a 128bit SIMD vs the droid 2's OMAP cores 64bit SIMD.
the two processors are pretty much the same, except the GPU is faster in the Droid 2 and the droid2 will have better battery life due to having a 45nm CPU vs the 65nm in the evo 4g snapdragon...
http://www.anandtech.com/show/3908/motorola-droid-2-review-rebooting-the-droid
Click to expand...
Click to collapse
HTC GPU's are bad, but I'd give up graphics for overall performance that HTC offers. Just my 3 cents

Droid 2 omap is faster than the scorpion cpu used in the evo 4g
Sent from my DROID2 using XDA App

Benchmarks are the stupidest thing one could base performance on. Instead of actually using the phone to see how it performs, you were too worried about benchmark numbers, and how much free ram the phone has after killing its tasks? If all you care about are those two things, why bother asking here? You already tested the phone with what matters to you.

I've heard that by design linpack does not score well on OMAP processors. If you are getting scores around 16 then you are doing well, but again it's just a benchmark

moto xoom vs fascinate

Thought i would drop in and let you know the results of my testing, as I have a lot of downtime.
I used antutu benchmark as it would give me values for each category.
Moto xoom - 1.5 oc kernel, stock 3.0
Fascinate - voodoo eb16 kernel, superclean 2.7
Processor - as you all have heard the new dual core tegra 2 is fast, through same benchmark tests I have found that it twice as fast as the hummingbird w/ no over clock, the tegra was oc to 1.2ghz
Xoom 1034 and 766
Fascinate 596 and 142
Graphics - this is where some eyebrows will be raised! Everyone says the tegra is supposed to be the best at 3d but I found quite to opposite. There are a lot of variables out there too though, multi threadding and is 3.0 as mature as 2.2 and last the screen resolution is higher on the xoom.
Xoom 2d 148 3d 205
Fascinate 2d 158 3d 364
These results can be seen by the naked eye as things just seem slower on the xoom in 3d.
I did not include linpack as its obvious the xoom will out perform the hummingbird no questions. I am just thrown off by the gpu scores, anything out for the tegra the fascinae should be able to run, extra help will come from the faster processor but i am not seeing an incredible difference that was advertised. After these findings I am more excited for the dual core snapdragon. Things my improve as honeycomb matures and they iron out the details, from first use right now it seems like its a beta 2.2 that we had on the fascinates, its just not smooth. Over all if you want a good tablet w/ verizon 3g/4g the xoom is a good chipoice, those wanting a finished product, I would hold out a few mnths. Thunderbolt vs fascinae coming soon, as soon as the phone hits the streets. I will compare stock TB to modded fascinate, for those considering the upgrade.
Final on the xoom, it is a good tablet, maybe expensive

forgot to include wifi, another big dissapoitment, xoom being 4g upgradeable, I thought would kill it, it did not.
Netgear wireless n router, 12mbps line
Xoom - 2mbps
Fascinate - 6.5mbps
Hopefully an update will fix that

Well, the fact that most benchmark applications, besides Smartbenchmark, are not optimized correctly for Tegra2 puts these benchmarks to shame. Nenamark caps at 30fps, Quadrant caps at 60 or 30fps, and 2D benchmarks cap at similar fps as well. Real world speed is faster, as well as games optimized for the Tegra2. Though, movie compatibility with the Fascinate is better because of the extra codecs courtesy of Samsung. Not sure whats wrong with your Wifi..

Hitting fps caps is not in the cards right now quadrant hits 6fps 2d and about 20 3d, maybe when its optimized it will reflect capability better but now it just looks like its close. Everyday useability, my only compplain is the keyboard is sometimes laggy in the browser, most likely will be patched in an update.

I have both. And its too early to do a fair comparison. Apps haven't been optimized for the xoom.
I'm just bummed out that i can't use my fascinate to tether the xoom. I'm stuck paying for verizon monthly bill until the fascinate offers wifi infrastructure not ad-hoc. or switch to a phone that actually offers it.

You can get 3g mobile hotspot free google it
Sent from my SCH-I500 using XDA App

I think partially the difference comes from the higher resolution on the Xoom. But we do have a great GPU indeed.

Sunspider Benchmark XOOM vs ATRIX

Sunspider Results (lower is better) from http://www.engadget.com/2011/03/09/ipad-2-review/
Code:
Apple iPad 2 (iOS 4.3) 2173.1ms
Apple iPad (iOS 4.2.1) 8207.0ms
Apple iPad (iOS 4.3) 3484.7ms
Apple iPhone 4 (iOS 4.2.1) 10291.4ms
Apple iPhone 4 (iOS 4.3) 4052.2ms
Motorola Xoom 2141.8ms
Motorola Atrix 4G 4100.6ms
Shouldn't atrix and xoom has the same results since they have the same hardware ?
http://www.webkit.org/perf/sunspider-0.9.1/sunspider-0.9.1/driver.html

Different OS on each device.
Hardware alone does not control the experience.
The OS has a lot to do with it as well.

Yeah I know 2.2 vs 3.0 but 2.2 was optimized for dual core by motorola. Shouldn't it be close though ?
The only way this makes sense is that Motorola rushed out the atrix and didn't bother to optimize for the hardware ...

GhostXtreme said:
Yeah I know 2.2 vs 3.0 but 2.2 was optimized for dual core by motorola. Shouldn't it be close though ?
The only way this makes sense is that Motorola rushed out the atrix and didn't bother to optimize for the hardware ...
Click to expand...
Click to collapse
No, that's not the only way it makes sense. It may be optimized for dual core, but that's hardly all that it's testing. 3.0 and 2.2 are very different animals.

I noticed these scores in the engadget review yesterday as well. But I figure the combination of the Xoom's 1.5GHz core clock as well as optimizations in Honeycomb probably account for it. I ran sunspider on my Atrix to confirm engadget's results as soon as I saw the article and scored 4068.xx so their results are definitely in the right ballpark.

isn't the Xoom running a higher reolution than the Atrix? Which would decrease the speed slightly on the Xoom.
Sent from my MB860 using XDA Premium App

Software!
XXtremeAzzKicker said:
isn't the Xoom running a higher reolution than the Atrix? Which would decrease the speed slightly on the Xoom.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Different softwares utilize the same hardware in diferent ways. A smaller screen with same resolution will require more coding than a larger Screen to achieve the same UI capabilities. More code slower processing.

I believe the tegra2 parts are different. T20 vs t20h. I forget which one is the lower powered mobile phone version.

My Atrix scores in the 2800 realm deodexed v.7 ADEO
Kueller said:
I noticed these scores in the engadget review yesterday as well. But I figure the combination of the Xoom's 1.5GHz core clock as well as optimizations in Honeycomb probably account for it. I ran sunspider on my Atrix to confirm engadget's results as soon as I saw the article and scored 4068.xx so their results are definitely in the right ballpark.
Click to expand...
Click to collapse

Kueller said:
I noticed these scores in the engadget review yesterday as well. But I figure the combination of the Xoom's 1.5GHz core clock as well as optimizations in Honeycomb probably account for it. I ran sunspider on my Atrix to confirm engadget's results as soon as I saw the article and scored 4068.xx so their results are definitely in the right ballpark.
Click to expand...
Click to collapse
Xoom has the same clock. It can be OC'd to 1.5 GHz but that's not available in stock form.

rjohnstone said:
Different OS on each device.
Hardware alone does not control the experience.
The OS has a lot to do with it as well.
Click to expand...
Click to collapse
Correct. For example, on the same PC, I get 2 very different runs, depending on the browser:
Firefox: 817.0ms
Chrome: 267.8ms

GhostXtreme said:
Code:
Apple iPad 2 (iOS 4.3) 2173.1ms
Apple iPad (iOS 4.2.1) 8207.0ms
Apple iPad (iOS 4.3) 3484.7ms
Apple iPhone 4 (iOS 4.2.1) 10291.4ms
Apple iPhone 4 (iOS 4.3) 4052.2ms
Motorola Xoom 2141.8ms
Motorola Atrix 4G 4100.6ms
Click to expand...
Click to collapse
As for the influence of software, notice the differences iOS made to the iPhone 4 & the original iPad.

Just wanted to update this thread with some new test results...
Sunspider 0.9.1 on Motorola Atrix
Opera 11 mobile: 2211.4ms
Stock Browser: 4040.0ms
I guess the honeycomb browser must support hardware acceleration w/tegra2 and our stock 2.2 browser evidently doesn't. Where's my update Moto? Don't leave your flagship phone crippled like this...

dont want to bother that but.. couldnt help myself
atrix's latest sunspider scores are 1717 and 1721...
firmware: 4.1.1 jellybean - cna 3.4.1 th3bill's port
stock jb browser

Why would you do this.
Sent from my Atrix 4G

A difference I saw b/w Samsung and HTC users.

Hello guys . I have been using my S2 for more than a year but never felt of overclocking it where as in many HTC phones thread on XDA i have seen people talking of overclocking their phone . Like Sensation many of its custom rom thread has written 1.7 or 1.5 Ghz oced . I have been noticing it for more than a year when I got S2 while at the S2 threads i rarely see people talk about Overclocking. What's your take on it ?

2 words - Exynos and Mali
Beats the hell out of competition without any sort of OC
Sent from the Matrix

anshmiester78900 said:
Hello guys . I have been using my S2 for more than a year but never felt of overclocking it where as in many HTC phones thread on XDA i have seen people talking of overclocking their phone . Like Sensation many of its custom rom thread has written 1.7 or 1.5 Ghz oced . I have been noticing it for more than a year when I got S2 while at the S2 threads i rarely see people talk about Overclocking. What's your take on it ?
Click to expand...
Click to collapse
yup there is no need to OC. It will only consume more battery and heat up the phone. S2 has a powerful processor

anshmiester78900 said:
Hello guys . I have been using my S2 for more than a year but never felt of overclocking it where as in many HTC phones thread on XDA i have seen people talking of overclocking their phone . Like Sensation many of its custom rom thread has written 1.7 or 1.5 Ghz oced . I have been noticing it for more than a year when I got S2 while at the S2 threads i rarely see people talk about Overclocking. What's your take on it ?
Click to expand...
Click to collapse
I've owned both S2 n Sensation I had Sensation XE so it was clocked at 1.5Ghz by default. That's why it was recommended and now 1.7Ghz coz One S Indians version has same chipset but clocked at 1.7Ghz. So that chipset can be OC'd without damaging. And on S2, everything's so smooth even with broken stuff on exynos that one simply does not talk about OCing

Yup, S2 isn't necessary to OC. Never felt like it's working too slow, even thinked about selling my S2 and buy worse LG G2x and save money, but saving it the other way, not buying new phone and holding S2 for longer. Really I don't get why people need to use quadcore CPU when IMO dual is efficient enough. I always flash different kernel/software just to save battery, even was working on CPU with UC to 600MHz per core.
HTC One S interests me most, but I don't have time for any deals and swapping. And this need to be said: Sense is awesome UI and all developers working on HTC phones, because they always try to port latest version unlike S2, which had very low interest in getting JB from S3 port or w/e other softwares except miui, aosp etc. (haven't said features ported like multiwindow now or note gallery are for nothing, they are also cool and thank for this). Liked it more than TW, but just thinking now, TW is user-friendly and not like first impression when it sucked for me, got familiar with it pretty fast.

I had previously Galaxy ACE which was clocked at 800 MHz which i felt was not efficient in running ICS ROMS so overclocked it to 900Mhz.. symptoms like overheating started to crawl in.. But in S2 i never OC'd I never felt it as slow sloth.. In jelly Bean i feel it lags sometimes, ICS and GB never lagged.. I dunno abt HTC but they made ICS run flawlessly on Desire C with 600Mhz proc!! So then i thought OC s for gamers, for normal calls, msging i think OC is useless...

rakeshishere said:
2 words - Exynos and Mali
Beats the hell out of competition without any sort of OC
Sent from the Matrix
Click to expand...
Click to collapse
yes true that

pasanjay said:
yup there is no need to OC. It will only consume more battery and heat up the phone. S2 has a powerful processor
Click to expand...
Click to collapse
Yes even i never felt like over clocking , a friend of mine has HTC Sensation and its always oced to 1.7
mesaj said:
Yup, S2 isn't necessary to OC. Never felt like it's working too slow, even thinked about selling my S2 and buy worse LG G2x and save money, but saving it the other way, not buying new phone and holding S2 for longer. Really I don't get why people need to use quadcore CPU when IMO dual is efficient enough. I always flash different kernel/software just to save battery, even was working on CPU with UC to 600MHz per core.
HTC One S interests me most, but I don't have time for any deals and swapping. And this need to be said: Sense is awesome UI and all developers working on HTC phones, because they always try to port latest version unlike S2, which had very low interest in getting JB from S3 port or w/e other softwares except miui, aosp etc. (haven't said features ported like multiwindow now or note gallery are for nothing, they are also cool and thank for this). Liked it more than TW, but just thinking now, TW is user-friendly and not like first impression when it sucked for me, got familiar with it pretty fast.
Click to expand...
Click to collapse
Yes totally agreed
Prashanthme said:
I had previously Galaxy ACE which was clocked at 800 MHz which i felt was not efficient in running ICS ROMS so overclocked it to 900Mhz.. symptoms like overheating started to crawl in.. But in S2 i never OC'd I never felt it as slow sloth.. In jelly Bean i feel it lags sometimes, ICS and GB never lagged.. I dunno abt HTC but they made ICS run flawlessly on Desire C with 600Mhz proc!! So then i thought OC s for gamers, for normal calls, msging i think OC is useless...
Click to expand...
Click to collapse
hmm I think even after more than a year (actually its going to be 2 years) S2 is still performing great with no lags and problems and the Exynous 4 is doing a great job .!

Some quick points here.
The CPUs used in the SGS2 (Cortex-A9) and the HTC Sensation (Qualcomm Scorpion) are vastly different beasts. One of the most consistent ways to measure a CPU's performance is in DMIPS. An A9 puts out 2.5DMIPS per clock cycle. A Scorpion puts out 2.1. So, at 1.2ghz, an A9 puts out 3000 DMIPS per core. At 1.5ghz, a Scorpion puts out 3150 DMIPS per core. However, A9 does true symetrical multi-processing whereas Scorpion does not. This means that in single threaded applications, a 1.5ghz Scorpion will be about 5% faster than a 1.2ghz A9. But, in multi-threaded applications, or in multi-tasking environments, the A9-based SOC (Exynos) pulls ahead. That's why HTC users tend to need to overclock more often. They were behind right off the bat and needed to compensate. In most cases, the A9-based Exynos at 1.2ghz is as fast as or faster than the 1.5ghz Scorpion-based Snapdragon S3. And, that doesn't even count the GPUs in these phones.
Also, someone mentioned that HTC has better developer support, having developers port newer versions of Sense to older phones. There's a reason for that. When Samsung updates their older phones, they include many/most aspects of the newer TW UI (such as the SGS2 now getting the Nature UX). HTC rarely does this, so WE have to do it for them. Hell, my old Droid Incredible had Sense 1.0. The slower Desire Z (and variants, like the Merge) got Sense 2.0, but we didn't. The next lineup of phones got Sense 3.0, and we didn't. Our Android 2.3 looked and acted the same as 2.2 and even 2.1, just smoother. So the community has to backport these features. With Samsung, they do it for us in many cases.

oc is not worth it, with this kind of powerful chipset. i even tried it (1,5 ghz) but i only realized a higher battery drain and just minor speed improvements.

jaykresge said:
Some quick points here.
The CPUs used in the SGS2 (Cortex-A9) and the HTC Sensation (Qualcomm Scorpion) are vastly different beasts. One of the most consistent ways to measure a CPU's performance is in DMIPS. An A9 puts out 2.5DMIPS per clock cycle. A Scorpion puts out 2.1. So, at 1.2ghz, an A9 puts out 3000 DMIPS per core. At 1.5ghz, a Scorpion puts out 3150 DMIPS per core. However, A9 does true symetrical multi-processing whereas Scorpion does not. This means that in single threaded applications, a 1.5ghz Scorpion will be about 5% faster than a 1.2ghz A9. But, in multi-threaded applications, or in multi-tasking environments, the A9-based SOC (Exynos) pulls ahead. That's why HTC users tend to need to overclock more often. They were behind right off the bat and needed to compensate. In most cases, the A9-based Exynos at 1.2ghz is as fast as or faster than the 1.5ghz Scorpion-based Snapdragon S3. And, that doesn't even count the GPUs in these phones.
Also, someone mentioned that HTC has better developer support, having developers port newer versions of Sense to older phones. There's a reason for that. When Samsung updates their older phones, they include many/most aspects of the newer TW UI (such as the SGS2 now getting the Nature UX). HTC rarely does this, so WE have to do it for them. Hell, my old Droid Incredible had Sense 1.0. The slower Desire Z (and variants, like the Merge) got Sense 2.0, but we didn't. The next lineup of phones got Sense 3.0, and we didn't. Our Android 2.3 looked and acted the same as 2.2 and even 2.1, just smoother. So the community has to backport these features. With Samsung, they do it for us in many cases.
Click to expand...
Click to collapse
Very well said mate .
Sent from my GT-I9100 using xda premium

chomsky101 said:
oc is not worth it, with this kind of powerful chipset. i even tried it (1,5 ghz) but i only realized a higher battery drain and just minor speed improvements.
Click to expand...
Click to collapse
Agree with you bro .
Sent from my GT-I9100 using xda premium