So I recently just rooted my droid and I'm running the evileris firmware atm I'm really happy with everything except that my phone can no longer make phone calls. The sound during phone calls does not work and I think it may not work sometimes in the music player as well. It works when I plug in the headphones but when i take them out no sound.
Airplane mode and resetting do not fix this problem and the updates that I've tried flashing from [FIX] Audiofix. NEED TESTERS FOR NEW KERNEL in the Hero CDMA forum do not work either.
This phone worked fine before rooting and flashing and the problem is present on all the roms I've used. The update above simply hangs my phone at the bootscreen, no matter which one I use. (Maybe its written just for hero?)
Anyways I was hoping one of you guys could have a fix or maybe have also had this same problem? Thanks!
(from what I've read in the thread above it seems the issue is a bad kernel that hangs up or fails to reset so you have to do it manually, but resetting doesn't fix the issue for my. My problem is constant phone call audio loss)
UPDATE: I have done some more experimenting and it seems the only problem is from the in-cal speaker, because when I put speakerphone on it works fine. The problem lies with the front speaker (part that goes to your ear).
maybe your phone is broken?
I went back down to 1.5 root, works fine. Its an issue with 2.1 :/ So currently I have 2 nandroid backups, 1 of 1.5 and 1 of 2.1 so I'm just switching in between the two.
did you try....
Did you wipe before flashing? After flashing did you try *228 opt 1? This may help as it sorted my audio issues with another Rom.
im having this same problem and i have no clue why i have tried everything knows possible to fix this.
I wipe before each flash as well as each recovery haha. atm my setup is 2.1 evil eris for the weekends and 1.5root for the weekday when i actually need to make calls
*228 opt 1 did not work btw
I just make a new backup at the end of the week and recover to the other one, works like a dual-boot pc or a bootcamp mac. It works, but its getting kidna old I'd rather just have 2.1 for good haha.
Longtime lurker.....1st time poster....I just installed leak v2 (I was one of those that was too impatient to wait for root)...I had the same problem that everything worked fine except the phone had no in call sound. went through all the setting and found that TTY was set to full...I unchecked it and the sound came back. I know this may be simple...but it worked for me.
brianwin33 said:
longtime lurker.....1st time poster....i just installed leak v2 (i was one of those that was too impatient to wait for root)...i had the same problem that everything worked fine except the phone had no in call sound. Went through all the setting and found that tty was set to full...i unchecked it and the sound came back. I know this may be simple...but it worked for me.
Click to expand...
Click to collapse
yesss thank you this worked for me.
BrianWin33 said:
Longtime lurker.....1st time poster....I just installed leak v2 (I was one of those that was too impatient to wait for root)...I had the same problem that everything worked fine except the phone had no in call sound. went through all the setting and found that TTY was set to full...I unchecked it and the sound came back. I know this may be simple...but it worked for me.
Click to expand...
Click to collapse
I'm having the same problem... During a phone call, I get no sound / can't hear the person I am calling from the "internal speakers" (i.e. the one you hold to your ear during a call). If I switch to external speakers (i.e. loudspeakers) I can hear the person I'm calling...
What is this "TTY" setting that fixed this problem for you? Where can I find it and uncheck it?
Related
EDIT:
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
That post fixed my problem, as well as fixed the problem which the data connection turns off after a call.
Hey guys, sup?
I have a huge problem with my TELUS Touch Pro. Great phone, but just one problem...
Whenever somebody calls me, I can't answer the phone. The onscreen "Answer" button doesn't work, the Talk button doesn't work, pressing the Select button doesn't work...pressing the headphone button does, but sometimes my headphones are in my pocket, or sometimes they're not with me at all!
The only way I can answer them is by ignoring the call, and calling them back. It sucks big time.
Anybody have a solution? And no, I'm not hard-resetting my phone. It started doing this for my first call, so I'm pretty sure it's not my fault.
HEEAAALLLPPP!!!
Is this the stock ROM?
Do you have BT on and connected?
Mine started doing that yesterday. I did a hard reset and so far everythings back to normal. Still do not know what it was tho
I just had my TP replaced and the new one did the same thing, I did not notice until a few days later as I use a bluetooth headset and pushing the answer key on the headset worked. I had to RTN the device to make it work properly. Have not had a problem since. it has been aabout a week and a half.
Sometimes I've noticed this happens when my memory is tied up elsewhere, ie media player or something. Try soft resetting your phone every morning that might help clear it up.
I have had this happen with me on my Titan which I recently traded in for my Touch Pro, and also on my Touch Pro. I noticed it coincided with installing iGo8 GPS software on both. A hard reset was the only way I found to fix it. Uninstalling the software did not do the trick. I could be wrong about the software title I am blaming, but I have everything reloaded on my phone except that, and all is well. I do have a Slide To Answer incoming call screen now with the MightyRom 4.9.5 rom installed, maybe this is a work around, don't know for sure. If anyone else has more feedback, let me know. I would love to find a fix for it so I can use my GPS software.
Mine started doing this crap last night. I reinstalled the S2A cab and just let it go.
I am starting to think it might just be the telus network being a boatload of suck. Mine does it with the stock rom without any programs loaded from time to time. I am thinking it must be the tower failing to acknowledge that you want to answer the call, so the phone keeps ringing becuase it sees there is an incoming call but the tower ignores that you are trying to answer it. This is just my guess based on what I have read about CDMA, I wonder if any GSM users have the same issue.....
Do any of you have Advanced Configuration installed? This is what caused this problem for mine and my brother's TP. Uninstalling didn't fix it. Had to hard reset.
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
I can tell you that this will more than likely fix this for you. Mine was doing the same thing, applied this, done and shut! Good luck.
OMG OMG OMG thanks!!!! That also fixed the problem where it ended the data connection after the call.
Sorry I took so long, I THOUGHT I was subscribed to the thread...
Thanks again!
I have eris21official-root.zip and sense-able 2.0.
When the phone rings I slide the slider down to answer and I cant hear anyone and the caller cant hear me. The call timer never starts. I had my friend sitting next to me call me, I answer and he hears in his earpiece my phone stop ringing but we cant hear each other.
When I try to make a call the contact picture comes up but no timer and the call doesnt ring in my earpiece or on his phone. Its like the phone is not connecting.
If I power down the phone and back up it works....and then a few calls later the same thing....nothing.
Any ideas?
I also have two icons in my programs for PDF viewer and contacts. They are side by side...
I hate to be a bother. I have read all I could to resolve this without posting but nothing worked.
Any help would be appreciated.
Do a factory wipe, and a dalvik with. Then reset the phone up, and do the 228 activation again. Still won't work, use my downgrade and wait for a rom based on the offical 2.1 upgrade.
NOOO!!! go into settings and change tty mode to off trust me
i have been having this same problem oh my god.. finally someone wth the same problem as me.. what i did was installed the heroic radio and did a *228 activation.. it has worked for me so far its been two days without the phone messing up..
Palmbxr said:
NOOO!!! go into settings and change tty mode to off trust me
Click to expand...
Click to collapse
Thanks for the reply, but tty was already off.
i can also vouch for this...my wife's eris has the same issues. In fact, she has had two eris's that have had it. I have checked the TTY and the also flashed the newest heroc radios to no avail. If anyone else has any ideas, it looks like i will have to revert hers back to 1.5
i can also vouch for this...my wife's eris has the same issues. In fact, she has had two eris's that have had it. I have checked the TTY and the also flashed the newest heroc radios to no avail. If anyone else has any ideas, it looks like i will have to revert hers back to 1.5
my phone is doing the same thing.. there has to be a fix for this. i have done everything i know to do and it still does it.. i will keep trying to fix it.
I just bought a new car recently and when I try to pair my Fascinate with the car bluetooth, my phone slows down considerably, won't successfully complete calls, and eventually locks up, forcing me to do a hard reset. My car's bluetooth program locks up as well. One time I got an error message on my phone saying services.exe had to force close. At first I thought the problem was with the car, but my dad's Droid Incredible works beautifully on it.
My phone is rooted w/o lagfix, and has launcher pro. It's also been de-binged and has other basic bloatware removed. I don't use taskillers either. Any help or advice would be greatly appreciated, thanks!
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Bluetooth Crash After 1st Call is Ended
DeezNotes said:
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Click to expand...
Click to collapse
I'm also having this same problem with my Bluetooth crashing after my first call ends when using following:
ROM ComRom 1.3
Kernel TW with Voodoo Sound+BLN+UV+Misc tweaks 4/15 by jt1134
Radio ED04
2011 VW Jetta SEL (just purchased a few weeks ago)
I'm thinking to go back to stock as well but would prefer some kind of fix or even a workaround over doing that.
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
(No Longer Resolved) The ROM was the Problem with Bluetooth
DeezNotes said:
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
Click to expand...
Click to collapse
Excellent!!! Thank you for this! I already had the ED04 modem so that wasn't the problem. Last night I updated my kernel and this morning I tried again with no success so the kernel wasn't the problem. Later this morning, I loaded up the MIUIwiz 1.1 ROM and on the way home from work, I tested 4 calls and viola SUCCESS!!! ComRom 1.3 was the culprit and even though MIUIwiz is based on ComRom, somewhere along the line Bluetooth in the ROM was fixed.
Thanks again DeezNotes!
Edit: My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
On the same setup, the problem is back. Its actually a lot worse than before. I actually noticed crashes from Pandora when hanging up a call and Pandora wasn't even running (for days). Even after uninstalling Pandora, still get plenty of consistent crashes after hanging up a call. Interestingly enough, this is with an Audi, so hearing the issue is with a VW isn't far off from what I'm seeing since those cars are typically very identical.
I'm trying out a different phone on a different carrier [again] later this week. If all goes well, I'm going to chalk it up to Samsung and their lack of QC. I would say it's an Audi/VW issue, but I've successfully used the same features with a Blackberry and an LG G2x. Later this week I'll try the HTC Sensation and see how things go. Based on my experiences so far, this might be the last Samsung smart phone I'll ever get.
Bluetooth drivers issue - causing crashes.
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
piemmmm said:
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
that sounds really really technical. any ideas on what we can do to fix it?
Handsfree Bluetooth Problem is Back
My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
I have the same issue with ED05 de-bloated, stock kernel.
Has anybody found a solution?
My calls are always on speakerphone, doesn't matter if the speakerphone button is on or not, I don't believe this is a hardware problem even though my screen was replaced a few days ago, I mean how could it possibly be. I can't be the only one with this problem, I have searched everywhere, seems like I am. I'm running stock (rooted) so I don't believe it is a software problem either, I have tried rebooting and clearing cache so far.
Details: Stock E2303 MM Rooted. Only thing that could be screwing with audio is Viper4Android, and I uninstalled its drivers already. Also the headphone jack is dead if it matters.
Sorry for creating thread ahead of time, but the problem has been fixed by flashing stock using Flashtool, incase someone has the same problem.
Hi, I'm having a issue with my redmi note 9 pro. Whenever i try to make a call, it always goes to speakerphone. I cannot get it to go to the earpiece. WHen i try turning off speakerphone, the audio is still routed through the bottom speaker, and the person on the end of the call notices i sound broken up. WHen i swotch on the speakerphone the sound is clear, and then the person can hear me just fine. I've tried with whatsapp, google voice, and the regular phone app, and all have the same issue. I'm running Evolution X currently as my rom, but i've tried lineage os, and it has the same bug. On stock MIUI I don't remember having this issue, so maybe it's something weird with the custom roms. I'm also rooted with magisk. Anyone got any ideas, or has anyone ever experienced this issue when running custom roms on this phone? Any ideas, or suggestions are welcome. Thanks
Hi, I have this problem too. Of course inside the pubg mobile game. To temporarily solve this problem, first turn off the phone and connect the headphones when the operating system logo is displayed. A hissing sound is heard when plugging in the headphones.
Of course, to avoid this problem, you should use Bluetooth headphones.
Hi, I just tried your suggestion. it doesn't appear to work. My issue is with the earpiece, not headphones. Headphones for me have always worked flawlessly when running custom roms or stock. My issue is when making calls using the earpiece. Making calls using headphones seems to work fine. However when trying to use the earpiece, i cannot get it to work. What i mean by earpiece, is the top speaker of the phone, the one you have to hold close to your ear when making a call. FOr whatever reason calls always remain on the bottom speaker, and never seem to go to the top speaker aka earpiece. This happens in all calls, and in apps like whatsapp. Has anyone else ever experienced this issue? Again, headphones seem to work fine, and yes I'm rooted, and running a custom rom. When i was running stock, I don't ever remember this happening, but now that i'm running a custom rom, i can't get the earpiece to work. I really don't want to go back to the stock miui rom, but idk maybe i will if a solution can't be found
pielordbrian said:
Hi, I'm having a issue with my redmi note 9 pro. Whenever i try to make a call, it always goes to speakerphone. I cannot get it to go to the earpiece. WHen i try turning off speakerphone, the audio is still routed through the bottom speaker, and the person on the end of the call notices i sound broken up. WHen i swotch on the speakerphone the sound is clear, and then the person can hear me just fine. I've tried with whatsapp, google voice, and the regular phone app, and all have the same issue. I'm running Evolution X currently as my rom, but i've tried lineage os, and it has the same bug. On stock MIUI I don't remember having this issue, so maybe it's something weird with the custom roms. I'm also rooted with magisk. Anyone got any ideas, or has anyone ever experienced this issue when running custom roms on this phone? Any ideas, or suggestions are welcome. Thanks
Click to expand...
Click to collapse
I am having the same issue! any solution please let me know!
I am having the same problem - BUT on stock MIUI 12.5 - it started happening after I upgraded. If I could go back I would, but am happy to flasha new ROM if that will fix it.
I was thinking of flashing Lineage 18.1 but if that is having the save issue I ont bother. It must be a note 9 pro issue seeing as I only have the stock version..
I wonder if anyone at all has fixed this issue. I even contact xiaomi technical support but they were useless!
Anybody found its solution please update?
I'm having the exact same issue. When I initiate call it's on loudspeaker even though I didn't select that option. The other side can't hear me well. When I select "speaker" then it's still on loudspeaker, as it should be, and the other person can hear me fine.
I had the problem on crDroid (Android 12) and am currently experiencing the same problem on Pixel Experience (Android 12).
Please help someone us
I found the solution when I changed sim 1 to sim 2 the problem was solved.
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Not quite sure I follow. Are you saying to remove sim 1? Or are you saying to change the default calling sim to sim 2 or something? I should note that I'm using both sims and a SD card. Are you saying I should just use sim slot 2?
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Short version:
OK, so I just tried your advice, and it WORKED.
Long Version:
Ok, so I first removed both sims with the phone off. Then i put one of my 2 sims ONLY in slot 2 like you said. I inserted it into the phone, booted it up, and made a test call. To my surprise, the phone wasn't on speaker. I couldn't beileve it. I tried again, and it worked. I switched to speaker, now it's on speaker. I turned off the speaker and it was back to the earpeice! I tried whatsapp, and same result, the earpiece was working. I then decided to shut the phone down, and put the both sim 1 and 2 back in the phone. Guess what? after booting the phone up again, and making a test call, it still works! I don't understand the rhyme or reason behind it, but I'm not complaining. I'm so happy it FINALLY works.
to recap, Basically here are the steps:
1. Turn Off phone
2. Remove both sim cards.
3. Put a sim only in slot 2
4. Turn on phone and make a test call, it should no longer be on speaker!
5. go ahead and shut down the phone, and put a sim in both slots, if you are using 2 sims.
6. Turn the phone back on, and make a test call. It should still be working on the earpiece!
yes - this worked for me also - I have been looking for so long. A simple and un-remarkab le solution to a serious problem. Xiaomi should have been able to solve this.
All the same - thank you!
Great phone that was hindered for quite a few months by this serious problem
Again - thank you !
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Thank you so much. I have been waiting for it for more than a year.