Database Info

SMS/ Phone call Issues

Hello everyone!
I installed TKHD ROM and love it except i'm having 2 very big issues!
1. Text messages. I don't get messages friends send me even when they're right next to me.
I've tried AirPlane Mode, rebooted, cleared Data and Cache of the app itself and nothing :'(
2.. Phone calls. When placing a phone call it sometimes lags before making that little chime (the one that notifies you that you're now making a call before the ringer sounds) It could sometimes take a good 5 seconds before making the call. Or, sometimes i make a call and it goes straight to VM even tho the person im trying to call is right next to me. This is also the same when people sometimes try to call me. Tho i'm not even using the phone, when thye dial it goes straight to VM sometimes.
Once again i've tried rebooting, flashing the ROM clean all over again etc but the same thing persists.
How did i install this ROM? By following the exact guide provided on the OP.
ROM: Latest version of TKHD
Kernel: Whatever comes with this ROM tho i also use SkyHigh
Recovery: Latest TWRP
Bootloader/ Modem: The latest version (OKC?)
I know some may say its my device but we'll idk about that. It only happens on this ROM.
I really like this ROM and would love to stay with it but idk how i can do that if i can't get the basics to work
Please help XDA !

Have you tried Odin to stock rom. Factory reset then fresh install? Also, I would download another copy of the rom. Could be a bad download.

edward6790 said:
Hello everyone!
I installed TKHD ROM and love it except i'm having 2 very big issues!
1. Text messages. I don't get messages friends send me even when they're right next to me.
I've tried AirPlane Mode, rebooted, cleared Data and Cache of the app itself and nothing :'(
2.. Phone calls. When placing a phone call it sometimes lags before making that little chime (the one that notifies you that you're now making a call before the ringer sounds) It could sometimes take a good 5 seconds before making the call. Or, sometimes i make a call and it goes straight to VM even tho the person im trying to call is right next to me. This is also the same when people sometimes try to call me. Tho i'm not even using the phone, when thye dial it goes straight to VM sometimes.
Once again i've tried rebooting, flashing the ROM clean all over again etc but the same thing persists.
How did i install this ROM? By following the exact guide provided on the OP.
ROM: Latest version of TKHD
Kernel: Whatever comes with this ROM tho i also use SkyHigh
Recovery: Latest TWRP
Bootloader/ Modem: The latest version (OKC?)
I know some may say its my device but we'll idk about that. It only happens on this ROM.
I really like this ROM and would love to stay with it but idk how i can do that if i can't get the basics to work
Please help XDA !
Click to expand...
Click to collapse
What app are you using for messaging? I'm having an issue with MMS sending right now, but I think it's related to WiFi Calling and EvolveSMS. However my cousin did send me a text yesterday which I did not receive, and I wasn't on WiFi Calling at the time.

I am actually using stock SMS and MMS.
And I heard something about WiFi calling or wifi in general
And I do have them off and still run into this issue

Mi4, CM13 echo in calls

Hello,
I have a Mi4 with TWRP and CM13, latest nightly from today, but the problem also occured on the nightlies before.
During calls the other party complains about hearing himself. On the internet I found ideas like:
- disabling the "OK Google"-recognition on every screen (although this held true for Skype-video-calls)
- lowering in-call volume
I did not find any other ideas. Do you have an idea?
EDIT: I also tried two things:
1. entering the following things -> no changes
su
setprop persist.audio.fluence.mode false
setprop persist.audio.handset.mic analog
reboot
2. disabling the mic while calling -> success, the other party has no echo anymore
This of course is no useful solution, as normally a mic is needed for calling.

I'm facing the same problem. Did you find a solution?

nope

Same here.
Posted this in another forum. After trying a few things it appears that microphone is relaying sound from the speaker back to the caller. It's like the microphone is too sensitive so it picks up the callers voice from the speaker.

yes, it is definitely a problem with the mic. as soon as you deactivate it, the other party has no echo anymore.
EDIT: I wonder if this is the case, because in the native MIUI there was a noise-suppression and dual-mic option which may be good for avoiding this problem. I highly doubt CM will implement this specifically for this phone. Right now I am always calling with a headset which works fine.
EDIT: Headset isn't working anymore too. Callers say I am way too silent. Soundrecorder App confirms that mic sensitivity is too low.

I think the solution might be here, thought I am not able to understand completley what they are doing there: https://jira.cyanogenmod.org/browse/NIGHTLIES-2619

It should be solved after installing the next nightly:
https://www.cmxlog.com/13/cancro/
http://review.cyanogenmod.org/#/c/139932/
Could someone pls give a feedback after installing it? I switched from nightly to snapshot-channel and therefore am not able to check.

hsquare said:
It should be solved after installing the next nightly:
https://www.cmxlog.com/13/cancro/
http://review.cyanogenmod.org/#/c/139932/
Could someone pls give a feedback after installing it? I switched from nightly to snapshot-channel and therefore am not able to check.
Click to expand...
Click to collapse
Is the problem still existing with the new snapshot release?

I'd like to know that too! I switched to nightlies now and some people I talked with say it's still there, some don't.

hsquare said:
I'd like to know that too! I switched to nightlies now and some people I talked with say it's still there, some don't.
Click to expand...
Click to collapse
I heard from some guys using latest Snapshot that the echo is gone but when they make a hands free call, the speaker and mic is very quiet/ low. So probably the problem is not totally fixed right now.

I'm on Nightly 13/04 right now, no echo at all but the phone is turning of during call (after I tried to turn on the display). Is there another behaviour on the Nightly you are using?

Microphone not working...

My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??

i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse

LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.

since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.

I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.

toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...

I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.

Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem

LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?

I installed lineageos 16 without gapps and is working good for hours until installed gapps.

ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??

18.1 hotdogb phone app issue

I hope this goes to the right place, if not can someone direct me to where it goes.
I'm having an issue with what appears to be the phone app. i can call out but when the recipiant picks up all they here is a beep like a old school fax whine. I've searched this issue and I'm at a loss. Phone is Oneplus 7t with 18.1 hotdogb with no Google.
Thanks for any help,
Lowdownin

It is not just the phone app from my digging. I am also having the same issue with Signal, as well as another dialler I have installed to test. It also happens when using a SIP client both in the Phone app and separately (Mizudroid).
Regardless of how the call is made (inbound to me or outbound to another), all they hear is a high pitch tone. I can hear them fine. Hitting mute stops the noise for them, however unmuting restores it.
I have checked and the phone records sound via the microphone and when in speaker mode and the playback is perfect.
As per @Lowdownin928, I am at a loose end. I am in the process of downgrading and will report if that has an effect.

New ROM released today, tried that first - https://download.lineageos.org/hotdogb. No change.
Downgraded to the last before the one I was having trouble with - lineage-18.1-20210926-nightly-hotdogb-signed.zip - however this has the same issue.
At this stage I cannot work out why the ROM could cause this but then using other ROM's does not fix, even when doing a full wipe. Something else is going on.
Am looking at reverting to a t-mobile or international ROM to go way back and see what happens. If that does not fix it then I am stumped, as it seem to not be hardware. Very, very strange.

OK, so have installed an original t-mobile version of Android 10.0.3 for the 7T and low and behold, it works perfectly. No issue with outbound calls from SIM or SIP, did not bother testing further.
For reference, factory default t-mobile rom I used was at https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/Q/, put phone in EDL mode and run the MDM. Came up fine.
Proceeded to System Update to v. 11.0.1.4.HD63CB. Reboot then tested for outbound noise on calls - no problems at all.
So at this stage the only way to fix this is to revert to the stock ROM, even with 11 it works fine. I have no idea what has happened with the LineageOS ROM but there is a fault somewhere. I am heading off to ask the question (and hope you will as well) but hope all this detail gives you an idea of where to go.
Just had a thought - there may be other ROM's that work fine, it could only be LineageOS that has this issue. If you don't need the feature set then look around in here.
Super surprised no-one else has had this issue, but there you go.

Success. Thanks to LuK1337, Lineage Team Member on the Reddit Support area this seems to have cleared the issue.
---
T-Mobile firmware isn't supported, you can flash retail one by following https://wiki.lineageos.org/devices/hotdogb/fw_update
---
So bootloader, flash lineage recovery, enter fastboot mode inside lineage recovery, flash all the .img's as laid out and then follow the rest of the install. Took a long time and careful reading but this was the key for the phone noise.
Thanks LuK1337.

Just wanted to let you guys know that I was also having the same issue and this solved it for me. Thanks so much dmc.kiint and LuK1337

is there a working build of lineage 18 for moto g8 plus?

hi, I have a moto g8 plus and I want to use Lineage but my devices isn't under the supported devices list. is there a working unoffical lineage build that is opensource for the moto g8 plus?
and if there is no build, how much work is it to port lineage to a new device and what knowledge is needed?
thx for your answers beforehand

I used @waltermobile's guide for 17.1 https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83094247
plus @AndyYan's 18.1 build: https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Seems fine so far - bluetooth audio wasn't working at first, but this workaround fixed it: https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83397105

stormarrest said:
Seems fine so far - bluetooth audio wasn't working at first, but this workaround fixed it: https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83397105
Click to expand...
Click to collapse
Are you still using this? Any additional quirks or oddities besides the known bluetooth issue? I'm thinking of installing it; i'm tired of waiting for a custom ROM. thanks.

gfrank227 said:
Are you still using this? Any additional quirks or oddities besides the known bluetooth issue?
Click to expand...
Click to collapse
Yes! After it took 5 days to set up, I was loath to throw any more time after it
The only other problem I've seen is that I can't join Zoom meetings – I'm able to log in, but either clicking a link or entering a code just dumps me back on the app's main screen. Other meeting / call apps work fine.

stormarrest said:
Yes! After it took 5 days to set up, I was loath to throw any more time after it
The only other problem I've seen is that I can't join Zoom meetings – I'm able to log in, but either clicking a link or entering a code just dumps me back on the app's main screen. Other meeting / call apps work fine.
Click to expand...
Click to collapse
OK thanks for the info.
I attempted to install Lineage 19.2 on my moto g8 plus but it got stuck on the curved line and circle screen. i'm not even sure if I flashed it correctly; this is literally my first time trying to flash a whole GSI/Rom on any phone. Any advice or instructions would be appreciated (I used TWRP; after it was done flashing and I tried to restart it gave a warning that there was no OS; not sure how that's possible, and I still got that curved line screen). In short, I am not sure if it's the .img file I used or the flashing method, or perhaps even both.