Hello there, I have this problem on my samsung galaxy s4 i9505 LineageOs 14.1
I can´t send voice notes on whatsapp and also makes calls. It´s like the mic its "mute". The only thing i can do its recording videos and make and recive calls only in speaker mode, thats the only way to make the mic works.
I tried everything: Cleaning, wiping, full wipe, changing roms, editing the "build.prop" and nothing.
I searched in the forum for this trouble, and no one can solve this.
help, please.
aguu352 said:
Hello there, I have this problem on my samsung galaxy s4 i9505 LineageOs 14.1
I can´t send voice notes on whatsapp and also makes calls. It´s like the mic its "mute". The only thing i can do its recording videos and make and recive calls only in speaker mode, thats the only way to make the mic works.
I tried everything: Cleaning, wiping, full wipe, changing roms, editing the "build.prop" and nothing.
I searched in the forum for this trouble, and no one can solve this.
help, please.
Click to expand...
Click to collapse
The WhatsApp low sound when recording is a bug in all LineageOS 14.1 roms, the only way to fix it is waiting or reverting back to cm13.
its a hardware problem, need to replace the power conector board.
MigoMujahid said:
The WhatsApp low sound when recording is a bug in all LineageOS 14.1 roms, the only way to fix it is waiting or reverting back to cm13.
Click to expand...
Click to collapse
I just tried lineage os 13, and it also had the low volume problem when recording. Do you any any aosp based rom that doesn't have this problem?
trasabdcf said:
I just tried lineage os 13, and it also had the low volume problem when recording. Do you any any aosp based rom that doesn't have this problem?
Click to expand...
Click to collapse
If that so, then you will have to try the stock rom first, if that bug is there also, then I'm afraid @Leozaors might be right and it's a hardware issue.
MigoMujahid said:
If that so, then you will have to try the stock rom first, if that bug is there also, then I'm afraid @Leozaors might be right and it's a hardware issue.
Click to expand...
Click to collapse
I am using stock right now and the sound recording works just fine, well, it worked fine before. This being a hardware problem, could that be caused by flashing a custom rom?
What did you edit in build.prop?
forfriends said:
What did you edit in build.prop?
Click to expand...
Click to collapse
If you're refering to me, I didn't even touch the thing. )
trasabdcf said:
I am using stock right now and the sound recording works just fine, well, it worked fine before. This being a hardware problem, could that be caused by flashing a custom rom?
Click to expand...
Click to collapse
If you're on stock and it's working good, then the custom rom is faulty, if it's not working on stock as well, then it's a hardware issue.
Related
i flashed AOKP on my S3 and it works perfectly. i hadn't made any calls up to that point but once i did i realized i wasnt getting any call audio. i googled and got to the thread below and flashed these files but no i am stuck in an endless bootloop.
http://forum.xda-developers.com/showpost.php?p=28159725&postcount=1
the ROM is really awesome and i dont want to go back to the previous one but unless the call audio issue is resolved i might not have a choice
HELP!!!!!
Hi,
Had same problem.
You should try to flash build 40.
There is no audio bug there.
Marvius said:
Hi,
Had same problem.
You should try to flash build 40.
There is no audio bug there.
Click to expand...
Click to collapse
thanks for the prompt response!
could you please send me a link if its not too much trouble. i erased my titanium backup files too....so i am pretty much screwed since i wont be having a backup of all my apps
sorry to hear...
https://www.dropbox.com/s/1oinzs5hjkrbdk8/aokp_i9300_build-40-(20120630).zip?m
There you go, AOKP build 40
thanks a bunch mate!
np mate
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
ilum90 said:
Hi everyone.
First of all, i apologize if there's an answer out there i'm looking but i cant find it anywhere of the hundreds of threads containing thousands of posts.
I bought a cracked Nexus 4 on ebay and i already fixed the screen by replacing a new one and everything is working now.
The phone was already rooted with Mako's Android L beta4 i believe and to be honest i didnt really liked it.
I know it is on its early stages and the official one from google is still far from the next month of its release and im in no rush to get it and experience until it gets more stabilized so i would rather use Cyanogenmod 11.
So i did a full wipe/factory reset, wipe partition cache, wipe dalvik cache and installed with a nightly CM 11 from 20140907.
Everything works perfectly and cant find anything thats causing problems except one thing.
When i make a phone call, the screen turns off as if i pressed the lock screen button which i didn't but the call is still ongoing and i have to press to unlock button to turn on the screen and unlock, and when i'm on the call at the dialer i cant hang up by pressing the red hang up button, neither pressing the numbers or anything. Nothing works, the dialer is frozed and the only way i can hang it up is by going on the home screen and going to notifications and hang it up from there.
I never encountered this problem before on cyanogenmod and i believe its not from it but from the installation of makos android L b4 itself from its kernel that its not allowing me to make the phone calls. That's just my opinion. Anyone has any idea of whats causing the problem?
Is there a solution? Do i have to do a fresh clean install from the beginning maybe like to stock and from there to cyanogenmod?
Please help me out guys, im loving the Nexus 4, came from the Galaxy S2 i9100M and i had no problem rooting it at all and its still with CM 11.
Thank you all for taking the time to read this, and any ideas are welcome.
Click to expand...
Click to collapse
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Rohit02 said:
Try flashing other roms... Stock I would recommend and then test for that issue if not good or else then flash AOSP romwith good custom kernel(ak , hellscore)
Click to expand...
Click to collapse
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
ilum90 said:
Is it possible to use hellscore kernel wit CM rom?
Sorry for the noobish questions but i havent mastered when it comes to rooting and all.
I never installed any rom besides CM.
Click to expand...
Click to collapse
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Rohit02 said:
yes hellscore has cm version too..
I would recommend you to flash aosp rom -any.
Click to expand...
Click to collapse
At first, i installed another rom like paranoid 4.45 20140729 and it didnt work, it got worse.
When i would make a call, the screen would turn off and couldnt get to back on and it does but not even for a sec so it kept remaining wit a screen off but the call was still going.
The next step i tried AOSP build 12 rom, with same kernel and it also didnt work. Same as before when i had CM 11.
I just installed CM 11 rom with hellscore b55 CM anykernel and it does the same thing.
My only next step based on your opinion is trying AOSP rom with hellscore kernel (not the CM version).
Is there anything else i can try if the aosp wit hellscore kernel doesnt work?
could you indicate me where to get the stock kit kat because i see versions of them and im not sure if their stock or not.
is it also possible to use stock with hellscore kernel?
Much appreciate for all the help you have given me so far.
Same problem with simple AOSP with hellscore b55 anykernel.
Any other ideas?
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
RolF2 said:
try this fix :
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
Click to expand...
Click to collapse
I can't believe it! After all this time, blaming on the software so hard and for the last resort I actually did dissembled my N4 to check the sensors and everything but did nothing. But dude, you solved the mystery! Everything is working perfectly now. I can't appreciate how thankful I am. Many thanks
HTML:
http://forum.xda-developers.com/galaxy-s4/i9500-orig-develop/5-0-cyanogenmod-12-beta-t2944968/
Im using this rom.
and so far I got two problems.
one of them is colour changes in instagram video recording.
another one is the abnormal voice in the skype.
when i called test echo.
the replay is just like electric blazer sound non stop.
couldnt hear anything else even I was speaking
Your first question:
- Read the OP in the thread.
About skype:
- Use the searchbar in that thread and type "skype".
That will give you all the answers to your question.
Lennyz1988 said:
Your first question:
- Read the OP in the thread.
About skype:
- Use the searchbar in that thread and type "skype".
That will give you all the answers to your question.
Click to expand...
Click to collapse
I'm sorry but I have used the searching system.
However, I think in the thread the solution of the skype's noise was not been mentioned.
I'm sorry but I have used the searching system.
However, I think in the thread the solution of the skype's noise was not been mentioned.
Is there anyone who can help me?
I did flash the rom again today.
with complete wipe( three wipes)
then I flashed the rom, gapps and the kernel.
the skype problem is still here.
I was using beanstalk rom before.
Should I flash the official rom first?
then flash the custom one?
Androidtso1 said:
Is there anyone who can help me?
I did flash the rom again today.
with complete wipe( three wipes)
then I flashed the rom, gapps and the kernel.
the skype problem is still here.
I was using beanstalk rom before.
Should I flash the official rom first?
then flash the custom one?
Click to expand...
Click to collapse
It's a bug in the rom. Nothing you can do about it.
Lennyz1988 said:
It's a bug in the rom. Nothing you can do about it.
Click to expand...
Click to collapse
Because it was not mentioned as a known issue and I think some of the user do not have this problem
Hi guys, I'm facing a bug with whatsapp, can't hear audio messages by bringing the phone to my ear, whatsapp freezes and so does my phone for a little.. I clean flashed everything and I'm on freedom OS 1.3..
Anyone? I think I'll go back to stock..
Works fine on OOS 4.5.5 for me...
In the freedom OS thread one user said that he has the same bug since build 1.0.. Maybe it's a rom problem, if someone has the same issue please let me know!
carlese said:
Hi guys, I'm facing a bug with whatsapp, can't hear audio messages by bringing the phone to my ear, whatsapp freezes and so does my phone for a little.. I clean flashed everything and I'm on freedom OS 1.3..
Click to expand...
Click to collapse
I'm experiencing the same problem with F-OS 1.3 - but this worked fine in previous versions of the ROM.
I have deep suspicions that this might have something to do with the newest release of Viper4Arise and the way it modifies the system/build.prop file.
shahishikari said:
I'm experiencing the same problem with F-OS 1.3 - but this worked fine in previous versions of the ROM.
I have deep suspicions that this might have something to do with the newest release of Viper4Arise and the way it modifies the system/build.prop file.
Click to expand...
Click to collapse
I am on stock now, without viper4arise, and no bugs.. If you want you can try without v4a on freedom os, let me know because I'm interested!
I was on stock ROM as @ Noob
Changed to Aex Extended 5.7 official because of garbage volume , now on Aex ROM bootloop ,auto reboot,Pubg ping unstable network and many more bugs told me to change it.
Finally
So I installed Crdroid ROM yesterdayIt is mind blowing but still I can't call someone on this one
:crying:(Volte is working fine)
But while calling there is no sound from speakers (both)
and even on headphone also Mic is not working so No one will hear me on the other side ...
Please Guys please give me solution for it.:cyclops:
PS: suggests some other ROMs with better stability and performance with battery life
I'm on 331,same problem
Bhone Myat Kyaw778 said:
I'm on 331,same problem
Click to expand...
Click to collapse
If volte is working and you are facing problem with calls try flashing this file. It may work.
https://forum.xda-developers.com/devdb/project/?id=27084#downloads
guys install any 9.0 ROM and get out of it! it worked for me.
My issue was started when I moved from 9.0 to 8.1, so however, every time when I used a higher ROM it fine but its impossible to come down.
but someone has reported that it didn't work for him, but I think you should try it. https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/guide-revert-custom-rom-to-stock-rom-t3808248/post77920970#post77920970
check this
good luck.
I did everything. But no use. please help me. I flashed the above zip but no use
dxsyrz said:
I did everything. But no use. please help me. I flashed the above zip but no use
Click to expand...
Click to collapse
I feel so bad about you to mate, I'm so terrified when I was #$%@ed up with the same issue and most of the developers or users has little understanding about every device, and we tend to do with our own knowledge but 90% we fail and there is none to help.
In my case, I found a guy who can do it for me, it's very expensive to return back to normal and I did, since then I don't do this experimental **** anymore, I better advice same to you.
In my very personal experience, I did not enjoy the Rooting power of wisdom than running into lots of problems. So I quit and bought One Plus 6 and will never root again.
I have reached my limits. So I hope you will find a good solution outside the XDA and stop the madness of root and use a good VPN like TOR and move on.
Good luck and I'm very sorry that I, not able to help you out.
refai said:
I feel so bad about you to mate, I'm so terrified when I was #$%@ed up with the same issue and most of the developers or users has little understanding about every device, and we tend to do with our own knowledge but 90% we fail and there is none to help.
In my case, I found a guy who can do it for me, it's very expensive to return back to normal and I did, since then I don't do this experimental **** anymore, I better advice same to you.
In my very personal experience, I did not enjoy the Rooting power of wisdom than running into lots of problems. So I quit and bought One Plus 6 and will never root again.
I have reached my limits. So I hope you will find a good solution outside the XDA and stop the madness of root and use a good VPN like TOR and move on.
Good luck and I'm very sorry that I, not able to help you out.
Click to expand...
Click to collapse
Maybe you just went faster than what you could comprehend, didn't research enough, hyper excited to try new things etc..
Yes, it's okay that you were frustrated and you won't do this again.
But, it's clearly stated that what we do here has it's ups and downs!
You just failed to understand the cost to benefit ratio for you.
Also what was prognosis for your problem that was so costly?!
Probably you should have used an older device to get your hands dirty and learn & tinker a bit!
Nothing can be done here for a hardware issue.
Though there are extremely talented and brilliant developers and some users too who gladly help and guide here.
Though in all fairness it's your opinion after going through bad experiences so I feel for you mate & on the flipside I do respect it.
Peace.
I have same problem but when flashed this dolbyplus zip my problem solve
thekrishna said:
I have same problem but when flashed this dolbyplus zip my problem solve
Click to expand...
Click to collapse
Life saver !!!! god bless you bro !!!
Bro, I used pie rom for 5 days after I flashed an Oreo rom with pico gaps.I got rid of incall volume problem. thanks to developers
hacker_zombie said:
I was on stock ROM as @ Noob
Changed to Aex Extended 5.7 official because of garbage volume , now on Aex ROM bootloop ,auto reboot,Pubg ping unstable network and many more bugs told me to change it.
Finally
So I installed Crdroid ROM yesterdayIt is mind blowing but still I can't call someone on this one
:crying:(Volte is working fine)
But while calling there is no sound from speakers (both)
and even on headphone also Mic is not working so No one will hear me on the other side ...
Please Guys please give me solution for it.:cyclops:
PS: suggests some other ROMs with better stability and performance with battery life
Click to expand...
Click to collapse
I Know the solution
1)flash fastboot stock 247 rom
2)flash twrp 3.2.2
3)install any of your favourite oreo rom
4)see mic will work now
5)reboot to recovery and select backup
Backup all the partitions
6) reboot to system and save both twrp 3.2.3 and twrp 3.2.2
.
7)If u want to use pie roms first install twrp3. 2.3. img and then flash your rom (mic works)
8)If u again want to come back to oreo roms just flash that twrp 3.2.2 reboot to recovery again
and restore that whole backup we created in step 5
9)Now Mic will work even after downgrade g from 9.0 to 8.1
Press thanks if it saved your Device and your time. ?????????????
thekrishna said:
I have same problem but when flashed this dolbyplus zip my problem solve
Click to expand...
Click to collapse
Work for me too.
Thanks.
thekrishna said:
I have same problem but when flashed this dolbyplus zip my problem solve
Click to expand...
Click to collapse
Thanks my friend, this fix worked on my Max Pro M1 (4GB version) running LineageOS 15.1.
My calls stopped working pretty much overnight, I'm still not sure what caused it. I couldn't hear the caller and they couldn't hear me. I wonder how exactly this fix works?
Edit: I just realized that Dolby Plus also disables SElinux. Is there no way around it?
I already have 3.2.3 installed, it's still not working. I'm running OxygenOS port
thekrishna said:
I have same problem but when flashed this dolbyplus zip my problem solve
Click to expand...
Click to collapse
Worked
Thanks for saving
thekrishna said:
I have same problem but when flashed this dolbyplus zip my problem solve
Click to expand...
Click to collapse
sadly I've just moving into Pie, but several things happened. And I'm about a few steps from going back to Oreo
thekrishna said:
I have same problem but when flashed this dolbyplus zip my problem solve
Click to expand...
Click to collapse
Thanks a lot my friend,u save my day