thesweetens, Google "KitKat 4.4 problems" sometime before you get too excited about another (flawed?) update. I, personally, just look forward to an update that's 95+% problem-free for a change.
What kind of problems are you having with your S4? I am on the current 4.3 update and I don't have any issues that I am aware of. What are you experiencing?
Don't worry... in true Verizon fashion we will be dead last to get the update.
Verizon will fiddle with the update (and add as much crapware & bloatware as they can) until the other major carriers push out the update. Once there backs are against the wall, they will release it.
What really surprised me is that Sprint got out the gate first and supposedly US Cellular is right behind them. As soon as I read Sprint went first I started looking for people complaining of update issues after Kit Kat. So far everything has been quiet.
This tells me the update must be pretty solid and Verizon should have no problem pushing it out right now as we share similar cellular technology with Sprint phones.
But as I said... we will be dead last.
As someone up the chain asked, I googled Android 4.4 problems. From what I read, it seemed that a lot of issues were nuisance things that Google handled. The only major thing I read about was Samsungs meddling that broke the SView access to third party accessories.
Since you know VZW will be last to the table...you have been around VZW for some time. I just hope the don't come to the table with an update that breaks every ones phone as they did a few updates back with the S3. That update put out many of the GS3's to a point they could not even make a phone call and it took the many weeks to put out an update that would fix all these broken phones. I have the S4 now but I did have the S3 in those days. Many people resorted to getting rid of the stock android rom do they could have use of their phones..
In my personal opinion, I think that maybe Samsung, Verizon, and the other phone manufacturing companies should maybe take a page out of Microsoft's book. They should add a compatibility check to the updates that will scan the apps on your phone to see if they are compatible with the update. It should give you a list of the apps that you may have on your phone that could cause a problem and give you the option to uninstall these apps before the update is installed. Once the update has been installed you can try to re-install the apps (if you wish) that were removed before the update or maybe look for an app that is compatible.
Sound like a good idea but in all actuality it would be almost an impossible task to test an update against the, maybe, millions of apps for compatability. I do believe that Verizion and Samsung tests their updates against the apps that they install on the phones.
I still say the best way to install an update is to do a factory reset first, download the update, then reinstall all your old apps, getting them from the app store instead of backup, then test the apps one at a time for compatability. This naturally takes a lot of work and most just don't want to deal with it.
People whine at how long it takes VZW to bring updates to the table now...can you imagine how much longer this would add to that time...and how much more people would whine about it. Not that I care because I would rather have a good update than the failed ones I have seen. i know Microsoft procedure is not fool proof.
I just hate being dead last.
We have two CDMA carriers releasing the update and the largest of three CDMA carriers is leaving us tacking in the wind. If the update is good enough for Sprint, than it should be good enough for us.
The only thing I can guess is Verizon has not messed it up enough by their special blend of crapware and bloatware.