Hi!
I have problems getting my Creative WP-350 headset to connect properly. I went away from Sense some time ago due to different problems and started using CyanogenMod. I was on 4.2 and it was good in general. Used it for a long time and now I decided to try something fresh. So i tried Venoms Sense 5.5 3.1.2 version and its a beauty. But due to random boots I dropped it and went for version 2.x. Bluetooth pairs but fails to give me "the second beep" while connecting. Resulting in the sound being sent to the phone speaker. Now i ditched it and went back to CM, but on 10.2 running android 4.3. Still the same bt problem. No second beep.
Anyone else having this issue across different roms and are there any tricks I can pull on it?
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...
[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.
I've been scouring this site for similar problems, I found one thread that sounded similar but no one responded to it...
I've been running CM10 and CM10.1 on my phone since I've had it, a little over a year. Last weekend I updated to the newest nightly with the CM updater like I always have. As far as I could tell, everything worked normally.
That afternoon, the phone rebooted a few times on its own after it froze up. It slowly got worse, and now its to the point where it will not stay running for longer than about 2-3 minutes on any CM10 based rom. Additionally, on boot up, when it gets to the home screen, the message, "no sim card detected" shows up for a few seconds until 4g connects. Then, when I unlock the screen it takes me to the activation screen which seems to go nowhere. If I press the home button, it will take me back to the home screen and the phone will work like it should until it reboots.
On Monday, reinstalled the stock touchwiz rom and that seemed to make everything better. I haven't noticed any random reboots or the sim card message thing. So today, I tried CM10.1 again. Same issues. I also tried Carbon and PacMam - both resulted in the same issues.
So....I seem to have a functioning phone on touchwiz, which is good...but I really don't like touchwiz. I'd really like to be running carbon, but a hard reboot every 3 minutes is unacceptable. Obviously, this can't be a software thing - everything was fine until a week ago. Could a dying SIM card cause this?
Same thing here,,,, I can not install any 422 rom... and I notice it will not see my Ext-SD card.
Ive been getting that same activation issues as well, are you rebooting the phone in an area with poor reception?
Some 4.2.2 ROMs do not seem to have this issue, ParanoidAndroid, and ParanoidKANGDroid are two i can think of.
eyerawnick said:
Ive been getting that same activation issues as well, are you rebooting the phone in an area with poor reception?
Some 4.2.2 ROMs do not seem to have this issue, ParanoidAndroid, and ParanoidKANGDroid are two i can think of.
Click to expand...
Click to collapse
Yeah, signal is strong. Something like -89dB. I'll try paranoid android this afternoon.
Try liquidsmooth ... I had many reboot issues with carbon and a few other roms but none when it comes to liquidsmooth (recommend 4-16 nightly) and ktoonz 4-11 kernel ... perfect match ... if issues continue there im out of options good luck
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.