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?
I bought a used t-mobile galaxy s8. The website I used said clean imei and I put my sim in the phone and it worked fine. After taking it home it stopped working. I played around with the settings to get it work and came to find that it works briefly after turning phone off and then back on. After about 10 minutes I can't make call or even perform a speed test via speedtest app. The dialer screen will not even load and remains blank, then no calls incoming or internet. If i restart then it starts again. This made me suspicious and I eventually found the t-mobile imei site which says it has an outstanding balance and may not be able to be used. I just find it weird it works then stops. Is that what is causing it? Will it eventually stop working completely?
call tmobile and describe your issue. they can help or at least tell you what to do.
OP, where did you buy the phone from?
I purchased one from S**p*a and have similar concerns.
I recently had the same issue.
I found out somehow an option was enabled that made it seem like i was network blocked or had a bricked sim card.
Under settings/connections/more connection settings/wifi calling
Make sure the middle option is selected and not "never use cellular network"
For some reason every samsung phone i have owned has enabled this option atleast once during ownership.
Sent from my SM-G950U using Tapatalk
Every day I travel on the London Underground and obviously lose 4G signal when I am below ground.
Since the last update a week ago to 10.2.26.0, when I come back into a 4G area I cannot use any data services without either rebooting the phone or toggling Mobile data on and off, which is very frustrating.
The bars will show full 4G but no data will flow on any app until I do this.
Has anyone else experienced this?
Same on mine...
Yes same issue here
I had this happen to me earlier and it turned out that the access point settings had been altered at update from one firmware to the next. The system tries to install some generic APN-settings based on my operator’s name as my operator has no automatic way of installing them the usual way on this phone as it does on the more commonly used brands.
Check with your operator what the settings should look like and enter them under the access point settings for the sim-card if the current ones look off. Just an idea because I had the same problem going back to 4G from Wi-Fi. Reboot or airplane mode was the only thing to fix it for me. To be more exact it was the address for the setting “APN” that was wrong for me. The system had put an address that wasn´t a valid IP-address. Obviously, Xiaomi had tried to guess the address based on my operator name but got it wrong. As soon as I got the right setting in place all problems were gone.
This problem got worse as I had activated LTE voice calls. Before that it only happened occasionally, but with LTE-voice calls activated it happened every time I went from Wi-Fi to 4G.
gerhard_wa said:
I had this happen to me earlier and it turned out that the access point settings had been altered at update from one firmware to the next. The system tries to install some generic APN-settings based on my operator’s name as my operator has no automatic way of installing them the usual way on this phone as it does on the more commonly used brands.
Check with your operator what the settings should look like and enter them under the access point settings for the sim-card if the current ones look off. Just an idea because I had the same problem going back to 4G from Wi-Fi. Reboot or airplane mode was the only thing to fix it for me. To be more exact it was the address for the setting “APN” that was wrong for me. The system had put an address that wasn´t a valid IP-address. Obviously, Xiaomi had tried to guess the address based on my operator name but got it wrong. As soon as I got the right setting in place all problems were gone.
This problem got worse as I had activated LTE voice calls. Before that it only happened occasionally, but with LTE-voice calls activated it happened every time I went from Wi-Fi to 4G.
Click to expand...
Click to collapse
Mine is unchanged from update, and it's as indicated on my operator site
meti84 said:
Mine is unchanged from update, and it's as indicated on my operator site
Click to expand...
Click to collapse
So do you have:
wap.tim.it
or:
ibox.tim.it
gerhard_wa said:
So do you have:
wap.tim.it
or:
ibox.tim.it
Click to expand...
Click to collapse
Well, I didn't update my profile in a while, I have fastweb now... BTW I have apn.fastweb.it
meti84 said:
Well, I didn't update my profile in a while, I have fastweb now... BTW I have apn.fastweb.it
Click to expand...
Click to collapse
When I ping that address it comes up as invalid. You should see if there are alternatives.
gerhard_wa said:
When I ping that address it comes up as invalid. You should see if there are alternatives.
Click to expand...
Click to collapse
https://www.fastweb.it/myfastweb/as...ne-configura-internet-su-smartphone-o-tablet/
It's in Italian, but as you can see it's the official Fastweb guide
gerhard_wa said:
I had this happen to me earlier and it turned out that the access point settings had been altered at update from one firmware to the next.
Click to expand...
Click to collapse
Doesn't seem to be the issue. I am on EE here in the UK and the APN is correct. Can't see how toggling data off and on would resolve this if the APN was wrong anyway?
meti84 said:
https://www.fastweb.it/myfastweb/as...ne-configura-internet-su-smartphone-o-tablet/
It's in Italian, but as you can see it's the official Fastweb guide
Click to expand...
Click to collapse
I can see that but still, do a trace route for apn.fastweb.it and it can´t solve that address so there is something wrong with it. Anyway hope you will find the culprit of your problem!
I almost have the same problem .. after a phone call 4g disappears .. After the talk 4g comes back but the data connection does not work anymore .. Data off and switching on is the solution. I have send my phone back to the retailer i hope dee can fix the probleem.
I have the same issue.......latest Global Beta......switching data off and on for now....and hoping that fix is coming as it is annoying...
Okay so this is found to be experienced by others - how do we bring this to Xiaomi attention? Right now a phone that just randomly chooses to lose data capability is useless, as I lose notifications, messages, home automation activity prompts, Ring doorbell alerts, Nest smoke alarm alerts - pretty much renders the phone useless if I am not connected to WiFi, and the worst is not knowing it's stopped working till I try something.
One thing you could do if you have activated VoLTE is to deactivate VoLTE. If this makes a difference it sugests that something is wrong in your local configuration. Otherwise you may have to take it back to the seller.
Same problem here in Germany with o2.
I just found this solution to slightly another but very similar problem and I'm testing it right now.
Go to the APN settings (Settings -> SIM card Settings) and better do a reset to default (not necessary). Choose the o2 option and in a field called MVNO type select IMSI. You should be fine.
Will report back if this worked.
gerhard_wa said:
One thing you could do if you have activated VoLTE is to deactivate VoLTE. If this makes a difference it sugests that something is wrong in your local configuration. Otherwise you may have to take it back to the seller.
Click to expand...
Click to collapse
VoLTE is not enabled on my device, but this doesn't sound likely anyway - I have had the phone since the first week it was available in Europe - over 3 months - but the data stopping working only happened with a recent update. Anyway, this thread and other forums suggest this is a wider issue - can't see that sending it back to the retailer will achieve much as the replacement will likely do the same!
cool400 said:
Same problem here in Germany with o2.
I just found this solution to slightly another but very similar problem and I'm testing it right now.
Go to the APN settings (Settings -> SIM card Settings) and better do a reset to default (not necessary). Choose the o2 option and in a field called MVNO type select IMSI. You should be fine.
Will report back if this worked.
Click to expand...
Click to collapse
The APN settings are all greyed out on EE - I can read them but I can't edit them?
Any news here? I'm still stuck with this annoying problem.
I'm on MIUI 10.2. 9.0 Global and no updates available.
Just came here to say I have he same problem. Not really too annoying as all it takes is toggling airplane mode off then back on after a couple of seconds. But sometimes I don't even know the problem has surfaced and I end up missing notifications.
It happens sometimes even after I enter an elevator then leave.
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 don't think VOLTE is working for me. Maybe I'm not sure how voLTE works, but on my Nokia 9 and OnePlus 7 Pro I have an icon that says VOLTE.
When I place a call my signal goes from LTE/LTE+ to either 3G/H+. Which I don't think it's supposed to do on VOLTE.
I have:
XQ-AT51
Build Number: 58.0.A.3.170
Google Play System: September 30th 2020
Baseband version: sdx55.rmtefs-00068-13
Carrier: T-MOBILE USA
In Network & Internet > Mobile Network: Enable VoLTE is enabled
In About Phone > SIM Status: Mobile Voice network type is LTE. However, when I'm on a call it says UMTS and HSPA+ for voice and data
In *#*#4636#*#* VoLTE is also enabled.
So, I'm not sure if I'm missing something, but I've never had this issue before on my other phone.
EDIT: Spoke with a technician at T-Mobile and they said everything is fine on my account. Did say to get a new sim card, which didn't fix the issue.
tjk639 said:
I don't think VOLTE is working for me. Maybe I'm not sure how voLTE works, but on my Nokia 9 and OnePlus 7 Pro I have an icon that says VOLTE.
When I place a call my signal goes from LTE/LTE+ to either 3G/H+. Which I don't think it's supposed to do on VOLTE.
I have:
XQ-AT51
Build Number: 58.0.A.3.170
Google Play System: September 30th 2020
Baseband version: sdx55.rmtefs-00068-13
Carrier: T-MOBILE USA
In Network & Internet > Mobile Network: Enable VoLTE is enabled
In About Phone > SIM Status: Mobile Voice network type is LTE. However, when I'm on a call it says UMTS and HSPA+ for voice and data
In *#*#4636#*#* VoLTE is also enabled.
So, I'm not sure if I'm missing something, but I've never had this issue before on my other phone.
EDIT: Spoke with a technician at T-Mobile and they said everything is fine on my account. Did say to get a new sim card, which didn't fix the issue.
Click to expand...
Click to collapse
Yeah bro i have two Xperia 1 IIs and i didn't update the other one but the one i updated seems to have the same issue i even switched carries VOLTE is enabled and not working I'm thinking of factory resetting as last resort I'm contacting Sony first you should do the same. I have same build number as you.
tjk639 said:
I don't think VOLTE is working for me. Maybe I'm not sure how voLTE works, but on my Nokia 9 and OnePlus 7 Pro I have an icon that says VOLTE.
When I place a call my signal goes from LTE/LTE+ to either 3G/H+. Which I don't think it's supposed to do on VOLTE.
I have:
XQ-AT51
Build Number: 58.0.A.3.170
Google Play System: September 30th 2020
Baseband version: sdx55.rmtefs-00068-13
Carrier: T-MOBILE USA
In Network & Internet > Mobile Network: Enable VoLTE is enabled
In About Phone > SIM Status: Mobile Voice network type is LTE. However, when I'm on a call it says UMTS and HSPA+ for voice and data
In *#*#4636#*#* VoLTE is also enabled.
So, I'm not sure if I'm missing something, but I've never had this issue before on my other phone.
EDIT: Spoke with a technician at T-Mobile and they said everything is fine on my account. Did say to get a new sim card, which didn't fix the issue.
Click to expand...
Click to collapse
I software repaired the phone and volte is working again sadly I found no other way that doesn't involve that , I too thought it was my sim card/service and switched carriers only to find the same issue but it's fixed now sucks I wasted my time looking for a solution all this time since November
charlie313 said:
I software repaired the phone and volte is working again sadly I found no other way that doesn't involve that , I too thought it was my sim card/service and switched carriers only to find the same issue but it's fixed now sucks I wasted my time looking for a solution all this time since November
Click to expand...
Click to collapse
What did you do exactly?
bbot3k said:
What did you do exactly?
Click to expand...
Click to collapse
I plugged my phone into my laptop and it installed the xperia companion and I picked software repair which I thought wasn't gonna erase my data but it turned out it's basically like factory reset and then I just reinstalled everything . I then updated my apn settings manually from the TMobile apn settings and it was working like it was before the dumb update but sadly wasted reinstalling but I guess I should've just done this from the beginning instead of wasting all my time fiddling with secret menus, customer service and crap so if you want it fixed definitely give it a try if not hopefully the next update fixes, I'm hoping it doesn't happen again, major time wasted searching the internet for a solution
charlie313 said:
I plugged my phone into my laptop and it installed the xperia companion and I picked software repair which I thought wasn't gonna erase my data but it turned out it's basically like factory reset and then I just reinstalled everything . I then updated my apn settings manually from the TMobile apn settings and it was working like it was before the dumb update but sadly wasted reinstalling but I guess I should've just done this from the beginning instead of wasting all my time fiddling with secret menus, customer service and crap so if you want it fixed definitely give it a try if not hopefully the next update fixes, I'm hoping it doesn't happen again, major time wasted searching the internet for a solution
[/QUOTE
charlie313 said:
I plugged my phone into my laptop and it installed the xperia companion and I picked software repair which I thought wasn't gonna erase my data but it turned out it's basically like factory reset and then I just reinstalled everything . I then updated my apn settings manually from the TMobile apn settings and it was working like it was before the dumb update but sadly wasted reinstalling but I guess I should've just done this from the beginning instead of wasting all my time fiddling with secret menus, customer service and crap so if you want it fixed definitely give it a try if not hopefully the next update fixes, I'm hoping it doesn't happen again, major time wasted searching the internet for a solution
Click to expand...
Click to collapse
But yeah definitely back up to a computer or something and/or Google all your stuff before you decide to software repair. If you don't have one maybe factory reset it because I honestly think they're same thing I could be wrong though but I couldn't find any difference on the internet between the two.
Click to expand...
Click to collapse
I am SO glad I found this thread and it's not just me having this issue.
I originally thought it was Google Voice messing with my phone, since I make calls and texts from Google Voice, and have my incoming TMobile calls and outgoing TMobile calls redirect to be to/from my Google Voice number. But even after removing Google Voice and completely unlinking it from my phone, my phone refuses to do VoLTE calls.
When receiving a call, the phone will drop down to HSPA+ and sometimes, it takes so long for it to do this, my phone only rings once before I just end up getting a missed call notification. Meanwhile, the caller says they were ringing for the full 30 seconds. Similarly when I make a call, the phone drops down to HSPA or even EDGE to make a call. When I hang up, or get off a call, boom, back to LTE or LTE+.
I went to a TMobile store and they gave me a new SIM and fiddled with my APN settings, to no avail. I haven't bothered contacting Sony, since I figure they will just blame TMobile. The only thing I haven't tried is the factory reset, which is something I very much wanted to avoid, but I'll try it with the Xperia Companion software and keep my fingers crossed. I'll update with my results.
In the meantime, I'm attaching some screenshots of my device info showing the VoLTE is indeed enabled, as well as my APN settings. Maybe they'll help someone here. (WiFi calling is apparently not a thing on this phone, which is disappointing, but I also have Google Voice under normal circumstances, so that hasn't been a problem for me).
GrumpyFox said:
I am SO glad I found this thread and it's not just me having this issue.
I originally thought it was Google Voice messing with my phone, since I make calls and texts from Google Voice, and have my incoming TMobile calls and outgoing TMobile calls redirect to be to/from my Google Voice number. But even after removing Google Voice and completely unlinking it from my phone, my phone refuses to do VoLTE calls.
When receiving a call, the phone will drop down to HSPA+ and sometimes, it takes so long for it to do this, my phone only rings once before I just end up getting a missed call notification. Meanwhile, the caller says they were ringing for the full 30 seconds. Similarly when I make a call, the phone drops down to HSPA or even EDGE to make a call. When I hang up, or get off a call, boom, back to LTE or LTE+.
I went to a TMobile store and they gave me a new SIM and fiddled with my APN settings, to no avail. I haven't bothered contacting Sony, since I figure they will just blame TMobile. The only thing I haven't tried is the factory reset, which is something I very much wanted to avoid, but I'll try it with the Xperia Companion software and keep my fingers crossed. I'll update with my results.
In the meantime, I'm attaching some screenshots of my device info showing the VoLTE is indeed enabled, as well as my APN settings. Maybe they'll help someone here. (WiFi calling is apparently not a thing on this phone, which is disappointing, but I also have Google Voice under normal circumstances, so that hasn't been a problem for me).
Click to expand...
Click to collapse
Yeah someone explained to me that Software Repair is different from Software Reset . It's what i did to fix this issue i hope it fixes it for you as well. I know how much of a hassle and time wasted on this is
charlie313 said:
Yeah someone explained to me that Software Repair is different from Software Reset . It's what i did to fix this issue i hope it fixes it for you as well. I know how much of a hassle and time wasted on this is
Click to expand...
Click to collapse
I also couldn't find anything to help me and as soon as i posted on here and reddit out came people like you with the same issue. Glad i posted and hope everyone who's done a software repair has fixed the issue. Happy Holidays
charlie313 said:
I also couldn't find anything to help me and as soon as i posted on here and reddit out came people like you with the same issue. Glad i posted and hope everyone who's done a software repair has fixed the issue. Happy Holidays
Click to expand...
Click to collapse
I'm in the process of doing the "Repair" now. Hopefully this fixes it. If it does, 1- Awesome! 2- Hopefully it doesn't get borked again when Android 11 rolls around. It's supposedly making its way to the 1ii, but I personally haven't gotten it yet.
GrumpyFox said:
I'm in the process of doing the "Repair" now. Hopefully this fixes it. If it does, 1- Awesome! 2- Hopefully it doesn't get borked again when Android 11 rolls around. It's supposedly making its way to the 1ii, but I personally haven't gotten it yet.
Click to expand...
Click to collapse
Yeah that's what I'm afraid of too i don't want to be reinstalling all my stuff again. If it happens to get stuck on you while you're doing the process just try again. Mine froze during the restarting part of the repair i just held the volume and power button at same time to hard reset it
charlie313 said:
Yeah that's what I'm afraid of too i don't want to be reinstalling all my stuff again. If it happens to get stuck on you while you're doing the process just try again. Mine froze during the restarting part of the repair i just held the volume and power button at same time to hard reset it
Click to expand...
Click to collapse
Yup. My device appears to be bricked. The repair failed on my PC and now when attempting to turn the phone on, I'm met with "Your device is corrupt. It can't be trusted and may not work properly. It will shut down in 5 seconds."
I'm attempting to get it to boot into recovery.
I never imagined my first experience with a Sony phone would be so bad.
GrumpyFox said:
Yup. My device appears to be bricked. The repair failed on my PC and now when attempting to turn the phone on, I'm met with "Your device is corrupt. It can't be trusted and may not work properly. It will shut down in 5 seconds."
I'm attempting to get it to boot into recovery.
I never imagined my first experience with a Sony phone would be so bad.
Click to expand...
Click to collapse
Yeah just horrible luck. Still prefer a software problem over a house fire like that samsung fiasco but still . Yeah just keep trying I'm sure there are ways to factory reset it and then software repair it.
R
....and Never forget its
"Enable VoLTE when available"
There might be the network issue too.
I'm in Nepal and the carrier has started VoLTE few days ago but they haven't listed my phone for VoLTE supporting device . They just have iPhone, Samsungs, Xiaomi etc and not SONY but you know what... Its working for me.
HD voice and LTE while in a call too.
Glad I found this thread. I've got an Xperia 10+ doing the same thing under Lineage 18.1 (Mermaid). Will give this a shot and see what happens. Hopefully I don't brick it.