Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Alan_Hill said:
Dear xda friends,
I've been trying few AOSP rom on my N9005 always have the noise and crackling sound problem.
I tried to search but couldn't find solution to fix that.
Click to expand...
Click to collapse
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
jakhan86 said:
I have n-900. I had the same crackling sound problem coming from the bottom of my phone. I gave it to Samsung Agency they changed the speaker first. Same problem persisted after a few days.
So i gave the phone again and asked for a replacement. Thankfully, they changed the chipset. Now its fine. *Touchwood*
Click to expand...
Click to collapse
But mine work with Samsung based rom without any issue like this one .
You tried a few AOSP roms, well ain't that cute.
But not once did you read the first posts or a few last posts of the rom thread. If you would, I'm sure you'd found at least a hint on this bug.
And do learn how to Google search !
Sent from my N9005
Had the same problem too, this issue is for all AOSP roms as I see .. but after some restart and charges he go away .. No worries to have man
Same problem. Been having it ever since I installed cm12.1. Most sounds work like they should, but certain apps only crackle. Like, my gf got a vanilla note3,and we both have the game "just get 10". To her, the sound is as it should be. To me it's horrible.
I've been using it ever since the unofficial ports, and been updating nightlies ever since. The problem still persist. If this could be fixed, it would be amazing!
I've also tried the equalizer ports of dsp mamager and audiofx, but no changes whatever I do.
Headphones, and Bluetooth headset works fine.
I too have experienced that allot. And have noticed that it occurs mostly when you use different sound drivers. Like if even on TW you flash beats audio mod or maxx audio you can hear the same crackling.
I suggest you use temasek rom. Its a solid and very stable one.
Hey thanks man, I'll do that
Edit, I've done did it and now everything works flawlessly. It's also a great rom, good battery. Thanks man.
This problem exists in all AOSP based ROMs and after some research I found the solution:
Go to settings -> apps manager -> select google app -> permissions -> disable the microphone permission.
Done
Worked on Galaxy S7 Edge
Related
Sometimes when I plug my earphones in, the music player shows it as playing, but there's no sound in the earphones. When i remove them, it works fine through the speakers. Tried using different earphones, but same result. Have to restart the phone to be able to use the earphones again.
I have been experiencing this problem since 3 days now.
Has anybody else experienced similar problems? Any solution?
I'm using stock Gingerbread on Moto Defy+.
Please ask all questions in Q&A. Thread moved there.
At first, I see only 2 options, despite trying another ROM:
1 - Try other music players.
2 - Be sure that you haven't changed any option in any Voice Search / Dialer. And if you have changed, try to reset to default options.
Lorenard said:
At first, I see only 2 options, despite trying another ROM:
1 - Try other music players.
2 - Be sure that you haven't changed any option in any Voice Search / Dialer. And if you have changed, try to reset to default options.
Click to expand...
Click to collapse
I have tried other players also. Same result.
And i haven't changed any such option recently.
neo.dcm said:
I have tried other players also. Same result.
And i haven't changed any such option recently.
Click to expand...
Click to collapse
Hmn... in tha case, there's still a lot of things to do.
If the problem is with the phone's jack, you can try to clean it with a blow or compressed air.
There's a bunch of apps, like Ringo Pro, that are known to cause some similar issues, as reported in this thread: https://forums.motorola.com/posts/6f261e8427?commentId=564506#564506
After all, if you'r not willing to root and flash other roms in your phone, you might also try bluetooth earphones.
Lorenard said:
Hmn... in tha case, there's still a lot of things to do.
If the problem is with the phone's jack, you can try to clean it with a blow or compressed air.
There's a bunch of apps, like Ringo Pro, that are known to cause some similar issues, as reported in this thread:
After all, if you'r not willing to root and flash other roms in your phone, you might also try bluetooth earphones.
Click to expand...
Click to collapse
If dust etc were the problem, it wouldnt have worked after restart.
I went through the forum in the link. I havent installed any such app recently. The post might be useful for future though, thanks for that.
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
I have you seen s you. Have you found a solution yet? When I use a bluetooth headset it works Fine
You need to update your radio
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I was having this issue as well, and that worked perfectly! Thanks man!
*system error* said:
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I tried that and that app and messed with different settings and it didn't work. I'm gonna try updating the radio and see what that does.
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
That worked actually. Thanks!
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
Huge thanks for this one. I had been searching google for a solution to this one for a week or so now. I will have to say, the most annoying thing I've had to deal with in quite some time. I should have just come to XDA first like an adult.
T-mobile s4
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Try the T-Mobile S4 Forum
ptsite said:
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Click to expand...
Click to collapse
Sorry, but I don't know if this applies to the Samsung S4. I would try posting over in the T-Mobile Galaxy S4 forum.
Hello all,
I have a question and if some one can help me i would be very grateful
I have the Samsung Note 3 SM-N9005, and i am using the Cyanogenmod 11 on it, but i am experiencing some sound statics that are very annoying in general. Basically when the phone uses the speakers the sound in most of the cases is awful with static distortion.
Does any one has any solution to this, or ideas how to fix it ? i tried the latest nightly builds (till 01.05.2014) and nothing helped even if in those builds it was written that they have fixed the sound static distortion.
Thanks allot for any help given!
tixoo said:
Hello all,
I have a question and if some one can help me i would be very grateful
I have the Samsung Note 3 SM-N9005, and i am using the Cyanogenmod 11 on it, but i am experiencing some sound statics that are very annoying in general. Basically when the phone uses the speakers the sound in most of the cases is awful with static distortion.
Does any one has any solution to this, or ideas how to fix it ? i tried the latest nightly builds (till 01.05.2014) and nothing helped even if in those builds it was written that they have fixed the sound static distortion.
Thanks allot for any help given!
Click to expand...
Click to collapse
I have tried many versions of cm11 and have always experienced this problem with the sound.. i think we will just have to wait for a fix
Sent from my SM-N9005
celderic said:
I have tried many versions of cm11 and have always experienced this problem with the sound.. i think we will just have to wait for a fix
Sent from my SM-N9005
Click to expand...
Click to collapse
Dang, i was hoping for a solution ... dony really want to go back to TW honestly, but this ia killing me from inside.
Do you think that a stable update will fix it only or a nightly can do the trick to?
Dang
It's like that in cm roms since 1800.
Try turning off all system sounds, sometimes it helps.
Sent from my N9005
tixoo said:
Dang, i was hoping for a solution ... dony really want to go back to TW honestly, but this ia killing me from inside.
Do you think that a stable update will fix it only or a nightly can do the trick to?
Dang
Click to expand...
Click to collapse
Well in this cas how should my phone ring if i have them all off?)
System sounds...
Unlock sound, keyboard sound, dialpad sound, screen touch sound,...
Sent from my N9005
Dejan Sathanas said:
System sounds...
Unlock sound, keyboard sound, dialpad sound, screen touch sound,...
Sent from my N9005
Click to expand...
Click to collapse
Will try, will see what happens
It works, for now at least, but it works!
I dont see what those sounds have to do with the speakers in general but ... bugs are bugs i guess.
Any ideas of when they will fix this? I actualy love these sounds
Ps: you can leave the click sounds, the problem is with the lock/unlick sound(at least for now i did not have problems, but will continue testing)
Don't ask me, because i don't know why, but it's like that and that's the way it is.
As i told you, this is a bug since forever. Don't think a proper fix is coming soon.
Sent from my N9005
Dejan Sathanas said:
Don't ask me, because i don't know why, but it's like that and that's the way it is.
As i told you, this is a bug since forever. Don't think a proper fix is coming soon.
Sent from my N9005
Click to expand...
Click to collapse
Ah well, at least its better now, thank you for the help, one more bug to fix and the rom is good to work as a daily driver
Cyanogenmod 11 sound fault temporary solution??
An alternative temporary solution is to download an equalizer app. Drop all the controls down to zero and then bring them back up one by one. I had a sound issue with just one app on my Samsung galaxy ace II so this might work on your note 3. Ran the equalizer, ran the app, no more screeching or buzzing. When equalizer off, app on its own reproduces sound problems. Several equalizer apps I tried seemed to do the trick. DSP allows you to disable and enable when required. This is my first post and as a noobie I read the terms and conditions first; but I apologize if I have still not followed protocol. Hope this is still relevant.
I had that issue too. Not really sure if it has a permanent fix; it kinda came and went away on its own.
Anyone else experiencing this issue? When I'm listening to music and I get sound notification from whatsapp for example, it becomes distorted for a good five seconds atleast (the music and the notification) and maybe even longer sometimes. I'm using the latest nightly and still experiencing this issue
Flash Temasek's unofficial CM build. He builds from official CM sources and then adds some useful features. A lot of problems in regular CM are fixed in his builds, including broken sound.
Whenever I play music on my Note 3 SM-N9005, it's fine at the beginning but if I touch any options or click on anything, it starts making a crackling noise. I'm currently running CM13 Android 6, rooted with Xposed framework. Earlier, I had installed CM14 on my phone and used it a bit, but I didn't like it although I had no issues with the crackling noises at all, I wiped it and reinstalled CM13 and then suddenly the crackling noise showed up again. So I've eliminated the possibility of it being a hardware problem, but now I have absolutely no idea how to fix it.
Thanks in advance
Rom thread, xda, google,... Search. It's been mentioned like 6 million times.
Dejan Sathanas said:
Rom thread, xda, google,... Search. It's been mentioned like 6 million times.
Click to expand...
Click to collapse
I did, I couldn't find anything helpful
rithvikp said:
I did, I couldn't find anything helpful
Click to expand...
Click to collapse
In that case use another rom/ stock.
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.
Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.
piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.
Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )
Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.
supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!