every android rom i install on my tilt has a problem right after i reset the phone i can hear and talk to people but after a short while all sound quits working and the mic doesnt work. any help is apriciated. anyone else have this problem?
What radio are you using?
problem resolved your the best
I really hate this so bad.
When your problem is resolved, type how it was resolved.
I don't know how hard it is, but when you have a problem, someone else will have a problem, and your "problem solved' is useless.
That being said... I have the same problem, can someone help me out?
try changing your radio http://forum.xda-developers.com/showthread.php?t=393182
Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete
Dirty Pete said:
Hello all,
I have a very odd problem that I'm hoping others may have run into and solved. When I'm playing audio over the A2DP data path to my car, the audio randomly will drop for half a second, then gradually comes back to full volume over perhaps a second of time. Speaking like a programmer, it's almost like something mutes the audio and then slides the volume up in a loop or something.
This problem did not occur on Bombaridier and the older Synergy Kernel, however it is happening with the newer kernel on Juggernaut v5, Paradox and SlickMOD, leading me to believe something in the kernel or newer system binaries might be causing it. This behavior happens in Pandora, Amazon MP3 and also the stock Music app.
Thinking that maybe a stray notification was the problem, I've tried disabling notifications in all of the apps I know of that notify, I've also tried switching the phone into vibrate and finally into full-silent, but it does not seem to affect the behavior. I have found no likely cause. I wish I was able to log alsa changes; maybe a script running constantly with something like:
Code:
while (true)
do cat /proc/alsa/some_alsa_status_entry >> /tmp/alsalog
sleep 1
done
Does anyone else have any ideas as to what this might be? It's really annoying!
Thanks in advance,
Pete
Click to expand...
Click to collapse
I second this as an issue that I have run across quite often. I use this BT for music in my car on a daily basis. I usually get a .5 second audio drop out at lest twice each song. Seems to be about every 2 minutes if I would have to guess.
I have just learned to get used to it but it would be fantastic if this could be resolved.
I've also tried fiddling with the CPU governor ant the IO scheduler, but to no avail. Im wondering if there is a bug in the bluetooth module introduced in the latest kernel.
Sent from my SGH-T989 using xda premium
Works great for me and I've tried just about every rom and kernel over clocked and under clocked. I had it skip once before, I rebooted and it was fine.
Sent from my SGH-T989 using Tapatalk
I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.
scotty-dont said:
I'll give this a bump, because I have the exact same problem. Never had this problem on my Blackberry (sad), in the same car. OP has described the issue better than I could have.
Click to expand...
Click to collapse
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete
I've tried black edition and warfare, never had any issues
tomasitoc said:
I've tried black edition and warfare, never had any issues
Click to expand...
Click to collapse
What version of the kernel on your warfare mod? SlickMOD uses the Darkside 2.6.35.14 kernel.
Dirty Pete said:
Thanks for posting, out of curiosity, what ROM and kernel are you running? Maybe we can find some sort of similarities...
My phone's currently running SlickMOD 3.1 with kernel "2.6.35.14"
-Pete
Click to expand...
Click to collapse
Hi Pete,
I've noticed it on Digital Warfare 2.5.1 and BeastMOD 5.0 ("Test 13"), using TDJ's personal kernel and the same 2.6.35.14 above, respectively.
I'll post to Melvin on rootzwiki in the hopes that he can investigate maybe.
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.
scotty-dont said:
It might be better to bring this up in other sections as well. I came across this post by accident while researching extended batteries.
Click to expand...
Click to collapse
I originally posted it in a different forum, but a moderator kicked it over here. It's not really an accessories question as I'm pretty sure it's a kernel bug, but I wasn't about to argue with site moderators on a forum like this where I'm definitely the new kid on the block.
That being said, if you have some other suggestions as to where we can ask about this, I'm all ears and would be more than willing to help debug/diagnose. I've been a Linux user since '96, so I'm unafraid of poking around in the kernel's guts to get answers.
Pete
Yeah that's the problem with this place... and why I have less than 10 posts.
On second thought, I'm tempted to just wait. It sounds like we will have a proper ICS rom and true kernel on about April 25th, to coincide with the launch of the HTC One S on T-Mobile. I can't find the threads. Hopefully then it will be an issue of the past.
I'm glad I'm not the only one though.
Just a thought....I don’t think this has anything to do with CPU performance
Hi, I have a Galaxy 2s with this exact problem but I wonder if I might offer a suggestion as to what could potentially be the cause. I have no idea how to fix it but I’m hoping that what I share here might help someone who knows more about the way these things work to be able to solve the problem.
I have spent much of my career working in Broadcast Radio, the problem I have heard my phone have with audio dropouts followed by either a ramp up of volume back to the previous level OR an audio dropouts followed by a momentary slight speed shift in the audio playback (sounds a bit like an old cassette recorded when the batteries are starting to fail) many people would probably not notice the later problem because it is very subtle and you have to know what you’re listening for.
Anyway, I believe this could be caused because of a lack of word clock sync between the phone and the bluetooth receiver. I say this because there have been times when I have had digital audio devices such as CD players that are connected to an audio console or digital amplifier and with both devices free running in terms of their clock synchronisation exhibit almost exactly the same symptoms.
You see all digital audio devices require that the audio data be put into frames much the same as regular Ethernet data is transmitted around a network is put into frames, however in order for the audio to be at the correct pitch and speed generally speaking both the playback device (Phone) and the receiving device (Bluetooth receiver) need to have the same word clock, otherwise you end up with the two devices running freely and the audio frames wont by in sync.
Depending on the Error correction implemented (sample rate conversion) on the receiver you can get really odd audio results. I think that this is what is causing this problem. Basically the Bluetooth receiver and the phone aren’t in sync so every few minutes you get a drop out.
It doesn’t seem to happen when you are talking on the phone which makes me think that when you have a call connection as this is bi-directional, the phone is probably synchronised to the Bluetooth device word clock. But when you are listing to music the connection is mono-directional so there is no sync.
Anyway just a thought. Maybe someone out there who understands the way these units synchronise can figure out a fix.
Mine has random just disconnects from the phone altogether. I have Jawbone Era, Voyager Pro Plus, and a Jabra Wave + and all will just randomly disconnect and have a hard time connecting back to phone audio. It will reconnect to media pretty much first time but won't show coonected to phone audio for some reason unleass I turn off BT, turn off headset, and sometimes even re-boot phone.
I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.
I had this issue when I tried out juggernaut, so I went right back to Bombardier with Synergy kernel. Anyone have this on any if the ICS roms?
Sent from my beastly Galaxy S 2.
Shane_pcs said:
I am sure you guys have ruled this out, but this was a common problem with bluetooth audio on android. I haven't had the problem for a long time, but I used to have to disable wifi during my commute due to this dropout. Can you turn off wifi and see if the issue still happens? I was able to identify it by changing the time between wifi scan. If you had custom rom settings you could push it out and sure enough, my bluetooth dropouts happened on the same schedule (2s, 10s, more)
Just a thought.
Click to expand...
Click to collapse
I disable my wifi while I'm in the car, so this wasn't my issue. Thanks for the suggestion though!
I used to have occasional a2dp problems, however I have not had them since I started using various ICS releasese. The problems I would occasionally have would be a total loss of bluetooth till I rebooted the phone.
Since using Infamous I haven't had the problem other then for some odd reason occasionally having to reenter the PIN #
I'm using a Scoche Bluefusion in my car.
It had to be the fuse.
Sent from my SGH-T959 using xda premium
After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.
Dirty Pete said:
After upgrading to DARKSIDE's latest ICS rom, this problem has not recurred. I'm assuming that my early thought was correct in that it was some kind of kernel bug.
Click to expand...
Click to collapse
With Darkside and the stock ROM I have not only this problem, but crackly/staticy audio and my phone and car won't communicate once I've shut the car off. I have to completely re-pair the phone. They're bugs in 4.0.3, which Samsung dumped off on us.
4.0.4 via CM9 already doesn't exhibit the connection issue (I have to turn Bluetooth on and then off though) but I'm not sure about the others yet.
This is a very strange issue, and I hope someone can help!
I'm running the HTC One-X with the Viper-X rom. It's awesome, except I have one slight issue.
When people ring me, there's a 50% chance that my phone won't actually ring. Alternatively, even when it does ring, it's VERY quiet. Finally, if I have headphones in (which is about 90% of my day due to work), I again have like a 40-50% chance to hear it ring - other times my music will play happily while the phone 'vibrates' in my pocket and lights up, which I don't always notice.
Has anyone else encountered this? Anyone got any ideas what I can try to prevent this? It makes the phone largely unusable as a phone, since I'm not getting the right indicators that it's ringing!
Your in the wrong forum. You have an international hox.
Sent from my Nocturnalized Beast
Moved to correct forum
the_scotsman said:
Moved to correct forum
Click to expand...
Click to collapse
Thanks for moving, not sure how I ended up in the wrong one!
I don't even know how to begin to troubleshoot this because it happens once in a blue moon, but when it does happen, it is annoying as hell. Every now and then, when I connect my phone through the auxiliary port to play music, there will be a phantom ring that persists even as the music is being played. It's kind of a quiet ring.
Disconnecting and reconnecting the auxiliary cable does not fix the issue. The only way I can make this go away is by rebooting my phone. What in the world is this and has anyone else ever encountered this? I'm losing my mind thinking maybe the ringing is in my head, but others who have been in my car when this happened can confirm that I'm not a lunatic.
raphytaffy said:
I don't even know how to begin to troubleshoot this because it happens once in a blue moon, but when it does happen, it is annoying as hell. Every now and then, when I connect my phone through the auxiliary port to play music, there will be a phantom ring that persists even as the music is being played. It's kind of a quiet ring.
Disconnecting and reconnecting the auxiliary cable does not fix the issue. The only way I can make this go away is by rebooting my phone. What in the world is this and has anyone else ever encountered this? I'm losing my mind thinking maybe the ringing is in my head, but others who have been in my car when this happened can confirm that I'm not a lunatic.
Click to expand...
Click to collapse
I read something about this. Some say the .10 update fixed the issue, and as a work a round placing a call resolves it or a reboot WITHOUT fastboot checked. At work atm and cant look up the references for that sorry, just what i remember.
I nvr had it on mine yet and it seems to happen when switching in/out of 4g/3g modes as well.
I've had this happen only once. Only it was over bluetooth while streaming audio to my car stereo. Had to reboot to get it to stop. WIERD!
carm01 said:
I read something about this. Some say the .10 update fixed the issue, and as a work a round placing a call resolves it or a reboot WITHOUT fastboot checked. At work atm and cant look up the references for that sorry, just what i remember.
I nvr had it on mine yet and it seems to happen when switching in/out of 4g/3g modes as well.
Click to expand...
Click to collapse
i had it happen on my dna! but it only happened when i was out of signal, barely into 3g! it stopped when i put it in airplane mode and a reboot!
Well I'm glad it's not just me who has experienced this, but is there any way to completely resolve the bug? It's pretty annoying when it happens and even more annoying that it's difficult to replicate.
raphytaffy said:
Well I'm glad it's not just me who has experienced this, but is there any way to completely resolve the bug? It's pretty annoying when it happens and even more annoying that it's difficult to replicate.
Click to expand...
Click to collapse
Are you on the latest software and if so can you try airplane mode when this occurs ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
Are you on the latest software and if so can you try airplane mode when this occurs ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
From what i seen on the VZW forums the only way to kill the sound is a re-boot or make a call of some kind.
has anyone been able to find the solution to the problem of knock on double tap ?? since i upgrade from the kit kat I could not find a way to make my phone back to have that feature, someone else would still happening? has anyone been able to find the solution to this problem? and I have another problem. from that time I stopped working that feature, I have a problem with a certain part of the screen at the top does not detect touch, know someone that is? someone else will happen? or is it just me? .... please if anyone has a solution to these problems, I ask you to help me. thank you very much.
the problem with my screen
fanocampo2293 said:
has anyone been able to find the solution to the problem of knock on double tap ?? since i upgrade from the kit kat I could not find a way to make my phone back to have that feature, someone else would still happening? has anyone been able to find the solution to this problem? and I have another problem. from that time I stopped working that feature, I have a problem with a certain part of the screen at the top does not detect touch, know someone that is? someone else will happen? or is it just me? .... please if anyone has a solution to these problems, I ask you to help me. thank you very much.
Click to expand...
Click to collapse
thats the part of my screen not work the touch
Looks like a bad screen. Especially missing that whole section. If it was a corner or something, I would think something like a drop. But straight across, that's not good.
Sent from my LG-LS980 using Tapatalk