Related
Hello,
I was so close to buy the Desire until I saw the ad of the Galaxy S..
Amazing screen (normal under sunlight), more powerful cpu/gpu.. but its Samsung! and after reading lots of comments they said that Samsung is crap! is it right? Why?
If its only the UI that is crap can I root it and install another room?
So, Should I wait for the Galaxy S or get the Desire?
Thanks.
DESIRE without doubt
It all depends on what you want. I have had Samsung phones in the past and they were pretty good. Those types of responses remind me of students in college who say "Yea...that professor is hard and rude...don't take him!'
IMHO the best thing to do is get some hands-on time with both of them if possible. Even try them out for a couple of days. That is the only way you will actually know which one is right for you.
you will actually know which one is right for you.
Click to expand...
Click to collapse
What do u mean by that?
They are the same super phones but with some advantages to the Galaxy, right?
I will use my phone for apps, games, multimedia, browsing etc. (not for business..) so I think both those phones are the top for these kind of stuff..
I just dont understand why everyone hates so much Samsung..
leoon said:
What do u mean by that?
They are the same super phones but with some advantages to the Galaxy, right?
I will use my phone for apps, games, multimedia, browsing etc. (not for business..) so I think both those phones are the top for these kind of stuff..
I just dont understand why everyone hates so much Samsung..
Click to expand...
Click to collapse
In other words...use your buyers-remorse, return/exchange period to try out both phones. Do research when the Samsung Galaxy S comes out and see what others have to say on the forums.
The worst thing you can do is be biased towards one or the other. If you believe what others say about Samsung and how sh*tty they are, then once you actually do see the phone...you will try to find some sort of discrepancy with it (its simple psychology )
Yes, the Galaxy has a bigger screen and a "rumored" faster processor. However, until the final product is made and released...the hardware and software can still change.
leoon said:
What do u mean by that?
They are the same super phones but with some advantages to the Galaxy, right?
I will use my phone for apps, games, multimedia, browsing etc. (not for business..) so I think both those phones are the top for these kind of stuff..
I just dont understand why everyone hates so much Samsung..
Click to expand...
Click to collapse
Samsung are fully behind their new Bada OS. They've stated that only 20% or less of their devices from now on will run Android and I only expect that to go down. That and HTC are the de facto hardware standard for all Android devices.
Haha you have no clue.
Actually, 50% of Samsung phones will be Android and another 33% will be Bada. The rest is for Windows Phones and other crap.
In response to the thread question: I chose the Desire, because the Galaxy S doesn't have a flash for the camera.
One (and the only!) annoyance with the Desire is the limited internal storage for applications. It's only 140MB. You can install applications to the SD card, but it will still go down. According to Google, the option to install to the SD card will come to Android 'soon'.
The Galaxy S will also have the better screen I think. That's because the Desire's screen is not full 800x480, because it uses a pixel layout with only two sub-pixels instead of three, which makes it seem a little bit blurry (but really just a little bit).
And last, but not least, I think HTC's software is probably better than Samsung's. Sense (even if you don't like the launcher) is a very useful add-on (e.g. the much better dialer) and I am not sure about whether Samsung is able to compete in that regard.
I chose the Desire, because the Galaxy S doesn't have a flash for the camera.
Click to expand...
Click to collapse
It seems that you choose the Desire just because the galaxys doesnt have flash! even though the screen+cpu+720p video recording and still only for the lack of flash you dont choose the galaxys!?
What im gonna do is to wait till its released and read the indepth review about the phone.
Thanks for the replies goys.. i choose to wait.
I feel compelled to point out a few things in this discussion.
First, assuming that "buyer's remorse" is a global standard is a mistake. In many countries, including Sweden where I'm based, you can return products for up to 30 days after a purchase with the caveat that the package/seal is unbroken. This applies to electronics. This means that everybody needs to check up on their local regulations and that of the retailer before you go out and buy something, expecting to be able to fiddle with it and then just return it.
Secondly, calling Bada an OS is a misnomer. It's a platform. A platform that can be placed on many different OS's. To me, it sounds like Samsung will be releasing several phones with Bada on top of their own proprietary operating system until they can either see a clear winner of the OS market share battle or until the OS's catch up with what they want and know they can offer the market in terms of functionality. Of course, where the boundary between the platform and the OS goes is kind of an unknown, but I would be surprised if the Galaxy S didn't have an Android version of Bada placed on top of it - think of it as Samsung's Sense.
Thirdly and lastly, I think there is a lot of displeasure with Samsung among smartphone users because they have a tendency to both promise more than they can deliver and after the first few months of a new smartphone release quit updating the software. I own an Omnia i900 and an Omnia HD i8910 and speak from experience on this front. Mind you, the devices they put out are generally top-notch, but Samsung has a problem managing expectations.
My Desire is currently my main phone, but I'm still interested in the Galaxy S and will be waiting to see what the consumer verdict on it is once it comes out. As others have said, HTC offers a very useful overlay in Sense, the Desire is already rooted (you should never assume a phone will ever be rooted when you buy it, but it's more likely that HTC will, and in the case of the Desire it's already a fact) and, more than anything, the Desire development community is huge, active and dedicated. So at the end of the day, opting to wait several more months just to get a larger screen and a promise of 720p video recording does have its downsides.
I'm pretty interested in the Galaxy S, will almost certainly get one soon after release and see how I like it, so I can give a users comparison of both nearer the time. As per usual I'll keep whichever suits my use best.
Regards the pros for the Galaxy S, these are the main things as I see them, a few mentioned earlier and a few not yet mentioned:
- screen will be considerably better, more battery efficient, better sunlight legibility, larger, won't have the subpixels issue
- better battery capacity
- 8 or 16GB internal memory in addition to card slot
- the stills camera in all situations not requiring a flash is likely to be considerably better than the Desire's
- 720P video capture
- divx/xvid/mkv support out of the box, with certification for 720P avi playback
Worth noting that the last two there may yet come to the Desire, since they have been rumoured to be coming via firmware update for some time.
The main positives for the Desire is Root, more active Dev community, better HTC support in terms of FW upgrades/hotfixes etc.
Lets say it gets rooted, Will I be able to install into the Galaxy S the ROM of the Desire, so I can take advantage of the active dev community?
Thanks.
In theory, yes, you can. But there will be issues, which means it may not be worth it.
I think not, maybe, but different drivers..it would take time for sure!
leoon said:
It seems that you choose the Desire just because the galaxys doesnt have flash! even though the screen+cpu+720p video recording and still only for the lack of flash you dont choose the galaxys!?
Click to expand...
Click to collapse
Yes, just because of the flash. I absolutely need it, that's why I chose the Desire.
Other than the missing flash, the Galaxy looks quite good.
@NZtechfreak
Your points are right, except for the part about the camera. The Desire uses a camera module made by Samsung. The Galaxy will very likely use the exact same camera module. And of course, at night, it will be useless without the flash.
Galaxy S may be better hardware-wise, but..
It's possible that Galaxy S won't have flash (but there are some rumors it will), so that is a dealbreaker for me (the reason why I switched from the Hero).
The other (more important) reason is that previous Android phones from Samsung had almost no scene development going on. Just compare the Dream/Hero scene to the Galaxy i7500.
Last but not least Samsungs support and bugfixing is worse that HTCs (yes, it is possible ).
That is why I decided to go with the Desire. If you don't mind waiting I would suggest to wait for the Nexus Two.
Or you can wait until the Google I/O Conference...
Quist said:
As others have said, HTC offers a very useful overlay in Sense, the Desire is already rooted (you should never assume a phone will ever be rooted when you buy it, but it's more likely that HTC will, and in the case of the Desire it's already a fact) and, more than anything, the Desire development community is huge, active and dedicated.
Click to expand...
Click to collapse
Hi all, been reading the Desire threads with interest as I'm able to upgrade in July, currently have a Blackstone, and at the mo it's most definately looking like the Desire will be my new phone, looks like a superb piece of kit, but, I need to use tethering on whatever handset I have, and up until now thought I would have to do this on a Desire via USB, because you can't do it wirelessly unless you root first.
Everything I have read here and anywhere else up until I read the above post says the Desire needs rooting to do this.
So, is it already rooted out of the box or not ? I'm puzzled !
Comments from a tester of RC1 firmware Galaxy S in an Australian forum:
- much faster in use than Desire
- much better screen (brightness, vividness & outdoors visibility)
- better battery life time than Desire with stock ROM (no hacks)
- camera is only ok
- very responsive touch
Just FYI. I think both phones are great.
two phones are great and the galaxy s does have super amoled, altho desire have amoled, super amoled is better under the sun. but somehow i don't like how the galaxy looks. it looks - plain, boring..
hopefully htc will release the update when froyo is out together with some fixes and 720p recording.
The only Android phone I would buy is Google branded or HTC. Because they have much more experience with Android than others, and they are more connected together. Also updates will be much more regular for Desire, since it is almost N1 clone. And community for HTC Android phones is much bigger than for Samsung.
Hi all,
I have Palm Treo 700p's and want to update a bit without losing my fair and flex
family plan with Sprint; unfortunately Spring says I can't upgrade to any of the
phones that natively run Android,
I learned about flashing HTC phones running WM and have been trying to learn.
Trying to decide between the Touch or Touch Pro which seem to be the newest
HTC phones I can use.
It appears that the Touch had the best support but the developers have moved
on and the Touch Pro may now be getting more support; do I read this correctly?
Which would you recommend, Touch or Touch Pro, or is there another phone I
should check with Sprint for use?
I welcome your input
Thanks
FS
You're going to be very disappointed if you expect either of these phones to run Android natively well.
This port isn't nearly done. Perhaps the only phone (to my knowledge) that could be considered complete is the HTC Vogue - which is ironically the original Touch you are probably speaking of.
The TouchPro IMHO is a better phone (the keyboard is fantastic - only better is on the TP2 ) but does not run Android very well. Android is just a plaything, for testing and for fun on most WinCE devices.
To sum up - the Vogue & the HD2 have the most complete port of Android, with the Vogue probably being considered "completely finished" (full NAND), however... that hardware is old. HD2 is very promising, they have a few little bugs to squash and then NAND... But no HD2 love for Sprint.
Not sure how good of an Android experience it is on the Vogue. Won't ever be that fantastic on the TP or TP2 tho.... Old hardware there as well my friend
I was in the same boat. have a great (cheap) old data plan that I was not willing to give up.
I went with a touch diamond. My previous phone was a vogue.
I can say that the diamond is a far better phone than the vogue. Better screen, more responsive touchscreen, better video, accelerometer, better camera... but the Vogue probably does better with Android since it can run Android from Nand instead of the storage (SD) card.
Android is fun on the Diamond, but its pretty crippled. No camera. No speakerphone for things like GPS. Poor battery life. Too slow for any flash apps to run fluidly... Basically android on the Diamond feels more like an emulation- because that is all it is.
That said, its fun to be able to play around with android, and WinMo is not so bad for a dead OS. There are some decent ROMs and plenty of freeware still floating around. And the Diamond makes for a nice phone on terms of small size, GPS, good speakerphone, WIFI and even WIFI sharing with the right ROM.
tk76 said:
I can say that the diamond is a far better phone than the vogue. Better screen, more responsive touchscreen, better video, accelerometer, better camera... but the Vogue probably does better with Android since it can run Android from Nand instead of the storage (SD) card.
Android is fun on the Diamond, but its pretty crippled. No camera. No speakerphone for things like GPS. Poor battery life. Too slow for any flash apps to run fluidly... Basically android on the Diamond feels more like an emulation- because that is all it is.
That said, its fun to be able to play around with android, and WinMo is not so bad for a dead OS. There are some decent ROMs and plenty of freeware still floating around. And the Diamond makes for a nice phone on terms of small size, GPS, good speakerphone, WIFI and even WIFI sharing with the right ROM.
Click to expand...
Click to collapse
Just to set the record straight, this project is running natively on the hardware - it's not a virtual machine, and it is certainly not being emulated in any way shape or form...
I could see how you would think that, because of all the broken/not working stuff... Well we just have to reverse engineer WinMo libs, dlls, etc and then write our own drivers basically for the different pieces of hardware.
Hence the reason new kernels come out so frequently - there's a lot of work that needs to be done on that kernel to get everything working the way it should. Devs are making some good progress lately, hopefully DIAM/RAPH will have NAND soon. I heard Neopeek was working on NAND back in August on his DIAM... haven't heard much about it since unfortunately. However, RHOD's have a partial NAND, and with the head of steam we've got going now, I'm pretty confident soon we will be up to the level of the Vogue - if not beyond it. However, the processor/RAM specs are pretty paltry compared to most native Android devices.
Sorry for the damned long post. One last question, your speakerphone doesn't work in GPS? Hrm. It should. Have you tried the newest kernels...? The autobuild service is down, but F22's been kindly building them for us...
why not just get a NEWER phone other then one that was released 2-4 years ago?
Cause after having invested SO MUCH time into running android on the phone, it's impossible to give up.. And having full control over hardware compensates for the hardware being ancient
Aaron McCarthy said:
why not just get a NEWER phone other then one that was released 2-4 years ago?
Click to expand...
Click to collapse
Because moneys doesn't grow on the trees..
HELICOPTER88 said:
Because moneys doesn't grow on the trees..
Click to expand...
Click to collapse
Exactly! Or I would have had a nexus 1 a long time ago... ;D
e334 said:
Exactly! Or I would have had a nexus 1 a long time ago... ;D
Click to expand...
Click to collapse
and I would have had a Desire...
Source
HTC Bresson, just revealed by This is my next as being on T-Mobile's roadmap, is the 16-megapixel Windows Phone 7 handset we recently saw a commercial for. According to the blog, Bresson is coming "beyond" the September 2011 timeframe, making it sound like a holiday release is in the cards -- and thus a likely Windows Phone 7.5 Mango build. Note that the hardware being displayed here is almost definitely just a placeholder for the real Bresson, as it seems to be little more than a modified Desire S.
Besides Bresson, we're also expecting HTC to bring the Ignite slate and Prime QWERTY slider to the WP7 family this year, although carriers for those devices (if they are coming to the US at all) remain a mystery. Bresson will likely only be rivaled in the megapixel count by the Altek Leo and Nokia N9/N950, whose premiere teaser advertisement we spotted earlier today. However, as many observers have noted, pixel count alone is not the most significant factor in determining picture quality.
Just a pity the device is HTC made.
They make the worst cameras don't they.
doministry said:
Just a pity the device is HTC made.
They make the worst cameras don't they.
Click to expand...
Click to collapse
agreed. I am curious to see a new Samsung or what Nokia is going to bring Post-Mango.
doministry said:
Just a pity the device is HTC made.
They make the worst cameras don't they.
Click to expand...
Click to collapse
Yea, I was thinking the same thing. Their cameras are...ok, not great. 16mp or 250mp, what's the difference if your quality is just...ok...????
Maybe we'll be impressed but, I'm not counting on anything myself.
Chances are this is the new Sony Exmor R module in the phone. Remember, manufacturers do not make all of a product in these kind of devices (LG/Samsung screens, Qualcomm chip, etc).
I am guessing HTC is not in the optics business. But I could be wrong.
Of course, putting a nice camera module in your phone is only half the battle; you still have to do some programming to get it to work well.
This is... weird.
Looking at the bigger picture here, you would have thought looking at their previous models that HTC would choose Android for a phone that's quite clearly going to be a high end flagship, they wouldn't put a 16mp camera in something that isn't going to be a big model for them.
I wonder if this indicates a shift in their preferred OS, or maybe I'm just reading too much into this
The Snapdragon 8x50 and 8x55 support up to 12 megapixels. The 8x60, which Windows Phone 7 does not currently support, supports 16 megapixels.
Edit: Though I did just notice that the official Qualcomm page says the 8x60 supports Windows Phone: http://www.qualcomm.com/snapdragon/specs
Sounds like it will be pretty nice.
my next WP7 device will be NOKIA......
It is a great sales pitch.
The only HTC device I ever used was the HD7 and the camera was dreadful.
I guess it's just me but HTC seem to make phone that all look roughly the same.
At this time I think I'm going to be looking at the Nokia's WP7 models available In the first quarter of 2012 and pick up one of those.
I don't buy the phone for only the camera. Agree that HTC usually have a worse Camera than other smartphone, but they have a better build quality. Almost all HTC device look damn sexy. For example: HTC Leo and it's younger brother.
if youre into phone camera, nokia is the way to go. a lot of people are very impressed with phone camera nokia has in each of its phone releases. im sure nokia will bring that to their wp7 release. another thing, nokia also has phone releases that are very appealing to teens and they are way cheaper.lol!
well, with stock software my 12mp mozart is ok in daylight situation.
the updated software for the camera (which still hasnt been officially released)
is just awesome, it does near perfect pictures
ive uploaded two of them, currently im not running the updated camera and pictures tend to be bad quallity.
htc really need to step it up, get all parts of their phone working flawless together... like the xenon flash...
root beer said:
I guess it's just me but HTC seem to make phone that all look roughly the same.
At this time I think I'm going to be looking at the Nokia's WP7 models available In the first quarter of 2012 and pick up one of those.
Click to expand...
Click to collapse
Nope. Not just you.
What HTC DOES do is reuse their shell and specs, as seen in all the Leo-ish devices. However, that design is a simple, yet beautiful design. I loved my HD2's design & I think the HD7 improved on it in every aspect. But you also have the EVO and such which use the same design.
webwalk® said:
well, with stock software my 12mp mozart is ok in daylight situation.
the updated software for the camera (which still hasnt been officially released)
is just awesome, it does near perfect pictures
ive uploaded two of them, currently im not running the updated camera and pictures tend to be bad quallity.
htc really need to step it up, get all parts of their phone working flawless together... like the xenon flash...
Click to expand...
Click to collapse
Xcuse me but which 12mpx on your Mozart?!
A typo I think
Anyway daylight pics are easy for almost any camera today.
Show some night ones or in difficult light than we can talk.
aww its only 8 x(
however, in lowlight it gets grain and noisy,
the xenon provides good light for close ups, but thats it
well all im sayin is htc need to push some updates for cameras
but the hardware should be capable of making good pictures...
doministry said:
Just a pity the device is HTC made.
They make the worst cameras don't they.
Click to expand...
Click to collapse
Also, touchscreens are poor too compared to Samsung/Apple and probably others. I have the HD7 and it doesn't track smoothly in the horizontal axis (with the phone in portrait more). Presume the HD2 and Desire HD are the same.
Im curious, the imagesense found on the One X supossedly makes the shutter speed faster, improves the quality on the pictures and videos taken with the phone but they use propietary drivers, so they're not used on AOSP roms like CM10 or AOKP, is the chip never going to be usable on these roms?
Yeah. I like to know that too
Sent from my HTC One X using xda premium
Interesting... I haven't heard about that one. How much difference does it make just out of interest?
chrisoverson said:
Interesting... I haven't heard about that one. How much difference does it make just out of interest?
Click to expand...
Click to collapse
Difficult to say, since the images and videos are massively over compressed.
Pretty sure that's the Sense camera app and not the chip, though.
If you mean the sense camera then no..it is possible..but too difficult to get it working on aosp based roms..
hello00 said:
If you mean the sense camera then no..it is possible..but too difficult to get it working on aosp based roms..
Click to expand...
Click to collapse
No, no im not refering to sense camera, supossedly the one series phone have a dedicated chip for processing images and videos recording check this:
"HTC was proud to announce that not only are the phones awesome, built extremely well, trimmed down and run fast with HTC Sense, but they’ve also developed a new technology called ImageSense. HTC has actually added a separate processing core for the camera alone. So a dual-core phone will actually have three cores.
The ImageSense chip will not only offload the duties from the regular processor to keep the phone and operating system fast and stable. It will leave the camera completely uninterrupted to take quality, impressive photos. This also allows super-fast shooting possible with a 0.7-second shot time and a 0.2-second autofocus."
http://androidcommunity.com/htc-one-x-photos-show-off-new-imagesense-camera-technology-20120302/
Chad_Petree said:
No, no im not refering to sense camera, supossedly the one series phone have a dedicated chip for processing images and videos recording check this:
"HTC was proud to announce that not only are the phones awesome, built extremely well, trimmed down and run fast with HTC Sense, but they’ve also developed a new technology called ImageSense. HTC has actually added a separate processing core for the camera alone. So a dual-core phone will actually have three cores.
The ImageSense chip will not only offload the duties from the regular processor to keep the phone and operating system fast and stable. It will leave the camera completely uninterrupted to take quality, impressive photos. This also allows super-fast shooting possible with a 0.7-second shot time and a 0.2-second autofocus."
http://androidcommunity.com/htc-one-x-photos-show-off-new-imagesense-camera-technology-20120302/
Click to expand...
Click to collapse
That sounds a bit misguided. The SoC has some space devoted to image processing, it's not another general processing core!
BenPope said:
That sounds a bit misguided. The SoC has some space devoted to image processing, it's not another general processing core!
Click to expand...
Click to collapse
Its not another general processing core but its a dedicated discrete chip for the camera so not part of the SOC, could be image processing parts there as well ofc.
Granted this is about the MSM8960 One X but from what I've read the camera stuff is the same for all One S/X models and in part also for One V.
Source: http://www.anandtech.com/show/5779/htc-one-x-for-att-review/5
"HTC’s ImageChip is responsible for most of the things that would traditionally be done on the SoC ISP. 3A (Autofocus, Auto white balance, and Autoexposure), lens correction (geometric and chromatic correction), noise reduction, best shot selection, continuous auto focus, controlling gains on the CMOS sensor, LED flash level decision, region of interest identification (augmented with face detection) and so on. This is all stuff you can verify yourself by taking apart some of the ISP related files - curiously enough internally ImageChip is actually referred to as “rawchip.” This is also the hardware responsible for enabling HTC’s extremely fast image continuous capture and frame grabbing during video capture (HTC Video Pic). It’s somewhat analogous to what Google and TI did with the OMAP4460 on the Galaxy Nexus, except discrete and with a much more ambitious focus."
More here in the One S review: http://www.anandtech.com/Show/Index...ug=htc-one-s-review-international-and-tmobile
Discrete? That surprises me, and I stand corrected.
Guess HTC aren't ambitious enough to expect sales of these phones to be high enough to work it in as a part of the SoC. That's at least a quid to the cost of the phone right there!
BenPope said:
Discrete? That surprises me, and I stand corrected.
Guess HTC aren't ambitious enough to expect sales of these phones to be high enough to work it in as a part of the SoC. That's at least a quid to the cost of the phone right there!
Click to expand...
Click to collapse
Guess it enables HTC to have a consistently nice camera experience for users across their phones while picking whatever SOC is best/cheapest/comes with the right air interface for a region or carrier. Lol I feel like a PR parrot after typing that... Anyways IF a dev ever gets it working on AOSP for any device it might be easier to port it to other devices. I hear its not impossible, just a massive undertaking and will bring a lot of Sense framework which is not useful for much besides the camera, or maybe documentation will be released sometime. Now I'm just a hardware nerd with zero programming experience so take that with a grain of salt, I'd love to be proven wrong though
I can imagine the camera apk needing sense, but not the chip driver. Reverse engineering that driver and pulling in its dependencies could be a pain, as well of course as creating a new camera app.
If only there were more hours in the day...
After doing some research I found this phone (desire hd) has many similarities to the sony xperia 2011 line (me personally having an Xperia Ray). So I was wondering which hardware are actually the same like the cpu and the gpu, they both have have an 8.1 mp camera but are they both developed by sony? , I've been looking through this development forum, and have found some interesting roms I would like to port over, as the ray development is quite dry, and if the camera is indeed the same, then I wouldn't have to port over that driver, (which in jellybean roms would mean that the camera would actually work in the ray because jellybean roms for xperia don't), if their are anymore similarities then cross development between xperia 2011 line and the desire hd wouldn't be too hard. I will make a custom rom at some point in the future, but don't have enough knowledge yet for kernel or driver development, or how the android system works yet, but once that time comes, I will seriously consider porting it for this phone!
I think that you've got a long way to go before you just jump in to porting stuff over. As far as the specs go, you can check the Wiki here for some of that, you can also use google for many of the questions you have asked.
I've tried researching, but I haven't found enough detail yet (much like the wiki on here). I have successfully ported a desire s rom, but not a desire hd one, as they have some screen issues, which is too technical for me to get in to at the present time. But camera drivers is one of the key things I wanted to find out about, and there is just nothing I can find out about it. I know the the iPhone 4S camera is exactly the same but not sure about the desire hd.
There are two types of camera for dhd, some are produced by Samsung and some by OmniVision.
So it definitely hasn't the same camera of Ray.
Sent from my Desire HD using Tapatalk 2
only processor is the same.
chipset is different. radio is different.
camera is different. source is closed.
-> chance of a working port 0%