Sometimes after I reset the my phone I get the notification "restricted access change".
At first i thought it might be sim card since it is a new phone. So I switched it with my wifes and she put mine in hers. Her phone worked perfectly but when I turned mine on, It worked for a bit (sometimes does this also) then eventually stops working.
* no Texts can be sent or received and no calls can be received. If I try to call someone it stays on dialing and I can't cancel the call. (stays as if I am calling and have to reset phone)
Sometimes It doesn't show error, Just stops all of the above anyway.
Any suggestions or comments? anything would help.
Did you ever get to solve this issue? I am getting it on my T-mobile S3.
Tmobile could not solve the issue. Now sending the device to Samsung support to see any hardware issues...
cnraghu said:
Did you ever get to solve this issue? I am getting it on my T-mobile S3.
Tmobile could not solve the issue. Now sending the device to Samsung support to see any hardware issues...
Click to expand...
Click to collapse
I am getting this error too on my T-Mobile S3. Any info on this would be greatly appreciated.
EDIT:The reason I was getting this error was due to the guy I got my S3 from closed his t-mobile account without paying the ETF. Therefore my S3 now has been blocked on Tmobile network. The guy gave me a refund on the phone tho.
Related
I have a Bell atrix phone unlocked and currently on Rogers system. Once a day i get the call ended 0:00 error when attempting to make a call, or I can't receive a call. A reboot fixes the problem. Not sure if its a setting that i have in my phone, I have done a factory reset, but i still happens. Any solutions. Called motorola and i get the famous "we never heard of this problem, send your phone in for repair" line. HELP please its driving me nuts.
Same problem here but I have an AT&T Atrix on Straight Talk
i also have had this problem, at&t phone
have changed radios, roms, still have the problem.
i'm going to ask for a sim replacement, see if that works.
sanriver12 said:
i also have had this problem, at&t phone
have changed radios, roms, still have the problem.
i'm going to ask for a sim replacement, see if that works.
Click to expand...
Click to collapse
Let me know how that works for you. Getting a replacement sim from straight talk is a pain in the A$$!!!
For some reason it just started hanging up whenever i try to make a call with google voice or without...
I uninstalled and reinstalled google voice with the same issue...
Phone is working fine randomly... Still says 0:00 when I hang up after a long call. lol
Did the same thing to me on one certain phone number with Att cyanogenmod.
I remember deleting the area code off and dialing again for the fix.
Sent from my MB860 using Tapatalk 2
Just very strange when I originally made the switch to my verizon phone to AT&T it was because Verizon had no service at my work and AT&T had excellent service...
it worked beautifully for a months, always had HSPA+ with the Atrix or "3.5G" with the E71
Now i always have Edge or nothing and it's dropping calls like crazy and doing this 0:00 thing...
Going to swap over to a new sim as well and see what happens.
Just got my new sim and ported over.
Still stuck on edge with 1-3 bars where before i was always 3g-hspa+
I'll check back in the 0:00 issue after i have made some calls
My ATT HOX+ is not receiving incoming calls.
I am not sure when it started.
I rooted with Hasson's tool several days ago and I have no other problem that I know of. Not sure if rooting is responsible or not.
I can receive calls from my GF's ATT iPhone, but I get no image of her for some reason.
I do not get calls from my ATT landline (not U-verse VOIP).
I do not get calls from my mothers landline, she does have VOIP from something other than ATT.
Data, wifi, sms, mms, all seem to be fine,
Any advice is greatly welcome
joshua43214 said:
My ATT HOX+ is not receiving incoming calls.
I am not sure when it started.
I rooted with Hasson's tool several days ago and I have no other problem that I know of. Not sure if rooting is responsible or not.
I can receive calls from my GF's ATT iPhone, but I get no image of her for some reason.
I do not get calls from my ATT landline (not U-verse VOIP).
I do not get calls from my mothers landline, she does have VOIP from something other than ATT.
Data, wifi, sms, mms, all seem to be fine,
Any advice is greatly welcome
Click to expand...
Click to collapse
You could run the RUU and see if that clears up the issue. If not, then you know it is a phone or network issue.
Tried everything that seemed safe to try.
Called ATT, the nice person took me off network and back on again while I had the sim card out.
Fixed the problem with my landline not being able to call, but not my mother not being able to call.
The tech is sending my to get a new sim card on the off-chance it is the culprit, but believes that it is a network problem.
I will check back with an update later incase anyone else has a similar problem.
joshua43214 said:
Tried everything that seemed safe to try.
Called ATT, the nice person took me off network and back on again while I had the sim card out.
Fixed the problem with my landline not being able to call, but not my mother not being able to call.
The tech is sending my to get a new sim card on the off-chance it is the culprit, but believes that it is a network problem.
I will check back with an update later incase anyone else has a similar problem.
Click to expand...
Click to collapse
Keep us posted.
Sent from my HTC One X+ using Tapatalk 2
No Incoming Calls
joshua43214 said:
Tried everything that seemed safe to try.
Called ATT, the nice person took me off network and back on again while I had the sim card out.
Fixed the problem with my landline not being able to call, but not my mother not being able to call.
The tech is sending my to get a new sim card on the off-chance it is the culprit, but believes that it is a network problem.
I will check back with an update later incase anyone else has a similar problem.
Click to expand...
Click to collapse
I'm having the same problem as are others. Found this fix which might help.
http://www.andromods.com/fix-troubleshoot/fixing-htc-one-x-plus-cant-receive-calls-voicemail-problem.html
I'm experiencing this problem as well. It doesn't matter who tries to call me from what, but calls only make it through about 5% of the time, which is completely unacceptable. The calls that don't make it through won't go to voicemail. Half the time it rings endlessly, the other half it will give some message saying the call cant be completed.
When I first got the phone, I didn't switch my data plan to an LTE plan right away (Best Buy didn't require me to do so, and AT&T insisted that I had to switch to their $30/mo plan so I kept my $25/mo plan for the first few weeks). During the time I did not have an LTE data plan I experienced no issues with the phone. A few weeks back I noticed that AT&T was now giving me an option for a $25/mo LTE plan, so I switched to that. That exact day is when I started not being able to receive phone calls.
Other things I've noticed since switching to the LTE data plan:
When I make calls, I often have to try 2-3 times before I can get the call to go through. Sometimes as soon as I try to make the call, the phone beeps at me. Sometimes it will hang for a good 10 seconds before it starts to ring.
Occasionally my phone will stop recognizing the SIM card, requires reboot.
Occasionally I'll lose my data connection, requires reboot.
Text messages some times take over an hour to send/receive, sometimes this is solved by a reboot, other times not.
I went to an AT&T store, they tried switching out my SIM card, but did not help me any further because I bought the phone at Best Buy. (I wanted to argue with the rep, because I had bought my Atrix from Amazon, and the same AT&T store helped me with the problems I had with that phone). The rep fed me some garbage saying that some phone numbers just don't work with HTC phones. Fed up, I left the store.
Hello All,
I have been looking around and seeing if anyone else is experiencing the same issue I have. But I have not had much luck. I have seen similar cases, but for whatever reason, some of the workarounds found that worked for others have not been successful for myself, or are temporary.
For the past three months, I have been experiencing an off and on issue where I am unable to receive texts, but I am able to send out text. And it is something that I would not realize until people actually notify me, or it is awkwardly silent on the "texting front", which makes me second guess myself. Almost every other week or two weeks this has occurred. At the time, I am running Darky's 8.8 [4.1.2] ROM for the i9300. I have tried rebooting, taking out the SIM, re-flashing Darky and re-flashing Stock (full wipe, etc), and replacing my old SIM with a new one. None have been successful thus far. The only success I have found is that inserting my SIM in a different phones allows the text to flow through almost immediately. I would then place the SIM back in the i9300 and any new texts sent I would receive immediately. After a week or two, it randomly just stops receiving text again, and the cycle continues.
I was wondering if whether this may be a bug with the Android OS itself? I have seen a few posts in regards to SMS being handled by Jelly Bean, but I am not 100% sure if my issue would fall in the same boat. Or if it is possibly faulty hardware? Or some kind of network issue. My network is AT&T, but I'm ruling out a network issue since I am able to receive text almost instantaneously on other phones.
Any information, advice, or help would be greatly appreciated.
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
JJEgan said:
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
Click to expand...
Click to collapse
I've verified that the MMS APNs and SMS settings are correctly configured to AT&Ts network. If it were incorrect from the beginning, I would not get text messages (or MMS) at all. But in this case, it is intermittent and only resolved when I get to "unload" the text messages on to another device.
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
b-eock said:
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
Click to expand...
Click to collapse
Ahh! Thank you b-eock! I don't mean this in the wrong way, but I'm glad that I'm not the only who has experienced this. When this occurred to you, were you on some version of 4.1.2? From what I can remember, this issue never came up until I upgraded from 4.1.1 to 4.1.2. Just trying to find some kind of trend here...
I have had to call up AT&T a number of times regarding this issue. And each time they were of no help. Although they were able to confirm that everything on their end of setup correctly, I got the same BS that you got. And they even gave me the whole baloney that I should upgrade so that they can help assist me better and that since it is not their branded phone, it may not be fully compatible.
I really do not want to give up on this. And I definitely want to find a solution. So I am hoping there is a lucky one out there that has tried different ways of getting fixed. Whether that be trying a new ROM, or downgrading from Jelly Bean to ICS, etc.
Came up a few weeks after I upgraded to 4.1.2 but there isn't really a connection between that. It worked before. Its just random crap. And them telling us everything is good on their end, that's complete BS. They don't know what's going on behind their computer screen.
Same exact thing happens to me. It's ROM dependent i'm thinking. Samsung roms from other countries do it the most for me. Has done it on AT&T and AT&T with StraightTalk. Experiencing it on Purelok HD v3.1 right now. I love this rom but im probably going to go AOSP/AOKP as I don't experience it on those kind of roms.
Camera just isn't the same without the Samsung software to me.
Hi Guys,
I am hoping that someone can help me here. I recently purchased the Xperia Z Ultra (huge!) and I have noticed that it has an intermittent network loss issues. I took my SIM card from the HTC One and put it in this one and entered the Fido APN settings. 3G and H+ works fine but the phone loses network every now and then. It is strange cause the bars are all still available on top but the error just says network lost. Usually notice it when sending text messages as they get queued. Sometimes, it just starts working on its own and sometimes I have to turn on/off the airplane mode.
The phone is an unlocked version purchased from the States. Please help me someone!
Thanks
Anyone has any ideas? This is really started to annoy me to the point where I wanna get rid of this phone. And I only got it yesterday. I've noticed that the issue is ONLY with the SMS service. When I try to send a text, randomly I get a message saying, 'message queued and will be send with service available'. I tried making/receiving calls during this time and it works fine. So it's definitely not that the service is lost. Such a strange issue.
Could it be that I have a LTE SIM that is causing the problems? It is a C6802 version of the Z Ultra and my understanding is that it doesn't have LTE. So just wondering if it could be that since I have a LTE SIM card in the phone it is causing these issues? I highly doubt that is the reason though.
Any help is really appreciated. Thanks.
phone_fanatic said:
Anyone has any ideas? This is really started to annoy me to the point where I wanna get rid of this phone. And I only got it yesterday. I've noticed that the issue is ONLY with the SMS service. When I try to send a text, randomly I get a message saying, 'message queued and will be send with service available'. I tried making/receiving calls during this time and it works fine. So it's definitely not that the service is lost. Such a strange issue.
Could it be that I have a LTE SIM that is causing the problems? It is a C6802 version of the Z Ultra and my understanding is that it doesn't have LTE. So just wondering if it could be that since I have a LTE SIM card in the phone it is causing these issues? I highly doubt that is the reason though.
Any help is really appreciated. Thanks.
Click to expand...
Click to collapse
Same problem with no solution till now. I may have to return for to warranty.
Its a software issue. Mine does the same thing.
Try to download new APN settings from the menu.. Mine grabbed weird info (proxy) which I had to remove, but it fixed some of the connection issues.
Now its only occasionally.. Is yours automatically changing from HSPA to 3G when Idle? Mine does this, which I forget which update I noticed it with... I assume its a battery saving issue. I have the stamina feature on, if you do you may try turning it off. I'd guess that would be the main culprit if you have it on, or related to the APN. It may or may not have a timer that tries to auto update the first time you put in your asim . if so, being you had to manually put your APN info in it couldn't connect at first so it may be caught up or whatever.. Good luck, I doubt its a warranty issue, but if you swap and it fixes, please let me know!
Anyone get their call forwarding to work? If so what did you do.
I keep getting this same error: Failed to forward incoming call from your mobile device to your Gear. Tap OK to try again.
I got that too from time to time. But that is because my phone has a poor reception at home. Gear S need to ask your phone to setup the forwarding via special dialer code. If your phone can't get signal for dialing code, it will fail even though it may be connected to Internet via wifi.
foxbat121 said:
I got that too from time to time. But that is because my phone has a poor reception at home. Gear S need to ask your phone to setup the forwarding via special dialer code. If your phone can't get signal for dialing code, it will fail even though it may be connected to Internet via wifi.
Click to expand...
Click to collapse
Yea I think I'm screwed. At least I know it is possible on AT&T tho.
FIXED IT!
I was able to get this issue fixed. This was bugging me for a month. Here are the steps I took to resolve this issue.
Uninstalled Gear Manager from the Note 4.
When I reinstalled Gear Manager it forced me to do a factory reset on the Gear S. This did not fix the issue however.
Did a factory reset on both the phone and the Gear S. This also did not fix the issue.
Got a new sim card for the Gear S. This did not fix the issue.
Got a new nano sim card for the Note 4. The Note 4 takes a micro sim but I had an adapter I bought off Amazon that takes a nano sim and makes it fit into micro slots. This also did not fix the issue.
Upgraded to Lollipop. This did not fix the issue.
Finally I found this thread.
https://forums.att.com/t5/Samsung-D...y-Phone-Settings/td-p/4170378/highlight/false
Someone said it was the settings on my account. I called AT&T on my Gear S number and pressed some buttons till I got their Technical Support team. I somehow got transferred to their Advanced Technical Support team right away. I talked to a guy named Robert. He was super helpful and listened as I told him what my issue was. I didn't even mention the Gear S call forwarding problem as that confuses a lot of reps. I just told him that I couldn't access the call forwarding setting in my Android Note 4 because I was getting a sim card or network error. Which I was. I told him to check deep in my account setting as I researched this online and it appears to be an account settings issue. He worked on his end and told me to turn my phone off. Then he told me to turn it back on. I did and went into the settings and did not get the error message. I was soooo happy. I thanked Robert and told him I was just going to mess with the settings a bit more and I didn't want to keep him. He said thank you for being a valued customer and we hung up.
My real reason for going thru this was to get the call forwarding set up between my Gear S and my Note 4. I made a sign of the cross and kissed the feet of my Roman statue before trying to initiate the call forwarding through a remote connection between my Gear S and Note 4. This time it worked.
So in my opinion it appears to be an account settings issue because it works for me now.
The Problem Came Back Again
Ok so the problem came back again. AT&T said that it is a known issue where you can't set up your device for call forwarding. To fix it, all you have to do is call AT&T and they reregister your device to the network. Then, you turn your phone off and on again and everything works.
SaintCrispin said:
Ok so the problem came back again. AT&T said that it is a known issue where you can't set up your device for call forwarding. To fix it, all you have to do is call AT&T and they reregister your device to the network. Then, you turn your phone off and on again and everything works.
Click to expand...
Click to collapse
All i did was downgrade back to kitkat then tried call forwarding and it worked perfect then let the note 4 re update to lollipop and call forwarding still works and has ever since no more sim or network error this was the only way i found to fix it cause AT&T couldn't tell me why it wouldn't work.
You know I think you're right. Because in my case I took my Note 4 to the Samsung Experience in Best Buy and they flashed lollipop thinking that would fix it but it didn't. I had to call AT&T support each time it didn't work. Then the OTA update of lollipop came thru to my phone and I let it install. So basically I reinstalled lollipop even tho I already had. There must have been some AT&T updates in there because ever since the OTA it has been working flawlessly.
I still get the network or sim card error from time to time. Call forwarding works after a reboot of both the phone and the watch. It's dumb that I have to do that tho.
SaintCrispin said:
I still get the network or sim card error from time to time. Call forwarding works after a reboot of both the phone and the watch. It's dumb that I have to do that tho.
Click to expand...
Click to collapse
This is for at&t/takes a few minutes to get to the point but maybe it will help. This guy also does a pretty comical review of a durability test too. I heard at&t auto call forwarding is finicky.
How To Setup Call Forwarding for the Samsung Gear…: http://youtu.be/-pAeLZxOuqk
Yea that guy is awesome. I've seen his videos before.
Samsung locked the forwarding option off the note 4 at least for Att. Once you call them and have them set it up server side everything works perfect
kirewade said:
Samsung locked the forwarding option off the note 4 at least for Att. Once you call them and have them set it up server side everything works perfect
Click to expand...
Click to collapse
Yea mine has been working recently so I'm good. My problem appeared to be AT&T. I went to the AT&T store and they told me to contact Samsung. I went to Samsung and they told me to contact AT&T. Made me wish I had an iPhone at that point.
Forwarding is an account feature. Samsung can't lock it. It is AT&T that locked it. It depends where your original AT&T account came from and how it was setup. They used to charge customers for this feature. That's why not everyone has it turned on.
Hope my experience will help someone. I followed all the tutorials I could find and could not get it to work. I finally gave in and called AT&T support. I didn't get the brightest person but this woman would not give up. On a last ditch effort it ended up being 2 things. I am behind a Microcell and forgot to enter the Gears S number. Second was she noticed that the profile for my line still had a Blackberry Passport on it from when I was messing around with one. She entered the IMEI for the Samsung device I am using and had me reboot. Wham, the Gear went into Call Forwarding mode. Tested all day today and just left my device at home. It worked like a charm.
I Still Love AT&T Tho
You got lucky. Whenever I call AT&T and mention the Gear S, they're like "uh" and don't even know what the device is. Same with the store. I went in there and they were like "man the Samsung guy was just here." I went to Samsung and they told me it was AT&T's fault and to contact them. I felt like Samsung was blowing me off but it really was AT&T's fault. If you ever have a problem with your call forwarding, don't even mention the Gear S when talking to AT&T. Just tell them you can't get your Samsung phone to set up call forwarding. Tell them every time you go into the call settings, then more settings you get a network and sim card error. When they fix this, they also fix your Gear S forwarding error without even knowing it.