Database Info

[INFO] Benchmark results

Hi
I've been testing and comparing some of the top candidates og android phones on the market now.
The competitors are: Samsung Galaxy SII, Lg Optimus 2x (CM7) and HTC Sensation
And I must say, I'm pretty disappointed with HTC Sensation so far. Don't know if I'm just unlucky, or if we should expect an update on this in the future, but the GPU is way behind in comparison to the two others.
www.antutu.com benchmark results:
4578 - Samsung Galaxy SII
4456 - LG Optimus 2x
3758 - HTC Sensation
Goint through the details, the most worrying is HTC Sensation scores low on 2d/3d graphics, about half of what LG Optimus 2x scores, which is the winner, with a total of 297 + 350 in graphics. Sensation scores about 300 in total.
Qaudrant benchmark goes like this:
3678 - Samsung Galaxy SII
3120 - LG optimus 2x
2170 - HTC Sensation
Basically Samsung wins because of scoring higher on both CPU and memory (1gb ram)
LG Optimus 2x got he best GPU and Database IO (data transfer rate)
HTC Sensation is just way behind
What is your results? Is it just me, or could we hope for an update?
I have heard rumors about HTC Sensation only running on half of the kernels ind the GPU, is this true?

I heard it scores so low because of the Sense 3.0 requiring so much to run.

Maybe HTC should start concerning themselves more with function rather than form. I think everyone hear would rather have a faster device with less eye candy. If you look at what Samsung had done since the Behold II they have progressively toned Touch Wiz down with each iteration. I just hope we get the boot loader unlocked quick.
Sent from my LG-P999 using XDA App

I hated touchwiz, and still hate Samsung.
Always have liked the sense. To.each their own.
Sent from my HTC Sensation 4G using XDA Premium App

Sensation has such low benchmarks because it has qHD screen and Sense 3.0. Take Sense 3.0 away and this thing'll fly!
As I said in my own Sense 3.0 thread, having Sense 3.0 and qHD screen beats having high benchmarks. Benchmarks don't mean ANYTHING unless they're running the same UI overlay. Put them on stock/CyanogenMod and the Sensation will be a lot lot faster!

redbullcat said:
Sensation has such low benchmarks because it has qHD screen and Sense 3.0. Take Sense 3.0 away and this thing'll fly!
As I said in my own Sense 3.0 thread, having Sense 3.0 and qHD screen beats having high benchmarks. Benchmarks don't mean ANYTHING unless they're running the same UI overlay. Put them on stock/CyanogenMod and the Sensation will be a lot lot faster!
Click to expand...
Click to collapse
I agree with this. Sense requires a lot of ram and so does the qHD screen. That's the only reason benchmarks are so low. Get some stock GB on here and you'll see the difference. It also explains why the chip is clocked at 1.2GHz. I wonder how much further it can be pushed, though.

ericc191 said:
I agree with this. Sense requires a lot of ram and so does the qHD screen. That's the only reason benchmarks are so low. Get some stock GB on here and you'll see the difference. It also explains why the chip is clocked at 1.2GHz. I wonder how much further it can be pushed, though.
Click to expand...
Click to collapse
I've heard the chip is underclocked to 1.2ghz to save battery...it apparently can go to 1.5ghz, at least.

jrwingate6 said:
Maybe HTC should start concerning themselves more with function rather than form. I think everyone hear would rather have a faster device with less eye candy. If you look at what Samsung had done since the Behold II they have progressively toned Touch Wiz down with each iteration. I just hope we get the boot loader unlocked quick.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
If you don't like sense then why buy the Sensation? That's like buying car that's a stick and then complaining because it's not an automatic. Yes sense is on the phone, yes sense may cause lower benchmarks, yes it's heavily intergrated. If those things bother you then perhaps purchasing a sensation was a mistake...not trying to start an argument, but really it illogical to complain about something you knew going in was a core part of the phone. I don't like touchwiz...so I don't purchase devices with touchwiz on them...it wouldn't make sense for me to buy a phone with touchwiz knowing I don't like it and then complaining about it.

Some ignorant people just don't get the fact. HTC had been advertised about Sense 3.0 for Sensation and we all do know it is a core part of the phone. So don't get the phone if you are for benchmarks isn't it? this sound silly, doesn't it?

Ah! Of course... the screen res is higher, that should influence on the benchmark for sure. Moto Xoom scores low also, but that too, has a higher res.
Im just concerned if it is still scoring lower when on stock. Does anyone have a true benchmark of the Adreno220, which is within the Sensation?
The benchmarks I found on the internet, the Adreno220/M8660 beats the crap out of LG optimus 2x and SGSII.
Anyone know if there is a truth to the "half cores only support" yet?

larsn84 said:
Ah! Of course... the screen res is higher, that should influence on the benchmark for sure. Moto Xoom scores low also, but that too, has a higher res.
Im just concerned if it is still scoring lower when on stock. Does anyone have a true benchmark of the Adreno220, which is within the Sensation?
The benchmarks I found on the internet, the Adreno220/M8660 beats the crap out of LG optimus 2x and SGSII.
Anyone know if there is a truth to the "half cores only support" yet?
Click to expand...
Click to collapse
When we get s-off, we'll have some true benchmarks for all devices. Optimus 2x, Galaxy S II, Sensation, and possibly Moto Atrix. Put them all on latest release of CyanogenMod7 and benchmark them using a range of apps.

ImHuge07 said:
I heard it scores so low because of the Sense 3.0 requiring so much to run.
Click to expand...
Click to collapse
Actually its mainly because HTC chose to use old technology and use 2 second gen snapdragon chips which use the arm 8 instruction set, instead of using a cpu based on the new arm 9 technology which is what every other new dual core cpu is set up with.

TheRiceKing said:
Actually its mainly because HTC chose to use old technology and use 2 second gen snapdragon chips which use the arm 8 instruction set, instead of using a cpu based on the new arm 9 technology which is what ever other new dual core cpu is set up with.
Click to expand...
Click to collapse
As other people have stated, this view is nonsense. Scorpion is a parallel development to A9. It has advantages and disadvantages in comparison.

lol if you want to try and call it nonsense... I'm really just trying to help educate you and explain, but you can continue to think that if you wish
Scorpion incorporates some ARM 9 features, its basically like ARM 8 and a half and that is being optimistic -_-'

TheRiceKing said:
Actually its mainly because HTC chose to use old technology and use 2 second gen snapdragon chips which use the arm 8 instruction set, instead of using a cpu based on the new arm 9 technology which is what ever other new dual core cpu is set up with.
Click to expand...
Click to collapse
Your post is wildly inaccurate... First of all there is no ARM 8 instruction set. All A8, A9, and Scorpion processors use the ARMv7 instruction set. Second, Scorpion is Qualcomm's own architecture, it is not based on the A8 design, they created their own design from scratch. It is not as simple as A9 > A8 for this reason. The Scorpion architecture implements features that are not available on A8 but are available on A9. The main difference between the Scorpion and the A9 is the number of pipeline stages. The Scorpion has 13 while the A9 has 8. This is positive and negative for both, as more pipeline stages improves throughput, but is more costly if an instruction has to be aborted and the pipeline flushed.
I have gotten a lot of responses telling me that the Scorpion is based off A8 and tweaked. This is not correct. If it were simply tweaked, it would not be able to have a clock over 1 GHz without overclocking, as that is the limitation of the A8 architecture. It also could not support dual cores, again a limitation of A8. The Scorpion also has partial support of out-of-order processing. This is impossible on an A8 processor, but is fully supported on an A9.
You are correct in saying that every other dual core is based off an A9 processor because the A9 is the only design you can license from ARM that can support dual cores. The only alternative is for a company to license the instruction set itself and design their own architecture (Qualcomm's approach). I should also point out that the A9 processors are synchronous, while the MSM8260 is asynchronous, allowing separate clock speeds and voltages to each core, which can greatly increase battery performance (especially on processes that only utilize 1 core).
I will agree that A9 is more advanced than Scorpion, but it is not by nearly as much as the "Scorpion is A8" argument would indicate. The MSM8260 can also support clock speed up to 1.5 GHz, so the Sensation can be overclocked without actually overclocking the processor.

LittleMerc said:
Some ignorant people just don't get the fact. HTC had been advertised about Sense 3.0 for Sensation and we all do know it is a core part of the phone. So don't get the phone if you are for benchmarks isn't it? this sound silly, doesn't it?
Click to expand...
Click to collapse
Exactly! I don't understand the logic of people that purchase a device that they know has certain features and then complain about it. That's like buying a phone with a slide out keyboard and then complaining saying you don't like the fact that it has a slide out keyboard. My thing is, Sense is not a surprise. Everyone knew going in that it was there, and they know what it is and how it works. If certain people don't like that, then they probably shouldn't have bought the phone. Doesn't make sense to complain about getting exactly what you were paying for.

mpjohns3 said:
Your post is wildly inaccurate... First of all there is no ARM 8 instruction set. All A8, A9, and Scorpion processors use the ARMv7 instruction set. Second, Scorpion is Qualcomm's own architecture, it is not based on the A8 design, they created their own design from scratch. It is not as simple as A9 > A8 for this reason. The Scorpion architecture implements features that are not available on A8 but are available on A9. The main difference between the Scorpion and the A9 is the number of pipeline stages. The Scorpion has 13 while the A9 has 8. This is positive and negative for both, as more pipeline stages improves throughput, but is more costly if an instruction has to be aborted and the pipeline flushed.
I have gotten a lot of responses telling me that the Scorpion is based off A8 and tweaked. This is not correct. If it were simply tweaked, it would not be able to have a clock over 1 GHz without overclocking, as that is the limitation of the A8 architecture. It also could not support dual cores, again a limitation of A8. The Scorpion also has partial support of out-of-order processing. This is impossible on an A8 processor, but is fully supported on an A9.
You are correct in saying that every other dual core is based off an A9 processor because the A9 is the only design you can license from ARM that can support dual cores. The only alternative is for a company to license the instruction set itself and design their own architecture (Qualcomm's approach). I should also point out that the A9 processors are synchronous, while the MSM8260 is asynchronous, allowing separate clock speeds and voltages to each core, which can greatly increase battery performance (especially on processes that only utilize 1 core).
I will agree that A9 is more advanced than Scorpion, but it is not by nearly as much as the "Scorpion is A8" argument would indicate. The MSM8260 can also support clock speed up to 1.5 GHz, so the Sensation can be overclocked without actually overclocking the processor.
Click to expand...
Click to collapse
Wow, informative post. That should stop the A9 >A8 (Scorpion) because it's a bigger number rubbish, for a while.
Sent from my HTC Sensation Z710e using XDA App

How do the Dual cores work in this phone?

I got my sensation and love it, I have Android Revolution 3.1 and the RCMix version 1 kernel. It is currently overclocked to 1.78 ghz with Daemon OC.
I was curious though, I heard that some games and apps are not optimized for the dual cores. How do they work in these situations? Will one power down while the other works?
Also, In the newest update for Revolution HD, in the change log he mentions how the dual cores run constantly and that this is a first. Wouldn't this drain battery life?
Sorry about starting a new thread, im just curious. Thanks for any help!!

yes it s a very good question
i am gonna try that rom
especially about battery life.
any idea ?

i'd love the answer to this one myself.

Anyone??
Sent from my Virtuous Sensation, and loving it...

About the thing where the cores run constantly; I've been following the oc dual core thread, and someone found a way to keep both cores online and that overall, it had almost no effect on battery life but seemed to increase performance slightly.
To describe the way our dual core chips are setup would be very complicated, and would draw away from you initial question.
Just know, it shouldn't effect your battery too much.
Sent from my HTC Sensation 4G using XDA App

Generally
Dual Core = Better battery life
As long as the software is optimised to use them both

Really? Wow i thought dual core will consume more battery
Sent from my GT-I9100 using XDA Premium App

The dual cores in our phones are asynchronous, meaning instead of both cores splitting the workload evenly like some other chipsets, one core will remain offline until it's needed then spool up to assist with the load. This was causing a problem with overclocking because only one core was recognizing the clock speed and governor settings. Keeping both cores idling allows them to both recognize the proper settings. The thread about it can be found here http://forum.xda-developers.com/showthread.php?t=1233103

CrazyCharlie said:
The dual cores in our phones are asynchronous, meaning instead of both cores splitting the workload evenly like some other chipsets, one core will remain offline until it's needed then spool up to assist with the load. This was causing a problem with overclocking because only one core was recognizing the clock speed and governor settings. Keeping both cores idling allows them to both recognize the proper settings. The thread about it can be found here http://forum.xda-developers.com/showthread.php?t=1233103
Click to expand...
Click to collapse
dual core. Keeping it simple
think of a double Decker bus as synchronous CPUs
And two single deck buses. As asynchronous CPUs
passengers are your workload.
Most cpus out there are synchronous. so this means both processors split the load continuously at any one time. . Eg galaxy s2 and Intel CPUs
Asynchronous
Each core works independently from the other. Amd cpus do this and sensation.
But sensation only keeps one active till it needs the other one
Synchronous dual core cpus. These are your double decks. the bus Carries people and uses both floors at one time
Asynchronous in sensation.
these are your single decks. Only one bus will carry passengers. But when the bus is full or cannot cope the second bus is used
Sent from my HTC Sensation Z710e using XDA App

xl VipeR lx said:
dual core. Keeping it simple
think of a double Decker bus as synchronous CPUs
And two single deck buses. As asynchronous CPUs
passengers are your workload.
Most cpus out there are synchronous. so this means both processors split the load continuously at any one time. . Eg galaxy s2 and Intel CPUs
Asynchronous
Each core works independently from the other. Amd cpus do this and sensation.
But sensation only keeps one active till it needs the other one
Synchronous dual core cpus. These are your double decks. the bus Carries people and uses both floors at one time
Asynchronous in sensation.
these are your single decks. Only one bus will carry passengers. But when the bus is full or cannot cope the second bus is used
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
first : the best explanation so far about how this phone works , two thumbs up !!!!
2nd : I'm currently thinking on moving from my Htc DHD to a new dual core phone ( had the Atrix , hated the pentile screen )
so in terms of everyday use ( i don't give a s**t about benchmarks ) which one is better to get - SGS2 or HTC Sensation ?

moshikko said:
first : the best explanation so far about how this phone works , two thumbs up !!!!
2nd : I'm currently thinking on moving from my Htc DHD to a new dual core phone ( had the Atrix , hated the pentile screen )
so in terms of everyday use ( i don't give a s**t about benchmarks ) which one is better to get - SGS2 or HTC Sensation ?
Click to expand...
Click to collapse
LOL well I.am the noobproof dude. so just keeping it simple.
At the moment its hard to say. Depends on your taste and also true power of sensation isn't even seen yet
Sent from my HTC Sensation Z710e using XDA App

SetCPU?

Will programs like SetCPU work on a rooted MT4gs?

They will but since we don't have source won't be able to overclock and only able to use one cpu to mess around with...
Sent from my Supercharged MT4G Slide Running Undead's Senseless ROM using XDA App

Jesuddha85 said:
They will but since we don't have source won't be able to overclock and only able to use one cpu to mess around with...
Sent from my Supercharged MT4G Slide Running Undead's Senseless ROM using XDA App
Click to expand...
Click to collapse
Wait, that confused me. Does that mean setcpu is only scaling one core?
Sent from my Supercharged MT4G Slide Running Undead's Stock Sense ROM using Tapatalk

I underclock. Saves battery.
Sent from my MyTouch 4G Slide using xda premium

I like to overclock too (in the future).
Anybody knows to change the auto value of the brightness?
like 10 35 100

I've been trying to map out the hardware, and near as I can tell without physically opening up the device...
Seems we have the 8660 version of the qualcomm snapdragon processor, and not the 8260 version.
The 8260 is rated at 1.2, the 8660 is rated at 1.5
I'm pretty sure that we have the 8660 governed down to 1.2 instead of the 1.5 it should be at.
Can anyone confirm or deny this and explain why?
I'm drafting a paper on snapdragon that i'll post when it's done - but honestly i'm taking a week off and just playing with the phone - all the games i've gotten and haven't really used and so forth.

Hmmmmmmm that would mean we have a better processor then the sensations. Ha +1 for Doubleshot. I will do some research on it and let you know.
Sent from my myTouch_4G_Slide using xda premium

Undeadk9 said:
Hmmmmmmm that would mean we have a better processor then the sensations. Ha +1 for Doubleshot. I will do some research on it and let you know.
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
Clock Frequencies
Recommended Minimum Clock Frequency: 1200 MHz
Recommended Maximum Clock Frequency: 1500 MHz
Source: http://pdadb.net/index.php?m=cpu&id=a8660&c=qualcomm_snapdragon_msm8660

Blue6IX said:
I've been trying to map out the hardware, and near as I can tell without physically opening up the device...
Seems we have the 8660 version of the qualcomm snapdragon processor, and not the 8260 version.
The 8260 is rated at 1.2, the 8660 is rated at 1.5
I'm pretty sure that we have the 8660 governed down to 1.2 instead of the 1.5 it should be at.
Can anyone confirm or deny this and explain why?
I'm drafting a paper on snapdragon that i'll post when it's done - but honestly i'm taking a week off and just playing with the phone - all the games i've gotten and haven't really used and so forth.
Click to expand...
Click to collapse
Without actually pulling it and inspecting the processor, I looked at this thread:
http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
which tells us that we have the 8260 chip. However, the 8260 and 8660 are both rated at 1.2-1.5, so who knows...
In the end we need overclock anyway just for fun, and WE NEED kernel source so we can get low voltage kernels!!!

it's a MSM8x60 series Snapdragon processor.
The MSM8260 is for HSPA+, and MSM8660 is for multi-mode HSPA+/CDMA2000® 1xEV-DO Rev.B. This basically means MSM8x60 will offer support for most of the contemporary mobile broadband air interface protocols such as HSPA+, LTE and WiMAX.
MSM8x60 features Adreno 220 GPU (88M triangles/sec, 532M 3D pixels/sec, 1080p video recording and playback up to 30 frames/second) and it supports for 24-bit WXGA 1280x800-pixel resolution displays.Not bad!
So yes 1.5ghz should be ok, since they are likely to be the same. but i m Wondering if you need a sort of special Thermal Compound or if it will be ok. Maybe a different battery, more amps since it may drain too fast and damaged the battery?

cedde said:
... but i m Wondering if you need a sort of special Thermal Compound or if it will be ok. Maybe a different battery, more amps since it may drain too fast and damaged the battery?
Click to expand...
Click to collapse
(not to cut out the helpful info in your post)
The anker battery solved my number one issue with a stock phone, which is heat. The phone would heat up tremendously, much more so then it seemed it should.
My theory was spreading the same level of drain over a higher volume of charge would help with the heat issue, since heat = waste. Lithium-ion batteries become extremely inefficient the more load is put on them.
I don't know if it's the quality of materials, or in fact the drain being spread over a greater volume is what solved the issue - most likely it was a combination of both.
If anyone has been following the development of the snapdragon, series 2 (we have series 3) processors suffered from severe overheating problems, resulting in the chip only being usable at lower and lower temperatures.
Overclocking our processor will definitely generate more heat. A stock battery will give the device a very low survival rate for such an act, though the aftermarket anker battery might give you a chance. Without the anker battery you'd probably have to have it plugged in to some power source to get any usable run-time out of it at full speed.
Thanks for posting some info on the processor - i'm confused because I know in build.prop it's listed as 8660 architecture - but i'm sure I saw the 8660 designation somewhere else in the system files - damned if I can remember where though.
Qualcomm doesn't seem to differentiate between the 8260 and 8660 in any of their documentation, and i've sent them an email to see if they'll clarify it a bit for me - though I had no business to send the email from so I doubt i'll get a reply.

I have tried it and it doesn't work properly, my battery drains out like hell.

Overclocking or the battery?

Can't overclock with it yet. But underclocking with setcpu works great.
Sent from my myTouch_4G_Slide using XDA App

Bump.... Anyone? Saving battery? Underclock?
Sent from my MyTouch 4G Slide using Tapatalk

Don't know if it means much but I just ran CF-Bench and it lists the board platform as msm8660. If it is the same processor as the EVO 3D, it explains the earlier rumors of it being a 3D phone when leaks first started to show up on the web. A quick search on PDADB.net shows the EVO 3D as the oldest phone with that processor. It also shows the 4G Slide as a 8260 so I guess we just need someone to physically look at it. It would be interesting for someone with a sensation to see if CF-Bench reports a 8260 or 8660 for them.

The overclocking kernal is out
Sent from my mt4gs

sensation performance / aSMP info needed please

Hi,
i recently return my samsung (4th time) galaxy s2 becouse of various defects , i been looking at the sensation however i have a few questions , firstly for all its issues i like how fast and responsive the galaxay was however when i tryed the sensation i noticed its not as smooth as the galaxy or that much smoother then the desire hd.
One possible reason for this i noticed was that the sensation uses a asmp cpu , which seems a bit cheeky to me. I mean im buying a dual core phone so i would like both cores to work at the same time as opposed to one working then the second kicking in when the first is loaded. From what ive read ics should have better support for this setup , so i was curious does anyone think we will see that much of a difference bearing in mind the sensation is asmp.
I notice there`s a lot of talented devs from the desire development and hd which is encouraging so i was hoping to learn from various users how much of a performance increase there seeing in custom roms ie is the browser jerky like stock ??
Appreciate any / all feedback thank you

I'm interested in some more more info on this topic as well.....
Sent from my Sensation using xda premium

Read up!
ok so aSMP doesn't really work in the method of core 0 gets loaded then core 1 kicks in, thats way off.
basically SMP cpus like Tegra and Samsung's both cores run at the same speed, so core 1 follows core 0. This doesn't mean that core 1 is actually processing anything. In most cases due to gingerbread the phone is still mainly running on one core unless the app supports multicore.
aSMP allows the cores to run completely independent. This is great for battery life. Core 0 can do things like play games and stuff at full speed while core 1 handles background data.
so playing angry birds while syncing photos on flickr:
core 0 could be running at full 1.5Ghz
core 1 could be running at 500Mhz just do handle the syncing
This is basically the idea. We will get better support with ICS for full and proper support for multiple cores and the kernels will only get better as devs learn.
http://forum.xda-developers.com/showthread.php?t=1233103

Hi,
Thank you for you detailed reply ive been following the thread you posted which is what led me to posting question here , i obviously misunderstood what was being said. That being said im no expert but if i buy a dual core phone id rather have both cores committed to one task like pc ... this is one of the things thats making me hold back on sensation. Althougth its a great phone with great ui and fantastic potential with future updates and dev support to the touch at present the galaxy s2 just seems smoother with the way its doing thing.
As i say thou im not expert i can appreciate theres other factor to take into account such as kernal etc, im just going with hands on usage and trying to evaluate the future potential for both devices before making a decision to which i should choose

tonnytech said:
Hi,
Thank you for you detailed reply ive been following the thread you posted which is what led me to posting question here , i obviously misunderstood what was being said. That being said im no expert but if i buy a dual core phone id rather have both cores committed to one task like pc ... this is one of the things thats making me hold back on sensation. Althougth its a great phone with great ui and fantastic potential with future updates and dev support to the touch at present the galaxy s2 just seems smoother with the way its doing thing.
Click to expand...
Click to collapse
The sensation's CPU works in a much more power efficient way, while still offering the speed of any other dual core CPU. It allows different clock speeds for different cores so applications using only a single core will be able to clock it differently to those using the other in the background. Computers, especially laptops work in a similar way, as there is a need for power efficiency. Realistically the Galaxy SII runs smoother due to it running a much less resource hungry skin on top of android, but both the CPU of the sensation and the Galaxy SII are both of a similar calibre, so it is very difficult to say which is better.

again thanks for the reply , defintly understand how this asmp buisness works more now which has given me some stuff to think about

tonnytech said:
Hi,
Thank you for you detailed reply ive been following the thread you posted which is what led me to posting question here , i obviously misunderstood what was being said. That being said im no expert but if i buy a dual core phone id rather have both cores committed to one task like pc ... this is one of the things thats making me hold back on sensation. Althougth its a great phone with great ui and fantastic potential with future updates and dev support to the touch at present the galaxy s2 just seems smoother with the way its doing thing.
As i say thou im not expert i can appreciate theres other factor to take into account such as kernal etc, im just going with hands on usage and trying to evaluate the future potential for both devices before making a decision to which i should choose
Click to expand...
Click to collapse
Neither architecture, SMP or aSMP, will commit both cores to one task unless the app is multithreaded and it currently needs the use of both cores. This is the same way that multicore pc's operate. That's why when quad core CPU's first came out people said that they didn't feel any faster than comparable dual core chips - most existing apps at that time were written for single or dual threaded use so the third and fourth cores largely sat unused. The pc doesn't just force the use of the extra cores just because they are there (regardless of how they scale, aSMP or SMP).
Sent from my HTC Sensation Z710e using xda premium

Also the new firmware has made it smoother due to extra optimisations. Web browser is not as good as the galaxy S 2 due that being GPU accelerated. Power wise the Sensation you will get somewhat more out of your battery life wise.

hardensm said:
Realistically the Galaxy SII runs smoother due to it running a much less resource hungry skin on top of android, but both the CPU of the sensation and the Galaxy SII are both of a similar calibre, so it is very difficult to say which is better.
Click to expand...
Click to collapse
If you look at my thread and see the post:
MSM8x60:
Adreno 220 GPU
2x Cortex A8 Based Cores
512KB L2 Cache
45nm
upto 333Mhz LPDDR2
Exynos 4210:
Mali 400 GPU
2x Cortex A9 Based Cores
1MB L2 Cache
45nm
support for LPDDR2/DDR3
Tegra 2:
ULP Geforce GPU
2x Cortex A9 Based Cores
1MB L2 Cache
40nm
support for 600Mhz LPDDR2
So the biggest thing is is that the Exynos is based on a new core micro-arch then the Snapdragon 2, also it has the ability to support DDR3 memory. To go into more detail about ARM Cortex.
Items that A8 and A9 have in common:
Jazelle RCT for JIT Compilation
Neon SIMD Instruction Set (Optional)
Thumb2 Instruction set
VFPv3 Floating Point Unit (Optional)
Cortex A8:
Superscalar Dual-Issue Micro-Arch
2.0 DMIPS/Mhz
Cortex A9:
Out-Of-Order Superscalar Micro-Arch
2.5 DMIPS/Mhz
Jazelle DBX for Java Execution
Dual-Core Processing Built In
The SGSII has a new generation architecture as so does the Tegra

This thread is iteresting. I want to continue that.
my cpu0 and cpu1 arrive at 1,7 ghz. so cpu1 doesnt arrive up to 500 mhz

[q] cpu chipset

does anyone know if setting the CPU SPEED to 1.5 GHz is dangerous while the SENSATION XL has the same chipset as the desire s has (Qualcomm Snapdragon MS8255) and the SENSATION XL's CPU speed is set to 1.5GHz .

sensation has msm8260 (dual core 1.2-1.5 GHz and adreno 220)

Sensation XL indeed has MSM8255.
Just like in PCs, chipsets in phones are binned not only by their type, but also by their target frequency. You don't go overclocking Core2Duo 1.8 GHz to 2.4 GHz because it's "the same CPU", right? Because it isn't the same CPU. The same applies here.

אז זה מסוכן או לא ?

English, please.
Answer - would you run the CPU on your computer at 1.5x the speed it was made to run, because there's CPU with the same name (i3/i5/i7/whatever) that runs at 1.5x the speed?
The same answer applies to your phone.
I expect people to be able to make minimal logic work with their own brains rather than just answering "yes/no". I think that this way people actually understand more than what they've asked for.

i guessed that was the answer but just wanted to be sure...
thanks anyway !

msm8255 should run stable on 1.5GHz (if stock freq is lower)

441Excelsior said:
msm8255 should run stable on 1.5GHz (if stock freq is lower)
Click to expand...
Click to collapse
No it won't. It depends on the specific part, and few parts run stock 1.5 GHz without stability issues surfacing / burning out very fast (if overvolted).
If you really want - you can try it on T-Mobile G2, that has MSM8255 of the earliest bin, with stock at 800MHz. Good luck, don't forget to write how did you like a phone as a toaster.
I suggest refraining from bad advice, especially when it's in the forum and it's not your phone you're talking about. You can burn your phones as much as you like, but don't go around suggesting it to others. Just let me understand something: you have stock non-rooted ICS and have no idea about such basics as which guide to use to downgrade, but you allow yourself posting about chipset frequencies?

so which speed can i overclock to that shouldn't turn my device into a toaster ?

deanshugan said:
so which speed can i overclock to that shouldn't turn my device into a toaster ?
Click to expand...
Click to collapse
1.2 runs most things with no lag.
Sometimes you're the windshield; sometimes you're the bug.
- Mark Knopfler.

The point is each chip is different even if the same model
What works for me on my device won't necessarily work for you
So test and see if your brave enough, but be aware of the consequences
Sent from my Nexus 4 using xda premium

I overclock my ds to1.5 every time I play games and it doesn't even get warm. So I think it's pretty harmless.
Sent from my Desire S using xda premium