Original Bionic (5.5.886) had high-pitch whine coming through the audio line when using wired headphones. Bug was addressed and fixed with the (5.5.893) update.
So far, I'm hearing the high-pitch whine in the wired headphones again when listening to audio in the ICS leaks. I have been on (6.7.230) and just updated to (6.6.232).
Can anyone else confirm this behavior? Any of the slim few on .235 noticing this?
Hopefully, Motorola fixed this before releasing the build. It's really a deal-breaker when using headphones often...
Yes it happens on mine as well. 232 build.
I use bluetooth headphones, so I've never noticed. I do use the headphone jack in my car though, but I have a ground loop isolator (alternator whine in the Mazda 3), so I don't notice it there either.
I know this is of no help to you, but I'm on 230 and do not have that audio problem. However, this particular Bionic never had that issue on GB either.
Sent from my DROID BIONIC using xda premium.
My Bionic has had it from the beginning, stock or custom ROM. I was under the impression it was a hardware issue, not software?
Reports are that it is better in the .235 leak, but since you cannot ever go back from that leak, I'd recommend waiting until ICS goes live.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
I was happy with 232 except for the return of the whine so I went ahead and wiped it and went to 235. 235 still has the whine, perhaps even worse for me than on 232. Argh. So now I'm stuck until something new. Maybe I'll safestrap and try a custom.
Has anyone tried a factory data reset? I'm a Bluetooth person on my handheld.
But I had this problem with my Xoom after update to JB on my headphones.
The factory data reset did fix the problem.
greeneink said:
Has anyone tried a factory data reset? I'm a Bluetooth person on my handheld.
But I had this problem with my Xoom after update to JB on my headphones.
The factory data reset did fix the problem.
Click to expand...
Click to collapse
Just did, reinstalling apps now but can already confirm still whines on headphones.
Has anyone with the headphone whine problem (as myself) tried any of the newer ICS leaks since the last post in this thread? Is it still there? I'm also curious if any of the Kexec ROMs will ever fix it.
I still have the problem on 246, and all of the older leak versions I've tried.
Sent from my DROID BIONIC using Tapatalk 2
Related
Greetings,
I have a question for other rooted nook color owners. Specifically, has anyone else had issues with balance on the NC when using various video/audio applications? I'm trying to figure out if it's a software or hardware issue in this case. I've used a couple IEMs and headphones and they all have the same issue. Sometimes the levels will be equal, but should I unplug and plug my headphones back in the right channel is substantially louder than the left.
Anyone know if this is a software issue, or should I assume it's hardware? What's the best way to confirm which it is?
zinjashike said:
Greetings,
I have a question for other rooted nook color owners. Specifically, has anyone else had issues with balance on the NC when using various video/audio applications? I'm trying to figure out if it's a software or hardware issue in this case. I've used a couple IEMs and headphones and they all have the same issue. Sometimes the levels will be equal, but should I unplug and plug my headphones back in the right channel is substantially louder than the left.
Anyone know if this is a software issue, or should I assume it's hardware? What's the best way to confirm which it is?
Click to expand...
Click to collapse
I have noticed it when watching movies (even before my NC was rooted). What's more, I have noticed that L and R are reversed sometimes (always?). In any case, a reboot solves the volume imbalance problem (though not, as far as I can tell, the channel reversal.)
Are you positive the headphones are plugged in all the way? You got to really push hard to get the headphones all the way in.
Sent from Fascinate SuperClean 2.9.2 Voodoo Using Xda Premium App
ajd88 said:
Are you positive the headphones are plugged in all the way? You got to really push hard to get the headphones all the way in.
Sent from Fascinate SuperClean 2.9.2 Voodoo Using Xda Premium App
Click to expand...
Click to collapse
Positive, the grounding jacket is touching the unit chassis. It's going in the same distance from when it does work and when it doesn't. It's really . . . weird.
dsf3g said:
I have noticed it when watching movies (even before my NC was rooted). What's more, I have noticed that L and R are reversed sometimes (always?). In any case, a reboot solves the volume imbalance problem (though not, as far as I can tell, the channel reversal.)
Click to expand...
Click to collapse
I plan on contacting B&N regarding it. Did you try contacting support to see what they said?
zinjashike said:
I plan on contacting B&N regarding it. Did you try contacting support to see what they said?
Click to expand...
Click to collapse
No, when I realized that a reboot solved the balance issue, I just decided to let B&N handle it with their next software update. As for the inverted channel issue, that's more of an annoyance than anything. I'm hoping it's software, but if it's hardware, it's not enough to make me give up my NC for replacement.
Using ICS 232 leak I am able to utilize Webtop 3.0 nicely. I have encountered an issue with the HDMI out of my phone being a fixed volume. If I change the audio routing from HDMI to phone speaker I am able to change the volume on the phone. Every time I put it in the Lapdock I must change the routing manually to Phone Speaker. I am trying to find out if anyone else has had this issue.
I assume if I were to hook up to another device besides the Bionic Lapdock I would control the volume from the other device but the Lapdock even has nice fancy function keys for this purpose. Should you have installed ICS Leak 232, have a Bionic Lapdock and a Bionic (goes without saying) I would appreciate you seeing if you see the same issue. Failing that I would be curious if any other Lapdock model exhibits the behavior.
Thanks a bunch!
<rant> The one thing that kind of sticks in my craw is not that I am beta testing for Motorola and VZW. It is the fact that VZW and Moto want to tell you that you voided your warranty because you used the software that they intentionally leaked. How many leaked copies of Windows betas do you really see? Certainly not 4 different releases in less than 6 weeks. These companies are smart. I don't mind testing stuff, just don't tell me that their software leaks void their hardware warranty. </rant>
I'm with you. I've had broken audio control since moving to Webtop 3.0 on ICS leaks. I've searched the forums (including the RAZR and Atrix forums) to see if there had been problems on other devices and I only found one proposed way to fix it- turn off the audio effects when in webtop. It didn't work for me though. This might be something that just gets fixed along the way to a stable build. I've also had the same thought (that you mentioned also) that it could just be a problem on the "Bionic Lapdock" and not the newer models. Hopefully we get some answers soon?
I'm on the .232 leak and the volume keys work just fine on my Lapdock 500. Works with audio effects turned on or off. Wonder what's different?
[edit] Just noticed you are both using the Bionic Lapdock rather than the 500 -- that must be it. Hopefully they fix it in a future build.
I'm going to give the audio effects controls a try a little later. I could simply use external speakers with the headphone jack as I have an audio cable to use with my stereo.
I'm just frustrated because I was honest with VZW about what I had done with my phone and now it is out of warranty. No need to wield empty threats about another vendor, it's about the network, but their business practices leave something to be desired.
Sent from my DROID BIONIC
Now I know why my Lapdock was only $50.
Crippled hardware because they don't wanna spend the time or effort to develop the drivers properly. I do have to say that the webtop 3.0 does run very nice.
I never ran the earlier versions of webtop I don't know the difference.
Sent from my DROID BIONIC
Honestly I plug my radio in most of the time because of how awful the speakers sound in the lapdock but it would be nice to use the device properly.
Sent from my DROID BIONIC using xda app-developers app
I've got a New Potato Tunelink I've been using with my old Verizon Galaxy Nexus successfully for about a year. Since that time I've gone through several ROMs and Android versions, 4.2.1, 4.2.2 and now 4.3. Bluetooth audio always worked fine with Pandora, Google Music and Pocket Casts.
I got a Verizon Moto X yesterday and while I can pair it with the Tunelink and it plays, music skips, stutters and is unlistenable. Voices sound worse, they're low or deep and also skip and stutter.
I've Googled and found lots of "bluetooth stuttering" threads all over (like this one) but none of the things I've tried have improved the audio. I've turned off wifi, changed wifi settings, tried it with and without the battery saver turned on. I took it out of the box and set it up yesterday, I doubt a factory reset would do anything for me.
I can plug in the stereo minijack and it sounds fine but the Tunelink was supposed to stop the inconvenience of that and did, until the Moto X.
Any ideas? Anyone experiencing the same issue?
I've been using J3 Bluetooth headphones and the moto x has been performing better than my GS4 did. I can put the phone down at my gym and walk 30 feet away and it doesn't skip or degrade.
I don't think it's the phone.
Have you tries re-pairing?
Sent from my XT1060 using xda app-developers app
skinien said:
I've been using J3 Bluetooth headphones and the moto x has been performing better than my GS4 did. I can put the phone down at my gym and walk 30 feet away and it doesn't skip or degrade.
I don't think it's the phone.
Have you tries re-pairing?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yes, re-paired several times. If I go back to the Galaxy Nexus it sounds fine.
ShanMan14 said:
Yes, re-paired several times. If I go back to the Galaxy Nexus it sounds fine.
Click to expand...
Click to collapse
Just to be clear, I have the Verizon variant of Moto X also. Have you considered trying a replacement Moto x?
Also, the Moto X is bluetooth 4.0 and the Galaxy Nexus is 3.0. Could it be that your headset doesn't play nice with 4.0?
skinien said:
Just to be clear, I have the Verizon variant of Moto X also. Have you considered trying a replacement Moto x?
Also, the Moto X is bluetooth 4.0 and the Galaxy Nexus is 3.0. Could it be that your headset doesn't play nice with 4.0?
Click to expand...
Click to collapse
I haven't considered a replacement yet, the fact the stores don't have them is a factor.
Good point about 3.0/4.0, the specs on the Tunelink don't specify, I'll contact them.
ShanMan14 said:
I haven't considered a replacement yet, the fact the stores don't have them is a factor.
Good point about 3.0/4.0, the specs on the Tunelink don't specify, I'll contact them.
Click to expand...
Click to collapse
Good luck!
Yeah - no problem here as well... Do you have another blu tooth device you can try with?
skinien said:
Just to be clear, I have the Verizon variant of Moto X also. Have you considered trying a replacement Moto x?
Also, the Moto X is bluetooth 4.0 and the Galaxy Nexus is 3.0. Could it be that your headset doesn't play nice with 4.0?
Click to expand...
Click to collapse
rman18 said:
Yeah - no problem here as well... Do you have another blu tooth device you can try with?
Click to expand...
Click to collapse
I have my Galaxy Nexus which works fine.
I ordered this and it should be here today to test out.
I have the same issue with a Motorola Roadster 2. Static is pretty bad when on the phone with other people.
The Kinivo BTC450 Bluetooth Hands-Free Car Kit arrived yesterday and works great. It seems to be the X with the Tunelink. I actually like the Kinivo better as it also allows phone calls and the remote/mic allows me to start/stop music and podcasts.
I also have a Tunelink and am having the same stuttering issue with the audio. Works great with my Nexus 4. Not so much with the Moto X.
+1 for the diagnosis of the Tunelink not playing nice with bluetooth 4.0
I also am experiencing issues with my Moto X and bluetooth. Something tells me it is due to the custom bluetooth 4.0 implementation that Motorola used for Android 4.2.2. I figure that the only "real" fix will be waiting for the 4.3 OTA to add official support.
I tried everything under the sun to resolve my issues. I did a factory reset, un-paired and re-paired, tested on multiple devices and even did a RMA with Verizon. I called up Motorola prior to the RMA and told them about the issue and they said that it was a defective unit. I'm planning on calling them again today to let them know they have an actual issue with at the very least the verizon moto x.
As a follow-up, while my new Bluetooth unit does not stutter and sounds great, my phone now consistently reboots itself after pairing but not until I initiate playing something.
Thankfully the phone reboots quickly.
I am going to wait till the first OTA is released and see if it resolves the issue or not.....if it still has the problem then I'll have to try a 3rd RMA.
I have LG stereo headset, jlabs crasher speaker, and an eclipse headunit and i dont' have any issues with playback. Are you just letting things play or are you messing with the device while playing music? I know on both my Moto X (vzw) and GS3 i'd get some stuttering some times if the phone was under some heavy usage.
I'm experiencing stuttering on my VZW Moto X DE with my Tunelink as well. I had stuttering on my GNex on one version of 4.2.x but all other builds worked fine and it got much better when I upgraded to 4.3, so I'm hoping a new Moto X 4.3 rom will fix this...
Add me to the list of people having the stuttering issue with the Moto X (GSM Dev Edition) and the TuneLink Auto BT unit. Frustrating as hell. I hope the KitKat upgrade fixes it.
Bump. Tunelink is stuttering for me too. Must be incompatible. My tune link is wired to the headphone jack (not using FM transmitter). Sucks.
640k said:
Bump. Tunelink is stuttering for me too. Must be incompatible. My tune link is wired to the headphone jack (not using FM transmitter). Sucks.
Click to expand...
Click to collapse
Not tunelink related but when listening to my Moto X in car with my Alpine UTE-42BT I notice a crazy amount of skipping/stuttering. Doesn't mater what music player I use. If I turn the device off and restart it seems to fix it for a brief time.
I created a post here about my issues. http://forum.xda-developers.com/showthread.php?p=48496071#post48496071
Anyone else having the same problems or have a solution it's driving me insane!?
apologies i forgot about this thread. i bought my TuneLink over two years ago. i emailed them and they are honoring my warranty by sending out a new revision of the device. its one they're currently working on releasing and i've been on a waiting list to get it.
so far i've sent in my current device and they sent me the same revision. i'm still waiting on the new device, which is supposed to take care of all issues. I have a Vizio soundbar at home and i have no stuttering issues. looking forward to the update.
Since upgrading to 4.3 on my Note Ii, I have noticed that when the pebble is connected to my phone, it causes the sound quality to diminish significantly. Sort of like resembling a low bitrate MP3.
This doesn't seem to be a problem on the Nexus 4 or on the 4.1.2 version of Android that was on my Note II before.
I was wondering if anyone has any suggestions, as it is a bit of a dealbreaker for me?
Thank you
Don't have any issues like yours but I have a Note 3.
Sent from my SM-N900P using Tapatalk
Shawheim said:
Don't have any issues like yours but I have a Note 3.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Glad to hear you don't have this problem on the Note III. Strange because you're also on 4.3 (I think), unless you've already been updated to kitkat.
It's infuriating though and it's really making me want to change phone or cancel my pebble steel order and sell my current one too.
I am on 4.3. Haven't got my KK yet, had it this morning and wasn't on WiFi. Now I have to wait. But I've had my pebble since September and haven't had any issues with sound or anything. I've connected Bluetooth headsets while having the pebble connected and no issues. Only issue I've had is the talk back bug with the stock browser.
Sent from my SM-N900P using Tapatalk
Just tested this on a stock HTC One (also on 4.3) and it has the exact same issue. Seems to be a problem with Android itself. I find it hard to believe that this problem isn't widespread on 4.3. Will test it on a Note 3 tomorrow.
I hope the Kit Kat update gets a move on...
Streaming Bluetooth audio to my LG soundbar works only within 6-7 feet, everything beyond it gets choppy frequently.
I did the same experiment with an older ipad2, sgs2 and the newer Nexus 7 2013. All worked fine within the soundbars specs, 30ft. The nexus actually stretched it the furthest, I streamed from my second floor with only one slight interruption.
Is it that my phone is faulty or is just the compatibility with this exact soundbar? Are there settings or other means to improve the bt signal/range?
Sent from my HTC One
millicent said:
Streaming Bluetooth audio to my LG soundbar works only within 6-7 feet, everything beyond it gets choppy frequently.
I did the same experiment with an older ipad2, sgs2 and the newer Nexus 7 2013. All worked fine within the soundbars specs, 30ft. The nexus actually stretched it the furthest, I streamed from my second floor with only one slight interruption.
Is it that my phone is faulty or is just the compatibility with this exact soundbar? Are there settings or other means to improve the bt signal/range?
Sent from my HTC One
Click to expand...
Click to collapse
is your phone stock or custom recovery / rom
Viper rom latest with elementalx 18.0. Also on latest sense fw.
I will definitely try it again with stock kernel although I doubt it's a kernel issue. I might try perhaps a different radio but if anyone knows a proven way to make it work.. I surely appreciate any input on this.
Sent from my HTC One
millicent said:
Viper rom latest with elementalx 18.0. Also on latest sense fw.
I will definitely try it again with stock kernel although I doubt it's a kernel issue. I might try perhaps a different radio but if anyone knows a proven way to make it work.. I surely appreciate any input on this.
Sent from my HTC One
Click to expand...
Click to collapse
Using a RUU back to stock always worked on my AT&T M7
I seemed to have that problem when using the Developer Edition software versions
In case someone experiences the same issue and hopefully before rma-ing his/her soundbar, I isolated the issue to the custom kernel I was using. As soon as I reverted to stock I could take my phone 30ft or more without a single hiccup.
Sent from my HTC One