Usually I am pretty quick when it comes to updates. I like having the latest (just short of beta testing) and don't get bothered by the small stuff when it doesn't work. With Android it happens more often than not and even with having a Nexus device you can feel the priority level from Google with so many devices that have those lingering problems.
After updating to Kit Kat (4.4) I came across one of the few times that I actually regretted updating a device, and I haven't been the only one. Many people have even created a Google group surrounding one glaring issue in 4.4 (Link HERE) pertaining to Bluetooth and its reliability. I for one use it in my car daily, from streaming Pandora or making calls to family on the way home it's an easy and safe(ish) way to accomplish my tasks. Once I had upgraded to Kit Kat though it was another ball game entirely. From my phone crashing weekly, to being unable to turn on or off my Wifi or Bluetooth, to finally having my Bluetooth cut out every 30 seconds or so during phone calls drove me mad.
Like most people I went to Google and instead of doing a technical support call for help I searched for my issues instead. It lead me to the group (linked above) and after reading 8 pages (then) of user responses I came to two conclusions.
1. Google doesn't see the issue as high priority enough to fix out of cycle from another main release.
2. The only sure fire way to remove the problem was to flash back to 4.3.
I read up one some pretty helpful posts on flashing an older rom onto my Nexus and took a night to work through it. Though the page linked for instructions was lacking in some ways I was able to trail and error through commands and files from my Windows machine and flash the phone back successfully. After setting up my phone from scratch (I have it back up but never use it) I tested it out in the car the next day. All the issues I had were solved and found myself back in the land of peace and tranquility. I do miss some features of Kit Kat but none of which are more important to me than a working Bluetooth connection. Big thanks for everyone who posted and the mounds of solutions tried. Google never chimed in once, but like normal the Internet is there to save the day.
Showing posts with label issues. Show all posts
Showing posts with label issues. Show all posts
Friday, March 7, 2014
Nexus 4 and Android 4.4 Bluetooth Issues
Labels:
4.0,
android,
bluetooth,
bluetooth 2.0,
bluetooth issues,
connection loss,
drop out,
google,
google product forums,
issues,
kit kat,
nexus,
nexus 4
Location:
St. Louis, MO, USA
Wednesday, March 5, 2014
Intel WiDi Stops Lync 2013 from Recognizing Audio Devices
We have used Lync 2013 for a while the company I work for and overall with little issues (amazingly). However the other day I attempted to join a conference call and utilize my built in webcam/mic but found that Lync couldn't see any audio device at all. This was strange considering it was showing up in the computer management console, and in recording devices. I could even use the microphone and record with windows built in recorder so that was odd too.
I attempted first a repair of Lync 2013, but no dice. Then I re-installed my Dell audio drivers, but no luck there either. A bit of Google searching lead me to just a few articles stating that Intel's WiDi application caused some problems with audio devices. Sure enough one of the posts in particular was on Lync specifically so I decided to give it a shot and uninstall. After a quick reboot Lync was perfect again and I was without one more useless program (to me at least). Dell (from whom we buy our laptops) has components in most of their laptops which include this application, however I have never used it. Uninstalling it did not show any unknown devices in computer management or prompt for driver installation every time the machine booted up so I'll be making sure to uninstall this from all new deployments of laptops within the company.
I never could figure out the "why"behind the failure for the applications to not play nice, but what's fixed is fixed.
I attempted first a repair of Lync 2013, but no dice. Then I re-installed my Dell audio drivers, but no luck there either. A bit of Google searching lead me to just a few articles stating that Intel's WiDi application caused some problems with audio devices. Sure enough one of the posts in particular was on Lync specifically so I decided to give it a shot and uninstall. After a quick reboot Lync was perfect again and I was without one more useless program (to me at least). Dell (from whom we buy our laptops) has components in most of their laptops which include this application, however I have never used it. Uninstalling it did not show any unknown devices in computer management or prompt for driver installation every time the machine booted up so I'll be making sure to uninstall this from all new deployments of laptops within the company.
I never could figure out the "why"behind the failure for the applications to not play nice, but what's fixed is fixed.
Labels:
audio,
audio driver,
conflict,
dell,
devices,
driver,
intel,
intel widi,
issues,
lync,
lync 2010,
lync 2013,
recording devices,
widi,
windows
Location:
St. Louis, MO, USA
Saturday, January 11, 2014
Monoprice Cables and Dell Switches - A Strange Affair
I spent most of my day today trying to replace cabling in our closet to tidy up the place. After purchasing 2 pass through patch panels to route cables from the back of the rack to the front in a neat manner I came across issues with some ports not working and coming online with my Dell switches.
All ports in the pass through jacks tested fine, cables tested fine and the switches worked after testing as well.
After 2 hours of fooling around and trying this and that I found my culprit.
The cables I ordered from Monoprice (in this case 3ft and 1ft yellow Cat6 cables) seem to have their pins clamped a bit higher than other cables I have ordered (especially in this case since I ordered blue 3ft cables in the same order and their pins are placed lower in the RJ-45 ends) and cause a loss of connectivity with my Dell switches.
I am assuming at this point that Dell switches have their "spring" pins set just a tad bit lower than normal as my Fluke tester worked just fine with said yellow cables. Looking under a microscope to compare the blue 3ft to yellow 3ft and 1ft cables I was able to confirm that in fact the pins were in fact higher on them.
What a mess, I will have to return the whole order and reorder new ones (and this time maybe from Cables 2 Go). Be on the lookout for the strangest issues, they can creep up anywhere.
All ports in the pass through jacks tested fine, cables tested fine and the switches worked after testing as well.
After 2 hours of fooling around and trying this and that I found my culprit.
The cables I ordered from Monoprice (in this case 3ft and 1ft yellow Cat6 cables) seem to have their pins clamped a bit higher than other cables I have ordered (especially in this case since I ordered blue 3ft cables in the same order and their pins are placed lower in the RJ-45 ends) and cause a loss of connectivity with my Dell switches.
I am assuming at this point that Dell switches have their "spring" pins set just a tad bit lower than normal as my Fluke tester worked just fine with said yellow cables. Looking under a microscope to compare the blue 3ft to yellow 3ft and 1ft cables I was able to confirm that in fact the pins were in fact higher on them.
What a mess, I will have to return the whole order and reorder new ones (and this time maybe from Cables 2 Go). Be on the lookout for the strangest issues, they can creep up anywhere.
Location:
St. Louis, MO, USA
Subscribe to:
Posts (Atom)