Shared publicly  - 
Dear CM team (I know you're lurking here), for the love of everything that is sacred in Android, can you please note down the actual phone models we can recognize next to codenames? These are unknown to 99.99% of us: es209ra, smb_a1002, etc.

cc +Steve Kondik +Atin M, etc.

Art Russ's profile photoAnjie Cai's profile photoAl Sutton's profile photophysilenzz techjunky's profile photo
I don't have an Xperia X10 or X10i, and I have no idea what es209ra is when it shows up on that page. Google has very limited knowledge of it, and after research, it's definitely possible to figure it out, but it would be far better if we didn't have to do that. And it's not just this page - there are many places like that. Being more clear wouldn't hurt. Android doesn't have to be cryptic.
It's a buffer that would prevent ultra noobs from learning how not to be a noob. 
+Akhil Patel I'd also like to tell him to get some RSS feeds going. Been dying for those.
It makes the job a million times easier for Art and company to report for everyone, that's the point.
Why would anyone withhold information that could educate those who need it? Unless they enjoy feeling superior. 
Also, isn't the same model name used for different hardware in different markets? I.e. the Japanese Xperia X10 is physically different from the European one?
+David Carr everyone is an ultra noob at some point why would you want to exclude people from the community? Because it might create some extra blog posts that help other ultra noobs in the future? I'm just sayin, we all have been there so it doesn't hurt to give a little back.
Or, if you thought the other way round, this naming scheme due to its uniformity across differente device carriers (with different namings and all) makes it easier for the developers to actually develop and test stuff out. Of course adding an extra layer of abstraction to the naming scheme (accounting for the different names of the same device) would be possible but...
Any n00b can really mess up their phone without using the device cypher. This really doesn't protect anyone.
+boris iomdin That's not the RSS I am talking about - I want an RSS of changes, not releases.
+boris iomdin The page you linked to lists commits as they happen - to read release notes, which are oftentimes generalized, you will have to wait for said release. Nobody does release notes for nightlies. Release notes for nightlies are the commit logs.
+Zach Coma Nobody said remove the device codename - just add some common device names next to them.
I didn't say remove it, I agree with you that adding a name would be helpful for everyone.
real androids know them all ;D
motorola atrix, had that for a while then accidentally bricked it q_q
I had this exact issue this weekend. I'm now sporting 2.3.1 on my Samsung Galaxy S but it took way too fucken long to install and most of that was due to trying to find the appropriate things to work with.
+Art Russ should find a list of the vendor name for the devices and stick it on Androidpolice
Not speaking on behalf of the team, just for my personal opinion. I think this is a non issue.

* The method used is mainly for consistency, as one device name can have multiple 'marketing' names.
* The names shown are also how Rom Manager interprets new releases.
* On top of that, as new devices roll in, a wiki page is created that states the following for every device: "The Sony Ericsson Xperia Mini Pro (aka Mango)" with the corresponding name and device inserted. The speed of this is up to the wiki team, but they do a great job of having the info up before any stable/RC release (nightly users are expected to have the knowledge)
* With the variety of 'marketing' names, how would you propose listing the Z71 variants (which are 15 separately named and sold devices)?
* Finally, yea, there is a learning curve built in; but nothing that can't be easily overcome by reading through the wiki or release post (as even the release posts reference the device names)

tl;dr: Its not changing; learn to love it :) [Edited for readability]
if i didn't own an Atrix, i would've been lost as to what Olympus was myself. just as i had no clue what the es209ra was until i read the comments.
too many code names, i believe the nexus one was called passion and dragon? (maybe more who knows)
HP Touchpad is called....tenderloin :/
+Enrico Perera I don't see the name on the list? :/ Do we have to wait till beta comes out?
GGGEEEEEEEeeeeee i could pick an argument with some of you geeks......why can't you just make it as easy as possible for non geeks to root there phone and mod it just like you can...... most people have a life other than total geek dom. Me, I am a fulltime Single Dad and well i have a kid with #Autism...... I simply don't have the time to learn how to Root an Android device or to flash a new Rom onto it.
#Android devices are a great #Learning tool + #Speech / communication Aid for kids with #Autism or any Disability for that matter
I want SOMEONE to make it as Easy as possible to #Root , #Flash or #UnBrick any Android Device. And I sure as hell want to be able to EASILY identify my device and what #Rom i can Install on it
You Want to walk a mile in my shoes ???

Now who can help me Unbrick a Teclast T760 7' Android2.3 tablet.......anyone point me to help
cheers D
+Anjie Cai Its still in its alpha stages and therefore not part of the nightlies yet. But the codename for touchpad is tenderloin, it says on the alpha install :)

If you have a touchpad, the alpha build is great! Theres almost no problems (none that i can see anyways, or even care about).
+Abhisek Devkota i'm just wondering but what's the difference between i9000 and i9000-gt? I didn't understand the difference when flashing the recovery image.
+Darren Moore im sorry to hear all that. But you must understand that somethings, are technical and not everyone will understand it. Thats just how it is. I understand that time is not a luxury you might have, but you make claims with 'wants' is unnecessary. If you want something, you must be willing to go out and do it yourself. IF the want is great is enough. The main thing is, there are somethings that others will know and others will not. Its not fair to accuse people of making things too technical, because really the amount of complexity and cleverness that goes into rooting a device from scratch and all that reverse engineering, IS very technical.

Now, there are SOME simple methods (one click solutions), but they may or may not work in all cases and for all devices.

If you really WANT something, you must be willing to do it yourself (learning, asking, doing, trying, fixing, etc...) regardless of the circumstances you have, positive or negative.

But i suggest, if you arent that technical, you avoid rooting, or anything that can brick your device (as it seems you have already), UNTIL you become MORE familiar with how these devices, and what rooting does and how to do it. Or at least follow procedures well enough that if something goes wrong, you know where the problem might lie to speak with the devs.

Good luck with your tablet, I sincerely hope it does get unbricked.
+Anjie Cai, +Shawn Alty can answer this better, but in technical terms, there is nothing different between the two devices, its a naming issue that arises between the SGS Vibrant (GT) and the TMobile Vibrant (SGH-T959) that causes the GT to occur.

The GT is the International Vibrant, which is the same as the i9000 Samsung Galaxy S that was sold in other parts of the world.

tl;dr Because Samsung
One should (at the very least) learn the code name to one's own device before flashing anything, not just CM..... And if anything, a code name could trick a young android tinkerer into doing more research on his own device, which is a good thing
+Art Russ never heard of p970 in my life o_o I know most of the weird ones... heh
Smba1002 is viewsonic gtab. Malata based board... Ni adam is smba 1006, hannspad is smba1007
Wow I thought I was the only one who didn't no what the codenames meant!! 
Btw my phone is zte blade. And it is BLADE!!!! 
Unfortunately, those are the actual names of the devices the manufacturers assigned them, and how the devices refer to themselves. The names we're used to seeing are what the respective marketing departments of AT&T, Sprint, T-Mobile, Verizon, etc. gave them.
You do know "n00bs" can find out the codenames too and that doesn't do anything to imply they are any less likely to brick their phone.
+Anjie Cai Been trying to do that and keep up with everything. Our categories have codenames next to device names.
+Art Russ why so many fricken code names? Can't the oem and carrier just keep it the same?
Add a comment...