Database Info

ANDROID 2.2 Supposedly this Wednesday!

First Off, OMGOMGOMGOMGOMGOMGOMGOMGOMG!
Take this with a grain of salt but I just got off of the phone with AT&T after calling in about not being able to send MMS messages with my phone since I have had it.
They said it has been an Ongoing problem and Samsung has been working on the issue and that Samsung would be releasing a fix this Wednesday (Not Today Wednesday).
Note that I was actually talking to the real tech support people at AT&T(I was transfered to them)
I asked the lady if it was going to be an OTA update and if it was going to be Android 2.2 and she put me on hold to go ask her supervisor and he said He believes that the fix is going to be released with/through the Android 2.2 update...
Needless to say, I was a very giddy customer on the phone and I am going to be an extremely satisfied customer if this is true.
These were the actual tech support people I was talking to so it should be true right?
I just thought I would share this with everyone.

This would be good news.
From what i heard, and this is only a rumor, that sept 23 is froyo for non US devices.
I hope you're right!!

It would be kind of silly for other countries to be receiving the Android updates before we do. Google, an American based and located company.
Am I the only one who thinks that?

Shival said:
It would be kind of silly for other countries to be receiving the Android updates before we do. Google, an American based and located company.
Am I the only one who thinks that?
Click to expand...
Click to collapse
Nope. The galaxy s came out months before the us and google has nothing to do with the captivate except just providing the source code for samsung...
Sent from my fonez so excuze the speling erors

hehe your really going to trust AT&T on that promise lol that funny

Sorry. I don't believe a att Rep.

Well I am in agreement here that the ATT rep is probably incorrect. Working as a vzw customer service rep we get no indication as to when updates will be pushed to phones and also our tech support people don't even know.

ahhh i can believe it and it would be great because im looking forward to flash 10

tytdfn said:
Nope. The galaxy s came out months before the us and google has nothing to do with the captivate except just providing the source code for samsung...
Sent from my fonez so excuze the speling erors
Click to expand...
Click to collapse
Oh my gosh, I have no idea why I was thinking google worked with the phones lol. Opps.
But I guess Samsung is working on a fix and what better way to release it than through Froyo =]

I've heard rumors as well but not from any great sources. A majority of the AT&T representatives that I've dealt with are very ill-informed about anything android related.
While talking to a VZW rep he mentioned something about the Fascinate being better than the Captivate because it does have the newest version of android.. 1. No it doesn't 2. The Fascinate has a flash, that must mean it's more powerful >.>
Take anything you hear from a carrier with a lot of salt. The best way to figure out when 2.2 will be available is to watch over firmware websites. A new 2.2 I9000 firmware was just posted and leads me to believe that it is going to be released soon. The AT&T branded official firmware will be a bit farther off.

Shival said:
It would be kind of silly for other countries to be receiving the Android updates before we do. Google, an American based and located company.
Am I the only one who thinks that?
Click to expand...
Click to collapse
Unfortunately, it's a South Korean company that makes our phone.

WOW! Another "I talked to an AT&T rep and they told me something great" thread. Because this must be the one AT&T tech person that has the inside scoop.
Sorry to rain on anyone's parade, but if we took all the threads that contained a statement "X is coming on day Y because an [carrier name here] rep told me so and they know because they are [insert highest level possible here]" and then we did an analysis to see which ones turned out to be true - I bet the percentage would hover around 0 - I would go out on a limb and say the percentage actually is 0.
Since we haven't even seen a leaked 2.2 captivate ROM, this is more then a longshot.
Samsung still has to create and test the Firmware and then AT&T has to test it. It will be a while.

Shival said:
Oh my gosh, I have no idea why I was thinking google worked with the phones lol. Opps.
But I guess Samsung is working on a fix and what better way to release it than through Froyo =]
Click to expand...
Click to collapse
Since I keep reading a lot speculation about this around here, maybe I can shed some light into the typical process a device goes through when it is built and updated.
The carrier commits to ordering x number of units from the OEM with options to buy more at a certain price. In exchange for the minimum order commitment, the OEM promises to make customizations to the build of the device (industrial design, firmware and installed software) for the carrier. The OEM will also commit to a certain number of updates, fixes or patches contractually. And in this case, Google as the OS supplier will support and work very closely with both AT&T and even more so with Samsung. However, all the coding and build work is done by the OEM. Testing is done first by the OEM who puts out interim builds as defects get addressed. Release candidates are then sent to the carrier who will do their own testing mostly to make sure the devices play nicely with their network.

ianwood said:
Since I keep reading a lot speculation about this around here, maybe I can shed some light into the typical process a device goes through when it is built and updated.
The carrier commits to ordering x number of units from the OEM with options to buy more at a certain price. In exchange for the minimum order commitment, the OEM promises to make customizations to the build of the device (industrial design, firmware and installed software) for the carrier. The OEM will also commit to a certain number of updates, fixes or patches contractually. And in this case, Google as the OS supplier will support and work very closely with both AT&T and even more so with Samsung. However, all the coding and build work is done by the OEM. Testing is done first by the OEM who puts out interim builds as defects get addressed. Release candidates are then sent to the carrier who will do their own testing mostly to make sure the devices play nicely with their network.
Click to expand...
Click to collapse
So in other words, since we all decided to go with AT&T we are gunna be stuck with 2.1 until hell freezes over... great... FML

alphadog00 said:
WOW! Another "I talked to an AT&T rep and they told me something great" thread. Because this must be the one AT&T tech person that has the inside scoop.
Sorry to rain on anyone's parade, but if we took all the threads that contained a statement "X is coming on day Y because an [carrier name here] rep told me so and they know because they are [insert highest level possible here]" and then we did an analysis to see which ones turned out to be true - I bet the percentage would hover around 0 - I would go out on a limb and say the percentage actually is 0.
Since we haven't even seen a leaked 2.2 captivate ROM, this is more then a longshot.
Samsung still has to create and test the Firmware and then AT&T has to test it. It will be a while.
Click to expand...
Click to collapse
actually here is a 2.2 captivate rom from a couple days ago at samfirmware
i would post link but im not approved... its the first one there though

vin050 said:
actually here is a 2.2 captivate rom from a couple days ago at samfirmware
i would post link but im not approved... its the first one there though
Click to expand...
Click to collapse
you sure, i think the i9000 firmware is up to 2.2, but the cappy and the other US Galaxy S phones are stuck at 2.1

You can get your hopes up as much as you want... I'm saying that it ain't gonna happen any time soon.
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm putting the Froyo update up there with Santa Claus, The Easter Bunny, and The Tooth Fairy...

I've been with At&t for ten years. Not because they've treated me so well, but because they are the only game in the country. No one else goes to the trouble; that makes At&t something special. In the city you have choices; here we have At&T...
I waited specifically for a Samsung android phone because I like Samsung and as a linux user I am committed to open source. Yeah, I would like to get a froyo update, and soon, but I like this hand-held as is. So, I'll wait for a while, and if At&t still doesn't come through, then I'll avail myself of the offerings here and get it by whatever means necessary. It's not so long yet that there is no hope of At&t doing what is right...

krakerx said:
So in other words, since we all decided to go with AT&T we are gunna be stuck with 2.1 until hell freezes over... great... FML
Click to expand...
Click to collapse
Not saying that at all. But if there is to be a Froyo release for the Captivate, it will already be part of the deal AT&T has with Samsung.
Since Froyo was GA before the Captivate was even in stores, I think AT&T would almost have to plan for the upgrade. And I think Google will have put some pressure on AT&T to provide the upgrade since it helps to reduce OS version fragmentation which is very much in Google's interest. So my guess is, WE WILL see a Froyo build for our Captivate. The question is when.

Android rooting days are coming to an end?

Verizon and other carriers are working with Google to ban rooting phones. Data will get throttled and possibility of the phone getting banned from network coverage.
1. The way that they were able to track rooted users is based on pushing updates to phones, and then tracking which meid's did not take the update.
2. More than one major carrier besides Verizon has implemented this program and that all carriers involved had begun tracking rooted phones. All carriers involved were more than pleased with the accuracy of the program.
3. In new builds the tracking would be built into the firmware and that if a person removed the tracking from the firmware then the phone would not be verified on the network (i.e. your phone could not make phone calls or access data).
4. Google is working with carriers and manufacturers to secure phones, and although Google is not working to end hacking, it is working to secure the kernel so that no future applications can maliciously use exploits to steal end-user information. But in order to gain this level of security this may mean limited chances to root the device. (This item I've been told but not yet able to verify through multiple sources – so take it for what you want)
5. Verizon has successfully used its new programs to throttle data on test devices in accordance with the guidelines of the program.
6. The push is to lock down the devices as tight as can be, but also offer un-lockable devices (Think Nexus S).

NOOOOOO,
that sux and i wanted to buy a andriod soon because of the rooting.

I wouldn't see it as a threat the reason being :
Majority of people root they phones just to get the better version of the android software which they would have not got otherwise due to the companies not releasing the updated software so obviously the companies wont bother to send the so called update to this old phones anyway.
Secondly Google seems to trying to close the gap on fragmentation in the android as most phones were updated to the Eclair version. so I believe most of the phones of 2010 will eventually get the Gingerbread release depending on the carrier
and last of all there will always be great softwares released and some one out there will come with a hack or whatever

tfn said:
I wouldn't see it as a threat the reason being :
Majority of people root they phones just to get the better version of the android software which they would have not got otherwise due to the companies not releasing the updated software so obviously the companies wont bother to send the so called update to this old phones anyway.
Secondly Google seems to trying to close the gap on fragmentation in the android as most phones were updated to the Eclair version. so I believe most of the phones of 2010 will eventually get the Gingerbread release depending on the carrier
and last of all there will always be great softwares released and some one out there will come with a hack or whatever
Click to expand...
Click to collapse
i completely agree with your first point considering I am one of those ppl! also I rooted my EVO to get better battery life....thats another reason to rooting.
i do see the carriers point of view tho.....they dont want people using the tethering workaround they gain from rooting since that is money that they are missing out on.
i should mention, tho, i am against the carriers doing this!! im just saying that i see where they are coming from

I dont think there is any blocks coming to any of the networks in the UK

This subject has already been discussed - more than once, you'll see, from the link I posted in that thread.

If this takes place, I'll be going back to Iphone.

his was an email I got from my networking team. Just wanted to inform and at the same time get a few informed views.
Sent from my ADR6300 using XDA App

tfn said:
I wouldn't see it as a threat the reason being :
Majority of people root they phones just to get the better version of the android software which they would have not got otherwise due to the companies not releasing the updated software so obviously the companies wont bother to send the so called update to this old phones anyway.
Secondly Google seems to trying to close the gap on fragmentation in the android as most phones were updated to the Eclair version. so I believe most of the phones of 2010 will eventually get the Gingerbread release depending on the carrier
and last of all there will always be great softwares released and some one out there will come with a hack or whatever
Click to expand...
Click to collapse
I know this is my first post, but this thread caught my eye.
the reason they don't want us rooting our phones is because if we do we can use out old phone longer and don't have to pay out he wazoo for a brand new phone. I have a Samsung Moment the last O/S that I could get was Android 2.1 Update 1 which basically rendered the Spring gps useless, and made calls and texts come in when ever they wanted, forcing me to think about a new phone, So i joined the SDX forums and rooted it installed 2.2 with the EB28 rom and so far every thing works as good as a Samsung epic just not 4 g,. which doesn't bother me since I don't video chat.
As far as I am concerned YOU paid for the, phone YOU pay the phone bill its YOURS, you should be able to do whatever you want to with it.

that realy sucks. I dont like that

I wouldn't sweat this too much.
I understand the tethering issue, and I also understand that the base is, and always will be, money. That's the whole point of any business.
Having said that, this community in itself is a market and there are people watching what we are doing and where we are going, because there's cash to be made. If we run into locked bootloaders, dead phones, crappy updates and new phones riddled with bloatware, you better believe that someone else will be ready to snatch all of us up and give us exactly what we want, if not close.
If I owned a company large enough to deliver wireless service, I'd be sitting silently with a squad of high-end 250 dollar unlocked smartphones ready for some good ol "we have your back" marketing. ...granted my wireless was on point and I got good reception.
I don't think us getting into our phones and tinkering with it's innards is ever gonna stop. It might change, yeah, but it won't stop.

damn that doesn't sound to good

even if this happens i'm pretty sure there will be workarounds..

So please explain me how that would work in the court room :
- defendent : I paid for a data plan, and now I am accused of using it
- provider : he has installed an upgraded OS on his phone, your honor !
That would be the same as switching phones (for example if I change my Hero for an unlocked Nexus S, I would be using the same OS as in my hacked Hero), while still having the contract.
I can not see how they can enforce such a thing.

I always buy SIM free phones, so they cant really get me with that as I dont ever get carrier updates.

jh71 said:
So please explain me how that would work in the court room :
- defendent : I paid for a data plan, and now I am accused of using it
- provider : he has installed an upgraded OS on his phone, your honor !
Click to expand...
Click to collapse
Try again...
Defendant: I paid for a data plan that expressly stated that tethering is not included so I fiddled with my phone so that I could do that without paying the appropriate charges.
Network: as you can see, a clear breach of contract.
Not that it would ever reach a courtroom anyway.
waz000000 said:
I always buy SIM free phones, so they cant really get me with that as I dont ever get carrier updates.
Click to expand...
Click to collapse
That's got nothing to do with it though - I have an unlocked. unbranded Motorola Defy but the bootloader is still encrypted.
Some manufacturers can and do lock down handsets that aren't tied to any one network. Motorola do it, HTC seem to be moving in that direction - only SE are taking clear steps in the opposite direction.

Let's have a go at it one more time:
Defendant :
"Your honor, android is all about innovation, and carriers are ganging up with manufacturares cuz they want more, and more, and more, but are to lazy or incapable, or lacking inspiration. I do root, but tethering might as well not even be there, as it is part of many official out of the box releases. If i root, i do it cuz some manufacturers and some carriers are incapable of offering me the google experience im locking for, and as this is a carrier dominance, i dont have a choice but get the closest device for my budget, and that delivers the closest version to that google experience, and then root it, to get the proper battery life i paid for, and get rid of bloatware, which isnt productive for my needs, as THIS DEVICE IS MINE, I OWN IT!"
Network:
We are directly against Android!!!!
,

if this happend i think hes going to loose a lot of client so i don't think thats going to happend if no root no theme change no a lot of other things no liberty so if they do that i buy an iphone ^^

hey andy...why dont u guys start investing in you own hardware... apple is pretty good at it, google would be a hit. at least a research would be more then worthed.
my, how the tables would turn in such case....

The more I read and hear this, the more I don't believe it will ever happen.

ICS future for the Atrix 2 gloomy?

Talked with a Motorola rep via support webchat who said that they "don't know" if an update for ICS will come to this phone. This is highly disappointing. Does anybody have any other information? I am considering returning it if they back out on it (as I am still within the return period). Maybe AT&T has a better answer?

toastthemost said:
Talked with a Motorola rep via support webchat who said that they "don't know" if an update for ICS will come to this phone. This is highly disappointing. Does anybody have any other information? I am considering returning it if they back out on it (as I am still within the return period). Maybe AT&T has a better answer?
Click to expand...
Click to collapse
Unfortunately no AT&T does not have a better answer, actually it is worse. I got the "We are working very hard to have ICS ready for all phones that have the capability, and we don't have any dates to reveal for any phones upgrade to ICS". I then also got the "We have 4 phones getting ready to be released in the next 60 days that will have ICS already on them".
I also asked around at corporate, and I can not get any of the people I work with there to give my any information at all on ICS one way or the other, for any phone.
Don't worry though ports are on the way, I know that both lfaber06 and I will be working to get a real port of it over ASAP. In fact he has a true pre-alpha version already posted this morning.
Jim

Major bummer, considering this phone is only about 2 months old. Either way, I love the phone and I'm keeping it for as long as its functional!
Sent from my MZ617 using Tapatalk

big ach said:
Major bummer, considering this phone is only about 2 months old. Either way, I love the phone and I'm keeping it for as long as its functional!
Sent from my MZ617 using Tapatalk
Click to expand...
Click to collapse
Same here, its a solid phone.

PeteSeiler2010 said:
Same here, its a solid phone.
Click to expand...
Click to collapse
I just think it's too "plastic" (while it's still ... a kind of solid)...

If you think this phone is too plasticy...then your best bet would be an HTC phone. I think the Atrix 2 is very solid feeling.

toastthemost said:
Talked with a Motorola rep via support webchat who said that they "don't know" if an update for ICS will come to this phone. This is highly disappointing. Does anybody have any other information? I am considering returning it if they back out on it (as I am still within the return period). Maybe AT&T has a better answer?
Click to expand...
Click to collapse
Ok lets see if I have this straight
You want to return the Atrix 2 when they don't even have the ICS update for the Motorola Razor yet and it's guaranteed? Me, I'm waiting for the Atrix 2 and here is why.
Google states that phones that run 2.3 can run ICS and it's up to the manufacturer to push the upgrades out. What manufacturer is going to push the hardest to get their handsets running ICS
Motorola/Google hands down

Clovett said:
Ok lets see if I have this straight
You want to return the Atrix 2 when they don't even have the ICS update for the Motorola Razor yet and it's guaranteed? Me, I'm waiting for the Atrix 2 and here is why.
Google states that phones that run 2.3 can run ICS and it's up to the manufacturer to push the upgrades out. What manufacturer is going to push the hardest to get their handsets running ICS
Motorola/Google hands down
Click to expand...
Click to collapse
Not so fast there.... you are forgetting AT&T is the carrier, and they HAVE to do the actual ROM build, MOTO will give them all of the needed firmware and drivers and such, but it is AT&T who actually does the final build and approval for the releases, what we get off the MOT dev sites, actually is a joint effort from both Moto and AT&T.
I have direct information that if the Atrix 2 gets an ICS build, and IF is the word here, it will not be right away.
Why? You will most likely ask. It is becuase they (Moto and AT&T) are more interested in "Selling" you another more expensive phone, with ICS already on it. Both MOTO and AT&T don't get anything by releasing a new version of the OS to your phone. Just because a Phone can run it, does not mean that they will make it happen. Don't wait for something that might or might not come. If that is the attitude then go get a phone that already has ICS on it, you will be much happier.
I have information that IF, this comes out it will be after June most likely, April or may possibly. This last sentence is unofficial information, the official info I got from my client is posted in the second post here.
Jim

jimbridgman said:
Not so fast there.... you are forgetting AT&T is the carrier, and they HAVE to do the actual ROM build, MOTO will give them all of the needed firmware and drivers and such, but it is AT&T who actually does the final build and approval for the releases, what we get off the MOT dev sites, actually is a joint effort from both Moto and AT&T.
I have direct information that if the Atrix 2 gets an ICS build, and IF is the word here, it will not be right away.
Why? You will most likely ask. It is becuase they (Moto and AT&T) are more interested in "Selling" you another more expensive phone, with ICS already on it. Both MOTO and AT&T don't get anything by releasing a new version of the OS to your phone. Just because a Phone can run it, does not mean that they will make it happen. Don't wait for something that might or might not come. If that is the attitude then go get a phone that already has ICS on it, you will be much happier.
I have information that IF, this comes out it will be after June most likely, April or may possibly. This last sentence is unofficial information, the official info I got from my client is posted in the second post here.
Jim
Click to expand...
Click to collapse
I agree completely on the time frame. However unlike other releases this one is different for Google. They will press extremely hard and bend over backwards to help update every phone in the field they can. The why is extremely easy
This ICS build will allow Google to build for their tablet platform AND the phone platform. The more phones they convert the larger the base to attract developers. This is the first shot they have had to have a single operating system. If they update every phone that can run ICS in about a year most phones current in the lineup and still in the field will be running ICS. Most tablets will be running ICS. As for the carriers they will leap on board since Google is going to be doing the work for them. The more phones on one platform the easier it will be to support. It's truly a win/win

^ Grabs popcorn
Sent from my MB865 using Tapatalk

If Atrix 2 does get ICS, it will be a very long time before that happens, Motorola hasnt even released an update to 2.3 to fix all the damn bugs on the phone. Atrix 2 is the red headed step child.

Red-heads rock ... FYI ...

assuming the carpet matches the drapes
off-topic apologies... back to maintaining positive ICS thoughts...
From what I have read..it would seem that perhaps manufacturers and the "almighty goog" are fighting over device disk space with their proprietary interface bloatware and OS upgrades as well...hence the perpetual speak of "fragmentation" as well... too many differences and no commonality. To someone else's point, hopefully ICS can bring a closer point of unification.

shanghei said:
If Atrix 2 does get ICS, it will be a very long time before that happens, Motorola hasnt even released an update to 2.3 to fix all the damn bugs on the phone. Atrix 2 is the red headed step child.
Click to expand...
Click to collapse
Interesting point well taken, but I'd have to as you this
Assuming you are the CEO of a carrier and you are presented with two paths and only have the time to pursue one course of action.
A) Put your programmers on fixing the current system and take them off upgrading as many phones as possible to ICS, even though the bugs with the phone are minor and don't impede actually using it as a phone.
B) Concentrate on moving forward with one platform so you can decrease support costs overall and get a big fat bonus
chose

shanghei said:
If Atrix 2 does get ICS, it will be a very long time before that happens, Motorola hasnt even released an update to 2.3 to fix all the damn bugs on the phone. Atrix 2 is the red headed step child.
Click to expand...
Click to collapse
Long time or not, as long as it comes before my contract renewal date, I'll be happy
Considering this phone came out about two months ago, I will go ahead and assume that most of us just renewed our at&t contracts to get it... I will also assume that most of us have about two years before we can renew our phones so basically, there's no rush guys lol
Sent from my MZ617 using Tapatalk

The biggest problem I see is that Google is in the process of buying Motorola. The issue is that during such buyouts, there are a lot of movement of people who work there. Usually a lot of instability, layoffs and/or management changes happen during this period. The end result will be that the Atrix 2 will be caught in the shuffle and so I don’t have know if ICS will ever come to this device. Motorola doesn’t even seem to care to address the many bugs as it is with this phone, much less care about ICS.

Clovett said:
Interesting point well taken, but I'd have to as you this
Assuming you are the CEO of a carrier and you are presented with two paths and only have the time to pursue one course of action.
A) Put your programmers on fixing the current system and take them off upgrading as many phones as possible to ICS, even though the bugs with the phone are minor and don't impede actually using it as a phone.
B) Concentrate on moving forward with one platform so you can decrease support costs overall and get a big fat bonus
chose
Click to expand...
Click to collapse
It all depends on LOE. If the LOE is less than the cost to implement with newer handsets, then it will happen. If the LOE is more than the cost to implement ICS with all new phones, then it will not happen. Look AT&T has 4 different versions of the Iphone that all can run 5 different versions of IOS, and there is not a way to FORCE anyone on an older Iphone to upgrade, becuase there was not OTA until IOS 5.
Support is not a big issue for the carriers, because they really don't support the devices the manufactures do.
You need think way higher than just google and android in this equation and the fact that AT&T still has to support ANY handset (on their network) that has been sold through AT&T or Cingular since 3g rolled out. There are guys at corporate AT&T that still carry the first HTC Tytn phone (the first 3g phone on cingular / AT&T), because it was a beast for the time, and since it is still 3g, and works, AT&T has to provide support for it. Now are there updates from AT&T or HTC, no, but that is why this community is here. Those guys are all running some form of windows mobile 6 on it, so is it the latest, no, does it do the job, yes.
Again ICS might or might not come (at this point the LOE says no, most likely not), I can't spell it out for you any clearer than that or I will no longer have my current customer. I have way more information than I am letting on, that I can not release at this time.

Motorola has issued very few statements about devices that will be on the upgrade path to ICS and the ones that were stated are on Verizen and they havnt even been given a specific date as to when to expect the update.
AT&T has a very good record at getting updated to their devices and doing it in a timely manner compared to the other carriers. Look at the phones on Verizen and tell me how many are up to date and running Gingerbread 2.3.5 or higher, very few. Heck their famed Thunderbolt is still trying to get the Gingerbread update going. The OG Atrix recieved the Gingerbread update before 90% of all other phones had.
Im not confirming nor denying that we will get it but we have a very good chance considering AT&T's track record even though they are being tight lipped about things and I personally think we will. But hey I have been proven to be wrong also
So if Jim says May - mid summer I say that is acceptible in my books. Has anyone seen a PROVEN date as to the other devices yet? NO. We all just have to be patient and see how the events play out. Hope everyone has a good day!

JRW 28 said:
Motorola has issued very few statements about devices that will be on the upgrade path to ICS and the ones that were stated are on Verizen and they havnt even been given a specific date as to when to expect the update.
AT&T has a very good record at getting updated to their devices and doing it in a timely manner compared to the other carriers. Look at the phones on Verizen and tell me how many are up to date and running Gingerbread 2.3.5 or higher, very few. Heck their famed Thunderbolt is still trying to get the Gingerbread update going. The OG Atrix recieved the Gingerbread update before 90% of all other phones had.
Im not confirming nor denying that we will get it but we have a very good chance considering AT&T's track record even though they are being tight lipped about things and I personally think we will. But hey I have been proven to be wrong also
So if Jim says May - mid summer I say that is acceptible in my books. Has anyone seen a PROVEN date as to the other devices yet? NO. We all just have to be patient and see how the events play out. Hope everyone has a good day!
Click to expand...
Click to collapse
That is exactly what I have been trying to get across, Thanks! I also want to note that the carriers are not the ones that really care about which OS a phone is on or if it is up to date, just that it does not harm their network.
AT&T is really trying to get phones updated as soon as they can, if it is a feasible LOE. And they do have a good track record of doing so.

mathk said:
I just think it's too "plastic" (while it's still ... a kind of solid)...
Click to expand...
Click to collapse
I want to know what everybody does with there phone's that it has to be built like a tank. The A2 seems pretty tough. The only phone I ever had that died was because my dog got it.
Sent from my MB865 using xda premium

We may need a campaign of annoyance...

Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.

I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.
If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Sent from my Samsung Galaxy S Blaze.

Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Sent from my SGH-T769 using xda app-developers app

dr4stic said:
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
Click to expand...
Click to collapse
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us

Chitown021 said:
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Click to expand...
Click to collapse
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.
I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.
Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.
I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.
I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.
chjema said:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Click to expand...
Click to collapse
You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone

Yeah, a 720p screen would have been nice... thanks for the detailed explanation.
I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB.
Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).
Sent from my Samsung Galaxy S Blaze.

Yes lets please do this.
T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182
I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.

Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.

Dr4stic
If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
Sent from my SGH-T769 using xda app-developers app

heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Click to expand...
Click to collapse
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.

I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.
I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.
If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.
I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.
Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.
I know this all sounds cynical but I've seen this show before.
Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.

Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.

L7ChrisL7 said:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
Click to expand...
Click to collapse
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back

heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem.
Click to expand...
Click to collapse
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?
And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.
And don't get me started on the underutilisation of the video hardware.
AwesomeTurtle said:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
Click to expand...
Click to collapse
No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.
This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.
If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.

dr4stic said:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
Click to expand...
Click to collapse
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.

L7ChrisL7 said:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
Click to expand...
Click to collapse
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone

dr4stic said:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
Click to expand...
Click to collapse
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.

http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone

here's a thread we can vent at!
spartanerik said:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
Click to expand...
Click to collapse
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!

anactoraaron said:
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
Click to expand...
Click to collapse
http://support.t-mobile.com/people/tmo_erica
Try sending an email to [email protected] and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction

TouchWiz 4.3 update - WHY

Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"

galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
Because you can't. Once you take the 4.3 OTA, you're stuck with it.

McDastardly said:
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
Click to expand...
Click to collapse
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?

galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
What features were taken out? Anything that can be replaced with better apps on the market shouldnt count. In my opinion the new stock task manager makes it worth it.
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Well if I could go back in time I would have just waited for a custom 4.3 tw rom. But at least I don't feel the need to flash a new rom every day now.

ThePagel said:
What features were taken out?
Click to expand...
Click to collapse
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)

galets said:
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
Click to expand...
Click to collapse
I can understand your annoyance with the hidden menu being gone. But that wasn't a "feature" it was a "hidden menu" after all and with root there are ways to get rid of the volume warning. That bugs the crap out of me as well but not to the point to change it yet.... YET!

galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
Click to expand...
Click to collapse
Nah, Samsung hasn't been overwhelmingly developer friendly for awhile. There's a bit of dislike for them due to Exynos processors.

Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step. That's why it was mentioned multiple times to not accept the 4.3 update in case it locked the bootloader.
Samsung hasn't been developer friendly for a long time. Anytime you take an OTA update you can expect it to prevent the use of custom firmware unless a trusted source says it doesn't.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step.
Click to expand...
Click to collapse
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"

galets said:
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"
Click to expand...
Click to collapse
Samsung isn't as nice as you think. HTC will often allow you to unlock the phone by signing an agreement that you are voiding the warranty. Verizon has had a history of locking bootloaders that other carriers wouldn't.
This bootloader lock is mostly Verizon's implementation anyway. They're the ones who changed the bootloader and patched our loophole. Other devices on the 4.3 OTA update (sprint and T-Mobile) still have unlocked bootloaders.
The custom icon was only stating we had a custom recovery installed. Didn't have anything to do with firmware checking.
Sent from my SCH-I535 using Tapatalk 2

It's hard to call it sneaky if you look back at the thread that was all about waiting for the update it was repeated daily, if not a couple of times a day that if the OTA hits your phone not to take it because it would lock your bootloader. Taking my early upgrade from the Bionic this didn't really surprise me lol. It just clinched it that, I'll maintain my unlocked bootloader and rom away until its time for my next phone, which will be a nexus or amazingly enough a moto if i can let go of my bionic anger lol....

If you purchase a phone to be modded, after you mod it, why would you ever take a manufacturer OTA?
Sent from my SCH-I535 using xda app-developers app

galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
Click to expand...
Click to collapse
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang

XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Its samsung. Every version of the s3 is locked on 4.3 the only difference is nobody is complaining about it on the other forums. samsung wants to be able to have there phones used in government agencies and the like so they locked the phone down. I accidentally upgraded and haven't complained once because its not that big of a deal. I am just not buying from samsung from now on (unless they make the tablet that folds into a phone). Someone can correct me if I am wrong but everything I have read says every s3 on 4.3 has been locked down. If you do say I am wrong please give me a link so I can educate myself.

XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang

XdrummerXboy said:
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
You can still root the OTA by using saferoot. Once rooted, superSU will ask if you want to disable knox. You can then load safestrap which will allow you to load other 4.3 roms and multi-boot your phone etc. Read ALL the threads on saferoot and safestrap before you install them.
Sent from my SCH-I535 using xda app-developers app

galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
App access to notifications. That is my killer app for 4.3