Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What problems were you having? I have a T-mobile G2 that runs pretty well, but I don't do much on it. The last upgrade actually seemed to introduce a random shutdown, making me actually regret upgrading the OS, but that's about the only problem I have.

It's unclear to me what I really need from further OS upgrades, as I'm not currently wanting any features. If the Galaxy S is really buggy I get you, but in general, I don't get the desire to upgrade Android rapidly.

I haven't dealt with Android technically, but my assumption would be that in Linux fashion, an older version isn't necessarily a bad thing as long as it still works for you (I have a 2.4 kernel on a netbook, for instance, who needs 2.6? I think even the 2.2 and possibly 2.0 kernel branches for linux are still used by certain projects).



It's been a while, but here are the issues I remember:

* GPS was completely broken (a known and admitted issue with the T-Mobile variant of the Galaxy). If you disabled it, you could use tower triangulation to get a rough position, but that made it unusable for things like driving directions.

* Battery life was terrible (probably not specific to that model, but it didn't get through a day the whole time I had it).

* The camera was awful (not unusual for smartphones at the time, but my old crappy N73 had a camera that was easily 10x better).

* If you unplugged the headset, the phone would automatically launch the music player and start playing music through the speaker, even if the music player wasn't running.

* USB mass storage mode didn't work, so you couldn't move files to it. The only workaround was to turn on debugging on the phone, which would then let it show up in as a USB device, but you'd have to enable/disable debug every time you plugged it in, as leaving it in debug made the screen not turn off.

* Lots of crap applications that you couldn't remove.

* Most of the menus had misspellings or bizarre word choices, like it had been passed through Google Translate (a nitpick concern, I realize, but it didn't give me a lot of faith in the quality control of Samsung).

Then there were all the issues with Android itself, which aren't specific to the phone, and I really don't want to hash out here, as some of them have been fixed by now, and I really have no desire to get into a debate about the merits of the platform.

I spent the next six months or so after returning the phone to see if the issues ever got addressed, just to see what would have happened if I kept it, and it seemed like most of them were still known issues. That made me feel better about my decision to return the phone.


I can identify with most of these issues on my Captivate, and that many of them were improved or resolved by installing Cyanogenmod (the big issues, GPS and camera, remain). That isn't a legitimate option for the vast majority or smartphone buyers, but it has extended my patience with an expensive purchase not living up to the claims of its maker.


Android OS upgrades almost always come with fixes for security flaws. You wouldn't be OK running your desktop with software that hadn't gotten updates for a year, right?


Depends on what security flaws they update, I've had my linux box up for over a year before, but I don't run many services and it sits behind a router. Windows is set to autoupdate, so it reboots pretty often, though.

I'm not saying I'm against updating, but if my phone is working (luckily it currently is), I shouldn't be forced to update unless there is something that actually is a problem for me, like someone being able to send an SMS to me that does something.

All the bugs the original poster notes would make me want an update, too, but I think returning the phone was the right thing to do. If my phone was that buggy from original purchase, I wouldn't want to wait for an update, either.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: