Hacker News new | past | comments | ask | show | jobs | submit login

"Most of all, I love that neither Apple nor any other company can tell me what I can and cannot install on my phone."

though on the other hand, I hate, no. HATE, the fact that $CARRIER$ can tell me what application I have to have installed on my phone without any ability of uninstalling them.

Android is not all sunshine. I might post more comments as I continue reading the article.




That's only true if you use the distribution provided by your carrier.

If you don't like the OS the way they provide it, then wipe it and use Cyanogen or some other ROM that is set up exactly how you like it.

Cyanogen may not work on every Android phones, but there are still a lot more phones out there that can run Cyanogen than can run iOS.


This isn't that much different from jailbreaking your iphone and using Cydia though. Both techniques rely on exploiting flaws of the security framework put in place by $VENDOR.

Don't get me wrong: I do like the slightly increased openness of Android, but that just stems from the fact that the OS provides more hooks to hook your app into - it's not more open in the sense that there's less control inflicted upon you on what you may or may not do with the device you legally own.


That is not totally true: there is a fundamental difference between a closed source OS purposefully locked by its maker, and an open source OS tentatively locked by a mere distributor. On almost every Android phone, you can just flash the entire OS and replace it with a plain vanilla one or your own custom build. Try that with an iPhone...


well. On older iPhones with known issues in the bootloader, you could in theory also replace the apple OS with something completely different (remember the Android on iPhone 3G videos earlier this year?).

The fact that HTC and other vendors are sloppier in securing their phones (remember the discussions about Motorola's e-fuse?) doesn't make these phones more "open" in the "freedom" sense.

It just means that it's easier to exploit them to install a different OS.

Now the Android OS of course is open source, but what good is that if there's no device available that actually allows you to officially install your own build? This also means that my earlier comments are about the phones, not the OS itself.


The Nexus One does officially allow you to install your own build. Google gives you the directions to "unlock" your N1 bootloader, which granted, voids the warranty, but is a "sanctioned" method for flashing your phone's firmware.

Alternately, the OpenMoko FreeRunner is a "truly free" phone, and has its own distribution of Android available in which you have total control of the entire hardware and software stack.


While, as you said, you can "in theory" replace Apple's OS -- with Android, it's a practical possibility since the OS is available for you to tinker.

But I totally agree, this declared "openness" is bullshit. The situation with Android ROMs right now is almost identical to the situation with Windows Mobile and nobody would claim that is open.


There are 3 such devices: the ADP1 (aka G1), ADP2 (aka Magic, and the ADP3 (aka Nexus One)


My own custom build? That sounds wonderful. What phones/carriers allow this without jailbreaking? What stores/carriers sell those phones to consumers?

Before I customize it, how do I get/build a fully functional current vanilla version? By fully functional I mean all of the things normally needed/expected by default (like the app store for instance).

Does each carrier post source to their builds so I can modify what the phone came with?

There are many developers on this site. Have ANY of you built Android from source and used that on your phone? How did it work out?


What phones/carriers allow this without jailbreaking? What stores/carriers sell those phones to consumers?

T-Mobile and my local carrier Cincinnati Bell are both happy to recommend and "sell"/refer you to a Nexus One. CBW even has a couple N1's on display in their premiere display case, and a rep even asked me about what ROM I used on my N1, and said he used CyanogenMod on his.

Does each carrier post source to their builds so I can modify what the phone came with?

The carriers aren't the ones writing the software; you'd have to talk with HTC, Motorola, Samsung about that. Some carriers make specific requests, like Sprint putting their NASCAR app on, or Verizon's exclusive Skype app, but that's an app, not Android.

Have ANY of you built Android from source and used that on your phone? How did it work out?

I've had multiple attempts over the past couple years to build my own Android ROM, most recently with Cyanogen's mass of repos on Github, but either I wasn't looking in the right spot, or there wasn't enough documentation for me to figure out how to build it all on my own, so I failed on that aspect.

However, MoDaCo forum has the concept of "kitchens" where you can customize what features you want to include/exclude from various ROMs, and allows you to generate "your own" ROM that you can then flash to your phone, and I personally find this extremely attractive, even if I don't use it for myself because I like what the "vanilla" Cyanogen build includes.

All that said, you do however have multiple valid points, and I don't disagree with you on any of them.


Except much of the good Android parts, hardware drivers, and applications aren't actually open source. It's a nice pipe dream, though.


I've been pondering making the switch, but I refuse to buy a smartphone that I am not in control of. (The current solution has been to not buy a smartphone.) Can someone who has done this share how practical this solution is? Does your carrier retaliate in any way? Is this a constant task to keep updated? Do you lose features? Or is this something so simple any techie should do it without any pause for thought as it is all upside and no downside?


Installing Cyanogen on basically any HTC phone is trivial. You don't lose features (though you might gain a bit of flakyness in the software, depending on the phone). Carriers wouldn't be able to retaliate (unless you need a warranty repair) and keeping it updated is trivial too as the ROM Manager comes with auto update functionality

The downsides are that you might lose your warranty and that stuff breaks a little bit here and there (at least on my SLCD Desirefor which sending mail via Gmail stopped working and which crashes here and then - the usual little things)

But it's trivially done and generally works well.


I started using Froyo earlier this year by loading it on my Droid. (I really wanted the chrome to phone!) It took about 30 minutes to do, mostly by reading guides ahead of time then giving it a whirl. No problem at all.

Functionality overall improved. Verizon releases a version that requires additional cash for a few simple things (like tethering) that using 2.2 allowed stock.

Some android apps developed problems updating. The cause was some apps were not appearing as valid/runnable for 2.2 in the market.


Wait, verizon's 2.2 for the droid requires additional cash in order to tether? I ask because I'm a droid owner using verizon's 2.2 on my droid. I see the tethering option available, but I haven't tried to use it yet, so I don't know if it requires extra cash.


Whenever I signed my contract - it did. It was one of the "upgrade packages" along with the verizon mobile tv that tacked 10$ a month onto the bill.


Getting Cyanogen on your phone isn't always an easy task. I'm rooted on my EVO, but not rooted enough to get Cyanogen. Thanks Sprint for locking down an "open" phone.


Oh you mean that hacked up version of AOSP by slang-talking enthusiasts often missing the proprietary drivers needed to use things like 4G, GPS, and the device's camera? The one that includes the wallpaper with the scantily clad women in breast-exposing football outfits?

That ought to go well with the IT folks at the office.


There was some development since you looked at it. For example, that wallpaper is no longer in the builds by default ;).


I installed Cyanogenmod 6.0 final on my Evo this weekend. It was still in there at that time. Has something changed in the past couple days?


It is not in Cyanogenmod 6.0 final for Dream and Sapphire. It used to be in 5.0.x series.

Edit: Sorry, my bad, it is still there. The Cyanogenmod wallpapers section grew up in size and somehow I missed that the last wallpaper is still there.


People that felt this way should have purchased the Nexus One from Google while they were generally available. If more folks had, it might have validated the carrier-less model of selling phones.


It's hard for any company to try and work against the carrier-subsidized pricing of handsets. As long as carriers are supplying the access, this will continue to be the case.

To pay $500 for a phone, versus the $100 subsidized price, is a silly move—especially if you're planning to upgrade every 2-3 years.

I say this because the service from the carriers still costs the same regardless of how you obtained the handset, and in some cases you may be paying even _more_ for service if you don't have a contract.

(Of course, I'm speaking with the US/Canadian carriers in mind. I know things are better outside of North America.)


I say this because the service from the carriers still costs the same regardless of how you obtained the handset

T-Mobile's non-contract plans are $20 less per month, so over 2 years you save $480.


Are all the features accessible in non-contract plans?

I've got a few contract-only perks here in Canada on Rogers, such as the 6GB data plan add-on for $30/mo, and an "Employee Purchase Program" discounted voice service at $17/mo.

I don't think you can get non-contract data plans for under $30, and that only buys you 250MB/month, and voice plans start at around $25-30/month.

I may be able to set up a similarly-priced plan up here, but I would lose out on many of the important features (tethering, visual voice mail, larger data caps, free evening/weekend calling, etc.)


I did buy a N1 (gray import even). Too bad it has its hardware flaws: The touchscreen is really bad (choppy, inaccurate) and the button on my wired headset started working only rarely after two weeks of usage (sometimes the press isn't recognized, sometimes as "jump back" - and sometimes it even recognizes button presses even if there's no button on the headset).


Yeah. I've also got an N1, and the hardware flaws suck. The touchscreen is my biggest complaint, having previously used an iPhone. That said, I'm extremely pleased with it overall, and the lack of a carrier telling me what I can and can't do with it is surprisingly awesome.


My biggest issue with buying an unsubsidized phone is that I would still be paying the carrier a premium for subsidizing a phone purchase (to my understanding) without actually getting that benefit. (I guess there are other carriers, I have not actually bothered to look) In the end I just seem to be loosing about $400 or so since my phone bill remains the same, but I have to spend more to buy the phone.


Actually, as another poster already pointed out, with TMobile you don't have to pay the carrier a premium. They have a set of plans (called "Even More Plus") that are unsubsidized and are cheaper monthly.

Since the initial N1 model used the Tmobile 3G bands, it made a perfect match, and a great deal for anyone willing to do the math.


Apparently the author agrees with you, because he complains about "how sluggish some manufacturers are to release critical operating system updates for their devices." I'm curious to know how he reconciles that with the comment that you have quoted.




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

Search: