What's up. I've been having really bad bluetooth issues lately. I'm running the latest October ROM and its pretty bad. When I go for a run and out my phone in my pocket the sound breaks up. Also if I go more than a few feet from my phone it cuts out.
Any way to fix via software tweaks or other means??
Related
So far I've tried both TnT Lite and the VEGAn roms and by far I prefer the VEGAn rom. My only issue is every once in a while, usually when something uses audio (movie, music or even a typing sound) I get a static/hissing/sounds like your TV is on a channel that doesn't have anything on it sound.it goes away after a couple seconds, but it's at full volume, doesn't matter of the audio is turned all the way down and will do it again if I do anything. I've tried the add and remove headphones, but it doesn't work. I've wiped and reinstalled the ROM, but it always comes back. The hissing/static sound happens on either the headphones or the speakers. Audio will work again when I reboot the unit but only for a little while. Any solutions?
There's another thread about a similar issue. 5 or 6 people responded that they get a crackle or pop every now and again. I get it also. One guy had it with the stock ROM. Another guy gets it through headphones when jogging.
No solution posted that I can find.
Thanks for the info. I guess it's either a hardware issue or an incompatibility between android and the driver.
I'm getting constant speaker hiss through the headphone jack, even when nothing is playing and when the display is off. Only exception is if the tablet is fully powered off. I'm flashed to VEGAn right now, but was getting the same hiss with TnT Lite. Didn't leave the stock ROM on long enough to know if it's happening there, too.
I get the same problem with some low volume hiss via headphone jack. Only happens when devices is in "sleep" -- not when powered off...
Sounds like this ROM (Vegan 5.1) leaves the the jack powered when in sleep...
My phone had the same problem until the ROM it was based on got fixed (it's running a CyanogenMod derivative)
It may be fixed in the CM7 builds -- so given that the next Vegan will incorporate some CM code as well, I'm hoping it will be fixed soon...
It has to be draining the battery if it is true that the jack is powered when in sleep...
First I guess it'd be important to say I'm using Ravers (awesome) Beatiful SG4G build and I love it. It's terrific. The only thing "plaguing" me is bluetooth.
I have a Motorola S9 headset, which sounds beautiful. The problem is sound randomly seems to cut in and out at times, especially when walking around the city. I tried disabling wi-fi, but to no avail. It's fine sitting in my dorm, and seems to always be ok when the screen is on. But if I walk around with it in my pocket, sound goes to crap. Is there any known fix to regain stability.
hampsterblade said:
First I guess it'd be important to say I'm using Ravers (awesome) Beatiful SG4G build and I love it. It's terrific. The only thing "plaguing" me is bluetooth.
I have a Motorola S9 headset, which sounds beautiful. The problem is sound randomly seems to cut in and out at times, especially when walking around the city. I tried disabling wi-fi, but to no avail. It's fine sitting in my dorm, and seems to always be ok when the screen is on. But if I walk around with it in my pocket, sound goes to crap. Is there any known fix to regain stability.
Click to expand...
Click to collapse
have u had that issue on all gb or is this ur first gb?
Sadly that's hard to say. I've been using your roms since Audiophile Froyo. I just got the headset today, so I haven't been able to see if it's a rom issue, phone issue, or a headset issue yet. I'm trying to figure out if anyone else has already been through the process before I flash my phone a few times troubleshooting.
Looking around, signal issues are common with my particular headset, so it may not be a phone issue. I'll try and do some flashing to further test it, and try to use it with other phones.
So I think I figured it out and sadly I don't think software can fix it. The bluetooth has a "blind spot". The headset works fine when my phone is in a bookbag or coat pocket or sitting on my desk across the room, but it fails in my pocket. I guess it'll keep me in a good habit of actually bringing my notes to class
[RESOLVED] Hardware issue, please see this post for repair instructions: http://forum.xda-developers.com/showthread.php?p=29615619#post29615619
Setup: Hellfire ICS v1.9, and flashed the newest Harsh non-OC kernel on record as of yesterday. Baseband is 21y, RIL matches BB (it's built into Hellfire ICS). Used GetRIL to verify.
Problem: All is perfect except for in-call audio (keep reading....), but takes a bit to surface. 5-10 minutes into a call the audio clicks and drops but comes back, missing a few words of conversation. This may happen 1-5 times a minute. Then it will eventually cut the audio and not come back but leave the call in progress. If I call the person back, the process happens but much quicker next time, within the first minute of the call.
I'm hoping someone would be willing to try the same setup on their G2x to see if this is just a gremlin in my phone, or if the Harsh kernel is doing something odd with Hellfire ICS. I've looked over several of the baseband issue chains we have here but I'm not finding any additional gems that can explain why this is still happening with the matching BB/RIL. (Hoping I missed something simple) I may just have to abandon this mix of ROM-kernel.
If anyone knows how to read the logcat files to figure this out as well it would be nice (there is alot of junk in them on these ICS builds). I was thinking of making a call with it connected to ADB. But it would be nice to see if another user has the same issue on this config.
Major step forward after last night. Logs said the phone was flipping into headset made and enabling the headset jack. I know this may seem odd but I have never used my headphones on my phone in the last 7 months I have owned it so headset mode never crossed my mind. Which leaves me with the final problem.
Why the heck is my device stuck in headset mode after never before using it? I have tried blowing the jack out, and inserting a pair of headphones into the jack about 50 times now. I can only hear audio with the headphones plugged in. Crazy thing, the Hellfire boot sound works, just no sound after the ROM is loaded.
Off to do more searching/research...please let me know if anyone has any ideas.
First, my apologies if this has been covered elsewhere but I don't read every post and XDA gets so much traffic that searching cold usually doesn't work well (and hasn't) for issues like these.
A bit of background.
I've used CM10.2, and loads of CM 11 nightlies and snapshots and have had the following issues on my One S
1) CM 10.2 crash happy. yes, I did do a factory reset and clean install. A couple of times just to make sure the problem wasn't me.
2) Went to CM11 and have the following issues consistently
1) Bluetooth crackle. usually after a fresh install things sound fine. After a few hours or a day the audio will start to crackle, almost like all the highs are clipping.
2) Bluetooth range. Much like the last one things start off ok but when the crackle appears, the range also drops to nothing. I can have the phone in my front pocket while I'm walking and experience regular signal drops and loss.
3) Audio playback through the ear speaker doesn't work except for phone calls. Everything else only works through a headset or on the back speaker.
Most everything else works well but these items are a deal-breaker. I've tried several CM11 based ROMs and Carbon and had the same problems.
Am I doomed to go back to stock? In the end I need something that works but also can get the latest security updates and Tmo has dropped this phone like a hot potato.
Try Viper.
Well, my initial attempt resulted in a phone that only boots to recovery.
Going to try to temporarily go back to CM since I need a working phone this afternoon
Okay so I was on the M8 for about a year being a crack flasher and never having my phone set up quite the way I like it. I then switched to this phone and am loving it except the bluetooth. When I got it, I updated to 05Q before trying to connect to my car's bluetooth. I then had a lot of problems with bluetooth connecting, It would take forever to auto connect, music would skip and my phone would randomly disconnect. I did some reading and discovered it may be an issue with the update so I used the tool kit to downgrade to 44S. While less often, the issues are still very much present. I've been tempted to try CM12 but need something relatively stable. That being said, the 11s doesn't seem to be very stable itself, and I'm curious is bluetooth is better in the cm12 nightlies. I've done some research and I see references here to issues and then fixes and I'm not sure where things have landed at this point. Looking for some input on whether things would improve if I switched to the nightlies. Forgot to mention on my M8 bluetooth in my car worked flawlessly.