No problems after kitkat.. Phone is now perfect.. Great battery life and very smooth and quick... Finally.
Posted via Android Central App
I am thinking of getting the s4, should I wait till all the issues are fixed with the 4.4?
Sent from my DROID RAZR HD using AC Forums mobile app
What's the build number ? Mine is NB3
Updating my S4 to kitkat as i type this..hope all works well cause i already have issues with 4.3.. if its buggy, ill just flash it back to 4.3.
SIM card and ALL contacts, photos, calendar, everything that was saved on the phone gone when doing a factory reset. The update attacked the card I think and we lost everything, was told the reset would work and wouldn't affect anything on the Samsung website.
DONT DO THIS !!!
It might work for some but I wouldn't take the chance... There are so many different problems and it seems like each phone is reacting differently to this update!
Seriously I am so sad. I thought upgrading to 4.4.2 would fix many things for my s4 but it just got worse. I admit that the system is much more smoother now but it's far away from faster. My phone won't unlock/wake up now.. I can swipe on the black screen and it would make the unlock sound but the screen would still not respond/stay black and there is nothing to do unless I pull out the battery. my keyboard is jamming; it happens often that I can't type anything, can't press anything and again, theres nothing to do unless I pull out the battery. I never experienced any of this before the update and it's making me upset because I feel like it's really damaging my only 5 months old s4. I never had to restart my device before and now I have to restart it at least twice a day.. Anyways, I absolutely do not recommend this update.. but for those who their phone seems to be fine, well. you are lucky.
Edit: I'm not the only one!!
Sprint Galaxy S4: Kitkat Update Screen Problem - Android Forums at AndroidCentral.com
Galaxy S4: I Think I'm Beginning to Despise This Phone - Android Forums at AndroidCentral.com
Videotron / S4 / SGH-M919V
Posted via Android Central App
Seriously I am so sad. I thought upgrading to 4.4.2 would fix many things for my s4 but it just got worse. I admit that the system is much more smoother now but it's far away from faster. My phone won't unlock/wake up now.. I can swipe on the black screen and it would make the unlock sound but the screen would still not respond/stay black and there is nothing to do unless I pull out the battery. my keyboard is jamming; it happens often that I can't type anything, can't press anything and again, theres nothing to do unless I pull out the battery. I never experienced any of this before the update and it's making me upset because I feel like it's really damaging my only 5 months old s4. I never had to restart my device before and now I have to restart it at least twice a day.. Anyways, I absolutely do not recommend this update.. but for those who their phone seems to be fine, well. you are lucky.
Edit: I'm not the only one!!
Sprint Galaxy S4: Kitkat Update Screen Problem - Android Forums at AndroidCentral.com
Galaxy S4: I Think I'm Beginning to Despise This Phone - Android Forums at AndroidCentral.com
Videotron / S4 / SGH-M919V
Posted via Android Central App
Umm.... Yeah. That's normally how it works. Did you back up your data first? If you back up your data first, typically via Kies, or any number of other cloud services that allow backing up contacts, etc, (I use One Media Hub) you wouldn't have lost them. Factory resets don't "attack" your phone or your card. It does exactly what it says it does, returns your phone to its state it came from from the factory - empty.
capT
Umm.... Yeah. That's normally how it works. Did you back up your data first? If you back up your data first, typically via Kies, or any number of other cloud services that allow backing up contacts, etc, (I use One Media Hub) you wouldn't have lost them. Factory resets don't "attack" your phone or your card. It does exactly what it says it does, returns your phone to its state it came from from the factory - empty.
capT
But that's not a bug---it's, alas, a feature.