Anyone here using a mix of the latest Oreo 8.1 with an older baseband? If so, which version and why.
I ask this because I have been experiencing a rapid pulsing sound randomly during phone calls, network tower or wifi calling, in which calling back or rebooting the device fixes. This also happens when using voice only on Hangouts. This is my second Pixel XL warrantied for this issue and figure might be a baseband issue. Any feedback appreciated. Thanks.
Related
Just wanted to see if anyone else has been experiencing this or maybe knows a way to fix this. I have 2 issues with the phone calling on this phone. I had the 925T since launch and never had an issue with it. ever since i sent it in for repair, I've had a strange issue. Fist one is dialing out. When attemting to make a call, it takes anywhere from 3 seconds to 40 seconds before the call actually gets connected. this is highly annoying as i dial a number and it feels like forever before the call actually connects. my other issue is after the phon ehas been one for a few hours, I dont get any incoming calls. the phone will not show me any incoming calls at all so I don't even know when someone calls me. Ive tried everything i can. tried changing sim cards, updated the bootloader and modem, tried different roms, kernels, stock odin, everything. and its the same story no matter what I do. Anyone Have an idea of what it could be? It only works well after a fresh reboot. calls works without issues. hours later, problem comes back
I've had the same exact problem but I attributed it to using an AT&T Sim card on an unlocked T Mobile phone.
I've now rooted and installed Xtrostolite Rom with latest modem and bootloader. I've yet to have any issues. Good luck.
Anyone else have this issue?
I have this issue. It seems if i leave wifi off i do not ever have this issue. I live in a crappy coverage area so i have to have wifi on at home. I just reboot when i leave. I hate this phone....
btothec said:
I have this issue. It seems if i leave wifi off i do not ever have this issue. I live in a crappy coverage area so i have to have wifi on at home. I just reboot when i leave. I hate this phone....
Click to expand...
Click to collapse
You think the problem is WiFi related?
Yes. If i leave wifi off i never have the issue.
Still is happening. whether I have wifi on or off it always happens. It seem,s to be an issue related to VoLTE. When I turn LTE off, the issue dissapears. Updated baseband and bootloader to latest version and issue is still there. Have a custom rom and the issue is still there. go back to the tmobile rom and the issue is still there. thinkiing of going back to a tmobile firmware and turning off VoLTE in the firware then reflashing back to custom rom and seeing if that helps. if not, im selling the phone and getting the F version of the regular S6 and calling it a day. im done with carrier branded phones.
Interesting enough I haven't had this issue in the last 3 to 4 days. I wonder if it is AT&T related.
I have this issue. All the time. Unlocked from tmo, using straight talk at&t. This phone is the worst.
Anyone not on AT&T network having this issue?
I wonder if flashing the AT&T modem on TMO model will help.
cbutt said:
I have this issue. All the time. Unlocked from tmo, using straight talk at&t. This phone is the worst.
Click to expand...
Click to collapse
Maybe you should get a phone from att.
If att service is better than tmobile then maybe there phone is better than tmobile's phone.
Pp.
PanchoPlanet said:
Maybe you should get a phone from att.
If att service is better than tmobile then maybe there phone is better than tmobile's phone.
Pp.
Click to expand...
Click to collapse
I've been able to switch between carriers on any phone that has the supported bands since the galaxy s2. The issue is with this phone. My mistake in buying it.
Please help!
same thing here its unbearable, using latest unibase and xtrestolite
I have tried a few roms and a few kernels. I have tried differ apns but att Sim in this phone doesn't work like it should. I was going to get a TMOBILE note 5 to use on att but now I know it's not worth the risk.
@stu5797, yea man, I wish I had a solution. I'm happy it's not just me, but pretty bummed that there seems to be no answer other than it just doesn't work properly.
I've noticed the issue only happens during peak hours. Can anyone confirm?
I was having similar problems after the 5.1.1 update so after a few troubleshooting sessions with TMO, they sent me a new phone. 2 weeks now and no more problems. First phone that I have not rooted and flashed..... I was also told by a store rep that a lot of people were having issues since TMO is upgrading towers for 12 band.
osmosizzz said:
Just wanted to see if anyone else has been experiencing this or maybe knows a way to fix this. I have 2 issues with the phone calling on this phone. I had the 925T since launch and never had an issue with it. ever since i sent it in for repair, I've had a strange issue. Fist one is dialing out. When attemting to make a call, it takes anywhere from 3 seconds to 40 seconds before the call actually gets connected. this is highly annoying as i dial a number and it feels like forever before the call actually connects. my other issue is after the phon ehas been one for a few hours, I dont get any incoming calls. the phone will not show me any incoming calls at all so I don't even know when someone calls me. Ive tried everything i can. tried changing sim cards, updated the bootloader and modem, tried different roms, kernels, stock odin, everything. and its the same story no matter what I do. Anyone Have an idea of what it could be? It only works well after a fresh reboot. calls works without issues. hours later, problem comes back
Click to expand...
Click to collapse
Are you still having this issue? I have the same issue and the same phone but mine is unlocked and working on cricket network. So yeah same problem taking forever to connect a call and no receiving calls mos of the time. No ring no notification of missing call. I been doing some research and find a temporary fix. Try going to settings -mobile networks and switch from lte/wcdma/gsm to wcdma/gsm or gsm only. But before do a test. Turn off data and try to make a call see how fast it connects then have someone to call your phone. If it works then this trick will work for you. Of course you gotta sacrifices lte speed . Basically having 4g only but at least will fix your calls. These problems seem to ve related to volte i been trying to disable it but there is no such option under phone app setting. I just dont have it. (I cann show some screen shots) so if someone knows a secret code or app whatever to turn it off i will appreciate it. My phone is a t mobile galaxy s6 edge.
PHP:
---------- Post added at 11:00 PM ---------- Previous post was at 10:45 PM ----------
stu5797 said:
I have tried a few roms and a few kernels. I have tried differ apns but att Sim in this phone doesn't work like it should. I was going to get a TMOBILE note 5 to use on att but now I know it's not worth the risk.
Click to expand...
Click to collapse
Try this..
Are you still having this issue? I have the same issue and the same phone but mine is unlocked and working on cricket network. So yeah same problem taking forever to connect a call and no receiving calls mos of the time. No ring no notification of missing call. I been doing some research and find a temporary fix. Try going to settings -mobile networks and switch from lte/wcdma/gsm to wcdma/gsm or gsm only. But before do a test. Turn off data and try to make a call see how fast it connects then have someone to call your phone. If it works then this trick will work for you. Of course you gotta sacrifices lte speed . Basically having 4g only but at least will fix your calls. These problems seem to ve related to volte i been trying to disable it but there is no such option under phone app setting. I just dont have it. (I cann show some screen shots) so if someone knows a secret code or app whatever to turn it off i will appreciate it. My phone is a t mobile galaxy s6 edge
Didn't work for me. I turn off data and I still have to wait until the call goes through
Hello, I have Tmobile and an unlocked firephone running the latest 4.6.6 (but this issue also happened prior to the latest update) When I am connected to WiFi at home, i do not receive text or calls, and yes i have full service, as soon as I turn of WiFi, all my texts and missed calls come pouring through all at once. is anyone else experiencing this? and if so, is there a fix? I have tried changing the Preferred network types and APN settings. Maybe there's a configuration I'm missing...
If I switch on wifi calling on Tmobile, caller cannot hear any dial tone/ringtone when they call me but my phone will ring as normal. One thing I noticed is that the caller is calling on a landline. I called Google support and they are not aware of this issue and send me a replacement phone. I have the same problem with the replacement phone. Does anyone have the same issue? Any idea on how to resolve this?
i been having it the other way around..
i am on verizon google pixel xl , and when i been calling lately, no dial tone.. but other person answers .. .
im rooted, and unlocked..
other day my dial screen had scrambled lettters too . .
helloagain said:
If I switch on wifi calling on Tmobile, caller cannot hear any dial tone/ringtone when they call me but my phone will ring as normal. One thing I noticed is that the caller is calling on a landline. I called Google support and they are not aware of this issue and send me a replacement phone. I have the same problem with the replacement phone. Does anyone have the same issue? Any idea on how to resolve this?
Click to expand...
Click to collapse
I am having the same problem on my new Pixel XL with WiFi calling on my end. I didn't have this issue on my Nexus 6 or 6P, so something is going on. I'm following this for a resolution.
EDIT: Yesterday my brother called me from his Verizon mobile phone and didn't hear it ring on his end, so it doesn't seem to be a landline only issue.
I'm bumping this up as it's still happening on my stock rooted Pixel XL with the January NMF26U update, and I haven't found any resolution anywhere. Has anyone else had this problem and found the solution? It sucks that I can't use WiFi calling because of this issue.
JimSmith94 said:
I'm bumping this up as it's still happening on my stock rooted Pixel XL with the January NMF26U update, and I haven't found any resolution anywhere. Has anyone else had this problem and found the solution? It sucks that I can't use WiFi calling because of this issue.
Click to expand...
Click to collapse
I dont think it's the phone, or at least not just this phone. I had the same thing with other devices using Wifi Calling.
pcriz said:
I dont think it's the phone, or at least not just this phone. I had the same thing with other devices using Wifi Calling.
Click to expand...
Click to collapse
Agreed, although as I said in my first post, this didn't happen on my Nexus 6 or 6P. I have the same ISP and the same T-Mobile Personal Cellspot/WiFi Cellspot Router that I had with the other phones. I see that you are on T-Mobile as well, and most of the complaints I find online are also T-Mobile customers with various phones.
Has anyone figured out a solution?
I'm currently on T-Mobile and I have the same issue. I thought it was on a landline at first, but tried with a co-workers phone (Sprint) and it doesn't ring on his end but on mine it does.
Called my phone using my wife's phone, Pixel as well using T-Mobile and hers rings.
Kind of weird.
Sent from my Pixel XL using Tapatalk
I'm out of town until next week so I can't install the 7.1.2 beta yet. I have seen talk of VOLTE improvements with it, so maybe it will help this issue too.
Sent from my Pixel XL using Tapatalk
Hopefully it works.
Just missed 10 calls from my boss. He said there was no ringtone and it wouldn't go to voicemail.
I mentioned before that it did go to voicemail even after not sounding but now this is ridiculous.
Some people with T-Mobile have the issues and others don't. Might have to call T-Mobile.
Checked all the settings in that "special" menu and everything's provisioned.
Sent from my Pixel XL using Tapatalk
I have this problem. Person calling me hears no ringing, just dead silence. Often they will hang up and call again because they think something's wrong (I mean there is...but so annoying lol). I haven't called T-Mobile yet. Never had this problem on my 6P. Only the Pixel.
Does anyone know if this has been fixed yet? I'm afraid to switch back to WiFi calling until it is, as I can't afford to be missing calls because people don't hear the ring on their end.
Have you guys filed a ticket with Google and T-mobile about this? I sent feedback through the Settings->Phone status way. It's definitely still happening on my Pixel XL with stock 7.1.1.
This is also happening to me. I'm with T-Mobile on their Prepaid Legacy plan. Brand new unlocked Moto 5g Plus.
Any incoming wifi calls and the caller gets silence and never sent to VM. On my end everything seems fine, I hear it ring and once I answer the connection is great. My old Galaxy has wifi calling and worked with no problem.
I've done a factory reset and gone through about every setting three times over. I pretty much bought the phone specifically for wifi calling since I live in the sticks and now can't even turn it on without missing calls.
welp11 said:
This is also happening to me. I'm with T-Mobile on their Prepaid Legacy plan. Brand new unlocked Moto 5g Plus.
Any incoming wifi calls and the caller gets silence and never sent to VM. On my end everything seems fine, I hear it ring and once I answer the connection is great. My old Galaxy has wifi calling and worked with no problem.
I've done a factory reset and gone through about every setting three times over. I pretty much bought the phone specifically for wifi calling since I live in the sticks and now can't even turn it on without missing calls.
Click to expand...
Click to collapse
Others have said that the June security update fixed it. After flashing that, I turned on WiFi calling again and it works for me now on my Pixel XL. If you haven't installed it yet, you should anyway.
Recently I noticed that I had been having some intermittent issues with audio on both incoming & outgoing calls since the 8.1 update. Basically, when the issue happens I can’t hear the person I am talking to nor can they hear me for ~10-15 seconds at the start of the call. It sounds as if the line is dead due to all of the silence.
Because of this, I decided to disable Enhanced 4G LTE Mode under the mobile network settings and haven’t had issues since doing this. My Pixel 2 XL is on 8.1 with the January 2018 security update. Has anyone else experienced a similar issue as I have? Were you able to fix it so that there weren’t issues when using VoLTE for calls & if so what was done to fix it?
Decept1k0n said:
Recently I noticed that I had been having some intermittent issues with audio on both incoming & outgoing calls since the 8.1 update. Basically, when the issue happens I can’t hear the person I am talking to nor can they hear me for ~10-15 seconds at the start of the call. It sounds as if the line is dead due to all of the silence.
Because of this, I decided to disable Enhanced 4G LTE Mode under the mobile network settings and haven’t had issues since doing this. My Pixel 2 XL is on 8.1 with the January 2018 security update. Has anyone else experienced a similar issue as I have? Were you able to fix it so that there weren’t issues when using VoLTE for calls & if so what was done to fix it?
Click to expand...
Click to collapse
No. I'm on AT&T using HD calling and it works great. How about try resetting your network in Settings>>System>>Reset options. You may also want to check your SIM because if it is an older one it may not (fully) support it. The SIM has two lines of numbers. The top line should end with at least 27. If that last number is less than 27, you will need a new SIM provisioned.
Is anyone else noticing this persistent issue across all the Pie ROMs where the phone doesn't ring when you're on LTE/4G?
If I set my phone to WCDMA preferred it locks to 3G and this seems fine. Calls are as normal.
On LTE the caller gets the usual connection tones and it seems like my phone is ringing to them, but it goes to voicemail.
On my end the phone fails to ring at all.
Didn't experience this with Oreo ROMs at all, but its been consistent across Pie.
I have seen a couple of complaints about it but maybe it got solved?
I'm not talking about VoLTE which is known to not work after the first reboot on Pie ROMs. My carrier doesn't support VoLTE.
I noticed that on official LOS 15.1, my carrier also does not yet support VoLTE so LTE should be dropping automatically to 3G when receiving phone calls but that is not happening and it goes to voicemail. This is the only reason why i returned back to MIUI.
uoiea0 said:
I noticed that on official LOS 15.1, my carrier also does not yet support VoLTE so LTE should be dropping automatically to 3G when receiving phone calls but that is not happening and it goes to voicemail. This is the only reason why i returned back to MIUI.
Click to expand...
Click to collapse
I seem to have solved it by totally disabling Volte from build.prop with a magisk module.
Seems the phone wasn't reporting to the network that it was only expecting calls via 3g