The #1 Nexus 7 News, Discussion and Fan Site!
2012 Nexus 7 Discussion Forums (1st Generation) => Nexus 7 Help => Topic started by: sluggomagoo on December 02, 2012, 07:59:11 AM
-
I've just updated this as I had two different model headsets to test with. I'm starting to think I have a defective Nexus unit.
I’ve tried a couple of these Plantronics Bluetooth plt 510 and Model 330 bluetooth head sets ear piece that I have been using with my iPhone and Windows XP machines around the house. I typically only use them for phone calls either will the default phone or a google voice phone app. On the Nexus 7 I can get them to pare but when I make a phone call and redirect the sound the earpiece and it begins to screech like an AM radio next to a neon sign with a short in it. Ok so I’m showing my age now. For those of you that don’t know what AM radio is, please see Paul Harvey.
I have not had the opportunity to test any other Bluetooth ear pieces besides the PLT 510 and Model 330 yet. I’m wondering if anybody has with the Nexus 7 and a compatible google voice phone app.
-
Bump to the top due to an edit of the main quesiton.
-
There have been Bluetooth issues with the N7 so its possible this is one of them. I don't have any phone apps so I can't try it. I know my Gnex works fine.
-
You were already at the top.
Like Sarge mentioned Bluetooth has some issues right now. I have had problems sound wise with headsets as well. I had Plantronics HD and took them back. Google is aware of the problems and are supposedly working on them with BT.
Sent from my Nexus 7 using Tapatalk 2
-
I guess they do. As it stands right now I’m feeling like I have an inferior product :(. I called Google Support using my iPhone 4 with the same VOIP app and the Plantroics PLT 510. The sound was perfect ;D. The person I spoke to said that I was pushing the limits of the model (Nexus 7 16gig) and that’s why it didn’t work. He actually wasn’t really sure why it wasn’t working and when on to say I should go to the Nexus 7 – 32. So, I went back to the retailer and exchanged the unit for a Nexus 7 32gig and guess what? It has the same exact problem :'(. At this point I'm not sure if it's a problem with the Hardware or Jelly Bean. If I knew that, I could make a decision on whether or not I'm going to keep the unit. Otherwise I’ll have to take it back because having the ability to make VOIP calls is important to me. If this little iPhone can do this, why not this Asus unit?
-
I guess they do. As it stands right now I’m feeling like I have an inferior product :(. I called Google Support using my iPhone 4 with the same VOIP app and the Plantroics PLT 510. The sound was perfect ;D. The person I spoke to said that I was pushing the limits of the model (Nexus 7 16gig) and that’s why it didn’t work. He actually wasn’t really sure why it wasn’t working and when on to say I should go to the Nexus 7 – 32. So, I went back to the retailer and exchanged the unit for a Nexus 7 32gig and guess what? It has the same exact problem :'(. At this point I'm not sure if it's a problem with the Hardware or Jelly Bean. If I knew that, I could make a decision on whether or not I'm going to keep the unit. Otherwise I’ll have to take it back because having the ability to make VOIP calls is important to me. If this little iPhone can do this, why not this Asus unit?
Your not understanding. There is a bug right now with 4.2 with the Bluetooth. Google is aware and working on a fix. Should be fixed by the end of the month.
-
I think you're the one that doesn't understand. I'm not going to keep the device is someone can't tell me the details. Is it a hardware defect or a software bug. There's a difference for me because if it's a Hardware defect I'm not keeing the device. Do you understand that?
-
Dude. Please settle down. People have taken their time and tried to give you advice and you continue to be what seems incoherent and borderline disrespectful .If you are hell bent on Frapple and have given up on Android why are you still here? .
Oh Magoo. You've done it again .
Sent from my Nexus 7 using Tapatalk 2
-
I can't believe somebody from Google told you that you were pushing the limits of the Nexus 7 16GB and exchanging it for a 32GB would help??
How does upgrading storage capacity help a software Bluetooth bug....
On another note, bjs is right in that you should calm down because the people trying to help you are not Google employees and they are trying to help you on their own time so please show some appreciation.
Thank you.
-
I think he's just trolling.
-
Could well be...
-
I am temporally locking this topic for review. Thanks for everyone's understanding.
S.Prime
-
Guys...I've taken a look at the thread and I'm unlocking it but I'd ask everyone to please keep the tone of the thread positive. I understand sometimes these tech issues can be frustrating and sometimes it's easy to get out some of our frustrations on anonymous people in a forum. But that's not gonna help get the issue resolved any sooner so let's keep the tone positive.
Now as far as the bluetooth issues with the headset, I think there are many people that are having some bluetooth issues since the 4.2 update and since Google is aware of the problem we'll just have to wait for them to issue a fix. When Google or any company for that matter offers an upgrade to their software there is always a tradeoff of getting great new features with the possibility of there being a glitch or two that they didn't expect or foresee. Google has had a good track record of recognizing these glitches in a fairly timely manner and issues fixes for them. I'm sure this will be the case with this bluetooth issue as well.
Every company...Apple included...has glitches from time to time with their updates. Look at the fiasco of Apple's latest mapping software that has been written about all over the web. So since no company is immune to these kinds of issues and glitches as it's simply a part of progress...there's no point in getting angry or bent out of shape about them.
As owners of a Nexus 7 you are on the cutting edge by getting all the latest updates to Android first...before any other device. Part of the fun of owning a Nexus device is knowing that we are getting the latest and greatest Android version before anyone else. It's inevitable that there are going to be software glitches along the way but keep in mind we also get the fixes first as well...so in the end we still come out ahead. I'm confident that Google will fix the bluetooth issues and any other issues with the latest 4.2 update soon...just like they always do. Meanwhile we get cool new features like multiple user support...which you won't find on any Apple product ;)
Thanks everyone,
BFM
-
Wish I could like posts on tapatalk but well said.
Put simply to the OP, it is a software bug, not hardware. It will be fixed soon.
-
Well stated, BFM.
Sent from my SCH-I535 using Tapatalk 2
-
Thank you for unlocking the thread BFM. Very well stated indeed. I feel the frustration of the OP first hand. I have been struggling with BT issues for a long time. I first discovered the issues when trying to use a speaker months ago. It was frustrating because I didn't see many instances of it and I spent hours troubleshooting and wondering if it was my devices. I went through 5 different speakers, 2 headsets and what turns out to two different Nexus 7's. The new update seems to have just brought the problem into a brighter light. I have been active in some Android development forums where these issues have been discussed with Google development and they have assured the community that it is being worked on.
I love this little device. I love the operating system. It isn't perfect. I have faith that fixing these bugs is a priority and have already been through several updates in the short time I own my tablets.
I hope that Sluggo decides to hang in with us here and with his Nexus.
-
Maybe Magoo should use this....
http://www.ekids.com/products/robo-ihome/ (http://www.ekids.com/products/robo-ihome/)
Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2
-
Its funny. I see that name and it makes me smile. Used to love that cartoon as a kid. Oh Magoo you've done it again ! Jim Backus. Love him.
If that little thing works as opposed to my Jambox I will freak! Lol
Sent from my Nexus 7 using Tapatalk 2
-
From reading these messages my persecution was that the "N7 has an issue with bluetooth". So what does that mean? Is it a HW or a SW problem? I couldn't tell. I called Google again tonight and they claim that jelly bean 4.2 is the issue and they rolled out 4.2.1 to address some of the Bluetooth problems but, he wasn't sure if that was supposed to resolved my issue. Again nobody seems to know if the problem is with the OS or the hardware manufacture. As a consumer of these products I have a right to know! I have a right to a product without flaws and when there’s problem a public disclaimer that states the correct facts. That’s why IBM, HP, Microsoft, Apple and a whole lot of other companies publish customer advisories. They know they have to keep people informed otherwise the consumer market will eat them alive. So, again I don’t think I’m the one here that doesn’t get it..
-
Its funny. I see that name and it makes me smile. Used to love that cartoon as a kid. Oh Magoo you've done it again ! Jim Backus. Love him.
If that little thing works as opposed to my Jambox I will freak! Lol
Sent from my Nexus 7 using Tapatalk 2
You got the wrong guy. You're thinking of Quincy Magoo the cartoon character. Sluggo Magoo was an Irish immigrant turn cop in Boston in the 1800s. He was notorious for resolving issues the brown shoe way.
-
I am sorry that you feel persecuted. Definitely not my intention. I have horrible bluetooth issues as well so I can relate. I can assure you that you don't have a hardware issue. It is just a matter of making a decision to buy a cutting edge device and growing with it. Every device and operating system has its problems. IMHO Android happens to do an excellent job fixing their screwups.
Yes. I was thinking of Therston Howell.
Sent from my Nexus 7 using Tapatalk 2
-
Google puts out a "Customer advisory" as much as everyone else which isn't at all lol. I've never seen anyone do that they just update. I don't think you read through the posts or maybe our opinions don't mean much to you but we said 5 times that IT IS A SOFTWARE BUG THAT GOOGLE IS AWARE OF AND IS WORKING ON. NOT HARDWARE. None is persecuting you we just expecting you to read the peoples post before saying we didn't answer your question.
It doesn't matter what device you have, what OS you have, or how new or old it is, every software has bugs in it especially when it updates. Its a cycle. As we close the door and solve one another opens. Its how technology works. Now if you feel that strongly about how the nexus doesn't fulfil your needs sell it or return it and try a different tablet. Just know that the nexus line will have an update very soon to correct all of these issues.
-
+1
I've actually used an am radio to track down ground faults and broken neon (argon).lol master sign electrician. Signtist on irs forms.
That is full band rfi due to the Marconi Effect. (Should be Tesla Effect)
I doubt the blue tooth corruption is due to anything arcing, it wasn't there before some recent downdates.
I'm getting a bit grumpy waiting for an update to fix this too. Hang in there.
-
I knew it, I found out today that it's a Hardware problem. Someone gave me one of these (the exact same one) for Christmas and it doesn't have the problem. I can use it as an IP phone with my bluetooth headset and it works perfectly. It has the same exact software on it as the one I puchased on 12/2. I called Google again today and they said they don't know what's going on and I would have to call the manufacture to get more information about the problem. Yea will bull Schit on that. So far I've made 12 phone calls on this one without a single problem. I went down to the retailer and retured the defective unit (second one) without any questions asked and it was 24 days old. Those of you sitting around waiting for a software update you bet be aware of what I went through.
-
Glad you figured it out.
Sent from my Nexus 7 using Tapatalk 2
-
Someone gave me one of these (the exact same one) for Christmas and it doesn't have the problem...It has the same exact software on it as the one I puchased on 12/2. I called Google again today and they...I would have to call the manufacture to get more information...I've made 12 phone calls on this one...retured the defective unit (second one) without any questions asked and it was 24 days old.
Did you return the Nexus or the bluetooth device? Your post isn't clear as to what you identified as the issue.
-
This is an issue that is not cut and dry. I am glad that you have a working system together but it is NOT as simple as a bad hardware /BT device. I have been thru several of each. There are hundreds if not thousands of people struggling to have the closure that you seem to have right now. You are lucky.
Sent from my Nexus 7 using Tapatalk 2
-
The last time I called Google they suggested that I contact Asus for more information and the last two times I called nobody ever heard of any bluetooth problems with the OS above jellybeen 4.2.1. One person went on to say that 4.2.1 has addressed the known bluetooth issues and he seemed to think that the issue was defective hardware. In my experience when you have features that only work on some devices and not others, it's typically either a firmware or hardware problem. I've been working with computer hardware since the early 90s, have a A+ certification and renewed it a few years back, and I'm considered the hardware go to guy for my company. This smells so much like a hardware problem it's stinking up the place. Since you can't update the firmware, replacing the device is the prudent thing to do.
-
Thanks for your contribution. If the problem does ever recur, it might still be a firmware issue. There are ways to change the firmware, either with custom roms or reverting to previous versions.
The wifi and bluetooth both are in the 2.4ghz band. How they keep from interfering is beyond me.
The only bt problems I've seen have been with game controllers that no longer work with 4.2.1.
My bt headset has dropouts occasionally but no screeching. Admittedly, I haven't tried using it next to a microwave.
Just for grins, (and to rub our noses in it), post a screen capture of your kernel and build versions in settings, about tablet.
Software companies will always blame the hardware and vice versa in an attempt to stave off class action lawsuits. Search xda and google issues threads for multiple instances of bluetooth problems.
In short, the google tech was lying or misinformed.
-
Sorry but this forum won't allow for the attachment. It kept saying error occurred, upload folder is full and/or contact administrator.
-
I get that too. I'm going to delete all my old uploaded screen captures and convert newer ones to 640x480. It seems to be a data cap on uploads per user. I haven't tried using the mike on my bt headset as I have a real phone which I use to cuss out all the telemarketers to make their jobs as lousy as possible so they will quit. Calmly explaining the national do not call registry does not work. Call blocking helps, but I only get to block 30 on my phone and 40 with the phone company. So they get rotated. Pita.
-
Would like to know if you ever encountered anymore issues related to this. It was a strong thread and had many folks involved. Did the exchanged unit solve everything in an instant or is the problem intermittent?
Sent from my Nexus 7 using Tapatalk HD