After I signed up for the Pie beta on my U1 Note and upgraded to ZRKP, although I see the option for "Caller ID and spam protection" being turned ON, it does not work any more.
Any number I dial out (that are not in my contacts) or any incoming call I receive, Smart Call seems to be resting.
I cleaned up cache in both SmarCall app and the Phone - but to no avail.
Anyone else is experiencing this issue?
mffu said:
After I signed up for the Pie beta on my U1 Note and upgraded to ZRKP, although I see the option for "Caller ID and spam protection" being turned ON, it does not work any more.
Any number I dial out (that are not in my contacts) or any incoming call I receive, Smart Call seems to be resting.
I cleaned up cache in both SmarCall app and the Phone - but to no avail.
Anyone else is experiencing this issue?
Click to expand...
Click to collapse
I'm in the same boat man. Hopefully the next beta fixes that issue
I appreciate your reply!!! Seems like we are the only two sharing the same issue. Thanks again!
mffu said:
I appreciate your reply!!! Seems like we are the only two sharing the same issue. Thanks again!
Click to expand...
Click to collapse
I'm not sure how many others depends on it but personally it's a a very important reason for me to buy the unlocked version
my note 9 is able to identify all callers even those not in my contacts. its working for me. HD voice and volte is not however can anybody else confirm this?
AndrewM3 said:
my note 9 is able to identify all callers even those not in my contacts. its working for me. HD voice and volte is not however can anybody else confirm this?
Click to expand...
Click to collapse
What carrier do you have?
Mr. Orange 645 said:
What carrier do you have?
Click to expand...
Click to collapse
I have TMobile
But I think it's cuz I'm on the beta that's why I don't have volte anymore I also just flashed 960U1
AndrewM3 said:
I have TMobile
But I think it's cuz I'm on the beta that's why I don't have volte anymore I also just flashed 960U1
Click to expand...
Click to collapse
HD Calling and VoLTE (They're the same thing) should be working. I know it works on Oreo U1 on TMB. But maybe it's not implemented on the beta yet. Honestly I haven't thought to check for it.
Mr. Orange 645 said:
HD Calling and VoLTE (They're the same thing) should be working. I know it works on Oreo U1 on TMB. But maybe it's not implemented on the beta yet. Honestly I haven't thought to check for it.
Click to expand...
Click to collapse
I'm on Verizon and HD Calling and VoLTE working fine but not the caller ID spam protection.
mffu said:
After I signed up for the Pie beta on my U1 Note and upgraded to ZRKP, although I see the option for "Caller ID and spam protection" being turned ON, it does not work any more.
Any number I dial out (that are not in my contacts) or any incoming call I receive, Smart Call seems to be resting.
I cleaned up cache in both SmarCall app and the Phone - but to no avail.
Anyone else is experiencing this issue?
Click to expand...
Click to collapse
FYI. It is back working on the very newest beta
Stevieboy02008 said:
FYI. It is back working on the very newest beta
Click to expand...
Click to collapse
I am on Verizon and ZRLL beta (latest), Smart Call is still not working. Hopefully, the official Pie will fix it.
I'm in the same boat. Unlocked Note 8 on 2nd beta of Pie and Smart Call simply doesn't work. I really do not want to download anything 3rd party. Hoping it works in the official release.
I'm also wondering if it has anything to do with Hiya going to a paid subscription.
I'm writing from Turkey, I have also unlocked note 9. after i updated my phone to pie, smart call stoped working. I've reached someone from Samsung Turkey they told me to do somethinks ( inc. factory reset ) it didn't solve my problem. As i read some forums the problem comes from pie... Hope samsung would fix this issue.
Related
Do any of you notice, all the incoming calls on S5 is showing up with +1 as prefix.
I checked my Call History and before update i don't see the +1 prefix while all received calls after update is showing +1
Is it Just me?
Is there a setting to not show +1 code?
TIA
sakdroid said:
Do any of you notice, all the incoming calls on S5 is showing up with +1 as prefix.
I checked my Call History and before update i don't see the +1 prefix while all received calls after update is showing +1
Is it Just me?
Is there a setting to not show +1 code?
TIA
Click to expand...
Click to collapse
I believe Land line numbers or numbers outside of your area code generally come up with a +1 Cell numbers should come up as (xxx) xxx-xxxx
cstayton said:
I believe Land line numbers or numbers outside of your area code generally come up with a +1 Cell numbers should come up as (xxx) xxx-xxxx
Click to expand...
Click to collapse
You wrong all my calls on S5 and Note 4 coming with +1. Must be software related.
Edit: I just check my wife phone Note 3 with 4.4.4 and is the same with +1. Anybody else with 4.4.4 software can confirm this ?
Clicking from notecable N910A
norbarb said:
You wrong all my calls on S5 and Note 4 coming with +1. Must be software related.
Edit: I just check my wife phone Note 3 with 4.4.4 and is the same with +1. Anybody else with 4.4.4 software can confirm this ?
Clicking from notecable N910A
Click to expand...
Click to collapse
im on OA1 4.4.4 and my numbers display as (xxx) xxx-xxxx only time mine show the +1 is if it is outside my area code or if it is a land line, I'm not seeing any settings related to the +1 prefix. Do you have any custom mods installed? xPosed framework and modules? could be one of those causing the issue.
cstayton said:
im on OA1 4.4.4 and my numbers display as (xxx) xxx-xxxx only time mine show the +1 is if it is outside my area code or if it is a land line, I'm not seeing any settings related to the +1 prefix. Do you have any custom mods installed? xPosed framework and modules? could be one of those causing the issue.
Click to expand...
Click to collapse
No. 100% stock. If you check you call log you have all incoming calls display as (xxx) xxx-xxxx? If you do why I have different ? I have +1 on all my (S5, Note 4) , my wife's (Note 3) and my daughter's( S5) with software 4.4.4 all phones are bone stock
Clicking from notecable N910A
norbarb said:
No. 100% stock. If you check you call log you have all incoming calls display as (xxx) xxx-xxxx? If you do why I have different ? I have +1 on all my (S5, Note 4) , my wife's (Note 3) and my daughter's( S5) with software 4.4.4 all phones are bone stock
Clicking from notecable N910A
Click to expand...
Click to collapse
as you can see in the screenshot attached, it all displays correctly (I have oblitered the details of the numbers but it is still visible that they display correctly
cstayton said:
as you can see in the screenshot attached, it all displays correctly (I have oblitered the details of the numbers but it is still visible that they display correctly
Click to expand...
Click to collapse
This is not stock rom. I see some modifications, clock in middle and battery. Try this on 100% stock rom.
I checked on my Collegues Phone and his also shows up with +1 ...
Yep, both are Stock ROM.
I remember in S3, when Likewise ROM for 4.4.2 was introduced using Sprint ROM, it had same issue and Lemonboi did some fix in the ROM.
norbarb said:
This is not stock rom. I see some modifications, clock in middle and battery. Try this on 100% stock rom.
Click to expand...
Click to collapse
this is OA1 and it is stock except for my personal modifications and i can gaurentee you nothing in incallui or contacts has been touched and even before i made any mods whatsoever it still worked correctly.
cstayton said:
this is OA1 and it is stock except for my personal modifications and i can gaurentee you nothing in incallui or contacts has been touched and even before i made any mods whatsoever it still worked correctly.
Click to expand...
Click to collapse
Something must be off since on my 4 phones i got same thing. You are running Samsung Galaxy S5 SM-G900A Root KoolKit ROM. This maybe modify xlm for log display or contacts. I also check with two of my friends on bone stock on S5 4.4.4 OA1 and they have +1 on all incoming calls. BTW on your picture you show me dialed numbers (outgoing calls) not received calls. Received call will have green arrow.
norbarb said:
Something must be off since on my 4 phones i got same thing. You are running Samsung Galaxy S5 SM-G900A Root KoolKit ROM. This maybe modify xlm for log display or contacts. I also check with two of my friends on bone stock on S5 4.4.4 OA1 and they have +1 on all incoming calls. BTW on your picture you show me dialed numbers (outgoing calls) not received calls. Received call will have green arrow.
Click to expand...
Click to collapse
look I'm the DEV of the koolkit and Unity ROM's I am also the DEV that did the mods for my personal ROM that I'm running, I know exactly what mods have been done and what they do. NOTHING and I mean NOTHING was done to modify contacts or incallui. I just scrolled down and checked the incoming calls and those are correct as well displaying as (xxx) xxx-xxxx
cstayton said:
look I'm the DEV of the koolkit and Unity ROM's I am also the DEV that did the mods for my personal ROM that I'm running, I know exactly what mods have been done and what they do. NOTHING and I mean NOTHING was done to modify contacts or incallui. I just scrolled down and checked the incoming calls and those are correct as well displaying as (xxx) xxx-xxxx
Click to expand...
Click to collapse
Then you must be special...
Clicking from notecable N910A
sakdroid said:
I checked on my Collegues Phone and his also shows up with +1 ...
Yep, both are Stock ROM.
I remember in S3, when Likewise ROM for 4.4.2 was introduced using Sprint ROM, it had same issue and Lemonboi did some fix in the ROM.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2777482
Guess it was smart of me making this thread for the issue when it happened since I was a developer on that rom. As far as actually fixing the issue it wasn't fixed until I rebased the rom to ATT that it worked properly.
@norbarb Shame on you @cstayton is only trying to help. This can be chalked up to another blunder by AT&T in a update we shouldn't of gotten this late anyway.
talkingmonkeys said:
http://forum.xda-developers.com/showthread.php?t=2777482
Guess it was smart of me making this thread for the issue when it happened since I was a developer on that rom. As far as actually fixing the issue it wasn't fixed until I rebased the rom to ATT that it worked properly.
@norbarb Shame on you @cstayton is only trying to help. This can be chalked up to another blunder by AT&T in a update we shouldn't of gotten this late anyway.
Click to expand...
Click to collapse
Really... Why don't you read whole thread, and then judge. Seems like i was correct he is not on 100% stock that why he have no +1 in from of number.. Good day sir.
norbarb said:
Really... Why don't you read whole thread, and then judge. Seems like i was correct he is not on 100% stock that why he have no +1 in from of number.. Good day sir.
Click to expand...
Click to collapse
I wouldn't of commented on it if I hadn't read everything and had something else to add to this thread besides that. Which I did giving the OP the fix that we used on the S3 in the past that he mentioned.
You're just taking this off topic arguing about what he is running. He may have done something else to fix it that he wasn't aware of. Assuming what he is running and the way that you handled it comes off very rudely. There is no point in arguing this though so be done with it and provide him some information to help figure out why theres a difference instead of just proving him wrong and coming off the way that you are. I only judged because it appeared to come off to him that way as well.
I'm also going to throw out my hypothesis here that those of you with the +1 have taken the forced ota instead of updating to it using muniz's root thread in a non ota way? I haven't touched this update and don't plan to but I'm glad I read through this thread because I did have a method to fix this to add.
talkingmonkeys said:
I wouldn't of commented on it if I hadn't read everything and had something else to add to this thread besides that. Which I did giving the OP the fix that we used on the S3 in the past that he mentioned.
You're just taking this off topic arguing about what he is running. He may have done something else to fix it that he wasn't aware of. Assuming what he is running and the way that you handled it comes off very rudely. There is no point in arguing this though so be done with it and provide him some information to help figure out why theres a difference instead of just proving him wrong and coming off the way that you are. I only judged because it appeared to come off to him that way as well.
I'm also going to throw out my hypothesis here that those of you with the +1 have taken the forced ota instead of updating to it using muniz's root thread in a non ota way? I haven't touched this update and don't plan to but I'm glad I read through this thread because I did have a method to fix this to add.
Click to expand...
Click to collapse
Glad there is a fix, but all in all this wasn't an issue I have seen in the past so was at a loss as to why it was happening. And as a side note the rom I'm running is my personal build based of of muniz_ri sys dump. And the only modifications was to add 3minit battery and center the clock as well as deodexed, outside of that I made no changes.
P.S. building off of a system dump presents many different hurdles some mods don't work at all others have to be put together peicemeal. That is the biggest reason I wouldn't post a unity rom on 4.4.4
All things said and done I'm glad he's working now thanks for the heads up on the fix.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
talkingmonkeys said:
I wouldn't of commented on it if I hadn't read everything and had something else to add to this thread besides that. Which I did giving the OP the fix that we used on the S3 in the past that he mentioned.
You're just taking this off topic arguing about what he is running. He may have done something else to fix it that he wasn't aware of. Assuming what he is running and the way that you handled it comes off very rudely. There is no point in arguing this though so be done with it and provide him some information to help figure out why theres a difference instead of just proving him wrong and coming off the way that you are. I only judged because it appeared to come off to him that way as well.
I'm also going to throw out my hypothesis here that those of you with the +1 have taken the forced ota instead of updating to it using muniz's root thread in a non ota way? I haven't touched this update and don't plan to but I'm glad I read through this thread because I did have a method to fix this to add.
Click to expand...
Click to collapse
Whatever. ...
Used muniz's rooted OA1 here. On all incoming calls there +1. All out going calls are fine. Was wondering if one xposed apps had caused it.
XRange said:
Used muniz's rooted OA1 here. On all incoming calls there +1. All out going calls are fine. Was wondering if one xposed apps had caused it.
Click to expand...
Click to collapse
This is all related to VoLTE. If you have rom with out VoLTE you will not have +1 on incoming calls.
Making notes from Note 4
norbarb said:
This is all related to VoLTE. If you have rom with out VoLTE you will not have +1 on incoming calls.
Making notes from Note 4
Click to expand...
Click to collapse
I "#" out two lines in build.prop for VoLTE
but incoming calls still +1. It's no big deal.
Least it was something to try.
Thanks @norbarb
It seems VoLTE with T-Mobile US has broken on the 3T. Calls will come in as non-HD and SMS will not send with it enabled. Multiple confirmed reports on both 3.5.3 and 3.5.4.
Anyone experiencing this issue?
If so, please post here and in the bug thread: https://forums.oneplus.net/threads/volte-does-not-work.480271/
Additional discussion: https://www.reddit.com/r/oneplus/comments/5jdlz3/volte_breaks_sms_on_tmobile_us_3t/
edit: 8:10PM EST The issue is resolved for me!
lonequid said:
It seems VoLTE with T-Mobile US has broken on the 3T. Calls will come in as non-HD and SMS will not send with it enabled. Multiple confirmed reports on both 3.5.3 and 3.5.4.
Anyone experiencing this issue?
If so, please post here and in the bug thread: https://forums.oneplus.net/threads/volte-does-not-work.480271/
Additional discussion: https://www.reddit.com/r/oneplus/comments/5jdlz3/volte_breaks_sms_on_tmobile_us_3t/
Click to expand...
Click to collapse
I can confirm that this morning I was unable to send an SMS.. came here to look for threads.. disabled VoLTE and SMS sent just fine..
yup.. same issues here...
Same issue. Worked fine last night, this morning it's down. So many T-Mobile issues, starting to have some buyers regret (not remorse).
I'm on T-Mobile and having the same issue, I even factory reset but it wasn't fixed ??. I'm kind've glad I'm not the only one going through this. It started this morning at 9.20am to be exact.
It seems the issue is happening to those on the Axon 7/Nextbit Robin as well. T-Mobile must have changed something on their end.
https://www.reddit.com/r/tmobile/comments/5jdl90/can_receive_texts_but_not_send_them/
i had this issue this morning in NYC on tmobile. i went into airplane mode and out, and it resolved the issue. issue resurfaced later, but then enabled airplane mode again and issue went away. haven't had the issue since. think maybe some kind of upgrades being performed.
i'm able to send with voLTE on, voWIFI on, voLTE/voLTE off, and wifi enabled.
kramer987 said:
i had this issue this morning in NYC on tmobile. i went into airplane mode and out, and it resolved the issue. issue resurfaced later, but then enabled airplane mode again and issue went away. haven't had the issue since. think maybe some kind of upgrades being performed.
i'm able to send with voLTE on, voWIFI on, voLTE/voLTE off, and wifi enabled.
Click to expand...
Click to collapse
Im in Texas and airplane mode did nothing.. Still a problem.. Even rebooted the phone and still there.. With VoLTE activated, cannot send text messages. when placing a call it drops down to 3g to place.. VoLTE deactivated, i can send text message and calls seems normal.
Same issue, however turning off VoLTE FIXED the issue. Thanks. XDA.
same issue here, called T-Mobile and was told everything is fine on their end, they did create a support ticket, will see what happens.
OnePlus support useless as most of the time.
Anyone else call T-mobile? Everyone should call so they are aware of it?
---------- Post added at 12:08 PM ---------- Previous post was at 11:39 AM ----------
lonequid said:
It seems the issue is happening to those on the Axon 7/Nextbit Robin as well. T-Mobile must have changed something on their end.
https://www.reddit.com/r/tmobile/comments/5jdl90/can_receive_texts_but_not_send_them/
Click to expand...
Click to collapse
I wonder if T-mobile decided to kick out all unlocked phones from the VoLTE party....
vince1228 said:
Same issue, however turning off VoLTE FIXED the issue. Thanks. XDA.
Click to expand...
Click to collapse
Thought if fixed but it only lets me send texts. I can't. Make calls.
yea i spoke too soon. so basically if voLTE is on, i cannot send SMS. when i try to call, it falls back to H+.
with voLTE off, everything works as expected.
There IS an issue but it is on T-Mobile's end. Check out this website: http://downdetector.com/status/t-mobile.
B4oE said:
There IS an issue but it is on T-Mobile's end. Check out this website: http://downdetector.com/status/t-mobile.
Click to expand...
Click to collapse
There will always be a handful of users reporting issues; that doesn't look abnormal to me.
Yeah can't send SMS with VoLTE on. It had been working up until this morning so it's something with T-Mo. Hopefully it's temporary and they're not disabling VoLTE for unlocked phones permanently but that seems like a move they would do...
Edit: Have to turn off VoWiFi too to get any SMS to send. Well this is kinda bull**** now
lonequid said:
It seems VoLTE with T-Mobile US has broken on the 3T. Calls will come in as non-HD and SMS will not send with it enabled. Multiple confirmed reports on both 3.5.3 and 3.5.4.
Anyone experiencing this issue?
If so, please post here and in the bug thread: https://forums.oneplus.net/threads/volte-does-not-work.480271/
Additional discussion: https://www.reddit.com/r/oneplus/comments/5jdlz3/volte_breaks_sms_on_tmobile_us_3t/
Click to expand...
Click to collapse
Found this by Googling. This is not confined to the One Plus 3T. I have the Axon 7 and can't SMS while LTE is active, and phone calls drop out of LTE. I've also seen the Nextbit people having the same problem.
Same issue here. Same solution of turning off VoLTE. Hope T-Mobile isn't taking this away permanently...
only Unlocked "Chinese" phones are having the issue, OnePlus, ZTE, Nextbit etc.... all these Chinese companies probably didn't go though approval process, just figured out how to go around it.
Unlocked Motorola is fine....
Just curious.. has anyone heard from OnePlus yet or has T-Mobile say anything? I threw a pm to crystal z but doubt she will respond until middle of the night...
Sent from my ONEPLUS A3000 using Tapatalk
djr4x4 said:
Just curious.. has anyone heard from OnePlus yet or has T-Mobile say anything? I threw a pm to crystal z but doubt she will respond until middle of the night...
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Oneplus tech support is pretty much useless, they just say is T-mobile, and wait.
T-mobile says nothing wrong with their network....
so both companies just pointing fingers at each other.
I bought this Note 8 (SM-N950F) in Amazon.
Sometimes when people call me I dont receive the calls nor notifications...they go directly to voicemail.
I'm in US using the same T-Mobile SIM that I've used with my two previous phones (they worked perfectly).
I'm aware that this is not a US model but I'm able to make calls and receive many calls, I can use 4G too with no conectivity issue.
But sometimes I dont receive calls and that worries me because that'd be a big deal in case of an emergency :/
I've searched on the web but have found no solutions. I will really appreciate your help guys
el4nimal said:
I bought this Note 8 (SM-N950F) in Amazon.
Sometimes when people call me I dont receive the calls nor notifications...they go directly to voicemail.
I'm in US using the same T-Mobile SIM that I've used with my two previous phones (they worked perfectly).
I'm aware that this is not a US model but I'm able to make calls and receive many calls, I can use 4G too with no conectivity issue.
But sometimes I dont receive calls and that worries me because that'd be a big deal in case of an emergency :/
I've searched on the web but have found no solutions. I will really appreciate your help guys
Click to expand...
Click to collapse
Same thing happens to me i have the Duos Taiwan version using Tmobile
recepo1 said:
Same thing happens to me i have the Duos Taiwan version using Tmobile
Click to expand...
Click to collapse
Have you found a solution?
It happens with SMS too, I can send but sometimes I can't receive them.
I spoke with T-Mobile, tech support...they did something to the SIM, I hope it works now
el4nimal said:
Have you found a solution?
It happens with SMS too, I can send but sometimes I can't receive them.
I spoke with T-Mobile, tech support...they did something to the SIM, I hope it works now
Click to expand...
Click to collapse
Nope no solution let me know how it works what did you tell Tmobile? I will call and try as well
recepo1 said:
Nope no solution let me know how it works what did you tell Tmobile? I will call and try as well
Click to expand...
Click to collapse
I explained them the problem I just posted, I think they refreshed the SIM.
Now it's worse, I cant even make calls or received...not even to the voicemail
el4nimal said:
I explained them the problem I just posted, I think they refreshed the SIM.
Now it's worse, I cant even make calls or received...not even to the voicemail
Click to expand...
Click to collapse
Wow i dont know if its certain apn settings for Tmobile that needs to be changed.
recepo1 said:
Wow i dont know if its certain apn settings for Tmobile that needs to be changed.
Click to expand...
Click to collapse
You can just search "tmobile apn setting for [your phone]" on google and it should appear. I found mine and I did it but still cant make or receive any calls. I think they messed up my SIM, Im trying to figure out how can i contact them cause i cant even call them.
I will keep you updated with any solution or idea
recepo1 said:
Wow i dont know if its certain apn settings for Tmobile that needs to be changed.
Click to expand...
Click to collapse
I still have the same problem. Have you found something?
I'm able to make calls any time, and receives calls sometimes...but I recently noticed that when I'm not receiving calls, I just make a call and instantly I'm able to receive calls...so, I'm pretty sure it has to do with the phone app going to sleep.
el4nimal said:
I still have the same problem. Have you found something?
I'm able to make calls any time, and receives calls sometimes...but I recently noticed that when I'm not receiving calls, I just make a call and instantly I'm able to receive calls...so, I'm pretty sure it has to do with the phone app going to sleep.
Click to expand...
Click to collapse
No i still am not receiving calls at times where a voicemail just pops up with my phone never ringing. Talked to a friend he is experiencing the same issues. Im going to Tmobile to see if a new sim card will help
recepo1 said:
No i still am not receiving calls at times where a voicemail just pops up with my phone never ringing. Talked to a friend he is experiencing the same issues. Im going to Tmobile to see if a new sim card will help
Click to expand...
Click to collapse
I went to TMobile and I got a new SIM too....still the same issue. But let me know if it works for you anyways.
Like I said, I'm sure that what's causing the issue, is the "phone" app simply hibernating, but I don't know specifically what's the name.
If anyone here could let me know what's the name of the app that controls the cellular activity, would be great
el4nimal said:
I went to TMobile and I got a new SIM too....still the same issue. But let me know if it works for you anyways.
Like I said, I'm sure that what's causing the issue, is the "phone" app simply hibernating, but I don't know specifically what's the name.
If anyone here could let me know what's the name of the app that controls the cellular activity, would be great
Click to expand...
Click to collapse
Wow thanks for letting me know i will try to look into that toi
I decided to load the pie beta (csa7) to test it and see what it's like since so many people say they don't like it. The only thing I can't get to work is making the volte work like I did with oreo using shortcut Master or quick shortcut maker.
Has anyone that's been using it already been and to get it to work? Currently the only thing that would my gf and I from updating
my_handle said:
I decided to load the pie beta (csa7) to test it and see what it's like since so many people say they don't like it. The only thing I can't get to work is making the volte work like I did with oreo using shortcut Master or quick shortcut maker.
Has anyone that's been using it already been and to get it to work? Currently the only thing that would my gf and I from updating
Click to expand...
Click to collapse
did you ever figure it out, I am experiencing the same issue, my wife has the iPhone XS which allows her to activate Voice and Data over LTE.
nickscap said:
did you ever figure it out, I am experiencing the same issue, my wife has the iPhone XS which allows her to activate Voice and Data over LTE.
Click to expand...
Click to collapse
The closest we have is answering a call on wifi then turning off wifi and having VoLTE. But having actual VoLTE no sprint changed it disabled the system enough that our workaround doesn't work any longer.
Hello guys, I need someone, who can check something for me.
I'm using Redmi Note 10 Pro with MIUI 13.0.10, Android 12, EEA region (with Google Dialer). I'm bothered, because every time I answer incoming call, there is a "call forwarded" arrow before phone number on a call screen. Basically, earlier I saw it only, when I was calling someone and I was redirected to his voicemail. I'm attaching two screenshots - one is incoming call (with arrow), and the second is outgoing call (without arrow). Maybe I'm getting a little bit paranoid, but I would love to know that it is something new in Google Dialer and everyone now sees this arrow and I'm not being wiretapped by someone. My Google Dialer version is the latest version from Google Play - 87.0.468061598.
I would really appreciate if anyone can check it for me.
Hi! I've notice the same issue today, only during incomings answer. Have you found any info about It?
In my case is a Mi 11 Lite 5G, MIUI 13.0.9, Android 12
meilann said:
Hi! I've notice the same issue today, only during incomings answer. Have you found any info about It?
In my case is a Mi 11 Lite 5G, MIUI 13.0.9, Android 12
Click to expand...
Click to collapse
Thank you very much for your response, I'm glad I'm not the only one Well, since there are two of us, we can assume that it is either a feature or a bug of a new version of Google dialer or MIUI 13. Or we both are being wiretapped BTW, what is your country and your service provider? Poland/PLAY here.
Gleniu said:
Thank you very much for your response, I'm glad I'm not the only one Well, since there are two of us, we can assume that it is either a feature or a bug of a new version of Google dialer or MIUI 13. Or we both are being wiretapped BTW, what is your country and your service provider? Poland/PLAY here.
Click to expand...
Click to collapse
Spain/DIGI here.
I hope is a MIUI 13 bug. On my husband's phone, with same mobile and provider doesn't appear but it is still in MIUI 12.
Maybe we both are person of interest
meilann said:
Spain/DIGI here.
I hope is a MIUI 13 bug. On my husband's phone, with same mobile and provider doesn't appear but it is still in MIUI 12.
Maybe we both are person of interest
Click to expand...
Click to collapse
Maybe, who knows... One more thing - is your phone rooted? Do you use any call recording software by any chance? Because I'm using Call Recorder by SKVALEX, maybe it is related. Oh, and one more thing - I started to notice it just after updating to MIUI 13 / A12. In MIUI 12.5 / A11 it wasn't present.
Gleniu said:
Maybe, who knows... One more thing - is your phone rooted? Do you use any call recording software by any chance? Because I'm using Call Recorder by SKVALEX, maybe it is related. Oh, and one more thing - I started to notice it just after updating to MIUI 13 / A12. In MIUI 12.5 / A11 it wasn't present.
Click to expand...
Click to collapse
Nope, I haven't rooted phone. I use the Google Dialer from factory and haven't installed any Call Recorded. I would swear It happens since yesterday or maybe three days ago, al least I haven't notice before. But I update to MIUI 13 a few weeks (or maybe a month) ago. As I said, on another phone with MIUI 12 doesn't appeared. Idk if there has been a second upgrade in MIUI 13 this week or something.
I was worried about charges on the bill but apparently the forwarding call is inactive.
meilann said:
Nope, I haven't rooted phone. I use the Google Dialer from factory and haven't installed any Call Recorded. I would swear It happens since yesterday or maybe three days ago, al least I haven't notice before. But I update to MIUI 13 a few weeks (or maybe a month) ago. As I said, on another phone with MIUI 12 doesn't appeared. Idk if there has been a second upgrade in MIUI 13 this week or something.
I was worried about charges on the bill but apparently the forwarding call is inactive.
Click to expand...
Click to collapse
Yup, my billing looks OK as well. There was an update to a new main version of Google Phone (v86 -> v87) recently. I don't know the exact date, but it was about 20th August. New features like this are mostly released with the main version update, so maybe that's the case. Maybe update on your phone didn't installed instantly, but after some days? And the second question is - why does the same Google Phone version look different on exactly the same version of app, but on different phone? Maybe it's also Android 12 related.
Gleniu said:
Yup, my billing looks OK as well. There was an update to a new main version of Google Phone (v86 -> v87) recently. I don't know the exact date, but it was about 20th August. New features like this are mostly released with the main version update, so maybe that's the case. Maybe update on your phone didn't installed instantly, but after some days? And the second question is - why does the same Google Phone version look different on exactly the same version of app, but on different phone? Maybe it's also Android 12 related.
Click to expand...
Click to collapse
I think I fixed it but no idea why it was happening xD I downgraded the Google Dialer version (actually wanted to uninstall it but only got the old version from the Play Store) and now the arrow is gone.
Maybe it's just a bug after all.
meilann said:
I think I fixed it but no idea why it was happening xD I downgraded the Google Dialer version (actually wanted to uninstall it but only got the old version from the Play Store) and now the arrow is gone.
Maybe it's just a bug after all.
Click to expand...
Click to collapse
I was going to try the Google Dialer downgrade as well when I have some time, so thank you very much for reporting back, now I don't have to do it myself Well, then we can assume that it is not a bug, but a new feature - pretty cool if you ask me - but now they have to change "call forwarded" icon to something else, so people don't get confused. Have a nice evening!