I cannot find words strong enough to express my outrage at the havoc, expense and lost productivity that I have, so far, endured following the Ice Cream Sandwich (ICS) Android update on my phone.
I have been using a Sprint/Samsung Epic 4G Touch Galaxy S2 since Jan. 2012. At that time I reluctantly made the transition from a Sprint Windows-Mobile phone that I had used for the previous 5 years, during which I experienced no major data losses nor any significant time/expense lost to system software or firmware bugs.
Yesterday morning, 16Jul12, I was prompted to click "OK" to update my phone's Android system software. No warning was given to backup the phone's data or apps prior to performing the update. I naively clicked “OK”. From that moment forward my workday ground to a halt and I descended through ever-maddening levels of Sprint/Samsung/Google/Android "support" h#ll.
First the facts:
1) Following the ICS “update” the Swype app "disappeared" from my phone.
2) When attempting to do web searches via my phone (the bulk of my web searching) ALL text, in the search box and in results, displayed in a micro/nano font size that was completely, and without the slightest exaggeration, UNREADABLE. Happily, the Google logo remained in its normal giant font as a searing taunt of my inability to perform ANY web surfing.
3) The update graciously preserved my browser bookmarks (I'm a Luddite that uses the native Google browser). Less graciously, ALL the folders that I had setup over the last 7 months to organize my bookmarks were GONE, GONE, GONE. I estimate that my individual bookmarks number well over a hundred and possibly in the multiple hundreds. To stare, slack-jawed, at a single listing of this number of bookmarks is the definition of "useless".
Next, the single-user impact and costs of this "update" fiasco:
On my windows phone (the preceding 5 years) I used the wonderful NATIVE Win-Mobile handwriting recognition program for all my input. When I moved to the Android phone I found no handwriting recognition Android software that remotely approached the functionality of the Win-Mobile counterpart, so I quickly adopted Swype as my sole keyboard input app. In other words, for the past 7 months, my only keyboard input experience with the Android phone has been via Swype. The loss of Swype following the ICS “update” was excruciating.
I do much of my business communication via my phone and SMS. I also do the bulk of my web browsing via my phone.
To suddenly find myself pecking at the Samsung keyboard at the pace of a toddler, while my work, colleagues and clients were moving at normal business warp speed, was dysfunctional. To, further, find myself trying to surf the web without the use of ANY of my bookmarks was seriously impairing my productivity and effectiveness. To, additionally, have to attempt to read micro/nano text in my browser's search box and in returned results put the last nail in the coffin of my workday. After two hours of this outrage, I informed all that I would be taking a personal day to resolve these issues. I will not detail here the havoc that my bowing out of the workday meant for others- suffice it to say that the cost to others conservatively rises into multiple person-hours of lost productivity.
From noon yesterday untill 1:00 AM today I spent my time:
1) on various phone calls to Samsung and Sprint, and
2) online (via my computer- as my phone was rendered useless):
a) crawling through the morass of similar nightmarish experiences being related by other Sprint customers through the day and evening, and
b) attempting, in vain, to gain some insight and/or relief from Sprint, Samsung and Google support.
The “conclusions” and “remedies” offered by Sprint, Samsung and Google following this 13 hour investment on my part were:
1) Google (when speaking with Samsung or Sprint), Samsung (when speaking with Google or Sprint) or Sprint (when speaking with Google or Samsung) were DEFINITELY AND COMPLETELY responsible for this ICS “update” debacle.
2) Google (when speaking with Google) and Samsung (when speaking with Samsung) and Sprint (when speaking with Sprint) were DEFINITELY AND COMPLETELY INNOCENT AND BLAMELESS for the ICS “update” debacle.
3) The sole and only remedy to MY problems with the infarcted update was to reset the phone to its factory defaults. I was duly warned by all (Samsung, Sprint and Google) that such a reset would result in complete loss of all installed apps and data, and that I would need to spend yet MORE of MY time reinstalling apps and data and restoring my systems' state (bookmarks, home screens, etc.).
After a fitful night, I rose early and made further unsuccessful attempts to restore Swype to my phone- the most promising of which seemed to be downloading the latest beta test version of Swype and using it in place of the native Samsung/Sprint Swype- duly warned by Swype that there "is no support for beta Swype, and it will be deactivated every 6 months for release of a new beta version of Swype", clearly a new flavor of nightmare in the offing.
At 9AM, I cancelled a second work day to, again, attempt finding resolutions to these problems. I then Sprinted (sad pun intended) to my Sprint store for another round of pleading and cajoling. When I arrived, I found all technicians up to their eyeballs in phones and customers reporting the same or similar problems. From what I overheard and comments made to me by the technicians, the most expeditious path to a solution for those in line ahead of me was a factory default reset, with concomitant loss of apps and data ("Sorry for the inconvenience").
I awaited my turn at the "desk of despair" and informed the technician that I wished to forego the factory default reset "solution" in favor of finding an alternative keyboard app (end run around the Swype problem) and possibly an alternative browser app (would like to be able to read my browsing activities without having to reserve time on the atomic force microscope). I “volunteered” to eat the loss of my bookmark folder organization if we could just achieve the preceding two goals.
The technician (Mike, Sprint Store, 266 East Travelers Trail, Burnsville, MN) graciously (under tremendous pressure and managing factory resets on several phones while serving me) offered recommendations on alternative keyboard and browser apps. More impressively, he asked to look at my phone again to see if he could find the "missing" Swype app. Within a couple minutes he did just that. Apparently the ICS “update” inactivated/disabled the Swype app so that when looking under settings/applications/all tab the Swype app was not listed alphabetically in its previous location, but rather, at the bottom of the alphabetic listing of active apps. No one at Samsung, Google or Sprint thought to have me look here the previous day for the "missing" Swype and, rather, insisted the ONLY way to "recover" Swype was to do the dreaded factory default reset.
Mike reactivated the Swype app and cleared its data and cache (apparently these two steps resolved the issue for customers that could still see Swype after the ICS update) and then attempted to set Swype as the default keyboard/input method under settings/language and input. Surprisingly, Swype was STILL not listed/available as an input/keyboard option, even after the steps taken above. We seemed to be back to the factory default reset or pitch-Swype-with-the-bathwater alternatives. At this point, I thought that, perhaps, a "hard" shutdown (long press of the power button and selecting "Power Off"), and then a restart (long press of the power button until the "4G" screen appeared) might get us over the hump. Happily, this was the case and, after performing the above, Swype was restored to its former function and glory (sans my personal dictionary- but desperation makes no good deals, and I “volunteered” to also eat the time and inconvenience to redefine my personal dictionary). Most perplexing, following these operations, the font size displayed by my browser operations returned to normal size. I'm sure someone can explain this. I will, however, quote Rhett and say "Frankly my dear, I don't give a dam#!"
So, in review for those who came here for the fix to their Swype/ browser nano-font woes following their ICS “update”, these were the steps that resolved both for my phone:
1) Find a responsive, patient and knowledgeable Sprint technician that has read this post, or, do steps 2-17 below.
2) DO NOT do a factory default reset.
3) Consider backing up your apps & data before proceeding.
4) Find your "missing" Swype app by:
a) holding menu hard key and then selecting "settings",
b) scroll to and select "Applications",
c) select "All" tab at upper right corner,
d) scroll ALL THE WAY TO THE BOTTOM of the list to find Swype as an "inactive" app,
5) press on "Swype" to open its app info,
6) press the "Enable" button to the right just beneath the Swype version number at the top of the screen,
7) press the "Clear data" button if lit/white under the "Storage" section,
😎 press the "Clear cache" button if lit/white under the "Cache" section,
9) press the back arrow key three times to return to the home screen,
10) perform a "hard" shutdown of the phone (on the Galaxy S2, long press the power button and select "Power Off"),
11) after the "hard" shutdown, wait 30 sec or more, then restart (on the Galaxy S2, long press the power button until the "4G" screen appears),
12) go again to the "Settings" screen (long press the menu key and select "Settings") and scroll to "Language and input" and select it,
13) under "Keyboards and input methods" select "Default",
14) you should now be able to see Swype listed as an option- select it,
15) on being returned to the "Language and input methods" screen you should also see Swype listed under the "Keyboards and input methods" where you can select the "bar-dot slider" icon to the right of "Swype" if you wish to change your Swype settings,
16) press return arrow twice to return to your home screen,
17) open your SMS or browser app and input some text, you should be using Swype by default. Enjoy!
If you also experienced microscopic browser type size with the ICS “update”, you may be lucky and the procedure above may correct this. If it does not, I throw my hands skyward and pray for you. If you also experienced deleted personal Swype dictionary and deleted browser bookmark folders with the ICS “update”, then, like me, you will probably eat the time and labor to restore these.
Some thoughts on the destruction wrought by the Sprint/Samsung/Google ICS "update" debacle (THIS SECTION IS PRIMARILY FOR CLASS ACTION LEGAL PROFESSIONALS TROLLING FOR A LUCRATIVE CASE AND A COLLEGE TUITION OR RETIREMENT ANNUITY):
1) From web traffic and from foot traffic in the one Sprint store that I observed, it is clear that many users lost many hours of productivity, and endured much stress, pain and suffering (I do not editorialize here) due to this botched "update". A small bit of research and legal discovery process regarding market penetration of the Sprint/Samsung Galaxy S2 phone and reported frequency of these and other ICS "update"-related problems could put a limiting number on the actual total $ of productivity lost and potential $ to be recovered from responsible parties.
2) I have worked 30 years in the medical device, diagnostic and pharmaceutical industries. These are heavily regulated industries in each market/country that they serve. If companies in these regulated industries released a software or firmware "update" or product that REMOTELY approached the shoddiness, poor quality control and destructiveness of the ICS Android/Samsung/Sprint “update”, all affected products would be immediately reported by users to regulators and all affected products would be immediately recalled and criminal and civil penalties and fines would likely follow in EACH country that the product was marketed in.
3) A cursory examination of the history of regulatory oversight in the food, pharmaceutical and medical device industries is relevant and, perhaps, prescient. Just over a hundred years ago enough human suffering had resulted from adulterated foods, sham medical devices and poisonous "curative" concoctions that public outcry gave birth to the first governmental agency, the US Food and Drug Administration or FDA, charged with regulating the production and sales of foods, drugs and, later, medical devices. Every major strengthening of regulatory oversight in these industries in the ensuing century has been the result of some human tragedy that raised awareness that significant additional oversight of industry was needed to protect the public from unscrupulous and/or shoddy business practices.
The results of this regulatory history are: 1) food and health care consumers today have much greater assurance of and confidence in product safety and effectiveness than their counterparts of a century ago, 2) the food and health care products industries today enjoy a much larger and more confident market than would exist had such extensive regulatory oversight not developed over the last century, 3) the "bad apples" of the food and health care products companies today run the very real risk of significant and costly financial, civil and criminal penalties for attempting to foist shoddy, half-a$$ed, harmful and destructive products on an innocent and unsuspecting public, and 4) consumers and ethical food and medical products companies have benefitted tremendously from regulatory pressures that have weeded unethical and incompetent companies out of the marketplace.
4) The mobile computing industry and its consumers are still in their infancies. I suspect that the mobile computing industry today is no more welcoming of additional regulatory oversight than the food and medical industries were a hundred years ago when they were selling putrified "food", charlatan medical devices and poisonous pills. I further suspect that any significant improvement in the competency and ethics of today's mobile computing industries must come from consumer outcry and financial, civil and criminal penalties being levied whenever companies subject their users/customers to damaging products and services either as a result of incompetence or unethical practices. In other words, WAKE UP USERS, CONSUMERS AND CUSTOMERS AND DEMAND THAT YOUR MOBILE COMPUTING VENDORS FOLLOW THE FIRST RULE OF MEDICINE'S MOST SACRED OATH- "FIRST, DO NO HARM"! Also, class action legal professionals take note: there are HUGE dollars to be made here with hundreds of millions of consumers depending on and paying dearly for mobile computing products and services the world over.
5) As a former, long-time user of a Windows Mobile smart-phone, I am appalled at the pathetic state of software and firmware quality control in the Android world (I have no experience with iphones, so have no opinions to offer regarding that platform). Microsoft has utterly failed to gain any significant foothold in the world of mobile computing- this will likely be their undoing. Suffice it to say that I moved to the Android platform reluctantly and with hesitation. In fairness, until yesterday's botched ICS “update”, I was reasonably happy with my phone, and my confidence in the Android platform was growing steadily. I leave it to the reader to guess what the last 36 hours has done to my confidence in the Android platform and in all things Samsung and Sprint. The reader can also infer from the preceding narrative what my reply will be the next time I am prompted to "OK" an Android system "update", assuming I give a rat's rear about Android the next time an "update" is shoved down the throats of consumers.
6) To all culpable parties and all executives at Google, Samsung and Sprint (you know who you are), I ask two simple questions. Have you no shame? Have you no pride? This is the 21st century. Over-the-air firmware updates are neither rocket science nor brain surgery. I would go so far as to say that they are not particularly difficult. Yes, I have professional experience in developing and distributing/installing firmware updates to a widely distributed user base. The list of ALL that is required to perform a successful firmware update is small indeed. These are: 1) time, 2) money, 3) competent professionals, 4) firm and demanding leadership, and 5) unyielding quality controls and standards. There, you can count those on one hand. You can count them twice on your two hands. Note that “luck” and “profit” are not on the list. You make your own luck and profits by attending properly to the handful of items on the list.
Finally, I offer the ultimate executive/management tool for ensuring a successful OTA firmware update: the output of the 5 requirements listed above must pass the “RFT” test before the update is released to your unsuspecting users. The “RFT” test, of course, is the “Right First Time”/”Red Face Test”. That is, it must be done “Right the First Time” or it will NOT pass the “Red Face Test”. Or, as my mother said so eloquently all my formative years: “If you don’t have time to do it right the first time, tell me when you will make time to do it right the second time.” Should you require further assistance in implementing these requirements for future firmware/software releases I am available to help, for a nominal fee.
7) I am a professional business user and am NOT prone to exaggeration, flaming, ranting or the like. I rarely use my time to post in product support discussion groups or fora. In other words, it takes a great deal of inconvenience and damage to inspire me to post this type of comment. Congratulations Google, Samsung and Sprint, you succeeded in getting me to ignore my personal, professional and financial interests for almost two days- long enough to solve the problems you foisted upon me and long enough to pen this missive. My only question for you is: to whom should I send the bill for recovery of my lost time and wages?
M. E. Collison, Ph.D.
Collison-Carr Consulting, Inc.
To all interested participants,
I posted to several Sprint discussion threads invitations for people to read and/or participate in the thread listed above (94318). To date, I have been informed by Sprint that these invitations have been "rejected" by moderators of two threads (see below). No reason for these rejections has been given.
TO ALL INTERESTED IN RESPONDING TO THIS POST, YOU WILL NOT BE ABLE TO USE THE LINK BELOW BECAUSE SPRINT HAS REJECTED/DELETED THE ASSOCIATED THREAD, WITHOUT STATING WHY (SEE A COPY OF THE EMAIL RECIEVED, IMMEDIATELY BELOW).
If you are concerned about these rejections, and possible attempts by Sprint to suppress this thread, please contact Sprint with your concerns. Use the link to this thread to post your concerns: //http://community.sprint.com/baw/message/452349#452349
TO ALL INTERESTED IN RESPONDING TO THIS POST, YOU WILL NOT BE ABLE TO USE THE LINK BELOW BECAUSE SPRINT HAS REJECTED/DELETED THE ASSOCIATED THREAD, WITHOUT STATING WHY (SEE A COPY OF THE EMAIL RECIEVED, IMMEDIATELY BELOW).
Please feel free to use the text below in your responses, and/or add your own.
Also, please feel free to invite your friends, family, colleagues, etc. to view and participate in the original thread (94318):
Thank you much for your interest in this discussion and for defending free and open access to the same.
RE: possible suppression of community.sprint.com discussion thread 94318 by Sprint moderators
Sprint Communications administrators, as of 23Jul12 two Sprint moderators have twice rejected invitations (see copies of email notices below) to the Sprint community to participate in discussion thread 94318:
THESE REJECTIONS SUPPRESS FREE AND FULL PARTICIPATION IN THIS THREAD AND DO A SERIOUS DISSERVICE TO YOUR CUSTOMERS. Further, SUCH SUPPRESSIVE ACTS SERIOUSLY COMPROMISE SPRINT'S RELATIONSHIP AND STANDING WITH IT'S CUSTOMER COMMUNITY, AND THE LARGER MOBILE COMPUTING USER COMMUNITY AND INDUSTRY.
PLEASE HAVE THE THE TWO MODERATORS THAT REJECTED INVITATIONS TO JOIN DISCUSSION THREAD 94318 (SEE BELOW) IMMEDIATELY POST THE INVITATIONS TO JOIN THIS THREAD.
ALSO, PLEASE ENSURE THAT ALL SPRINT COMMUNITY DISCUSSION MODERATORS HONOR ALL INVITATIONS TO PARTICIPATE IN THIS DISCUSSION AND, FURTHER, REFRAIN FROM ANY AND ALL SUPPRESSION OF PARTICIPATION IN DISCUSSION THREAD 94318.
Currently Being Moderated
Below are some examples of posts from other discussion threads that have referenced this thread
The Sprint moderators enforce the community guidelines.
If you are posting comments in more than one area, disrespecting / baiting others (including moderators), flaming or trolling or posting off topic in a thread, those posts will be rejected. Continued posting in this manner is a bannable offense. Please review the guidelines for proper posting behavior.
Message was edited by: mapesy
I upgraded to ICS. Sure there are some quirk/issues/bugs that need to be resolved , but for the most part, I made the choice to upgrade , and I knew it was not perfect.
Nothing about the upgrade is causing me to lose sleep, nor productivity (I have a laptop for that), other than having to perform a factory reset after the upgrade.
Phone works. GPS works. SMS works. 4g works, Google Voice works.
I have only had this phone for 3 months, and it is still great!!
Hello mlbp, I do contribute to this site in a professional capacity, and I feel that it surely goes without saying that my fitness test of the phone is not the complete testing battery that is performed with the release candidates. I can assure you that this update was thoroughly tested prior to being released, and you are not part of a beta testing group. As of now our last communication is that the software update is still being released, and with any update we are collecting information about problems that may have developed from the update. These reported problems are generally kept to problems that can be duplicated after a factory restore, and are more than just preferential changes.
Thank you for your reply. Please see my questions/comments to the same in bold/italics below.
Hello mlbp, I do contribute to this site in a professional capacity,
Your professionalism has not been questioned. Rather, you were asked to clarify whether or not you are authorized by Sprint to respond, with Sprint's OFFICAL POSITIONS/REPONSES, to Sprint policy and business practices questions. Again, if your answer to this question is "yes", please email me official Sprint contacts so that I may verify your answer.
and I feel that it surely goes without saying that my fitness test of the phone is not the complete testing battery that is performed with the release candidates.
Again, results of your tests on a single phone are anecdotal and are of no help to the readers/participants of this thread in ascertaining to what extent Sprint tested the ICS update on relevant hardware/software configurations. If Sprint did large-scale testing before launch of the update, then posting quantitative statistical summaries of bug/error rates against different hardware and software configurations is relevant and helpful. Anecdotal results on one phone are not.
I can assure you that this update was thoroughly tested prior to being released, and you are not part of a beta testing group.
As I've stated before, evidence would suggest otherwise.
As of now our last communication is that the software update is still being released, and with any update we are collecting information about problems that may have developed from the update.
Is this Sprint's OFFICIAL response? If so, thanks in advance, for communicating it. I will continue to argue that it is unprofessional, inappropriate and unethical to use non-consenting, uninformed users for "information about problems that may have developed from the update."
These reported problems are generally kept to problems that can be duplicated after a factory restore, and are more than just preferential changes.
Many users are posting consistent reports of fundamental, basic functionality losses (significant decreases in battery life, significant losses of phone and 4G signal/service, loss of Native Swype functionality, loss of Native Swype personal dictionaries, loss of SMS text messaging, loss of Native Google browser functionality, etc.) resulting from ICS updates. Such reports can, in no way, be interpreted or construed as "preferential changes."
Just a comment (and please don't bash me for this ). I "was" truly trying to buy into your original issue (when you first posted) but.........I believe you have gone over the edge. I have seen your postings in "all" of the discussions and quite honestly ignore them. They are extremely annoying. I believe that is what those moderators are trying to tell you by deleting.
This update may have had changes that you do not like or have caused issues but to go on with this rant is ridiculous. Not trying to stop your freedom of speech but just do it somewhere else. You "chose" to update/you can ignore updates (I have done it for months for a preinstalled app that was updated in the Play Store and I don't use/don't want it but I can't get rid of it - there is my rant end of story).
I am not a Sprint employee - I am just a customer for over 12 years and use the Sprint Community to be informed (and/or inform if the need arises).
Please get a life and get back to work (your employer would probably like to see you more productive ).
Like a few other posters here I do dev work for a living. Testing in programming rarely ever matches a clinical trial model, especially with an upgrade as significant as this one. The ICS upgrade was, in layman terms, more of a complete rewrite than an "upgrade." This was because ICS was a combination of Gingerbread (2-3 years old) combined with Honeycomb and new changes just for ICS. Many things were reworked at a driver/hardware level to increase performance - and the E4GT has benefited from this. Sprint (at some level; how far down is unknown) and Samsung R&D both have had been testing ICS for approximately 4 months (From 2/17 to 6/18 based on build numbers). To say that they thoroughly tested everything is hard to say; rumors are that they did select several people for testing groups and asked them to put it through the proverbial wringer. But even your model of clinical trials often cannot catch everything - mainly due to sample size. I support a user base of approximately 2,500 users and even with extensive testing we have found that while we can effort to catch most things a goal of 100% error free programming is unrealistic at best.
Now I have one major difference from you - my Epic 4G Touch comes from a MVNO (Mobile Virtual Network Operator) called KDDI Mobile. Great rates but zero technical support - so at least if you have a problem you have someone to ask. I had no choice but to learn more about Android and how to support my family's devices if we were going to upgrade to a smartphone. No offense, OP, but a simple search even in the Sprint Communities threads could have shown that sites like XDA-developers had ICS leaks, including a copy of the now official FF18... and that many of the issues were known and discussed ad nauseum with one exception - Swype. This one didn't appear to be known as prevalently as other issues and certainly was not disabled like it was in the official release in previous leaks. You'll find that some of the more serious issues are still not addressed - and probably won't be as they don't apply to "stock" software.
Everything is not perfect and software will never be as we are only human (and humans do the development). Working in a medical field I am sure that you can appreciate risk management; while you may have had a significant inconvenience I suspect the larger customer base has not. Simply put I am certain that if it was that significant of an issue it would have been resolved. There are also other factors that people may forget - such as the applications a person has installed. Like any software installation this would have been done best as a "clean" install versus an upgrade; however, that option has not been brought to most phones yet. (If you would like to know how to do this please PM and I can send you some information.)
Finally, I must second the option that was given to you - you were under no obligation to accept the update. Blaming Sprint, Samsung, Google or anyone that happens to question you is childish and neglects the fact that you are the owner and end user for your phone. Just because an update is available doesn't mean you should rush into it - do you do the same whenever a new iOS or Windows release is out? I'm in my early 30s and learned over 15 years ago not to for one reason - bugs will always exist after a major upgrade. Would you rush to the same in new medical technology or drug therapies? Most would not until long term effects are better studied and known - LASIK is yet another example on that.
In the end you're on ICS - lesson (hopefully) learned that you should consider getting an app such as Titanium Backup or other backup tools to ensure that the things you really need are backed up, just like on a PC. And if you're really that unhappy about being on ICS please PM me and I can send you information on how to go back to GB.
Thank you for your time.
Most of these are good points, but there are still some simple things missing:
1. This is hardly the first time that software for this specific phone has been released by Sprint/Samsung/Google with no testing. How in the world could this phone be sold without a working GPS? Unless that just wasn't part of the testing, or they just didn't think people would care.
I am also in software development, and we have extensive testing procedures for all our mission critical software releases. We would be, literally, out of business if we have Sprint/Samsung/Google's finger pointing and 'it's not our problem' attitude. They should either fire everyone working in software quality control, or fire management who is possibly burying the quality reports and letting this moronic junk be released to paying customers on a regular basis.
2. People .. read these posts! Do not whine about how you don't have the update! You are LUCKY if you don't have the update. It's obvious that this is a catastrophe, and if you get the update you will just be another victim of this incompetence.
3. And, just wow. A major upgrade to the Android operating system goes out without testing. Think about all that means. They couldn't determine that battery life was going to be slashed because 'there are too many configurations out there'??? Really? Really, Sprint? Really Samsung and Google? They couldn't be bothered tryhing to send a text, just to see if Swype was still working? They couldn't be bothered to try going to a couple of webites, where they would have seen the reformatting bug? What do you suppose they actually did test? Maybe they placed a couple of calls and dusted off their lapels with 'well, that's done.'
Multiple and repeated failures. I still know not to try to use Google Maps without having several minutes to spare for the approximately 1/4 of the time that there will not be a sync. I'm not going to be pressuring any tech support ref to help me put on a buggy OS update, and no one else should, either.
I feel like you just took me to chruch with all that truth!!! LOL AMEN
Pinch to zoom and reformat text will not work after the update.
After several hours speaking with Sprint Tech support two visits to the Sprint store and a facory reset to solve this issue I finally got my answer.It's no longer available as an option. Period. The feature was removed because it belongs to apple and Samsung was ordered by a judge to remove this capability.
Nice, huh? Sure wish tech support would have told me that from the beginning...