Seems on my Note 4 (SM-N910W8) on Rogers (Canada) the blocking mode is broken. It will NOT allow incoming text notifications from my "Allowed contacts" lists. The incoming phone calls works but incoming texts are all blocked regardless of being on my allowed contacts list or not. Anyone have any idea why and how to fix it (if possible)? It is really starting to piss me off, I need to get messages from certain contacts for work but I either now don't get any or I don't use blocking mode and get disturbed by all. I know their are apps out there to do this but I tried that and I preferred Samsungs blocking mode on my old Galaxy S3 and am now disappointed it does not work properly on the Note 4.
Related
I was wondering if you clever devs could look into adding phone functionality to the adam 3g model ?
it should be capable and would be handy for the odd occasions with a bluetooth headset.
The early tablets and recently at ces the tablet had phone icons on the desktop so im sure its at least a possibility !!
many thanks in advance
On the Battery Use, I have seen a "Phone" process.
Maybe it is already activated, but not used
You can get to the phone section via "contacts" but when you try to make a call it says "call ended" after you hit the call button. From the FCC docs, it says that the Ericcson F3307 3G card is "voice" capable so in theory it is possible! The only thing even close to phone functionality that does work is the sending/receiving SMS messages atm.
Just a shot in the dark, but does google voice's data calling use the same process?
yes and it sucks. it only stinks that the google voice works over data and not wifi. so i cant make a call over wifi if i dont have a valid sim card in.
Hi,
I bought recently a galaxy tab for a company. I took a data plan with my operator to allow Internet browsing with it. The sole problem is : I can call with the tab but should not be able to. I called my customer service and they told me they can't desactivate the line without desactivating the data part with it (noobs!??!!). This they will bill me every call as extra communication (believe me, it makes phone calls VERY expensive). The tab will be handed to people we do not trust a lot.
So I would like to know if there is a way to prevent users to call with the tab without needing a complex operation to do it (like reinstalling the whole tab).
Thanks a lot for your help on this one...
Ok, I will respond to myself hoping it might help someone. After looking a lot into this, I found that you can do just that by going into the phone settings, calls, fixed number and by activating the feature. you can add allowed calls and it blocks every call not in the list. You set specific PIN (different from the one used to unlock the phone) to activate the feature and it will be needed to add/remove elements in the authorized list as well as to disable the feature.
It is great!
Woops, this seems to block the connexion to the 3G too. Didn't notice before because it was already connected but if you disconnect for a X or Y reason, then it won't work again... That is a shame...
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.
Problems Handling Phone Calls (Call Waiting, 3 way, etc.) Verizon S5 on AT&T Network
I recently bought a used Verizon Galaxy S5 (SM-G900V). It came with the lollipop OS. From the outset, I had problems with phone calls, text messaging.
1. When I'm in a call, I'm not able to dial (Like to enter numbers for automated systems).
*I solved this one by going to:
settings>applications>call>
Scroll down to DTMF tones and change setting to long.
2. When I'm in a call, I'm not able to click over to calls on call waiting. When I do try to click over, I still hear the original call for a few seconds and then both calls drop and I get an error message that says "no sim or invalid sim". If I don't answer the call, both calls drop and I get the same message. The same thing happens if a try to make a 3 way call.
3. If someone calls me and I try to call them back, the call redirects to turn it into an international call and the call doesn't go through.
*I solved this using an app called prefixer
4. If I try to text message someone who called me, I get an error message back saying the phone number is invalid.
I figured I would have to root my phone to be able to make some custom changes. I first had to downgrade to kitkat (android 4.4.2) and root it and then upgrade with root using some very helpful posts and resources found on this site (thanks). When I downgraded, problems 1 and 2 went away (for number 1, I had to change my network mode, but that solution didn't work when I went back to lollipop). After upgrading beack to lollipop, all of these problems were there, though I was able to resolve 2 of them, the other 2 are problematic.
I think theres a problem with the way the phone is handling the AT&T network signal since they have a different type of network from verizon but i don't know. I need some help please. Has anyone encountered these kinds of problems and solved them. Thanks
Does anyone else have issues with advanced messaging? I had to call att to update my imei to even get the read receipts to work however i still cant see when someone is typing and they cant see when i am typing either. tested note 7 with wife's s7 edge. It used to work on my original note 7 but now doesnt since the exchange
Hm, silly question but I assume you checked. Are both settings enabled in your message settings? Mine works fine.
I disabled mine as it is messing up with Tasker's text message receive events.
I'm having a different issue...
My "Use Advanced Messaging" checkbox isngrayed out, but on. I can't even disable it if i wanted to. The option below it works just fine.
Sent from my SAMSUNG-SM-N930A using Tapatalk
I turned mine off. It interferes with some apps.
Problem has been solved it just requires a strong network connection to work. Only issues now are pictures being occasionally choppy which others have noted many times hopefully fixed by an update in the near future. AT&T is upgrading the towers in my area however to do so they must first downgrade them supposably