Related
Trying to gather information about the no audio on phone call issue in order to troubleshoot it.
Symptom: You answer an incoming phone call or make an outgoing phone call and the call connects however there is no audio on the phone regardless if using the phone or Bluetooth device. The other party only hears complete silence. Rebooting temporarily clears the issue, but it can occur again at anytime.
My config is ViperOne 7.0.1 and ElementalX 18.0 (Issue also occurred on 17.x) and I have the latest 6.09.401.5 firmware.
I have seen this issue reported in a few ROM threads and for different kernels, so it seems to happen for other ROM/kernel configurations.
If anyone else is having this issue can you please post your:
Firmware version
Rom and version
Kernel
Settings/reasons for why you think it is occurring?
I love my current setup and it performs awesome with super battery life, but this issue is killing me as I have to use my phone for work and I never know if I will be able to properly make or answer a phone call.
Any idea's for a root cause?
Having this very same issue on my stock rom. 4.4.3 / 6.09.401.108 . I personally think it's an issue with HTC's latest updates as I am pure stock.
Xistance said:
Having this very same issue on my stock rom. 4.4.3 / 6.09.401.108 . I personally think it's an issue with HTC's latest updates as I am pure stock.
Click to expand...
Click to collapse
That is very good info as I was wondering if pure stock had the issue.
Do you remember when the issue first started? Was it just after the first 6.09.401.1 OTA update or did it happen at all back on 5.xx?
Thanks again for the info.
I do not recall having this problem prior to the previous update. This latest update and the last one, both have had this issue.
My setup is ViperOne 7.0.1 and elementalx 18.0.
Fw version is: 6.09.401.5
I don't remember if I altered the radio separately, anyways here's the version I am using : 4T.29.3218.08_10.33F.1718.01L
Experienced this mute call once while on previous kernel version, 17.2, upon reboot all was well again.
Kernel is and was installed with pretty much default options.
Seeing that this issue is very difficult to reproduce, maybe it's not related to the kernel at all but simply some external app (from rom or otherwise)? Well as to it chances are this to be rom related since we're all using this rom?
Sent from my HTC One
millicent said:
My setup is ViperOne 7.0.1 and elementalx 18.0.
Fw version is: 6.09.401.5
I don't remember if I altered the radio separately, anyways here's the version I am using : 4T.29.3218.08_10.33F.1718.01L
Experienced this mute call once while on previous kernel version, 17.2, upon reboot all was well again.
Kernel is and was installed with pretty much default options.
Seeing that this issue is very difficult to reproduce, maybe it's not related to the kernel at all but simply some external app (from rom or otherwise)? Well as to it chances are this to be rom related since we're all using this rom?
Sent from my HTC One
Click to expand...
Click to collapse
I have seen it reported on a few other ROM threads and even stock software, so I am pretty sure it is not related to Viper. Might be an app we all installed that causes it, or some other weird setting we all use.
I also experience occasionaly problems with an audio in phone calls, reset helps though.
My config is:
Unlocked, S-on
ViperOne 7.0.1
6.09.401.5
If you upgraded your firmware directly to 6.09.401.5 from 4.x/5.x, try flashing the 6.06.401.1 firmware first and then update it to 6.09.401.5
That seem to help me with this issue.
Sorry, still kind of a newb when it comes to roms. I've had viperone installed for the past year (currently running 7.0.0) but in the past two weeks, all audio during calls has completely quit working. The calls go through, but I can't hear them and they can't hear me.
So.... how can I fix this? haha
lotreaglesfan said:
Sorry, still kind of a newb when it comes to roms. I've had viperone installed for the past year (currently running 7.0.0) but in the past two weeks, all audio during calls has completely quit working. The calls go through, but I can't hear them and they can't hear me.
So.... how can I fix this? haha
Click to expand...
Click to collapse
like the post above yours suggest start updating your firmware ... you may need to s-off your phone first
http://forum.xda-developers.com/showthread.php?t=2365506
http://forum.xda-developers.com/showthread.php?t=2316726
http://forum.xda-developers.com/showthread.php?t=2428276
having the same no sound issue during calls. Reboot seems to help but this is getting annoying.
On ViperOne 7.0.1
Firmware 4T.28.3218.04_10.33E.1718.01L
Stock kernel.
My wife also has an HTC One and its completely stock on the whatever the last OTA update was and its also having the same issue with no sound.
lotreaglesfan said:
Sorry, still kind of a newb when it comes to roms. I've had viperone installed for the past year (currently running 7.0.0) but in the past two weeks, all audio during calls has completely quit working. The calls go through, but I can't hear them and they can't hear me.
So.... how can I fix this? haha
Click to expand...
Click to collapse
enkur said:
having the same no sound issue during calls. Reboot seems to help but this is getting annoying.
On ViperOne 7.0.1
Firmware 4T.28.3218.04_10.33E.1718.01L
Stock kernel.
My wife also has an HTC One and its completely stock on the whatever the last OTA update was and its also having the same issue with no sound.
Click to expand...
Click to collapse
it's not ROM related, some users are experiencing it, others are not (pretty much irrelevant of ROM / firmware combination.... though obviously having the ROM inline with firmware is always better), anyway:
http://forum.xda-developers.com/showpost.php?p=56516913&postcount=39
crushalot said:
Trying to gather information about the no audio on phone call issue in order to troubleshoot it.
Symptom: You answer an incoming phone call or make an outgoing phone call and the call connects however there is no audio on the phone regardless if using the phone or Bluetooth device. The other party only hears complete silence. Rebooting temporarily clears the issue, but it can occur again at anytime.
My config is ViperOne 7.0.1 and ElementalX 18.0 (Issue also occurred on 17.x) and I have the latest 6.09.401.5 firmware.
I have seen this issue reported in a few ROM threads and for different kernels, so it seems to happen for other ROM/kernel configurations.
If anyone else is having this issue can you please post your:
Firmware version
Rom and version
Kernel
Settings/reasons for why you think it is occurring?
I love my current setup and it performs awesome with super battery life, but this issue is killing me as I have to use my phone for work and I never know if I will be able to properly make or answer a phone call.
Any idea's for a root cause?
Click to expand...
Click to collapse
Update to the latest Google play services with this version, released yesterday https://play.google.com/store/apps/details?id=com.google.android.gms. Or download apk from here http://www.apkmirror.com/apk/google.../google-play-services-6-5-99-1642632-038-apk/ Problem is solved for me. Also clear cache and data for Google Play Services and for Google Play Services Framework (Settings -> Apps -> All -> Google Play Services -> clear cache -> Manage space -> Clear all data).
For me all works now with latest services
To solve the gms problem do this:
Go to play store and search for "disable services"
Install it and Browse to Google play services (in system or after self autoupdate in data)
Only disable the checkinservice .
Reboot and till now all Works
thx goes to n0j0e he found it out .
After disabling checkinservice, did you experience lots of wakelocks from checkinservice?
chrriiiss said:
After disabling checkinservice, did you experience lots of wakelocks from checkinservice?
Click to expand...
Click to collapse
After you disabling checkinservice, google play service always try to run it, that puts your m7 in awake mode all the time even in screen off. Applying the venom fix & re-enable the checkinservice is the best solution for me.
Sent from my HTC One using XDA Free mobile app
Hi everyone. I have a Korean variant note 5 (SM-N920K). and I've rooted it with the noble kernel specifically for the K model. Everything runs fine except the fact that absolutely no sound can be heard when making calls. I flashed back to stock rom and calls work like normal, but once rooted the sound goes again. I can make calls perfectly well but it's as if the speaker for calls doesn't exist. Putting it on speakerphone doesn't help either.
Has anyone had a similar issue and knows what I might have to do to fix this? I tried flashing one of the other kernels such as arter97 but they crash the phone and I'm unable to boot up.
My version is the 64GB version...any help would be much appreciated!!
Same problem here! Any solution ?
Hi, I just rooted my korean SM-N920S by following the steps in the link below:
https://clickitornot.com/twrp-recovery-and-root-samsung-galaxy-note-5/
I didn't root my phone by flashing kernel. Instead, I flash twrp first, then flash supersu or magisk to root my phone. After that flash custom room which come with custom kernel.
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...
Hi,
my ASUS ME176CX currently is:
* rooted
* xposed
* able to boot "anything" (unsigned bootloader)
* using L-Speed
and is running UL-K013-WW-12.10.1.24
So fine so nice...but:
My charging rate drops from 0.5% each minute to 0.125% each minute.
APK-files I download from apkpure reaches the external SD-card as *.zip files, which
I first have to rename to install them (so the structure as such is not touched).
May be all this problems are a result of my experimenting...
I think it is time for the total reset of everything.
But what to take?
* UL-K013-WW-12.10.1.24 again ?
* UL-K013-WW-12.10.1.33 (I read about a sever impact to battery life, though) ?
* UL-K013-WW-12.10.1.36 ?
* the russian lite version of the 36er firmware (I read of not working audio/gps/camera with this?)
* anything else which I had not found while searching?
And: Since TWRP now is installed, I would flash whatever it is advisable to flash with that...
and overwriting the code of a running program -- in this case the flashing application: TWRP itsself.
At this point I need the help of some deep gurus, I think?
How should I flash what firmware to get "the most" (less lagging, more battery life) out of my tablet?
Thank you very much for any help!
Cheers,
Noriatell
PS: Does anyone has experienced any wearout of the internal flash due to write cycles so far?
i use .36 uk release and i havent got any issues with it, ive rooted and debloated (i dont know why people are banging on about a russian lite version, its just debloated aswell isnt it)..
Theres been no point really for TWRP so far, i dont know if a custom rom will be released anytime soon
Hi russy23,
thank you for your reply
One thing I didn't understand (language problem...I am no native english speaker):
"Theres been no point really for TWRP so far" means: There are no problem reported
so far flashing a official ROM with the combon of unsigned bootloader and permanent
TWRP?
Do I need to reflash the bootloader?TWRP again?
Sorry for the tutti frutti of questions...I simply fear to lock out myself from the tablet...
Thanks a lot!
Cheers
noriatell
Ive not lost TWRP after i reflashed the official firmware, so it must be a permanent recovery..
well we were given TWRP a while ago to flash custom roms and eveything has gone silent since, for me stock rom debloated is good
russy23 said:
Ive not lost TWRP after i reflashed the official firmware, so it must be a permanent recovery..
well we were given TWRP a while ago to flash custom roms and eveything has gone silent since, for me stock rom debloated is good
Click to expand...
Click to collapse
Hi russy32,
I flashed the 36er ROM...and got an error at the end...but it rebooted fine (so far...did made extensively testing right now, though).
I had to reflash SUPERsu and xposed, but this seems to be quite normal...
Do you know, what triggers this error (Saying "Error flashing <filename of ROM>.zip") ?
When reflashing the 24er ROM there was a problem with a check in one the scripts, which has to be removed by hand before flashing...
I currently dont know of any similiar with the 36er ROM. And that failure was right in the beginning of the process and the ROM.
Is there a way to check whether I am on 36er ROM now (something which is for sure, since the "About" is only a copy of a string...)?
Cheers,
noriatell
If I remember correctly I got an error when installing..but everything was working well after..I installed it through adb. The only way I know to check version is the about section
russy23 said:
If I remember correctly I got an error when installing..but everything was working well after..I installed it through adb. The only way I know to check version is the about section
Click to expand...
Click to collapse
Bad news...
To get a clean install without error I wiped cache, system, Dalvik-cache and system and reinstalled the ROM.
I got errors and a bootloader-loop (stuck in the "Intel" logo).
Now the tablet is charging...I need new power for the next steps.
TWRP is still working.
What had caused this?
How can I get back a clean boot?
Post edit:
I have reapplied my nandroid backup of the 24er ROM. It works so far (It boots). But I have
back the problems I described above.
Question remains:
How can I get a clean install of the 36er ROM?
Cheers,
noriatell
I posted this in the Q&A thread but it looks pretty dead, I can delete that if needed but hoping to get some help on this one.
I had an Android 10 update this morning, and ever since the person on the other end cannot hear me at all. No way to fix, reset etc.
I don't think I can roll back right? My only solution might be to unlock BL and flash custom, because I cannot wait for a patch to fix this.
Anyone have this same issues? Is there an alternative to going custom? If I do go custom what is the closest to stock that actually fixes this?
This sounds like the problem I have been having since December with still no permanent fix. A temporary fix is to turn on the loudspeaker and then back off and the other caller can hear you. Seems the bug will never get fixed after waiting 3 months now for a fix now.
I decided to use a custom Rom (Ion OS is what I'm using, but any AOSP Rom will do), which fixes the issue altogether. Or you could downgrade back to MIUI 10, which I can confirm it also fixes the call audio issue. So, yes you'll need to unlock the bootloader. I tried other MIUI Roms like Mi-globe, Xiaomi.EU, and ROS-MIUI, and all give the same issue. Well, the ones that's base on android 10 give the call audio issue, the ones based on android 9 don't.
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
orangekid said:
Ok I fixed this yesterday on my own, here's what I did:
1) Back everything up that i needed, then unlocked the BL.
2) booted into TWRP, then flashed TWRP, then flashed the disable verity zip
3) Tried a few ROMs, all had the same issue, and other issues
4) Finally downloaded a ROM I "built" from mi-global, https://mi-globe.com/miui-firmware-rom-builder/
5) Once the ROM was built (I included Magisk, removed some bloatware etc), I flashed it, I intentionally used about a month old build since the the current stock one is what borked me. Mic problem still evident.
6) So finally I removed the modem.img file from the ROM zip and went into fastboot and manually flashed the modem image, rebooted, and that fixed it.
No matter what you have to be BL unlocked to flash files in fastboot, but I think just flashing the older modem.img would have fixed it, but I am better for it because now i have a stock android 10 ROM with bloat removed, and root permissions.
Click to expand...
Click to collapse
Hello orangekid, am on the same situation as you was. The 2 mic Works flawlessly when i rec a vidéo or audio memo but when its on call other hear me with buzing and muffling sound.
I am on custom rom Android 11 (EvolutionX 5.3).
Can u plese give me a link to the modem that you flashed in order to ride off this issue.
Thanks in advence
Sld_Ultra said:
I might have to give that a try then. Glad you have yours working, hope that's the problem I'm having too with the modem.img.
Edit: Tried your steps, but what I get is complete silence now on both ends of a call. Used a modem from the 11.0.6.0.PEAMIXM (android 9) stable build.
Tried V11.0.3.0.QEAMIXM (android 10) firmware and it just brings back the buzzing/static muffled sounds. Shame I can't find why I can't use MIUI 11 without getting this issue.
Click to expand...
Click to collapse
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Sindalf said:
Hello sld ultra, did u find a solution for the mic problem since ? Its really annoying.
Click to expand...
Click to collapse
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Thanks for
Sld_Ultra said:
The problem went away after updating to a MIUI 11 build a month later, can't remember which one. Ever since then, the mic problem hasn't come back and had no problems with MIUI 12.
I'm now using Evolution X 5.3 since the Mi 8 stop getting MIUI updates. Now the only time the mic problem comes back is is when I flash ZenX OS ROM, none of there builds work for me. I don't know why, I just decided that my phone hates what ever setting or config that's in the ROM. From the maintainer's view, I missed up something on my phone, yet other custom and MIUI ROMs work fine.
Back to your question, I didn't find a solution to the problem, it just went away after an update. Now ZenX OS is the only ROM that brings back the problem. Plan to try their A11 build when it comes out, if the problem is still there I'll just move back to Evolution X. Are you using the latest MIUI 12 build? Global stable or xiaomi.eu beta?
Click to expand...
Click to collapse
Thanks for the reply, i was with official MIUI 12 globale version , now i am using évolution x 5.3, i have also replaced my screen and only some twrp Works.. the issue it not related to hardware because when i rec a vidéo or audio memo its Works normally, but when calling the sound is muffled and buzing.. i will try to get back to an android 9 rom ? I will try and will see