Related
I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue
Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either
I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.
hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts
I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.
Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.
I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.
Are any of you using task-killers that may somehow be interrupting an important background service?
I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102
Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?
My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?
Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.
jacka$$1 said:
Mod it. What have you got to lose? Your overall performance will increase. The radio signal may even improve. Your call.
Click to expand...
Click to collapse
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh
Hey!
You dont want to lose your warranty, then use it!
Your phone seems to be faulty...
My phone is experiencing the same problem as of yesterday. Won't connect. Wonder if it's a T-Mobile issue.
laughter95 said:
thanks for the tip. i've been thinking about it. it's the warranty i don't want to lose. eh i'll keep thinking about it.
this phone sucks. it's glitchy, can be sluggish. iphone got dumbed down but at least its functions work.
meh
Click to expand...
Click to collapse
Its only glitchy coz you have stock rom
Cyanogen is really stable and adds alot of features / functionality.
Fair enough you dont want to lose warranty but i remember in the general thread that lots of hardware failures and others can still fix your n1 under warranty even though they unlocked the bootloader.
I too have this problem, hopefully the 2.2 update will fix the problems.
Can you guys confirm if its android or your service provider thats causing this...
laughter95 said:
My N1 will not reconnect to a mobile network if it has been sitting for a few hours in a no-coverage area, such as a building. I cannot get it to reconnect, even after refreshing the network search. This action only leaves me with no result or a message saying that there was an error in searching or connecting to mobile networks. The only solution is to restart the phone. Every time I try to turn the phone off after this error has occurred, the shutdown sequence hangs until either I become frustrated and do a battery pull, or it automatically restarts and do a battery pull, or it automatically restarts itself. Furthermore, the phone used to give me an error notification saying that the phone does not have carrier service. Now, it does not. Furthermore, the phone used to give me an error notification saying that the phone does not.
I tried uninstalling all my programs and nothing has worked for me. I've also tried toggling the airplane mode to no avail.
I'm considering putting on the cyanogen ROM to see if it would fix this error, but I am hesitant to void my warranty. It's a pretty serious problem as I'm very frequently in a building where I don't get service. It's quite frustrating to have to wait to reconnect to a mobile network once I leave the building and hope that the error didn't occur or have to do a battery pull every time I realize that the phone simply won't reconnect.
Can anyone suggest any solutions?
Click to expand...
Click to collapse
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!
rensky said:
I have the same problem and it's starting to bother me a lot because my car is parked in a garage with no coverage. My in-car BT then becomes useless as my phone won't reconnect to the network once I exit the garage
I just called Google support 10 mins ago about this and they went through normal protocol to reset to factory settings. They then called Tmo and let them know what the issue was while I was still on the phone. Tmo unregistered my phone from the network while my battery was taken out of my phone and then reregistered my phone to the network. Tmo asked me to monitor this for a few days and call them directly (not Google) if the issue persists. They will then elevate this to a higher level because they feel this would be a network problem, and not a hardware issue.
Hope this helps! Please post what you have tried to solve the problem!
Click to expand...
Click to collapse
^ it worked! my phone reconnects to the cellular network after what Google/Tmo did for me on the phone!
I haven't tried calling tmobile, but it is NOT something that will be fixed by hopping on cyanogen's rom. I've been rooted on cyanogen's rom for quite some time and this problem still exists on my n1 which is SUPER annoying. I will try calling tmobile to see if they can fix it on their side, but rooting is not the fix here.
I had the same issue. I used anycut and phone info shortcut and changed the wireless default setting to us and it totally fixed the problem. Have not had that issue again.
-------------------------------------
Sent via the XDA Tapatalk App
I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"
I get this too with an at&t phone.
Have asked for a replacement device from HTC (since the reception is crappy to begin with).
I also have audio quality problems when reception is only 1-2 bars.
Will see if the new phone is better.
I had this problem regularly. It hasn't happened once since I upgraded to Froyo, so I think it has been fixed in that release.
sometimes have this too, i fix it by going to the settings > wireless > mobile networks > APN. at first i deleted and retyped my password in the selected APN, now i just click my network in the APN settings, don't change anything and leave. It immediately reconnects after that.
edit: and i have stock froyo & live in belgium.
I got a new, replacement phone from HTC today.
This new phone has a BIG PROBLEM with this issue.
Even if I am only without reception for a couple of seconds (go through the garage, etc.) it will not connect to any network until I reboot.
My old phone would only experience this problem maybe 25-35% of the time.
Very, very annoying!!!
wildfyr said:
I resolved this by going to the T-Mobile store where they replaced my SIM card. They made a copy to a new SIM card, installed it and everything works fine.
For the record symptoms included:
* "Error while searching for network" message
* Found networks but said "your SIM card is not authorized for this network" when connecting
* Network listed as "No service" or "Emergency calls only | T-Mobile"
Click to expand...
Click to collapse
I had similar issues and called tmobile support. I was first linked to Google support. They went through the similar process as described by in the first page. (#*#*4636*#*# select USA band etc). While I was on hold, they called t mobile tech support and had them reset network connection and tried to get me onto a different tower etc.
Tmobile support stated that my sim card (had for about 2 years) was the cause of the issue as they can't handle smartphones as well as their new sim cards. They also said the new sim should improve reception and connection stability (Don't see how a new sim could do this but what do I know?). Moreover, they noted my account and told me to go into the nearest store for a new sim card. Went into the nearest tmobile store told them the issue, they pulled up my account and gave me a new sim. Took less then 5 minutes and I have not had the issue with staying connected to the tmobile network.
I will update this after a few days to see if I still have the issue.
I have the same problems that i cannot connect to network here in germany. first i think it was my sim card, but befor i had another provider (E-Plus) where i had the same problems with reconnecting to network. and one day my eplus sim card is broken so i had to buy a new one by t-mobile. i have tried a lot of roms from here (cyanogen/ 5.0.7 /5.0.8T5 Kangorama rodriquezstyle and leofroyo) everyone seems to have the same problems with reconnecting to network. i hope im not alone with my problems and someone can help.
hmm...
Count me as another. I just upgraded to froyo and it went beserk. Had no service for a while. It would only come on after constantly tapping "select network automatically" until it kicked me out of the menu. It started getting better but kept kicking me out of 3g. I set it to stay always on 3g and it seems to be better... still I'm going to call tmobile and see if I can get a new sim as well.
Thanks for the info guys!
Hi I am in need of some help. I will try to give as much detail as possible.
I was talking on the phone 3 days ago and suddenly my call was cut short. The signal icon at the top was greyed out and it had a little x in the bottom. I tried to figure out what happened and at first I thought the cell tower went down because I was unable to connect to 2g, 3g, LTE/4g, nothing.
Next day with my father visiting my house, I tried his phone, put in my SIM, it works, there is signal (nothing greyed out) and I see the name of the phone service at the top left "Personal". His phone with his SIM works as well. Cell towers are working fine. I put my SIM back in my phone, no signal, not able to make phone calls or receive text messages.
At this time WIFI, Whatsapp, the phone itself works. I double checked APN settings from the carriers website, everything matched. I tried rebooting the phone, reseating the chip, selecting towers automatically, manually, and read many many discussions on the web none of which helped. I decided to do a factory reset. Backed up all photos to the computer and proceeded to reset it to factory new. Put in the SIM and same problem. Oh I also in the meantime have spoken with my service provider and they do not see anything wrong on their end.
So now I proceed to restore the phone from a backup on my MI account, all apps restored. Now I try to use Whatsapp and it wants to confirm my account with a text message, that is a problem because I can't receive text messages. I went to my service provider today, they put in a store SIM with a different number and it worked, they assumed I had a faulty SIM and gave me a new SIM with my number, same problem. Now I think it has something to do with XIaomi or MIUI or my MI account. I log into my MI account from my computer and try to add my email under security and it won't let me because it needs verify my account by sending a text message to my cell which of course is not working.
I am thinking of rooting the phone but I imagine I will somehow be blocked there too.
What happened to my phone?
Is my account being protected in some way MIUI, XIaomi or my MI account preventing me from activating my SIM?
Everything I try to do requires a confirmation text.
I want to root the phone but in order to do so I need to request that Xiaomi unlock the bootloader which will require a text message which of course is to be sent to my phone that wont connect to the cell tower.
Was I hacked or spoofed?
How do I go about fixing my situation?
Have you tried changing region and changing back to your country again? That may be possible reason.
For confirmation of code for bootloader unlocking, while applying put your sim card into other phone and that way you'll be able to get code and bootloader unlocked and can flash and try with different rom.
Similarly if your device is out of warranty then you may want to check with the antenna cable inside phone if that is got disconnected or got loosen. I don't if this would have happened or not but this could be issue. Process with precaution if you do so,I won't be responsible for anything.
My phone is constantly being interrupted by this annoying popup: (I can't post links being a new user, but the image is at imgur FN7uUhL )
"Alert
Sorry, we're having trouble connecting. Make sure you have a good signal and try again. If you still can't connect, call us at 800-922-0204.
Error code 1001"
It doesn't say what app it is, but I suspect it's from Verizon because the phone number is theirs.
My phone is unlocked and I use it on Personal in Argentina. I've used this phone for years and this only started happening last Thursday out of nowhere. No new apps, no system upgrade.
Rebooting the phone doesn't help either, and I wouldn't want to factory reset if it can be avoided. Any ideas what this might be?
Thanks!
same, just today noticed this on an older LG G4
Alert Message - Same thing here...
Same thing here have had Moto E4 Plus on Metro PCS for the last few years and just started receiving this message in the last week. The phone was a Verizon phone that I unlocked and has been working great on Metro...until now. What's going on?
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
bump
Greenguru said:
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
Click to expand...
Click to collapse
bump...
Same here on my note 4, using T-mo prepaid. Just started a week ago. Also the verizon splash screen still displays on power up. My understanding is the V boot loader is locked.
Greenguru said:
This issue has me needing to toss my note 5 in the lake I wonder has anyone called the number in the error message thanks happens when i need every second . My note 5 unlocked and running on cricket
View attachment 4827857View attachment 4827859
Click to expand...
Click to collapse
SOLVED I had the same problem as well but I found a way to get rid of it, you gotta disable the My Verizon app and then 1 settings then mobile networks then network mode and set the global off to LTE/GSM/UMTS and then it will not pop up anymore, your welcome.
by Myles Tecomba
Good news, I found the locations since I don't have "my verizon apps" Bad news, the fix does NOT work at all.
Solved
I actually got online with Motorola because I knew that the app causing this nightmare was Verizon Login . The problem is that I debloated all my Verizon and the problem still occurred. But then by going through Settings | Apps | ... |Show System, I say the bugger was still there. I disabled it and the problem was solved. Of course this worked for me because I'm on an unblocked phone and note using Verizon.
My husbands Samsung Galaxy S7 has been doing this for over a month. He tried disabling anything Verizon related and even a factory reset and it's still doing it.
XCutecakeX said:
My husbands Samsung Galaxy S7 has been doing this for over a month. He tried disabling anything Verizon related and even a factory reset and it's still doing it.
Click to expand...
Click to collapse
Yes, I did same with my note 4, still there. IGNORE those solved posts, this problem is NOT solved. I use T-mobile prepaid with this phone and since verizon locks the boot loader, there is not yet a rooting solution for this phone and since it's a note 4 there will not be one forthcoming.
fixed it permanently
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
In addition, disable permissions of My Verizon: SMS, phone and GPS location, your welcome
gobearsltl said:
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
Click to expand...
Click to collapse
So I have an old Verizon tablet that is running android 5.1.1. I don't have options for "show system" or "Verizon login" that I can find. Anybody familiar with this 5.1.1 that knows where it would be or if I'm overlooking. Thanks.
Awesome! I'm using an unlocked Verizon LG G5 in Canada and I've been trying for quite some time to get rid of this problem. I've tried all the suggested fixes I could find on the net and this is the solution! Thanks so much buddy. Much appreciated eh!
This problem started recently for me on Samsung S6 unlocked Verizon phone that I use with foreign SIM cards when traveling. I tried restoring settings to default, but that didn't work. Then I tried resetting network settings and that appears to have worked. it was popping up every couple minutes and so far it has not.
don't work
i know this is a old post but i changed the network it didnt fix it it made me not have signal and still popped up so i had to change it back to global and its still doing it , it only started last month i have a s6 unlocked verzion its so annoying
Solved - BIG TIME!!
joshswife1992 said:
i know this is a old post but i changed the network it didnt fix it it made me not have signal and still popped up so i had to change it back to global and its still doing it , it only started last month i have a s6 unlocked verzion its so annoying
Click to expand...
Click to collapse
I had the same problem on my unlocked S6 Edge and knew that the Verizon Login app was the issue but the damn phone wouldn't let me disable it; grayed out. I bought an app in the Play Store named "Package Disabler Pro (Samsung)" for $2.99. The thing will let you disable ANY software whether built in or not. So once you launch, disable Verizon Login with it and the problem is gone. If you disable "Setup Wizard", you also won't get the stupid message about the SIM not being VZW card when you boot. I disabled all the other Verizon software too. Problem was so aggravating that I got an account here just to share the answer since I figure it has to be driving people CRAZY!!!!
- Bob
Help!!!
Still having this issue, I’ve disabled all those apps, force stopped them, and it continues to haunt the phone. I’ve called Verizon and they don’t know anything about it, and I’m really about to throw the phone away and buy a new one. It’s an s7 so it’s still a decent phone, but I don’t know what else to do
So Close, but Disable is Disabled
gobearsltl said:
SOLVED: I have two Verizon phones that I now use on T-Mobile and this has worked for both.
Settings->Apps & Notifications->App Info (options may be slightly renamed on different versions of Android, may be Applications instead, just get to the big list of applications in the Settings app)
then hit the triple dot/menu thing to give extra options and choose Show System
Scroll down and choose Verizon Login and disable it and force stop it.
Message will be gone forever. I've rebooted both phones several times and the message has never come up again.
Click to expand...
Click to collapse
This definitely got me closer. Using this method I was able to revoke permissions which forces VZ SpyLogin to fail so it isn't running, BUT, the "Disable" button is disabled, even if I force stop the app. It's most certainly this application causing the issue. Thanks for the closest solution.
**EXTRA info
This wasn't happening at all on my phone ever, and this is an old one (I need the IR blaster in the Samsung G6). It's an unlocked Verizon branded phone running on ATT network. I factory reset it yesterday and now I am getting this annoying Verizon Login nonsense.
I rooted my T-Mobile Pixel 4 XL last night, went fine.
I run my phone dial SIM. I have a T-Mobile ESIM and a physical ATT SIM.
After rooting the phone defaulted to the ATT sim and installed a bunch of BS ATT apps and my T-Mobile ESIM would not activate so I removed my ATT SIM and did a factory reset.
NOW I have no working SIMS. The phone will not detect the ATT sim, doesn't even see its in the phone. I tried it in another phone and it works fine so I dropped another SIM in my P4XL, does not see it.
I've reset again, still nothing.
I've reset the network settings, still nothing.
I've gone into the *#*#4636#*#* phone options and tried different network settings, nothing.
I'm lost at what to try next!
Took some work to get T-Mobile to unlock my phone on lease and only 5 days old, I really dont want to have to replace the phone if I'm over looking something!
Got this figured out. Had to provision the ESIM again via T-Mobile T-Force Twitter chat and the PSIM kicked in. I don't think it's that I needed T-Mobile to do anything, the phone just didnt realize I wanted to use any SIMS.
Once I tried to setup the new ESIM, the phone was like, "oh, do you want to use two SIM's? Do you want to use both Slots 1 and 2"? I said yes and poof, PSIM worked.
However the ESIM said it was not activated so we had to get TMobile to enter the full EID in the ICC box on their screen and my phone immediately accepted the QR scan and activated the ESIM again.
You beat me to it, yeah, it can get a little whack there when you factory, do a wipe full image, etc. As you've seen if you just go back and tell it you want to set up an ESIM it will work. I'm on Fi so it's easy to do myself as I can just open the app and it will say I'm not provisioned and offer to set up the ESIM. Only came up once for me here when I first unlocked the bootloader and had the unconditional wipe but ran into it a few times with my 3A.
Help me out guys. I wonked up my P4 XL trying to install some custom script, I need to factory reset the thing again and I really don't want to go through all that BS of having to get T-Mobile T-Force online via Twitter and try to fix it!
I swear I picked the option to not wipe the eSim with the factory reset but then I did a full factory wipe and it killed it so is there a different between factory reset and wipe or something I need to pick for either or what? Help?
In *#*#4636 etc make sure that DS is enabled under the first menu option