Nexus S is not a "developer phone" - stop calling it one! - Nexus S General

I keep seeing posts where people call this thing a developer phone. It is not a "developer" phone, and I wish people would stop calling it one.
From Google's official android developer's site (take note of the parts I've put in italics and bold):
"If you want a SIM-unlocked phone, then you might consider either an Android Dev Phone or the Google Nexus S. These are SIM-unlocked so that you can use them on any GSM network using a SIM card. The Android Dev Phones also feature an unlocked bootloader so you can install custom system images (great for developing and installing custom versions of the Android platform). To find a a place you can purchase the Nexus S, visit google.com/phone. To purchase an Android Dev Phone, see the Android Market site (requires a developer account)."
Click to expand...
Click to collapse
They wouldn't say "or a Nexus S" in the same sentence as developer phone if it were a developer phone, but the stronger argument that it's not a "developer phone" is the fact that you don't have to have a developer account on the Android Market to buy one.
People usually call it a developer phone while making excuses for buggy android software and other glitches. This is a disservice to all users and lets Google off the hook for all the major glitches in the Gingerbread just a bit more easily than they deserve.
The Nexus S is sold to the public at large, at the largest big box consumer electronics store in the US and marketed as the most advanced phone you can get. No mention of "developer" in any advertising, talking points, or Google literature on the phone that I've ever seen.
Even the Nexus One wasn't a developer phone until they stopped trying to change the phone industry by selling direct to the public via the web. Check Google's blog from last August.
The only thing even remotely developer-ish on the NS is the easily unlocked bootloader...but that doesn't make it one.
/rant off

Agreed.
Sent from my Nexus S using XDA App

True that it's not officially called a dev phone (isn't the N1 still the only one?)
But honestly, who cares what people call it? Dev phone or not, the GB glitches and bugs suck. Even if it was officially a Developer Phone, isn't a dev phone a phone people are supposed to develop and test their apps on? Not be guinea pigs for the OS itself...

fchipm said:
True that it's not officially called a dev phone (isn't the N1 still the only one?)
But honestly, who cares what people call it? Dev phone or not, the GB glitches and bugs suck. Even if it was officially a Developer Phone, isn't a dev phone a phone people are supposed to develop and test their apps on? Not be guinea pigs for the OS itself...
Click to expand...
Click to collapse
Right on the guinea pigs part. Gingerbread could have used a bit more beta testing in my opinion.
I don't have a dev account, so I don't know what the official list is, but I do know the Nexus S isn't the only one. I imagine there are many models; the developer phones are unlocked sims and unlocked bootloaders so devs can buy one and use on any network to test their apps without being forced to a certain carrier, which would turn some devs off.
My issue with people calling it one around here is that way too many people are quick to dismiss other people's (legitimate) complaints about the phone and Gingerbread with something along the lines of the two following remarks:
"It's a developer phone, you should expect bugs..."
"It's a Nexus phone, you're on the bleeding edge of the OS and you should expect bugs..."
Personally, I don't mind most of the quirks on the phone (the reboot during a call and the sudden loss of data are my only real complaints), but on a $600 (after taxes) phone that my mother could walk into Best Buy and purchase, I expect the thing to be solid enough for consumers and a bit more polished.
Though in fairness to the NS, I think most android phones have plenty of quirks, and to be fair to android in general, most versions of iOS do as well.

distortedloop said:
I keep seeing posts where people call this thing a developer phone. It is not a "developer" phone, and I wish people would stop calling it one.
From Google's official android developer's site (take note of the parts I've put in italics and bold):
They wouldn't say "or a Nexus S" in the same sentence as developer phone if it were a developer phone, but the stronger argument that it's not a "developer phone" is the fact that you don't have to have a developer account on the Android Market to buy one.
People usually call it a developer phone while making excuses for buggy android software and other glitches. This is a disservice to all users and lets Google off the hook for all the major glitches in the Gingerbread just a bit more easily than they deserve.
The Nexus S is sold to the public at large, at the largest big box consumer electronics store in the US and marketed as the most advanced phone you can get. No mention of "developer" in any advertising, talking points, or Google literature on the phone that I've ever seen.
Even the Nexus One wasn't a developer phone until they stopped trying to change the phone industry by selling direct to the public via the web. Check Google's blog from last August.
The only thing even remotely developer-ish on the NS is the easily unlocked bootloader...but that doesn't make it one.
/rant off
Click to expand...
Click to collapse
Yes it is true, nexus s is not a developers phone.
What is weird is that the nexus one aka "developers phone" still doesn't have android 2.3 after 7 weeks. I wonder on which phone gingerbread was developed and tested then. I also wonder, how are they going to test NFC on android 2.3+ on a nexus one... hhmm and also wonder how are they going to test video chat on google's Talk app (rumors says it is coming) on the nexus one... I also wonder how the game optimization done on gingerbread could be developed on a non-multi-touch developers phone... I'm confused

This topic has already been talked to death. Why open another thread just to rant, man? Get off your semantics soap box and give it up.
Sent from my Nexus S using XDA App

Nexus one wasn't a dev phone either... at first it was just another phone. Then became a dev phone and sold as a "official dev phone" for testing.
With time... the nexus s will also become a dev phone too.
And yes... this subject is getting old...
Google updates, No bloatware, stock hotspot and tethering, etc.. etc..
not official dev... but it taste, looks, and acts like dev.

I don't think they'll turn the NS into a dev phone, it might not even be a phone, It'll be ADD instead. (device)
What's gonna be defacto HW by july this year? All mfgs will have dual core phones and google will be planning for jelly by then.

kenvan19 said:
This topic has already been talked to death. Why open another thread just to rant, man? Get off your semantics soap box and give it up.
Click to expand...
Click to collapse
For the same reason everyone else does...
And it's a high horse, not a soap box.

distortedloop said:
For the same reason everyone else does...
And it's a high horse, not a soap box.
Click to expand...
Click to collapse
No, its definitely a soap box. One makes speeches from a soap box and it is typically associated with preaching on a street corner or in more modern terms making a speech to a crowd of people who couldn't care less.
Oh, and by correcting your mistake I am knocking you off your high horse as I'm proving you're fallible.

kenvan19 said:
No, its definitely a soap box. One makes speeches from a soap box and it is typically associated with preaching on a street corner or in more modern terms making a speech to a crowd of people who couldn't care less.
Oh, and by correcting your mistake I am knocking you off your high horse as I'm proving you're fallibility.
Click to expand...
Click to collapse
You meant to type "your".
"You're" means "your are", and saying "I'm proving you are fallibility" is grammatically incorrect.

JCopernicus said:
You meant to type "your".
"You're" means "your are", and saying "I'm proving you are fallibility" is grammatically incorrect.
Click to expand...
Click to collapse
Actually, it was merely a typo. I originally typed "fallible" and decided to change it to "fallibility" however forgot to change "you're" to "your". The mistake has been corrected.

**** me,
Does the word Anal mean anything to you guys hahaha
Some people are just so pedantic on xda, If you wanna argue, get married
JD

The Nexus S is a phone, no phone is ever released as a developer phone, it just evolves into one by the option of an easy root and unlock of the bootloader. In the future the Nexus One will no longer be able to support latest OS's so im sure the Nexus S will carry that torch,
And i dont give a toss about spelling mistakes,
JD

distortedloop said:
I keep seeing posts where people call this thing a developer phone. It is not a "developer" phone, and I wish people would stop calling it one.
From Google's official android developer's site:
Android Developers website said:
If you want a SIM-unlocked phone, then you might consider either an Android Dev Phone or the Google Nexus S. These are SIM-unlocked so that you can use them on any GSM network using a SIM card. The Android Dev Phones also feature an unlocked bootloader so you can install custom system images (great for developing and installing custom versions of the Android platform).
Click to expand...
Click to collapse
They wouldn't say "or a Nexus S" in the same sentence as developer phone if it were a developer phone, but the stronger argument that it's not a "developer phone" is the fact that you don't have to have a developer account on the Android Market to buy one.
Click to expand...
Click to collapse
Actually, the "Android Dev Phone" was a version of the HTC Dream sold with a specific unlocked bootloader. Therefore, this is not an either/or situation of a "developer phone" versus the Nexus S, but rather a specific model name. The Android developers' website has changed its wording since it was originally released, but if you do a search, you will still references to "ADP".
Likewise, if you look at HTC's Developer Center you will find links to the ADP1's proprietary binaries—this "ADP1" is the "Android Dev Phone" that is mentioned on the Android website. There was also an ADP2, which was called the Ion and given out at one year's Google I/O conference; that phone was made by HTC, and was sold under the names Magic and the T-Mobile myTouch 3G. (There is a forum here for the device under "Sapphire", the target name of the device.)
When Google brought out the Nexus One, it stopped selling through its site the ADP1 and ADP2, and the Nexus One replaced those products as a "developer phone". Similarly, the Nexus One has now been superseded by the Nexus S, which is the newest "developer phone".
While it may just be semantics, the Nexus S is a "developer phone", and the "Android Dev Phone" was the name of a specific phone model, just like "Nexus S" is the name of a specific phone model.

kenvan19 said:
No, its definitely a soap box. One makes speeches from a soap box and it is typically associated with preaching on a street corner or in more modern terms making a speech to a crowd of people who couldn't care less.
Oh, and by correcting your mistake I am knocking you off your high horse as I'm proving you're fallible.
Click to expand...
Click to collapse
I was trying to lighten the mood and be self-deprecating by saying it was a high-horse not a sop box, but your ego made you take it as some kind of challenge to your superiority and forced you to spew out more of the same? Trust me, there's no contest there, you are obviously more intelligent, compassionate, and a more valuable a member to the xda community than I am. I suspect I might be better looking, but that's a matter of taste, and unproven since I have no idea what you look like in person. My tongue is firmly planted in my cheek, please take it that way.
Anyways, like any other thread you think discusses something to death, give it a one star rating and stop participating, it will eventually filter down to the bottom and we won't have to look at it any more. I've given that advice in other threads on here, and followed it myself.
As it stands, your posts in this thread have been nothing but inflammatory and baiting. What's the point? At least when I get snarky about "that's already been posted/asked/discussed, I also add something responsive, like the answer to the question, an opinion on the topic, or a link to something to move the conversation forward. Have you done the same here?

I'm sorry you don't think it's a "developer phone" whatever the buttsmack crap that is.
Hate to burst your bubble, but any phone that supports USB debugging (AKA every Android phone? The iPhone? WP7?) is a developer phone.
Either way, if you're getting at buggy OS, even that would have nothing to do with whether it's a "developer phone" or not. Most phones are buggy. Developer phones or not. They all have their quirks. So wtf is this topic about?
Now if you're saying it's a developer phone to specifically develop Android on, and not apps, then yes, it compiles from source and you can fastboot from source with an unlocked bootloader.
Sorry it's not codenamed the "ADP4", yet.

distortedloop said:
I was trying to lighten the mood and be self-deprecating by saying it was a high-horse not a sop box, but your ego made you take it as some kind of challenge to your superiority and forced you to spew out more of the same? Trust me, there's no contest there, you are obviously more intelligent, compassionate, and a more valuable a member to the xda community than I am. I suspect I might be better looking, but that's a matter of taste, and unproven since I have no idea what you look like in person. My tongue is firmly planted in my cheek, please take it that way.
Anyways, like any other thread you think discusses something to death, give it a one star rating and stop participating, it will eventually filter down to the bottom and we won't have to look at it any more. I've given that advice in other threads on here, and followed it myself.
As it stands, your posts in this thread have been nothing but inflammatory and baiting. What's the point? At least when I get snarky about "that's already been posted/asked/discussed, I also add something responsive, like the answer to the question, an opinion on the topic, or a link to something to move the conversation forward. Have you done the same here?
Click to expand...
Click to collapse
I haven't posted any quotes to the prior conversation because I see no reason to post a link to a conversation I had with you in a different thread given that it was with you. My second post was to clear up that I was not, in fact, referring to a high horse, but a soap box. You asked me, whats the point of my posting this but I would rebut with the same question. Why would you post a meaningless, cluttering thread about an opinion based on semantics which has already been discussed at length in other threads? In fact, in your first post you are baiting others with a differing view point by explicitly stating that they are wrong.
My personal opinion on the matter is that it is a developer phone in spirit. I would never have called it that before I read this blog post on the Android Developers Blog:
The Nexus S, like the Nexus One before it, is designed to allow enthusiasts to install custom operating systems. Allowing your own boot image on a pure Nexus S is as simple as running fastboot oem unlock. It should be no surprise that modifying the operating system can give you root access to your phone. Hopefully that’s just the beginning of the changes you might make.
Click to expand...
Click to collapse
That is an endorsement of developing specifically mentioning that the Nexus S was designed to allow developers to develop on this phone. But I've said all of this before and I saw no reason to re-post the same opinion over and over, again, given that I had said conversation with you not two weeks ago.

There are two android dev phones. I just logged in to check.
One's a mytouch 3g and a Nexus One.
$399 & $529.

Anderdroid said:
I'm sorry you don't think it's a "developer phone" whatever the buttsmack crap that is.
Hate to burst your bubble, but any phone that supports USB debugging (AKA every Android phone? The iPhone? WP7?) is a developer phone.
Either way, if you're getting at buggy OS, even that would have nothing to do with whether it's a "developer phone" or not. Most phones are buggy. Developer phones or not. They all have their quirks. So wtf is this topic about?
Click to expand...
Click to collapse
But those are exactly the points that I was making: 100's of posts in here saying something to the effect of "You should expect bugs because it's a developer phone..." The buggy software isn't because it's some special kind of developer phone that should be given a pass because it has that label, and calling the phone a developer phone, when it's sold to the public via normal distribution channels, doesn't excuse the bugs.
There is no point to this topic...I'd suggest that everyone stop reading it.
formuk said:
There are two android dev phones. I just logged in to check.
One's a mytouch 3g and a Nexus One.
$399 & $529.
Click to expand...
Click to collapse
Thank you...

Related

G2 rootkit, prevents any permenant modification.

Just as the title stated Gizmodo has an article on how g2 revert to stock after reboot. This makes me feel better about owning a vibrant because of samsung lackluster support. Anyway, the point of this thread is about the " root kit" and your thought, discussion, etc
I personally think this is a low blow on htc part, especially looking at their track record with android.
Sent from my SGH-T959 using XDA App
Edit: now I have access to a computer here's the link to article (which summarize and link back what is already here at G2 forum, haha)
http://gizmodo.com/5656921/t+mobiles-g2-rootkit-will-reinstall-stock-android-after-a-jailbreak
Click to expand...
Click to collapse
they apparently can't even remove bloatware as it reinstalls upon reboot
Unfortunately locking down android phones is an inevitability. As more and more people transition their daily net use to smartphones so will the purveyors of malware. Making it more difficult to root is a necessary evil. The g2 has a backdoor otherwise there'd be no way to ota updates. It will be discovered. Though it might take more time than the couple of days the phone has been available. Relax
Sent from my SGH-T959 using XDA App
masterotaku said:
Unfortunately locking down android phones is an inevitability. As more and more people transition their daily net use to smartphones so will the purveyors of malware. Making it more difficult to root is a necessary evil. The g2 has a backdoor otherwise there'd be no way to ota updates. It will be discovered. Though it might take more time than the couple of days the phone has been available. Relax
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I agreed that the developers here will have no problem figuring out the backdoor as they are awesome. However, one can not ignore the fact that HTC which is known to promote customization, decided to install this type of "rootkit". Malware is inevitable which is why Google needs to step up their game, being "OPEN" does not mean no intervention of any sort. Simply looking through the app for malware while not irrationally rejecting App would bring a much needed safety net.
Makes me wonder if it is T-Mobile who requested the system to be put in place.
Its more accurate to say that HTC has been in the game longer with popular android handsets than deliberately having been more open than others. It might seem a tad ironic given the level of impatience with Samsung over updates and whatnot but they have been far more open with the galaxy s than pretty much any other manufacturer and any other phone....HTC included...
If its any consolation the non Tmobile version of this phone seems to have the same restrictions.
Sent from my SGH-T959 using XDA App
IF this is true, and I step back from being a fan of Android, it actually makes sense.
With Android, as with any consumer electronic product, "power-users" are a small percentage of total users. Applying this truth to Android, I think you can extrapolate out that manufacturers, don't want power-users causing all kinds of support nightmares (like bricking their phones and returning them as defective), so they start increase the effort required to do power-user type things.
I prefer to look at it in practical terms as the manufacturers saying, "If you want to do developer type things, you need to get developer type hardware."
It sux because the developer device won't ever be able to "keep up with the Joneses" as far as coolness factor. However, if you just reference all of the posts of people doing stuff the manufacturer did not intend for them to do, then claiming their phone was defective, and getting a new one, the manufacturers are almost forced into doing stuff like this.
Now you mentioned it, it was really easy to root and modify the phone compare to other phones "traditional" methods.
It is understandable of why people (myself included) were anxious of Samsung as they have horrible update history compare to HTC or Motorola in recent times. If Samsung can push out their update in a more timely manner, I wouldn't put it pass myself to say that Galaxy S is the best android phone on the market.
Perhaps the rollback is due to internal bugs similar to the storage issues G2 is having as well which is possible considered that a messaged up storage would not keep the changes made.
i'm sure this rootkit won't be a problem for long.
funeralthirst said:
http://img692.imageshack.us/img692/7089/whatrootkit.jpg
Click to expand...
Click to collapse
the what rootkit image was a joke per chris.
the problem with this is that there was recently a ruling that jailbreaking your device is legal - this move is in direct violation to the DCMA ruling.
byt3b0mb said:
the what rootkit image was a joke per chris.
the problem with this is that there was recently a ruling that jailbreaking your device is legal - this move is in direct violation to the DCMA ruling.
Click to expand...
Click to collapse
i know it was a joke, which is why i took down the link. but it was funny.
this isn't a violation, though. the act of jailbreaking/rooting a phone is legal, but that doesn't mean manufacturers can't try and restrict/prevent people from doing it.
devcurious said:
IF this is true, and I step back from being a fan of Android, it actually makes sense.
With Android, as with any consumer electronic product, "power-users" are a small percentage of total users. Applying this truth to Android, I think you can extrapolate out that manufacturers, don't want power-users causing all kinds of support nightmares (like bricking their phones and returning them as defective), so they start increase the effort required to do power-user type things.
I prefer to look at it in practical terms as the manufacturers saying, "If you want to do developer type things, you need to get developer type hardware."
It sux because the developer device won't ever be able to "keep up with the Joneses" as far as coolness factor. However, if you just reference all of the posts of people doing stuff the manufacturer did not intend for them to do, then claiming their phone was defective, and getting a new one, the manufacturers are almost forced into doing stuff like this.
Click to expand...
Click to collapse
I'm gonna go out on a limb and say that HTC didn't want it, but T-Mobile did. They removed tethering from the 2.2 build. They know that the first thing that rooters do is install tethering software to their Android devices. So yeah, TMO prolly asked HTC to block root so that people wouldn't be tethering all the time.
On 7.2 devices, that wasn't a big issue, but the G2 can theoretically get up to twice as fast as our Vibrants, and with TMO only using 10mhz or so for their HSPA+ deployments, they're probably concerned with too much tethering hurting network performance.
I love how the arguments on that website keep pointing to how its going to ruin android and how android is open source. Last time I checked Android is an operating system not hardware. Either T-mobile locked it or HTC. I'm going to bet like everybody else that its T-Mobiles doing.
The only thing its going to do honestly is piss off future buyers and they will either avoid that phone or wait for it to be rooted. When the G1 came out I waited until it was rooted then I bought. Vibrant I waited until it was confrimed to be rooted. Of course that was nearly before it hit the market so I bought nearly the day it was available.
So T-Mobile I hope you don't mind loosing sales on that model because its going to happen. I was -| |- close to buying that for my wife. I guess now its not going to happen and if she wants something else first then well you lost her business.
if assholes wouldn't tether 5+ gigs (or way way more) a month then come to the forums bragging about it....we might not have this issue
but people want to abuse it and use tethering for ****ing torrents
morons
But what a boneheaded move. They must have known that many people wanted the G2 as a successor to the N1 as a dev phone.
Why is this in the vibrant section, this has nothing to do with the vibrant
The cake is a lie!
Maybe this is why the G2 folks won't see the full 4G ram that's becasue HTC used part of it to store the firmware to be rewrite when it detects an modification to the phone. Now, who else is dumping the vibrant for the G2?
im sure the devs will figure out a way around this pretty quick lol
PaiPiePia said:
Malware is inevitable which is why Google needs to step up their game, being "OPEN" does not mean no intervention of any sort. Simply looking through the app for malware while not irrationally rejecting App would bring a much needed safety net.
Click to expand...
Click to collapse
And what is malware? Any app that reads your SMS? Well, Handcent needs to do that.
Any app that can dial? Google Maps can do that (not to mention the many Dialer replacements).
Any app that requests GPS? Well, if it's not in /system & your GPS is turned off, it can't turn it back on & if you want that app to remain free, the advertiser wants to target market.
Any app that sends your data someplace? Then just about everything on the phone is useless.
How can you look through the app & determine what is malware? Inspect the sourcecode manually? Some apps take nearly a year to get approved for the iDevices. Devs would abandon the Android Market if that started happening pretty quickly. The iDevices have a proven $ turnaround while Android has a pretty hefty piracy rate & others that just don't want to pay for any app because they shouldn't have to because the OS is open and free and so should the apps be.
byt3b0mb said:
the problem with this is that there was recently a ruling that jailbreaking your device is legal - this move is in direct violation to the DCMA ruling.
Click to expand...
Click to collapse
Just because it is legal for you to do it doesn't mean it is illegal for the manufacturer to make it as hard on you as possible.
trashcan said:
Maybe this is why the G2 folks won't see the full 4G ram that's becasue HTC used part of it to store the firmware to be rewrite when it detects an modification to the phone. Now, who else is dumping the vibrant for the G2?
Click to expand...
Click to collapse
That would make complete sense since they effectively need to keep a backup of the OS on hand in case you delete something....with most phones if you delete it, it's gone, you can't factory format back to stock (without a proper backup).
Since this was pretty much advertised as an upgrade to the G1 (hence the name and it coming out just about 2 years later), and most G1 owners were basically tech savvy people, this can't be good for HTC or TMO. This phone more than most others (excepting the N1) is the phone that the people who WANT root would be upgrading to (except for those of us that already swapped to the Vibrant).
Oops 10chars
HTC rocks!!!!!!!

My dealings with HTC

Just posted this on the T-mobs forums and some of this is already in the "lets get the kernel thread" but I think we should make a single source for what information HTC is giving us in case this does proceed to legal action, etc. Had to futz a little with the hyperlinks since I'm a new poster to XDA but am not a new user of this blissful place. So here it is...
I call BS on the whole thing.
I've been trying to get HTC to release the source code and also bringing up the shenanigans that they pulled on us all with this root block and internal memory bait and switch crap. Here is my dealings with HTC so far. Love the blame game they switch at the end of our discussion. I know this is a lot to read but trust me that this back and forth is quite entertaining.
MY 1ST HTC MESSAGE
To whom it may pertain to... Just purchased a HTC T-mobile G2 aka HTC Vision and have been a avid HTC supporter for quite sometime. Ever since I owned my first HTC device the codenamed blueangel. The fact that HTC would work with the developer community pulled me toward your devices. I can't believe you guys (HTC) would lock down the successor to the device that helped you start the "open" revolution. I know it was most probably T-mobile that made you do it but that is besides the point. Especially since they have blamed you in the press. You have spit it the face of the developer community and shame on you and T-mobile. This protection will be broken I have no doubt of that but the fact that HTC put it there at all is what is in question. Please don't make this a race of protection...hack...protection...hack. OPEN means we should work together not against each other. So please do the right thing and help us either root these devices or give us the kernel source to help us along. Or even better do both of the above and show you respect the dev community like we all thought you did. Below I have included the first post of a stream that will become a torrent against HTC from the XDA devs. Thanks for your cooperation.
MY 1ST HTC REPLY
We cannot comment on whether or not HTC has blocked any customer from rooting or hacking their phone. Rooting the phone may open the phone up to virus attacks and other un-secure activities, as well as introduce intended functionality, and as such is very difficult for us to support. We cannot comment on whether or not HTC, Google, or T-Mobile has blocked any customer from rooting or hacking their phone. All three companies work very closely to bring you the best experience on the phone possible. I do understand how important it is to be able to use your device to the best of its capabilities. We are not withholding the kernel; we are currently working through the legal channels that we must go through to make the kernel available to you. Each product is individually under review. When the kernel is available, you will be able to find it on developer.htc.com. I apologize for any inconvenience you may have experienced, and thank you for your patience in this matter.
MY 2ND HTC MESSAGE
I understand the position of HTC to not comment on the situation at hand even though it has already been outed in the press by T-mobile that HTC did indeed lock the phone. So either you are saying that the T-mobile press release was a hoax and HTC did nothing with write protection or HTC just want's the problem to go away. As far as not wanting us to root because of unsafe activities.... Well I don't even know where to start with that comment. We are all big boys and girls and can handle the effect of our actions. It's like saying Toyota installed a system in my car that will only let a certified technician open the hood because I may insert washer fluid into the engine instead of oil. Most companies would love it if you would void your warranty. Does it not lead to less operating cost for HTC in the long run to not support it's products because the warranties are void? You don't want me to void my warranty then do as the GPS companies do and make a disclaimer that I have to read and agree to before I go any further. Also on the subject of voiding warranties did HTC not say that G2 had 4gb's of internal storage? Yet only 1.2gb are available for use because of this lock? Back to the car analogies. If Ford says your car has 200 horse power in the brochure and (AFTER!!!!) you buy it you learn that only 50 horse power is unlocked you might be a little angry. No? I understand the position of all big companies is to play dumb until something either is forgotten or legal channels make them play smart but I do have to say that I did not expect this out of HTC. This post isn't directed at you Sarah but merely my G2 and thousands of others crippled devices. If you could pass this and my prior message to someone higher up that might at least read it and think it over it would be greatly appreciated.
MY 2ND HTC REPLY
Thank you for contacting HTC Technical Assistance Center. I do understand your desire to fully explore the G2’s potential. Let me try and address your concerns one by one. In regards to your request for source code, HTC will typically publish on developer.htc the Kernel open source code for recently released devices. HTC will normally publish this within 90 to 120 days. This time frame is within the requirements of the open source community. As for your concerns about the internal memory space, the space listed on the box and in advertisements is the total storage capacity of the phone, and in fact does exist in the phone. The majority of the space is being used to make sure your phone is running at optimal performance levels. If you require more space, you can use the provided SD Card to add media and other files. Our SD card reader can support up to 16gb of extended storage. Try and look at it along the lines of your computer. Just because on a floppy disk you had 1.44 mb of space didn’t ever mean you could use all that. There was always an amount of space you could never use. This is true for any computer type related device with storage. Big or small there’s always an amount of “floating” space needed. At this point we will be happy to document your concern with the current release state of the phone. Your concerns are being forwarded to the proper departments. Beyond the information provided, however, we would have nothing additional to release
MY 3RD HTC MESSAGE
Ummm. The reply on the 1.44mb floppy is just crazy out of bounds. Yes I understand that if I install a 1tb drive on my computer some 100mb's or so may be floating but not 500 gigs of my drive!!! You guys commandeered over HALF of the internal storage of the G2. That's just crazy. Also on the (right?) that you have to release the source code in 90-120 days.... Who made up that number? Certainly not the GPL you are supposed to adhere to. An excerpt from freedom-to-tinker talking about the G2 source code. "Perhaps HTC (and T-Mobile, distributor of the phone) should review the actual contents of the GNU Public License (v2), which stipulate the legal requirements for modifying and redistributing Linux. They state that you may only distribute derivative code if you accompany it with the complete corresponding machine-readable source code." Notably, there is no mention of a "grace period" or the like. The importance of redistributing source code in a timely fashion goes beyond enabling phone rooting. It is the foundation of the "copyleft" regime of software licensing that has led to the flourishing of the open source software ecosystem. If every useful modification required waiting 90 to 120 days to be built upon, it would have taken eons to get to where we are today. It's one thing for a company to choose to pursue the closed-source model and to start from scratch, but it's another thing for it to profit from the goodwill of the open source community while imposing arbitrary and illegal restrictions on the code." Please release the code. =)
MY 3RD HTC REPLY
I understand how this can be frustrating for you. To start, we are aware of a situation where the phone is not properly reflecting the correct amount of storage available on the device and we are working with T-Mobile to figure out why this is happening and how to resolve it. I appreciate your patience with it. Next, we provide a timeframe of 90-120 days for the release of the source code as a courtesy for our customer. Unfortunately, HTC Technical Support has no control over what is or is not published on our website and we can only forward the requests to our software developement team and website administrator. The code will be released and when it is you may find it on our developer website. Unfortuantely, my office only handles the technical troubleshooting of our devices stock software and hardware. I do apologize for any inconvenience that you may have experienced through this.
I SMELL WEAK SAUCE ALL OVER THIS!!!!
Are you emailing HTC America about this? Not sure what you think that will accomplish given that none of their low level engineering is done in the US. Also, what's with the rage over root? Did the labelling on your G2 box promise root or bootloader access? I thought we all went into this with the assumption this would be a consumer device and as such was fair game for any sort of anti-cracking protection.
It's not really about the protection on the device as it is that they have to release the source code when they release the devices. HTC is getting out of hand with this. Google HTC GPL violation and you'll see what I mean.
Also the box did say that it had 4gb of internal storage. That turned out to be as true as me saying "I have a 12 inch **** but only when I have a certain signed key unlockable erection."
simobile said:
It's not really about the protection on the device as it is that they have to release the source code when they release the devices. HTC is getting out of hand with this. Google HTC GPL violation and you'll see what I mean.
Also the box did say that it had 4gb of internal storage. That turned out to be as true as me saying "I have a 12 inch **** but only when I have a certain signed key unlockable erection."
Click to expand...
Click to collapse
lmfaooooooooooo i died reading this man hahahahahaha im in tears man. but that is true tho. what shocked is that this guys actually read and replied your messages. unbelievable, i would have thought they would send you one of those monotone messages like "thanks for contacting us, we appreciate your concern and we will get back to you type bologne " this shows that htc aint that bad but this still sucks, for now. two things lead me to believe that its gonna get rooted permanently:
1: this phone is bound to have updates which obviously isnt the stock that the phone came with. if this was a computer chip or whatever then any phone that comes with it wont recieve any updates because it will return to original way it came in the box right?
2: it will be really pointless releasing the source code if it wouldnt help with the rooting.
im not the best when it comes with source codes and rooting, im just thinking out loud is all. feel free to correct me.
Well done. The one thing that bugs me about HTC is that they make the hardware not the OS. It’s not like I'm opening the phone to change out chip sets. What I think we need is a well written stock letter that every member of XDA can e-mail by the masses to HTC and T-Mobile demanding them to release the open source code they use in there, so called “everything you” devices.
One person is noisy but a thousand or more is deafening.
what shocked is that this guys actually read and replied your messages. unbelievable, i would have thought they would send you one of those monotone messages like "thanks for contacting us, we appreciate your concern and we will get back to you type bologne "
Click to expand...
Click to collapse
I do agree that I was also shocked that they were actually responding to my messages instead of some generic corportate bs. So I do give them Kudos for that.
Well done. The one thing that bugs me about HTC is that they make the hardware not the OS. It’s not like I'm opening the phone to change out chip sets. What I think we need is a well written stock letter that every member of XDA can e-mail by the masses to HTC and T-Mobile demanding them to release the open source code they use in there, so called “everything you” devices.
One person is noisy but a thousand or more is deafening.
Click to expand...
Click to collapse
This is kinda what I envisioned for this thread. You could share your experiences with HTC or Tmobile if you have already contacted them and If you haven't hopefully it would prompt you too. I would like them to come out in November and say that that 90% of device complaint calls / emails were from the G2. Unrealistic I know but I can dream.
... Why do people keep bringing up the GPL? AFAIK, Android isn't released under the GPL. It's Apache licensed.
And even for the GPL, there's never been a 'the -instant- you release a product, the source must be there' - it's a 'you have to make the source available' (again, this is GPL, -not- Apache, just pointing out). That can be in the form of punch cards delivered via mule, if they want.
The GPL has many vagueness issues like this (or at least, v2 did, v3 fixed some of it, but who uses v3?).
I'd say HTC's being fairly good about it, in that they release the source at all, given that the Apache license doesn't require it.
I doubt they are withholding it just because they have nothing better to do. If you've ever worked with a large company, I'm sure you're aware of how the easiest tasks can take weeks of paper work and general BS to get done...
While I agree they should have it out a bit quicker, I'm really getting annoyed at all the whining (not necessarily directed at this thread). Most of the complaints are valid, but I wish people would just relax.
Despite the rooting issues, the "hidden" memory, hinge not being as firm as people want, etc...I still am happy with the phone. There's some preinstalled junk, but nothing like practically every other phone on the market. The hardware is nice, and there's already an update despite how new the phone is.
Sent from my T-Mobile G2 using Tapatalk
Ditto
Jorsher said:
I doubt they are withholding it just because they have nothing better to do. If you've ever worked with a large company, I'm sure you're aware of how the easiest tasks can take weeks of paper work and general BS to get done...
While I agree they should have it out a bit quicker, I'm really getting annoyed at all the whining (not necessarily directed at this thread). Most of the complaints are valid, but I wish people would just relax.
Despite the rooting issues, the "hidden" memory, hinge not being as firm as people want, etc...I still am happy with the phone. There's some preinstalled junk, but nothing like practically every other phone on the market. The hardware is nice, and there's already an update despite how new the phone is.
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Second that!
shograt said:
... Why do people keep bringing up the GPL? AFAIK, Android isn't released under the GPL. It's Apache licensed.
And even for the GPL, there's never been a 'the -instant- you release a product, the source must be there' - it's a 'you have to make the source available' (again, this is GPL, -not- Apache, just pointing out). That can be in the form of punch cards delivered via mule, if they want.
The GPL has many vagueness issues like this (or at least, v2 did, v3 fixed some of it, but who uses v3?).
I'd say HTC's being fairly good about it, in that they release the source at all, given that the Apache license doesn't require it.
Click to expand...
Click to collapse
Your right about android being apache, that's why they can have closed source things like sense. HOWEVER the kernel is infact a moddified linux kernel, which in fact falls under GPLv2. According to the GPL violations angency has stated that they are infact in viaolation.
And simobile glad you started this thread, seems people were more concerned with my grammer the the problem at hand here...
Knock this **** off before HTC stops making quality phones for us because of little ****s like you. Sit back and wait, the phone's only been out a week. Quit ruining it for everyone else.
SuperDave81 said:
Knock this **** off before HTC stops making quality phones for us because of little ****s like you. Sit back and wait, the phone's only been out a week. Quit ruining it for everyone else.
Click to expand...
Click to collapse
As someone who gives his hard earned money to HTC, how does he not have the right to ask them whatever he wants? If they don't respond, or blow him off, it'll turn a lot of us off HTC.
He isn't ruining anything other than your little bubble which I'm pretty sure no one else cares about.
One thing about their reply - they said the microSD card was max 16 gb. Whatever happened to the 32gb their other phones can read? Was this an error by customer services?
I know there is quite a few holes in the responses they gave me... 16gb vs 32gb, a bug that tmob and them are working on to fix missing memory? Quite odd indeed. Despite all those things I would urge everyone to send them a message and please post responses here. I'd like this to stay topical and not become a "oh I have a me too trolling comment in my head so let me reply" So please go to the link below and shoot them a message if you have a complaint about all this. The more people that do the better chance we won't have to sit back and wait 90-120 days for this source. It's super simple and they seem to respond pretty quick.
http://www.htc.com/www/about_htc_bymail.aspx
Man people are really butt hurt over everything not being perfect on launch day over this phone. Holy ****...
I mean come on guys. If your biggest problem is a lack of source code and part of the internal memory is supposedly missing then your life really isn't all that bad.
I'd like to think if the worst thing going on in my life is I'm mad at a cell phone then my life is at an all star level compared to most people.
Man people are really butt hurt over everything not being perfect on launch day over this phone. Holy ****...
I mean come on guys. If your biggest problem is a lack of source code and part of the internal memory is supposedly missing then your life really isn't all that bad.
I'd like to think if the worst thing going on in my life is I'm mad at a cell phone then my life is at an all star level compared to most people.
Click to expand...
Click to collapse
Congratulations you win a bridge....You can live under it and charge people as they pass over. Jesus Christ your thoughts are so important go ahead and spill them.
Plus you might be interested in my new site
www.XDA-i<3-stockdevices.com
Since that's all the trolls seem interested in.
simobile said:
Congratulations you win a bridge....You can live under it and charge people as they pass over. Jesus Christ your thoughts are so important go ahead and spill them.
Plus you might be interested in my new site
www.XDA-i<3-stockdevices.com
Since that's all the trolls seem interested in.
Click to expand...
Click to collapse
Ummm, wtf?
Funny how when a post doesn't adhere to the topic at hand it makes people go WTF? Now ask yourself did your post have anything to do with the topic of this thread? Or anything to do with the want to modify or dev a device?
SuperFly03 said:
Man people are really butt hurt over everything not being perfect on launch day over this phone. Holy ****...
I mean come on guys. If your biggest problem is a lack of source code and part of the internal memory is supposedly missing then your life really isn't all that bad.
I'd like to think if the worst thing going on in my life is I'm mad at a cell phone then my life is at an all star level compared to most people.
Click to expand...
Click to collapse
Uhm, I spend $500 on a new phone, and I can't even count on the stupid thing to stay running through the day? Yeah, I'd consider that something to be pissed about. I've owned many HTC devices over the years, and have bought most of them outright in the release week. NEVER have I had one with as many issues as the G2. I took it back today, and told them even if they fix all these issues (screen, memory, random reboots and lockups, and trackpad spazzing out) I doubt I'd pick another one up.
I've got a funny feeling, that some of these issues tie directly into the locking down of rooting on this phone as well... Whether it be technical, or they just wasted all their time locking it down rather than doing some basic Q&A, it's a pretty big issue.
So yeah, I don't advise you coming in here and telling people that it is no big deal that a device that costs as much as a new laptop doesn't work worth ****.
SuperFly03 said:
Ummm, wtf?
Click to expand...
Click to collapse
haha, just saw this. WTF are you doing on XDA if you don't want to mod your device?

SMS bug OTA coming in a few days

For those who don't follow @GalaxySsupport (official Samsung) on Twitter, they just tweeted the following:
"#NexusS owners! OTA update coming over the next few days. It will prevent an SMS from being sent to the wrong contact."
Click to expand...
Click to collapse
My response was great, but when's the reboot during a call bug fix coming...
distortedloop said:
My response was great, but when's the reboot during a call bug fix coming...
Click to expand...
Click to collapse
Not soon enough!
If I think that a call is likely to last a few minutes I pre-warn the caller that my phone might cut out. One of my contacts said that I ought to get an Android phone (he's apparently got a Desire) FFS!!!!!!!
Heres the news in written:
http://phandroid.com/2011/01/20/samsung-nexus-s-ota-coming-to-fix-sms-bug/
what puzzles me is that why is the samsung support releasing this news? aren't we getting all nexus ota's from google?
I'm confused why Samsung is the one announcing this.
Edit: lol seems I am not the only one
deeren said:
what puzzles me is that why is the samsung support releasing this news? aren't we getting all nexus ota's from google?
Click to expand...
Click to collapse
It's still a Samsung product, and despite people who populate this forum thinking of it as a Google phone, there are surely plenty of consumers who have purchased the phone at Best Buys just because it's heavily promoted there (at least at all 3 of the Best Buys near me) and is a really neat looking phone.
Samsung gets the black eye for bugs in the minds of those customers, and so they have an interest in this, even though it comes from Google.
If you check out the other tweets from the account I quoted, they do say the update comes from Google, not them, so they don't have a change log to share.
Seems Google is really taking a "hands-off" approach to the Nexus line.
Such a shame.
JCopernicus said:
Seems Google is really taking a "hands-off" approach to the Nexus line.
Such a shame.
Click to expand...
Click to collapse
Samsung makes an announcement, and suddenly it means Google is taking a "hands-off" approach?
I don't make the same connection quite so easily; but I'm an optimist.
distortedloop said:
Samsung makes an announcement, and suddenly it means Google is taking a "hands-off" approach?
I don't make the same connection quite so easily; but I'm an optimist.
Click to expand...
Click to collapse
Well it appears they are letting samsung deal with customer service, as opposed to dealing with it in house (like the N1 initially). Although they did shift CS off to HTC sometime in may of last year.
Google is basically acting as a hands off broker at this point.
My assumption(and hope) though is that they are just using Samsung as a gateway for direct customer interaction, and not for actual software development. *crosses fingers*.
JCopernicus said:
My assumption(and hope) though is that they are just using Samsung as a gateway for direct customer interaction, and not for actual software development. *crosses fingers*.
Click to expand...
Click to collapse
Google's never been good at customer service in that regard, with any product. Plus, unlike the Nexus One, Google never had anything to do with this phone's retail sales to the public.
If you read the rest of the twitter traffic on the @galaxySsupport account, there are numerous tweets that state the software is coming from Google, that Samsung doesn't even have change log knowledge, and that Google doesn't have to deal with carriers on this, and that Samsung isn't aware of what other fixes Google is working on.
Seems like Samsung's just the public voice in that light.
In semi-related news, the Vibrant will finally get 2.2. Roll outs start tomorrow. I think the most interesting thing to note in this report though is that Tmobile will be more strict about updating software.
Moving forward, T-Mobile will update all Android phones to new versions of the Android OS within 3-5 months after Google makes the new OS public. Smartphone users expecting frequent upgrades is “new to us”, Brodman said, “and we’re going to have to step up and change the way we do things.”
http://www.tmonews.com/2011/01/samsung-vibrant-froyo-update-coming-january-21st-tomorrow/
3-5 month is only a slight improvement, but does it change anybody's mind about the value of the Nexus line? Does it make not getting immediate updates slightly more tolerable?
What's also curious to me is, when exactly is the Nexus One going to get 2.3? The "coming weeks" has turned into a month now. Is this an indication for Nexus S owners at the end of 2011 or early 2012 when the next Nexus phone is released with the latest Android?
onthecouchagain said:
In semi-related news, the Vibrant will finally get 2.2. Roll outs start tomorrow. I think the most interesting thing to note in this report though is that Tmobile will be more strict about updating software.
Moving forward, T-Mobile will update all Android phones to new versions of the Android OS within 3-5 months after Google makes the new OS public. Smartphone users expecting frequent upgrades is “new to us”, Brodman said, “and we’re going to have to step up and change the way we do things.”
http://www.tmonews.com/2011/01/samsung-vibrant-froyo-update-coming-january-21st-tomorrow/
3-5 month is only a slight improvement, but does it change anybody's mind about the value of the Nexus line? Does it make not getting immediate updates slightly more tolerable?
What's also curious to me is, when exactly is the Nexus One going to get 2.3? The "coming weeks" has turned into a month now. Is this an indication for Nexus S owners at the end of 2011 or early 2012 when the next Nexus phone is released with the latest Android?
Click to expand...
Click to collapse
I don't think Tmobile's stance diminishes the value of the Nexus line at all and here is why: the point of the Nexus line has been to serve as a "developer phone." Its pure Android without bloat of any kind and that is why I love it. Any other phone on Tmo is going to have bloat and be laden with UIs and whatnot and some people like that. This just means that more people can get what they want with Android and stay up-to-date on software. I think its a great move on Tmo's part and I think it shows a lot of guts to hold manufacturers to that kind of a schedule. The true test will be to see how well it holds up in the real world.
kenvan19 said:
the point of the Nexus line has been to serve as a "developer phone."
Click to expand...
Click to collapse
Show me a credible link from Google that says the Nexus S is a "developer phone". Please.
distortedloop said:
Show me a credible link from Google that says the Nexus S is a "developer phone". Please.
Click to expand...
Click to collapse
I was stating an opinion? I didn't realize I had to quote sources for my opinions.
kenvan19 said:
I was stating an opinion? I didn't realize I had to quote sources for my opinions.
Click to expand...
Click to collapse
No, you don't have to quote sources for opinion, but you seemed to be stating that "the point of the Nexus line has been to serve as a "developer phone." " was a fact to support your opinion. Since I thought you were stating it as a fact, I would like to have seen something that supports that.
We've discussed that in some other thread here as well.
Plenty of people claim the Nexus S, and the Nexus "line" are intended as developer phones and throw it around as justification for buggy software and to dismiss complaints about the phone.
There's nothing I've seen from Google that says the Nexus S is a "developer phone", and someone linked an official list of developer phones, and the NS wasn't on it, and the N1 wasn't even on it until AFTER they pulled it from the Google Phone Store for sale to the public.
Not attacking you at all, just looking for clarification.
distortedloop said:
No, you don't have to quote sources for opinion, but you seemed to be stating that "the point of the Nexus line has been to serve as a "developer phone." " was a fact to support your opinion. Since I thought you were stating it as a fact, I would like to have seen something that supports that.
We've discussed that in some other thread here as well.
Plenty of people claim the Nexus S, and the Nexus "line" are intended as developer phones and throw it around as justification for buggy software and to dismiss complaints about the phone.
There's nothing I've seen from Google that says the Nexus S is a "developer phone", and someone linked an official list of developer phones, and the NS wasn't on it, and the N1 wasn't even on it until AFTER they pulled it from the Google Phone Store for sale to the public.
Not attacking you at all, just looking for clarification.
Click to expand...
Click to collapse
I'm sorry for the confusion then. All of my statements were conjecture and the reason I called it a "developer phone" and not a developer phone is that in spirit it seems to be something aimed more towards developers as this quote directly from the android developers blog imples:
The Nexus S, like the Nexus One before it, is designed to allow enthusiasts to install custom operating systems. Allowing your own boot image on a pure Nexus S is as simple as running fastboot oem unlock. It should be no surprise that modifying the operating system can give you root access to your phone. Hopefully that’s just the beginning of the changes you might make.
Click to expand...
Click to collapse
The author of this article is an engineer on the Android Security team and he makes it quite clear that the point of the Nexus S and the Nexus One before it was to allow people to design software for their devices. When the term "developer phone" is thrown around generally, however, it usually means something other than how I use it; its a catch-all for, as you said, software bugs and any other OS issues which is not how I see a "developer phone". I see it as a phone that is designed to be hacked. And in that sense, it really is a "developer phone".
Excellent, and I agree!
Thanks.
distortedloop said:
Plenty of people claim the Nexus S, and the Nexus "line" are intended as developer phones and throw it around as justification for buggy software and to dismiss complaints about the phone.
Click to expand...
Click to collapse
Quoted for the truth. This could not be more accurate.
I like my Nexus S, but I've been a huge critic of Gingerbread, and to a lesser extent, of the "pure" stock/vanilla Android experience. It could stand to be improved a lot and is sorely in need of bug fixes/updates. Having said that, I would never argue on for the side of OEM skins either. I'm just saying, vanilla Android has its own share of problems.
Side note: you know what's one thing that bothers me, purely for lack of intuitiveness? Sometimes when you open a field that requires typing, the keyboard doesn't show up. It requires you to tap the empty field for the keyboard to come up. Or other times, if the keyboard does show up, the cursor will be at the beginning of the word as oppose to at the end, or as oppose to having the entire word you want to replace/edit highlighted. These unnecessary "extra steps" don't hinder the phone useless, of course, but just a nuisance that shouldn't exist on a "smart" phone.
/end side note.
Isn't every Android phone a developer phone? I'm a developer and I own more than 6 of them just for compatibility.
Anderdroid said:
Isn't every Android phone a developer phone? I'm a developer and I own more than 6 of them just for compatibility.
Click to expand...
Click to collapse
The main difference is how easy the nexus s is to make open to roms. Most other devices require exploits to unlock the nand and bootloader whereas the nexus requires a single adb command.
Sent from my Nexus S

Google - No Honeycomb AOSP for you!

http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
Google says it will delay the distribution of its newest Android source code, dubbed Honeycomb, at least for the foreseeable future. The search giant says the software, which is tailored specifically for tablet computers that compete against Apple's iPad, is not yet ready to be altered by outside programmers and customized for other devices, such as phones.
almostinsane said:
http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
Google says it will delay the distribution of its newest Android source code, dubbed Honeycomb, at least for the foreseeable future. The search giant says the software, which is tailored specifically for tablet computers that compete against Apple's iPad, is not yet ready to be altered by outside programmers and customized for other devices, such as phones.
Click to expand...
Click to collapse
More beta BS. I'll sell you a car but we only completed the frame.
Yup - Its why I just sent my Xoom back to Moto.
Perhaps it's time to change your ID to "completelyInsane".
Sent from my SCH-I500 using XDA App
_RTFM_ said:
Perhaps it's time to change your ID to "completelyInsane".
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
LMAO!
Sent from my PC36100 using XDA Premium App
i dont understand what will make it "ready" if they are planning on eventually releasing it what will keep it from being ported to phones then. If its a matter of incompleteness then what's changed since Cupcake which everyone agrees was more .8 than 1.0. Releasing it to dev's will allow for bugfixes and tweaks to get merged upstream.
It will leak eventually. It always does...
Sent from my Xoom using XDA App
Yea I dont understand google some times. I understand the the OS isnt ready, but if it really is that bad and that unstable then why even put it on a tablet. And really what harm does it do the put out the code, so people will port it to other devices, you can keep doing what you will but make lots of devs happy.
They say they're worried about a poor user experience. Who do they think these users are? "I he4rd on the int3webz I can haz h0neycombz on my G1?" I mean we already know that the percentage of people running custom Roms, while large for what it is, is not the bulk of people using Android. And we know that what we're doing may not be the smoothest experience. The SDK has already been ported to pretty much everything, and they're worried about the actual 3.0 being a poor experience? Come on Google, what's this really about?
This wasn't the best source to quote from. Google said they don't want developers trying to port it to phones yet since they can't guarantee a good user experience on phones. They're afraid XDA is going to port it, people try to run it on their phones and then say how crappy it runs on a phone even though that's not what it was designed for. You know it would happen, and word would spread that it sucks on phones and yada yada it doesn't get a fair chance.
Sent via EVO
As much of a ROM guy as I am, I admit this makes sense from a business stand point. Google makes $ from licensing and distribution (with regards to Android). The hacker communities do not make up said market for the most part.
The worst thing companies combat these days is negative publicity.
I owned an iPhone, two iterations, the 3G and the original. Why did my mother never purchase one, nor my sister? Simply because of how locked down they are due to MY advice. Were they ever going to buy said device due to their hackability? Hell no. But because I said it was sh**** that Apple locks their stuff down so much, they declined to buy said hardware.
Releasing the software for Google could have a lot of negative effects on a BRAND NEW operating system for a BRAND NEW market for Google. If people are throwing this on phones, you search it out on the internet, and everything is Honeycomb this sucks, and honeycomb that sucks, due to people using it on phones, most people who try to do basic research, like my mother, or sister,
will only see "THIS SUCKS".
Just my 2c, but I can see their stand point. Until they can find a way to keep it off the phones, I see this as an issue for google.
~m
familiarstranger said:
They say they're worried about a poor user experience. Who do they think these users are? "I he4rd on the int3webz I can haz h0neycombz on my G1?" I mean we already know that the percentage of people running custom Roms, while large for what it is, is not the bulk of people using Android. And we know that what we're doing may not be the smoothest experience. The SDK has already been ported to pretty much everything, and they're worried about the actual 3.0 being a poor experience? Come on Google, what's this really about?
Click to expand...
Click to collapse
Uhmm, are we reading the same forum? Where people knowingly purchased a device that didn't have flash or lte or an ad card working at launch but are still *****ing and whining and returning their xoom regardless? What I mean is, those same people will install Honeycomb and complain that google released a lousy product.
Sent via EVO
thegeektern said:
I understand the the OS isnt ready, but if it really is that bad and that unstable then why even put it on a tablet. And really what harm does it do the put out the code, so people will port it to other devices, you can keep doing what you will but make lots of devs happy.
Click to expand...
Click to collapse
My understanding of that article is that Google doesn't feel its ready for phones. It's not that its not ready for tablets. They understand that they won't be able to stop people from using HC on phones, but trying to stave off the inevitable...
this HC thing looks like crap.... oh.. on my phone. In the end.. we are talking about a company here.. a company that needs to keep it's image.. and products.. (or software as you may call it).. as good as possible.
I don't think it's the best move Google could have made, but I think Google should do things in it's best interest to keep itself as a company in good standing. Long and short of it.. if things go south for google.. we'll all be unhappy. Just getting things out for the sake of allowing devs to play doesn't mean its the most sound decision for the company making it.
Yes, I know.. it's 'open source', but it is still a work-product. I think it's also entirely likely this is just a marketing ploy to say 'we told you so'.. and then it will get leaked and everything will go back to normal. But I still think people often forget that this is still a company that has to keep itself together to survive.
EDIT: So many things get written in the same time when you respond to a post! It seems as though I am joining the choir of.. this isn't so bad.
Sirchuk said:
This wasn't the best source to quote from. Google said they don't want developers trying to port it to phones yet since they can't guarantee a good user experience on phones. They're afraid XDA is going to port it, people try to run it on their phones and then say how crappy it runs on a phone even though that's not what it was designed for. You know it would happen, and word would spread that it sucks on phones and yada yada it doesn't get a fair chance.
Sent via EVO
Click to expand...
Click to collapse
Well that hasn't stopped devs on xda porting it already - http://forum.xda-developers.com/showthread.php?t=978939
Darn you almostinsane, I was just about to post this but you beat me to it!
Its really unfortunate that Google is doing this, whatever happened to a completely open source OS? In my honest opinion I think they should release it to the public and let the various devs have at it and see what can be improved and take those improvements into consideration for the next release of Android. If the OS was only meant for tablets who is to say that x developer can port it to a handheld flawlessly? It would be a HUGE leap ahead for us and for big ol' G.
Either way, it'll happen with or without Google releasing the source as our one dev spacemoose1 has shown us with making a near perfect port to the Samsung tab of honeycomb.
Stinks money is such an issue, Google doesn't really need anymore haha.
Done with my rant now
Sent from my ADR6300 using XDA App
Another business reason for this decision: Google may not have programmed Honeycomb well.
An obvious(?) repercussion for grimy source code going public is more bashing of Honeycomb's alleged "beta-ness". The more app developers that use the ...poisonous open-source code, the more ...poisoned apps there will be.
Or, they want to curb full-blown Honeycomb from appearing on devices other than the Xoom for just a little longer.
you're right. I just hate that its true. Your sig shows you remember the G1 days when we were all just so happy about what our phone COULD do. It's gotten a lot whinnier around here since then.
Sirchuk said:
Uhmm, are we reading the same forum? Where people knowingly purchased a device that didn't have flash or lte or an ad card working at launch but are still *****ing and whining and returning their xoom regardless? What I mean is, those same people will install Honeycomb and complain that google released a lousy product.
Sent via EVO
Click to expand...
Click to collapse
As a ROM enthusiast; yea this sucks. Business it's understandable; but as the former it doesn't make me happy.
My NC sorely needs a aosp honeycomb, HC's tablet interface is superior to even CM7 on it.
Honestly though it's a lot of speculation here on why, but it really just sounds like an excuse (Bad one) to quiet the devs while really being a straight business decision.
How is not releasing honeycomb aosp right away not being open? Would you like all your roms without SD card support right now? Honeycomb is most likely stable enough for normal use for the average consumer and Google had to make footprint in the tablet industry before ipad2 was announced. Things were obviously rushed so i rather wait for them get everything situated. I think this unfortunate news but I'm not gonna cry foul when its something that's probably for the better. Google has proven with each iteration of android they have released source so just be patient
Sent from my Xoom using Tapatalk
almostinsane said:
Yup - Its why I just sent my Xoom back to Moto.
Click to expand...
Click to collapse
I don't understand the logic here. What alternative are you seeking? Take it back for the Galaxy 10.1? It runs the same OS. Take it back for an iPad? It runs a closed OS.
The AOSP release is delayed ... maybe. Why would you return your Xoom because of this?
Sent from my Nexus One using XDA Premium App

The real truth about ANDROID.

For those of you who my not know of Androids beginnings, why it was created, who created it here it is straight from the horses mouth. Open Handset Alliance.
And for those who have heard about or those who know all about but have forgotten the "Roots" of Android.
www.openhandsetalliance.com
I bet these guys never envisioned carriers or manufacturers being allowed to restrict us, the entire Dev community be it however knowledgeable you are, with devices that have locked bootloader's without the opportunity to be unlocked.
Maybe instead of petitioning Google or the FCC, we should reach out to Open Handset Alliance and help them remember what they had dreamed of. And started all this for and with a promise the the dev community of the "completely open customizable platform" for us, consumer, and manufacturers.....
Either way its an interesting and very educational read if you haven't already or have never heard of them.
Enjoy....
You misspell the website: https://www.openhandsetalliance.com/index.html
Nice finding of such a retro feeling website.
jerryhou85 said:
You misspell the website: https://www.openhandsetalliance.com/index.html
Nice finding of such a retro feeling website.
Click to expand...
Click to collapse
Oh crap. LMAO thanks buddy. I bet there was some people clicking mine and thinking "this dude is an idiot"
jerryhou85 said:
You misspell the website: https://www.openhandsetalliance.com/index.html
Nice finding of such a retro feeling website.
Click to expand...
Click to collapse
I didn't just find it. Years ago when I was on VZW with the RAZR HD and HD MAXX, we had issues with the bootloader locking. I started researching who started/ founded ANDROID. And discovered the whole back story and a short documentary on the guys that started it. Pretty interesting. I'm a little shocked that they allow these carriers and manufacturers to implement bootloader's that "can't be unlocked". Seems as if it goes against every plan and idea they had in mind when they went open source. And clearly their website relays the same message.
mattwheat said:
I didn't just find it. Years ago when I was on VZW with the RAZR HD and HD MAXX, we had issues with the bootloader locking. I started researching who started/ founded ANDROID. And discovered the whole back story and a short documentary on the guys that started it. Pretty interesting. I'm a little shocked that they allow these carriers and manufacturers to implement bootloader's that "can't be unlocked". Seems as if it goes against every plan and idea they had in mind when they went open source. And clearly their website relays the same message.
Click to expand...
Click to collapse
This gives me a same feeling when I compare how I see Google 10 years aga and now. Back at that time, Google was like "Don't Do Evil", now, Google is like "The Biggest Potential Evil on This Planet"... and the similar to Facebook.
Tech infants now are tech gaints and they become everything...
jerryhou85 said:
This gives me a same feeling when I compare how I see Google 10 years aga and now. Back at that time, Google was like "Don't Do Evil", now, Google is like "The Biggest Potential Evil on This Planet"... and the similar to Facebook.
Tech infants now are tech gaints and they become everything...
Click to expand...
Click to collapse
Everything that they once hated and stood against... Thanks for the good read

Categories

Resources