Related
I just purchased the sII skyrocket 2 weeks back. About every 2 days the phone would stop receiving calls. When i get a call it would ring a half ring and then at the top where it shows the signal would have a no sign on it like there was no service. Once its goes in to this mode it would stay in it until i reboot the phone. The problem is that i never actually know who is calling because it never logs a missed call. This is the first i have seen this on any andriod phone. Here is some additional info, Stock Rom, Phone is rooted, i have the following apps frozen using TBP
Allshare
At&T code canner
At&T hotspots
At&T navigator
At&T ready 2 Go
Featured Apps
Kies Air
Kies via Wifi
Kobo
NFC service
NFC Test
QIK Lite
QuickOffice
Social Hub
Tethering Manager
Any thoughts? I should add that its not specific to one contact it will happen to anyone that calls, i have tested this calling from my wifes cell to mine when it was in this mode and saw it happen constantly. Rebooted sitting in the same place phone received calls.
no feedback yet from community but i thought i would post an updated.
I contacted AT&T that suggested it could be the SIM card, I went to the store tonight and changed out my SIM. I will update this if the issue goes away so in case some one has something similar they know what a potential fix could be.
Interesting.
Did you get a new SIM card when you get the Skyrocket as well?
I know they issued me a new SIM card at purchase because of the LTE upgrade.
yep they gave me a new sim card when i purchased it said the old one wasn't compatible. So the one i just received replaced the new one that is about 10 days old.
just to update this, this seemed to have fully fixed my issue.. since i swapped the sim there have been no issue
Your SIM was probably dying out, it happens.
Glad to see your issue was fixed, I was thinking you were having LOS, same as the Sprint SGS II.
Yeah just another update thread. Who here is still getting the no sim error after installing the update it is now worse for me! I am more of a reader and not a poster im just curious is there a work around for this like for example has anyone installed a rom and the problem went away?
LIttle Rant: I have had nothing but motorola smartphones Droid X, Droid Bionic, Razr Maxx so I got curious since the S3 is one of the top selling phones to check it out and let me tell you love the phone but getting that stupid error all the time is annoying I picked my s3 up thinking I could make a quick sell on my razr maxx but now im stuck switching back and forth between the S3 and the razr maxx Verizon even sent me a replacement did that help? nope now its been 3 days they have a ticket open so who knows any help would be apprectiated and lets hear your story!
I'm still getting it, even worse than before I installed the new modem (radio). It seems to be more prevalent in areas where it's switching from 4g to 3g and back. If I'm in an area that has a strong 3g or 4g signal, it never gives me that problem. Has to be a Verizon thing or something with the SG3 that can't handle the switching between the two modes, just not sure......
amaury48 said:
I'm still getting it, even worse than before I installed the new modem (radio). It seems to be more prevalent in areas where it's switching from 4g to 3g and back. If I'm in an area that has a strong 3g or 4g signal, it never gives me that problem. Has to be a Verizon thing or something with the SG3 that can't handle the switching between the two modes, just not sure......
Click to expand...
Click to collapse
UPDATE: I can confirm that if I place myself in a particular position in town where my phone will constantly switch between 3g and 4g and I attempt to send SMS messages my phone inevitably drops all data signal and gives me the no sim and no connectivity message.
I haven't been to were I used to get them bad....but I got one in an area yesterday where I generally get a strong 4G single that I had never had the no SIM issue before.
I was not happy.
galaxy. s3. synergy. yadda yadda.
I am getting it all the time at my house sometimes to the point where the phone does not work at all but if I drive down the road phone works flawless no errors even at work no errors im starting to think it might not be the phone it could be there network but for the hell of it lastnight I switched back from my razr maxx at home and the phone worked fine and when I woke up phone was fine im wondering if this only happens when the network is more at peak operation im growing very frustrated with this phone might off it and just use the razr maxx or hope for another update.
jparasita said:
I am getting it all the time at my house sometimes to the point where the phone does not work at all but if I drive down the road phone works flawless no errors even at work no errors im starting to think it might not be the phone it could be there network but for the hell of it lastnight I switched back from my razr maxx at home and the phone worked fine and when I woke up phone was fine im wondering if this only happens when the network is more at peak operation im growing very frustrated with this phone might off it and just use the razr maxx or hope for another update.
Click to expand...
Click to collapse
I had the same situation just moving from one room to another in my house. Yesterday evening I received a text from my neighbor asking if I had noticed we were receiving a 4g signal in our area (we are in a rural area about 12 miles outside of Tallahassee, FL.). Since yesterday I have a solid 4g in my home area so the no sim problem has disappeared. But there are pockets of weak coverage areas on the way to work in town and at the Florida State University where I work and I continue to find small areas where the problem persists. It has to be the SG3's inability to handle the hand-offs between 3g/4g which produce the no sim problem. My Thunderbolt would handle the switching from 3g/4g much better and not produce the no sim error. I'm sure Samsung could remedy this with a software change (at least not display the no sim) when switching service.
I still have the error on 2 phones. Funny thing is it seems that now it is worse on my wifes phone where it was the other way prior to the update.
From reading this thread and similar threads/topics regarding the sim errors with the GS3, I figured I'd post this here. This is confirmed, my friend and I both have a GS3 bought on the same day at the same VZW store. She keeps getting a sim error while I have never gotten one regardless of coverage or 3G/4G switch frequency, I frequently switch from 4G to 3G when on the subway. She went into the store and requested a new sim card, wound up arguing with the rep, according to him there's no possible way the error could be related, she finally got a new card by calling reps at various levels. After doing a factory reset and reprovisioning the internal SD card with the new sim, she has not yet had a sim error with the newest OTA. So it seems many Verizon sim cards aren't necessarily defective, but are improperly configured with the VZW network. This is just an educated guess based off personal experience, hopefully this is helpful to those with frequent sim errors.
Sent from my SCH-I535 using xda app-developers app
Shibby87 said:
From reading this thread and similar threads/topics regarding the sim errors with the GS3, I figured I'd post this here. This is confirmed, my friend and I both have a GS3 bought on the same day at the same VZW store. She keeps getting a sim error while I have never gotten one regardless of coverage or 3G/4G switch frequency, I frequently switch from 4G to 3G when on the subway. She went into the store and requested a new sim card, wound up arguing with the rep, according to him there's no possible way the error could be related, she finally got a new card by calling reps at various levels. After doing a factory reset and reprovisioning the internal SD card with the new sim, she has not yet had a sim error with the newest OTA. So it seems many Verizon sim cards aren't necessarily defective, but are improperly configured with the VZW network. This is just an educated guess based off personal experience, hopefully this is helpful to those with frequent sim errors.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How do you reprovision the internal SD card with the sim? If you are correct, some people may be able to fix the problem by doing so with their existing sim cards.
eagene said:
How do you reprovision the internal SD card with the sim? If you are correct, some people may be able to fix the problem by doing so with their existing sim cards.
Click to expand...
Click to collapse
I would also LOVE to know how to do this!!! Very frustrated with this!! Hopefully reprovisioning the sim finally works!!
After searching around, I found to reprovision, you need to go to stock and dial this in the dialar, *2767*3855#. My question is,
- Is it def not possible to do this from an AOSP rom?
- When they say "go to stock", can I just flash a TW based rom and do it?
reprovisioning does not work, don't waste your time
ripken204 said:
reprovisioning does not work, don't waste your time
Click to expand...
Click to collapse
Agreed, I have reprovisioned before, to no avail. I thought it might be my SMS client, GO SMS, but I am getting the same NO SIM error with that client that I get with Handcent as well as the stock messaging client.
I called Verizon back today, to note my account that it's still happening, and spoke to them about a replacement phone. (I am already on my second S3 and second SIM) They offered me my choice of Android device, which currently is a bad deal. So I asked them if their deal would hold true once the Note 2 came out, and the nice lady at level 2 support said yes.
So unless this gets fixed prior to the Note 2... a switch is almost inevitable for me.
Dont waste your time doing the reprovision does not work I tried it earlier today.
mdt73 said:
Agreed, I have reprovisioned before, to no avail. I thought it might be my SMS client, GO SMS, but I am getting the same NO SIM error with that client that I get with Handcent as well as the stock messaging client.
I called Verizon back today, to note my account that it's still happening, and spoke to them about a replacement phone. (I am already on my second S3 and second SIM) They offered me my choice of Android device, which currently is a bad deal. So I asked them if their deal would hold true once the Note 2 came out, and the nice lady at level 2 support said yes.
So unless this gets fixed prior to the Note 2... a switch is almost inevitable for me.
Click to expand...
Click to collapse
Interesting...I might be doing the same thing. This issue is beyond frustrating. However, I have not called Verizon about it yet. Mainly because there doesnt seem to be a fix. I dont want a refurb S3 and there currently isnt a valid replacement. Might try the Note 2 if its possible.
dmbfan13 said:
Interesting...I might be doing the same thing. This issue is beyond frustrating. However, I have not called Verizon about it yet. Mainly because there doesnt seem to be a fix. I dont want a refurb S3 and there currently isnt a valid replacement. Might try the Note 2 if its possible.
Click to expand...
Click to collapse
call verizon just so that they can put a note in your account.
vzw put a note on my account and I should be able to just call up and replace my S3 with something new... just have to wait for something good to come out
ripken204 said:
call verizon just so that they can put a note in your account.
vzw put a note on my account and I should be able to just call up and replace my S3 with something new... just have to wait for something good to come out
Click to expand...
Click to collapse
100% agree with Ripken... call them and have them note it in your account. Basically, I am documenting it once per day (it happens more, but calling more than once per day seems redundant) so they see it, but more importantly, I have some ammunition if I finally move to a new phone. Today's call to 2nd level tech support was a bit frustrating to me, as the nice lady said that, in fact, verizon did get a bad batch of SIM cards. When I pointed out that the bad batch must have been sent all over the country, because it's not a localized issue, and there was a software update addressing it... she didn't have a response. We went thru the same rigamarole with the phone... ie pull the battery, read the number on my SIM, read the numbers from my software build, etc. Again, she offered me any Android phone in exchange, which I turned down. But, at the end, she mentioned she was sending this issue up to a different tier of support that (her words) works with Samsung to fix these issues. I kindly asked her to have them address the headphone jack - bluetooth non-coexisistance, which she giggled at but assured me was working as intended.
So, back to waiting for a fix... or an inevitable new phone.
VRLHD Modem
Ok guys try this at your own risk! I might have found a fix looks like there is another modem floatng around called VRALHD I just flashed it in odin and guess what my phone seems to be working good here at home so try this at your own risk!
Download Link:
http://goo.im/devs/invisiblek/i535/modems
also if you google VRALHD modem galaxy s3 something will come up I cant confirm for sure this will help I will report back after some usage between now and tommorow.
Here it is on rootzwiki
http://rootzwiki.com/topic/34053-of...zon-sgs3-sch-i535-odin-or-recovery-flashable/
Guess I had high hopes for that modem does not fix the issues nevermind lol I am hoping when the jellybean update hits with a new modem this will fix the problem the waiting game begins.
Installed the HD modem last night. I have one area at work that I can test it. I'll report back later with my results.
Update: Flashed the HD radio last night (in CWM touch recovery), install went fine. Didn't have an opportunity to check it out till this afternoon when I put myself in a exact known location where I could reproduce the 3g/4g constant hand-off with the "no sim" notification. Sent out 6 text messages and a couple of phone calls with no problem. Either this new radio did the trick for me or it may be coincidental that Verizon has corrected this "dead" area that would produce this problem without fail everyday I was at work. Couldn't tell you for certain. All I know is that it's not happening anymore at this particular location. I used to have the "no sim" "out of area" notifications constantly at my home until just last week when Verizon finally covered this area with a strong 4g service. Only time will tell as I travel thru areas that have weak coverage. It's very obvious that this problem stems from weak coverage areas and the SG3's inability to handle the transfers effectively.
I picked up a mint verizon s3 local on a trade for some scrap phones I had. So here is my issue. I put in a sim(at&t) and got the switch to global notification but it never gets signal. Phone info shows -120dbm 99asu. Figured since it was free I would play with it and installed hyperdriver rls 16 still nothing. Took everything back to the first stock ics nothing. Currently have it on jb 4.1.1 nothing. I started to wonder if the radio was trashed so I dialed 911 with no sim in the phone and it popped up 3 bars and made the call.
Am I wrong in thinking this phone will work on US networks with a sim? Anyone ran into this problem possibly can maybe point me into a direction to get it working. The phone is clean and not blacklisted and it reads the different sims I have put in it I just can't get any signal to pull up other than an emergency call. I know there is signal my s4 is on the gsm network sitting right next to it.
Thanks in advance, I have been searching since yesterday for a solution.
****update.....Went ahead and took it to 4.1.2 stock and happened to find an old verizon sim. Phone picks up verizons network without issue. Still nothing when using the at&t sim.
It isn't working for AT&T because you haven't set up the appropriate APNs for that network. Google AT&T APNs. Reboot after making the changes. CHECK FOR TYPOS!
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
It isn't working for AT&T because you haven't set up the appropriate APNs for that network. Google AT&T APNs. Reboot after making the changes. CHECK FOR TYPOS!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I thought I would at minimum show signal even without adding the apn. From everything I have read its talk ready just inserting the sim. Will look at adding apn's this morning.
Final update. Still no joy on getting it to work and I listed it for sale.
There's a thread about getting vzw s3 to work on T-Mobile, I'd imagine you'd need to follow a similar process. And FYI, all phones will call 911, sim, no sim service, no service, they'll call 911. My niece was playing with one of my sisters old, no longer connected phones. All of the sudden police and ambulances showed up. She had dialed 911, they tried to return the call unsuccessfully so they used the phones GPS info and showed up at the house.
Eat Play Google
I spent over 2 hours last nite with att reps trying to enable numbersync to work between the s3 and s8 phones.. the s8 phone is an unlocked phone (not bought through att), only to find out today via another rep that the phone must be bought via ATT or truly att branded.. which i find a bit absurd, as i think others have succeeded..
Is this really the case.. anyone know or have this same experience?
Specifically this error would appear after going through the get started via the watch then on the phone (after creating a seperate accessid):
Oh darn! We can't enable device syncing on this phone. Want to find out more? Call us at 800.331.0500 so we can help.
(MSSITWINREL12)
If this turns out to really be an unlocked phone issue (which is a bit ridiculous), i think i read that it might be possible to take my sim card out of that phone and put in another phone that is att branded, enable number sync then put the card back in my s8 and go from there
Thanks
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
pasco8525 said:
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
Click to expand...
Click to collapse
Thanks for the reply.. your saying you had an unlocked tmobile phone on att and it was working till a recent tizen update then?
The rep further told me to take the phone to the best buy samsung experience store and have it flashed with the att firmware to get around this issue.. maybe not needed then? (which i assume means a wipe and possibly lose my unlock)
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
karlkarloff said:
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
Click to expand...
Click to collapse
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
markm75 said:
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
Click to expand...
Click to collapse
.
When I first bought the watch it was for the numbersync feature. My first problem was even though the Samsung rep and the bestbuy rep said that it would work with my Note3, it did not. took several calls and many hours of trying to figure out the HD Voice (VOlte) provisioning. Bought a TMobile Note 4, rooted and rom'ed this worked to setup numbersync. the only problem was it would occasionally turn off numbersync, this occurred about once a month. Then if failed completely said that this line is not accceptabl;e for numbersync. this was after about six months. Discovered that it appeared to be age of firmware related, I was on a TM firmware that was several updates out of date. When I odin flashed the latest firmware numbersync worked again until the recent update to 3.0.0.1 on the gear firmware. Now I have the line not acceptable for numbersync again. I'm going to try to update firmware again to see if that works. If not I will probably look to change carriers to TM. will cost the price of a new watch, but will get me out of AT&Ts locked boot loader.
BTW, setting up numbersync on a different phone and switching back will not work, Tried several times and as soon as you turn on the phone that is not HD Voice capable with your SIM card in it the system sees it and turns off numbersync almost instantly. went throught that trying to get my Note 3 to work.
In all my experience the Samsung and AT&T reps were not a good resource. Numbersync does not appear to be a very popular feature and they do not know much about it.
pasco8525 said:
.
When I first bought the watch it was for the numbersync feature. .
Click to expand...
Click to collapse
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
markm75 said:
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
Click to expand...
Click to collapse
Yes, that is the whole point of numbersync. The watch uses the phones number not it's own.
Tried updating to the latest firmware and a ROM based on it. No luck still get a rather comical response "Oh darn! We can't enable device syncing on this phone. " worked until the tisen update.
There also seems to be confusion on numbersync with the att reps.. one person told me the watches dont need their own numbers.. that numbersync is all we need (but how would the watch make a call if the phone is off).. another said yes they need external numbers for number sync or solo
edit: i see your last post.. so the latest reps are correct then.... so they assigned us numbers and $10 access fees each with activation fees for no reason basically.. ugh
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Just a quick note...i too spent 3 hours in an AT&T store trying to get numbersync to work..., finally returned the S3 Frontier cancelled the number in it and left frustrated...i now have a GS8 unlocked on AT&T through my work...that is synced to a Verizon Gear S3 Classic lte and i simply use call forwarding with YouMail. If i do not answer my phone after 3 rings it gets sent to my watch and if I still do not answer then Youmail picks it up..If I call out or text with the watch separately then I just let my customers know that I have 2 numbers 1 for my cell and one for their watch. I just don't think AT&T is ready for the Numbnersync technology yet and they just don't care enough to train their own people on it, sad as it is a good promise...
Sent from my iPad using Tapatalk
pasco8525 said:
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Click to expand...
Click to collapse
I meant phone number.. are you saying phone number? After the rep said i didnt need a phone number for each watch, she credited me back the cost of the two lines and said just to contact them that they would enable the numbersync once i had the phones ready.. I'm assuming number means imei, which they still have in the system.
Yes each watch has to have it's own phone number. I believe this is another case of AT&T rep not understanding number sync.
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
markm75 said:
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
Click to expand...
Click to collapse
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
markm75 said:
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
Click to expand...
Click to collapse
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
eaglerugby04 said:
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
Click to expand...
Click to collapse
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
Thanks. It sounds like the latest firmware they did seems to fix some of the issues from bringing a non-ATT phone over but does not resolve everything. It looks like I won't be able to do this though. ATT and the ebay seller are unable to clear the ICCID on my watch, I have to sadly do a return now.
Kinda unrelated, yet ATT was horrible even for normal Sammy phone/watch. After dumping ATT service/hardware for various reasons a few moths back... Sammy watch/phone from Verizon hardware/service works flawlessly. Am carrier neutral, but one works reliably, one didn't.
BTW, Sammy pay via watch hiccuped via ATT at times, yet works flawless via Verizon.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
well 5 chat people later they finally fixed the unknown callerid issue.. apparently there is an internal back end feature for numbersync regarding it set to active and on.. both toggles were on.. the rep removed the "on" and now my callerid shows my number when calling from my phone (and from the watch when watch is in solo mode too).. everything works! :laugh:
I recently purchased an open box Galaxy S10+ G975U. Phone was in excellent condition. Was told it was an unlocked phone from Verizon. Upon receiving it, it had ATT Splash Screen and Apps. Was trying to get it working on Page Plus, and MVNO of Verizon. After much effort between seller and Page Plus, we finally got just about everything right.
We switched it back to Verizon Splash and Apps. We got everything working or so we thought finally with some APN changes. However, after using it a day or two, I noticed that during a phone call, LTE would always drop to 1X, thus making MMS and Data usage unavailable. Page Plus Customer Service is not good, some are better than others, but I cannot seem to get the issue resolved.
I recently got rid of the Verizon from CSC just to see if it would help and switched to XAA/XAA/VZW. Thinking it would help and it has not. My Galaxy S8 that still works with the same Sim Card with LTE that works correctly as well during calls, has a CSC with TFN/TFN/XAA.
I do not have the ability to switch to Tracfone (TFN/TFN/XAA) but don't really think that is the issue as Page Plus uses VZW devices.
Does anyone have suggestions or an answer as to what could be the issue? I have collectively spent at least three full days of my life between customer support and reading through all the forums and posts.
Thank you in advance to anyone who replies or has knowledge that may help.