Related
After having tried out a few ROMs (none recently) I am somewhat disappointed with my Diamond's performance. I am tired of waiting for my menu pages to finally appear after selecting them, I don't feel the urge to keep on trying out new ROMs until one is maybe 10% faster than the original.
Is there any ROM/UI solution that is really fast and immediately makes my phone display what it is supposed to? What about other TF versions/substitutions?
Besides speed, my only requirements are absence of annoying bugs and a slider/hw-buttons-only option to accept/reject calls.
Could you guys please give me a recommendation? What was the fastest solution you encountered? Thanks in advance.
Mmmm....
That all depends on what you call fast. The device will never perform like current devices. The only speed increase I've noticed after trying many, many ROM's is with TF3D2. This is way quicker than the original TF3D shipped with the Diamond, but as for the general day to day operation, none of the ROM's in my opinion, are any quicker than any other.
Sure, chef's comment on lightening this, and speedy that, but at the end of the day, we're stuck with what that crap OMAP processor can handle. Bring on the Snapdragon powered devices!
I remember reading something about the CPU taking all the load for graphics processing. Is there a dedicated GPU and wouldn't appropriate drivers for its usage speed things up? Please correct me if I'm wrong.
the cpu is an MSM7201A which got an ATI Imageon gpu integrated into it
Ooops!
Rudegar said:
the cpu is an MSM7201A which got an ATI Imageon gpu integrated into it
Click to expand...
Click to collapse
Sorry... my apologies! I was thinking of the original Touch! You're quite right, the Diamond has a QUALCOMM processor
Graphics...
Affenpeter said:
I remember reading something about the CPU taking all the load for graphics processing. Is there a dedicated GPU and wouldn't appropriate drivers for its usage speed things up? Please correct me if I'm wrong.
Click to expand...
Click to collapse
I believe that 64MB of the onboard 192MB are dedicated to graphics processing. Drivers may come in to it, but whether updated drivers would make a huge speed difference is debateable!
Hi guys..
I sad Google developed 2.2 to improve snapdragon cpu and becuase of that the benchmarks shows 3X faster cpu on nexus,
will work 2.2 on galaxy like nexus ? or not for SGS cpu!
at all what you think about power of CPU/GPU in SGS on 2.2 ?
Is nexus cpu better than galaxy on Android 2.2 ?
The Galaxy's CPU/GPU is the best on the market right now and with 2.2 it should fix a lot of software problems with the SGS.
Actually can't wait for 2.2, and it's released around about my birthday!
When is your birthday
22nd September mate. You can buy me a Galaxy S as a spare if you want
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
matty___ said:
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
Click to expand...
Click to collapse
If it has rfs file format and TouchWiz, consider it ****ed up.
kgk888 said:
If it has rfs file format and TouchWiz, consider it ****ed up.
Click to expand...
Click to collapse
If froyo on the SGS sucks, then the chefs in here will cut it open and make it run properly and it won't matter what the FW was like when samsung sent it out. Also, TouchWiz is fine, even if it does have a dumb name.
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
shep211 said:
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
From what I've seen and read, the 2.2 builds for the Galaxy S do NOT have a JIT compiler enabled which explains the lower scores. The N1 got the huge CPU boost from having JIT enabled. That doesn't explain the Droid X's scores, but then again I haven't read enough about 2.2 running on the DX to see if it has JIT installed.
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Vogie said:
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Click to expand...
Click to collapse
I would wait at this time before purchasing an SGS if that's your concern.
Out of the box, the current phone/software is laggy and disappointing. If you're willing to hack it with some of the various fixes found here (I prefer samset with mimocan kernel), then you won't be unhappy with the phone, but there's no guarantee that Samsung will get FroYo right, and that if they do get it wrong that the devs here will be able to bring you a hot, non-laggy, super FroYo ROM before there's better, or at least comparable hardware done right by the manufacturer available.
That's no reflection on the devs here at all, I'm just thinking that Samsung won't release the firmware until the end of September, the devs will need a couple of weeks to make magic at least, and so now we're well into October. By October, the SGS will be a six month old phone. Six months is a very long time in the Android hardware world, and we'll likely see a landslide of new phones with faster CPU, maybe even dual-cores in the fall for the holiday season. The only thing the SGS will have over other phones at that point is the Super AMOLED screen by Samsung, since they're holding it all to themselves. I wouldn't be surprised if Moto or HTC try to kang the iPhone display tech for newer models if they can't get Super AMOLED for themselves.
In the android world it is nearly impossible to but a device that won't be out of date within at most a year and sometimes within 6 months.
Having said that, I don't see anything that will topple the sgs quite that soon. Although there is talk of dual core snap dragons, there has been nothing announced yet, and indeed the two new Desire handsets are still on the same chip.
I wouldn't expect to see anything that will have more raw power than the sgs until at least mid 2011. If there was anything closer than that it'd already be getting hyped.
If you keep looking at what is just over the horizon then you won't end up ever getting one, because there always seems to be something new out in a few months time. The sgs isn't prefect, but it beats the hell it of most anything that you'll be able to buy this year.
My humble opinion of course, but I think that if you want top end hardware, the sgs will serve you very well.
Sent from my GT-I9000 using XDA App
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
shep211 said:
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
The hummingbird core is widely recognized to be faster than the snapdragon core. Benchmarks do not tell you everything. Reference:
You might think that the Hummingbird doesn’t stand a chance against Qualcomm’s custom-built monster, but Samsung isn’t prepared to throw in the towel. In response to Snapdragon, they hired Intrinsity, a semiconductor company specializing in tweaking processor logic design, to customize the Cortex-A8 in the Hummingbird to perform certain binary functions using significantly less instructions than normal. Samsung estimates that 20% of the Hummingbird’s functions are affected, and of those, on average 25-50% less instructions are needed to complete each task. Overall, the processor can perform tasks 5-10% more quickly while handling the same 2 instructions per clock cycle as an unmodified ARM Cortex-A8 processor, and Samsung states it outperforms all other processors on the market (a statement seemingly aimed at Qualcomm).
Click to expand...
Click to collapse
Here is a GPU comparison for some of the leading smartphones:
Motorola Droid: TI OMAP3430 with PowerVR SGX530 = 7-14 million(?) triangles/sec
Nexus One: Qualcomm QSD8x50 with Adreno 200 = 22 million triangles/sec
iPhone 3G S: 600 MHz Cortex-A8 with PowerVR SGX535 = 28 7 million triangles/sec
Samsung Galaxy S: S5PC110 with PowerVR SGX540 = 90 million triangles/sec
Click to expand...
Click to collapse
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
ickyboo said:
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You can't really say froyo is over hyped, I mean its free, and beyond that its an incremental upgrade.
I don't see why anyone would be staying on eclair once official froyo drops, and you can't deny that it will bring a performance boost.
Now I doubt it will bring quite as much of a boost as it gave to the N1 until we get a few months of development to really get it running sweetly, but all the same its still not over hyped if I ask me.
With optimized ROMs and whatever fixes we need (cuz samsung WILL break something) I figure the sgs will shred the N1's new scores. I recon we'll see around 3k in quadrant.
Considering how far ahead of almost everything a lag fixed non-stock-rom sgs is now, we'll see something really special once froyo starts rocking our crotches.
Sent from my GT-I9000 using XDA App
The.Opethian said:
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
Click to expand...
Click to collapse
Why powerfull phone? ok i'll tell u:
Because I don't like to buy an expensive phone (like SGS) that power is lesser than a chipper phone (like N1) !
Because I'd rather a phone without stalling (lagging) to play games and running big applications. I will very gray if i'll se lagging/stalling...
Because I need a phone with a good support (it's enough, don't need mazing support). a phone with a clear (alive or nice) Future
JIT for Hummingbird should be promising.
High Mem
anyone got any idea on the high mem issue?... when i was browsing the Gmarket.com, i realize 305 total available memory is not enough for me... and the web page just closed....
why have they put an old model processor in there? why not the MSM8255?
i am holding out for a little bit, i am due an upgrade now, but dont want to rush into buying this phone if something better is coming.
Plus want to see what modding can be done to the software / themes, 3rd party apps etc
t3rm3y said:
why have they put an old model processor in there? why not the MSM8255?
i am holding out for a little bit, i am due an upgrade now, but dont want to rush into buying this phone if something better is coming.
Plus want to see what modding can be done to the software / themes, 3rd party apps etc
Click to expand...
Click to collapse
because Microsoft only support the "old" snapdragon .
why apple customers don't ask them the same question , they use the same GPU as what is in 3gs a year ago ,
a second thing wp7 is developed on the snapdragon which is more than enough for now with it's improved drivers and direct x 9 support , it will perform even 2x better than a DHD with 8255 processor
t3rm3y said:
but dont want to rush into buying this phone if something better is coming.
QUOTE]
Sorry I'm the one that had to break the news, but there is always something better coming...
Click to expand...
Click to collapse
hoss_n2 said:
why apple customers don't ask them the same question , they use the same GPU as what is in 3gs a year ago ,
a second thing wp7 is developed on the snapdragon which is more than enough for now with it's improved drivers and direct x 9 support , it will perform even 2x better than a DHD with 8255 processor
Click to expand...
Click to collapse
+1 and 10char
t3rm3y said:
why have they put an old model processor in there? why not the MSM8255?
i am holding out for a little bit, i am due an upgrade now, but dont want to rush into buying this phone if something better is coming.
Plus want to see what modding can be done to the software / themes, 3rd party apps etc
Click to expand...
Click to collapse
I have an HD7, it is lag free and very responsive, I think the processor will be up to the task as long as the coding is optimal.
Because having the next most powerful processor isn't important. It doesn't matter what kinda specs a device is running s long as the device runs well. Apple has proved that.
And from what I have seen, MP7 runs beautifully.
Lorddeff07 said:
Because having the next most powerful processor isn't important. It doesn't matter what kinda specs a device is running s long as the device runs well. Apple has proved that.
And from what I have seen, MP7 runs beautifully.
Click to expand...
Click to collapse
True that.
Old processor?
Maybe this is a bad news to you, but it's good to me cause of my hd2.
I probably would have been crying about the same thing, if technology was growing by leaps and bounds. But its not right now, technology is kinda stagnate as of lately. Yes, the HD7 has the same processor as its predecessor the HD2, but its not a bad thing. especially now that the new rom has came out for the HD2, it feels faster than ever (you can go on the HD2 and Leo boards to attest for yourself). Another thing to remember, is that the new Windows Phone 7, is not an OS that needs a 2Ghz processor to run buttery smooth. I think that we are used to the PC ideology that the next thing should have a higher number than the last, in order to be considered and respectable upgrade. But even those Intel and AMD processors, reached their, threshold for raw computing power (for now) and the companies are now refining their codes, and drivers, in order to utilize and maximize peak performance out of what they already have. (That's why 4Ghz desktop processors aren't mainstream yet)
Another thing is the WP7 is standardized with base set requirements for internal specs. I truly doubt that you'll find a noticeable difference between all the launch devices behavior with the OS, because of their processors. The mail screen might open up a little quicker on one device, but again, that could be a driver code magic for the display adapter in a particular phone, so the one that "wins" in our mind, should have been the "newer, speedier" processor but because of the refinement and more developed drivers, the one that displayed the inbox quicker was the "older" processor. (I hope you guys got that...lol)
So what I'm trying to say at the end of the day, is it really doesn't matter about the processor spec, because whats inside the HD7 is more than plenty to run the OS and its apps very very nicely.
forgiveness if this is wrong info, but i believe many of the first gen WP7 devices are using the same snapdragon CPU and GPU combo as the nexus one, the adreno 2.5 i believe. yet those devices are smooth as butter on all parts of the OS, including any web page you throw at the browser.
is there a reason why the same is not achieved on the nexus one and android phones? i assume its down to drivers, but seems silly that android wouldnt be similar...anyone have insight with this?
Minus the x,y axis touch screen limitation my n1 is pretty smooth all around, what sort of differences do you see ?
disgustip8ted said:
Minus the x,y axis touch screen limitation my n1 is pretty smooth all around, what sort of differences do you see ?
Click to expand...
Click to collapse
Don't get me wrong, my nexus one is smooth as butter in 95% of all areas. Home screen scrolling and transitions easily must be hitting 50fps. But certain websites like engadget or this forum can skip a tad. Throw those same sites on new windows phone and It's smooth as butter.
I just wonder how this is possible with the same chip set, especially considering how our adreno is supposedly not the best.
do you have the "enable plug-ins" setting in the browser set to "on demand"?
i have mine like this and xda loads pretty quick, ondemand just lets you tap on a flash item when you want it to be rendered.
Yes on demand has been set for many months. I'm not talking about load speed, but scrolling smoothness once loaded. There are minor examples else where in the OS. But in general I'm wondering about drivers between the 2 platforms. You'd prob have to use a phone to see.
ill check out my friend's wp7 tomorrow at work. i cant get my phone to be choppy on this thread or the main thread or the gigglebread thread zoomed in or fully zoomed out :\
Probably cuz the browser on WP7 is based off the best internet browser EVER. Duh!
</sarcasm>
But seriously, it's a different OS, and the browser is different than ours. My wife had an HTC Surround for about a month (returned it cuz of lack of apps right now), and I will say, it was a pretty nice phone. Maybe after a few updates it'll be something to look into again, but right now, it's at the beginning of it's life, so there's a lot missing in my opinion.
It's all about code optimization, proper drivers, hardware accelerated graphics...
since android must run on many devices with many different cpus they can't optimize everything for the snapdragon, as they've done with WP7.
elmerendeiro said:
It's all about code optimization, proper drivers, hardware accelerated graphics...
since android must run on many devices with many different cpus they can't optimize everything for the snapdragon, as they've done with WP7.
Click to expand...
Click to collapse
that's kinda the direction i was going. i wonder if this is something that qualcomm perhaps helps microsoft with providing optimized drivers, or they were paid to do so. it just shows how the snapdragon and adreno are pretty powerful but get a lot of negative talk around the community for it's graphics capability.
seeing as it was goog;e's first and initial phone, its too bad they did not attempt the similar performance optimizations. i mean each individual phone needs device specific drivers anyway, so its too bad they didnt take it to that next level.
Someone on Slashdot linked to a very interesting article relating to this problem.
Google "The Care and Feeding of the Android GPU"
(Note: This has probably been posted on the forums before, but it seemed worth adding to the current conversation)
EDIT: Wow. Terrible grammar. Wish I could blame Swype, but I'm pretty sure I'm just a moron lol.
inconceeeivable said:
Someone on Slashdot linked to a very interested article relating to this problem.
Google "The Care and Feeding of the Android GPU"
(Note: This has probably been posted on the forums before, but it seemed worth adding to the current conversation)
Click to expand...
Click to collapse
actually this totally answers my question. thanks. reading that slashdot article, there are some great comments at the bottom, one with a link to anandtech article about WP7 and GPU's etc. also a former google employee commented on the topic.
so basically yes MS very tightly controls things and wanted it that way. android has to code for common devices across many manufacturers etc.
one interesting thing the anandtech article says that WP7 is capped at 30 FPS by microsoft due to battery concerns. some dev's complained. remember the EVO had that cap, and it sucks because of it. but playing with WP7 devices i didnt notice it a bit. strange.
and the real answer as others have said in the past is lack of UI hardward acceleration. interesting topci on google bug tracker explains it all. but 3.0 seems to fix it!
http://code.google.com/p/android/issues/detail?id=6914
Simple, there is no hardware acceleration in the UI. Only apps that are programmed to use the GPU will use it.
Android needs a virtual machine, W7 doesn't, it runs native on the hardware. Full native support.
holy crap, i just watched a video of android which DOES have full graphics hardware acceleration thru the enture UI, and nearly crapped my pants. talk about iphone-like smoothness...
http://www.youtube.com/watch?v=JpH3oX9RhIE
Hi everyone!
I want to buy the tablet Samsung Galaxy Tab S 10.5 for its amazing screen, but the 64bits world is already here.
I checked that the only versions with a 64 bits cpu are just SM-T805S, SM-T805K, and SM-T805L with the Exynos 5433 in Korea.
Does anyone know where to buy it without going in person to Korea?
Or does anyone know if there is another version(s) with 64bits cpu and where to buy it?
Thanks!
Why do you want a 64 bit CPU?
codified said:
Why do you want a 64 bit CPU?
Click to expand...
Click to collapse
I'll bet he doesn't even know. Saying 64 "bits" tells me he isn't very knowledgeable with technology. He just heard it from somewhere.
bloodrain954 said:
I'll bet he doesn't even know. Saying 64 "bits" tells me he isn't very knowledgeable with technology. He just heard it from somewhere.
Click to expand...
Click to collapse
Or you can just be nice and explain to him why the 64 bit version won't garner him any real world benefits right now...:highfive:
wow!! how nice people are around here!!!
even if I dont have very high knowledge in technologies, you just have to write on google "64 bits android" to really know that 64 bits in android is not making any high difference now. So it doesnt really matter and whoever can know that. But at the same time, you can also see that there are some improvements and other "stuff" (typical word that some of my kind use) that will be useful soon while the rest of the techolopy (or technoloki... or how was the word? oh yes! = t-e-c-h-n-o-l-o-g-y ) is progressing.
I am not very advanced and thats why I am writing here, sorry that I didnt passed the test to write here.
Anyway, my only stupid reason why I want a 64 bits CPU is because of the money. Coz I dont have a lot. And I am the kind of person that tries to buy something that will last many years coz I cant afford to change deviced regularly. I bought my last laptop 10 years ago, it worked 7 years... and since then, there is no laptop. But my personal life is not the matter, and I am not asking about laptops or why I want a tablet now.
But I need a tablet that will last untill burns, and the "64bits world" is starting developing and in two years or so... I dont want to have a tablet that I cant use with something because 32 bits doesnt supported... but this is just an opinion anyway...
All 'new' tablets will last for a long time. 64 bit won't make a difference. If you feel it does, get the nexus 9. But even Google knows 32bit devices won't be going anywhere for a LONG time. Hence the reason the Nexus 6 is "only" using a 32bit processor. I'll be busy currently enjoying my brand new 32bit tablet
Just order online nuff said!
Sorry, didn't mean to make you feel stupid. I ask the question because a lot of people go blindly seeking the latest marketing term without realising what it means
64-bit processors are the new craze since Apple released one and had all the publicity about it
But it doesn't add much at all, and it won't future-proof your phone like you might think it would
This is a good article to read:
http://www.androidauthority.com/note-4-64-bit-32-bit-android-l-536280/
Anyway, the Exynos 5433 processor that you are talking about is technically 64 bit architecture but will only run in 32 bit mode, so you aren't really getting any of the advantages of 64 bit. You will have to wait for the Exynos 7420 for true 64-bit performance.
codified said:
Sorry, didn't mean to make you feel stupid. I ask the question because a lot of people go blindly seeking the latest marketing term without realising what it means
64-bit processors are the new craze since Apple released one and had all the publicity about it
But it doesn't add much at all, and it won't future-proof your phone like you might think it would
This is a good article to read:
http://www.androidauthority.com/note-4-64-bit-32-bit-android-l-536280/
Anyway, the Exynos 5433 processor that you are talking about is technically 64 bit architecture but will only run in 32 bit mode, so you aren't really getting any of the advantages of 64 bit. You will have to wait for the Exynos 7420 for true 64-bit performance.
Click to expand...
Click to collapse
You are right, 64-Bit processors are only really beneficial if you have the added memory to make good use of them, Apple's was only a gimmick when you consider they still only come with 1gb of RAM whereas most other devices not coming from Apple have 2gb or more.
lorinkundert said:
You are right, 64-Bit processors are only really beneficial if you have the added memory to make good use of them, Apple's was only a gimmick when you consider they still only come with 1gb of RAM whereas most other devices not coming from Apple have 2gb or more.
Click to expand...
Click to collapse
Thats not true. A 64-Bit processor have more registers and handle processing generally faster than the 32-Bit, even if you don't run any 64-Bit code on it.
caravana said:
Thats not true. A 64-Bit processor have more registers and handle processing generally faster than the 32-Bit, even if you don't run any 64-Bit code on it.
Click to expand...
Click to collapse
Not without more RAM it doesn't, I design mobile devices so I have a ton of experience.
lorinkundert said:
Not without more RAM it doesn't, I design mobile devices so I have a ton of experience.
Click to expand...
Click to collapse
RAM has nothing to do with the processors architecture, and with all due respect, your experience is not an argument. About the ARM 64-Bit architecture I can quote the AnandTech guys here:
Architecturally, the Cortex A57 is much like a tweaked Cortex A15 with 64-bit support. The CPU is still a 3-wide/3-issue machine with a 15+ stage pipeline. ARM has increased the width of NEON execution units in the Cortex A57 (128-bits wide now?) as well as enabled support for IEEE-754 DP FP. There have been some other minor pipeline enhancements as well. The end result is up to a 20 - 30% increase in performance over the Cortex A15 while running 32-bit code. Running 64-bit code you'll see an additional performance advantage as the 64-bit register file is far simplified compared to the 32-bit RF.
Click to expand...
Click to collapse
And here AnandTech does detailed arm 32bit vs 64bit performance comparison:
The conclusion? There are definitely reasons outside of needing more memory to go 64-bit.
Click to expand...
Click to collapse
So yes, the ARM 64-bit architecture is generally faster than the 32-bit counterpart, because of enhancements that does not depend on the amount of RAM available.
lorinkundert said:
Not without more RAM it doesn't, I design mobile devices so I have a ton of experience.
Click to expand...
Click to collapse
I have a feeling you don't.
to take full advantage of a 64-bit processor you'd need an operating system that is also 64-bit as well, more than 4GB of ram (since 32-bit has a limitation of 4GB ram), and apps that are 64-bit.
For the pace of technology I'd say applications in the server-world (SQL and stuff) have fully taken advantage of 64-bit architecture for 10ish years, desktops maybe in the past 6 or 7 years.
It really depends on what type of programs you're using because certain things use the CPU, other's use the GPU. This being for games and such.
Apps like MX Player would take advantage of the CPU. ART in Android Lollipop will do us well. Bottom line- way too many factors but I don't think anything coming out on Android will make good use of a 64-bit architecture for a few more years. I mean, anything that would need 64-bits is really a battle with "is this a battery-friendly app or some intense app that should really be on a desktop?" or something. 64-bit just isn't needed right now. Personally, I like when developers focus on making programs that work best in a low power environment like a mobile device architecture.
You're buying an octacore tablet which is the most high-end device right now. I'd say Android and the hardware won't get much more fancier fancier for the next year or 2 and, TBH, this tablet won't start feeling sluggish for maybe 4 or 5 years as far as technology typically progresses.
Here's a video by Linus Tech tips detailing 64 bit vs 32 bit in a more layman term:
https://www.youtube.com/watch?v=IknbgnJLSRY
Thanks for your messages.
After reading all and watching videos... I see that 64bit is not a big difference now, but it won't be for a very long time either... so it will be a little bit like the current situation in deskpots: even if 64bits is generally seen in everything, everything (almost) is still compatible with 32 bits and companies still give support to 32 bits...
and, on top of everything, if the "highest" option with this tablet is the exynos 5433 64 bits but only runs in 32bits mode... it makes no sense.
so, according to this, my question would be: how this tablet is going to handle Android Lollipop with the exynos 5420? I mean, how does the exynos 5420 (32 bits) handle android lollipop (64bits)?
There is a 64 bit option on my kernel configuration file for Note Edge 5433 and if enabled + unlocked 64 bit bootloader + firmware = winner. The 5433 Tab S is the same and has been deliberately crippled by Samsung to keep it on par with the crappy Snapdragon 805 which won't be ready for 64 bit until mid-next year. Even then, SD performance and potential doesn't even come close to the Exynos.