Beta

Slashdot: News for Nerds

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Android 2.1 Finally Makes It To Droid

timothy posted more than 4 years ago | from the for-all-your-robot-needs dept.

Cellphones 132

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."

cancel ×

132 comments

first (-1, Offtopic)

Anonymous Coward | more than 4 years ago | (#31512752)

First

v2.1 Post (-1, Offtopic)

Anonymous Coward | more than 4 years ago | (#31512766)

Beat the droid to first post

I am quite happy! (4, Insightful)

ircmaxell (1117387) | more than 4 years ago | (#31512794)

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...

Re:I am quite happy! (3, Informative)

GweeDo (127172) | more than 4 years ago | (#31513156)

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.

Re:I am quite happy! (2, Funny)

Anonymous Coward | more than 4 years ago | (#31513376)

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 :)

Re:I am quite happy! (1)

ThermalRunaway (1766412) | more than 4 years ago | (#31514384)

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.

Re:I am quite happy! (2, Insightful)

Hurricane78 (562437) | more than 4 years ago | (#31514514)

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. ;)

Re:I am quite happy! (1)

Threni (635302) | more than 4 years ago | (#31514804)

> 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.

Re:I am quite happy! (2, Insightful)

nschubach (922175) | more than 4 years ago | (#31514816)

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.

Re:I am quite happy! (2, Interesting)

centuren (106470) | more than 4 years ago | (#31515190)

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/ [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.

Re:I am quite happy! (1)

Skuld-Chan (302449) | more than 4 years ago | (#31516806)

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.

What? (-1, Troll)

Anonymous Coward | more than 4 years ago | (#31512804)

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, this phone is still a tinkerer's best friend."

Tinker all you like. I'll keep on using my iPhone. I also don't use Windows as I've got work to do. I don't work for Microsoft or Norton either. I use a Mac because the OS isn't full of holes and doesn't get in my way when I'm working.

Re:What? (0, Offtopic)

Pojut (1027544) | more than 4 years ago | (#31512930)

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.

Re:What? (1)

ircmaxell (1117387) | more than 4 years ago | (#31512952)

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)...

Re:What? (0)

Anonymous Coward | more than 4 years ago | (#31513170)

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.

Re:What? (0)

Anonymous Coward | more than 4 years ago | (#31514008)

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

Re:What? (1)

BatGnat (1568391) | more than 4 years ago | (#31514236)

Commodore 64?

Re:What? (2, Informative)

sbeckstead (555647) | more than 4 years ago | (#31513430)

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.

Re:What? (0)

Anonymous Coward | more than 4 years ago | (#31516338)

I use Linux because it's cool and I like to use it.

Already use DroidMod (2, Informative)

Aequitarum Custos (1614513) | more than 4 years ago | (#31512852)

which has all the features 2.1 has that I found useful Multi-touch + Picasa Gallery + Google Earth!

Re:Already use DroidMod (1)

Mike Buddha (10734) | more than 4 years ago | (#31513410)

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?

Re:Already use DroidMod (1)

nschubach (922175) | more than 4 years ago | (#31513996)

One feature makes you question dedication?

what is this "ROM" of which you speak? (0)

Eunuchswear (210685) | more than 4 years ago | (#31512990)

On my linux based phone I juat "apt-get update; apt-get upgrade"

None of this "ROM" or "flashing" nonsense.

Re:what is this "ROM" of which you speak? (2, Interesting)

Sir_Lewk (967686) | more than 4 years ago | (#31513036)

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.

Re:what is this "ROM" of which you speak? (0, Offtopic)

Lunix Nutcase (1092239) | more than 4 years ago | (#31513162)

And to be even cooler, why don't you whine about how people don't use "hacker" like the old 70s neckbeards did?

Re:what is this "ROM" of which you speak? (1)

Mike Buddha (10734) | more than 4 years ago | (#31513438)

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!

Re:what is this "ROM" of which you speak? (0)

Anonymous Coward | more than 4 years ago | (#31515378)

DEY DOOK OUR WERD!!!

Re:what is this "ROM" of which you speak? (0)

Anonymous Coward | more than 4 years ago | (#31515620)

DURK ORR WUURRK

Re:what is this "ROM" of which you speak? (1)

violasvegas (1662837) | more than 4 years ago | (#31514746)

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?

Re:what is this "ROM" of which you speak? (1)

Sir_Lewk (967686) | more than 4 years ago | (#31515054)

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.

Re:what is this "ROM" of which you speak? (1)

gd23ka (324741) | more than 4 years ago | (#31513472)

Love your sig, yes you are right on the money dude.

Re:what is this "ROM" of which you speak? (1)

Mike Buddha (10734) | more than 4 years ago | (#31513550)

So you can update your Baseband with apt? I'd didn't know it was capable of that.

What is this "apt" of which you speak ? (0)

Anonymous Coward | more than 4 years ago | (#31513744)

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!

Re:what is this "ROM" of which you speak? (1)

BatGnat (1568391) | more than 4 years ago | (#31514280)

my linux based phone is an Android based phone

Re:what is this "ROM" of which you speak? (0)

Anonymous Coward | more than 4 years ago | (#31514680)

Yeah, that sounds like a ridiculously easy way to administer a phone.

Re:what is this "ROM" of which you speak? (1)

Sir_Lewk (967686) | more than 4 years ago | (#31514740)

He isn't disaproving of the technology, he is disapproving of the terminology (which sounds suspiciously like the terminology used in the 'warez' scene...).

Re:what is this "ROM" of which you speak? (0)

Anonymous Coward | more than 4 years ago | (#31514778)

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.

Re:what is this "ROM" of which you speak? (0)

Anonymous Coward | more than 4 years ago | (#31515220)

Yes. Yes you really can.

Fuck, I just did it last weekend. Somehow I really doubt you have ever used a real linux system.

Re:what is this "ROM" of which you speak? (1)

AndrewNeo (979708) | more than 4 years ago | (#31514802)

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.)

Re:what is this "ROM" of which you speak? (1)

Threni (635302) | more than 4 years ago | (#31515098)

You could always go here:

http://www.cyanogenmod.com/ [cyanogenmod.com]

And give this "Cyanogen" character a piece of your mind - he clearly doesn't know what he's talking about.

Too bad it won't work in Canada (2, Interesting)

i_ate_god (899684) | more than 4 years ago | (#31513078)

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.

Re:Too bad it won't work in Canada (1)

ThatFunkyMunki (908716) | more than 4 years ago | (#31513264)

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?

Re:Too bad it won't work in Canada (1)

malefic (736824) | more than 4 years ago | (#31513320)

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.

Re:Too bad it won't work in Canada (1)

ezesolares (1769606) | more than 4 years ago | (#31514540)

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...

Re:Too bad it won't work in Canada (1)

AndrewNeo (979708) | more than 4 years ago | (#31514844)

Well, the bootloader on the Droid is supposed to be signed, but there was a bug in the source code (patch [android.com] ) 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.

Re:Too bad it won't work in Canada (1, Interesting)

Anonymous Coward | more than 4 years ago | (#31515990)

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.

Re:Too bad it won't work in Canada (0)

Anonymous Coward | more than 4 years ago | (#31517582)

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.

Re:Too bad it won't work in Canada (1)

Mike Buddha (10734) | more than 4 years ago | (#31513498)

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).

Re:Too bad it won't work in Canada (1)

Lunix Nutcase (1092239) | more than 4 years ago | (#31513572)

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.

Re:Too bad it won't work in Canada (3, Informative)

ajlitt (19055) | more than 4 years ago | (#31513266)

Today is your lucky day: N1 for 3G 850/1900/2100 [google.com]

Re:Too bad it won't work in Canada (1)

i_ate_god (899684) | more than 4 years ago | (#31514174)

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).

Re:Too bad it won't work in Canada (0)

Anonymous Coward | more than 4 years ago | (#31516404)

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.

Re:Too bad it won't work in Canada (1)

vio (95817) | more than 4 years ago | (#31513288)

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).

Re:Too bad it won't work in Canada (1)

ezesolares (1769606) | more than 4 years ago | (#31514394)

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).

Re:Too bad it won't work in Canada (0)

Anonymous Coward | more than 4 years ago | (#31513322)

IIRC, Rodgers is going to have a Nexius One that works with the 3g

Re:Too bad it won't work in Canada (2, Informative)

shutdown -p now (807394) | more than 4 years ago | (#31513850)

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.

Re:Too bad it won't work in Canada (1, Informative)

Anonymous Coward | more than 4 years ago | (#31514676)

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

Re:Too bad it won't work in Canada (1)

shutdown -p now (807394) | more than 4 years ago | (#31514822)

If you want a hackable Android phone, it would seem that Nexus One remains the best bet, anyway.

Re:Too bad it won't work in Canada (1)

ezesolares (1769606) | more than 4 years ago | (#31515342)

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

Re:Too bad it won't work in Canada (0)

Anonymous Coward | more than 4 years ago | (#31513972)

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

Re:Too bad it won't work in Canada (0)

Anonymous Coward | more than 4 years ago | (#31514322)

http://www.theglobeandmail.com/blogs/globe-on-technology/nexus-one-now-available-in-canada/article1502169/

Re:Too bad it won't work in Canada (1)

GreenEnvy22 (1046790) | more than 4 years ago | (#31514350)

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.

Re:Too bad it won't work in Canada (1)

js3 (319268) | more than 4 years ago | (#31514876)

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 [www.cbc.ca]

"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 [www.cbc.ca]
"

Re:Too bad it won't work in Canada (0)

Anonymous Coward | more than 4 years ago | (#31517692)

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.

Re:Too bad it won't work in Canada (-1, Flamebait)

Anonymous Coward | more than 4 years ago | (#31514500)

I don't know about other Slashdotters, but Canadians constantly moaning about not having the same treatment as the US gets on my tits.

Seriously - move down south or shut up!

- Not an American

Re:Too bad it won't work in Canada (1)

Hurricane78 (562437) | more than 4 years ago | (#31514566)

Wait. The N900 definitely is compatible with American networks. So shouldn’t that make it compatible with AT&T networks too?

Help... (1)

sbeckstead (555647) | more than 4 years ago | (#31513384)

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?

Re:Help... (2, Informative)

loconet (415875) | more than 4 years ago | (#31513468)

Re:Help... (1, Troll)

sbeckstead (555647) | more than 4 years ago | (#31513552)

Cool, a blog.. thanks...

Re:Help... (3, Insightful)

GweeDo (127172) | more than 4 years ago | (#31513634)

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.

Re:Help... (1)

sbeckstead (555647) | more than 4 years ago | (#31515962)

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.

Re:Help... (1)

GweeDo (127172) | more than 4 years ago | (#31516408)

Your thanks sounded a bit sarcastic. I took it as you were upset he linked you to a blog.

Re:Help... (1)

The Moof (859402) | more than 4 years ago | (#31513642)

This [android.com] might be a little more helpful. The blog was just regurgitating this page, but was out of date anyway.

Re:Help... (1)

loconet (415875) | more than 4 years ago | (#31513934)

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.

Re:Help... (1)

Volante3192 (953645) | more than 4 years ago | (#31514052)

If you want to rub even more salt in his wound, point out that Google owns Blogspot!

Re:Help... (1)

sbeckstead (555647) | more than 4 years ago | (#31515932)

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.

Re:Help... (1)

BertieBaggio (944287) | more than 4 years ago | (#31517276)

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 ("...")?

Re:Help... (0)

Anonymous Coward | more than 4 years ago | (#31513524)

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.

Re:Help... (1)

sbeckstead (555647) | more than 4 years ago | (#31513576)

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.

Re:Help... (0)

Anonymous Coward | more than 4 years ago | (#31513582)

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.

Re:Help... (1)

sbeckstead (555647) | more than 4 years ago | (#31513660)

OK makes sense, but..
http://developer.android.com/resources/dashboard/platform-versions.html [android.com]
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.

Re:Help... (1)

tweek (18111) | more than 4 years ago | (#31513872)

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/ [androidguys.com]

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.

Re:Help... (1)

sbeckstead (555647) | more than 4 years ago | (#31516000)

Thank you. Oops last time I said that I was marked a troll. Aw well.

Re:Help... (1)

Svartalf (2997) | more than 4 years ago | (#31516160)

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.

Bitchin Bagle is where it's at. (1)

gimmebeer (1648629) | more than 4 years ago | (#31513786)

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....

Re:Bitchin Bagle is where it's at. (0)

Anonymous Coward | more than 4 years ago | (#31514072)

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.

Re:Bitchin Bagle is where it's at. (2, Informative)

nschubach (922175) | more than 4 years ago | (#31514114)

FYI, the SholesMod guys moved onto DroidMod [droidmod.org] . Not sure if you followed any of that.

Flash? (1)

sycorob (180615) | more than 4 years ago | (#31513836)

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 ...

Re:Flash? (1)

nschubach (922175) | more than 4 years ago | (#31514140)

The first, and last, I heard was first half of 2010. I've never heard anyone say end of 2009.

Re:Flash? (2, Informative)

BatGnat (1568391) | more than 4 years ago | (#31514318)

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/ [androidauthority.com]

Re:Flash? (1)

AndrewNeo (979708) | more than 4 years ago | (#31514888)

And yet, this article is about the Droid, making your statement irrelevant?

Tinkerer's best friend? (0)

Anonymous Coward | more than 4 years ago | (#31514184)

Have you heard about Nokia N900? That's the true tinkerer's best friend.

Super. (5, Interesting)

nine-times (778537) | more than 4 years ago | (#31514276)

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.

Re:Super. (1)

GooberToo (74388) | more than 4 years ago | (#31516792)

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.

Re:Super. (1)

dudpixel (1429789) | more than 4 years ago | (#31518272)

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?

Re:Super. (1, Informative)

Anonymous Coward | more than 4 years ago | (#31516866)

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.

Re:Super. (1)

jmrives (1019046) | more than 4 years ago | (#31516926)

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.

G1 replacement yet? (0)

Anonymous Coward | more than 4 years ago | (#31515052)

Is there a decent G1 replacement out yet? I want a Nexus One with a physical keyboard that works on T-mobile

Re:G1 replacement yet? (1)

Svartalf (2997) | more than 4 years ago | (#31516278)

If you can find an unlocked BackFlip, you'd be in the right ballpark.

Not really news (0)

Anonymous Coward | more than 4 years ago | (#31515090)

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).

Load More Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account

Loading...