Related
Hi everyone,
I was just wondering what are the fastest & most responsive VGA-screen PPC Phones out there (or coming by end 2009)? I quantify performance in terms of 2D graphics, and I've been using SPB Benchmark Graphics benchmark. Of course, one can always argue there's more than 2D graphics in terms of speed, but slow phones really pissed me off. I used to had a HTC Universal and that was a steaming pile of junk. Switched to HTC Hermes 2-3yrs back... and it's been barely tolerable.
Right now, I've only found 2 "fast" VGA PPC Phones - ASUS P565 and Samsung Omnia II. However ASUS P565 is a questionable VGA phone since it's screen is a puny 2.8" size (might as well get a ASUS P552W). Both have a graphics benchmark of around ~2500, which is quite sad since that's equivalent to the Eten M600 speed (ok it runs as a QVGA). Compare this to Samsung Omnia I (~5000) or the ASUS P552W (~11,000) both of which uses the slower Marvel 624MHz CPU, Monahans and Tavor generation respectively.
I read that Toshiba TG01 Snapdragon is coming soon, but are there any concrete benchmarks done on it?
So, does anyone know if there is any fast & responsive VGA PPC Phones out there? Or do we have to wait for Snapdragon, Tegra or Marvell's 1GHz CPU? Can we expect such CPUs to make VGA screened phones fast enough? Or should I just get the ASUS P552W which means giving up my QWERTY keyboard , and wait for another 2-3years?
Hi
I can think on Tosh tg01 that is already on sale as the fastest to this date (I believe)
On december some snapdragon tosh models will be launched! perhaps HTC also...
Other ones not so fast but also good options are:
Touch pro 2
Hero
Acer M900?
YOu cannot treat a processors MHz as the be-all-end-all. Its an indicator and nothing more. You cannot compare processor speeds across diferent manufacturers either.
And no matter how fast the processor, if the drivers/design around it is sh*t, the phone will suffer greatly. A good example of this, Acer Shell to access contacts can be a little slow, SPB Shell however, is instant.
You can only compare by running the same app performing the same task on each phone. Benchmarks try to do this but can become far too specific at times. Again, they are a (good) indicator but not the be-all-end-all.
On a side note, I have an m900 and if you turn off Acer Shell (coz it sucks!) it is VERY fast.
When you want speed, why do you need speed exactly? Are you talking about accessing contacts etc? Are you talking about screen orientation or maybe playing games?
Your best bet is try and get hold of devices, install the required game/software and THEN see how responsive it is.
Monty Burns said:
YOu cannot treat a processors MHz as the be-all-end-all. Its an indicator and nothing more. You cannot compare processor speeds across diferent manufacturers either.
And no matter how fast the processor, if the drivers/design around it is sh*t, the phone will suffer greatly. A good example of this, Acer Shell to access contacts can be a little slow, SPB Shell however, is instant.
You can only compare by running the same app performing the same task on each phone. Benchmarks try to do this but can become far too specific at times. Again, they are a (good) indicator but not the be-all-end-all.
On a side note, I have an m900 and if you turn off Acer Shell (coz it sucks!) it is VERY fast.
When you want speed, why do you need speed exactly? Are you talking about accessing contacts etc? Are you talking about screen orientation or maybe playing games?
Your best bet is try and get hold of devices, install the required game/software and THEN see how responsive it is.
Click to expand...
Click to collapse
Easier said than done, I would love to have a try out by to replicate real-life performance one has to install all the apps one normally use, so it's not practical unless you have a dozen friends with different PPC Phones. While benchmarks aren't perfect, I don't see anything better to replace it. Sure, there is software optimizations and driver stuff, but if it sucks... no matter how much you cook your ROM and optimize, it sucks.
Take for example HTC Universal. That is one slow piece of junk. No matter how much optimization you do, you're not going to beat say the current HTC Hermes that I am using in terms of responsiveness. Another example is the last 1-2 yrs of HTC <Insert Model> running Qualcomm CPUs. So many users have reported the unbearably slow speed, and it doesn't help that many of them come with VGA resolution screens. Almost all evidence point to date that VGA phones are slow and crappy... and I was wondering if technology has advanced the point whereby this can be rectified.
Speed? It's the most importing thing when dealing with PPC Phones. For many years now, I the name Pocket PC is a real misnomer, as previous generation and maybe even current generation of phones acts in no way like a real personal computer.
What is acceptable? Fast 2D graphics. Instant response when I click on something, as I was using a laptop. No lag. No lag when rotating the screen. Faster loading of webpages instead of waiting for ages... and then it crashes. And btw I use Phone Weaver, Pocket Plus and SPB Diary on my Today screen, which makes it more taxing on the 2D system. Sure the HTC Universal with a fresh install can rotate screen in 1-2 seconds when optimized, but load in all my Today plugins it takes like 10-20 seconds!
Next comes fast 3D graphics and the ability to play movies. Right now my HTC Hermes can't play normal sized video files, i.e. 640x480, XVID/DIVX. Of course you can always recode with a lower res, but what's the point? It's all extra work.
Ronnie,
Have you thought about doing the 128MB memory upgrade, and overclocking the CPU on the Universal? May help things a bit.
Some other devices that may be faster:
Xperia X1
Acer F1
02 XDA Flame
Asus P835
Here is a site that test floating point and OGL performance in smartphones. Donot know how legit it is however.
http://www.glbenchmark.com/latest_results.jsp?benchmark=glpro
Most certainly don't look to HTC.
e.g. Kaiser - even if the CPU/GPU supports faster performance, they don't deem that necessary and don't include the required drivers.
The video 'hack' to speed up 2-D performance for the Kaiser proves that there are even more inefficiencies/missing drivers for that HTC phone.
I would suggest that the new Acer Tempo range and new Samsung Omnia's are a good way to investigate. Both these brands are selling the fact that there chips have built in 3d graphics and I believe the Samsungs even come with a free 3d game - could be wrong though. Either way, you wouldnt sell the fact you have a 3d games capability if you haven't programmed proper 3d drivers - something HTC have never really done afaik.
Again, the Acers are only showing a 528mhz (something like that anyway) but don't be fooled by a mhz rating. For example, just because a snapdragon is showing a 1ghz processor doesn't means its faster than a 528mhz Samsung... if you use google you will find plenty of winmob experienced people that feel its not as fast as it should be.
edit: Im sure the Samsung Omnia II's come with a Need For Speed Variant?
Hi! Reading around the web I've found out that Android still lacks of hardware acceleration in the windows' contents (enabled for compositing) and so does, of course, the browser (in the specific)! This is why we have not an as smooth as iPhone scrolling/zooming! Here an interesting article:
http://connect-utb.com/index.php?op...z-cpu-is-enough&catid=36:technology&Itemid=67
And here is a question made to a developer by an AndroidCommunity user:
http://androidcommunity.com/forums/f41/the-hardware-acceleration-question-8963/index2.html
So my question is: Will be possible to have hw acceleration (also on cooked roms, doesn't matter) in the near future? I still can't understand why, for example, my Hero cannot handle games like NOVA altough has a dedicated GPU and its CPU is quite superior to the iPhone 3G's one! While on this one the game runs smoothly! My supposition was that these games are not even developed thinking about Android...They only are miserable portings from iPhone! Please tell me that one day (maybe with 3.0) will be possible to have Flash 10.1, great 3D (or at least comparable to 3G) and COMPLETE acceleration in Android on my Hero and other MSM 7XXX devices (dream, magic ecc.) I'm really thinking of selling my Hero to buy something like a Milestone (Droid in US) or a Liquid (not sure about this one)...Thanks in advance
Surely they did this in an attempt to save battery life?
Maybe that's where OpenCL comes in?
Well I don't know how much hardware acceleration can damage battery life...I'm pretty sure this doesn't happen on other devices with iOS or WinMo where hw acc. is enabled And battery lasts normally!
About OpenCL I'm not sure it has something to do with graphics enhancements! Maybe it's used to accelerate computational stuff like physics...Or, at least, this is what I can read from here (it uses GPU to enhance NON graphical computing):
http://en.wikipedia.org/wiki/OpenCL
What I'm talking about is to enable acceleration in UI and browser (as well as has been done with 3D graphics and videos with SnapDragon and Cortex A8) like iPhone did! And I think this wouldn't decrease so much battery life! I prefer to have a functional and smooth browser more than save 1-2 hours of battery life! IMHO! Thanks to have answered my question
Just a little up! Thanks!
There is no hope for the msm72xx. Qualcomm or Htc or both of them are complete douches to us power users that want the max out of our devices. They do not provide efficient graphics drivers hence the horrible graphics performance. This is highly unlikely to change in the future and it seems to me that in order to compensate for sluggish graphic performance, they are upping the processor speed as seen by the recent slew of snapdragon 1ghz which also underperforms due to lack of proper drivers.
Gosh... This means that not even Google took care of developing proper drivers fot ITS OWN DEVICE! This is pretty bad...And means that Android could be a "poor" OS because of the laziness of some developer...I'm wondering if is convenient to buy an Acer Liquid (very low price here! And I can't afford a N1 or a Desire) or an iPhone 3G at all! Games like NOVA run GREAT on both of them...And I'd really want a smooth browser...But I'm pretty sure on one thing: My Hero needs to be replaced It made me too much disappointment...
Thanks for your answer
Yes your hero is an outdated mid range device that needs to be replaced...i would suggest a samsung galaxy S or any of its variants.
Thanks but...Who's going to give me the money to do that? XD I can't afford a Galaxy S (549€ here!) while an Acer Liquid (with the same performance of a N1 and I know what I'm saying ) is WAY more affordable (299€! Almost half of the Galaxy S price!).
For giggles, can one of you that's stock run the Electopia benchmark? There's been some interesting results and it would be cool to see how another dual-core phone with a different CPU/GPU performs. The Sensation folks are obviously not amused.
Sensation
800x480
Average FPS: 23.65
Time: 60
Number of Frames: 1419
Trianglecount: 48976
Peak Trianglecount: 68154
960x540
Average FPS: 19.90
Time: 60.01
Number of Frames: 1194
Trianglecount: 49415
Peak Trianglecount: 67076
SGS2
Average FPS: 37.58
Time: 60.01
Number of frames: 2255
Trianglecount: 48633
Peak trianglecount: 68860
DHD
Average FPS: 23.36
Time: 60.03
Number of frames: 1402
Trianglecount: 48835
Peak trianglecount: 67628
Even the Desire HD blew away my G2x on this benchmark but it could be the custom ROM... I'll switch back to AOSP and try it again.
16FPS
Can't be right, my Thunderbolt smoked my g2x
26 FPS Thunderbolt vs 16FPS G2x
Something is very wrong with those numbers if this is supposed to be measuring opengl 2.0
I have stock and with a really hard time getting it to respond to touch input and with the sound off here are the scores:
Average FPS - 15.56
Time - 60.04
Number of Frames - 934
Trianglecount - 48928
Peak Trianglecount - 68838
This was a super buggy program on the G2x. I think it is definitely not optimized for dual core or at least the Tegra 2 architecture.
Sent from my T-Mobile G2x using XDA App
There's no way the G2X would be lower than the Sensation. The test probably isn't dual-core optimized and the new CPU/GPUs are throwing it off. Thanks for trying though.
BarryH_GEG said:
There's no way the G2X would be lower than the Sensation. The test probably isn't dual-core optimized and the new CPU/GPUs are throwing it off. Thanks for trying though.
Click to expand...
Click to collapse
And there is no way the g2x could be lower than a single core adreno 205 Thunderbolt.
15.57 FPS for me running stock/not rooted. Like previously mentioned, it was very unresponsive to touch.
Badly designed benchmark programs are bad.
diablos991 said:
Badly designed benchmark programs are bad.
Click to expand...
Click to collapse
The sad part is that this isn't just a benchmark - its a game first and foremost.
And yeah I can't get past 16FPS on stock speed OR at 1.5GHz so I think there's definitely coding issues as Nenamark using Trinity on Bionic scores 72FPS. I think my Inspire (Adreno 205) got about 35?
+1
Lets all buy phones with top benchmarks!!!!!!
Better yet lets all get iPhones.....
Fu*k a benchmark
Sent from my LG-P999 using XDA Premium App
But if you really stop and think about it, if each of the different CPU/GPU's behave differently running the same software because of proprietary hardware performance tweaks we'll all be screwed in the long run. No matter how Electopia was written, one would think it would behave the same way on different CPU/GPU combinations - even if it wasn't dual-core optimized. So developers are either going to have to start testing on every CPU/GPU combo to release a single version of an app or release different apps for different CPU/GPUs. It's way too early to tell as dual-core and 2.3ish isn't that common now but it should be interesting watching software performance and development play out in the future.
BarryH_GEG said:
But if you really stop and think about it, if each of the different CPU/GPU's behave differently running the same software because of proprietary hardware performance tweaks we'll all be screwed in the long run. No matter how Electopia was written, one would think it would behave the same way on different CPU/GPU combinations - even if it wasn't dual-core optimized. So developers are either going to have to start testing on every CPU/GPU combo to release a single version of an app or release different apps for different CPU/GPUs. It's way too early to tell as dual-core and 2.3ish isn't that common now but it should be interesting watching software performance and development play out in the future.
Click to expand...
Click to collapse
Its piss-poor coding on the app developer's part - plain and simple. While there are Tegra 2-specific instructions that an app developer can use in their application, there are not any mobile OpenGL 2.0 instructions the Tegra 2 doesn't support as far as I am aware.
If you want a good challenge for the chip, download an3dbench XL from Market. I just scored 32640 and that's with a bunch of background apps.
Isn't this a windows mobile port (had it on my HD2 running WM6.5)? So, how does it provide an accurate representation of gaming on an Android device? Since it is the only bench my G2x has scored poorly on and (more importantly) real world gaming is spectacular on this thing, I'm going to say it doesn't. I wouldn't put a whole lot of stock in this one...
Yeah agreed. I just ran it on the Nexus/CM7 AOSP hybrid and it still was only 16.06 while I got almost 40,000 on an3dbenchXL which put me like 30-something out of 7000ish results.
This application was influenced by Qualcomm specifically to run poorly on Tegra 2 devices. They messed with the shaders so everything is rendered at a weird angle. If you change the code to run with a normal approach, you see the same results on Qualcomm chips but also 3-5x perf on NVIDIA chips
why would you say this benchmark was influenced? if you have the sources ..please share .. so we can all look ... and how can you say BenchXL is a good benchmark? I have run BenchXL Benchmark and seen un matching results on many forums ... it is very unreliable... not a good benchmark. At least electopia gives consistent reliable results... I would go with electopia as a GPU benchmark ..
i have a xperia play for myself - which performs superb for gaming - awesome graphics - i love the games on it - awesome device. my wife has g2x - which is equally good for gaming (thought she just uses it for texting - LOL )....
i think for gaming both xperia play and g2x are good...
I'd hardly say it's biased to any one specific manufacturer based on these benchmarks:
More so I ran it myself with the latest firmware at stock frequencies (SGS2 btw ) and got:
Average FPS: 51.44
Time: 60.02
Number of frames: 3087
Trianglecount: 48827
Peak trianglecount: 68868
Quite funny difference to any other device I might say.
It's not biased towards any manufacturer, it is biased against NVIDIA's ULP GeForce GPUs in Tegra 2 SOCs.
Changes to the code cause increases in performance on Tegra 2 devices, while results on other platforms do not change.
In general, there is never a single, all-encompassing GPU benchmark to accurately compare devices. It all depends on the code, and how it interacts with the specific hardware of the device.
images |DOT| anandtech |DOT| com /graphs/graph4177/35412.png
images |DOT| anandtech |DOT| com /graphs/graph4177/35412.png
Source: Anandtech Samsung Galaxy S2 review (I can't post links )
http://images.anandtech.com/graphs/graph4177/35412.png
That AnandTech review is badly outdated, like I said; the SGS2 gets for example 16fps there in February. I myself get 58fps today.
And I don't think it's biased against Tegra. Tegra performs pretty much there where it should be considering its age, and corresponds to it's specs.
And just to prove dismiss your point that Tegra gets a different codepath, I ran Electopia Bench again via Chainfire3D using the NVIDIA GL wrapper plugin emulating said device and I'm still getting the same amount of FPS.
If what you're saying is that it's not utilizing Tegra's full potential through proprietary Nvidia OpenGL extensions, might as well pack the bag and leave because then that logic would apply to pretty much every graphics core since it's not optimized for it. What we see here in these benchmarks is a plain simple ES 2.0 codepath which all devices should support and so we can do an oranges to oranges comparision. It's also one of the heaviest fragment-shader dependent benchmarks out there for the moment, and less geometry and texture bound, and that's why it runs so badly on pretty much every chip, since they don't get this type of workload in other benchmarks. This is also why the Mali gets such high FPS as that's where the quad GPU setup in the Exynos can shine.
AndreiLux said:
I'd hardly say it's biased to any one specific manufacturer based on these benchmarks:
More so I ran it myself with the latest firmware at stock frequencies (SGS2 btw ) and got:
Average FPS: 51.44
Time: 60.02
Number of frames: 3087
Trianglecount: 48827
Peak trianglecount: 68868
Quite funny difference to any other device I might say.
Click to expand...
Click to collapse
It's clearly MALI 400 in SGS2 is most powerful GPU right now. There is a 60fps limit on Galaxy S2, so you'll need a powerful benchmark. You can also see that in Nenamark2 too. SGS2=47fps, G2X=28fps, SGS=24fps
Are really stupid. Between the governor differences, ram differences, thermal limit tweaks and whatever other little tweaks per phone/soc, what is the difference between Samsung or x OEM modding their phone to run full throttle and the consumer putting the phone in performance governor and running it full throttle? The benchmarks between phones with similar soc's have less merit than guaging against phones with different SOC's and checking performance against different generation SOC's. I think it is best that OEM' tweak their phones to run full throttle on benchmarks as it leaves less question about what is better/best. The benchmarks aren't all that scientific anyways with all the variables anyways. It was funny at first when people were crying about it but now it's just frustrating and another stupid first world problem for all the peeps with little weiners.
Now I do have a problem with tweaks that aren't available as a preset like running a cpu or GPU above frequency that the soc isn't rated for. That itself is deceiving. But running benchmarks similar to running a performance governor I have no problem with. Some of these big review sites need to get together and come up with a standard that leaves little question if the OEM is running the benchmarks above spec. Just smdh. Simple solution.
To me Samsung just makes the phone do what the so called benchmark app is supposed to do anyway...make the phone run full throttle. There is no difference than setting your gov to performance and running the test.
@rbiter said:
Are really stupid. Between the governor differences, ram differences, thermal limit tweaks and whatever other little tweaks per phone/soc, what is the difference between Samsung or x OEM modding their phone to run full throttle and the consumer putting the phone in performance governor and running it full throttle? The benchmarks between phones with similar soc's have less merit than guaging against phones with different SOC's and checking performance against different generation SOC's. I think it is best that OEM' tweak their phones to run full throttle on benchmarks as it leaves less question about what is better/best. The benchmarks aren't all that scientific anyways with all the variables anyways. It was funny at first when people were crying about it but now it's just frustrating and another stupid first world problem for all the peeps with little weiners.
Now I do have a problem with tweaks that aren't available as a preset like running a cpu or GPU above frequency that the soc isn't rated for. That itself is deceiving. But running benchmarks similar to running a performance governor I have no problem with. Some of these big review sites need to get together and come up with a standard that leaves little question if the OEM is running the benchmarks above spec. Just smdh. Simple solution.
Click to expand...
Click to collapse
Totally agree, if they over clocked it that would be one thing, but this is no different from intel or amd binning thier chips for reviewers to make sure the fastest chips go
Thread closed as its essentially a duplicate of this >>> http://forum.xda-developers.com/showthread.php?t=2465518
This question is more for Developers\Advanced Users\Geeks, than the normal user\average Joe (who uses the phone 90% for Calls \SMS , Whatsapp and just a few games like Candy Crush\Fruit Ninja and a little Web surfing):
Which Phone would you prefer? Phone A or Phone B ?
I personally can't decide which I should use..
I will not (yet) post Geekbench\Antutu because:
1) The App says the name of the phone, so it wouldn't be a blind poll anymore
2) I don't really trust these more popular tests anymore because money CAN buy results or at least app optimization so less popular (but well made) apps are more likely to tell the truth
Please Read the whole text above ^ and carefully look at the Screenshots I attached before posting.. Saying that I should just choose the one with the higher numbers\benchmarks would prove to me that you do not (ever?) read the Original Post and just like troll every thread you find, OR if you did read, it would make me doubt that your IQ is enough for the xda forum.
Obviously one would choose higher benchmarks.
Thread cleaned up.
Please be civil and respect each other.
There is absolutely no need for foul language.
Let's keep it on topic please.
Thanks!
Regards
Vatsal,
Forum Moderator.
Hey.
Given your use, I would say that Phone A is the best choice. Better graphics, better Ram, onlty has a worse read and write speed (although it's half the speed, which is bad).
Still, for the type of use you describe, can't really see why you would pick phone B since it does not take a lot of read speed to open those apps decently.
Any reason for you not saying which phones they are? You clearly know that tests are not all the story, and saying wich phones these are you are letting people with that phone tell you about their experience
This does look like a Pixel vs Galaxy S7 though.
badjoras said:
Hey.
Given your use, I would say that Phone A is the best choice. Better graphics, better Ram, onlty has a worse read and write speed (although it's half the speed, which is bad).
Still, for the type of use you describe, can't really see why you would pick phone B since it does not take a lot of read speed to open those apps decently.
Any reason for you not saying which phones they are? You clearly know that tests are not all the story, and saying wich phones these are you are letting people with that phone tell you about their experience
This does look like a Pixel vs Galaxy S7 though.
Click to expand...
Click to collapse
thanks for your reply... you understood me wrongly...I said ''This question is for Developers\Advanced Users\Geeks, {not for } the normal user\average Joe (because [average Joe- meaning most people] uses their phone 90% for Calls \SMS , Whatsapp and just a few games like Candy Crush\Fruit Ninja and a little Web surfing)'' and they don't know anything about these geeky things.. so the cannot help me with the question. ..but that doesn't matter..it's not the point here. I just wanted to see what other people think is more important: RAM speed or NAND speed.
NOW THE DISCLOSURE:
Phone A is the Lenovo ZUK Z2 (Snapdragon 820 with adreno 530, 4gb ram,-flashed with Lineage OS ) -cost me 200€ (almost a year ago)
Phone B is the S8+ (Exynos 8895, 4gb ram) cost me 900€
Of course in all other Benchmarks (Geekbench, Antutu, Basemark OS, Basemark X,Basemark ES 3.1, 3D Mark, Lightmark, Brue Bench Pro etc) the S8+ absolutely dominates\destroys the ZUK but in these 2, where ONLY the RAM (and the Storage) gets tested , the difference is not that big between the 2 Smartphones.
In daily use I cannot see a difference in responsiveness with both of them..If I could, I wouldn't have made this thread, and would have decided on my own (which one I should use daily).
P.S: It couldn't have been the Pixel because: see my Signature (phone history).. I never had that ugly ''Ferrari''
sensationvsgalaxy said:
thanks for your reply... you understood me wrongly...I said ''This question is for Developers\Advanced Users\Geeks, {not for } the normal user\average Joe (because [average Joe- meaning most people] uses their phone 90% for Calls \SMS , Whatsapp and just a few games like Candy Crush\Fruit Ninja and a little Web surfing)'' and they don't know anything about these geeky things.. so the cannot help me with the question. ..but that doesn't matter..it's not the point here. I just wanted to see what other people think is more important: RAM speed or NAND speed.
NOW THE DISCLOSURE:
Phone A is the Lenovo ZUK Z2 (Snapdragon 820 with adreno 530, 4gb ram,-flashed with Lineage OS ) -cost me 200€ (almost a year ago)
Phone B is the S8+ (Exynos 8895, 4gb ram) cost me 900€
Of course in all other Benchmarks (Geekbench, Antutu, Basemark OS, Basemark X,Basemark ES 3.1, 3D Mark, Lightmark, Brue Bench Pro etc) the S8+ absolutely dominates\destroys the ZUK but in these 2, where ONLY the RAM (and the Storage) gets tested , the difference is not that big between the 2 Smartphones.
In daily use I cannot see a difference in responsiveness with both of them..If I could, I wouldn't have made this thread, and would have decided on my own (which one I should use daily).
P.S: It couldn't have been the Pixel because: see my Signature (phone history).. I never had that ugly ''Ferrari''
Click to expand...
Click to collapse
Sorry for misreading your text.
I have a S8+ but I have had just about everything that was graded as a flagship since the time when flagships were snapdragon 600s (htc one m7 and s4) and before that all galaxy S phones.
I have had phones with the snapdragons: 800, 801, 805, 810, 820 and now 835
The thing is, could you tell the difference between what you have benchmarked in the real world? I don't think so.
Can you tell the difference between a snapdragon 800 and a 805? I sure couldnt and had a few 800s; Could you tell the difference between a 800 and a 810? definetly, although subtle; Could I tell the difference between a 810 and a 820? yup, but it's even more subtle... but from a 820 to a 835? No way.
Funny enough, you can tell the difference between a galaxy s6 and a oneplus 2, or between a Mi Mix and a S7, and both these comparisons have the same processors (hell, if we are comparing exynos, the samsungs have a more powerful processor)... The chinese phones are faster
This said, if you want to chose between a SD820 and a SD835 based on real world performance, the difference if negligible at best; if you want to go by benchmarks my Exynos s8+ scores 181k on antutu (overclocked 2.5ghz scores 5-6k more) and that is a full 20k faster than a OnePlus 3t with a SD821.
My advice won't be geeky or anything like that, we got to a point where we are putting more horsepower in a car that has no more runway to run. No app laggs a 820.
If you have both phones, use as a daily driver the phone that suits your needs better.
A phone is not a processor nor a LDDR4 ram, a phone is a whole and as a whole, AT THIS MOMENT, nothing beats the S8+ in my opinion.
badjoras said:
Sorry for misreading your text.
I have a S8+ but I have had just about everything that was graded as a flagship since the time when flagships were snapdragon 600s (htc one m7 and s4) and before that all galaxy S phones.
I have had phones with the snapdragons: 800, 801, 805, 810, 820 and now 835
The thing is, could you tell the difference between what you have benchmarked in the real world? I don't think so.
Can you tell the difference between a snapdragon 800 and a 805? I sure couldnt and had a few 800s; Could you tell the difference between a 800 and a 810? definetly, although subtle; Could I tell the difference between a 810 and a 820? yup, but it's even more subtle... but from a 820 to a 835? No way.
Funny enough, you can tell the difference between a galaxy s6 and a oneplus 2, or between a Mi Mix and a S7, and both these comparisons have the same processors (hell, if we are comparing exynos, the samsungs have a more powerful processor)... The chinese phones are faster
This said, if you want to chose between a SD820 and a SD835 based on real world performance, the difference if negligible at best; if you want to go by benchmarks my Exynos s8+ scores 181k on antutu (overclocked 2.5ghz scores 5-6k more) and that is a full 20k faster than a OnePlus 3t with a SD821.
My advice won't be geeky or anything like that, we got to a point where we are putting more horsepower in a car that has no more runway to run. No app laggs a 820.
If you have both phones, use as a daily driver the phone that suits your needs better.
A phone is not a processor nor a LDDR4 ram, a phone is a whole and as a whole, AT THIS MOMENT, nothing beats the S8+ in my opinion.
Click to expand...
Click to collapse
I agree with everything you said..except the last sentence:
There is something faster than a s8+: a s8+ WITH CYANOGENMOD\LINEAGE OS or Oxygen OS:angel::angel::silly::victory: