Live data from Hacker News

Why U.S. Galaxy S Phones run Android 2.1

forum.xda-developers.com

51–60 of 101 posts

Re: Why U.S. Galaxy S Phones run Android 2.1

#51
I've been planning to give up my iPhone for a 4G VZW Android, but it's easy to take a direct update channel for granted.

So, iOS 4 has 90 percent share amongst iOS device owners. What about Android 2.3? 0.4 percent, as of a couple weeks ago. Yes, that’s zero point four percent.

But for the sake of this being slightly more fair, let’s compare iOS 4 to Android 2.2 — an OS which came out well before iOS 4. The adoption rate there? 51.8 percent. That’s still pretty pathetic.

http://techcrunch.com/2011/01/17/ios-android-breakdown/

Re: Why U.S. Galaxy S Phones run Android 2.1

#52
As an Android user (and promoter to my friends/family), I'm starting to get worried about Google's approach to the product. Not because of "fragmentation" (which to me is an argument that essentially says "Android isn't going to ever be successful because its too successful now"), but because of the lack of attention it seems to be getting from Google.

It isn't just the OS itself-- several of Google's own apps are getting buggier and buggier. Voice worked fine when I first got my Droid a year or so ago, but has had a lot of bugs-- including dialing random numbers instead of the one I wanted. (Just yesterday, I tried to send a text message to XXX-XXXX and it truncated the last digit of the first group and complained that it couldn't send a text to XX-XXXX. Nothing I did could stop it from doing this except using the web-based version). Google Listen has stopped refreshing for huge numbers of people, and my wife's new Galaxy S won't even accept subscriptions. Not a word from Google on either issue, even though both show up in searches for the problem.

I had to install Launcher Pro to get any kind of performance out of my Droid, and even then it occasionally locks up on the home screen. Sometimes calls come in and the touch interface freezes, which means that I can't answer the phone. The Droid also will occasionally decide that there is no data connection when it has full 3G service according to the indicators.

I don't use it, but the stock SMS app has apparently has its own problems too-- at least Google has acknowledged those and is working on a fix, but as a whole, Android has gone from less technologically interesting (no wi-fi hotspots, etc) and stable to exciting and really buggy. Combine that with this kind of politicking, and I'm getting less and less enthusiastic about Android every day.

Re: Why U.S. Galaxy S Phones run Android 2.1

#53
post #8

Gee, I'd kind of liked Samsung because they seemed to focus on delivering good technology at a good price. I'd figured they perceived themselves as something of an underdog in the past (perhaps relative to the Japanese tech industry). This makes it seem like they're hiring Marketers and MBAs who think the best plan is to try to squeeze as much as they can out of their contract customers (the cell carriers) rather tha…

In fairness to Samsung they do incur non-trivial cost doing this. Imagine this situation Verizon says, "Our Samsung Galaxy S phone must get 2.2" while Sprint says, "No need". Should Sprint have to pay for what Verizon is getting? The issue is that you're going to pay, whether its Samsung or HTC. Some companies will build the price into the phone, others will price it in some other way (or some companies could eat the…

The biggest downside I see is that it will shackle Google's ability to move the platform forward. For example 2.3 is reported to include some major improvements for low latency audio. As a game developer how do you handle this? Just ignore this 2.3-only feature and target 2.1? Or do you build a 2.1 and 2.3 version? 2.2? 3.0? 3.1? Unfortunately we're talking about these phones being around for another 2-3 years at minimum so realistically you might be asking a developer to support 2.1 3 years from now? That's going to be a really tough sell. The other issue is security. Leaving all those old versions out there with little or no post-release updating is just begging for trouble. (and let's not forget about bug fixes -- no one wants to suffer 2 years working around an annoying bug. They simply won't buy another Android phone after a bad experience like that)

Re: Why U.S. Galaxy S Phones run Android 2.1

#55
post #50
post #13

The conflicting interests issue is really a problem in the Android space. As has been shown time and time again, vendors really don't want the burden of keeping your handset up to date forever because there is nothing in it for them, aside from perhaps avoiding too much negative press. Naturally people are going to compare it to iOS, where updates are free and rapidly disseminated. The difference there is that there…

" As has been shown time and time again, vendors really don't want the burden of keeping your handset up to date forever because there is nothing in it for them, aside from perhaps avoiding too much negative press. " The reality is a lot more depressing; the vendors actually want you to buy a new phone. If your current phone can run the latest version of Android - why would you bother ... ?

True to a point, but they don't have the luxury of assuming that you'll buy from them. Not upgrading their devices works against a repeat consumer, really, so you're just as, if not more, likely to help the bottom line of one of their competitors if they leave you in the cold.

And of course there's the march of progress, and the nexus one of one year ago is now outmatched by almost all devices with better screens, dual cameras, coming dual core processors and much better GPUs, etc.

Re: Why U.S. Galaxy S Phones run Android 2.1

#56
post #45

Earlier quoted context omitted.

I wouldn't be surprised if the in-house development costs rivaled or exceeded what something like Windows Mobile cost to license. That implies that Windows Mobile doesn't require similar in-house effort, on top of the OEM license fees. Windows phones still require the same hardware driver development effort, and WM7 is already starting to receive the carrier-bastardization treatment. I'd say Android's licensing being…

I have no idea how the Windows Phone 7 dev kit works, however with CE it literally was configuring some flags and resources, and that was it. Microsoft did a tonne of heavy lifting to make it so. There were boxed in drivers for virtually everything, and customization was absolutely minimal. And when you bought a MotoQ, it was stock CE.

As far as I understand it, Windows Phone 7's API is Silverlight with a few restrictions related to screen size and the like.

I haven't coded anything for Windows CE, but making a Silverlight app for Windows Phone 7 is about a difficult as making a WCF app for Windows, or an ASP.Net app for the web.

Re: Why U.S. Galaxy S Phones run Android 2.1

#57
post #4

This might be plausible, but it can't possibly be confirmed which makes it no better than speculation. I'm as frustrated as the next guy that my Captivate is still running Eclair, but stuff like this doesn't really get us any closer to a solution. When both carrier and manufacturer neglect to offer explanation or consideration for their collective failure to deliver, they must collectively be held responsible. This m…

> I'm as frustrated as the next guy that my Captivate is still running Eclair, but stuff like this doesn't really get us any closer to a solution. Maybe you already know, but you can get an unofficial Froyo rom from xda-developers. And before people jump on me about how it won't work for their mom or next-door neighbor - this is just a tip for fellow HNers, in case they didn't know already.

I'm no expert on flashing ROMs but bit the bullet this weekend. Flashed the latest Cognition ROM (3.02) to my Captivate. It was easy to do (for users of HN) and is quite an improvement over stock. I'd recommend owners of Captivates look into it. Take the standard precautions, read up, make backups, etc.

Re: Why U.S. Galaxy S Phones run Android 2.1

#59
post #13

The conflicting interests issue is really a problem in the Android space. As has been shown time and time again, vendors really don't want the burden of keeping your handset up to date forever because there is nothing in it for them, aside from perhaps avoiding too much negative press. Naturally people are going to compare it to iOS, where updates are free and rapidly disseminated. The difference there is that there…

> As has been shown time and time again, vendors really don't want the burden of keeping your handset up to date forever because there is nothing in it for them, aside from perhaps avoiding too much negative press. Then stop locking the bootloader and let me put the latest version of CM on my phone. I'm not going to buy Motorola and I'm not going to buy Samsung. Samsung won't release their kernel modifications for Fr…

  > Samsung won't release their kernel modifications for
  > Froyo which are needed by the CM team to get CM7 running
  > on the Galaxy S devices
Isn't this a violation of the GPL?

Re: Why U.S. Galaxy S Phones run Android 2.1

#60
post #55
post #50

Earlier quoted context omitted.

" As has been shown time and time again, vendors really don't want the burden of keeping your handset up to date forever because there is nothing in it for them, aside from perhaps avoiding too much negative press. " The reality is a lot more depressing; the vendors actually want you to buy a new phone. If your current phone can run the latest version of Android - why would you bother ... ?

True to a point, but they don't have the luxury of assuming that you'll buy from them. Not upgrading their devices works against a repeat consumer, really, so you're just as, if not more, likely to help the bottom line of one of their competitors if they leave you in the cold. And of course there's the march of progress, and the nexus one of one year ago is now outmatched by almost all devices with better screens, du…

The Nexus One may not match the hardware specs of some of the newer phones, but that doesn't mean it is out of the game. My Nexus One is still fast and powerful, and outside of that one Unreal Engine 3 game, has no problems with any app. So my point is that even though other devices have better hardware, rarely is the Nexus One outdated.
Post reply on HN