The kit kat update has ruined my phone. Verizon had to send me a new droid, after doing a factory reset. The update caused a conflict of bluetooth and wifi. Could not see my home network with bluetooth running. Hours spent dealing with verizon support - at least 7 reps, New phone is without kit kat upgrade - not going to do it. Battery drain while using an app for a while. Never did before while using this app before kit kat.
Yes I have had the same issue... my droid worked great till the upgrade to kit kat
was on the phone with a Verizon rep for over an hour, no luck... Went to the store waited over an hour only to have someone say nothing we can do 3 people sitting around me same issue...
Thanks Verizon I will never get the 2 + hours I wasted with you back in my life ever...
If you turn off your Bluetooth you will connect and stay connected to WIFI just fine and battery life will be back to normal. I used the SmartActions app to turn off Bluetooth when I am on a WIFI network signal and it works great. After I am out of the range of the WIFI the bluetooth turns back on and it sync's with my car. I guess if you use Bluetooth at home that's not practical but it works great for me and other apps I have had problems with work great with KitKat.
Note 3.... kitkat 4.4.2 is KILLING my device. (Battery drain like CRAZY and won't charge via USB, lag, heating, wonky text behaviors, etc...)
WHEN will this be fixed??????
Jake, I don't mean for this to come across rude, but how are you certain of this? I posted in the Motorola forum for anyone to tell me if they know of these issues and for them to please tell me if there is a fix being worked on and acknowledge the problem and haven't seen one thing since.
This is in the Motorola Forums and was confirmed by Matt and Mark the Motorola Forums Managers. In this link is a description around the issue being discussed but the other Link I am looking for is the one that has Motorola's confirmation on the issue and their statement they are working on it. Actually if you read down into this link you will see Mark confirming they are aware of the issue but not sure if this is the one that list the fix being worked on. I will try to find that link as well.