Android 2.1 Finally Makes It To Droid

← Back to Stories (view on slashdot.org)

Android 2.1 Finally Makes It To Droid

Posted by timothy on Wednesday March 17, 2010 @06:30AM from the for-all-your-robot-needs dept.

MrSmith0011000100110 writes "The lovely people over at AndroidCentral have broken the announcement that Android 2.1 is finally coming to the Motorola Droid, with actual proof on Verizon's Droid support page (PDF). I don't know about my Droid brethren, but I'm pretty excited to see the new series of Android ROMs for the Droid phone that are based on a stock Android 2.1. As most of us know, the existing 2.1 ROMs can be buggy as hell and either running vanilla 2.1 or a custom ROM; but this phone is still a tinkerer's best friend."

132 comments

Min score:

Reason:

Sort:

I am quite happy! by ircmaxell · 2010-03-17 06:34 · Score: 4, Insightful

I am quite happy about it! I LOVE my Droid, and the added features will be a welcome addition.

And no, I won't root it. Not because "I'm scared", but because I don't mess around with my primary device (I have a G1 and a ATT Tilt (HTC Tyan II) that are both rooted). If something goes wrong, I want the ability to drive directly to Verizon and get a new device without worry about "Crap, it's still rooted, let me get home and try to unroot it before taking it in"... Plus, I rely on it for daily use. So if for some reason it bricked, I'd be up the creak without a paddle...

--
If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
1. Re:I am quite happy! by GweeDo · 2010-03-17 06:55 · Score: 3, Informative
  
  Nandroid full backup of your stock 2.0.1 install. That is all you need. Something isn't working, just flash back to that and it will even rewrite your recovery image if you want it to. Verizon will never know.
  
  --
  Unstable Apps: Our Android Apps Don't Suck
2. Re:I am quite happy! by Anonymous Coward · 2010-03-17 07:08 · Score: 2, Funny
  
  And no, I won't root it. Not because "I'm scared", but because I don't mess around with my primary device (I have a G1 and a ATT Tilt (HTC Tyan II) that are both rooted). If something goes wrong, I want the ability to drive directly to Verizon and get a new device without worry about "Crap, it's still rooted, let me get home and try to unroot it before taking it in"... Plus, I rely on it for daily use. So if for some reason it bricked, I'd be up the creak without a paddle...
  So in other words, you're scared :)
3. Re:I am quite happy! by ThermalRunaway · 2010-03-17 08:12 · Score: 1
  
  Yes, but if you use nandroid, it't almost impossible to really be up a creek. Just backup your "clean" image and you can always get back. I'm played around with some 2.1 roms on my Droid and I love the new features.. but there are a few too many bugs to make me use it on a daily basis. I have a few roms on my SD and I just boot whatever I want at the moment to play around.
4. Re:I am quite happy! by Hurricane78 · 2010-03-17 08:19 · Score: 2, Insightful
  
  Has anyone noticed how bad it is, that you have something that is supposed do be an open source Linux-based phone, and you don’t even have root access right out of the factory?
  Even worse, not only do you have to root it with a hack, but you are also supposed to feel bad about it when returning it for broken hardware (which has nothing to do with modded software)?
  Sorry, but how can you stand something like that? I would never buy it, or be very very pissed.
  My Linux phone had root. I installed my own software, and various other packages. And it’s not only OK with the vendor. No, it’s even expected.
  (I’m not going to say which one, so I don’t sound like a retarded fanboi. But it’s pretty obvious which one it is, since it’s as far as I know the only one. ;)
  
  --
  Any sufficiently advanced intelligence is indistinguishable from stupidity.
5. Re:I am quite happy! by Threni · 2010-03-17 08:36 · Score: 1
  
  > Sorry, but how can you stand something like that?
  Exactly! I'd take one of the alternatives where that isn't a problem. For example the iPhone - Apple go out of their way to help you mod your phone and install whatever OS and software you like on it. Microsoft also provides many, many pages dedicated to showing you have to put Linux on your Windows Mobile device.
6. Re:I am quite happy! by nschubach · 2010-03-17 08:36 · Score: 2, Insightful
  
  I understand your sentiment, but let's be honest here for a second. If you want support, the best way to go about it is using "approved" versions of the software. I love Linux, but it makes it hard for a company to support. Now, they could insist on nandroid backups of the OEM system in order to support phones with root, but that's yet another system they have to support. For instance they could say, "Do with it what you like, but before returning it to the store for repair, run this to restore the default configuration."
  Hell, back when I did PC support, most OEMs insisted on this for even Windows builds. I'm sure we all remember the Packard Bell/Compaq/etc. system restore discs. They were more to ensure that the software wasn't the problem and it truly was a hardware issue. Most of them don't even help you today with Windows builds unless they are factory stock.
  
  --
  Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
7. Re:I am quite happy! by centuren · 2010-03-17 09:00 · Score: 2, Interesting
  
  Has anyone noticed how bad it is, that you have something that is supposed do be an open source Linux-based phone, and you don’t even have root access right out of the factory? Even worse, not only do you have to root it with a hack, but you are also supposed to feel bad about it when returning it for broken hardware (which has nothing to do with modded software)?
  I have indeed noticed something at least a bit...off about Android phones, but that something could easily be something I'm missing. Before I explain my situation, perhaps someone with more experience can enlighten me: what's the deal with carrier released Android ROMs? More specifically, is this news only to Droid users who haven't rooted their phone, or are Android phone owners really not able to upgrade their OS version without a carrier release?
  I've wanted an Android phone since the G1 was announced, more or less, but never could justify committing to the total cost of ownership (I get by with spending $10/mo on voice and ~$5/mo for 400 or so texts). Less than 6 months ago, I won a Samsung Behold 2 in an online giveaway (to my amazement). It's not the Android phone I would have picked by far, but it has enough of the hardware features one needs to use all the neat apps (touch, tilt, compass, gps, a rather nice camera, etc). Already being a T-Mobile customer, I put my existing sim card into the new phone, turned off all the wireless data conduits, and only use "network access" via WIFI (home, work, friends' places). I miss out on key things like maps and Internet outside where they can be most needed, but it works out well enough compared to the alternative of not having an Android phone at all.
  As many will know, the Behold 2 shipped with Android 1.5 or 1.6. I have looked into rooting it but haven't put any serious effort into it yet, primarily because I haven't come across information on upgrading the OS version. I understand the advantage to getting a ROM from a carrier (e.g. I'd really like my camera software to keep working properly), but I expected to go to http://www.android.com/ and find a "Download Android 2.1 Now" link, with general documentation about how one goes about installing Android on their supported device.
  All I find is the release notes and the SDK, which I've downloaded and used before with an emulator. If that's a path to upgrading my phone, I missed it (not having a phone at the time). If I have to root my phone before I can install / upgrade on that level, fine, just point me to a tangible Android 2.1 download I can use on my phone once I've rooted it. Since 2.1 is a big upgrade over 1.5/1.6, I'm not exactly going to be spending any money in the Android marketplace, since I don't know which weak points I want to replace are improved in the OS upgrade.
8. Re:I am quite happy! by Skuld-Chan · 2010-03-17 11:07 · Score: 1
  
  I suspect there is a lot of custom code/drivers for each specific handset model - while you can download the source to the android OS the expectation as an OEM is its your job to make it work on your device (kinda like the way Windows Mobile works actually).
  Not all android devices have phones in them, or cameras for that matter. There are some really stripped down models that are being marketed in Korea that have no touch screens either.
9. Re:I am quite happy! by mjwx · 2010-03-17 14:29 · Score: 1
  
  Nandroid full backup of your stock 2.0.1 install. That is all you need. Something isn't working, just flash back to that and it will even rewrite your recovery image if you want it to. Verizon will never know.
  Unless the keyboard dies.
  
  A better question is why should Verizon care, or be permitted to care. In Australia if there is a hardware fault on my Motorola Milestone (what the Droid is called in the ROTW) Motorola is required to repair it if I am still under the warranty regardless of what software is on it or if I have root access. But software faults in this case are my problem.
  
  I haven't rooted my Milestone and wont in the foreseeable future as I don't have a need to, unlike with my HTC Dream (G1 in the states) as the Australian carrier, Optus took 6 months to deliver the 1.5 update.
  
  BTW, how do you get Nandroid on there without Root? Also a restore to factory settings should re-load the original bootloader, at least it did with my Dream.
  
  --
  Calling someone a "hater" only means you can not rationally rebut their argument.
10. Re:I am quite happy! by El+Royo · 2010-03-17 15:21 · Score: 1
  
  You really should take a look at webOS. You don't need to root the device. You have root access available just by downloading the SDK. Everything is modifiable and easy to recover because Palm makes the OS images available for download. There's a really strong homebrew and patching community.
  
  --
  Author of Enyo: Up and Running from O'Reilly Media
11. Re:I am quite happy! by centuren · 2010-03-17 15:50 · Score: 1
  
  I suspect there is a lot of custom code/drivers for each specific handset model - while you can download the source to the android OS the expectation as an OEM is its your job to make it work on your device.
  At the moment, I'd be quite happy with the source. The developer site provides lots of helpful tools and documentation for developing "apps" for the Android platform (the version of which you include as a component in the SDK), but I can find little about producing my own custom ROM to experiment with on my phone.
  I suppose I probably have to just look through the SDK more carefully, if the workable source code isn't included in that download and I missed it, then I've no idea where it is. I haven't looked too deeply, but the SDK never gave me the impression it was for anything other than application development for Android (rather than Android development for my hardware).
12. Re:I am quite happy! by Hurricane78 · 2010-03-17 23:05 · Score: 0
  
  I understand your sentiment, but let's be honest here for a second. If you want support, the best way to go about it is using "approved" versions of the software.
  Again: Hardware support does have nothing to do with installed software!
  Just as it does not matter at all what OS I am using on my desktop PC (as opposed to my mobile pocket PC called “phone”), when one of the PCI cards fails!
  It’s a hardware error, you have to fix it, or I’ll sue you for selling me defective hardware.
  And if your software, using the same hardware interface, works, then it’s my problem if my chosen software doesn’t. Because software has nothing to do with hardware support.
  On the other hand, if you also offer software, and I chose to use your software, and it fails, then that’s an entirely different thing. Because then it’s like e.g. Autodesk offering a Linux version of Maya, and it not working with my hardware acceleration, despite me having the driver installed that should enable it. That either a configuration error on my side, or a software error on your side. In which case your support has to fix it.
  Yes, that makes it harder to support it. Well tough shit, cause that’s your freaking job on a open source platform.
  I write software for a bazillion of platforms. If I chose to support that platform, I have to support the difficulties that come with it. And so do you.
  Besides: Your whole argument is void, since Nokia is doing it already with the N900. So if you can’t that’s only your incompetence, and Nokia will swallow you alive. ;) Unless you man up and stand by, supporting, what you chose to sell to me.
  
  --
  Any sufficiently advanced intelligence is indistinguishable from stupidity.
13. Re:I am quite happy! by ircmaxell · 2010-03-18 00:55 · Score: 1
  
  It's a hardware error, you have to fix it, or I'll sue you for selling me defective hardware. And if your software, using the same hardware interface, works, then it's my problem if my chosen software doesn't. Because software has nothing to do with hardware support.
  You've hit the nail on the head. The reason most support companies want you to roll back to stock, is so that they can determine if the problem is truly hardware or if it's a driver/os issue... I had a problem with IBM and a server I was using. There was a bug in the motherboard that would cause excessive IO to lock the board under Linux (CentOS specifically). After working with a few friends that I have who have worked on the kernel team, it was determined that the only explanation was a faulty MOBO (More specifically, one that didn't behave according to standards). I called IBM, and they said that I'd have to recreate the problem under Windows Server or RHEL to be able to claim warranty. I tried Windows, and nothing happened (I found out later that Windows doesn't even use the bit of hardware that was causing the problem). I didn't want to shell out the $$$ for RHEL just to prove it was hardware, so I was stuck with a useless server (for CentOS at least). So we put Windows server on it, and re-purposed the box. Does it suck? Yes... Is it the end of the world? No (especially since we got a better deal on a better server for the project in question)... It's just the realities of support...
  
  --
  If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
14. Re:I am quite happy! by Anonymous Coward · 2010-03-18 02:10 · Score: 0
  
  as long as it fixes my issue of the phone locking itself while i'm in the middle of a phone call requiring me to unlock it just to hang up..
  then i'll be happy.
15. Re:I am quite happy! by Skuld-Chan · 2010-03-18 02:54 · Score: 1
  
  Source is right here:
  http://source.android.com/download
Already use DroidMod by Aequitarum+Custos · 2010-03-17 06:37 · Score: 2, Informative

which has all the features 2.1 has that I found useful Multi-touch + Picasa Gallery + Google Earth!
1. Re:Already use DroidMod by Mike+Buddha · 2010-03-17 07:10 · Score: 1
  
  The Picasa "integration" on 2.0.1 I found to be particularly aggravating. You can easily upload pictures to Picasa from your phone, but good luck trying to get a URL of one of your uploaded pictures(to link on a message board, for instance). That major oversight caused me to question Google's dedication to their platform. If they aren't building in support for their own applications, who do they expect to do that?
  
  --
  by Mike Buddha -- Someday the mountain might get him, but the law never will.
2. Re:Already use DroidMod by nschubach · 2010-03-17 07:46 · Score: 1
  
  One feature makes you question dedication?
  
  --
  Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
3. Re:Already use DroidMod by bemymonkey · 2010-03-17 18:51 · Score: 1
  
  So use Photobucket...
Re:What? by Pojut · 2010-03-17 06:42 · Score: 0, Offtopic

So what you're saying is that you are closed-minded, set in your ways, and enjoy being told what applications you can and can't use on your mobile device?
Wow...I'm so happy for you.

--
Living With a Nerd
Re:What? by ircmaxell · 2010-03-17 06:44 · Score: 1

Good for you! I don't use Windows either... And I don't use OSX. And since iTunes isn't supported on Linux, I can't use an iPhone or an iPod Touch or an iPad... Not that I'm really complaining (because I wouldn't use them anyway, but because I like the alternatives better)... Just because you like something better doesn't make it better (Then again, maybe I shouldn't feed the troll)...

--
If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
what is this "ROM" of which you speak? by Eunuchswear · 2010-03-17 06:46 · Score: 0

On my linux based phone I juat "apt-get update; apt-get upgrade"
None of this "ROM" or "flashing" nonsense.

--
Watch this Heartland Institute video
1. Re:what is this "ROM" of which you speak? by Sir_Lewk · 2010-03-17 06:48 · Score: 2, Interesting
  
  This is what happens when you bring linux to the masses. A perversion of terminology. Just one of the reasons I am not a linux evangelist.
  
  --
  "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
2. Re:what is this "ROM" of which you speak? by Lunix+Nutcase · 2010-03-17 06:55 · Score: 0, Offtopic
  
  And to be even cooler, why don't you whine about how people don't use "hacker" like the old 70s neckbeards did?
3. Re:what is this "ROM" of which you speak? by Mike+Buddha · 2010-03-17 07:12 · Score: 1
  
  And to be even cooler, why don't you whine about how people don't use "hacker" like the old 70s neckbeards did?
  "Hacker" is our word!
  
  --
  by Mike Buddha -- Someday the mountain might get him, but the law never will.
4. Re:what is this "ROM" of which you speak? by gd23ka · 2010-03-17 07:14 · Score: 1
  
  Love your sig, yes you are right on the money dude.
5. Re:what is this "ROM" of which you speak? by Mike+Buddha · 2010-03-17 07:18 · Score: 1
  
  So you can update your Baseband with apt? I'd didn't know it was capable of that.
  
  --
  by Mike Buddha -- Someday the mountain might get him, but the law never will.
6. Re:what is this "ROM" of which you speak? by BatGnat · 2010-03-17 08:05 · Score: 1
  
  my linux based phone is an Android based phone
7. Re:what is this "ROM" of which you speak? by Anonymous Coward · 2010-03-17 08:27 · Score: 0
  
  Yeah, that sounds like a ridiculously easy way to administer a phone.
8. Re:what is this "ROM" of which you speak? by Sir_Lewk · 2010-03-17 08:32 · Score: 1
  
  He isn't disaproving of the technology, he is disapproving of the terminology (which sounds suspiciously like the terminology used in the 'warez' scene...).
  
  --
  "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
9. Re:what is this "ROM" of which you speak? by violasvegas · 2010-03-17 08:32 · Score: 1
  
  Yeah, because THAT's the important thing, making sure you get to keep all of your super cool lingo pristine. Forget about bringing useful technology to people who could use it. How can that possibly make anything better?
10. Re:what is this "ROM" of which you speak? by Anonymous Coward · 2010-03-17 08:34 · Score: 0
  
  This is an embedded device dude, you can't just apt-get update the kernel. Somehow I doubt you even have a linux based phone.
11. Re:what is this "ROM" of which you speak? by AndrewNeo · 2010-03-17 08:35 · Score: 1
  
  When dealing with Android phones:
  ROM = A zip file containing system update files that will be added/replaced and scripts that perform the upgrade.
  Flashing = Extracting the update file and running the shell scripts.
  People just use the same terminology as regular cell phones when it comes to this stuff. You're not overwriting the (whole) NAND when you flash and there's nothing "read only" about it (after the /system partition has been mounted rw, for 'flashing', that is.)
12. Re:what is this "ROM" of which you speak? by Sir_Lewk · 2010-03-17 08:52 · Score: 1
  
  Pervasions of terminology are not to be taken lightly. Jargon facilitates effective communication among members of a field and using it improperly does nothing but needlessly fragment the community and stiffle progress.
  Your attempts to spread linux to people that do not care enough to actually learn about it will backfire in your face... and annoy the hell out of the rest of us.
  
  --
  "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
13. Re:what is this "ROM" of which you speak? by Threni · 2010-03-17 08:54 · Score: 1
  
  You could always go here:
  http://www.cyanogenmod.com/
  And give this "Cyanogen" character a piece of your mind - he clearly doesn't know what he's talking about.
14. Re:what is this "ROM" of which you speak? by Anonymous Coward · 2010-03-17 09:01 · Score: 0
  
  Yes. Yes you really can.
  Fuck, I just did it last weekend. Somehow I really doubt you have ever used a real linux system.
15. Re:what is this "ROM" of which you speak? by Anonymous Coward · 2010-03-17 09:09 · Score: 0
  
  DEY DOOK OUR WERD!!!
16. Re:what is this "ROM" of which you speak? by Anonymous Coward · 2010-03-17 09:28 · Score: 0
  
  DURK ORR WUURRK
17. Re:what is this "ROM" of which you speak? by Eunuchswear · 2010-03-17 20:25 · Score: 1
  
  Love your sig, yes you are right on the money dude.
  What, in pointing out that ESR is a paranoid lunatic? (who doesn't know the difference between IDL and Fortran).
  
  --
  Watch this Heartland Institute video
18. Re:what is this "ROM" of which you speak? by seandiggity · 2010-03-19 06:33 · Score: 1
  
  Your attempts to spread linux to people that do not care enough to actually learn about it will backfire in your face... and annoy the hell out of the rest of us.
  Cuz, um, having multitudes of Windows and Mac users that don't know the technical terminology is a good alternative? Let's just go back to the days of time-sharing systems in locked rooms because most users don't care about what's inside the shiny box on their desk or in their hands. Some users will learn about their systems, others won't, but that's no reason to keep FOSS software from the "unwashed masses". Why would we want to establish/reinforce a culture of technocrats vs. n00bs? Elitism is completely counter to the goals of free software, for reasons that should be obvious. And, btw, the Wikipedia article on ROM is just a click away thanks to a commitment to education and diffusion of information, not snobbery.
  
  When I was a kid, I thought ROM was just a spaceknight, but I seem to have gotten past it...
  
  --
  Geeks like to think that they can ignore politics, you can leave politics alone, but politics won't leave you alone.-rms
Too bad it won't work in Canada by i_ate_god · 2010-03-17 06:51 · Score: 2, Interesting

Unless you're with CDMA Telus or WIND which only exists in two cities. Otherwise, all the other networks are AT&T compatible which means no Droid, Nexus One, or N900 for me, the three phones I want to replace my iPhone with.

--
I'm god, but it's a bit of a drag really...
1. Re:Too bad it won't work in Canada by ThatFunkyMunki · 2010-03-17 07:02 · Score: 1
  
  Um, at&t compatible means it uses GSM. N900 and Nexus 1 both are unlocked and use GSM. You can easily use them on your network without any problems. Droid is CDMA so you cant use that one but 2/3 is OK, right?
  
  --
  If patriotism is racist, is racism patriotic?
2. Re:Too bad it won't work in Canada by ajlitt · 2010-03-17 07:02 · Score: 3, Informative
  
  Today is your lucky day: N1 for 3G 850/1900/2100
3. Re:Too bad it won't work in Canada by vio · 2010-03-17 07:03 · Score: 1
  
  Actually N1 for ATT/Rogers was released a couple of days ago, so that's an option now. N900 works fine on any GSM network (but no 3G).
  The "Canadian" TELUS Milestone (Droid) seems to have been rooted, but still no news on custom ROMS (or official 2.1 updates for that matter). I expect it'll arrive eventually though (and the Milestone can be used on all 3 networks).
4. Re:Too bad it won't work in Canada by malefic · 2010-03-17 07:05 · Score: 1
  
  The Milestone offered by Telus is the DROID using GSM. I have it and I'm quite pleased with it. The only thing I want to know about 2.1 is whether they fixed voice calling via bluetooth.
5. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 07:05 · Score: 0
  
  IIRC, Rodgers is going to have a Nexius One that works with the 3g
6. Re:Too bad it won't work in Canada by Mike+Buddha · 2010-03-17 07:15 · Score: 1
  
  The Milestone (aka Droid in UK) is GSM. I don't think it has AT&T 3G frequencies, though, so you'd be stuck in 2G mode, but that's the same as the N900. You can use 3G on the N900 but only on T-Mobile's network (aka the only US network that's more anemic than AT&T).
  
  --
  by Mike Buddha -- Someday the mountain might get him, but the law never will.
7. Re:Too bad it won't work in Canada by Lunix+Nutcase · 2010-03-17 07:19 · Score: 1
  
  Except that all the phones would be limited to 2g/Edge as AT&T is incompatible with the 3g bands. I'm pretty sure if he wants to go to a Nexus One, Droid or N900 he would want 3g.
8. Re:Too bad it won't work in Canada by shutdown+-p+now · 2010-03-17 07:37 · Score: 2, Informative
  
  Motorola Milestone is a GSM variant of DROID that's offered in Canada. So far exclusive to Telus, though.
  And yesterday, Google has released a variant of Nexus One that works on AT&T 3G frequencies in U.S., which means that it also works in Canada. And, yes, they do ship to Canada. You can only order an unlocked one online, though, not subsidized via any operator.
9. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 07:45 · Score: 0
  
  Apparently you missed the announcement yesterday that the Nexus one will work in Canada on Rogers, Telus and Bell
  http://www.vancouversun.com/technology/Google+releases+Nexus+smartphone+Canada/2693212/story.html
10. Re:Too bad it won't work in Canada by i_ate_god · 2010-03-17 07:58 · Score: 1
  
  As several others have pointed out, this is quite interesting.
  So now my question is: what's more hackable: N900, Nexus One, or jailbroken iPhone (which allowed me to do, amongst other things, write my own apps in Python).
  
  --
  I'm god, but it's a bit of a drag really...
11. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 08:08 · Score: 0
  
  http://www.theglobeandmail.com/blogs/globe-on-technology/nexus-one-now-available-in-canada/article1502169/
12. Re:Too bad it won't work in Canada by GreenEnvy22 · 2010-03-17 08:10 · Score: 1
  
  Google recently released Nexus one that supports Rogers 3G networks, and it is available for Canadians to buy, there is also a version for Wind. Bell/Telus can't run the Nexus one yet though.
13. Re:Too bad it won't work in Canada by ezesolares · 2010-03-17 08:13 · Score: 1
  
  sadly, the milestone bootloader is signed, so no custom roms for milestone users... we tried to talk to motorola but they just dont give a crap about us (srsly.. check the european milestone facebook page).
14. Re:Too bad it won't work in Canada by ezesolares · 2010-03-17 08:21 · Score: 1
  
  Thats a lie that motorola made us belive and i bought it beliving it.. the milestone is a locked version of the droid. Has a signed bootloader so we cannot load custom roms... check europe motorola facebook page...
15. Re:Too bad it won't work in Canada by Hurricane78 · 2010-03-17 08:22 · Score: 1
  
  Wait. The N900 definitely is compatible with American networks. So shouldn’t that make it compatible with AT&T networks too?
  
  --
  Any sufficiently advanced intelligence is indistinguishable from stupidity.
16. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 08:27 · Score: 1, Informative
  
  Milestone is not only the gms version of the droid.. is the locked version with a signed bootloader. we cannot run custom roms and motorola we told motorola about it and they just dont care about it.
  https://supportforums.motorola.com/thread/22962?tstart=0
17. Re:Too bad it won't work in Canada by shutdown+-p+now · 2010-03-17 08:37 · Score: 1
  
  If you want a hackable Android phone, it would seem that Nexus One remains the best bet, anyway.
18. Re:Too bad it won't work in Canada by AndrewNeo · 2010-03-17 08:38 · Score: 1
  
  Well, the bootloader on the Droid is supposed to be signed, but there was a bug in the source code (patch) that let people sneak modified updates through. There's a good chance the official 2.1 bootloader will close this hole, since the patch has been merged already.
19. Re:Too bad it won't work in Canada by js3 · 2010-03-17 08:41 · Score: 1
  
  Google recently released Nexus one that supports Rogers 3G networks, and it is available for Canadians to buy, there is also a version for Wind. Bell/Telus can't run the Nexus one yet though.
  Yes they can http://www.cbc.ca/technology/story/2010/03/16/google-nexus-canada.html
  "A spokesperson for Telus confirmed the Nexus One would work at full 3G speeds on the company's — and Bell's — network without any problems.
  The AT&T and Rogers version uses the 850 and 1900 megahertz frequencies, which are in the same bands used by Bell and Telus's new network.
  "If you have a Nexus One, bring it to us and we'll give you a SIM card for $9.99 and off you go," said a manager at a Toronto Telus store.
  Read more: http://www.cbc.ca/technology/story/2010/03/16/google-nexus-canada.html#ixzz0iT6s1ryc
  "
  
  --
  did you forget to take your meds?
20. Re:Too bad it won't work in Canada by ezesolares · 2010-03-17 09:08 · Score: 1
  
  Nexus one is not sold in my country and thats not the point, they sold us the droid experience with another name and they blantly lied to us... and we need to be able to run custom roms since our cel company dont give a rat ass about us (telecom personal - argentina). We are still waiting for them to make the 2.0.1 version available here
21. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 09:54 · Score: 1, Interesting
  
  It should be observed that they'd best not do that- it's not going to be in keeping with their rights obligations with respects to the Linux kernel that Android's based upon.
  Seriously, I'd have thought that Motorola would have figured this one out, after pretty much everyone watched what'd happened with Verizon and Actiontec over breaking the GPL licensing like this. This would be a bigger and nastier breach than the Actiontec one- and Actiontec and Verizon CAVED once it got to an actual lawsuit.
22. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 10:28 · Score: 0
  
  The N900 is more hackable, but less usable. That's the tradeoff between Maemo/Android/iPhone - user friendliness vs. geek friendliness. Me, I prefer the middle ground that Android offers.
23. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 12:43 · Score: 0
  
  nah, some folks from a forum talked with a guy whos into gpl and laws.. and since they r giving back their kernel modifications, they r not breaking the gpl v2. there is no part in the kernel licensing that say that u should be able to run your own custom rom(based on their changes) on their hardware.
24. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 12:55 · Score: 0
  
  Except any sane person would rather poke their eyes out with a rusty nail than deal with Telus. It's a lot less painful.
  Telus sucks - it's true.
25. Re:Too bad it won't work in Canada by Anonymous Coward · 2010-03-17 15:13 · Score: 0
  
  How about the Mot Milestone? It's the GSM droid.
26. Re:Too bad it won't work in Canada by Nursie · 2010-03-17 19:51 · Score: 1
  
  More hackable?
  N900 every time. Comes with a terminal program and busybox installed. Getting root is as simple as installing the rootsh pacakge from the app manager.
  It's awesome :)
Re:What? by Anonymous Coward · 2010-03-17 06:56 · Score: 0

Good for you! I don't use Windows either...
I'm happy to hear that. I don't care if you don't use Mac OS X or iTunes either, as long as you're not helping Microsoft's stronghold on the computer OS.
Help... by sbeckstead · 2010-03-17 07:09 · Score: 1

Ok I'm about to start Android development, what version should I develop for? There seem to be about 4 different versions of the SDK? Are all the phones at 2.1 now?

--
Why bother
1. Re:Help... by loconet · 2010-03-17 07:14 · Score: 2, Informative
  
  Knowing is half of the battle.
  
  --
  [alk]
2. Re:Help... by Anonymous Coward · 2010-03-17 07:17 · Score: 0
  
  First of all, -1, offtopic. Or maybe you're trolling, but I'll bite.
  Secondly, no.
  You'd hit the vast majority if you target 1.6, but not necessarily everyone.
3. Re:Help... by sbeckstead · 2010-03-17 07:18 · Score: 1, Troll
  
  Cool, a blog.. thanks...
  
  --
  Why bother
4. Re:Help... by sbeckstead · 2010-03-17 07:20 · Score: 1
  
  Excuse me it is at least a little on topic, a phone get's upgraded to a new version and it's apparently news. So I ask a question related to phones being upgraded. Thanks for the reply, I'll uninstall the 2.0 version I just installed and go back to 1.6.
  
  --
  Why bother
5. Re:Help... by Anonymous Coward · 2010-03-17 07:20 · Score: 0
  
  Are all the phones at 2.1 now?
  http://developer.android.com/resources/dashboard/platform-versions.html
  That's two months old, but the answer to your question is still no.
  
  what version should I develop for?
  The lowest version that supports the features you need. If you can accomplish your purpose with the features in the 1.5 SDK, use that. If not, move to a newer one. You'll set a "minSDK" attribute in your project that will limit your application to only those devices that will support it.
6. Re:Help... by GweeDo · 2010-03-17 07:23 · Score: 3, Insightful
  
  A blog link that answers your question. If you target 1.5, you will cover 99%+ of the users with Android phones. The best bet is to decide what features your app needs. Then target the lowest API version that allows for that.
  
  --
  Unstable Apps: Our Android Apps Don't Suck
7. Re:Help... by The+Moof · 2010-03-17 07:23 · Score: 1
  
  This might be a little more helpful. The blog was just regurgitating this page, but was out of date anyway.
8. Re:Help... by sbeckstead · 2010-03-17 07:24 · Score: 1
  
  OK makes sense, but..
  http://developer.android.com/resources/dashboard/platform-versions.html
  wasn't too helpful. The previous answers were actually clear and useful something that sometimes lack on /. Thanks for the minSDK thingy though, I'll look it up.
  
  --
  Why bother
9. Re:Help... by tweek · 2010-03-17 07:39 · Score: 1
  
  Androidguys has an awesome series about android development. Ignoring the version issue for a moment, the other aspect that can cause "issues" is being a responsible multitasked process and screensize. They have articles on those specifically:
  http://www.androidguys.com/category/ag-originals/building-droids/
  But back to the version information, 1.5 is the base version on any device out today but pretty much everything out there will be getting upgraded to at least 2.0. 2.1 is almost a feature set upgrade for 2.0 as opposed to a different release. I think a good rule is if you're developing something simple and "stupid" like a fart app, go 1.5. Gaming? Go 2.0+ (and look at using the NDK for that matter). Productivity I'd go 1.5 to reach the widest audience.
  
  --
  "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
10. Re:Help... by loconet · 2010-03-17 07:43 · Score: 1
  
  Yah the official "blog" for android.com developers hosted through blogspot. I guess if you had bothered to actually read where you were, you would have known that.
  
  --
  [alk]
11. Re:Help... by Volante3192 · 2010-03-17 07:51 · Score: 1
  
  If you want to rub even more salt in his wound, point out that Google owns Blogspot!
12. Re:Help... by sbeckstead · 2010-03-17 09:51 · Score: 1
  
  what wounds, I sincerely thanked the guy for pointing me at the blog (didn't come up anywhere near the top in my Google search the other night) and I get marked a troll. I know blogspot is owned by Google I have a blogspot blog myself.
  
  --
  Why bother
13. Re:Help... by sbeckstead · 2010-03-17 09:53 · Score: 1
  
  Wow, you get insightful for pointing out what the other guy pointed out in less words. And I get a troll for thanking him. I'd say thank you to you as well but I would probably get modded down again.
  
  --
  Why bother
14. Re:Help... by sbeckstead · 2010-03-17 09:55 · Score: 1
  
  Thank you. Oops last time I said that I was marked a troll. Aw well.
  
  --
  Why bother
15. Re:Help... by Svartalf · 2010-03-17 10:06 · Score: 1
  
  Depends on your application. Pick the lowest one that supports what you need out of the API edges for the application. For the applications I'm writing right at the moment, that would be 1.5 or later since they've got OpenGL ES 1.1 support (at minimum) available if the vendor making the device licensed the driver stack from the respective GPU vendors sitting in the SoC's in use (So far, I've not seen an Android that had a decent 1.1 GPU not have the drivers licensed for them...).
  As long as you're not hitting an API breakage (It's my understanding that there's none with 1.5 going forward...) the app should just simply work.
  
  --
  I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
16. Re:Help... by GweeDo · 2010-03-17 10:28 · Score: 1
  
  Your thanks sounded a bit sarcastic. I took it as you were upset he linked you to a blog.
  
  --
  Unstable Apps: Our Android Apps Don't Suck
17. Re:Help... by BertieBaggio · 2010-03-17 12:00 · Score: 1
  
  Don't take this the wrong way; it is intended to help you convey meaning better. That said: think about how you phrase your sentences. The way you typed it it sounds as though you are being hesitant and, well, insincere. I'm sure your intention was to sincerely thank him.
  
  Cool, a blog.. thanks...
  is only one (albeit important) step away from:
  
  Gee... a blog... thanks.
  Without the nuance of spoken words it can be difficult to gauge tone and intent. Why did you use the trailing periods / ellipses ("...")?
  
  --
  If all you have is a grenade, pretty soon every problem looks like a foxhole -- MightyYar
18. Re:Help... by Anonymous Coward · 2010-03-18 01:48 · Score: 0
  
  quit karma whoring
  
  you were being a sarcastic ass to someone who was helpful to your stupid LMGTFY question. when you got called on it you started whimpering all over the thread over the troll mod. is the karma hit from one downmod so important to you? damn, i wish i had points right now so i could drop all 15 on downmodding your posts. little fuckin bitch.
19. Re:Help... by sbeckstead · 2010-03-18 04:58 · Score: 1
  
  No the karma hit is irrelevant, but the courtesy of not assuming (remember what happens when you ass u me) my sarcasm. So now I'm an ass and u are too. But thank you for pointing out that it did sound a bit whiny. Sorry about that. I'll try harder to convey my spite or appreciation in the future without leaving it open to interpretation. Oddly enough, the people who answered my question did so without assuming I was trolling (well except for one guy but he gave useful info anyway) it seems that not all people on /. are as sensitive to whining as you are. Oh and actually used their real names. Anonymous idiots abound here because they want the privilege of commenting and moderating so I'm told.
  
  --
  Why bother
20. Re:Help... by Anonymous Coward · 2010-03-18 06:28 · Score: 0
  
  Actually, you didn't say "Thank you"...
  You said "Cool, a blog.. thanks..."
Re:What? by sbeckstead · 2010-03-17 07:11 · Score: 2, Informative

I use Mac OS because it's cool and I like to use it. I use Windows cause it pays the bills. I use Linux because it's a neat hacker OS and it's cool too. But Windows still pays the bills. I'm working on fixing that but until we switch I'm stuck.

--
Why bother
What is this "apt" of which you speak ? by Anonymous Coward · 2010-03-17 07:29 · Score: 0

On my google nexus one phone, new updates just silently gets downloaded in the background, and i am then asked, with a nice yes/no window if i want to apply it or not.
none of this apt typing nonsense!
Bitchin Bagle is where it's at. by gimmebeer · 2010-03-17 07:31 · Score: 1

I'll update my phone to 2.1 when there's a root hack and the Sholes guys put out a ROM. Sholes includes must have stuff like wireless tethering and more than 3 screens. Not to mention overclocking....
1. Re:Bitchin Bagle is where it's at. by Anonymous Coward · 2010-03-17 07:51 · Score: 0
  
  I need a root hack just to use wifi at work (certificates). At least with 2.0 I do, maybe 2.1 supports more complex wifi setups.
2. Re:Bitchin Bagle is where it's at. by nschubach · 2010-03-17 07:55 · Score: 2, Informative
  
  FYI, the SholesMod guys moved onto DroidMod. Not sure if you followed any of that.
  
  --
  Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
Flash? by sycorob · 2010-03-17 07:35 · Score: 1

So Flash 10 obviously isn't in this update. Has anybody heard any recent news on when this would be available? Last I heard, it was supposed to come out end of 2009 ...
1. Re:Flash? by nschubach · 2010-03-17 07:56 · Score: 1
  
  The first, and last, I heard was first half of 2010. I've never heard anyone say end of 2009.
  
  --
  Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
2. Re:Flash? by BatGnat · 2010-03-17 08:08 · Score: 2, Informative
  
  They back-tracked and said that full flash ten will only work on phones that have an ARM v7 Cortex processer, so only newer phones get it (Droid, N1)
  http://www.androidauthority.com/index.php/2010/02/26/adobe-flash-10-will-not-support-first-generation-android-devices/
3. Re:Flash? by AndrewNeo · 2010-03-17 08:42 · Score: 1
  
  And yet, this article is about the Droid, making your statement irrelevant?
4. Re:Flash? by BatGnat · 2010-03-18 08:35 · Score: 1
  
  Is that a question, or a statement? I Cant tell because you put a question mark on the end.
5. Re:Flash? by BatGnat · 2010-03-18 08:37 · Score: 1
  
  It must have been a question.
Re:What? by Anonymous Coward · 2010-03-17 07:48 · Score: 0

wait, you didn't say you use Linux or don't use Linux - just that you can't use an iPhone or an iPod Touch or an iPad
Tinkerer's best friend? by Anonymous Coward · 2010-03-17 07:58 · Score: 0

Have you heard about Nokia N900? That's the true tinkerer's best friend.
Re:What? by BatGnat · 2010-03-17 08:02 · Score: 1

Commodore 64?
Super. by nine-times · 2010-03-17 08:05 · Score: 5, Interesting

I'm glad to see this. I'm a current iPhone user, but I'm considering moving to an Android phone. One of the things that has kept me from taking the plunge is the perception that the Android market is fragmented and manufacturers aren't bothering to update their existing models with the most advanced version of the OS available. I don't know if that's a reality, but that's my perception.
So what worries me is that I'll buy a Droid (or whichever model) and some feature will be buggy. The problem will be fixed in an OS update, but that update won't ever make it to my phone. Or some great new application will be released, but it won't work on my phone because I can't upgrade the OS.
I'm not a big fan of Apple's tight control over application distribution, but at least they're keeping things pretty compatible and offering free upgrades to their newest OS version. If Motorola can show that they'll keep these things up to date, maybe I'll make the switch.
1. Re:Super. by GooberToo · 2010-03-17 11:06 · Score: 1
  
  Five versions of Android were released last year (1.1, 1.5, 1.6, 2.0, 2.01). Furthermore, Verizon's Droid also has their own subtle incompatibilities with 2.0 and 2.01. Almost all releases had incompatibilities with each other and caused problems for various applications - including fully compliant applications. Really, the biggest problem is Google has created the world's biggest headache for developers to properly support their customers - for an *extremely* long list of reasons.
  Regardless, in a nut shell, Google has stated they intend to bring all current Android devices to 2.1. World wide, some carriers have indicated they'll resist the migration. AFAIK, no US carriers have signaled this reluctance. Overall, 2010 is looking to be the year of Android.
2. Re:Super. by Anonymous Coward · 2010-03-17 11:14 · Score: 1, Informative
  
  I had the same worries before I switched. Sadly some of what you mention is reality. The market is fragmented and apps that exist for one phone may not exist or work for another. The other thing I've found is that apps that do exist on both phones, trapster for example, have a shadow of the functionality on the moto droid as they do on the iphone. Some of this may be technical but some of it is definitely not. The player really makes me miss itunes smart playlists and ability to manage the files.
  With that said, I don't miss the conformist attitude that the iphone presents. I jailbroke for very few reasons. Five Icon dock, tether and categories. Apple could easily satisfy the aesthetics part of my wants but refuses to do so. AT&T won't officially allow tether. It's too troubling to mess with so now I've got a droid and love the freedom it presents.
3. Re:Super. by jmrives · 2010-03-17 11:21 · Score: 1
  
  You could buy a Nexus One directly from Google. There's a good chance they will keep it up-to-date with regards to the OS. Of course, you would have to use T-Mobile service. Not sure if that matters to you.
4. Re:Super. by dudpixel · 2010-03-17 14:20 · Score: 1
  
  meh - I dont understand all of this. Are you speaking from experience or are you quoting all of the FUD that exists on the net about this? I cant understand how one device (nexus one) can work well with 2.1 and another can be buggy, and yet its somehow the a fault of android. To me, if 1 phone works well with android, they all should - otherwise its a manufacturer fault (faulty hardware and/or drivers).
  I've got a HTC magic - still running 1.6 and I've yet to come across any of these supposed incompatibilities.
  I've browsed the Android Market a lot and I'm not sure what you mean by "fragmentation". There's just a lot of apps - I only use the ones with high ratings, and give feedback where its necessary. Its a great self-sustaining model, and it "works for me".
  The API's are all (supposed to be) forward-compatible. If something breaks - it should be a fault of the app developer. The only exception is if there is a bug in the API implementation - but this would be evident across all phones which support that API.
  As far as the API model goes, I cant see a problem with it. As long as google implements it properly - there should be no issue. All software written for 1.5 should work on 2.0 and 2.1 without a hassle. I've certainly not had any issues with stuff not running properly.
  I've also developed my own app and I'm really impressed by the SDK and also how well the app performed on my phone.
  i've never experienced any incompatibilities on my phone. maybe i'm just lucky?
  
  --
  This seemed like a reasonable sig at the time.
5. Re:Super. by mjwx · 2010-03-17 14:48 · Score: 1
  
  I'm glad to see this. I'm a current iPhone user, but I'm considering moving to an Android phone. One of the things that has kept me from taking the plunge is the perception that the Android market is fragmented and manufacturers aren't bothering to update their existing models with the most advanced version of the OS available. I don't know if that's a reality, but that's my perception.
  
  And that's exactly what it is a perception, most oft parroted by the fanboys opposing Android. Just like with Windows, the update to XP SP2 broke compatibility with programs that relied on hacks but not most programs. Backwards compatibility with Android software is quite good, I had no problems with 1.5, 1.6 on my dream and 2.0 and 2.01 on my Milestone. The marketplace generally wont show you software that is incompatible and wont run.
  
  So what worries me is that I'll buy a Droid (or whichever model) and some feature will be buggy.
  The Droid has been out long enough that you could tell if this is the case. Early adopters have problems (remember when the Iphone was released, or Vista), to avoid this don't be an early adopter. That way you can be more informed when buying a product. Also android updates are not forced on you, you have to consciously agree to install it.
  
  Motorola have committed to the next version of Android (2.5?). With the delivery of 2.1 in a fairly timely manner I think moto are keeping their end of the bargain, if they don't there are always custom ROMs.
  
  --
  Calling someone a "hater" only means you can not rationally rebut their argument.
6. Re:Super. by Anonymous Coward · 2010-03-17 14:54 · Score: 0
  
  The HTC Magic in Australia won't be upgraded. I asked Vodafone about it when I got my phone and the service guy didn't know what Android was...
  Get a job. Get a N-1
7. Re:Super. by nine-times · 2010-03-17 16:54 · Score: 1
  
  If the problem is that Google has created a headache for developers, that doesn't make me want to buy one of these things. Regardless, I've had enough dealings with carriers and cell phone manufacturers to doubt that they're innocent in delaying upgrades.
8. Re:Super. by nine-times · 2010-03-17 16:56 · Score: 1
  
  Or AT&T. (link)
  Of course, getting the unlocked version means that it's not subsidized by the carrier. I'm not sure how much that bothers me.
9. Re:Super. by Anonymous Coward · 2010-03-17 16:56 · Score: 0
  
  Now if only they'd quit sitting on their thumbs and actually fix the hands-free headset initiated voice dialing instead of just flagging it disabled in the OS since 1.5 and claiming it'll be fixed instead of an outstanding issue nearly a year later.
10. Re:Super. by bemymonkey · 2010-03-17 18:57 · Score: 1
  
  I've browsed the Android Market a lot and I'm not sure what you mean by "fragmentation". There's just a lot of apps - I only use the ones with high ratings, and give feedback where its necessary. Its a great self-sustaining model, and it "works for me".
  You're aware that ideally, apps flagged not to work on your phone model (or OS) don't even show up in the Marketplace, right? You could be looking at a ton of fragmentation and not even know about it.
11. Re:Super. by GooberToo · 2010-03-18 00:56 · Score: 1
  
  meh - I dont understand all of this. Are you speaking from experience or are you quoting all of the FUD
  
  Really? I just explained, what is in its own right, a major headache, and you're complaining about FUD? Your middle name is either "Bullshit Artist" or "FUD Master". Of those OS numbers which were released last year, 1.0 and 2.0 have been declared obsolete. That still leaves 1.5, 1.6, 2.01, and 2.1 to validate and test against. And in order to ensure proper functionality, many developers forced to either target a subset of OSes, or bring with their application chucks of the OS. Watch logs sometimes when you're installing applications - often you'll see a long list of OS functions which are replaced internally by the application. That's because the application includes them as they are not reliable across all OS versions.
  No FUD needed - just fact.
  
  I've got a HTC magic - still running 1.6 and I've yet to come across any of these supposed incompatibilities.
  Try speaking with actual developers. I know, how odd - talk to someone who actually knows. Or, try developing an actual, non-trivial application on the platform. This is not to say every application suffers. Additionally, the older the OS, the less likely you are to experience compatibility issues. Version 1.6 has been out for a while now so compatibility issues have long been resolved. You're position is like staring at a wall and saying, "I can't see traffic on highways, therefore it doesn't exist."
  
  The only exception is if there is a bug in the API implementation
  
  There has been plenty of bugs in the OS. Additionally, some API's have been deprecated and some have been obsoleted. The fact you don't know this further validates you're clueless on the subject matter. Furthermore, I know of at least one incompatible change made in 2.0, and carried forward to 2.1, which is in place strictly to break applications.
  
  As far as the API model goes, I cant see a problem with it. As long as google implements it properly
  As far as the API model goes, all versions previous to Android 2.1 have a serious service life cycle bug. That's per Google themselves - and contrary to their assurances, its still doesn't completely fix the problem. Additionally, the requirement for introspection is becoming standard fair. That's a sure sign of incompatibilities and breakage. Go read the docs already, not to mention Google's Android developer blog. As a side note, this bug is so serious (wastes lots of memory and slows device), IMOHO, that's why Google is pushing to get everyone to 2.1. Additionally, getting everyone to 2.1 will go a long ways to easing the support headache Google has created for developers.
  Don't get me wrong, I love Android, but to pretend its perfect is nothing short of idiotic. Realistically, there has been many, many problems and they've done a very poor job of taking care of developers as a whole; though phone give-aways are certainly nice.
  Since you obviously just want to Rah-Rah as a fan boy, and have no idea what you're talking about, don't expect another reply. In stead of sticking to your guns, might I suggest you actually go learn the facts first hand.
12. Re:Super. by MogNuts · 2010-03-19 01:52 · Score: 1
  
  That's great and all, but at the end of the day, it's what's provided to the end-user that matters. An Android phone is better. The second you do anything with your IPhone, and you're in an IM or in a web browsing session, or *actually* using an app that doesn't *just* make fart noises, you'll curse your beloved IPhone when you have to suspend the program to do something else, then re-login, navigate back, and go through all hoops just to get back to where you left off--for EVERY LITTLE THING. Multi-tasking is king, and your toy of an IPhone doesn't cut the mustard.
  And no, you *don't* know that the IPhone OS 4.0 will have multi-tasking.
  You lose! Try again.
13. Re:Super. by GooberToo · 2010-03-19 04:18 · Score: 1
  
  You lose! Try again.
  LOL! What a douche!
  I have an android phone. I've never owned an iPhone. Re-read what I said. Everything is factually accurate.
  Though honestly, I can't disagree with anything you said in your phone comparisons. Simply put, Android is a superior solution to the iPhone. Android even has higher end hardware available now and is far more likely to get next generation wireless technologies before the iPhone simply because its available on so many carriers and from so many more manufacturers.
  
  it's what's provided to the end-user that matters.
  Yes and no. The long list of problems, of which I outlined a very short list, is the major reason so many developers have either decided to pass (for now) on Android and or stopped developing on Android (yes, many have left Android). This means end-users are getting fewer quality applications. Right now Android has something like 30k apps available on the market. Of those, maybe 6k are worth consideration. Of those, maybe a couple hundred are really top notch, high quality applications.
  Additionally, the service bug I described absolutely does affect end users and is one of the reasons why so many users feel the need for applications, like Task Killer, are required.
  So please, grow up. As I previously said, Android isn't perfect and anyone who believes otherwise is an idiot. The sooner people like you stop acting like an idiot and start supporting your developers, the sooner EVERYONE involved with Android will benefit. Right now, your blind, idiotic, position is only helping to hinder developers. Stop being a problem and start supporting your developers.
14. Re:Super. by MogNuts · 2010-03-21 03:29 · Score: 1
  
  I re-read your OP. Now I see what you are saying. I apologize. I'm just tired of /. being filled with so many loser fanboys quoting the same old FUD and any slighting of their Jesus phone/Apple Jesus product/etc. meets with millions crying out with "But-but-but Apple :
  doesn't need multitasking!"
  doesn't need MMS!"
  doesn't need to make calls, because who buys a phone to call anymore!"
  So I stopped filtering my gut reaction comments.
G1 replacement yet? by Anonymous Coward · 2010-03-17 08:52 · Score: 0

Is there a decent G1 replacement out yet? I want a Nexus One with a physical keyboard that works on T-mobile
1. Re:G1 replacement yet? by Svartalf · 2010-03-17 10:16 · Score: 1
  
  If you can find an unlocked BackFlip, you'd be in the right ballpark.
  
  --
  I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
Not really news by Anonymous Coward · 2010-03-17 08:54 · Score: 0

Droid-native builds of 2.1 in build ERE25 and ESE53 have been available from some time after being leaked from Verizon. There are already several top-end custom ROMs based around ESE53 (and most had ERE25 versions as well). ESE53 adds native support for all 2.1 features, including gpu acceleration for 2.1 Live Wallpapers.
If you have a Droid and want to try it out, you can hit up droidforums.net or alldroid.org to get the ROMs. I recommend ChevyNo1's Simply Stunning, AdamZ's Smoked Glass, and blackdroid's Ultimate Droid. Pete is falling behind with Bugless Beast and he's kind of a dick to other developers too, so you can skip over it.
Just recently Helix Launcher 1.2a was released through XDA-Developers and on the Android Market for free, so it has made it's way into a few ROMs as well. I highly recommend rooting with Droid Root Helper, flashing recovery to SP Recovery 0.99.3b, and trying out Ultimate Droid 7.8 first. While a little more error-prone than some of the less complex ROMs, it is pretty much filled to the brim with features, and nonetheless is fairly solid these days (move from ported 2.1 to native ERE25/ESE53 helped considerably).
With a custom ESE53 ROM and Kernel (recommend AdamZ's Medium Voltage 1.1GHz or ChevyNo1's ESE53 5-slot 1.1GHz) you should be able to do 1.1GHz no prob, and possibly push as far as 1.3GHz on the CPU overclock. Help support good devs and buy TempMonitor and SetCPU in the Android Market to overclock and check your batt/cpu temps.
I highly recommend you do not wait for the over the air upgrade, as it is likely to be significantly reduced in feature set compared to current native development builds (ERE25/ESE53), and you will get quite a few added features in custom ROMs (HTC Sense UI, Helix Launcher, Swype, Full Live Wallpapers support, Wi-Fi Tethering, etc. with matching theme).
Re:What? by Anonymous Coward · 2010-03-17 10:21 · Score: 0

I use Linux because it's cool and I like to use it.
FREE BOOTLOADER FOR MILESTONES!! by Anonymous Coward · 2010-03-17 14:32 · Score: 1, Interesting

Hello.
Did you know Milestone (European/Canadian/Latinamerican) brother of the Droid has a signed bootloader?
You cannot run customized firmware/kernels on the Milestone like you do on the Droid. And this is just the beginning as more locked phones are coming.
Spread the voice. Don't buy Motorola Android phones. Even Motorola itself tells you to buy HTC:
http://community.developer.motorola.com/t5/MOTODEV-Blog/Custom-ROMs-and-Motorola-s-Android-Handsets/ba-p/4224
Thanks for reading
I hope it fixes some of the problems by AaronW · 2010-03-17 16:36 · Score: 1

I hope it fixes the problems I've been having, especially with Wireless and VPN. PPTP on the Droid is broken if encryption is enabled and at this point my Droid does not see any wireless networks at all now. Sometimes I run into other quirks as well, like Bluetooth not connecting or the GPS not getting a signal (until I power cycle the phone).

--
This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
What about HTC Hero? by Anonymous Coward · 2010-03-18 02:48 · Score: 0

I would like to know when the HTC Hero will be upgraded to Android 2.x on the Telus network in Canada. I am holding off buying one. Anyone have ideas?
Delayed... Again. In other news Gran Turismo 5 out by winningham.2 · 2010-03-18 08:18 · Score: 1

Official reports that Android 2.1 is delayed yet again and will not be released at noon Thursday March 18th. Heard the real reason for the latest delay on the Android 2.1 update for Droid phones is due to Motorola’s distribution vendor (Bitfone- now owned by HP). They are having capacity problems with a) the Bitfone application that distributes the updates and b) capacity issues with the current network infrastructure that hosts this application. Suckie.
Phones should not be appliances by Yfrwlf · 2010-03-19 18:54 · Score: 1

Phones should be like computers, and you should not have to code Android for specific phones other than giving Linux the needed drivers.

--
Promote true freedom - support standards and interoperability.