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.
So, now that windows phone 7 is out, is there any chance of us getting a port for the rhodium? I realize every windows phone 7 phone has a snapdragon and the os is pretty resource extensive, but is it possible, mindful of the performance degradation?
As has been said in the dozen other threads on the same subject...no.
kanwal236 said:
So, now that windows phone 7 is out, is there any chance of us getting a port for the rhodium? I realize every windows phone 7 phone has a snapdragon and the os is pretty resource extensive, but is it possible, mindful of the performance degradation?
Click to expand...
Click to collapse
You're kidding; yes? It makes no sense to try; however maybe the HD2.
tbh the OS is very complex and idk how itll behave on a storage card if youre talking about a port like XDANDROID, its very possible but itll need some serious time to optimize and be able to run flawless on our TP2s
Logical Answer (No Point)
Even if it were possible for developers to dedicate their time to yet another major long-term project, why would they when the hardware necessary to use WP7 isn't supported on Windows Mobile devices or if they found a work-around it wouldn't work as good.
I think the fact that we have Android is good enough, WP7 is a fresh OS and deserves better. — It's the same mentality as people who use OSX Visual Styles on their Windows 7 machines, it makes no sense or the people who use the iPhone or now WP7 overlay app on their device.
As much as I love the touch pro 2 for it's solid build quality and amazing keyboard; let's be honest, the smudgy resistive screen isn't nice compared with a capacitive AMOLED screen and many other reasons why WP7 wouldn't be as glamorous as on a new device.
*Also, look how long it took the team to get Android to run to a usable/enjoyable point, by that time Froyo was already released and you could have made enough money to go out and buy a brand new Android device. — With WP7 the project will be even longer in my opinion, as there are more components to think about in regards to how the OS operates and functions. (No 'expandable' SD-card, can only sync via Zune software and many other barriers)
*-No disrespect to any of the XDAndroid team you all did an awesome job, just pointing out the fact that delays and issues are to be expected, so WP7 would just be an even greater headache which isn't worth it, might as well start a WP7 project fresh with WP7 hardware then the fun can begin.
Is it possible we will see these on our phones at all? I think it would be fun.
unless some1 develops a new rom with that, then no
i wouldnt expect any of them to be ported because there wont be a lot of demand for that since one of the points of nexus is to be vanilla android
There is definitely not going to be a lot of demand for this. People buy the Nexus often for the specific reason of not using TouchWiz, Sense, or Blur.
And its definitely not going to happen until these companies start releasing phones based on Android 4 with the skin attached. Even then, its a lot of porting for a very small # of people.
ceredics said:
Is it possible we will see these on our phones at all? I think it would be fun.
Click to expand...
Click to collapse
Of course it's possible, and the one way you can be certain it happens is to port it yourself.
You'll probably have better luck with TW to start with, and it would make it much, much easier if you can find a phone that is almost identical to the Galaxy Nexus to port from. eg. same CPU, most same hardware, etc. A lot of times you can get it booting by just swapping the kernel with a native one and making a few minor changes to the ROM.
I'm attempting to port the leaked ics sense to the g nex today. Going to take some work but there are a few files that I know need changing and I'll use imoseyons kernel.
I upgraded from the Nexus S, after receiving the ICS 4.0.3 update on it, to the Galaxy Nexus. ICS on my Nexus S was running pretty much flawless. I had none of the issues some other users had.
Anyway, seeing how awesome ICS was I decided Galaxy Nexus was a must for me. Thus the problems began. While I'm not experiencing so many issues as other users do I'm sick of random reboots, freezes. And I'm on 4.0.2 that feels slower then it should be. Seriously instead of an upgrade I FEEL LIKE I BOUGHT A VERY EXPENSIVE DOWNGRADE.
I thought these issues will be fixed soon and Google will release the 4.0.5 update but it seems there is no word of that.
I was underwhelmed with stock performance, these phones beg for a ROM upgrade. CM is moving along much faster now with lots of the typical CM settings being added for ICS. Stable, smooth and fast. Nightlies are back. If you require a ton of customizations there are a few other good roms available that might sacrifice some of the stability and smoothness.
Point being, you'll like this phone
Another one of these threads?
You realize that the CM team would fall into the same problems that the Android team currently does. At last count, there have been just over 1,000,000 unique Cyanogenmod installs... There are 850,000 Android handsets activated every day, from different manufacturers, carriers, regions, etc..
Believe it or not, it gets very hard to support devices when that many are sold. By comparison it is easy to support 1,000,000 installs. A small fraction of which are actually updating nightly. As far as custom ROMs go, CM covers a large # of devices and does it well, but to assume because they can handle that they could handle running an entire phone manufacturer is laughable.
OP, massive leak on the next ICS update for the Galaxy Nexus.
http://www.youtube.com/watch?v=DksSPZTZES0
This is old news… Samsung hired Steve Kondik, the CyanogenMod founder...
zeekiz said:
OP, massive leak on the next ICS update for the Galaxy Nexus.
http://www.youtube.com/watch?v=DksSPZTZES0
Click to expand...
Click to collapse
this should be posted as sticky as information to all
zeekiz said:
OP, massive leak on the next ICS update for the Galaxy Nexus.
http://www.youtube.com/watch?v=DksSPZTZES0
Click to expand...
Click to collapse
now that was funny!
The problem is this:
Google has no balls. These companies are making bank on phones without any or very low software costs.
What is needed is a better end user experience and to get that they have to get fragmentation under control. It doesn't need to go away it just can't be the retardation that currently is Android.
They need to do the following:
User should be able to choose between AOSP and custom skins for every device. This ends the lack of updates and compatibility issues that crop up with sense, blur etc.
Custom skins and apps should all be uninstallable. No bloat if the user doesn't want it.
They need to get hardware variance under control to help developers with compatibility. Its getting crazy trying to support all these different devices. We need far fewer hardware revisions and a tad more uniform releases. No reason to have 20 different handsets every year complicating everything from drivers, app compatibility, updates etc.
Aridon said:
They need to get hardware variance under control to help developers with compatibility. Its getting crazy trying to support all these different devices. We need far fewer hardware revisions and a tad more uniform releases. No reason to have 20 different handsets every year complicating everything from drivers, app compatibility, updates etc.
Click to expand...
Click to collapse
Clipped, but all of what you said makes sense, to me, an advanced n00b who may not have the technical insight to understand all the implications.
How many devices has ICS officially been rolled out for? 2, maybe 3 (sticking to phones here). Code has been out for ~5 months (?). Android is great, but its popularity has led to a plethora of devices with dramatically differing hardware and it takes a lot of work to make it work. To keep device manufacturers happy I'm sure this means sacrifices have to be made at the Google level in order for ICS to work on whichever strange collection of hardware components go into Phone X.
I wouldn't like to see hardware dictated across the board, variation is great, but it would be better if there were a very small collection of basic ingredients going into the cornucopia of phones, each with their own HW specs, often questionable.
I'm happy I used plethora and cornucopia in the same post.
I figure it's possible, but could I theoretically port the Android L Preview for the Nexus 5 to my HTC M8 Google Play Edition?
The hardware is fairly similar: same amount of RAM, same resolution, pretty much identical CPUs, same Bluetooth number.
I'm aware it was recently ported to the Nexus 4, but the 4 and 5 are both LG devices.
It's summer, so I have plenty of time, and I really want to have KitKat on my M8 XD
I found a couple tutorials for porting ROMs, but they've been between the same manufacturer.
I'm almost wiling to just go buy a Nexus 5, but I much prefer the M8 so I'd like to give this a shot if possible.
Thanks in advance!
*I wasn't sure whether to put this here or in general Android Q&A, so please let me know if this is in the wrong place.
Posting here is fine.. Also just an FYI you already have "KitKat" on your M8 can it be ported? Anything can be ported with the right knowledg and resources. Similarity between devices is key, manufacturers being different isn't a deal breaker. You basically just need to figure out exactly what makes your device tick. Kernel is probably going to be tricky. If you can get it booted or at least partially booted a good kernel Dev can probably help out to get us a legit M8 Android L AOSP kernel and then from there the rest can be worked out ie: drivers and such for graphics, ril should be easy, WiFi will probably suck and be wonky... It can be done but will probably be a bunch of time and hackery lol... PM me... Maybe will get something going together! I have quiet a bit of Android knowledge when it comes to porting stuff... Hit me up
SolarTrans said:
I figure it's possible, but could I theoretically port the Android L Preview for the Nexus 5 to my HTC M8 Google Play Edition?
The hardware is fairly similar: same amount of RAM, same resolution, pretty much identical CPUs, same Bluetooth number.
I'm aware it was recently ported to the Nexus 4, but the 4 and 5 are both LG devices.
It's summer, so I have plenty of time, and I really want to have KitKat on my M8 XD
I found a couple tutorials for porting ROMs, but they've been between the same manufacturer.
I'm almost wiling to just go buy a Nexus 5, but I much prefer the M8 so I'd like to give this a shot if possible.
Thanks in advance!
*I wasn't sure whether to put this here or in general Android Q&A, so please let me know if this is in the wrong place.
Click to expand...
Click to collapse
Good luck. The experts with cm11 can't even get their roms working perfect. They still have quite a few bugs. It is up to you, but I feel spending a bunch of time on a preview is not a good usage of time. I have a nexus 5 also, and trust me, L is nothing really special. They have GPE roms that have almost all the L features already available for an m8.