I'm trying to listen to music over Bluetooth on my Jawbone era headset and everything seems like someone is playing the music faster than normal. Any ideas what is causing it?
Sent from my Nexus 4 using xda premium
tkgod said:
I'm trying to listen to music over Bluetooth on my Jawbone era headset and everything seems like someone is playing the music faster than normal. Any ideas what is causing it?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I don't know what causes it but I simply disconnect my Bluetooth headset and reconnect. I do it as much time as possible until it doesn't happen again. It doesn't happen very often so that's good. Also you can try to unregister it from the phone and re-register the headset again. Maybe its a Bluetooth bug or something. It happens on my iPhone 4 as well.
Sent from my Nexus 4 using Tapatalk 2
Got it fixed. I think it was a kernel issue or something I added to the Rom.
Sent from my Nexus 4 using xda premium
Hi guys...
Start using S4, and I noticed this little bug?
When i paired with the radio in the car, i need always to select Media Audio.
If I turn on them off, Media Audio, is not select.... it's a little boring, always need to go to settings..
Any one is having the same issue?
I'm using the last stock UK ROM.
This didn't happen with S3...
Thx
Sent from my S4 Tapatalk 2
Yes and it's dead annoying because everytime I turn my engine on I have to turn s4 BT off then back on and select stereo.
Sent from my GT-I9505 using XDA Premium HD app
Same here. Although sometimes I notice I has connected media aswell .
Sent from my GT-I9505 using xda premium
I have +- resolved the problem
Play store, and install this app
Bluetooth Auto Connect....
simple and it works.
Sent from,my GT-I9505 using Tapatalk 2
Hello,
I really tried to find an answer to my question but I couldn't. There is a thread in the Galaxy S3 forum but as I have a N4 and suggestions in the said thread did not help I'm trying here again.
As BBS tells me, Audioout_2 is causing a lot of wakelocks on my N4. In 10 hours of use, it caused 704 wakelocks (more than 50 minutes). I guess it is a lot since the next on the BBS list is Kakao talk with 9 minutes (280 times). The sound was turned off the whole time (vibrate only). And I don't have Viber installed (some people supposed that Viber caused the Audioout_2 wakelocks). I also turned off Google tts which was supposed to cause the problem too.
Does anyone know what Audioout_2 is and how to decrease the number and time of wakelocks?
Thank you very much in advance.
Edit: Running latest PA on latest franco kernel + some grammar corrections
Really? Am I the only one having this problem with a N4.
Sent from my Nexus 4 using xda app-developers app
I've read in a thread that the problem could be the touch sounds, try to deactivate them (touch sound, screen lock sound and keytones) and see if it desappears! (Reboot the phone after disabling those sound, in order to be sure)
Sent from my Nexus 4 using xda app-developers app
TheUnreaL said:
I've read in a thread that the problem could be the touch sounds, try to deactivate them (touch sound, screen lock sound and keytones) and see if it desappears! (Reboot the phone after disabling those sound, in order to be sure)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem. I've disabled touchsounds etc. a long time ago, so that's not the problem.
Really don't know what to do about those wakelocks...
Janne79 said:
Really? Am I the only one having this problem with a N4.
Click to expand...
Click to collapse
You'll need to wait longer than 3 hours before coming to that sort of conclusion.
Sent from my Nexus 4
TheUnreaL said:
I've read in a thread that the problem could be the touch sounds, try to deactivate them (touch sound, screen lock sound and keytones) and see if it desappears! (Reboot the phone after disabling those sound, in order to be sure)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the answer but that's definitely not the problem as I never ever used touch-, screenlock- or keysounds.
steviewevie said:
You'll need to wait longer than 3 hours before coming to that sort of conclusion.
Sent from my Nexus 4
Click to expand...
Click to collapse
Sorry, you're right, seems a bit impatient by me. But, it was 3 hours and 6 minutes No seriously, I'm sorry.
Sent from my Nexus 4 using xda app-developers app
Audio_2, so descriptive...
I have had the same problem with this strange wakelock on my N4 with stock google + franco kernel.
I am not sure when exactly it started to appear, so lets find some commonalities:
Do you have Calendar Snooze ( cannot post links yet ) installed ?
Andrey
PS (installed CyanogenMod without franco kernel 6 hours ago, lets see if it will reappear)
andrey.tch said:
Do you have Calendar Snooze ( cannot post links yet ) installed ?
Andrey
Click to expand...
Click to collapse
Nope. But latest "rumor" I heard is that the haptic feedback causes the wakelock too. Turning off sounds is not enough. So I'll try to turn off haptic feedback after next charging too (even though I will miss it)
Sent from my Nexus 4 using xda app-developers app
I'm pretty sure audioout_2 comes up when you are listening to music or watching a video. I've been listening to music on spotify and I get that wakelock normally.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
I'm pretty sure audioout_2 comes up when you are listening to music or watching a video. I've been listening to music on spotify and I get that wakelock normally.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I don't here any music on my phone. Maybe listening to music causes those wakelocks but there must be something else causing it too.
Sent from my Nexus 4 using xda app-developers app
Janne79 said:
Nope. But latest "rumor" I heard is that the haptic feedback causes the wakelock too. Turning off sounds is not enough. So I'll try to turn off haptic feedback after next charging too (even though I will miss it)
Click to expand...
Click to collapse
I did not have haptic feedback, which pretty much rules it out for me. I did use music player though (3rd party, not internal one) over bluetooth. But somehow it was appearing when I did not listen to the music too, just drove and phone (wow... feels weird to call it like that) was connected to in-car bt audio
Seems to be haptic feedback. After I turned it off the wakelocks from Audioout_2 almost stayed the same (2 min in 2 hours)
Sent from my Nexus 4 using xda app-developers app
Janne79 said:
Seems to be haptic feedback. After I turned it off the wakelocks from Audioout_2 almost stayed the same (2 min in 2 hours)
Click to expand...
Click to collapse
I am glad you have it solved for yourself. I will try to keep an eye on haptic thingy too.
Just a little update: Phone is unplugged for 3 hours now, haptic feedback off, wakelocks caused by Audioout_2 are down to 8 seconds (12 wakelocks). That's a huge improvement.
Sent from my Nexus 4 using xda app-developers app
Last update: 9hrs, 2 min with 63 wakelocks. I guess that's it, problem solved. I'm surprised how fast I got used to not using haptic feedback.
Sent from my Nexus 4 using xda app-developers app
Janne79 said:
Last update: 9hrs, 2 min with 63 wakelocks. I guess that's it, problem solved. I'm surprised how fast I got used to not using haptic feedback.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I hate haptic feedback. it's annoying and a waste of power. Grrr.
Sent from my Nexus 4 using Tapatalk 2
I love haptic feedback but it's a battery drainer indeed.
Sent from my Nexus 4 using xda app-developers app
Janne79 said:
I love haptic feedback but it's a battery drainer indeed.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'm glad you solved the problem. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Strange I've been running all day (5hrs) with haptic on and I've only got 12 seconds (count 13) worth of wakelocks from audioout_2...
Sent from my Nexus 4 using Tapatalk 2
rysup said:
Strange I've been running all day (5hrs) with haptic on and I've only got 12 seconds (count 13) worth of wakelocks from audioout_2...
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The whole Audioout_2 thing is strange. Some people solved the wakelock problem by uninstalling Viber, some by turning off system sounds only and in my case it obviously was the haptic feedback. I don't get it too but it solved my problem.
Sent from my Nexus 4 using xda app-developers app
I'm on 10.2-20131122, CWM recovery, and whatever kernel came with this version. I have tried other builds. I tried a few 10.1 builds also all with the same issue. I have wired headphones with mic that worked fine on stock and works on my girlfriend's HTC one running CM 10.2. The button still works to skip songs and activate Google now, but when it comes time to talk it doesn't pick up anything through the mic. Any ideas? TIA
So nobody else is experiencing this?
Sent from my Nexus 4 using XDA Premium 4 mobile app
More of the same on the latest stable release.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Uncle Lizard said:
I'm on 10.2-20131122, CWM recovery, and whatever kernel came with this version. I have tried other builds. I tried a few 10.1 builds also all with the same issue. I have wired headphones with mic that worked fine on stock and works on my girlfriend's HTC one running CM 10.2. The button still works to skip songs and activate Google now, but when it comes time to talk it doesn't pick up anything through the mic. Any ideas? TIA
Click to expand...
Click to collapse
I have just flashed the cm 10.2 stable version on my HTC oneX yestoday,and have the same problem with you.Would you pls let me know when you fix it?
[email protected]
I just read this a minute ago. It could have something to do with it.
http://www.androidpolice.com/2013/1...sound-levels-on-headset-mics-fix-coming-soon/
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hey guys im in a big problem here, after few days of updating to kitkat, My dads mobile is having sound issues.
Its not working while:
-listening to any audio/video by speaker.
-Alarms.
-Hangouts video call.
but its working while:
- listening music by headphones
-If the phone rings.
As i said its my dad's phone so it isnt rooted or anything..completely stock. Please suggest me some good solutions here.
THanks.
Please any help would be appreciated..
Sent from my Nexus 4 using xda app-developers app
I wish I could help but mine is doing the same thing. I'm on CM11 nightly though so I thought it might be that.
Any help out there?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Have you guys tried a full wipe with a factory reset? Also testing the device before bringing back any apps you have backed up? Sometimes you do a full wipe only to bring the problem back with a backup.
Sent from my Nexus 4 using XDA Premium 4 mobile app
My phone is having the same issue. I've rooted and installed many different ROMs. The last one I tried called Beanstalk installed with all the sound working properly but on the first reboot, the problem came back. I tried wiping an re-installing but the problem is still there, so it seems to be the luck of the draw. There is an app called Soundabout which you can install to route the sound to the speakers, but you would then have to go into the app to route the sound back to the headphones when you need. Very strange. I've seen many posts on different boards of people with the same issue but no true fix. I need to find a good android developer who knows the code well that could probably figure this out...but who that man could be I just don't know...
Are you still facing the problem?