Is root going to be possible for this phone?
Sent from my SM-G950U using XDA-Developers Legacy app
Once kernel source is released, it's very likely. Essential said they'd be releasing that soon in their AMA.
gk1984 said:
Once kernel source is released, it's very likely. Essential said they'd be releasing that soon in their AMA.
Click to expand...
Click to collapse
Thank you for answering I happy to hear it I heard this is great now except for the camera app.
Sent from my SM-G950U using XDA-Developers Legacy app
gk1984 said:
Once kernel source is released, it's very likely. Essential said they'd be releasing that soon in their AMA.
Click to expand...
Click to collapse
Keep in mind, Essential said repeatedly, week after week, while the phone was delayed 90 days beyond when they first said it would be released, that it would be "coming soon."
And they said recently that Oreo would come in the next couple months, which they described as "soon."
And the since it went up in May the website has said that the Stellar Grey and Ocean Depths colors would be "available soon." Even though in the AMA they admitted that they had no idea when those colors would be availalbe and in fact they don't even know how to get ceramic to be those colors, with their attempts so far failing (in other words, they said "available soon" for something they don't actually know how to make).
So Essential's idea of "soon" tends to be months and/or never. And, really, Essential seems to just say "soon" whenever anything is not ready, but they don't want people to go away, so instead they say "soon" to the point of meaninglessness, because they are unable to be honest about what's really going on.
I'm not saying they won't release the kernel source. I'm just saying their promises about when something might happen are empty and "soon" is just used as a delaying tactic.
cb474 said:
Keep in mind, Essential said repeatedly, week after week, while the phone was delayed 90 days beyond when they first said it would be released, that it would be "coming soon."
And they said recently that Oreo would come in the next couple months, which they described as "soon."
And the since it went up in May the website has said that the Stellar Grey and Ocean Depths colors would be "available soon." Even though in the AMA they admitted that they had no idea when those colors would be availalbe and in fact they don't even know how to get ceramic to be those colors, with their attempts so far failing (in other words, they said "available soon" for something they don't actually know how to make).
So Essential's idea of "soon" tends to be months and/or never. And, really, Essential seems to just say "soon" whenever anything is not ready, but they don't want people to go away, so instead they say "soon" to the point of meaninglessness, because they are unable to be honest about what's really going on.
I'm not saying they won't release the kernel source. I'm just saying their promises about when something might happen are empty and "soon" is just used as a delaying tactic.
Click to expand...
Click to collapse
The AMA said "a couple days" so it might be sooner than "soon"
I guess expected to much because Andy Rubin was involved. The whole internet is saying essential was released too soon, that they should have worked out all the bugs first.
Sent from my SM-G950U using XDA-Developers Legacy app
canynballa said:
I guess expected to much because Andy Rubin was involved. The whole internet is saying essential was released too soon, that they should have worked out all the bugs first.
Sent from my SM-G950U using XDA-Developers Legacy app
Click to expand...
Click to collapse
It really was. That and them being severely understaffed, not a good combination.
What really bugs me is releasing kernel is a matter of a clicking a button and they have yet to click that upload button. Very frustrating. I have tried reaching out to them on Facebook and Twitter but there has been zero word from essential or Andy since the AMA. Their silence is troubling
I had the phone and really like the build quality.
What disappointed me was that no source released, so no customs recovery.
No image so you could return the phone back to stock.
No cases.
I sent it back and will see what V2 looks like.
hellot1M said:
What really bugs me is releasing kernel is a matter of a clicking a button and they have yet to click that upload button. Very frustrating. I have tried reaching out to them on Facebook and Twitter but there has been zero word from essential or Andy since the AMA. Their silence is troubling
Click to expand...
Click to collapse
I'm not Android technical but wasn't there mention of proprietary assets mingled it and would need to be removed? Also read somewhere that OnePlus released theirs but it was still hard to create kernels because of the way they released the source. I think it was someone on the AMA thread.
*edit*
C&P from the AMA below. Doesn't specifically mention kernel....
[–]AmirZ 8 points 11 days ago
So, ROM development. Can you commit to releasing ALL of your framework sources like Google does with AOSP and Nexus? One frustration with OnePlus is that their released sources are missing parts and thus work a lot worse than their real OS (OxygenOS).
permalinkembedsavereportgive goldREPLYpocket
[–]EssentialOfficial 13 points 11 days ago
This actually turns out to be really hard technically. We're going to try to do more and more of this over time but ensuring you separate out any close source proprietary bits from the rest, but that things still work well is a big challenge. -Rebecca
flakko86 said:
The AMA said "a couple days" so it might be sooner than "soon"
Click to expand...
Click to collapse
Looking at it, it actually says, " We'll be releasing our kernel and factory images in the next few days." So, it says, "the next few days." And yet that was eleven days ago.
Another example of playing fast and loose with what I think anybody's idea of "few days" would be. Hopefully it will come soon. My point is only that people should not place much faith in Essential's statements about timing. They have only made promises and failed to keep them, just about without exception. It is not a good track record and part of why after my initial hopes and excitement about Essential, I now view them as an "essentially" dishonest company whose intentions are much less honorable than they claim.
This would all be more or less par for the course, for a big corporation spouting empty PR. But Andy Rubin, when he first introduced the phone, did this whole song and dance about how they were going to be a different sort of consumer friendly company. I no longer believe that at all. I no longer even believe that Rubin believed it when he said it. I think it was PR and nothing more.
---------- Post added at 05:11 PM ---------- Previous post was at 05:04 PM ----------
gqukyo said:
I'm not Android technical but wasn't there mention of proprietary assets mingled it and would need to be removed? Also read somewhere that OnePlus released theirs but it was still hard to create kernels because of the way they released the source. I think it was someone on the AMA thread.
*edit*
C&P from the AMA below. Doesn't specifically mention kernel....
[–]AmirZ 8 points 11 days ago
So, ROM development. Can you commit to releasing ALL of your framework sources like Google does with AOSP and Nexus? One frustration with OnePlus is that their released sources are missing parts and thus work a lot worse than their real OS (OxygenOS).
permalinkembedsavereportgive goldREPLYpocket
[–]EssentialOfficial 13 points 11 days ago
This actually turns out to be really hard technically. We're going to try to do more and more of this over time but ensuring you separate out any close source proprietary bits from the rest, but that things still work well is a big challenge. -Rebecca
Click to expand...
Click to collapse
Yes, I remember this. I was thinking when I first read that: Why don't they just open source the proprietary parts and problem solved? Rubin claimed this company is all about open source. That's part of his legacy with Android. He made a big point about how they are even open sourcing the hardware for module development. In fact, since they claimed the phone runs entirely stock Android I was suprised there even are proprietary parts. So to me rather than being an explanation, that was another example of the discrepancy between Essential's claims about what kind of company it is and the reality of the sort of company it really is.
cb474 said:
Yes, I remember this. I was thinking when I first read that: Why don't they just open source the proprietary parts and problem solved? Rubin claimed this company is all about open source. That's part of his legacy with Android. He made a big point about how they are even open sourcing the hardware for module development. In fact, since they claimed the phone runs entirely stock Android I was suprised there even are proprietary parts. So to me rather than being an explanation, that was another example of the discrepancy between Essential's claims about what kind of company it is and the reality of the sort of company it really is.
Click to expand...
Click to collapse
Not good.
cb474 said:
Looking at it, it actually says, " We'll be releasing our kernel and factory images in the next few days." So, it says, "the next few days." And yet that was eleven days ago.
Another example of playing fast and loose with what I think anybody's idea of "few days" would be. Hopefully it will come soon. My point is only that people should not place much faith in Essential's statements about timing. They have only made promises and failed to keep them, just about without exception. It is not a good track record and part of why after my initial hopes and excitement about Essential, I now view them as an "essentially" dishonest company whose intentions are much less honorable than they claim.
This would all be more or less par for the course, for a big corporation spouting empty PR. But Andy Rubin, when he first introduced the phone, did this whole song and dance about how they were going to be a different sort of consumer friendly company. I no longer believe that at all. I no longer even believe that Rubin believed it when he said it. I think it was PR and nothing more.
---------- Post added at 05:11 PM ---------- Previous post was at 05:04 PM ----------
Yes, I remember this. I was thinking when I first read that: Why don't they just open source the proprietary parts and problem solved? Rubin claimed this company is all about open source. That's part of his legacy with Android. He made a big point about how they are even open sourcing the hardware for module development. In fact, since they claimed the phone runs entirely stock Android I was suprised there even are proprietary parts. So to me rather than being an explanation, that was another example of the discrepancy between Essential's claims about what kind of company it is and the reality of the sort of company it really is.
Click to expand...
Click to collapse
Gotta have that special sauce... lol
cb474 said:
Looking at it, it actually says, " We'll be releasing our kernel and factory images in the next few days." So, it says, "the next few days." And yet that was eleven days ago.
Another example of playing fast and loose with what I think anybody's idea of "few days" would be. Hopefully it will come soon. My point is only that people should not place much faith in Essential's statements about timing. They have only made promises and failed to keep them, just about without exception. It is not a good track record and part of why after my initial hopes and excitement about Essential, I now view them as an "essentially" dishonest company whose intentions are much less honorable than they claim.
This would all be more or less par for the course, for a big corporation spouting empty PR. But Andy Rubin, when he first introduced the phone, did this whole song and dance about how they were going to be a different sort of consumer friendly company. I no longer believe that at all. I no longer even believe that Rubin believed it when he said it. I think it was PR and nothing more.
Click to expand...
Click to collapse
Lol well to look at it in a more positive light, I think the issue is he has a tendency to over promise and leave use twiddling our thumbs. Considering they are a relatively new company and are severely understaffed, the overpromising can be forgiven. However, when missing the said dates, there is barely any follow-up as to why the dates were missed leading to major concern for the customers. I think saying anything is better than silence. Like at least tell us that such and such update promised on such and such date has been moved.
On the plus side, during the AMA, VZW cert was promised and it was certified on the date promised. The recent security patch was released with bug fixes within a day of the Pixel. They have definitely improved thier presence on reddit which I think is a huge plus. They also have said on Twitter a couple hours ago that they are currently working on a Dev page for their website.
https://twitter.com/essential/status/912424863951810560
So calling them dishonest or not honorable or saying they aren't customer friendly I think is a bit of a stretch. I think they are still super swamped after getting knocked down from the initial release and are trying their darndest to get back on their feet so they can stay in the fight. Yes, I am giving them the benefit of a doubt but I think once Essential gets over this initial launch hurdle, promised timings will be a little more "on time" than they currently are.
flakko86 said:
Lol well to look at it in a more positive light, I think the issue is he has a tendency to over promise and leave use twiddling our thumbs. Considering they are a relatively new company and are severely understaffed, the overpromising can be forgiven. However, when missing the said dates, there is barely any follow-up as to why the dates were missed leading to major concern for the customers. I think saying anything is better than silence. Like at least tell us that such and such update promised on such and such date has been moved.
On the plus side, during the AMA, VZW cert was promised and it was certified on the date promised. The recent security patch was released with bug fixes within a day of the Pixel. They have definitely improved thier presence on reddit which I think is a huge plus. They also have said on Twitter a couple hours ago that they are currently working on a Dev page for their website.
https://twitter.com/essential/status/912424863951810560
So calling them dishonest or not honorable or saying they aren't customer friendly I think is a bit of a stretch. I think they are still super swamped after getting knocked down from the initial release and are trying their darndest to get back on their feet so they can stay in the fight. Yes, I am giving them the benefit of a doubt but I think once Essential gets over this initial launch hurdle, promised timings will be a little more "on time" than they currently are.
Click to expand...
Click to collapse
That is a more generous way to look at it.
It's true the Verizon thing is the one thing I'm aware of where they made a promise about when something would happen and did it. I didn't say they never kept their promises. I said they have simply failed to keep them just about without exception. They didn't really promise a specific time on the security updates, as far as I'm aware, but it is good that they did it right away. Anyway, there have been so many promises they have not kept that I'm underwhelmed by the one instance where they did.
But, for me, the thing really is they have been called out repeatedly on tech sites and even in the AMA about their promises and not keeping them. Instead of owning up to that, they just do it again. They have been called out even more on how bad the camera is, especially in low light, and how it's inferior hardware can never live up to the hype. And yet to this day their website still says: "That’s why we put so much effort into developing one of the world’s best phone cameras." And: "This results in stunning images that are rich in color and detail, even in low light." (CNET critized them for keeping this on their website.) The camera was also brought up in the AMA. Rubin's response was hand waving jibberish about "computational photography," which is a technical term for bull**** (isn't, after all, all digital photography "computational"). Rubin also said, " We are pretty happy with the hardware design of the camera," even though the inferior sensors they are using was public knowledge by then. Rubin as recently as four days ago claimed in Time Magazine (http://time.com/4950677/andy-rubin-essential-interview/) that the reviewers received phones with incomplete camera software and that caused the problems, but there have been subsequent updates. This was long after the reviews had been out, the updates had been issued, and all the reviewers said it made little to no difference. This is not honesty. That is engaging knowningly in PR bull and trying to obfuscate something.
It's one thing to overpromise. It's another thing to overpromise and when you are called out on it double down on the overpromising. Further, there is zero way that the engineers within the company who worked on the camera didn't know that they were using sensors that are not as good as the best camera phones, so they knowingly claimed to make "one of the world's best phone cameras" when they knew that couldn't be true. They released the phone with that camera anyway, because there was nothing (much) more to be done.
Lastly, yes they are small and overworked. That seems clear. But even here, in promotional events, over and over, they have hyped the fact that being small makes them more effective and efficient, because there are not a lot of layers of bureaucracy to go through to make decisions and get things done. Yet clearly, being small in Essential's case means there are a lot of things they don't have time to do that well (and may never have time). And they have never said, oh, we're small, be patient. They have said over and over, being small makes us better. So if they weren't out there promoting the benefits of being small in contradiction to the reality, it would be easier to forgive them on this account.
When you add it all up, I just don't buy that it comes down to a simple tendency to overpromise. As they say, fool me once, shame on you; fool me twice, shame on me. I think they are being knowingly dishonest or, at best, knowingly engaging in PR misdirection to try to mislead people about problems with the phone and company.
cb474 said:
That is a more generous way to look at it.
It's true the Verizon thing is the one thing I'm aware of where they made a promise about when something would happen and did it. I didn't say they never kept their promises. I said they have simply failed to keep them just about without exception. They didn't really promise a specific time on the security updates, as far as I'm aware, but it is good that they did it right away. Anyway, there have been so many promises they have not kept that I'm underwhelmed by the one instance where they did.
But, for me, the thing really is they have been called out repeatedly on tech sites and even in the AMA about their promises and not keeping them. Instead of owning up to that, they just do it again. They have been called out even more on how bad the camera is, especially in low light, and how it's inferior hardware can never live up to the hype. And yet to this day their website still says: "That’s why we put so much effort into developing one of the world’s best phone cameras." And: "This results in stunning images that are rich in color and detail, even in low light." (CNET critized them for keeping this on their website.) The camera was also brought up in the AMA. Rubin's response was hand waving jibberish about "computational photography," which is a technical term for bull**** (isn't, after all, all digital photography "computational"). Rubin also said, " We are pretty happy with the hardware design of the camera," even though the inferior sensors they are using was public knowledge by then. Rubin as recently as four days ago claimed in Time Magazine (http://time.com/4950677/andy-rubin-essential-interview/) that the reviewers received phones with incomplete camera software and that caused the problems, but there have been subsequent updates. This was long after the reviews had been out, the updates had been issued, and all the reviewers said it made little to no difference. This is not honesty. That is engaging knowningly in PR bull and trying to obfuscate something.
It's one thing to overpromise. It's another thing to overpromise and when you are called out on it double down on the overpromising. Further, there is zero way that the engineers within the company who worked on the camera didn't know that they were using sensors that are not as good as the best camera phones, so they knowingly claimed to make "one of the world's best phone cameras" when they knew that couldn't be true. They released the phone with that camera anyway, because there was nothing (much) more to be done.
Lastly, yes they are small and overworked. That seems clear. But even here, in promotional events, over and over, they have hyped the fact that being small makes them more effective and efficient, because there are not a lot of layers of bureaucracy to go through to make decisions and get things done. Yet clearly, being small in Essential's case means there are a lot of things they don't have time to do that well (and may never have time). And they have never said, oh, we're small, be patient. They have said over and over, being small makes us better. So if they weren't out there promoting the benefits of being small in contradiction to the reality, it would be easier to forgive them on this account.
When you add it all up, I just don't buy that it comes down to a simple tendency to overpromise. As they say, fool me once, shame on you; fool me twice, shame on me. I think they are being knowingly dishonest or, at best, knowingly engaging in PR misdirection to try to mislead people about problems with the phone and company.
Click to expand...
Click to collapse
I remember reading somewhere that someone messaged customer service and the rep said they would try to release the patches within two weeks of google's release.
I agree with you about the camera and how they are handling it. I think the AMA question should have been worded a bit more differently like "You claim to have one if the best cameras in the world but you are using a 2 year old sensor that is known to have problems with capturing images in low light. Other competitors at this price range such as the Google Pixel and the Samsung Galaxy S8 have far superior sensors. Can you really optimize the software that much to compete with them?". Something like that. Anyways, I forgot which reviewer stated it but there's a lot of hubris coming out of this company and I think that's what's causing them to have that "do no wrong" attitude, and Im not a big fan of it.
As for them being a small company, while the downside is not being able to handle handle thousands of orders and customers efficiently especially with a rushed buggy product (of course they will never admit that cuz hubris), im finding more recently that they are starting to frequent Reddit more often and I was assured when I sent the big bug report out, which was responded to in less than a day, that the company monitors the essential subreddit religiously and the software team is and will be referencing that thread. They aren't wrong in their statement about them being a smaller company. They just gotta shoot the issues and suggestions straight to the top making decisions a lot more efficient than a larger company. All I'm saying is let the dust settle from the launch and see how they deal with it the upcoming months
Maybe they'll do better the second time around when they make another phone.
Sent from my SM-G950U using XDA-Developers Legacy app
That's how OnePlus was.... their OPO launch was pretty horrible. They're doing much better now. Still with some hiccups but definitely much better than when they launched their first phone.
canynballa said:
Maybe they'll do better the second time around when they make another phone.
Click to expand...
Click to collapse
Yes, I agree, what will really be telling will be if they incorporate any of the criticisms of the Ph-1 into the Ph-2 (assuming there is a Ph-2).
I received this reply this morning. No dates, but it sounds encouraging.
Erich T (Essential Products)
Sep 27, 9:32 AM MST
Hi Mark,
Thank you for reaching out.
We are going to support the 3rd party developer community by releasing our kernel and factory images. These will be made available soon, but I don't have a confirmed date at this time.
I don't know at this point where they will be uploaded to, but please stay tuned to Essential.com, and our social media channels for announcements.
If you have any further questions, please don't hesitate to reach back out to us. Have a great day!
Sincerely,
Erich
Essential Customer Experience Team
Related
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?
Had an idea last night to expand the #NeverAgain Movement. Not sure what that is? (SEE THIS THREAD).
I want to create a consumer advocate blog/site. It will revolve initially around Samsung of course and their total failure to listen/support their consumers.
I am only asking for feedback on what you guys think will help the most. I need ideas on how to do the site (I have no skills in this regard). I am leaning towards a wordpress blog/site. I also need your sentiment on Samsung and their errors.
Planning to point out the errors of Samsung (feel free to post your ideas) and will ask for support by using ALL MANNERS OF SOCIAL MEDIA TO MAKE OTHER CONSUMERS AWARE OF HOW SAMSUNG treats their consumer.
Last time Samsung admitted they heard our voice, they then released Froyo very shortyly afterwards. Only problem is, DID THEY?
They shut us up, but I'm starting to think the Mini Kies was to stop their bleeding. Their Twitter accounts, facebook page, and the articles written by some large sites certainly hurt them. NOW I am concerned this will not be treated as an "official" release since it was not OTA... hence why source has not been released yet (my opinion). Our developers need this, and Samsung needs to know we take the Open Handset Alliance seriously. I know they have 60 days to release... but what if mini kies was not official... we could be waiting forever.
Well, I think we need to shoot back harder than last time. I will be working on the site and could really use yall's help. Thing is, I will probably use the site for future issues... consider it a site for consumer advocacy... not just to bash samsung.
Ideas, thoughts?
If you do not agree, fine... if you feel so strongly to post, fine... but do not ruin my thread by being a troll. I will respect you, respect XDA in return.
The thing that worries me is that the international galaxy s units never got a OTA release for froyo (kies) but did get source code released. To ME official release is anything that comes directly from Sammy for the general public, such as the case for kies mini.
I hope I am wrong in my assumption, but Samsung constantly surprises me.
While I commend your spirit, I think sammy will only listen to one thing... sales numbers... And right now they have no real reason to change.
For me my next phone will be HTC, LG or Moto. I'm done with sammy.
^ It's like you understand, and you don't.
Thats the point.. we are telling Sammy we will #NeverAgain buy their product unless they can prove they will support the consumer/Android/developer/OHA...
I agree, that IS the one thing they will care about.
I was floored at how well the movement worked last time, I had a LOT of article links sent to me... dont underestimate the power of social media. I did before this.
Consumerist.com is a very large, non-profit consumer advocacy site.
My biggest thing about techy type complaints, is you guys (and myself included sometimes) get distracted off with shineys and get off subject of the original real issue.
The source + developers does not matter. What matters is the 60 day timeline, the lack of phone support, the reoccuring glitch issues, and GPS problems. This is all documentable, proven issues that normal people would run into.
s15274n
You know, I would wait until they deliver the Source Code first before we make a move. Xplane9 is right, International Galaxy S has gotten the code and they never had OTA, but an "Official" update thru Kies. Like ours.
Or better yet, we make our mark a week before their deadline of the release of the code, if it hasn't been released yet. I9000 users got the source around 30 days (avg of 35 days). It's been, what? Almost a month since that leak from CNet of a CEO or something that said, we will get the update? So lets see first...
Too early to make a big move. Just imagine how much people out there here in the States are pissed at Samsung. Remember #NeverAgainSamsung? It blew up overnight. We'll do that again if they're releasing the source on the deadline.
My 2cents
^^
Agreed. No need to jump the gun. They still have time before the deadline to release the source.
Sent from my SGH-T959 using XDA App
I think they will release it in a week or two, if not then we start the crusade up again
Sent from my SGH-T959 using XDA App
I think your idea is good, you should do it. However the consumerist already exists, but always room for more.
Also, OTA just means it was delivered over the air, instead this time they chose Kies Mini to make the delivery. I do think this was "official" and I don't think it has to be delivered OTA to be "official."
The only only only thing that worries me about it being "official" is T-Mobiles wording that this is "optional" and "not required." Hmmmm
Nevertheless, those who choose to update using kies mini, then for those users, this is "official froyo."
s15274n said:
I hope I am wrong in my assumption, but Samsung constantly surprises me.
Click to expand...
Click to collapse
No doubt about it:
1. Samsung Galaxy S 4G announced before MWC, basically original Vibrant with a 4G antenna and FFC, minus spacious internal SD.
2. Samsung Galaxy S2 will be announced at MWC.
3. Samsung Galaxy SL is a Galaxy S budget device??? Sporting SLCD and a Texas Instruments CPU.
So I don't know about you guys, but I am tired of waiting for ICS. Even more so I am tired of there being not a word spoken about the progress of the update from Google, Sprint, or Samsung. Being that I am still paying the phones subsidized price to Sprint with my monthly payments, I have taken my complaints to their official forum.
http://community.sprint.com/baw/community/buzzaboutwireless/phones-and-devices/samsung/nexus_s_
I encourage all of you that are tired of the silence of these companies to please join me on Sprints forums and voice your complaints. Maybe if enough of us speak up someone will realize it is better to have transparency even when things go wrong.
*I know some of you will say quit complaining and flash a rom. I know what my options are, but that does not excuse these companies for treating us the way that they are. Sprint should not be advertising the Nexus S 4G as receiving "OS updates as soon as humanly possible"*
I've been wondering this for a while.. when the ota update comes out, do you (as in everyone who's waiting for it) plan on using it?
Drop w/e custom ics rom you might have with performance tweaks, themes, status bar toggles, settings you'd never get in a stock rom, etc. etc.?
"treating us the way that they are"? Maybe you've forgotten that Google pulled the first ics update because of issues, and they already have 4.0.5 planned, ics is obviously having issues.
Don't get me wrong, i can definitely understand the frustration with no news about anything at all. I can see your reasoning for complaining to Sprint about that.
i dunno, I'm just curious as to why everyone is freaking out over it. imo they should be pestering Google to release the 4.0.4 source for us to fix some things in our roms, instead of bothering the carrier
Sent from my Nexus S 4G using Tapatalk
kyouko said:
I've been wondering this for a while.. when the ota update comes out, do you (as in everyone who's waiting for it) plan on using it?
Drop w/e custom ics rom you might have with performance tweaks, themes, status bar toggles, settings you'd never get in a stock rom, etc. etc.?
"treating us the way that they are"? Maybe you've forgotten that Google pulled the first ics update because of issues, and they already have 4.0.5 planned, ics is obviously having issues.
Don't get me wrong, i can definitely understand the frustration with no news about anything at all. I can see your reasoning for complaining to Sprint about that.
i dunno, I'm just curious as to why everyone is freaking out over it. imo they should be pestering Google to release the 4.0.4 source for us to fix some things in our roms, instead of bothering the carrier
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Pestering Google would be the more direct approach for sure. But they already got their money for these phones. Sprint on the other hand I am still paying and will continue to pay (if I don't move to another carrier). So Sprint seems to be the more logical source to complain to and maybe if enough people pester them, they will in turn force Google to be more transparent. Because as is, it looks like Google could give a ****.
Ah alright, that makes more sense to me now. Thanks for the response
Sent from my Nexus S 4G using Tapatalk
kyouko said:
I've been wondering this for a while.. when the ota update comes out, do you (as in everyone who's waiting for it) plan on using it?
Drop w/e custom ics rom you might have with performance tweaks, themes, status bar toggles, settings you'd never get in a stock rom, etc. etc.?
"treating us the way that they are"? Maybe you've forgotten that Google pulled the first ics update because of issues, and they already have 4.0.5 planned, ics is obviously having issues.
Don't get me wrong, i can definitely understand the frustration with no news about anything at all. I can see your reasoning for complaining to Sprint about that.
i dunno, I'm just curious as to why everyone is freaking out over it. imo they should be pestering Google to release the 4.0.4 source for us to fix some things in our roms, instead of bothering the carrier
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
No, I would never give up my mods & tweaks, etc....but I would love to have a stock rom with all those tweaks, mods, themes, kernels, etc. added on to it. IMHO, stock roms are almost always stable beasts! Honestly, at this point, I am doubting whether or not sprint even cares enough to let us know what's going on with the update. We're now over 2 months since the first official ota was pushed to nexus s and the devs here have already beaten the bloody hell out of sprint in releasing working roms, with brand new radios, bootloaders, and all. Granted, the bootloader & radio were ripped from a leaked rom, but still....we've got over a dozen working roms before the people who have full access to schematics, closed source code, etc. could even get one out.....and that's just plain sad!!
Has anyone gotten this OTA yet? I can't even find one person that has. It's making me think that it was a false leak, maybe that's already well known though...
patokeefe said:
Has anyone gotten this OTA yet? I can't even find one person that has. It's making me think that it was a false leak, maybe that's already well known though...
Click to expand...
Click to collapse
Umm.. Its called a leak because it was err.. leaked... It was an OTA update that wasn't released yet and still hasn't been. Doesn't make it a false leak, just means they still aren't ready to release it.
Sent from my Nexus S 4G using Tapatalk
Is he possibly talking about the leaked release date of the ota ics update, the one of the screenshot from a Sprint webpage showing Sprint saying the update will be released on February 16th???? I think he might have been asking if anyone got the ota update that this was showing. I personally think that it was a misprint and the update will be released on March 16th, as there is another leaked piece saying the NEXUS S update will be released in mid March.
KID ANDROID said:
Is he possibly talking about the leaked release date of the ota ics update, the one of the screenshot from a Sprint webpage showing Sprint saying the update will be released on February 16th???? I think he might have been asking if anyone got the ota update that this was showing. I personally think that it was a misprint and the update will be released on March 16th, as there is another leaked piece saying the NEXUS S update will be released in mid March.
Click to expand...
Click to collapse
Exactly.
I should clarify, the substance of the leak-the date if the alleged OTA update-was false.
Sent from my Nexus S 4G using Tapatalk
Looks like Sprint is still sytematically deleting posts of their users and paying customers on their forum.
Go here and see before it is deleted: http://community.sprint.com/baw/thread/85388?start=0&tstart=0
"Nexus S 4g and ICS-where is it?
Why were these posts deleted? Why are you still trying to hide what is going on instead of answering my questions? There was nothing in these posts that was your content to delete. markie_b stated that posts that had Sprint property (screenshots) were deleted because of that, but why are these deleted?
POST 1
"@markie_b "the opportune word here is leaked which means someone is putting information out there before it is due and therefore Sprint has the right to delete any information"
Just because it was leaked does not make it any less true. There was a banner at the top of the page when Sprint employees logged into Dara and ISC. It was there for two days at least. Many different Sprint employees confirmed this as true. So deleting the screenshot and links to this image just makes it look like Sprint is trying to hide something. Which you are. Sprint messed up. Plain and simple. Maybe you guys should admit this and try to give us more information than just wait for ICS because we know nothing. We all know you and every other Sprint employee know nothing. You guys should work on changing that. Instead of hiding mistakes and staying silent on what is going on with an update, you should be proactive in letting us know every step of the process you are on in geting the update out. The source has been available for 3 months now, that is more than enough time to get the radios working. As I have said before we are all still paying Sprint for these phones. We deserve to be treated better. On a side note you should realize the Nexus is a developer phone. You are not dealing with your average Android phone users here. We will notice every single mistake you make and come looking for answers every time.
@aysdojo Why would you think it was an internal release? How many Sprint employees do you think still even own an NS4G? On top of that there is no system in place for Sprint to only push updates to Sprint employees. So how would they even accomplish an internal release?
@14knight So would you mind explaining why another post created by mattsholtz23 that asked why Sprint is advertising the Nexus S 4g as "OS updates as soon as humanly possible" were outright deleted and the member banned? There was no "leaked" information in that post. It was a simple question that was deleted instead of just being answered. It look like Sprints policy is to delete any post on here that makes them look bad. Instead of being up front and admitting when they do things wrong. A screen shot has been taken as proof of this post."
POST 2
"I must assume that you have trouble reading, as all proof needed was inside of last post. You must realize that you are asking for proof of things that do not exist, i.e. a way for Sprint to roll out releases only to employees all the while excluding every other NS4G owner on their network. This is like asking someone to prove that Santa Clause does not exist. The proof he does not exist is that no one has ever proven that he does exist. The same goes for Sprints secret employee OS upgrade system that you somehow beleive in. Like I said before, it would have been heard of by now through employee leaks, considering that the OP is about Sprint internal leaks this is something Sprint has a problem with. Also of note is that the one internal rollout you cited from Google had leaked screenshots of ICS (I guess you would have had to of read the article though) hitting Google+ and Twitter within hours of the actual rollout to employees. Further illustrating my point. I would also like to point out that I have answered your questions twice now with you still never answering my one question to you. Why do you believe this was an internal rollout? Any other post by you will be ignored as I must assume you are trolling and are hijacking the thread, considering your last 2 posts have not had a single fact in them and were all opinion, and that you never answered my one question to you. Now back to the real questions I would like to see answers to. I am still waiting Markie_B and 14Knight."
A screenshot has been taken as proof of this post, as have all my other posts."
And another one that was deleted:
"@dreamcat1138 You are correct. Not only does the NS4G have weak radio problems, but it is all Samsung devices that have signal issues. Samsung is notorious for using under powered radios inside of it's handsets. http://www.androidcentral.com/nexus-s-users-hows-your-wifi-strength http://www.androidcentral.com/are-you-having-radio-issues-your-nexus-s-4g-poll http://www.google.com/support/forum/p/Google+Mobile/thread?tid=34ad876196cb21c4&hl=en http://www.google.com/support/forum/p/Google+Mobile/thread?tid=72cde4a29b9021c3&hl=en http://forums.androidcentral.com/sp...e-wifi-radio-wifi-tethering-crashes-data.html Tweet from Engadget's Mobile editor - https://twitter.com/#!/zpower/status/15800092652998657 http://forums.whirlpool.net.au/archive/1714413 http://pocketnow.com/android/samsung-epic-4g-touch-hits-radio-problems-fix-promised http://pocketnow.com/android/epic-4g-touch-signal-loss-fix-coming-soon-user-leaks-it-early http://code.google.com/p/android/issues/detail?id=24345 http://www.theverge.com/2011/12/21/...signal-problem-fix-coming-meter-being-changed Trust me I could go on. Basically all Samsung devices including the Nexus S 4G have horrible radios. Just look at some of the other posts in Sprints Nexus S forum. There are more than one post asking when the radios would be fixed on the NS4G, and they always have the same answer. It's in the next update. Yet with the last 3 update the NS4G recieved that were supposed to fix the radio issues, they never did. And now we are being told it will be in the ICS update. That is untrue as there is no fix for the radio ssues, it is a hardware issue, and the only fix for that is not buying a Samsung phone. Screenshots have been taken as proof of this post."
Here are even more that were deleted.
"Why was the screen shot and link to the image of the leak deleted? Why does Sprint feel that hiding their mess ups is gonna help? It is all over the web, we already know. Why don't you take the time to admit your mistakes and tell us what is going on, instead of deleting posts banning members and deleting pictures. Is this really Sprints stance, to hide facts and lie to it's paying customers? Every person on this Nexus board is still paying for their phones with their contracts. Why are we being treated this way? Screenshots have been taken as proof of this post."
"So you don't believe everything you read on the internet, yet you believe the rumor one guy (not a Sprint employee) posted on this forum that this was an internal rollout. As that one guy (techguy379) is the only and original source that this was an internal rollout, and looking at his other posts, he knows absolutely nothing about what Sprint is doing. Not to mention that if it was an internal rollout wouldn't the Sprint employees who leaked these screen shots have known that, as they are internal employees. I personally know for a fact that one of the screen shot leakers/posters was himself an NS4G owner, wouldn't it make sense that he would have been one of the internal testers, since he owned the phone the test was taking place on and was himself an internal employee of Sprint? The proof that Sprint or any other prvider has never done an internal rollout to test an OS on their employees is that we would have heard about it, on Twitter, Facebook, and XDA. Do you really think Sprint could control leaks from their 18 year old work force. Most companies can't even control leaks from their programers and coders. Come on. You also just proved yourself wrong, as Google is the only company that does internal rollouts of Android to test OS updates. Since they are the ones who make it. There has and never been a single reported case of a service provider (Sprint, Verizon, AT&T, T-Mobile) ever internally testing an OS update on their work force, and that is because they don't. Really you are just making yourself look silly. I am sure Sprint can take care of defending themselves without your ill informed help."
*update* Looks like nexuss4glies was banned and most posts deleted.
Here is a full account of what is going on at Sprint's forums.
http://sprintlies.tumblr.com/
Here is a reddit link as well http://www.reddit.com/r/technology/comments/pyaow/a_full_record_of_how_sprint_is_deleting_its_users/
Your sense of entitlement is ridiculous at this point.
These updates take time, there is a massive amount of testing that has to happen before you release an update that could potentially brick hundreds of thousands of phones in one day. When working with a wireless carrier they must also test to make sure the radio is working properly with the network as well, in a variety of environments and situations.
If any problem comes up during these tests it has to start over again, if google has decided that 4.0.5 needs to be developed before they can re-test it, it's up to them. Google has never once stated a release date for ICS on our phones, sprint had it on an internal website for employees only (which could be a fake shot), not out there for public consumption. It's likely they are testing it internally and still awaiting approval somewhere down the line.
Just calm down, or just install the leak if you are really truely that desperate. The OTA will come out in due time and you'll look back at this and wonder how you could be so unreasonable.
They are releasing it as fast as humanly possible. Humans make mistakes, bugs can sometimes regress and appear again. Humans are flawed, humans write flawed code. Would you rather have a broken update or one that's stable enough to roll out to everyone?
Google, Sprint, and AT&T could all handle this better with some actual communication. However, I don't think any of them are holding back ICS intentionally. They are obviously working out issues and when they feel it is ready, they will release it. I'm not sure what the original poster is trying to gain by this crusade.
bozzykid said:
Google, Sprint, and AT&T could all handle this better with some actual communication. However, I don't think any of them are holding back ICS intentionally. They are obviously working out issues and when they feel it is ready, they will release it. I'm not sure what the original poster is trying to gain by this crusade.
Click to expand...
Click to collapse
I am trying to gain some transparency. I never stated that I thought ICS was being held back. But lets face it, there is no money in updating phones. The money is in selling them. I do believe that if more resources were put into development of updates it would result in faster updates. You would think this would be a priority for Google, at least with their flagship line of Nexus phones. Really, if this is what the "Nexus Experience" is supposed to be, then I am not on board. Second Sprint should have never sold this phone as a Nexus experience with "updates as soon as humanly possible" because the NS4G is not updated like the other GSM devices. Even Google has pulled CDMA Nexus's from it's Nexus developer page basically admitting that the update process works differently than the real (GSM) Nexus devices. I have a feeling this will all be happening again in a year when updates are needed for the Verizon and Sprint Galaxy Nexus.
My main goal is to draw attention to Sprint's and Google's mistakes as this whole process couldn't have been any more messed up. The more people that start criticizing these companies when they blatantly screw up the better off we will be in the long run. Staying silent for this long is just not the right way to be treating your customers. Especially when those customers are mainly the developers (Nexus devices are developer phones) who bolstered your OS to the number one OS in the world.
petrochemicals said:
My main goal is to draw attention to Sprint's and Google's mistakes as this whole process couldn't have been any more messed up. The more people that start criticizing these companies when they blatantly screw up the better off we will be in the long run. Staying silent for this long is just not the right way to be treating your customers. Especially when those customers are mainly the developers (Nexus devices are developer phones) who bolstered your OS to the number one OS in the world.
Click to expand...
Click to collapse
I don't think creating a blog full of screenshots of you ranting at community managers (that have no sway or special information, or right to speak on sprint's behalf) is helping at all.
Explain what you think 'as fast as humanly possible' means in the context of a highly complex and sensitive phone software rollout. There is a lot that could go wrong and delay an update, you know the update is coming. You are not paying a monthly fee for updates to your phone, find me the line in your phone contract that says that. A line on a product's website isn't a contractually binding agreement, maybe false advertising. If you wanted to prove that however you'd need proof that google and sprint engineers weren't even working on porting the software, and we know they are.
IMHO this is a little silly. Why does it even matter at this point? Almost every single ROM that is developed or being developed is ICS. We already have it so why would we need ota?
Sent from my Nexus S 4G using xda premium
Bauxite said:
I don't think creating a blog full of screenshots of you ranting at community managers (that have no sway or special information, or right to speak on sprint's behalf) is helping at all.
Explain what you think 'as fast as humanly possible' means in the context of a highly complex and sensitive phone software rollout. There is a lot that could go wrong and delay an update, you know the update is coming. You are not paying a monthly fee for updates to your phone, find me the line in your phone contract that says that. A line on a product's website isn't a contractually binding agreement, maybe false advertising. If you wanted to prove that however you'd need proof that google and sprint engineers weren't even working on porting the software, and we know they are.
Click to expand...
Click to collapse
Yes it is false advertising. The Nexus S 4G was falsely advertised by Sprint to me and everyone else when purchasing it, as receiving "OS updates as soon as humanly possible". As for the definition I would consider it to be defined as the first time they released the OS back in December of last year. Google is to blame for making a shoddy OS that didn't work when it was released. If they would bother actually putting any real kind of money into the development and work force that does design these updates, then maybe it would have worked the first time they released it. But like I said before there is no money in updates, so the development of them will reflect that. Just like we have seen here.
Why you feel the need to protect billion dollar companies, I am not really sure. Any kind of company like these should be criticized constantly, otherwise they will walk all over us, just as they are in this situation. The bottom line is Sprint and Google have screwed up. The more attention that is drawn to that fact, the better. More transparency is needed in Sprint and Google's relationship with their customers and that is not going to be fixed by people like you that are making excuses for them.
petrochemicals said:
Google is to blame for making a shoddy OS that didn't work when it was released. If they would bother actually putting any real kind of money into the development and work force that does design these updates, then maybe it would have worked the first time they released it. But like I said before there is no money in updates, so the development of them will reflect that. Just like we have seen here.
Click to expand...
Click to collapse
And you just lost the argument entirely. Android 4.0 was developed for one phone at the start, the Galaxy Nexus, they stated it would come to the Nexus S eventually. Your argument is that the software is crap because they haven't written the device drivers fast enough for you. You want them to release broken software because you are entitled to fast updates.
Apparently to you 'as fast as humanly possible' means something entirely different, where humans are perfect creatures that never make coding mistakes. And on the off chance that the code was perfect to start it still takes time to TEST, time that has paid off already because they would have released a buggy update.
You can't just hire more engineers and throw more money at something to make it go faster. You assume your monthly WIRELESS USAGE fees go towards software development for one of sprint's 20+ phones. They don't.
Get over your false entitlement, they don't owe you anything.
lol @ people getting angry over ICS not being released yet
.... clearly you didn't have an Epic 4g and have to wait from September to March of the next year for Gingerbread.... we have nothing to complain about here in the NS4g forums
Quite honestly, yes the wait sucks, but it'll be worth it to not have the same type of bugs as NS3G users on TMobile and other international carries are facing. I used OICS then went back to gingerbread in December and have been waiting until the official OTA because I know it'll be better than ANY of the roms we have yet! Yes Sprint sucks, but they're trying to protect us. Also, as aforementioned by snowmanwithahat, at least we aren't like Epic 4G users and waiting 6 months or the other countless people in 2 year contracts not even on GB. Plus, no other phone that isn't a Nexus S has gotten the OTA yet so until then I'm still happy. I will, however, be furious if any other Sprint phone gets it first... Just my 2 pennies...
I'm sure for many people, the last 24 hours has sucked in regards to SHIELD. I know for me it has. And even more frustrating is the lack of communication and transparency that should be expected from a large corporation who cares about its customers. Obviously, I feel the anger and frustration that is being vented both in the geforce forums and, to a lesser extent, over here on XDA. And I have no other outlet than XDA. First, and foremost, realize that the decision to delay the product, the reasons behind it, and the execution of the delay are unrelated. I, along with many, feel they really messed up on the execution of the announcement. Am I disappointed? Of course I am. There are hundreds of engineers around the world who have been putting in long hours for months (some of us, even over a year) to make this product. This is a passion for us. I, personally, involved myself into community aspects of the device. For example, I was one of the voices asking for the device to be unlockable. And NVIDIA didn't put up a fight for it, they agreed. Deep down, the heart of the company wants the best for everyone.
I'd like to answer a few questions that I ask myself, as a developer and a member of the XDA community:
1. Do you plan to run CM on the device, and why?
This is always a very important question for me while at work. This question is important because it represents all the shortcomings I feel exist in the product. But I'm not the average user, I'm an XDA member. That means that additional settings do not scare me. Ease of use can be reduced in the name of more advanced functionality. And Google Certification is a requirement that CM doesn't have. But I think deeply about every feature I want from a custom ROM, and what the product should do. Ultimately, yes, I plan to install CM. And it is because of the advanced tweaks available in CM that don't belong in a standard user device.
2. Do you think the device is worth it?
Do I think the device is worth the long hours, the stress, the loss of my personal development time (which is why I had to mostly drop the EVO 3D), and the time away from my kids? Obviously, that question also has the benefits I've gotten, like attending CES and Google I/O. But ultimately, I still work on it, and I still want it to be the best it can be. So the answer has to be yes.
3. This whole debacle is ridiculous, shouldn't I just cancel my pre-order? NVIDIA obviously doesn't know how to launch a product...
This comes back to the earlier message. Engineers build a product, marketing sells a product, and the company as a whole is represented by the product. The mistakes made in the messaging and delays don't represent the engineering and product, they represent a company which still has some lessons in releasing a customer product. It's easy to get emotionally wrapped up in it, because the disappointment so close to the release. And I'm not immune. If anything, I've also got the disappointment in the world finally getting to see what we've done and use it. That's why I'm writing this thread, because it helps me express my feelings in a constructive way.
4. What would you change?
I'm slowly becoming disenchanted with Google's AOSP design. While I love the product being so close to AOSP, it reminds me how ugly AOSP really is. I don't want something like Sense or Touchwiz. What I want is AOSP, but sharper looking and using the graphical power of modern devices. Does everything really need a flat gray look? TWRP looks ugly to me, compared to the install phase of 4EXT. Halo is outdated and sad-looking. I want glass effects, I want sharp text and lines. I want to feel like the display is sharp and crisp while in the launcher and settings. I want my settings to have tabs (like MIUI used to have, maybe still does?) for the different areas. But again, the goal is to line up with AOSP, which I can respect.
Ok, so I'm out of questions and I'm feeling a bit better. If you have questions for me, be my guest... I'll do my best to answer, and when I can't, I'll do my best to get an official answer...
agrabren said:
I'm sure for many people, the last 24 hours has sucked in regards to SHIELD. I know for me it has. And even more frustrating is the lack of communication and transparency that should be expected from a large corporation who cares about its customers. Obviously, I feel the anger and frustration that is being vented both in the geforce forums and, to a lesser extent, over here on XDA. And I have no other outlet than XDA. First, and foremost, realize that the decision to delay the product, the reasons behind it, and the execution of the delay are unrelated. I, along with many, feel they really messed up on the execution of the announcement. Am I disappointed? Of course I am. There are hundreds of engineers around the world who have been putting in long hours for months (some of us, even over a year) to make this product. This is a passion for us. I, personally, involved myself into community aspects of the device. For example, I was one of the voices asking for the device to be unlockable. And NVIDIA didn't put up a fight for it, they agreed. Deep down, the heart of the company wants the best for everyone.
I'd like to answer a few questions that I ask myself, as a developer and a member of the XDA community:
1. Do you plan to run CM on the device, and why?
This is always a very important question for me while at work. This question is important because it represents all the shortcomings I feel exist in the product. But I'm not the average user, I'm an XDA member. That means that additional settings do not scare me. Ease of use can be reduced in the name of more advanced functionality. And Google Certification is a requirement that CM doesn't have. But I think deeply about every feature I want from a custom ROM, and what the product should do. Ultimately, yes, I plan to install CM. And it is because of the advanced tweaks available in CM that don't belong in a standard user device.
2. Do you think the device is worth it?
Do I think the device is worth the long hours, the stress, the loss of my personal development time (which is why I had to mostly drop the EVO 3D), and the time away from my kids? Obviously, that question also has the benefits I've gotten, like attending CES and Google I/O. But ultimately, I still work on it, and I still want it to be the best it can be. So the answer has to be yes.
3. This whole debacle is ridiculous, shouldn't I just cancel my pre-order? NVIDIA obviously doesn't know how to launch a product...
This comes back to the earlier message. Engineers build a product, marketing sells a product, and the company as a whole is represented by the product. The mistakes made in the messaging and delays don't represent the engineering and product, they represent a company which still has some lessons in releasing a customer product. It's easy to get emotionally wrapped up in it, because the disappointment so close to the release. And I'm not immune. If anything, I've also got the disappointment in the world finally getting to see what we've done and use it. That's why I'm writing this thread, because it helps me express my feelings in a constructive way.
4. What would you change?
I'm slowly becoming disenchanted with Google's AOSP design. While I love the product being so close to AOSP, it reminds me how ugly AOSP really is. I don't want something like Sense or Touchwiz. What I want is AOSP, but sharper looking and using the graphical power of modern devices. Does everything really need a flat gray look? TWRP looks ugly to me, compared to the install phase of 4EXT. Halo is outdated and sad-looking. I want glass effects, I want sharp text and lines. I want to feel like the display is sharp and crisp while in the launcher and settings. I want my settings to have tabs (like MIUI used to have, maybe still does?) for the different areas. But again, the goal is to line up with AOSP, which I can respect.
Ok, so I'm out of questions and I'm feeling a bit better. If you have questions for me, be my guest... I'll do my best to answer, and when I can't, I'll do my best to get an official answer...
Click to expand...
Click to collapse
thanks man!
am i sad about the delay? yeah a little. but i respect Nvidia as a company and I know they can deliver. and if they need an extra month(or 4) to do so, im perfectly ok with it. from the gpu's to the specs to the videos, websites and drivers.. i love almost everything about Nvidia and a botched release date is NOT going to make me cancel my pre-order.
I hope nvidia uses this time to add/optimize a few extra streamable games
Excuse me for the non-Shield related question, I just wanted to know if you definetly dropped the EVO 3D or in future you probably come back..of course you don't have to give a single explaination to anybody, but if you won't develop anymore for evo, probably I will change device because there isn't a fully functional and stable rom (with or without 3D) with a new version of jelly bean and I have to stuck on the old Android 4.0..I appreciate the efforts that many developers are still making for this quite-old device, but some bugs probably won't never be fixed without you (i'm talking about battery drain, bootloops..).
Sorry for the off topic..
I know delays can happen. What frustrates me is the short notice and the fact that specs in the mobile world get outdated in about 6 months. I want this device while it is the cream of the crop as far as specifications are concerned. I don't think it was a coincidence that Gamestop had the release date listed as 6/30 for awhile.
Evo_Shift said:
I know delays can happen. What frustrates me is the short notice and the fact that specs in the mobile world get outdated in about 6 months. I want this device while it is the cream of the crop as far as specifications are concerned. I don't think it was a coincidence that Gamestop had the release date listed as 6/30 for awhile.
Click to expand...
Click to collapse
The 6/30 release date was because we listed "by the end of June" as our target launch date before we made had set a hard launch date. So GameStop did the obvious: June has 30 days, so it ships June 30th.
gigsaw said:
Excuse me for the non-Shield related question, I just wanted to know if you definetly dropped the EVO 3D or in future you probably come back..of course you don't have to give a single explaination to anybody, but if you won't develop anymore for evo, probably I will change device because there isn't a fully functional and stable rom (with or without 3D) with a new version of jelly bean and I have to stuck on the old Android 4.0..I appreciate the efforts that many developers are still making for this quite-old device, but some bugs probably won't never be fixed without you (i'm talking about battery drain, bootloops..).
Sorry for the off topic..
Click to expand...
Click to collapse
My future on the EVO 3D is on a feature-by-feature basis. As was pointed out accurately, since I don't run the OS as a daily, I don't see the issues like I did when it was my primary device.
Here's the petition on Samsung's software update policy for those who are tired of it. I request you all to please sign it, so we can raise our voice. After signing, don't forget to SHARE it.
Samsung Mobile : Software update policy of Shamesung - Sign the Petition!
https://www.change.org/p/samsung-mobile-software-update-policy-of-shamesung?recruiter=508463321&utm_source=share_petition&utm_medium=whatsapp
ammarwajihi said:
Here's the petition on Samsung's software update policy for those who are tired of it. I request you all to please sign it, so we can raise our voice. After signing, don't forget to SHARE it.
Samsung Mobile : Software update policy of Shamesung - Sign the Petition!
https://www.change.org/p/samsung-mo...utm_source=share_petition&utm_medium=whatsapp
Click to expand...
Click to collapse
Has any of those petitions ever produced a positive result?
Kamau54 said:
Has any of those petitions ever produced a positive result?
Click to expand...
Click to collapse
Don't know but we need to try at least.
ammarwajihi said:
Don't know but we need to try at least.
Click to expand...
Click to collapse
Good luck.
What is the point to be negative? If you want you can laid down and wait the dead. If someone can try, I wish the best. Simple.
Signed
Enviado desde mi SM-N920G mediante Tapatalk
Firstly not knocking the OP here just my view having been around a long time.
These petitions do nothing i remember seeing them about in the original note forum. Nothing has changed in that respect.
Secondly i have just returned to the note from a Nexus 6, and do you know what, i am glad to be back on Samsung software. Yes i had MM late last year but thats not always the greatest position to be in. as i felt i was an actual beta tester for most of that time, with odd things happening. SO samsung come out many months afterwards but let me tell you this, The MM i installed last week is a hell of a lot more stable than what i left with on the nexus range. So yes not first to the party but however i am happier having a stable feature rich software which means i can use my phone without fear of rebooting if it means i wait.
To be honest apart from Doze there is very little difference from LP, yes minor features here or there but nothing that would get me into os jealousy at all, i just wanted a good stable daily driver and we all have that. Will we get Android N who knows and to be honest ive got to the point where stock software is actually better than good enough and no longer feel the need to have the latest and have it now
Its just my opinion that suits my needs and i understand everyone is different, hell i used to be a must have it now os kinda guy but not any more, im just happy with what i have, and thats a stable feature rich os on a cracking device that performs everything i wont of it.
signed
Thank you those who are supporting.
ammarwajihi said:
Here's the petition on Samsung's software update policy for those who are tired of it. I request you all to please sign it, so we can raise our voice. After signing, don't forget to SHARE it.
Samsung Mobile : Software update policy of Shamesung - Sign the Petition!
https://www.change.org/p/samsung-mo...utm_source=share_petition&utm_medium=whatsapp
Click to expand...
Click to collapse
Its a bit whiney and you'd get better support and a better response by being positive.
Do you get sleepless night by a fw updated being delayed a few weeks? Really?? Sorry I'm not signing this one especially with a title like this.. It needs to be a little more focused and professional. For instance, I understand most phone makers offer updates for 18 months to 2 years and even then they don't say how they will be maintained.
HOWEVER what I would like to see is firms like Samsung issuing security updates more quickly and more regularly. Also why don't they package the security update enabling it to be distributed to ALL devices without having to customise each one?? Basic build standards I'd say.
Having the latest and greatest fw is fine - but it needs to work, and due to the fact they don't issue updates too often they need to get it right - hence peoples expectations aren't met. I say peoples expectations because Samsung don't issue exact dates - the press make them up. SO where are getting your info from??
I'd further add a security update is more important to me than receiving MM. The last update before MM was received on 11/11/15! Nexus received monthly updates....leaving our devices exposed to exploits.
Your intentions are good - just needs to be a little more specific, justified and a tad more professional.
Signed
Ok, enough with this stuff. Samsung is a multi billion dollar company. They will do whatever they want to do. Whenever they want to do it. Now, now instead of signing a petition. Why not stop buying the Samsung product. Use your head.
I'd rather wait for a solid update then a buggy one.
There is so much red tape involved with these updates. Different models, countries, different regulations, government, etc.
Then, if they screw it up, and your personal info is compromised, this opens up a huge liability issue.
It's far more complicated then most people realize. Things happen. Hell, the whole apple/fbi thing has all the manufacturers thinking and making changes.
Sent from my SM-N920T using Tapatalk
If you wanted rapidly released updates, you should have bought a Nexus. If you want leading edge hardware and solid reliable software, stick with Samsung.
I do wish the OP the best with this.
Unfortunately, I have seen many of these petitions, and cannot recall not one that gave the desired result. Besides, it's petitioning the government to intervene in a company and its operation. That alone will doom this petition.
Kamau54 said:
Has any of those petitions ever produced a positive result?
Click to expand...
Click to collapse
Signed
Sent from my SM-N920I using XDA Free mobile app
It's not only Samsung's problem and actually Google's design problem called "Fragmentation", just google it, you will find tons of stuff.
Nevertheless, Android N most likely will solve the problem. Android N is separating the partitions of Google Core and Vendor/Carrier Customization.
The advantage will be, same day Google core software update rollout in all devices without any dependency on Vendor/Carrier customization and vice versa.
Google for more details on Android N.
Fingers crossed....