Outgoing call waiting notification - Xiaomi Mi A1 Questions & Answers

Is outgoing call waiting notification not working in all custom ROMs? Cause it was working normally in stock Rom
For example if you called someone and that one have a phone call, you have a notification that the person you are calling is having a call

I've the reverse issue
From the 2 SIM's, one is always unable to knock in notify.
For a SIM which you use data also, the call knock in notify is possible. But for the other SIM which is only phone, it's grayed out, unable to set the knock in notify.

CommandAir said:
I've the reverse issue
From the 2 SIM's, one is always unable to knock in notify.
For a SIM which you use data also, the call knock in notify is possible. But for the other SIM which is only phone, it's grayed out, unable to set the knock in notify.
Click to expand...
Click to collapse
It is not working with me at all

Ahmed.ragab said:
It is not working with me at all
Click to expand...
Click to collapse
Try the following:
1. Install the latest RRemix ROM(0327)
2. Disable VoLTE
After a several reboots, it seems to me that in the GSM setting now it's possible to set the Call Waiting. It doesn't thow error messages now.
(I'm using this ROM since a few hrs only, but looks stable, even the GSM settings too)

Related

Call Forwarding Icon in Task Bar...ARGHHHH

how do i get rid of it, everytime i restart the phone, it comes back...its pissing me offfff LMAOOO HAHA....please anyone...help meeee
Did you ever figure this out?
I'm having this problem too since the latest rom upgrade. Seen a few others with the same problem after upgrading as well. I'm using ATT US X1a rom1.03.948.8.
I've tried a hard reset, swapping the sim out (as mentioned in another thread), using forwarding cancel codes (##62#), and obviously the normal call forwarding settings on the phone. It clears up the problem for a few soft resets, then it comes right back again.
call forwarding..
you seem to have call forwarding turned on.
Phone - Menu - Settings - services - call forwarding - get settings
there you will have all these type of settings like forward to number with no answer and also forward all calls.. just uncheck them all i guess.
Thanks
daniel
In NAM on AT&T, call forwarding is always turned on for something. Normally, it's turned on only for no answer and unreachable.
The phone should not show the call forwarding icon when these are the only services activated.
I don't understand how or why it happens, but I will occasionally get the call forward icon showing when I have nothing special turned on.
It will eventually go away, usually after I've had to power the device for some reason. Note, however, that it will not necessarily go away if I power the device to the specific purpose of removing the call forwarding icon.
I've never figured out what makes it show or why it goes away.
Lucky for me, I'm not too troubled by it.
Hmm
I think this problem is carrier related, (carriers have control over your call forwarding) because I have had this problem on many different phones from different manufacturers over the years. Not on my Xperia yet though.
Thanks for the replies. As stated in the earlier post, I have already tried unchecking, rechecking etc. As soon as it connects to the network it goes away. It seems to be an issue with the newest rom though as the previous rom does not have this issue at all (for me at least).
Call forwarding is definitely on the carrier side, but as soon as the phone connects to the network to pull call forward settings, it will always change the icon to the correct status (ie icon is there when forward all calls is on and not when it's not), which tells me that it's probably an issue with the rom, not the carrier. You're right about the settings George, but unfortunately I do use call forwarding from time to time and need to know when its truly on or off .
I've tried tweaking the cf values in the registry as well at hklm\software\htc\phone without any luck.
The call forwarding icon is also showing on my X1 I am on Orange UK.
I guess it can't be fixed.
Guys in US with AT&T.
I've got this issue that might be stupid but I suffer from it really bad. Everytime I get a new voice message, a text comes in with weired notes (which I know is for the phone to notify me) but I have to delete the sucker everytime. Or everytime I am in the voice box, it sends me another txt for deletion/
How can I get rid of this?
Do you guys have a good visual voice message system installed?
AT&T doesn't support any other phones except what they sell. AHhh
Thank you all.
Oddly enough my problem went away. I still think it's a ROM issue. I was playing with some other roms and eventually ended up flashing back to NAM R2AA008 (1.03.948.8). Restored my old config with full SPB backup and I haven't had the problem since.
I'm guessing that "if" it was a settings issue, the backup would've just recreated the issue. Plus hard resets didn't make the problem go away either. I even tried changing to a new sim as some people tried in other posts. But completely reflashing the rom seems to have done the trick for me at least.
The only difference that I can see is that I did the first update through SEUS. All the other flashes were done the old fashioned way. Not saying this would work for others, but it's been gone for weeks now for me.
Solution
Dial ##21# on the X1.
The "Call Forwarding" icon will disappear on the top bar of your X1. But, it won't affect your call fwd settings in the operator's mobile system.
P.S. I mean it won't change the call fwd settings defined by operator in the mobile system, e.g. no answer and the call will be directed to voice mail system.
##21# is the function code to cancel call fwd setup by your phone. If you did setup some call fwd scenarios on your phone, the call fwd icon will be displayed as an indicator for call forward is active.
For the purpose of just get rid of the icon right after power on or soft reset the phone, I think it is a simple solution.
minglee said:
Dial ##21# on the X1.
The "Call Forwarding" icon will disappear on the top bar of your X1. But, it won't affect your call fwd settings in the operator's mobile system.
Click to expand...
Click to collapse
I think most of the people having this problem on the thread are referring to a strange bug that seems to be affecting a small percentage of users. I've seen the same problem posted on a few other sites/threads as well. It doesn't really have to do with call forwarding being on at all, it's just that the icon is there. Using the forward codes or forcing an update will make it go away temporarily, but for me it kept eventually coming back no matter what I did. When my phone had the problem, I tried 21, 69, 67, 61. None of them made the issue go away permanently.
My X1 has this kind of problem as well. It is the problem from X1 itself, maybe the X1 can not log into the 2G or 3G network very well.
Nimche said:
Guys in US with AT&T.
I've got this issue that might be stupid but I suffer from it really bad. Everytime I get a new voice message, a text comes in ....
Click to expand...
Click to collapse
Whoa. LOL... I haven't seen this since the old Synergy Motorola days when we were all fascinated with foreign firmware.
I do not have this issue with the generic NAM or generic UK ROM in their latest iterations.
I guess the first thing anybody would normally suggest is to make sure you're on one of these ROM.
elite-fusion said:
how do i get rid of it, everytime i restart the phone, it comes back...its pissing me offfff LMAOOO HAHA....please anyone...help meeee
Click to expand...
Click to collapse
This is a carrier related issues. Some carrier has 2G and 3G network that if the area is not covered by 3G network, Internal using forward to their own 2G network in order to let the phone work. It happen not just on the X1, It happen on all other WM base phone I have before. However, if your carrier has only a single network whether it is 2G or 3G. This forward logo will go away. Good example. the 3 mobile Network in Hong Kong has 2G and 3G separate and on my X1, which use the 3 mobile has the forward logo all the time but on my Touch HD, I use the Smartone network which have a combine 2G and 3G network and you never see the forward logo.
Just so you know, same problem here.
The solution? I heop someone makes a pretty version for the "Call forwarding" icon haha.
With the help of Bxsteez I have fixed this issue with the R2 rom always doing this...
WC
Since the last firmware update, I have the same icon showing up.
But there is a cure at least for US AT&T.........
Like it has been said before go to phone setting
Select Call Forwarding and hit the get setting button...
Once it retrieves the setting from AT&T net, the icon goes Bye-Bye!!
I have to do this every hard-reset or complete power down...
This what works for me...
Stuart
scl_electronics said:
Since the last firmware update, I have the same icon showing up.
But there is a cure at least for US AT&T.........
Like it has been said before go to phone setting
Select Call Forwarding and hit the get setting button...
Once it retrieves the setting from AT&T net, the icon goes Bye-Bye!!
I have to do this every hard-reset or complete power down...
This what works for me...
Stuart
Click to expand...
Click to collapse
Same here for T-mobile
Same problem on my X1 and I am using HK 3 network..

Dialer won't allow SIP calls (claims "call barring" is on)

I'm trying to use the Nexus 6P's native dialer to make calls through my SIP provider. I have a configuration that works perfectly on the Nexus 5X and older 6 (shamu). I entered all my information in Dialer > Calls > Calling accounts > SIP accounts, and then enabled the account under ... > Calling accounts > All calling accounts. However, whenever I attempt to make a call through my SIP provider on the 6P, a message pops up saying "Can't make outgoing calls while call barring is on." Does anyone have an idea what might be causing this? Note that:
I can make regular phone calls from my mobile number just fine, tested with both a Verizon and a T-mobile SIM. However, the SIP call barring problem persists regardless of which SIM is in the phone.
I can make SIP calls using other apps, like CSIPSimple, so it's not a port blocking issue.
I can receive incoming SIP calls (to my DID number) just fine when enabling ... > Calling accounts > Receiving incoming calls, so clearly I didn't mistype my SIP account password. (I visually checked that all the other settings are identical between my 5x and 6P.)
I'm definitely on WiFi when I experience the problem. To be extra sure, I even tried it with airplane mode and WiFi both on, which is fine for CSIPSimple or incoming calls but still doesn't work for outgoing calls with the android dialer.
The message pops up instantly, making it seem like a setting on the phone rather than a response to network messages.
For what it's worth, I'm running build MMB29M (android 6.0.1). My phone is unlocked but not rooted. (I can still get root access to /data by booting TWRP, but have never mounted my system partition read-write.) The one thing it might be is that I put a Verizon SIM in my Nexus 6P when first booting it, whereas my other phones were all first booted with a T-mobile SIM. I think that caused some VZW apps to be installed that I since removed; perhaps it messed up other settings. I'm a bit reluctant to wipe my phone and try again, but will do it if people think it's the only solution.
Thanks.
My 6P won't allow the SIP account. Gives me an error every time I try to set it up.
skinnytoo2 said:
My 6P won't allow the SIP account. Gives me an error every time I try to set it up.
Click to expand...
Click to collapse
Do you have Verizon, or a different carrier?
15xda said:
Do you have Verizon, or a different carrier?
Click to expand...
Click to collapse
Yup Verizon
Sent from my HUAWEI NXT-AL10 using Tapatalk
Tmobile
I experience the same problem on a Nexus 5X with Android 6.0.1 SIP calls only exhibit this problem when the SIP username looks like a 10 digit phone number. All other outgoing SIP calls work correctly.
mndrix said:
I experience the same problem on a Nexus 5X with Android 6.0.1 SIP calls only exhibit this problem when the SIP username looks like a 10 digit phone number. All other outgoing SIP calls work correctly.
Click to expand...
Click to collapse
I am having this same exact issue on a Nexus 5X using Cricket. Anyone come up with a solution?
SOLVED
Okay, I finally broke down and wiped my Nexus 6p, flashing the latest google ROM with fastboot -w. This time I booted it with a T-mobile SIM for the first time. Lo and behold, outgoing SIP calls started working again.
This is super nasty behavior, because merely switching the SIM and even reflashing without -w did not solve the problem. The mere act of having a Verizon SIM in your phone the first time you boot it ends up crippling the SIP feature. On the plus side, it will probably continue to work even if I pop the Verizon SIM back in.
So now I'm going to lose an hour redoing all my settings on my wiped phone, but I'm super happy to have SIP working again.

[no call waiting] [need solution]

Hi friends, My friends use Asus Zenfone max pro M1
They are facing a error that when they are in a call 'The Call Waiting' feature is not working .
They searched for it in settings menu and no such option to ON/OFF CALL WAITING is found.
On the other end when someone calls them while on a call with some other person they are not notified of the incoming call that is under waiting.
Please suggest a solution if found any, Thank You
I am using ASUS ZENFONE 5Z and i have that feature in call settings
No call waiting
Same here no call waiting on stock rom
Mine is working fine.
For call waiting option, open google's Phone app> settings> calling accounts> choose your SIM provider> GSM call settings> Additional settings
apd55 said:
Mine is working fine.
For call waiting option, open google's Phone app> settings> calling accounts> choose your SIM provider> GSM call settings> Additional settings
Click to expand...
Click to collapse
For me Call waiting option is there and it is turned on but still no incoming calls notification while i am on a call
amity902 said:
For me Call waiting option is there and it is turned on but still no incoming calls notification while i am on a call
Click to expand...
Click to collapse
Check app notifications or try booting your phone into safe mode.
4G volte networks on vodafone don't support call waiting.
Turn off volte and take calls call waiting and conferencing all would work smoothly.
Same prob . Call waiting is enabled but not working. Can any one tried to use custom rom in thus phone and solved this issue or no.
Anyone found the solution for the problem? I am facing same problem with my max pro m2 with airtel or jio (both on volte).

GSI LTE Fix

I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Any chance it solves LTE problems with stock OS as well?
Renovatio33 said:
Any chance it solves LTE problems with stock OS as well?
Click to expand...
Click to collapse
IDK about what problems your talking about, but it definitely won't as the stock OS already has the necessary ims.apk.
In my case, even after installing this, (I use verizon) it won't even detect the sim no matter what rom I use...
CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
So are you able to receive text messages on LTE now?
Tredah212 said:
So are you able to receive text messages on LTE now?
Click to expand...
Click to collapse
Yes, I'll usually have to reboot and it starts working properly
I'm using Havoc 2.9 on Verizon, and even with this app installed, I'm not receiving incoming texts. Any suggestions on what to do?
Edit: Never mind. After multiple attempts, it finally started working.
Reznor7 said:
I'm using Havoc 2.9 on Verizon, and even with this app installed, I'm not receiving incoming texts. Any suggestions on what to do?
Edit: Never mind. After multiple attempts, it finally started working.
Click to expand...
Click to collapse
Really, you got everything working on GSI on Verizon?? What steps did you use? Is Volte working?
jal3223 said:
Really, you got everything working on GSI on Verizon?? What steps did you use? Is Volte working?
Click to expand...
Click to collapse
Yup. LTE seemed a bit spotty on staying connected though, and it seemed like sometimes texts didn't come through promptly compared to stock. I installed the ims.apk and selected TD-SCDMA/CDMA/UMTS in the Phone info menu (*#*#4636#*#*). Volte worked, but again, the overall stability of the connection didn't feel quite right. Unfortunately, the lack of Bluetooth media ability pushed me back to stock again.
Does anyone have the knowledge to make a Magisk Module making these changes? It would make it much easier to switch between different builds to test.
CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
I tried this with Android Q variants and wasnt able to access Phone Info any more. Is this only intended for Pie based GSIs?
Thanks
DarkestSpawn said:
I tried this with Android Q variants and wasnt able to access Phone Info any more. Is this only intended for Pie based GSIs?
Thanks
Click to expand...
Click to collapse
I have yet to get an Android 10 rom to work on my phone AND my phone is currently out for repairs, so I haven't been able to test it for Android 10.
CalebQ42 said:
I've been messing around with GSIs and found that texting on LTE didn't work at all (at least on T-mobile). If you aren't experiencing this issue, then it's worth noting that all GSIs I've used default to 3g instead of LTE. Turns out it was a problem with VoLTE, and I found the fix!
The FIX!!
It's really easy, install the ims.apk that's attached to this post. That's it.
In case you don't trust me (which is understandable), you can compile it yourself by using this script
Click to expand...
Click to collapse
Quick Question, since you are on tmobile..
Are you able to use WiFi Calling with GSI ROM?
I am thinking of going to GSI Q ROM but need to have WiFi calling working since coverage at my home is weak.
Thanks,
RJR
My carrier just enabled VoLTE for me today and I gave it a try.
While VoLTE works on Havoc 2.9 with this apk, I couldn't properly hang up the phone call and I have to reboot the phone.
By the way, I'm also having the issue of being unable to access the Phone Information menu. Nothing happens after typing *#*#4636#*#* on the dialpad.
EDIT: Turned out I set the default dialer to something else (Emerald Dialer) and the system would refuse to send secret code from non-default dialer for security reasons. However, it appears third party dialers may not be able to handle such codes correctly as when I typed the code on Emerald Dialer, it crashed. I set the system default dealer back to the stock one and now I could enter the Phone Information menu.
However, I'm yet to figure out what might have caused VoLTE to get stuck when hanging up...
Reznor7 said:
Yup. LTE seemed a bit spotty on staying connected though, and it seemed like sometimes texts didn't come through promptly compared to stock. I installed the ims.apk and selected TD-SCDMA/CDMA/UMTS in the Phone info menu (*#*#4636#*#*). Volte worked, but again, the overall stability of the connection didn't feel quite right. Unfortunately, the lack of Bluetooth media ability pushed me back to stock again.
Click to expand...
Click to collapse
I just applied this fix on Havoc OS, and it works! However after about 2 minutes reliably, my phone changes to "No Service, Emergency Calls Only" mode. Verizon totally disappears. It appears IPv4 still passes the ping test, however IPv6 fails(2). I'm not sure how to fix this problem
GalacticGLI said:
I just applied this fix on Havoc OS, and it works! However after about 2 minutes reliably, my phone changes to "No Service, Emergency Calls Only" mode. Verizon totally disappears. It appears IPv4 still passes the ping test, however IPv6 fails(2). I'm not sure how to fix this problem
Click to expand...
Click to collapse
I could never get Verizon to work at all on any Gsi. Have you gotten it to work on 9.0 Gsi roms?
I'm running Havoc (latest Pie version)
For the first 2-3 minutes after boot, I see 'Verizon 4G' as my carrier info. After that, the signal in the status bar changes to have a little x on it, and all branding disappears. It says No Service and Emergency Calls Only.
I'm not sure what I'm doing wrong
rrusek said:
Quick Question, since you are on tmobile..
Are you able to use WiFi Calling with GSI ROM?
I am thinking of going to GSI Q ROM but need to have WiFi calling working since coverage at my home is weak.
Thanks,
RJR
Click to expand...
Click to collapse
You can see if the Tmobile DIGITS app will work on your phone. I think it basically forces WiFi calling. I'm using an Android 10 ROM and DIGITS circumvents the no-texting on 3G issue. You can also set up RCS on Messages if you change your data to 3G, reboot the phone and wait for it to finish setting up. That doesn't exactly fix the SMS issues, but it at least is a band-aid solution, combined with DIGITS will effectively solve SMS issues altogether. And again, I am not sure, but I suspect that DIGITS is WiFi calling the app, but I could be very wrong on that. You can also force WiFi calling using adb, though I don't know if that actually works yet since I have not received or placed calls since manually setting it to on. Will report back.
EDIT: Forcing WiFi calling in ADB seems to have turned it on for good. I have the WiFi calling symbol even though I have no option in Settings.
Straum said:
You can see if the Tmobile DIGITS app will work on your phone. I think it basically forces WiFi calling. I'm using an Android 10 ROM and DIGITS circumvents the no-texting on 3G issue. You can also set up RCS on Messages if you change your data to 3G, reboot the phone and wait for it to finish setting up. That doesn't exactly fix the SMS issues, but it at least is a band-aid solution, combined with DIGITS will effectively solve SMS issues altogether. And again, I am not sure, but I suspect that DIGITS is WiFi calling the app, but I could be very wrong on that. You can also force WiFi calling using adb, though I don't know if that actually works yet since I have not received or placed calls since manually setting it to on. Will report back.
EDIT: Forcing WiFi calling in ADB seems to have turned it on for good. I have the WiFi calling symbol even though I have no option in Settings.
Click to expand...
Click to collapse
Has anyone figured out the sms issue on Q gsis yet? It's the only thing holding me back, and I'd rather avoid the Digits app.
tried to install. installed. did not change anything.
edit: tested also from phone info - no IMS menu and no buttons for enable VoLTE.

Unable to call people because of "Call barring is on", which it is not! Galaxy S10

Unable to call people because of "Call barring is on", which it is not! Galaxy S10
There is nothing wrong with my sim card nor the providers of it. However I am unable to call anyone or send text messages to anyone but I am able to receive calls and text messages from anyone.
Whenever I try to call someone I get the following message "Can't make outgoing calls while call barrng is on"
What I have tried: entered phone app -> Settings -> Supplementary services -> Call barring -> Voice call. Everything is unchecked! If I check everything, nothing changes about my situation I am still unable to call people
I am on Samsung Galaxy S10 Plus
Did you contact your carrier and actually verify that they aren't blocking outgoing calls from your number?
You could also check the network settings on your phone. Verify that the APN settings are correct for your carrier. Also look at the settings for Wi-Fi Calling and Volte. If either or both are enabled turn them off and then see if you can make calls.
jhs39 said:
Did you contact your carrier and actually verify that they aren't blocking outgoing calls from your number?
You could also check the network settings on your phone. Verify that the APN settings are correct for your carrier. Also look at the settings for Wi-Fi Calling and Volte. If either or both are enabled turn them off and then see if you can make calls.
Click to expand...
Click to collapse
I have verified that they are not blocking anything from me. I have verified that the APN settings are correct now. Wi-Fi calling is off and Volte does not exist on my phone in any setting or app. I have searched everythwere for them. I still cannot make phone calls because of "call barring" which is off.
Do you have a do not disturb setting activated by mistake or possibly a Bixby Routine running that could be interfering with your calls?
Samsung throws so many pointless features into their software it's hard to know where to look.
jhs39 said:
Do you have a do not disturb setting activated by mistake or possibly a Bixby Routine running that could be interfering with your calls?
Samsung throws so many pointless features into their software it's hard to know where to look.
Click to expand...
Click to collapse
I rarely have do not disturb active and activating or deactivating it does not change the error. I have never activated Bixby Routine, so no it cannot be that. Thanks for the ideas though! Please, if you have more ideas post them
plshelpmee said:
I rarely have do not disturb active and activating or deactivating it does not change the error. I have never activated Bixby Routine, so no it cannot be that. Thanks for the ideas though! Please, if you have more ideas post them
Click to expand...
Click to collapse
Honestly i would create a smart switch backup and factory reset. If that dosent work then manually backup your important files and start fresh as smart switch might be backing up whatever file may be causing problems. You could also exclude anything phone related from the backup.
Sent from my SM-G975U1 using XDA Labs

Categories

Resources