HTC Desire V Samsung Galaxy S

dedaw wrote: »

I'm looking at the HTC Desire (had previously considered a Smart phone) versus the Samsung Galaxy S. I have a Gold upgrade with my provder, making either phone only €99!!!
SO whick do you reckon? Had not considered the Galaxy but the guy in shop reckons it's the dog's! Bigger screen, HD screen, longer life battery, and still runs on android.
Any opinions, ideas, info would be much appreciated!

Im a Desire Owner, fantastic phone (if you can get your hands on one).
Iv owned 3 samsung phones in the past and all 3 were terrible. Now the Galaxy S could be different. Iv never used one but i will never touch a samsung phone ever again.

Read this comparison maybe

Don't worry about texting, with Android you can choose from a wide selection of keyboards and predictive methods. I think the Galaxy comes with Swype pre-installed, which would be my choice anyway.



I get a full day out of my HTC, no problem, and I rarely put it down for more than a couple of minutes.

Seeing the screen of each side by side really blows the Desire out of the water on that front.

Then again, there's no flash on the camera on the Galaxy S, but unless you take lots of photos that's not gonna annoy you that much.

ANy samsung phone ive had has been crappy so for me desire all the way

Some general differences between both phones based on my observations

I'll list the cons of both phones relative to eachother

Desire
Smaller screen with almost negligible difference in colour saturation and difficult to read in direct sunlight

No HDMI out

Adreno GPU (Slower than what's found on the Galaxy S)

Slightly heavier

Stocking issues

Galaxy S

No camera flash

Larger in size

Slower CPU

Poorer build quality and doesn't "feel" as nice as the Desire

Lacks the developer community of HTC Phones as well as the support

Many games do not function on the Galaxy S due to it's GPU (As a general rule, any application which doesn't work on the Moto Droid/Milestone won't work)

Touchwiz 3.0 pales by comparison to Sense UI

HDMI Out by Micro USB rather than a dedicated port

Froyo Sense + Expressobar = A winning combination

I'm buying a Galaxy S tomorrow for my father so i'll have firsthand experience with both.

partyatmygaff wrote: »

Froyo Sense + Expressobar = A winning combination

I'm buying a Galaxy S tomorrow for my father so i'll have firsthand experience with both.

That's actually what I have on my phone at the moment. I'm using neophyte 1.7.1 save battery sense. I use launcher pro over it though.

I think the CPU is underclocked to 800 mhz, and it uses f all battery in sleep mode. Went for 20 hours yesterday with a lot of usage, a few downloads, a couple of videos and still had 17% battery left. Runs smoothly enough aswell.

M5 wrote: »

BTW tocco was a joke of a phone, Samsung have moved on from there though

I agree the OS/software was painful, but my point still stands; it (Ultra) was very well built and had a great camera.

partyatmygaff wrote: »

I don't come to any conclusions. The stock standard cortex A8 as a CPU does not match the Snapdragon in CPU based operations. Quadrant scores take GPU in to account as well.

You just make it up as you go along. The Hummingbird processor used in the Galaxy S is NOT stock standard.

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).

http://alienbabeltech.com/main/?p=17125


Benchmarks comparing the Hummingbird processor (Galaxy S) against the Snapdragon show the former to be faster.

As shown by the charts above, the Galaxy S beat the two HTC-made devices by a bit for CPU and 2D graphics performance. But when it came to 3D graphics performance, the I9000 trumped the Qualcomm-equipped smartphones, achieving more than twice the frame rates of both the Nexus One and Desire (see video below).

These tests were performed on devices running Android 2.1. As some other reports have shown, the Nexus One is even faster with Android 2.2 (Froyo), improving upon its Eclair benchmarks, especially in terms of CPU performance. Given what the Galaxy S is capable of now, it's mouthwatering to imagine what it can do with a Froyo update.

http://asia.cnet.com/reviews/mobilephones/0,39050603,62200389,00.htm

GSM-Arena did CPU benchmarks of the Galaxy S and found it to be faster than the Desire as well: http://www.gsmarena.com/samsung_i9000_galaxy_s-review-478p3.php

Neocore Benchmark:

http://www.youtube.com/watch?v=DLUQP7CWyeQ&feature=player_embedded

Article comparing technical details of the two processors:

Lastly, since we know from the second article at the top that the Galaxy S performs so well with its GPU, why is it lacking in CPU performance, only barely edging past the 1 GHz Snapdragon?

http://alienbabeltech.com/main/?p=19309


The only benchmark tests where the Snapdragon outperformed the Hummingbird were where the device with the Snapdragon was running Froyo (2.2) and the device with the Hummingbird was running 2.1. Where testers have done this, such as here, They have usually gone on to say something like this:

Even though the Captivate lost to the Nexus One in every CPU benchmark, I would expect those results to change once the phone receives its Froyo update...

So as you can see, in ANY GPU benchmark, the Captivate (and all Galaxy S phones) simply walk away from the Nexus One.

What's even funnier is that the reported GPU performance from the next gen Qualcomm chip, the 1.5 GHz dual-core QSD8672, still wont quite match the GPU in the Hummingbird.

So any way you cut it, the standard hummingbird has a faster CPU than the Snapdragon, add overclocking and other tweaks that have been found, and the Galaxy S pulls even further ahead.

Qualcomm’s newest high performance chipset – the 1.5 GHz dual-core QSD8672 – also just so happens to have been specced to draw 80 million triangles per second. That’s pretty convincing for our hopes of this phone being able to nearly match the 3D performance seen out of the Galaxy S phones.

That’s until the phones get overclocked. The Samsung Galaxy S phones were rooted and modded as soon as the devices hit the UK and US markets. Since then, developers have been able to tweak the I/O read-write speeds for the phone’s default file system using a virtual EXT2 file system and some crafty hacking. That already made an impressive boost in Quadrant benchmark scores, but when you use a 1.2GHz overclock kernel, 2,500+ on Quadrant’s charts becomes a scary reality as no other Android handset has been able to crack the 2,000 barrier to date (let alone 2,500).
The kernels and file system tweaks are far from stable, however, but we’re confident the task is in good hands as it always is with the Android development scene. Then there’s FroYo yet to be released, as well: we might as well run for the hills at that point because these phones will have enough juice to build a mind of their own.

The only way you can have the Snapdragon CPU outperform the Hummingbird, is if you go to sleep and have a nice cozy dream where cold hard reality fades away and your wishful thinking becomes fact.

Cnocbui, I really couldn't care less. Reviews matter little, benchmarks are what matters. A Nexus One at 1GHz manages 75 MFLOPS. A Galaxy S manages 50 MFLOPS of CPU power using Linpack. There is no debate over GPU, CPU floating point operations however are a different matter. You don't own either phone so you can't really comment

However as of one hour ago I now have a Galaxy S AND a Desire (Well the Galaxy S isn't exactly mine as such but i've been using it for an hour now setting it up)

Here's what I can say

The Screen handles sunlight very good compared to the Desire. The extra 0.3 Inches of size make it seem massive in comparison to the Desire. Brightness between both is pretty much neglibile though.

TouchWiz 3.0 seriously sucks compared to Sense UI both in functionality and in speed. Menus lag and the widgets look poor and aren't as numerous.

The build quality feels decent but the phone feels too light and the plastics used feel cheap and thin

It looks like an iPhone rip off

Little and poor documentation when it comes to Android development on the phone (Rooting and ROMS, Kernels e.t.c.)

The GPU does make a difference. It makes some Live wallpapers like the Mario Bros run a tiny bit smoother (Although swiping between homescreens is pretty laggy)

The back cover looks cool despite feeling cheap :pac:

On all other accounts though it's a seriously good phone (I still prefer my Desire though)

Installed Launcherpro. The lag is still pretty bad but i'm gonna go do those Kernel mods to speed it up.

I'll keep you guys up to date

cnocbui wrote: »

Then why do you invent benchmark results out of thin air?

Did you say Linpack? Funny, that's exactly what they used here: http://asia.cnet.com/reviews/mobilephones/0,39050603,62200389,00.htm

Where they got 8.419 for the Galaxy S versus 7.003 for the HTC Desire.

Why do I need to own a phone in order to be able to research it's specifications and benchmarks performed by third parties? You were happy enough to state the Galaxy S had a slower CPU when you didn't own one at the time. As I said, you make it up as you go along.

I get a linpack of 50+ on my Desire, and depending how well the JIT works with the Galaxy that may well be higher than the Galaxy even when it finally gets 2.2.