http://www.androidcentral.com/asus-says-bootloader-unlock-tool-coming-gps-hard-yall
so, I know I personally am absolutely 100% enraged to read about this, since we still haven't heard anything about an official ota for NS4G.
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Ya, it is a bit disturbing.
Well, the work week just started back up for them, so maybe we will hear something in the next couple days?
hp420 said:
http://www.androidcentral.com/asus-says-bootloader-unlock-tool-coming-gps-hard-yall
so, I know I personally am absolutely 100% enraged to read about this, since we still haven't heard anything about an official ota for NS4G.
Click to expand...
Click to collapse
Sprint says we'll be "among the first" to updates, not "the first".
hp420 said:
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Click to expand...
Click to collapse
I'd be amazed if this is Google's doing.
Sprint's website says "It runs Android™ 2.3 (Gingerbread) the latest version of Android for smartphones." They're the ones that are clueopenic, not Google.
Don't get me wrong: I'm plenty annoyed at not getting OTA ICS. It's just that I don't actually expect Sprint to live up to their promises, since this is not something they've ever tended to do in the past. Sprint users go through this with every software update for every platform on every phone.
mstevens said:
Sprint says we'll be "among the first" to updates, not "the first".
I'd be amazed if this is Google's doing.
Sprint's website says "It runs Android™ 2.3 (Gingerbread) the latest version of Android for smartphones." They're the ones that are clueopenic, not Google.
Don't get me wrong: I'm plenty annoyed at not getting OTA ICS. It's just that I don't actually expect Sprint to live up to their promises, since this is not something they've ever tended to do in the past. Sprint users go through this with every software update for every platform on every phone.
Click to expand...
Click to collapse
The update does come directly from Google. Sprint works with Samsung to create proprietary hardware drivers that contain everything you need to access Sprint's cell phone network. These drivers are then made available in binary only form to Google. Google then adds these drivers to their official build. The final product is then delivered directly from Google to your Nexus S 4G phone.
Click to expand...
Click to collapse
this quote came from sprint community forums. http://community.sprint.com/baw/message/380145#380145
Sprint does NOT provide our update...google does. Google is falling behind, and they need to be held accountable for their screw-ups. Just because they didn't say "NS4G will be the first" does not make it acceptable for 3rd parties to get an update before they can even get off their lazy asses just to push a button for their OFFICIAL FIRST-PARTY USERS. Everything we need is on their server for download, and if devs here can get off their asses top compile this rom, google sure as hell can do the same!!!
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
mstevens said:
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
Click to expand...
Click to collapse
Source or GTFO. And we've already got the drivers, I'm using ICS on my NS4G right now. 4g and everything.
mstevens said:
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
Click to expand...
Click to collapse
lol...is that why every single file needed to build a FULL ics rom is already on the server??
I'm not saying you're wrong, but in my opinion, it does not look like it's sprint's fault. It looks like Google is either lazy about releasing it, or they are too dumb to build a rom that's working properly so it's stuck in pre-release testing. However, this is just my opinion....but as far as actually building/releasing the OTA, that is 100% on google's end. whether or not the authorization is coming/has to come from sprint is another story entirely....the point is, if that is the case, google isn't doing their jobs and telling them to screw themselves so they don't look like the bad guy in this!! It's not sprint who will have the damaged reputation after this is all said & done.
jesusice said:
Source or GTFO. And we've already got the drivers, I'm using ICS on my NS4G right now. 4g and everything.
Click to expand...
Click to collapse
<shrug> it's the way it's always worked.
This worked in our favor earlier when Sprint okayed deployment of Google Wallet on our devices and GSM users were foaming at the mouth to get it. In those cases, too, it wasn't Google (which has excellent reasons for getting Wallet into as many hands as possible) but the carriers which held up release.
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
hp420 said:
lol...is that why every single file needed to build a FULL ics rom is already on the server??
Click to expand...
Click to collapse
No.
What is the connection between having all the files on the server and Sprint's approval of a final release version?
In your earlier quote lifted from another site, the poster was saying the updates are pushed from Google's servers, not Sprints. That's correct. However, they can't just start pushing updates without carrier approval. This is why, for example, T-Mobile got ICS before ATT.
mstevens said:
<shrug> it's the way it's always worked.
This worked in our favor earlier when Sprint okayed deployment of Google Wallet on our devices and GSM users were foaming at the mouth to get it. In those cases, too, it wasn't Google (which has excellent reasons for getting Wallet into as many hands as possible) but the carriers which held up release.
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
No.
What is the connection between having all the files on the server and Sprint's approval of a final release version?
In your earlier quote lifted from another site, the poster was saying the updates are pushed from Google's servers, not Sprints. That's correct. However, they can't just start pushing updates without carrier approval. This is why, for example, T-Mobile got ICS before ATT.
Click to expand...
Click to collapse
that was a result of carriers' investment in other companies that developed very similar software to google wallet....exactly the same as when the GN was delayed for verizon because google wanted wallet on their official device and verizon had a coronary about it because they had already backed another company's software that does exactly the same thing.
as for carrier approval, google can only wait so long before they just snap and push the update anyway. carriers can not make the rest of the world wait for an update just because they don't want it released to their devices yet. Google needs to just ***** slap sprint, tell them to shut the hell up, and push the update before this damages their reputation any more than it already has. Like I said, it won't be sprint whose rep is damaged from all of this, just like no one looks towards verizon for the GN delay...the world will blame google, and they aren't even standing up for themselves.
hp420 said:
lol...is that why every single file needed to build a FULL ics rom is already on the server??
Click to expand...
Click to collapse
Sure, they could build ICS for the NS4G but the 4G radio wouldn't work. Drivers aren't part of AOSP.
Also, didn't Google pulled the ICS update for the (tmobile) Nexus S? If that's still true, they're clearly working out the issues with ICS before releasing it to the NS4G, etc.
It is most likely *not* Googles doing. I don't know where half of you get these crack pot ideas from that Google or any other OEM is in control over how and when they push an update.
- OEM builds ROM
- OEM submits ROM to carriers (i.e. Sprint branded phone would require Sprint to approve the update).
Carriers can be total dicks about updates and providing OTA. I've seen it all first hand from when I had a Motorola Milestone (Motorola telling us the 2.1 has been built and has gone through testing but they are waiting for carriers to approve them on their networks) we had to waiting months for the updates due to some carriers.
nside said:
Sure, they could build ICS for the NS4G but the 4G radio wouldn't work. Drivers aren't part of AOSP.
Also, didn't Google pulled the ICS update for the (tmobile) Nexus S? If that's still true, they're clearly working out the issues with ICS before releasing it to the NS4G, etc.
Click to expand...
Click to collapse
Driver binaries are on Google's servers for nexus devices. 100% built from source and 4g works just fine.....
Sent from my Nexus S 4G using xda premium
we are waiting for sprint to approve the new radio that will come with the ota. That is what causes the holdup.
Sent from my Nexus S 4G using xda premium
maybe Google is still fixing what does not go to ics now and then....maybe xD we can see ics on all nexus ^^
hp420 said:
that was a result of carriers' investment in other companies that developed very similar software to google wallet...
Click to expand...
Click to collapse
Precisely. I'm glad you finally see my point that Google can't just push out an update because they want to, but are hampered by needing carrier approval.
---------- Post added at 02:33 PM ---------- Previous post was at 02:28 PM ----------
hp420 said:
carriers can not make the rest of the world wait for an update just because they don't want it released to their devices yet.
Click to expand...
Click to collapse
When did this start being true?
It's absolutely true that carriers CAN prevent official release of an update for any reason, or for no reason. They've done it many times before and they'll do it again. Sprint has a long track record of doing exactly this.
hp420 said:
Google needs to just ***** slap sprint, tell them to shut the hell up, and push the update
Click to expand...
Click to collapse
You have an awfully lot to learn about how contracts work.
If I run a massive business and another massive business violates my contract with them (for example, pushes an unapproved update to what I think of as "my" devices irrespective of the beliefs or desires of my subscribers), many lawyers are going to be fed and I will expect a massive transfer of assets from that other company to mine.
mstevens is dead on. Sprint will not allow the push of an ota until they can be sure this update won't toast peoples phones, and for the people in the world that have a nxs4g and don't do modding, if the update is broken, they can't just fix what Google's update did. My brother has the GSM version, and received the update, and honestly were not missing anything. The user made roms are already becoming superior builds anyway. We will eventually get the update, I for one am glad sprint said no at the moment though, I would hate to waste my time on a broken ota lol
Sent from my Nexus IcS 4G using xda premium
lol...too many people to quote you all, so I'm gonna do my best to answer everyone
Ok, I understand how contracts work. My point is this: yes, google has a contract with sprint (or any other carrier, for that matter) to provide radios, wimax drivers, what-have-you, and I understand that if sprint won't sign, there's not much the manufacturer can do...I get that. But my biggest concern with all of this is that google is not flexing their muscles. They have made a guarantee to their customers (not explicit, but still implied) that they would provide ALL NEXUS UPDATES in a timely manner. Sprint is now holding google back from seeing this implied promise carried through, and the fact that other manufacturers are already pushing full ota updates now makes google look bad (grounds for a lawsuit).
I understand that if google were to break that contract by circumventing sprint by releasing the update anyway, they could be sued...I get that. However, google could also counter-sue for making customers wait an unreasonable amount of time for an update that is, by all rights, a "god-given right" to all nexus users prior to anyone else getting it.
Now let's talk about how many people use an NS4G to develop software that they get paid top develop. By sprint not releasing an official update, they are now inhibiting developers from doing business, and therefore they are taking money out of people's pockets. Yes, I know this last example is far-fetched a little bit, but honestly, it's really not all that far off. Yeah, people can just compile aosp themselves, and if they are truly developers, they should know how to do that....but let's say they are working on one particular app that is exclusive for sprint users, and they want to make sure it will run properly on sprint's network via an ICS handset....oh, wait...they can't because sprint are a bunch of lazy pieces of **** who won't sign. This is grounds for class-action, IMHO.
I may not be a lawyer, but it's blatantly obvious to me that if sprint holds out long enough, they are absolutely 100% vulnerable to class-action suits...and maybe even a suit from google, as well. Let's face it, no one but sprint & google execs really know the terms of the contract, but for all we know, it IS in the contract to provide timely updates. If this is the case, I hope someone gets sued like a SOB for this delay, because it's unacceptable!!!!!
hp420 said:
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Click to expand...
Click to collapse
I suggest that this LARGE chunk of nexus users may be better served by one of the many other smartphone mfrs who provided a pure ICS update (i.e. no BS extra UI layer and no bloat) over the holiday. Which one will you choose? Oh, wait.
hp420 said:
I hope someone gets sued like a SOB for this delay, because it's unacceptable!!!!!
Click to expand...
Click to collapse
Really. You want a lawsuit, because a bunch of software developers wouldn't work at your whim over the nation's biggest holiday?
The111 said:
I suggest that this LARGE chunk of nexus users may be better served by one of the many other smartphone mfrs who provided a pure ICS update (i.e. no BS extra UI layer and no bloat) over the holiday. Which one will you choose? Oh, wait.
Really. You want a lawsuit, because a bunch of software developers wouldn't work at your whim over the nation's biggest holiday?
Click to expand...
Click to collapse
actually, since the drivers, kernel, etc. was all pushed to google's update servers WELL over a week before christmas, they wouldn't have been working during the holiday at all to get it pushed to NS4g...they just had to click a few buttons....something I've done a few hundred thousand times in the last 5 minutes.
BTW, no need to be a smartass about it. if I want to switch from nexus to get a pure android ui, I can always just root and modify the ota to have a stock theme. So now what do you have to say about that, smartass??? Oh wait...
tool.
hp420 said:
actually, since the drivers, kernel, etc. was all pushed to google's update servers WELL over a week before christmas, they wouldn't have been working during the holiday at all to get it pushed to NS4g...they just had to click a few buttons....something I've done a few hundred thousand times in the last 5 minutes.
Click to expand...
Click to collapse
You're making multiple assumptions. You assume that by the existence of particular source files on a particular server, you know what Google's stance as to the public release candidacy of a compiled package is. Please explain why you believe this. There are only two ways we could know such a thing:
1) Google publicly declares it (i.e. this compiled package IS ready for public use... or vice versa)
2) Google actually pushes the compiled package (in the absence of such an action, the logical assumption to make is that they are not ready to do such a thing yet, for their own reasons... i.e. there is still something else they need to do. NOT that they are "too lazy/stupid to push a few buttons")
hp420 said:
BTW, no need to be a smartass about it. if I want to switch from nexus to get a pure android ui, I can always just root and modify the ota to have a stock theme. So now what do you have to say about that, smartass??? Oh wait...
Click to expand...
Click to collapse
You're right, the sarcasm is 100% optional. It's an option that I quite enjoy though. I won't, however, stoop to personal attacks.
How about this. Sarcasm removed for you, I will ask the question that was clearly evident in my last post. If you decide to "leave Google" because of your discontent, which handset vendor will you turn to? Who do you believe is a better option? Who will give you a pure Android update in a shorter timespan? I am genuinely (no sarcasm) interested!
Related
Will the phone get updates from Google or T-mobile?
I'm guessing neither. LG has a desktop app that they push updates through. Unless something's different with the G2X I'd assume they'll come through the LG app.
You could also get them from www.cyanogenmod.com!
jimbo831 said:
You could also get them from www.cyanogenmod.com!
Click to expand...
Click to collapse
Quoted for truth.
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
borchgrevink said:
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
Click to expand...
Click to collapse
You're looking at getting a Nexus S or Nexus One then. For those of us not willing to pay full price, and wanting better hardware, we have to deal with manufacturers instead.
MWBehr said:
You're looking at getting a Nexus S or Nexus One then. For those of us not willing to pay full price, and wanting better hardware, we have to deal with manufacturers instead.
Click to expand...
Click to collapse
I know, but this has more appealing hardware. I just don't get it if it really is LG pushing updates... Why not just let Google handle everything?
Yeah but the update has to go through tmo first before the release it, the have to make sure their crapware is in there.
Sent from my LG-P999 using XDA App
borchgrevink said:
I know, but this has more appealing hardware. I just don't get it if it really is LG pushing updates... Why not just let Google handle everything?
Click to expand...
Click to collapse
What I'm saying is no phone out there but the Nexus S or Nexus One has AOSP Android. Every other phone has a version modified by the manufacturer. Google has nothing to do with these changes. The only one who can release updates is the manufacturer (or service provider if the manufacturer chooses to send the update to them first).
That's just the way it is.
Are you opposed to rooting your phone and installing custom ROMs? If you are interested in that, CM will be your best bet by far as you get the best of both worlds (CM had Gingerbread on even the Nexus One before Google did!).
If you don't want to use unofficial software, you should stick with the Nexus line. Even pure vanilla Android devices get updates through the carriers, that is how it is and how it always will be. Nexus phones are different as they are not sold through the carriers, just designed to work on them. They are managed entirely through Google which means updates come from Google.
MWBehr said:
What I'm saying is no phone out there but the Nexus S or Nexus One has AOSP Android. Every other phone has a version modified by the manufacturer. Google has nothing to do with these changes. The only one who can release updates is the manufacturer (or service provider if the manufacturer chooses to send the update to them first).
That's just the way it is.
Click to expand...
Click to collapse
I was under the impression that the vanilla devices (like the G2x obviously) was AOSP. Do you know what is modified on this version by LG? I know there is preinstalled software, but that is different than changes to AOSP.
borchgrevink said:
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
Click to expand...
Click to collapse
LG's committed to before Summer. The O2X forum has them giving June as a time frame.
BarryH_GEG said:
LG's committed to before Summer. The O2X forum has them giving June as a time frame.
Click to expand...
Click to collapse
Just because they have the update for the O2x by June, doesn't mean the G2x will be ready. The two use different software, plus there are different expectations I think between the US market and European. I hope they come together, but I wouldn't be surprised if LG does the O2x first and then gets working on the G2x.
Bob from Wirefly.com said that he talked to someone from T-Mobile when he got the G2X for review and they said the 2.3 update was coming in one month. I'm not holding my breath, though.
Sent from my LG-P999 using XDA Premium App
scmurphy13 said:
Bob from Wirefly.com said that he talked to someone from T-Mobile when he got the G2X for review and they said the 2.3 update was coming in one month. I'm not holding my breath, though.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
LOL. "Bob from Wirefly" has the inside scoop, huh.
Don't ever believe anything somebody tells you when they're trying to sell you something. That's all I'm saying.
jimbo831 said:
I was under the impression that the vanilla devices (like the G2x obviously) was AOSP. Do you know what is modified on this version by LG? I know there is preinstalled software, but that is different than changes to AOSP.
Click to expand...
Click to collapse
It's not AOSP vanilla, but it's the closest you will get to it without buying a Nexus phone. There's lots of little tinkering to the OS on the LG2x. For example there's a "DTS" button in the music player to enable dts sound. Also, there's the T-Mobile motto when you drag down the status bar. There's a "tethering may incur charges" warning when you turn on wifi hotspot. There are different notification and ringtones put in. Etc etc. If you put this phone next to a Nexus phone, you will see lots of little differences beyond just the T-Mobile bloatware installed.
mapin0518 said:
It's not AOSP vanilla, but it's the closest you will get to it without buying a Nexus phone. There's lots of little tinkering to the OS on the LG2x. For example there's a "DTS" button in the music player to enable dts sound. Also, there's the T-Mobile motto when you drag down the status bar. There's a "tethering may incur charges" warning when you turn on wifi hotspot. There are different notification and ringtones put in. Etc etc. If you put this phone next to a Nexus phone, you will see lots of little differences beyond just the T-Mobile bloatware installed.
Click to expand...
Click to collapse
Interesting. Mine will be delivered tomorrow so I guess I'll see soon. I've had a Nexus One since release, so I'm sure whatever is different, I will notice. Thanks for the clarification.
Not sure where, but I read from one of the CM guys (I think, don't kill me) that it's not AOSP at all! It's actually that same O2X ROM themed to look like AOSP Froyo
"won't have to wait long for??"
Think we'll get this instead of 2.3.3? (Adds video chat to Google Talk, so most likely not on the Nexus One).
ref: http://www.androidpolice.com/2011/0...e-video-chat-no-need-to-wait-until-google-io/
ilanad said:
"won't have to wait long for??"
Think we'll get this instead of 2.3.3? (Adds video chat to Google Talk, so most likely not on the Nexus One).
ref: http://www.androidpolice.com/2011/0...e-video-chat-no-need-to-wait-until-google-io/
Click to expand...
Click to collapse
"carl" seems to think so..... but my guess is sense its tmobile we will get 2.3.3 in july-august (even though they say june/soon)
and wont see 2.3.4 till mid fall....
but ill give a 9/10 for wishful thinking
Maybe not officially but CM7 will have this and other unofficial roms.
I'd rather get frequent steppings and options then 1 upgrade in a year.
nate420 said:
"carl" seems to think so..... but my guess is sense its tmobile we will get 2.3.3 in july-august (even though they say june/soon)
and wont see 2.3.4 till mid fall....
but ill give a 9/10 for wishful thinking
Click to expand...
Click to collapse
Maybe so, but since they specifically say it's for video chat (ie. front facing camera) would make sense it would hit the G2x sooner rather than later (yes, yes, I know, I said "Make Sense" in regard to a Carrier). Would also explain why the G2X didn't hit with 2.3.3 with 2.3.4 in the wings.
Note: Google Tweet says this is heading to the Nexus One also
http://twitter.com/#!/googlenexus/status/63707554831806464
Android 2.3.4 OTA rolling out over the next few weeks! Has bug fixes for Nexus One, video chat for Nexus S. But a surprise is still to come!
I have trouble understanding why people complain about not getting updates.
You purchase a phone with specific version....why is update required?
I think updates for bug fixes are required but fixes for improved features....not so much...
In that case I should call honda our chevy to get my updates....
In some cases the updates are promised in which case it should be given on schedule but when its not promised....just be glad they aren't charging for them like apple......
I don't see anyone "complaining" about not getting updates. It was a simple musing on an announcement.
androph said:
I have trouble understanding why people complain about not getting updates.
You purchase a phone with specific version....why is update required?
I think updates for bug fixes are required but fixes for improved features....not so much...
In that case I should call honda our chevy to get my updates....
In some cases the updates are promised in which case it should be given on schedule but when its not promised....just be glad they aren't charging for them like apple......
Click to expand...
Click to collapse
There's sort of an expectation when it comes to software that you'll get updates for at least 12 months after purchase. Maybe not new software outright, but at least be up to date with whats current.
But even then, this phone would benefit hugely from a software update and I do think it's up to Tmobile and LG to fix a few of the launch issues.
androph said:
I have trouble understanding why people complain about not getting updates.
You purchase a phone with specific version....why is update required?
I think updates for bug fixes are required but fixes for improved features....not so much...
In that case I should call honda our chevy to get my updates....
In some cases the updates are promised in which case it should be given on schedule but when its not promised....just be glad they aren't charging for them like apple......
Click to expand...
Click to collapse
No one was complaining, they were just speculating. Also, upon release the g2x was already "behind" in it's os version compared to some other phones, which creates even more of an expectation for a timely release of a new version.
Also, are you really from the camp where you expect NO additional features stemming from updates for your phone? If that is the case, you probably would be better off with a *phone.
androph said:
I have trouble understanding why people complain about not getting updates.
Click to expand...
Click to collapse
There's a difference between "wanting" one and "needing" one. This phone is buggy as crap. I'd love Gingerbread but I'd settle for:
- Wi-Fi, Bluetooth, and a radio that get along.
- Bluetooth that remembers profiles.
- Not getting random reboots.
- Faster 4G than my old G2.
- A signal indicator that displays what the phone's actually doing.
There's more, but you get the idea.
androph said:
I have trouble understanding why people complain about not getting updates.
You purchase a phone with specific version....why is update required?
I think updates for bug fixes are required but fixes for improved features....not so much...
In that case I should call honda our chevy to get my updates....
In some cases the updates are promised in which case it should be given on schedule but when its not promised....just be glad they aren't charging for them like apple......
Click to expand...
Click to collapse
Probably because in most cases you have to sign up for a 2 year contract, which is like 5 years in techland. But that's just me.
Just an FYI, Google pushed the source and binaries for 2.3.4 to ASOP a little while ago.. and the signed update.zip for Samsung is available for direct download.
Sooner than we think may really be sooner than we think.
Sent from my beast, the T-Mobile G2x
ilanad said:
Just an FYI, Google pushed the source and binaries for 2.3.4 to ASOP a little while ago.. and the signed update.zip for Samsung is available for direct download.
Sooner than we think may really be sooner than we think.
Sent from my beast, the T-Mobile G2x
Click to expand...
Click to collapse
With the code now in ASOP, I would imagine that it will be a part of the CM7 build that finally gets released for us.
Can't say I'm surprised: http://support.vzw.com/system_update/thunderbolt.html
No voicemail notifications and FFC issues. Wonderful. How did this pass VZW testing again?
Nothing against you but people have een crying about other devices getting GB first and how we are getting screwed and blah blah and now GB is finally just around the corner and people are going to complain again. Can't be pleased it seems. Just root and run a custom ROM that runs better than stock and it's smooth(er) sailing!
I am running a custom rom. My point is that it's been how long since we were promised GB? 4 months? Weren't we supposed to get it in June? You'd think they would at least be able to iron out the bugs with this long of a delay. It's the end of September and they can't fix voicemail notifications which have plagued every leaked build for months? That's a huge bug (especially since voicemail is a Verizon feature) and it hasn't been fixed yet. Come onnnnn.
arh2o said:
I am running a custom rom. My point is that it's been how long since we were promised GB? 4 months? Weren't we supposed to get it in June? You'd think they would at least be able to iron out the bugs with this long of a delay. It's the end of September and they can't fix voicemail notifications which have plagued every leaked build for months? That's a huge bug (especially since voicemail is a Verizon feature) and it hasn't been fixed yet. Come onnnnn.
Click to expand...
Click to collapse
I see your point but I guess it all boils down to is GB worth not being notified of a VM especially with the other alternatives that are out there. With that said I do agree they should of made VM notifications work but I guess that means they will put out another update to fix that and other issues soon (hopefully).
Mustang302LX said:
I see your point but I guess it all boils down to is GB worth not being notified of a VM especially with the other alternatives that are out there.
Click to expand...
Click to collapse
I think what it really boils down to is the fact that VZW is releasing this buggy version as an OTA update, which will be rolled out to lots and lots of people who have never heard of ROMs or rooting or anything, and they will be stuck without voicemail notifications or a properly working front camera until VZW (I'm guessing) releases *another* OTA update later on to fix those problems. That's pretty bad customer service. I think they're just releasing it so they can (finally) actually stick to a release date, even if the release is buggy.
People who run custom ROMs won't have to worry about it too much but we are a small minority of all the people who have Thunderbolts.
Jacquestrapp said:
I think what it really boils down to is the fact that VZW is releasing this buggy version as an OTA update, which will be rolled out to lots and lots of people who have never heard of ROMs or rooting or anything, and they will be stuck without voicemail notifications or a properly working front camera until VZW (I'm guessing) releases *another* OTA update later on to fix those problems. That's pretty bad customer service. I think they're just releasing it so they can (finally) actually stick to a release date, even if the release is buggy.
People who run custom ROMs won't have to worry about it too much but we are a small minority of all the people who have Thunderbolts.
Click to expand...
Click to collapse
This is true but nothing anyone can do about it. VzW will have to deal with all the customer service calls they get for lack of VM notifications then and that sucks for them.
Jacquestrapp said:
People who run custom ROMs won't have to worry about it too much but we are a small minority of all the people who have Thunderbolts.
Click to expand...
Click to collapse
Actually, people who run custom roms WILL have to worry about it. Custom roms do not fix this problem. Using this phone for business it will be a HUGE problem...a liability problem.
I doubt they VM problem will be in this build thats pushing out whenever.
*Madmoose* said:
Actually, people who run custom roms WILL have to worry about it. Custom roms do not fix this problem. Using this phone for business it will be a HUGE problem...a liability problem.
Click to expand...
Click to collapse
You have usable, valid alternatives so it's not a make-or-break deal.
---------- Post added at 12:05 PM ---------- Previous post was at 12:03 PM ----------
Mustang302LX said:
This is true but nothing anyone can do about it. VzW will have to deal with all the customer service calls they get for lack of VM notifications then and that sucks for them.
Click to expand...
Click to collapse
Those who don't use Google Voice or YouMail and so on should call and call and call to get VZW and HTC motivated enough to fix it quickly. Maybe that will motivate them enough.... On the other hand, I have to think fixing VM notifications, for whatever reason, must be extremely difficult. I really don't see either company releasing an update without seriously trying to have fixed this.
People who use the Thunderbolt but do not know about leaked RUUs will not know about the VM bug. They will see their phone prompt them to update and click accept just to get rid of it. If they're in the subway, underground, or a place with no reception and someone leaves them a VM, they will have no idea it's broken until their find out the good old hard way. As you said, VZW will have their hands full with custom complaints in a few days after the OTA hits.
hallstevenson said:
You have usable, valid alternatives so it's not a make-or-break deal.
Click to expand...
Click to collapse
We were speaking specifically about custom roms, not 3rd party software. Everyone has access to those alternatives, whether its a custom rom or not.
Ahhh, yes, I overlooked that aspect of the issue. One won't KNOW they've rec'd a voicemail with this update.... I doubt people randomly check their voicemail to see if there's a new VM. People only do it when their phone tells them they have a VM waiting.
I really expected VZW to acknowledge this issue in their 'announcement' and to at least say "a minor s/w update will be released in the near future to resolve this".
Those are the details for the last ota update
MrCapcom said:
I doubt they VM problem will be in this build thats pushing out whenever.
Click to expand...
Click to collapse
The build number is the same as the leak from the other day, so it's there. Let's hope they do change the build before they push it.
Is there a way to not accept the ota? And just prevent it from downloading on its own? My wife's phone is stock and unrooted
Running Team Name SoaB .73, using XDA premium
So where's that new dock we were supposed to get with this OTA? I flashed it and nothing...
solarpolitiks said:
So where's that new dock we were supposed to get with this OTA? I flashed it and nothing...
Click to expand...
Click to collapse
No new dock here either. I'm hoping the actual ota is different from this leak.
hallstevenson said:
Ahhh, yes, I overlooked that aspect of the issue. One won't KNOW they've rec'd a voicemail with this update.... I doubt people randomly check their voicemail to see if there's a new VM. People only do it when their phone tells them they have a VM waiting.
I really expected VZW to acknowledge this issue in their 'announcement' and to at least say "a minor s/w update will be released in the near future to resolve this".
Click to expand...
Click to collapse
Use google voice. Problem solved!
Guys it's possible that voice mail and other things will work. The update according to them will be 147mb, much smaller than the full rom leak. As this is an "update" the camera and voice mail may work just fine.
Sent from my ADR6400L using Tapatalk
MrCapcom said:
I doubt they VM problem will be in this build thats pushing out whenever.
Click to expand...
Click to collapse
Wanna make a friendly wager?
5 bucks?
Send me your paypal.
I'll drop 5 that they do not have it fixed.
As Galaxy S owners, we are all united. As Android users we are all united. As far as Samsung is concerned we are all NOT created equal. Our device, the Vibrant (SGH-T959), is now being left to the wayside for any future updates from Samsung even though our core specs are extremely similar to the Google Nexus S, which has already received the ICS update. The CyanogenMod team has left us due to the on-going issue of 911/e911 and the lack of the proper code from Samsung to alleviate a potentially fatal result of a custom ROM. It is our intentions to serve Samsung with a petition asking for the update to ICS, which will in-turn, alleviate the 911/e911 issue as well.
We are asking all Galaxy S users to sign this petition to get Samsung to reconsider giving all top end Galaxy S devices the ICS update. Please help us with our goal and sign the petition. If you are on a Galaxy S phone, this affects you too.
Thank you for reading this and please see this link for more details and this link to sign the petition.
Ok, since it was explained a bit better to me, I'm allowing this to be reopened, however, I'll be keeping an eye on it. Keep it civil.
Thank you, Ann.
thanks for the update..hope things look up !!
I plan to sign this petition, but I'm a bit confused about how it includes all SGS devices. The entire letter speaks specifically to the Vibrant. Is a new letter still being written? Or how is it being conveyed that all SGS owners are signing this?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
The issue with the 3rd paragraph about how the Vibrant was released with 2.1 and then we fought for 2.2 only to be denied GB/ICS is in there to paint the picture of how consumer support has failed. It is specific to the Vibrant but the picture is for all Galaxy S users.
The CM team portion leaving the Vibrant is a problem (911/e911) that effects us all. For some reason they just dropped ONLY the Vibrant from their supported devices list b/c of this issue.
Still, we want to thank you for your support and help with this and hopefully they will at least listen to us.
Links to Samsung Twitter/Facebook/Google+:
Twitter:
- twitter.com/samsungtweets
- twitter.com/samsungmobileus
- https://twitter.com/SamsungJohn
- https://twitter.com/DigitalTrends
Facebook:
- www.facebook.com/SamsungUSA
- www.facebook.com/SamsungMobileUSA
Google+:
- https://plus.google.com/114303379611712597260/posts
let's be honest guys. Samsung did a logical thing by NOT giving us ICS update. I mean come on now.. even if they do decide to give us ICS, chances are it will be buggy as gs1 doesn't have enough memory to have ICS and TW... so really there is no point in giving us ICS, not only Samsung won't make any profit from doing this they might get flamed even more for making the phone slower buggier .. etc and
some people are saying they want stripped version of ICS on gs1 then why don't you just go buy yourself a nexus phone? Why would people buy nexus over galaxy when they're the same thing ? I could go on and rant about how samsung would have to meet terms with google, service providers and etc but ill stop here
Gingerbread from Samsung has been released. Rogers released it AGES ago.Gingerbread from AT&T has NOT been released.
your problem for Gingerbread is with AT&T. NOT SAMSUNG. Samsung released gingerbread to the carriers.
and to the post above, its not about buying an SG1 over a nexus, its about ALREADY OWNING SG1... and not enough memory for ics and touchwiz?? thats a propaganda lie. it would run fine. touchwiz consists of a launcher and a second (TW)framwork-res.apk and a few code changes to other system files. every rom has a laucher, so no loss there, wow extra 7mb framework... ohhh.. noo!
POST 3000!!!!!!
xriderx66 said:
Thank you.
Click to expand...
Click to collapse
Signed even though I don't own one. you guys should get updates too!!
Sent from my Nexus S using xda premium
TRusselo said:
Gingerbread from Samsung has been released. Rogers released it AGES ago.Gingerbread from AT&T has NOT been released.
your problem for Gingerbread is with AT&T. NOT SAMSUNG. Samsung released gingerbread to the carriers.
and to the post above, its not about buying an SG1 over a nexus, its about ALREADY OWNING SG1... and not enough memory for ics and touchwiz?? thats a propaganda lie. it would run fine. touchwiz consists of a launcher and a second (TW)framwork-res.apk and a few code changes to other system files. every rom has a laucher, so no loss there, wow extra 7mb framework... ohhh.. noo!
POST 3000!!!!!!
Click to expand...
Click to collapse
Just curious how do you know Samsung released GB to the carriers? Any sources?
EDIT: it is just me who finds big size fonts very irritating and irrelevant?
viny2cool said:
Just curious how do you know Samsung released GB to the carriers? Any sources?
EDIT: it is just me who finds big size fonts very irritating and irrelevant?
Click to expand...
Click to collapse
All carrier control the release of the updates, manufacturers create the updates for the phone, except for the Nexus line which is controlled by Google. The new exception to that might be the Verizon Nexus. The evidence is that the I-896 and I897 are the exact same phone, except one says ATT on the front.
Can someone explain this 911 issue? I mean how can you dial 911 and it won't work? IT seems like any number would work! I'm a bit confused by it, am I missing something? Thats seems like a phone being unable to dial, well Pizza hut, I dunno. It doesn't make sense.
Oh and I signed the petition.
Cor-master said:
Can someone explain this 911 issue? I mean how can you dial 911 and it won't work? IT seems like any number would work! I'm a bit confused by it, am I missing something? Thats seems like a phone being unable to dial, well Pizza hut, I dunno. It doesn't make sense.
Oh and I signed the petition.
Click to expand...
Click to collapse
I think its related to dialing 911 when u don't have any network. I mean when u don't have sim card you can still make emergency calls.
sent from my cappy rocking ICS
popfan said:
All carrier control the release of the updates, manufacturers create the updates for the phone, except for the Nexus line which is controlled by Google. The new exception to that might be the Verizon Nexus. The evidence is that the I-896 and I897 are the exact same phone, except one says ATT on the front.
Click to expand...
Click to collapse
I agree that they control it. But we don't know if Samsung actually gave it to ATT yet. Also there is no need of those kind of statements like in the post above my first post. No one is forcing him to sign the petition.
sent from my cappy rocking ICS
GB update (using KIES) for captivate:
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00024051&fm_seq=24219
viny2cool said:
I agree that they control it. But we don't know if Samsung actually gave it to ATT yet. Also there is no need of those kind of statements like in the post above my first post. No one is forcing him to sign the petition.
sent from my cappy rocking ICS
Click to expand...
Click to collapse
I support this, samsung should definitely take some initiative in regards to their previous devices.
Signed!
Sent from my SGH-I897 using xda premium
I will always be your side.But is it useful?
Has anyone heard or read anything about when we might get Android 6 on the S6? I read somewhere that Samsung has an Android 6 beta testing program going on in South Korea, but there was no mention of when beta testing would end. And then it has to go through Verizon before we get it, right? If we don't have an unlocked bootloader by the time the Android 6 OTA rolls out I think I'll just bite the bullet and update even if it means losing root.
The latest leak said 1st quarter 2016, but there's no proof the leak was legit. If it was, however, that give us until the end of March. Even then, I can't remember if that was just on Samsung's end or if it included Verizon's end.
2016 Q1 is just for Samsung's part of this.
I have a contact that I've asked that would absolutely know. I sent them a text asking for a date. They said "very soon". I will try to make time to call them today and get a more exact date.
I have read that S6 gets MM as soon as this month. But since Verizon seems to be slow at updates, i wouldnt hold my breath for anything soon.
Uh oh, now the buzz is that the first S6 marshmallow wont appear until February. And who knows when a Verizon version shows up.
And now... February / March. I may change to a 6P before S6 gets MM...
Thanks for the replies...I still remember waiting and waiting (and waiting) to get lollipop on my S4.
Whatever Samsung's release schedule is plus 3-4 months for Verizon to de-usefulapp-it and crap-ware-ify it.
---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------
Samsung needs to partner with Google and release a Play Version S7 that is compatible with the 4 big networks. 1 Device, all networks. Done.
el6006 said:
Whatever Samsung's release schedule is plus 3-4 months for Verizon to de-usefulapp-it and crap-ware-ify it.
---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------
Samsung needs to partner with Google and release a Play Version S7 that is compatible with the 4 big networks. 1 Device, all networks. Done.
Click to expand...
Click to collapse
It's extra annoying that the carriers still pre-load all that crapware. Their old justification that we're subsidizing your phone purchase so we're putting that junk on your phone doesn't hold water anymore since they are going to monthly payment plans. All of the apps (and I mean ALL) should be able to be completely uninstalled, not just disabled/hidden/frozen/etc.
February or March plus (hopefully not but very likely) another 3 or so months for Verizon to load it up with bloatware.
http://bgr.com/2016/01/25/galaxy-s6-note-5-android-6-0-update/
check this guys.
http://www.sammobile.com/2016/01/30...shmallow-updates-in-korea-for-s6-and-s6-edge/
so how long take about putting boaltware? haha
ericmtnbkr said:
It's extra annoying that the carriers still pre-load all that crapware. Their old justification that we're subsidizing your phone purchase so we're putting that junk on your phone doesn't hold water anymore since they are going to monthly payment plans. All of the apps (and I mean ALL) should be able to be completely uninstalled, not just disabled/hidden/frozen/etc.
Click to expand...
Click to collapse
Yep. I think carriers should now just keep all their crapware apps on the Play store. Some people do like some of the "value-add" crap that carriers install but many I think would like not having to deal with hiding/removing/freezing the crapware. All they have to do is just put the apps in the play store and if people want them, they can install them there. Maybe Google can jump in and help the situation somehow. I don't know.
el6006 said:
Yep. I think carriers should now just keep all their crapware apps on the Play store. Some people do like some of the "value-add" crap that carriers install but many I think would like not having to deal with hiding/removing/freezing the crapware. All they have to do is just put the apps in the play store and if people want them, they can install them there. Maybe Google can jump in and help the situation somehow. I don't know.
Click to expand...
Click to collapse
I couldn't agree more. I wouldn't mind if they "lock" the bootloader until you fully pay your device. The updates should be the same way Apple pushes their updates; regardless of carrier.
Google has the power to impose this just like Apple did; to control the user-experience all throughout. IT'S TIME!
el6006 said:
Yep. I think carriers should now just keep all their crapware apps on the Play store. Some people do like some of the "value-add" crap that carriers install but many I think would like not having to deal with hiding/removing/freezing the crapware. All they have to do is just put the apps in the play store and if people want them, they can install them there. Maybe Google can jump in and help the situation somehow. I don't know.
Click to expand...
Click to collapse
I don't so much have a problem with it being pre-installed, but that it can't be fully uninstalled. Sure, preload VZ Navigator, IMBD, NFL, etc but make all those completely removable just like any other app I download from the Play Store. The fact that all you can do is disable them is complete BS.
I've been complaining loudly to Verizon because their last 2 firmware updates have completely killed what little battery life my S6 used to have. When "Android OS" and "Android System" continually show up at the top of the battery usage list using 25% or more of my battery life I know there is a problem. I finally talked to someone willing to discuss the issue who "unofficially" agreed there is an issue and that they are working on it and it would probably be fixed in the 6.0 release "coming soon." Wasn't good enough for me so I bit the bullet and got a Nexus 5x (and am very glad I did!).
el6006 said:
Maybe Google can jump in and help the situation somehow. I don't know.
Click to expand...
Click to collapse
I think it's called the Nexus.
start just now
http://www.sammobile.com/2016/02/09...r-the-galaxy-s6-and-galaxy-s6-edge-in-poland/
mjmjhkgh said:
start just now
http://www.sammobile.com/2016/02/09...r-the-galaxy-s6-and-galaxy-s6-edge-in-poland/
Click to expand...
Click to collapse
Which means we'll get it in 6 months haha
Sent from my SM-G920V using Tapatalk