It would be really nice to have some devs working on a Nexus One ROM. That phone is really nice. There is already a custom ROM so i guess we can start from there and just modifying the hell out of it to make it fit on the HERO[CDMA].
Link(s)
Here is a link to the first Nexus One ROM... By: MODACO!! http://forum.xda-developers.com/showthread.php?t=614186
Here is the link to the Nexus One forum. http://forum.xda-developers.com/forumdisplay.php?f=556
Great thread to start. I would like to see the nexus rom on the hero. I like those live wallpapers. Maybe one day we could have a live wallpaper based on the weather like the HD2.
david279 said:
Great thread to start. I would like to see the nexus rom on the hero. I like those live wallpapers. Maybe one day we could have a live wallpaper based on the weather like the HD2.
Click to expand...
Click to collapse
You do know the Hero has a 512MHz CPU, while the Nexus One & the HD2 have a 1GHz Snapdragon. The Hero only has 256mb of RAM, while the Nexus ONe & HD2 have 512mb of RAM. also the Nexus One's GPU is leaps & bounds more powerful than the one in the Hero. So the likelihood of the Hero getting live wallpapers & actually basic functionality at the same time is slim to none.
gu1dry said:
You do know the Hero has a 512MHz CPU, while the Nexus One & the HD2 have a 1GHz Snapdragon. The Hero only has 256mb of RAM, while the Nexus ONe & HD2 have 512mb of RAM. also the Nexus One's GPU is leaps & bounds more powerful than the one in the Hero. So the likelihood of the Hero getting live wallpapers & actually basic functionality at the same time is slim to none.
Click to expand...
Click to collapse
QFT: Remember the Hero had the animated widgets removed from sense because of the lag the animations created. Animated wallpaper and such, while possible doesn't seem very practical for the time being on our devices.
gu1dry said:
You do know the Hero has a 512MHz CPU, while the Nexus One & the HD2 have a 1GHz Snapdragon. The Hero only has 256mb of RAM, while the Nexus ONe & HD2 have 512mb of RAM. also the Nexus One's GPU is leaps & bounds more powerful than the one in the Hero. So the likelihood of the Hero getting live wallpapers & actually basic functionality at the same time is slim to none.
Click to expand...
Click to collapse
Actually, the Hero has 288MB ram but who's counting
Seriously, before we get this we need a working .29 kernel otherwise we wouldnt be able to get the damn thing to boot. And if we did we would have the same trouble as we are having with 2.0 (camera issues, sync issues, etc). We will get to the fun stuff guys. Trust me. But before we focus on this stuff let's let the devs do the hard work and however we can help, let's help. Once we get the kernel then we get to the fun stuff.
Also, as for the CPU, it is *theoretically* possible to overclock this processor. The Dream was underclocked to 384Mhz and it ran a lot faster when overclocked to the standard 528Mhz. If we could actually push this thing to 768Mhz it could be really nice but like I said. That's theoretical. And we still have the GPU issue as well.
And the HD2 doesn't have 512 megs of RAM if I remember correctly. I think it only has about half that, but same processor is right.
deadonarivalry said:
And the HD2 doesn't have 512 megs of RAM if I remember correctly. I think it only has about half that, but same processor is right.
Click to expand...
Click to collapse
It has 488mb of RAM to be precise.
Not that I know half as much as you guys do, but when I had my touch pro 2 I had a custom windows 6.5 rom that was ported from the HD2 with the same live wallpapers based on the weather. For example when the weather widget displayed cloudy weather clouds would move across the screen. I remember reading that the touchpro 2 has a qualcomm 528 mhz processor like that in our heros. The tp2 had no lag at all and the animations were quick and detailed so I am just having a hard time seeing why the hero cant handle this, is it a difference with the way android and win mobile handle this type of stuff?
Related
I currently have a Wing OCd to 247Mhz. I was wondering whats the fastest HTC phone out there? Processor-wise.
I preferably want one that xda-developers support, as I love the custom ROMS especially JustStable.
Anyone have any ideas? 500+Mhz pref?
I tried search function, but most questions were like G1 VS Iphone or the new toshi/samsung 1ghz phones. I would love a 1 GHz phone, but not if you guys dont make custom ROMs for it
EDIT: please include Mhz of processor if suggesting a phone. Thanks!
I believe the fastest processor HTC has used in their handsets so far is the Qualcomm 528MHz, but there are plans to release a handset (HTC Leo?) with the 1GHz snapdragon
From the ones actually on sale
Touch Pro 2
Diamond 2
I presume...
orb3000 said:
From the ones actually on sale
Touch Pro 2
Diamond 2
I presume...
Click to expand...
Click to collapse
...or
Touch PRO
Diamond
They have the same processors.
Fastest phone is HTC Athena (624 mhz)
there are custom roms for it but not alot and not updated as frequent like Diamond.
D1ab70 said:
Fastest phone is HTC Athena (624 mhz)
there are custom roms for it but not alot and not updated as frequent like Diamond.
Click to expand...
Click to collapse
And in a moment it will be Touch PRO
Higher clock speed does not always equal faster processor.
I'm waiting on the Leo...very bored with these current small CPU's!
cmstackar said:
Higher clock speed does not always equal faster processor.
Click to expand...
Click to collapse
Read how the guy comments his achievement.. this time it seems to be faster. Of course there are lots of issues in this alpha-pre-alpha state. Lets hope he wont burn down the device
cmstackar said:
Higher clock speed does not always equal faster processor.
Click to expand...
Click to collapse
true, but I bet any decent 800Mhz phone with custom ROM will beat the **** outta my Herald 201Mhz with custom ROM in terms of speed
I already posted this in the Nexus dev forum, and I hate to clutter the boards, but I know that there are a bunch of talented devs here that may not see it on those forums. If we can bust the 30fps cap for good, and get the GPU overclocked, then we could see some serious gaming performance out of our Snapdragon devices.
I'm sure we all heard about being able to overclock the GPU on some of the old MSM devices, but the Snapdragon handles the graphics chip in a different way. The goal of this thread is to try and overclock the GPU on Snapdragon devices as well.
There is nothing GPU related in acpuclock-scorpion.c (the Snapdragon cpu clock settings) at least for setting gpu clock speed as far as I can tell.
In board-mahimahi.c (Nexus board file) and board-supersonic.c (Evo board file) there is some kgsl init code, but so far as I can tell it isn't setting the clock there, instead it seems to be pointing to PWR_RAIL_GRP_CLK to set the clock in both devices. It defines the variable in each of those files but I'm not sure where that variable is set, since it doesn't seem to be in any of the other board files as far as I can tell. I could be completely off here too though.
In drivers/video/msm/gpu/kgsl/kgsl.c there is a method called kgsl_clk_enable that seems to be called whenever the GPU is enabled. It looks like this:
Code:
/* the hw and clk enable/disable funcs must be either called from softirq or
* with mutex held */
static void kgsl_clk_enable(void)
{
//clk_set_rate(kgsl_driver.ebi1_clk, 128000000);
clk_set_rate(kgsl_driver.ebi1_clk, 245000000); // Looks like it sets the GPU clock, right? Wrong.
clk_enable(kgsl_driver.imem_clk); // Enable the clock
clk_enable(kgsl_driver.grp_clk); // Enable another clock, but why?
}
The line that's been commented out is the original value, I replaced it with my value on the line below it in a failed attempt to overclock it. Probably a stupid effort on my part, I doubt it's that simple, but it was worth a shot. The comments at the end of the line are also my additions.
According to the clk.h files in the standard linux kernel, clk_set_rate is obviously a method to set the clock rate. The first variable is a struct that tells it which clock to set, and the second variable is a long value that is the rate you want it set at. Is it setting the right clock there for Snapdragon chips? Or is it only the clock for older chips?
I'm in way over my head with this source, I'm but a lowly Java dev, but I really wanna solve this. Can anyone with a little more experience than me throw in a little more info? Sorry if it doesn't make much sense, if it isn't clear just ask me & I'll try to explain a little more.
Regards,
Jesse C.
EDIT: Okay I did a little more digging and those kgsl settings should work for QSD8x50 chips. In the config file, under Drivers, Graphics Support, it allows you to enable 3D accelleration for QSD8x50 & MSM7x27 chips. The tag for that is CONFIG_MSM_KGSL_MMU. If you check in kgsl.c it checks to see if that is enabled in the config, and if it is then it compiles and uses kgsl.c & all of the kgsl code. That tells me that the clock is either not being set, or the wrong clock is being set. I'm adding some debug code right now so I can see in dmesg what code is actually being run.
Dude I have no idea how to do this but bump and best of luck
Sent from my PC36100 using XDA App
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
fstluxe said:
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
Click to expand...
Click to collapse
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Geniusdog254 said:
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Click to expand...
Click to collapse
okey, But as far as I know that code is not standard... Becouse the Vugue msm7500 device is originally WM device.. so the Smart dzo managed this custom code.
I wil follow the nexus form .. This is Damn interesting !
i wish you guys the best of luck..wish i could help..i love xda..lol
I'm going to bump this, would be nice if more people were working on this.
Man... I absolutely love my phone. It really sux that this even needs to be asked. This device is so much more capable and I cannot understand why HTC would cripple it so badly. Look at the Samsung galaxy s or the Droid x. Or even a more similar phone like the nexus or incredible. They all stomp this phone when it comes to anything graphics wise even if it is just swiping home screens. It makes me sad. Lol
I love how it makes you sad, but you still lol. Lol (correctly placed)
This is big but first let's get a true cap fix!
Sent from my Evo 4G
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
psych2l said:
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
Click to expand...
Click to collapse
I don't know, yet I am in deep havoc lol. I activated my phone on the 20th. I have till 13th of July to pay my bill, so don't know.
I mean the locked bootloader of the Droid X is kind of lame. Also on the Evo, I have a 10$ discount because of the IO conference... unlimited texts too, and I bought two batteries for it with a charger(for 10$ lol, and they actually last a long time 1500ma, I put the 2 extras in my wallet)
Also I think I can upgrade my phone right away already if I read things right, so if Sprint gets an awesome phone I can upgrade to that whenever.
Verizon is more expensive, but I like how they let me do a 1 year contract. The Droid X is also nicer, I mean it has a better camera, and the mic quality when taking videos isn't piss, hopefully someone fixes that. It also has a real graphics card.
So yeah, it's hard to decide. A better phone, vs saving me some money. Though I plan to attend the IO conference once again. I'm still porting my distrubuted prime client onto Android, hopefully it will be high performance. So it's not like I just go there for a phone ^^. Hell I didn't even know about the phones till they said "Where do you want the Droid delivered" I lol'd. Though my time is limited, summer classes at UC Berkeley are tough : /
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
some of the source for the OpenGL ES GPU core was announced as being released today
Qualcomm releases open-source 3D Snapdragon driver
http://www.androidcentral.com/qualcomm-releases-open-source-3d-snapdragon-driver
havent looked at it yet, but im sure in the very least this should at least help shed some more light on overclocking the GPU and add another piece to the puzzle!
git location -
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
topdnbass said:
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
Click to expand...
Click to collapse
There isn't really a fps cap with the novatek kernel hack. It made the display much smoother for me and I am using it on EvolutionX. So beast.
Good news about the drivers, maybe we can actually see some overclocking now.
I want this to happen!
Nova runs pretty well on the Evo. Gameloft updated it recently.
I would just like for iphone ports to run well.
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
patelkedar91 said:
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
Click to expand...
Click to collapse
The Pixi doesn't have the same GPU, it has one of the low/mid-range MSM7227 (I think thats the model?) chips. It's similar as it's one of Qualcomms latest gen chips, but it is NOT a Snapdragon so it's different.
Also, the Snapdragon GPU's on HTC devices are clocked as follows:
GRP_CLK: The actual graphics clock, 256mhz
IMEM_CLK: The gpu memory clock, 256mhz
EBI1_CLK: As best I can tell, the bus that the GPU is on is EBI1, this is the clock for it, 128mhz
If you want more info, look here: http://forum.xda-developers.com/showthread.php?t=710850 since that thread is a lot more active, but please don't clutter it, there's actual devving going on there
Thanks for the info. I just wonder how they're going to get 3d games to work on the Pixi then... weird.
It was announced that the Pixi would get 3d gaming with the 1.4.5 update.
Much better (Y)
http://forum.xda-developers.com/and...ck-overclocking-tuning-snapdragon-s1-t2883708
see post 3...mind changed!!
guys please......which one shall i choose??
ok after a bit of work by myself....i found out that i have to increase my budget
..now i am choosing between
1>htc hd2 leo (huge screen! 1 ghz...)
2>mytouch3g slide(loved android 2.1 and keyboard)
i know my priority is android but since both the phones are priced around 360$(ebay)and the hd2 has a gorgeous screen & snapdragon i made it my option as well.also i came to know that there is a lot of work being done to port android to hd2.so should i go with hd2 or a mytouch slide .
also how do 3d accelerators in mytouch slide and hd2 compare to each other??do they even have them?? which one should i go for.
Good options!!
hard decision...
I love keyboard devices but donĀ“t like Android
On the other hand Leo is a great powerful device but no keyboard...
I think I would choose Leo
Hi,
I have the HTC HD2 and tried android clix, the newest one.
Had it for 2 days & it went back. The slid keyboard is hard to see.
TMO is coming out with a samsung galaxy android with 1ghz processor & big screen. Just check it out!
bliss23
thanks guys.....
i am also intended to surf a lot of internet in my phone.and ive never owned any phone with a keyboard.so is it helpful while surfing net??
also i came to know that both snapdragon 1 ghz processor and msm 7227 600 mhz processors have the same graphics controller. so in 3d profermance it should be the same for both mytouch slide and htc leo right?
and i think samsung galaxy s will not fit to my budget as my budget is only upto 400$ max
sorry for being so conservative as i have to get the phone internationally shipped to me and after that i cant return it back.
help appreciated
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
Hello I have a dual core 1.2 ghz phone and I love the customization u can do on an android, most of all the live wallpapers but sometimes when I swype the homescreen, the live wallpaper gets laggy as well as the transition effect, I just want to know if a quad core like the htc one x+ will fix the problem, I have an upgrade available and I could get this phone but I think it would be really expensive, would a quad core fix the laggines of transition effects and live wallpapers runnung on the background? What are the quad core pros?
noemisael said:
Hello I have a dual core 1.2 ghz phone and I love the customization u can do on an android, most of all the live wallpapers but sometimes when I swype the homescreen, the live wallpaper gets laggy as well as the transition effect, I just want to know if a quad core like the htc one x+ will fix the problem, I have an upgrade available and I could get this phone but I think it would be really expensive, would a quad core fix the laggines of transition effects and live wallpapers runnung on the background? What are the quad core pros?
Click to expand...
Click to collapse
Does this happen with all live wallpapers? If not then it could just be that that certain one is not well optimized, etc. Getting the new device may not have the issue, but is it worth it? Any device with the CPU power of yours should be able to handle a live wallpaper.
N.B. - The amount of cores is not the solution. Understand that core #'s are not the only things to look at when it comes to CPU's. The architecture is more important.
Ok man thanks but what do u mean with architecture? See I'm on tmobile and I'm a huge fan of htc sense even though is to heavy but I love the look, what do u think, should I change to att for the one x plus , or stay with tmobile and get the one s ?
noemisael said:
Ok man thanks but what do u mean with architecture? See I'm on tmobile and I'm a huge fan of htc sense even though is to heavy but I love the look, what do u think, should I change to att for the one x plus , or stay with tmobile and get the one s ?
Click to expand...
Click to collapse
An A15 dual core processor (e.g. In the Nexus 10) is more powerful than an A9 quad core processor (e.g. In the Nexus 4). This is caused by the architecture. See this versus this . If you have the money and the will to switch carriers, then an upgrade won't hurt. Otherwise, you could stay. Its ur choice .