Related
Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
chino0131 said:
Mine wouldn't activate for the first 20-30 minutes or so. I removed the sim card, reinstalled then went on the website and updated the Note 3 in formation for my line. Had keep refreshing my lines info on the Web page about 2 more times and hit accept before it Finally activated. Took about 5 additional minutes after removing the sim. Not sure if that will help, but hope you get it working.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well seeing as how I got mine on 10OCT2013 at 10 am and it still hasn't activated, I think it's not going to at this point. I may sadly have to go back to my GN2 and return the GN3 altogehter. :crying:
Mine seemed stuck on activation, ended up using my old sim card, activated almost instantly.
Update: just got off phone with Big Red and they said that for some reason when I'm on my "home" towers, my activation has trouble letting go of the GN2?? Maybe it really is hard to say good-bye...
They are working on it now...
I've always had an issue activating my old number on a new phone with a new SIM.... I've always just switched my old SIM card in and it's worked perfectly lol
Make sure the SIM card has been linked correctly to your phone number. The easiest way is to look on the VZW paperwork that came with the phone and make sure it's your phone nbr and not another person's on your plan.
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
I had an activation problem in store yesterday when swapping my note 2 for note 3. The sales rep entered the sim card info that was on the sticker on the box for the sim card that comes with the phone.
It all ended up causing major activation / service connectivity issues because the sim card info on the box did Not match the actual sim card number for the sim pre-installed on the phone.
This is apparently an issues for some other people as well. If the sim card in the phone is not reconciled with the info on the box prior to entering the info into Verizon's system.... You will be in for a time consuming headache
Sent from my SM-N900V using xda app-developers app
urielsynthesis said:
I am having more or less the same issue.
To make a long story short, whenever I leave the "home" cell tower that the phone was activated on, it will not connect to any kind of network whatsoever. It just shows a circle with a line through it, and at the same time it reboots itself, randomly and frequently, even when it isn't being touched. All of these problems go away as soon as I get back home to that cell tower. I wonder if the original poster activated his phone at work the first time, and that's why it only works when he returns to work?
I have tried 3 different SIMS to fix this: the one that came in the GN3, the one from my old Galaxy Nexus, and a brand new one from a Verizon store. I have done half a dozen factory data restores.
My next step is to try an in-store swap. A local store around here first refused to hold a phone for me to swap, then when I got there (or rather when a family member got there), we were told that there was a master ticket for this issue and there was a freeze on doing any exchanges until Samsung released a "fix". My subsequent conversations with Verizon tech support have confirmed that the whole story about a master ticket and not doing exchanges was a complete lie. The stores are actually required to uphold the 14 day worry free guarantee no matter what. Obviously this store didn't want to give up a phone to me that they could sell to someone else. They weren't just being unhelpful, they were running interference on resolving my problem for their own greed.
Click to expand...
Click to collapse
Switching your device or SIM will not work. I have now gone through 6 GN3's and almost 20 different SIM cards. It's the towers/service from Verizon. They have noted that this is a problem and are working diligently to fix it...lol Meanwhile, I've returned my GN3 and will wait until they fix this disaster. This rollout is almost as bad as Obamacare...haha
dead batteries said:
Hey all, I just got my GN3, still am using the GN2 though BC Verizon can't get the phone to activate to my phone number? Actually Verizon says it show the GN3 activated, but l have no service/phone/data/anything at all. They tried 5 different GN3's and 13 different SIM cards before they gave up trying to activate. My number works/activates just fine on my GN2. So they gave me a temporary number yesterday to see if it was a problem with my particular phone number and sure enough, my GN3 activated on the temp number. When I switched back to my reg # it wouldn't connect...again. Then I went to work which was about 10 miles away and the GN3 activated on my reg#. I called my wife, made a few texts, surfed the net, etc... for about 2 hours, when I got about 8 miles from home, I lost all connection again... What gives here? It's the weirdest problem I've ever seen. I'm home now, and tried activating it again with no luck. Any thoughts??
I'm sorry if this is the wrong forum for this thread, if so please move??
Click to expand...
Click to collapse
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
nimitch said:
Mine kept trying to activate on the phone and would continually fail.
I thought I had a faulty device and was going to go to the store. Something told me to login to MyVerizon online on my computer [since I kept my old phone off as directed via the on-screen instructions] and poke around and see if there was anything there that might be able to help me.
I clicked on my line, and the Manage My Device link on the left hand side of the screen and ended up being able to complete the activation via the website. Re-booted the phone, and then voila~! Activation complete.
FYI, I was migrating from an iPhone 5 to the GN3.
Click to expand...
Click to collapse
Yeah I tried that as well. I'm not sure there is anything I haven't tried. I've returned my device and decided to stick with my Note 2. Maybe when Verizon gets their heads on right and fixes this, I'll come back.
I have a Tmobile G2 that I just got a week ago. I played around with it for a couple days before deciding to root it, but finally pulled the trigger. Two days after rooting it a very strange thing happened. In the middle of the evening some of my Google applications stopped syncing. Gmail, Voice, and Contacts stopped. Drive still worked. Hangouts still worked... It was just weird. I clicked around for awhile and hit the interwebs to find the solution or to see if there was some widespread google outage again, but nothing.
I did everything I could think of, and then I finally clicked the option to take the phone back to stock. I know it wasn't going to take away my root, but at this point I wasn't thinking root was the problem. I just thought maybe I installed something that messed up the phone or something. Anyway, I took it back to normal and now the problem was weirder. It wouldn't even let me connect my Google account (or any google account) to the phone. It kept saying there was some sort of server error. I called TMO support and they couldn't figure it out either. They gave me a number to call Google support to let them fix it. They said that this was a 'known issue' and google support would be the one to fix it.
I kind of got nervous that they were going to creep into my phone or something and void my warranty. If my phone was broken and wouldn't connect to Google anymore then I at least wanted to be able to return it to the store and get a new one. I kinda like this device. So I un-rooted it and took it way back to stock. That fixed the problem. I don't know why, but it did. It left SU on the phone, so I'll have to get that off if it has issues again, but for now it is working fine.
Any idea why it would have just suddenly stopped connecting to Google? It connected to Drive just fine and several other apps, but the important ones wouldn't work. Unrooting it did the trick, but that would suck if you have a really great setup built. Oh well... The price you pay for being a hacker I guess.
ocdetails said:
I have a Tmobile G2 that I just got a week ago. I played around with it for a couple days before deciding to root it, but finally pulled the trigger. Two days after rooting it a very strange thing happened. In the middle of the evening some of my Google applications stopped syncing. Gmail, Voice, and Contacts stopped. Drive still worked. Hangouts still worked... It was just weird. I clicked around for awhile and hit the interwebs to find the solution or to see if there was some widespread google outage again, but nothing.
I did everything I could think of, and then I finally clicked the option to take the phone back to stock. I know it wasn't going to take away my root, but at this point I wasn't thinking root was the problem. I just thought maybe I installed something that messed up the phone or something. Anyway, I took it back to normal and now the problem was weirder. It wouldn't even let me connect my Google account (or any google account) to the phone. It kept saying there was some sort of server error. I called TMO support and they couldn't figure it out either. They gave me a number to call Google support to let them fix it. They said that this was a 'known issue' and google support would be the one to fix it.
I kind of got nervous that they were going to creep into my phone or something and void my warranty. If my phone was broken and wouldn't connect to Google anymore then I at least wanted to be able to return it to the store and get a new one. I kinda like this device. So I un-rooted it and took it way back to stock. That fixed the problem. I don't know why, but it did. It left SU on the phone, so I'll have to get that off if it has issues again, but for now it is working fine.
Any idea why it would have just suddenly stopped connecting to Google? It connected to Drive just fine and several other apps, but the important ones wouldn't work. Unrooting it did the trick, but that would suck if you have a really great setup built. Oh well... The price you pay for being a hacker I guess.
Click to expand...
Click to collapse
Google had problems with their servers, many services were unavailable... had most probably nothing to do with you rooting...
You just picked the right time to do that.
Google from time to time have some problems. But not related to rooting.
PAGOT said:
Google had problems with their servers, many services were unavailable... had most probably nothing to do with you rooting...
You just picked the right time to do that.
Google from time to time have some problems. But not related to rooting.
Click to expand...
Click to collapse
That's kind of what I thought, but it was miraculously healed when I unrooted it. It could have just been strange timing, but there was nothing on the web about anybody else having this issue. I'll root it again and see what happens. There are some definite advantages to root access that I don't want to lose, but getting my email and texts are pretty important too, so....
ocdetails said:
That's kind of what I thought, but it was miraculously healed when I unrooted it. It could have just been strange timing, but there was nothing on the web about anybody else having this issue. I'll root it again and see what happens. There are some definite advantages to root access that I don't want to lose, but getting my email and texts are pretty important too, so....
Click to expand...
Click to collapse
Seriously??? The web was full of it ...
read here for example http://techcrunch.com/2014/01/24/gm...mails-to-be-sent-to-one-mans-hotmail-account/
http://techcrunch.com/2014/01/24/gmail-goes-down-across-the-world/
PAGOT said:
Seriously??? The web was full of it ...
read here for example http://techcrunch.com/2014/01/24/gm...mails-to-be-sent-to-one-mans-hotmail-account/
http://techcrunch.com/2014/01/24/gmail-goes-down-across-the-world/
Click to expand...
Click to collapse
I'm talking about this past Saturday morning, though. February 1st. I know about the google issue a week or two ago, but this was only affecting my mobile apps and wasn't the same thing. I was able to access gmail on the computer just fine. I could even access it from the phone's browser fine, but connecting the Google account to the phone was not possible. All I kept getting was 'cannot make a reliable connection to the server' error, so that is why I took the phone back to stock and then all the way back to unrooted. Unrooting it solved it, so I don't think it was just a google server issue which only affected me between the hours of 7:30 on Friday night till Saturday afternoon when I finally gave up and unrooted. It could have been connected, but I doubt it.
Which rooting guide did you follow?
Sent from my LG-D802 using Tapatalk
ocdetails said:
I'm talking about this past Saturday morning, though. February 1st. I know about the google issue a week or two ago, but this was only affecting my mobile apps and wasn't the same thing. I was able to access gmail on the computer just fine. I could even access it from the phone's browser fine, but connecting the Google account to the phone was not possible. All I kept getting was 'cannot make a reliable connection to the server' error, so that is why I took the phone back to stock and then all the way back to unrooted. Unrooting it solved it, so I don't think it was just a google server issue which only affected me between the hours of 7:30 on Friday night till Saturday afternoon when I finally gave up and unrooted. It could have been connected, but I doubt it.
Click to expand...
Click to collapse
I'm having the same problem. I deleted my account and recreated it. But auto-sync does not work. This has nothing to do with syncing. That works - but I have to sync manually. If I manually sync it from either the app or from the accounts option in settings it works fine. But it won't sync again. I deleted the account, restarted the phone and added the account again. Still doesn't work. If you root it and run into the same problem, please post again. I'll unroot too then.
I know this used to work at some point. I don't know when it stopped working. But it's not been working for days now.
mrm43 said:
Which rooting guide did you follow?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I don't recall. The root part worked fine. I was able to use several of my apps which require root access and they all worked fine for a couple days. It just seems really random that this would all stop working one day.
So here is the timeline.....
Monday 1/27/14 - phone arrives
Wednesday - Rooted
Friday evening - Strange sync issues
Saturday morning - restored to stock while keeping root (did not solve problem and now I cannot connect any google account)
Saturday afternoon - unrooted and restored device (solved problem and google account synced fine after)
That was all in the same week. I've only had the phone since last Monday. It is worth saying that my HTC G2 and my wife's HTC G2 didn't have any issues with google syncing during this time. Totally different products, but I really tried to find anything to link the problem to something systemic and not just a device issue.
I haven't rooted it again just yet. I need to do it before I go too nuts re-installing the apks on my machine anyway. I'll definitely post again if I have problems again, but I really want to believe it was just something left over from whatever bug plagued Google a couple weeks ago.
Okay, so my old phone basically broke after I updated to 4.4.4, my service was absent almost everywhere, my bluetooth went in and out, my phone was slow and froze constantly, and my battery could drain completely in like 30 minutes if I didnt turn everything off and hardly use it, then it would maybe last a few hours. So I got a replacement through Verizon, and lo and behold, it came with 4.4.2. My last post was about me trying desperately to root, but I couldnt because of my 4.4.4 update. So I was thrilled. I transferred all my stuff, and actually managed to use towelroot and it worked.
Then, my phone automatically downloaded the update, and I couldnt figure out how to stop the update popup or notification. Nothing I tried worked, and I downloaded a few apps to try and turn it off. Disabling or etc Google Services Framework does nothing, but somehow, everything else I did managed to make the phone basically unusable. I get two errors: "Unfortunately, the process com.google.process.gapps has stopped." and the same one but about Google Play Services. I tried to undo what I did but it didnt fix it. I reset my phone to factory settings, and while that stopped the downloaded update from popping up, i cant use it because the popups are there literally every 2 or 3 seconds. I cant navigate through a menu without tapping a hundred times, usually on the wrong buttons. I dont have wifi on, so the ota update hasnt downloaded.
Im going to probably take it to Verizon tomorrow and ask them if I can just get a replacement replacement, but I hate having to do all that, because I might have to wait even longer now. If somebody has any idea how to fix google play services, please tell me. I reenabled them, cleared data and cache, force stopped them, turned them back on, nothing fixes it.
Also, I desperately need to know how to prevent an update from downloading, and how to get rid of it once it is downloaded. Ill have root access, but none of the methods Ive googled have worked, please help me, Im so frustrated with Verizon and Samsung all this bull**** now. Why cant they just let us enjoy our devices?
First off a Verizon store will not give you a new phone unless you are inside of 30 days of a new purchase. Ofirst din 4.4.2 to give it a clean start. Re root phone. Then disable sdm which will stop all ota updates.
No, Verizon will give you a replacement if you have their insurance. I've gotten dozens this way. As long as there isn't any serious physical damage like obvious scratches or cracks, water damage, or anything similar they overnight you a brand new device.
I have two phones in my possession right now, on Monday I'll have a third. I went in and showed them the replacement, they seemed confused, but they always do. They told me to just send back the broken replacement and went ahead and put in for a new one, which Ill get Monday since tomorrow is no post.
So that problem is solved.
Ill try what you suggested when I get my replacement. I've never rooted beyond the towelroot I mentioned before, so this is all new to me. It seems like some methods I've seen only work on certain phones, so thats what Im worried about.
Do you think you could give me more specific instructions, because I have no idea what everything you said meant. Im just tired of googling everything you know? Id appreciate it!
Thank you for the reply!
drewcam888 said:
First off a Verizon store will not give you a new phone unless you are inside of 30 days of a new purchase. Ofirst din 4.4.2 to give it a clean start. Re root phone. Then disable sdm which will stop all ota updates.
Click to expand...
Click to collapse
When I first got my s7 Edge, I was able to add both my wells fargo card and chase card into Samsung pay without any issues. (It's how i was able to redeem the wireless charger promotion)
However, after a new Samsung update, the app completely reset itself and I had to re-add the cards again. Not a problem. I was able to add my wells fargo card without any issue. However, when I tried re-adding my chase debit card, I was greeted with a "Problem with connecting to card holders server" issue. Has anyone else experienced this? I've uninstalled, reinstalled, cleared the cache from the app and I'm still having issues with just that card. I even tried adding my girlfriend's Chase card to see if my card was the issue and I'm still greeted with the same code. It's extremely annoying, especially since I knew before I was able to add it in without any problems.
Surprised you got it on first time. Cannot add mine and told that Chase is not supporting Pay at this time. Have new Explorer United card.
Chase was probably having down time on their servers, they do it REALLY frequently. I think it's every Sunday evening. Chase needs verification before Samsung will add the cards. Just give it time and try again later.
It turns out they are not supporting business cards like mine. Moved over to it to get 20000 extra United miles - didn't see this coming. My older personal card would have worked.
Negative, I've tried at different times and i'm still greeted with the same error. I'm surprised that it worked the first time and now I'm having issues. In fact I tried right now and it still wouldn't go through.
I just got the OTA update from AT&T for my V35 to Android 10. Now, whenever I try to Share from an app and the system Share panel is invoked, the Share panel starts to populate and then crashes and often takes the app with it. The only app that I can Share from now appears to be Firefox, but that doesn't appear to use the system Share but has its own.
Any ideas what could be going on? This is happening for my and my wife's phones (both V35). I contacted AT&T chat support and all they gave me was canned answers and then ended the chat; useless.
UPDATE 1: I found the problem with both phones is GroupMe. On the one phone I was able to get things working again by clearing the cache and data for GroupMe, uninstalling it, reinstalling it, and logging back in. For the other phone, this didn't work. I can Share when GroupMe isn't logged in, but once I log in, the Share crashes while populating. The only difference between the working phone and broken phone is that the working phone has a GroupMe account linked with Microsoft and the non-working phone has its GroupMe account linked with Google. So, it appears that a Google-account-GroupMe + Android 10 + Share is the broken combination. Now I'm really at a loss here.
UPDATE 2: Apparently I'm not the only one: https://www.reddit.com/r/AndroidQue...e_causing_android_system_share_menu_to_crash/
UPDATE 3: While GroupMe logged in with Microsoft was allowing Share to work on my phone for a while, Share has since stopped working while I'm logged into GroupMe. When I delete the data for GroupMe, I can share again. I've emailed GroupMe support about this matter and will report back. I'm currently running the latest version of GroupMe from the Play store: 5.47.4, released May 19, 2020
UPDATE 4: I've chatted with AT&T support a few more times. The first time was with Oliver, and that didn't go very well. I did manage to get a case number though. I was told that update V350AWM20i would be pushed to my phone in the next 24 hours which would fix the issue; I already have V350AWM30c, which is newer. I then spoke with Mike in a second chat session (which I started because Oliver hung up on me) and was told that my case has been escalated and I should at least hear back from AT&T in 24 hours. I'll keep updating this.
For sure GroupMe shouldn't be causing Android to crash, but Android shouldn't crash because of a bad app. IMO, both parties are at fault here.
UPDATE 5: I contacted AT&T today (they didn't contact me as they said they would) and they now say that I'll have a resolution by the 27th. GroupMe hasn't returned my request for support.
UPDATE 6: I contacted AT&T yesterday, the 26th, and they said that an update that would be pushed to my phone to fix the problem. They didn't know the version of the update that would be pushed. The update never came. Today, the 27th, I contacted AT&T again and they said that my case was closed and the the update was pushed. They said they pushed the latest version of Android Pie to my phone. So, here we go again. They decided they would re-open the case and would investigate my issue. For some reason they were under the impression that I opened a support ticket to get an update to Android 10. No one that I spoke with today could even tell me what my issue was, even after they read this post. I was transferred to another support agent where I sat for about an hour before quitting the chat. I only saw "Agent is typing..." and "Agent stopped typing" once, after about 45 minutes, but no actual interaction from the agent.
In other news, GroupMe has started replying to my request for support and apparently they can't open x265-encoded videos of a screen recording I took of the problem that they requested. I've sent them an x264-encoded screen recording to see where this goes.
UPDATE 7: I ended up calling AT&T support (866-344-6217) and spoke with a very helpful person who was able to correctly identify the problem and is escalating it to others, possibly LG, to see if the problem can be addressed. A remote control session was done with my phone where the problem was clearly reproduced. Such was the case even after clearing various cache and data for the app, web view, and system. I was informed that the problem will likely be solved by a hard reset of my phone. Apart from the obvious reason why I don't want to do that, the fact that this affects two of my phones the same indicates that it is an endemic software problem that should be addressed less this roll-out causes more problems for others. Since my phone has such a reliable reproduction and I need to schedule time to reset my phone, I'm holding off on doing this until I hear back about the escalations that AT&T is taking, which I'm expecting today, the 28th based on our conversation.
If anyone knows how to contact LG on this matter, or even AOSP, I'm all ears. It still should never be the case that a logged-in app should be able to crash the Share function in Android.
UPDATE 8: I just (8:49 am CST, May 28th) received a text message from AT&T saying that they were closing my "Urgent Case"; I was never called to inquire if my issue was resolved. Hopefully I'll still get the phone call I was promised later today.
UPDATE 9: I heard back from AT&T and they continue to work the issue. For reference, the model of my device is LM-V350AWM and it is SIM unlocked.
UPDATE 10: Microsoft GroupMe released an update to version 5.47.5 today which resolved the problem on my wife's phone. Thus, there are two solutions to this problem: 1) the comment below about turning off and on "Direct Share", and 2) installing the update for GroupMe. The reason why any installed app could cause the Android system to crash is still beyond me and hopefully is something that AT&T, Google, and LG can work out.
This happened to me last nite. I'm still on 9. Drove me cray untill I rebooted. Now I have some random app stop pop-ups, but sharing is fine.
Sent from my LM-V350ULM using Tapatalk
I had a similar issue. I had to disable the "direct share" and "nearby devices" under settings > network > sharing panel.
Oddly enough after verifying this fixed my issue I was able to re-enable them and sharing was still working.
wizardofwoz said:
I had a similar issue. I had to disable the "direct share" and "nearby devices" under settings > network > sharing panel.
Oddly enough after verifying this fixed my issue I was able to re-enable them and sharing was still working.
Click to expand...
Click to collapse
This absolutely worked. I'll continue watching to see if the problem returns as GroupMe contacts work their way back into my Direct Share list. I do find it strange this came up after the upgrade. It seems that the upgrade process didn't reset/flush something related to the list of contacts related to GroupMe.