Related
hi everyone,
I got my S3 from Bell two weeks ago, it worked fine most of the time including calls, sms and data.
but occasionally for whatever reason the phone cannot make call or send sms, no ring for incoming call also. it shows "not registered on network" when I try to dial. at the time showing this error, there was signal on the bar.
maybe after long time, it can registered itself into network again, but most of the time, I just restart the phone and it works fine again.
I called Bell and they asked me to replace the SIM card, so I did, but I still see this error. So I think it is not SIM issue.
anyone has idea what the cause could be? or is there anyway to fix it?
I tried to search online before I ask, just couldn't find a solution so far.
so post here and hope anyone can help,
thanks for the help in advance.
I've had this issue as well.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I had this problems with rogers as well. Same as you I contacted rogers they told me to remove the sim and replace it. Worked for a while but kept happening. I got fed up and rooted then installed kyan rom and haven't had the problem since. Not sure if it was rom based or if the factory reset before flashing resolved the issue but haven't had it since. Hope someone figures this out though because it's annoying especially on a new phone that is stock.
Sent from my SGH-I747M using Tapatalk 2
Good to hear you had fixed it.
I might try factory reset to see what happen.
healer82 said:
I had this problems with rogers as well. Same as you I contacted rogers they told me to remove the sim and replace it. Worked for a while but kept happening. I got fed up and rooted then installed kyan rom and haven't had the problem since. Not sure if it was rom based or if the factory reset before flashing resolved the issue but haven't had it since. Hope someone figures this out though because it's annoying especially on a new phone that is stock.
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
Had this problem on bell a few times the first 2 weeks I had my phone. Went to the bell store and without hesitation they told me to change the mobile network mode from gsm/hspa+/lte
To just gsm/hspa+.
Reason given was the Lte network where I was using my phone (west island, montreal) wasn't strong enough. So my phone would switch between networks until eventually it got in that state. Personnaly I think the problem was more signal penetration into the computer lab I work in.
It's been 2 weeks stable so far. A co-worker reported the same problem to me last week and he took my advice and hasn't had the problem since.
Sent from my SGH-I747M using xda app-developers app
Thank you very much for the tip. I was wondering that too, because I noticed that the network icon at top bar keep changing between H+ and LTE by itself. and I wonder why too.
I will try and see what happened.
thanks
uglyren said:
Had this problem on bell a few times the first 2 weeks I had my phone. Went to the bell store and without hesitation they told me to change the mobile network mode from gsm/hspa+/lte
To just gsm/hspa+.
Reason given was the Lte network where I was using my phone (west island, montreal) wasn't strong enough. So my phone would switch between networks until eventually it got in that state. Personnaly I think the problem was more signal penetration into the computer lab I work in.
It's been 2 weeks stable so far. A co-worker reported the same problem to me last week and he took my advice and hasn't had the problem since.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
SAMSUNG i747M not registered on network
I had this samsung s3 i747M from canada. Got it unlocked here in Pakistan. Placed a local sim in it. It recognizes the sim, registers it, makes calls, but then after a while, it shows "not registered on network". i restart, it registers network again, then loses it again. It keeps doing it. sometimes it is registered on network, but can't make or receive calls.
I have tried a number of things but the problem is not resolved and i'm fed up to the point that i want to throw this phone away.
The original rom had android 4.3
here's the list of things i have tried.
* changed the network mode to "GSM only" and "WCDMA/GSM (auto connect)" - NO USE
* Factory data reset a few times - NO USE
* tried a custom rom (it was so bad, i deleted it, don't even remember the name) - NO USE
* stock rom 4.4.2 from "sammobile.com" - NO USE
* tried flashing different modems from "http://forum.xda-developers.com/showthread.php?t=1831898" - NO USE
* tried changing the options from *#2263# to my network's specifications - NO USE
* tried sims from different networks - NO USE
PLEASE IF SOMEONE CAN HELP ME OUT HERE, I'M DESPERATE
@qamar_ish, what ROM is on your Samsung phone?
Originally it came with android 4.3. Currently it has this kitkat rom, which i downloaded from "sammobile.com".
the filename is this:
I747MVLUFNK2_I747MOYCFNK2_I747MVLUFNK2_HOME.tar.md5
It said on the webpage that it is the stock rom for SGH-i747M
audit13 said:
@qamar_ish, what ROM is on your Samsung phone?
Click to expand...
Click to collapse
Maybe flash the latest 4.4.2 ROM?
Thats what it is. it is the 4.4.2 rom, but the problem persists.
audit13 said:
Maybe flash the latest 4.4.2 ROM?
Click to expand...
Click to collapse
Does your carrier require an AWS-compatible phone? Does the i747m support all frequencies provided by your provider?
I'm not sure about whether an AWS phone is required or not. But it certainly supports all the frequencies provided by the networks here. I checked it by using the code *#2263# and the options have the frequency supported by my networks here, that is "ufone" and "warid"
PS. I'm not an expert on this thing, whatever i'm doing, i learnt it during the last week..
audit13 said:
Does your carrier require an AWS-compatible phone? Does the i747m support all frequencies provided by your provider?
Click to expand...
Click to collapse
It looks like your phone does support your carrier's frequencies.
Does your phone show the imei# from the dialpad? Is it possible there is something wrong with the phone's imei #?
It does show the correct imei when i dial *#06#. It had lost its imei initially when i got it unlocked, but got it fixed from someone.
qamar_ish said:
It does show the correct imei when i dial *#06#. It had lost its imei initially when i got it unlocked, but got it fixed from someone.
Click to expand...
Click to collapse
Do you know why it lost the imei during the unlock process? Does the imei # in the phone match the imei # on the label under the battery?
I dont know how it lost imei. The guy who fixed it said that the imei is corrupted and he fixed it. Now it shows the same imei as on the back of the device.
I have never had a Samsung phone lose the imei if the phone was unlocked using a code, assuming that is how your phone was unlocked.
Did you try re-injecting the imei with the efs folder? It can be done using nvwriter.
Ok. I will try that. Can u guide me how to do it? Or share a link or something.
And thanx for helping me out here man..
Link: http://forum.xda-developers.com/showthread.php?t=1804117
I've recently been having issues when calling certain numbers that my phone either starts ringing a few times then I get a busy signal or sometimes just a busy signl right away.
I know I'm not blocked from these numbers because one of the numbers is my gf and the other one of my close friends.
Now both my gf and friend have Sprint as well as myself. However, I can use my gf's phone to calll my number and she doesn't get a busy signal. And, if I call her phone from say a Verizon phone it rings normally.
This started happening very recently right before I upgraded to JB. I'm stock rooted.
Any ideas? I am thinking of calling Sprint to see if something is going on on there end.
Sent from my SPH-L710 using Tapatalk 2
Looks like your gf doesn't wanna speak to you anymore
Jk jk
It could be cause of hurricane Sandy
Try doing a nandroid and then going to stock
Sent from my SPH-L710 using xda premium
secondskin said:
I've recently been having issues when calling certain numbers that my phone either starts ringing a few times then I get a busy signal or sometimes just a busy signl right away.
I know I'm not blocked from these numbers because one of the numbers is my gf and the other one of my close friends.
Now both my gf and friend have Sprint as well as myself. However, I can use my gf's phone to calll my number and she doesn't get a busy signal. And, if I call her phone from say a Verizon phone it rings normally.
This started happening very recently right before I upgraded to JB. I'm stock rooted.
Any ideas? I am thinking of calling Sprint to see if something is going on on there end.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Have you made any progress on this?
I have an EVO 4G LTE,, my wife has an EVO 3D - both stock and unrooted.
I can call anybody but her - I get a busy signal. -= maybe for the last 4 days, (Hurricane Sandy related?)
Anyone else can call her without a problem
I can call anyone else without a problem.
I can text her just fine.
On her phone, I blocked my number from calling her - when I did that, I went straight to her voicemail. When I unblocked it, back to the busy signal.
I deleted my contact from her phone and Google account - no change
I spent 20 min on phone with Sprint Tech support- we restarted both phones, reset voice services on both phones, pulled her battery - none of this did anything.
The rep told me to either hard reset her phone, or to go to a store with both phones.
So, I hard reset her phone. I logged into her google account and did nothing else.
I called her from my home phone - call went through. I called her from my EVO - call went through!!!
So, feeling cocky, I saved my number to her phone as a new contact. I called her again - BUSY SIGNAL.
I deleted myself from her contacts again - no change
I have hard reset her phone twice more tonight - both times I just got the busy signal.
Anybody else have any thoughts?
Are either of you using Google Voice?
Sent from my Nexus 7 using xda app-developers app
dante32278 said:
Are either of you using Google Voice?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Im having the same issues when I call my wife's phone. I have Google Voice. Is that the problem?
Yes, had the exact same issue on my sgs2. Thought it was sprint, but after disabling Google voice the issue was resolved. I added it back about a month later with no issues.
Sent from my SPH-L710 using xda app-developers app
Had this problem as well. Originally had evolte, sprint kept telling me it was network related. After two weeks I finally went to a corporate store and they ported my number to a different phone and called the numbers that where getting busy signals, and it worked. So they said it was my phone not the network. Sprint wanted to give me another evo, this would be my fourth evo, I decli ed and said I wanted a different phone, after much arguing sprint agreed to let me switch to the gs3. Came back two days later to pick up phone, after activating the phone I called the same numbers and STILL COULD NOT CALL THEM. Wtf. So they blamed google voice and said to try deleting it, if that did not work then call cust. Service. Deleting google voice did not work. So I called cust. Service they said after explaning what was going on cust.u Service said this was a known issue and did not know what was causing it and had no estimate when it would be fixed. She asked for the numbers that I got busy signals on and then offered a fourty dollar credit a month for four months. Wierd. Today I could call one of the numbers and it went thru. Havent checked the rest yet.
Sent from my SPH-L710 using xda premium
It is not google voice. Sprints network is the problem. They are aware of this. If you have problems call them and give them the numbers you cant call. My problem seemed to be fixed on sunday.
Sent from my SPH-L710 using xda premium
Sorry for the delayed response. I didn't see much going on with this thread for a while so I thought I was just having a isolated issue.
Turns out the issue is a common Google Voice issue atleast if you have integrated your Sprint and Google Voice number into one.
I got rid of my Google Voice integration and am now back to the "lite" version where you have your regular Sprint number and a separate Google Voice number and the problem has totally stopped.
The reason I say it's a common issue is because people are posting about this in the official Google Voice support forums.
I wish I would have checked there first because it would have saved me a lot aggravation.
Anyway, try un-integrating Google Voice and see if that helps.
Sent from my SPH-L710 using Tapatalk 2
Using Google light and separating the numbers did not work for me I even uninstalled Google Voice completely and it did not work it may be true that Google Voice is having issues as well but the current issue is a network issue at least it was for me as a previous poster said mine started working on Sunday at least I got a Samsung Galaxy 3 and a 40 dollar credit a month for 4 months out of the deal
Sent from my SPH-L710 using xda premium
I have an LG CDMA phone first 2days i received any call normally .
Yesterday when try to call it it say that number is busy?
any idea to solve it?
Hope to see xda community the biggest cellphone solutions community
Hello fellow forum readers, im in dire need of some of your expert advice. I recently bought a Galaxy S4 from Ebay, the M919 model from tmobile. Today I received that phone, and proceeded to do the unlock guide fond here on the forum, it was succesful. I put my sim card in (im overseas, so its an international simcard) and the phone recognized my sims network. Well, next I tried making a phone call and thats where I found the problem, the phone simply wont make or receive a call. It tries to, but it hangs up. Sms also doesnt work. Wifi is fine. Everything else is fine. The phone is baseband version VUAMDL. I already flashed the same modem with odin to no avail. Does anyone have a suggetion of what to try next? Thanks a lot!
I just tried my data connection and its working fine! its only the calls! pls help!
re: calls
ferrojasaguilar said:
Hello fellow forum readers, im in dire need of some of your expert advice. I recently bought a Galaxy S4 from Ebay, the M919 model from tmobile. Today I received that phone, and proceeded to do the unlock guide fond here on the forum, it was succesful. I put my sim card in (im overseas, so its an international simcard) and the phone recognized my sims network. Well, next I tried making a phone call and thats where I found the problem, the phone simply wont make or receive a call. It tries to, but it hangs up. Sms also doesnt work. Wifi is fine. Everything else is fine. The phone is baseband version VUAMDL. I already flashed the same modem with odin to no avail. Does anyone have a suggetion of what to try next? Thanks a lot!
Click to expand...
Click to collapse
You need to flash the stock M919 Tmobile Samsung Galaxy S4 4.2.2 Odin flash firmware.
Here is the link to the official m919 firmware: http://www.hotfile.com/dl/213469534/9ff06bd/M919UVUAMDL_M919TMBAMDL_TMB.zip.html
After flashing all should be good!
Good luck!
Thanks Misterjunky! gonna try that as soon as I get home and let you know my results! :good:
Unfortunately no go.... I flashed the firmware with odin, everything is fine with the ezception of phone calls... pls help!
Sent from my LG-E970 using Tapatalk 4
I'd take the battery, sim card, and SD card out for 30 minutes, then put everything back in and boot up.
Sent from my SGH-M919 using xda app-developers app
Android_Monsters said:
I'd take the battery, sim card, and SD card out for 30 minutes, then put everything back in and boot up.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
thanks, tried that and still no go... :crying:
Well hate to say it. I think you got ripped of
Sent from my SGH-I337M using xda app-developers app
I have the same issue, mine is the wind m919v version. after two days of loading software and custom roms and fashing radios I got no service but had 4g and data working. I ordered an unlock code from a site and successfully unlocked it and it worked all last night perfectly with calls and txt. (weird cause its a wind phone and im on wind) Today Iwoke up to data working and emergency calls only again. I checked with another sim and the phone was carrier locked again. only this time putting in the unlock code didn't fix it. It unlocked it again but no service for calls or txt. so the phone can work it has to be something screwing up. so frustrating
damannn said:
I have the same issue, mine is the wind m919v version. after two days of loading software and custom roms and fashing radios I got no service but had 4g and data working. I ordered an unlock code from a site and successfully unlocked it and it worked all last night perfectly with calls and txt. (weird cause its a wind phone and im on wind) Today Iwoke up to data working and emergency calls only again. I checked with another sim and the phone was carrier locked again. only this time putting in the unlock code didn't fix it. It unlocked it again but no service for calls or txt. so the phone can work it has to be something screwing up. so frustrating
Click to expand...
Click to collapse
Flashing radios on the s4 messed up my service, only fix was Odin to stock. I do not mess with radios anymore
Sent from my SGH-M919 using xda app-developers app
Well this is kind of annoying... I'm using a T-Mobile S4 on the MetroPCS BYOD plan which is great... $55 all in (I have two lines).
The PROBLEM is while most manufacturers put their apps on the Google Play Store MetroPCS doesn't... all the MetroPCS apps (aka "bloatware" that come with a Metro phone aren't available anywhere.
This should be pretty simple, someone with a rooted phone could upload the apps. I really only want the the account management and visual voice mail apps.
I hope they fix this, any help in the mean time appreciated... the question is: WHERE CAN I GET THESE APPS?
Have you tried the metro app store, pretty sure it has that stuff.
https://apps.metropcs.com/c/939/metro-apps/
Sent from my SGH-M919 using XDA Premium 4 mobile app
http://androidforums.com/spirit-4g-metro-pcs-all-things-root/729769-my-metro-app.html
There's a link to MyMetro (account management), post #3 and voicemail app is in metro store that was linked above.
FYI, I switched my two Metro S4s to TMO recently, but I was only able to get MyMetro to work on one of them beforehand. Hopefully goes better for you, but I tried calling them and they seemed to have no clue what the app is or how to get it working. One person said that it wasn't compatible with my phone or plan, the fact that it worked on one of them was irrelevant....customer service gotta love them.
I have gone thru 2 sim cards, 2 SM-N910A with similar results.
In settings, call, additional settings, it comes up with Network or SIM card error. AT&T has replaced two sim card, one a micro sim, one a nano sim with adapter.
From the keypad, **21*808551999# the error message as attach
The AT&T associate spent an hour with the advanced tech support to no avail.
I have a Nexus 6 and I can access all the above function, so my account is provisioned properly and I'm post paid
Did you ever find a solution? I'm having the same problem.
It's something to do with the phone, as you seem to be aware of, I had a customer come in who wanted to forward his note 4 to his gear s, the same issue happened, from what I can gather it seems to just be an issue with the call app itself, a fix I read but never go to try was taking a sim card from a known working phone that has call forwarding on and inserting it into the unworking phone.
Try stopping the phone app and clear all data. I got a new sim card and then did that and my call forwarding worked. YMMV
I have the same problem. I called tech support today and the lady I talked to didn't even know that the gear app could auto forward you calls. She said she would set it up for me on her end. Not what I wanted. I want this 2 high end devices to perform the way they are suppose to before att got there hands on it.
So what I did was, I pulled out my Note 3. Updated to latest FireKat Rom and problem solved.
My note 4 and gear s worked perfectly when I first got them. THEN WE GOT AN UPDATE--------THE ONLY UPDATE.
That's when I first started having this problem.
Not only do we not have root, but now it isn't doing the cool things it should. I'm sorry for the long winded ***** but I shouldn't have to wait for the chance of a possible maybe sometime in the future if everything goes right update that may or may not correct this problem and could possibly inject more issues. I'm sure someone will correct me if I'm wrong.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
thanitos said:
It's something to do with the phone, as you seem to be aware of, I had a customer come in who wanted to forward his note 4 to his gear s, the same issue happened, from what I can gather it seems to just be an issue with the call app itself, a fix I read but never go to try was taking a sim card from a known working phone that has call forwarding on and inserting it into the unworking phone.
Click to expand...
Click to collapse
jrtireman said:
I have the same problem. I called tech support today and the lady I talked to didn't even know that the gear app could auto forward you calls. She said she would set it up for me on her end. Not what I wanted. I want this 2 high end devices to perform the way they are suppose to before att got there hands on it.
So what I did was, I pulled out my Note 3. Updated to latest FireKat Rom and problem solved.
My note 4 and gear s worked perfectly when I first got them. THEN WE GOT AN UPDATE--------THE ONLY UPDATE.
That's when I first started having this problem.
Not only do we not have root, but now it isn't doing the cool things it should. I'm sorry for the long winded ***** but I shouldn't have to wait for the chance of a possible maybe sometime in the future if everything goes right update that may or may not correct this problem and could possibly inject more issues. I'm sure someone will correct me if I'm wrong.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I came across this post:
This is a problem with AT&T. I'm running 4.4.4 Android on a new Note 4 and discovered that Google Voice wouldn't run on the phone. I suspect the issue is tied to AT&T's implementation of their Visual Voicemail.
After spending a few calls with AT&T Tech Support, I was able to get my Google Voice to work by using the Call Forwarding Settings of "Forward When Busy", "Forward When Unavailable", and "Forward When Unreachable" to be set to my Google Voice number. The problem is that the Note 4 has the bug you mention. It's not possible for the user to access the settings on the phone without getting the "Network or SIM card error" message.
AT&T Tech Support can manually configure these settings, but this will only help if you don't change the settings often because a call to AT&T is required. I'm hoping they fix this bug in the Lollipop build.
Be careful when calling AT&T Tech Support, the first two times I called, the Tech Support Agent had no idea that this type of Call Forwarding Settings were configurable.
For the 3rd try at calling them, I got someone more knowledgeable who first reset my voicemail to "Basic Voicemail". This is done in the AT&T system, not on the individual phone. Once that had been done, I then had to "activate" the Basic Voicemail by configuring my box. As soon as that was done, the AT&T rep was able to go into the AT&T system and manually configure the three Call Forwarding options that I wanted.
It was a huge pain to go through, especially because all I wanted to do was use Google Voice which has worked on AT&T Samsung phones going back to my first Galaxy SII.
My phone still shows the "Network or SIM card Error" whenever I try to access the Call Forwarding Settings, but at least I was able to get the Call Forwarding configured for my Google Voice to work again.
I don't know if this info helps you out, but I wanted to pass it along.
Went back to AT&T yesterday, this time armed with my Nexus 6. Got a nano sim. Nexus 6 call forwarding function work. Working sim into Note 4. same crap happens.
I just check again this morning, and my Note 3 is working flawlessly. Gear app autofowards my calls as it should and advanced call settings does not show error message. I believe it's a problem with the Note 4 not able to register it's self with the network. If I use another phone it registers fine, call forwarding work as does tethering hot spot. If I try my Note 4 neither wants to work. When I call att they can fix my tethering hot spot but can't fix forwarding. My Note 3 just works by its self without having to do anything such as clear app data or anything with I have tried along with phone reset multiple times. I'm going to use my Note 3 for a while.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Used my Note 3 all day today. Everything worked flawlessly. Got home and started my tethering hotspot and no problems. I'm thinking that I'm getting tired of my Note 4. My Note 3 running Firekat is just as fast. The only thing is the camera and the screen is so good. I wish my Note 4 was as, we'll I'll stop there. Thinking about trading Note 4 in for the iPhone 6 plus. I'll still have my Note 3 that everything works perfectly on. I get bored and like to be able to switch up the experience so if I have android, Note 3 would be note 4 but, and the hated ios witch just works and that can be jailbroken with a lot more help because they are all the same device and dose not have individually locked boot loaders. ????? What to do???
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
jrtireman said:
Used my Note 3 all day today. Everything worked flawlessly. Got home and started my tethering hotspot and no problems. I'm thinking that I'm getting tired of my Note 4. My Note 3 running Firekat is just as fast. The only thing is the camera and the screen is so good. I wish my Note 4 was as, we'll I'll stop there. Thinking about trading Note 4 in for the iPhone 6 plus. I'll still have my Note 3 that everything works perfectly on. I get bored and like to be able to switch up the experience so if I have android, Note 3 would be note 4 but, and the hated ios witch just works and that can be jailbroken with a lot more help because they are all the same device and dose not have individually locked boot loaders. ????? What to do???
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
Tethering should work unless you have unlimited data, all mobile share plans from att include thethering, also you can pre-order the s6 on Friday, if I remember what our new Sammy rep was talking to me about, got to play with it for 30 seconds before a customer walked in, the ui is nice and smooth and the new octa exynos chip is suppose to run cooler and it seemed, just for ui scrolling, to sail through it all. I like the look and feel, I want it......
Edit: keep in mind that you'll be in the same position you are now as far as root and unlocked bootloader, if you want these things wait to see who sells the phone unlocked then buy it at full retail and use it on your account. I work for att, I know even the nexus 6, the most close to stock phone we sell has bloat ware and is locked down tight. If I get the s6 it's out right and unlocked.
Yes I agree. It should work. If I switch my sim to another phone it works just fine. Everything works as it should, but if I put my sim back in my Note 4 in phone settings advanced settings I get an simcard or network error and call forwarding does not work. Also tethering will fail telling me to call 611 or visit website to register device for tethering. Gear app will fail to forward calls also and I have had problems with network data. If you Google this problem it is a problem with note 4. Some people on the att forums are just hoping for an update soon. That's is not acceptable to me. It worked when I bought the phone then there was an update that was pushed to my phone and now my phone is turned off and I'm using my Note 3. So by the time this gets resolved and I can enjoy my phone it will be old in the world of phone technology. So why should I keep it, hoping it will be updated sometime in the near future which keeps getting pushed back for some unknown to me reason. Don't get me wrong. I love my Note 4 but I want it to work now.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
The S6 Edge does look nice though.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
jrtireman said:
Yes I agree. It should work. If I switch my sim to another phone it works just fine. Everything works as it should, but if I put my sim back in my Note 4 in phone settings advanced settings I get an simcard or network error and call forwarding does not work. Also tethering will fail telling me to call 611 or visit website to register device for tethering. Gear app will fail to forward calls also and I have had problems with network data. If you Google this problem it is a problem with note 4. Some people on the att forums are just hoping for an update soon. That's is not acceptable to me. It worked when I bought the phone then there was an update that was pushed to my phone and now my phone is turned off and I'm using my Note 3. So by the time this gets resolved and I can enjoy my phone it will be old in the world of phone technology. So why should I keep it, hoping it will be updated sometime in the near future which keeps getting pushed back for some unknown to me reason. Don't get me wrong. I love my Note 4 but I want it to work now.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
The S6 Edge does look nice though.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Elpidio said:
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Click to expand...
Click to collapse
force stop the phone app and it should fix your issue.
icexshinigami said:
force stop the phone app and it should fix your issue.
Click to expand...
Click to collapse
thanks for the tip, I force stop all three phone apps to no avail.
Elpidio said:
thanks for the tip, I force stop all three phone apps to no avail.
Click to expand...
Click to collapse
I know you tried , the dialer codes.
always call forward setting , **21*808551999# (did you make sure it is 10digits? should be , **21*1808551999# if you are in the us. it might be worth a try.
conditional call forwarding **004*1808551999# (busy, rejected, missed calls)
icexshinigami said:
force stop the phone app and it should fix your issue.
Click to expand...
Click to collapse
icexshinigami said:
I know you tried , the dialer codes.
always call forward setting , **21*808551999# (did you make sure it is 10digits? should be , **21*1808551999# if you are in the us. it might be worth a try.
conditional call forwarding **004*1808551999# (busy, rejected, missed calls)
Click to expand...
Click to collapse
sorry, there's one digit missing in my original post
should have been +18085519959
There's definitely something wrong with how AT&T network supporting this phone. I have no problem with my Nexus 6. It's very frustrating but it's something I have to live with if I want to keep using this phone.
Anyways, thanks for trying to help.
Elpidio said:
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Click to expand...
Click to collapse
The upgrade fixed the problem for me. I didn't change anything else besides the OTA update.
scrtsqrrl said:
The upgrade fixed the problem for me. I didn't change anything else besides the OTA update.
Click to expand...
Click to collapse
only thing I have not done is "wipe data/factory reset" from the recovery mode. I'll see if I can back up my data on ODIN
Elpidio said:
only thing I have not done is "wipe data/factory reset" from the recovery mode. I'll see if I can back up my data on ODIN
Click to expand...
Click to collapse
Weird that would have been one of the first things I did.. Assumed you already went that way.. If after all this it doesn't work it seems you may have a defective device and should bring it up with samsung or att for an exchange...
icexshinigami said:
Weird that would have been one of the first things I did.. Assumed you already went that way.. If after all this it doesn't work it seems you may have a defective device and should bring it up with samsung or att for an exchange...
Click to expand...
Click to collapse
I did the "wipe data/factory reset" from recovery and its still the same. You maybe right that the device is defective and since its more than 30 days, either I'll call Samsung for a replacement or claim insurance, however, by looking at AT&T community forum thread, I read that it all worked with N910AUCU1ANIE firmware, when AT&T updated that firmware, all hell broke loose. I'll see if I can have Samsung replace it.
https://forums.att.com/t5/Samsung-D...e-Update-Broke-my-Phone-Settings/td-p/4170378
Elpidio said:
I did the "wipe data/factory reset" from recovery and its still the same. You maybe right that the device is defective and since its more than 30 days, either I'll call Samsung for a replacement or claim insurance, however, by looking at AT&T community forum thread, I read that it all worked with N910AUCU1ANIE firmware, when AT&T updated that firmware, all hell broke loose. I'll see if I can have Samsung replace it.
https://forums.att.com/t5/Samsung-D...e-Update-Broke-my-Phone-Settings/td-p/4170378
Click to expand...
Click to collapse
Its on its way to Samsung Repair Center in Plano, TX