Related
This morning I picked up my EVO and the wonderful people at the Sprint store ported over my number from T-mobile. They told me to leave my EVO off until my old G1 with T-Mobile stopped working. I think they might have screwed something up, though, because my voicemail number is a different number than mine and I can't use the device self service. Here's the skinny so far:
- I've done the profile update in the settings, that doesn't fix it.
- My visual voicemail does not work
- The device self service tells me that it's not the correct number for my account.
Now, this morning I did hear them mention something about a temporary number, so I'm thinking it might be defaulting to that. I'm going to call Sprint in the morning to get it taken care of, but I figured I'd come to the real experts first. Any ideas?
same exact problem.
ported my g1 number to sprint and was told the same, fired up the evo once my g1 stopped working.
the number displayed in settings>about phone is still the temporary number and the same functions do not work for me.
tell me how it goes with sprint.
much appreciated.
Same here as well but your number is actually your ported number. I called sprint and the guy said that's normal it can take up to 2 full days before all that gets sorted out. Once your ported number shows in your about phone your voicemail will work.
P_Dub_S said:
Same here as well but your number is actually your ported number. I called sprint and the guy said that's normal it can take up to 2 full days before all that gets sorted out. Once your ported number shows in your about phone your voicemail will work.
Click to expand...
Click to collapse
Got this from another thread in the general forum: Worse case get your msl and enter ##MSL CODE# this will bring up a menu where you can make sure that your new phone number is correctly placed in both those fields. If not you can save the correct number and reboot. Sometimes the phone provisions properly sometimes it will not.
They should have programmed your original phone number and MSID into the phone even though it had not yet been ported over yet. Call Customer service and get your programming info or go back to the store to have them reprogram it. It's going to be stuck with the temp number until it's manually configured.
Hey everyone,
I went to the Sprint store this morning to get my issue taken care of, and it was as simple as reprogramming. He took care of it in 30 seconds. All fixed!
i went to the sprint store, but i don't think the employee really understood the problem. they ended up doing a hard reset and not being able to fix it.
ended up calling customer care and they took care of it easily.
I had this same issue but with my wife's phone 2 weeks ago. I ended up doing a hard reset (not the one in the user menu for her phone) via a service menu (they provided code).
So my guess is either re-program or this service menu hard reset future reference for anyone with similar problem
So I had my Evo 4g rooted with Unrevoked3, had some nice ROMs and all that fun bling stuff for a few months without a hitch. Yesterday I had my number changed, didn't bother returning to stock or anything. I couldn't dial out or send texts (but could send texts) but had access to the mobile network. So I unrooted, returned to stock (no OTA cuz I intend to root it again), ran through Sprint's activation again and still exact same issue.
I get this message when I attempt dialing out and also when I dial my new number from a diff line: "We could not complete your call. Please try again." Google voice works fine though - but again, so does the mobile network.
Sprint customer service is no help - and right now the Sprint store is closed, so here I be. Any help would be appreciated.
it sounds like the number is not configured correctly on sprint's end. taking it into the store may be the only way to get it fixed. or go onto the sprint website n try
{ParanoiA} said:
it sounds like the number is not configured correctly on sprint's end. taking it into the store may be the only way to get it fixed. or go onto the sprint website n try
Click to expand...
Click to collapse
This, or call *2.
Problem solved! Turns out it was my Google Voice number integrated with my old Sprint number that was creating conflicts with my phone being able to use the new Sprint number. Talk about a whack attack. I spoke with five diff techs trying to figure this one out.
Man, I did all that unrooting and resetting for nothin! Except, of course, for other Google Voice subscribers to learn from my experience...
Hi all,
I've got a few quick questions that I was not able to find the direct answer to in other threads.
1) I'm using an unlocked international HOX on AT&T. I'm on firmware version 1.5 and am unable to get the phone to update. Do I have to do something out of the norm for the phone to see an update?
2) I saw the answer the other thread about Google Wallet being disabled in the States. Is there an APK or something I can load that will allow google wallet to work?
I'm coming from an Iphone 4S and this phone rocks!
Thanks for the help guys!
brashebb said:
Hi all,
I've got a few quick questions that I was not able to find the direct answer to in other threads.
1) I'm using an unlocked international HOX on AT&T. I'm on firmware version 1.5 and am unable to get the phone to update. Do I have to do something out of the norm for the phone to see an update?
2) I saw the answer the other thread about Google Wallet being disabled in the States. Is there an APK or something I can load that will allow google wallet to work?
I'm coming from an Iphone 4S and this phone rocks!
Thanks for the help guys!
Click to expand...
Click to collapse
1. No, updates are pushed out in batches so your batch must not have received it yet.
2. If you have Google Wallet it will work just fine, it does on the Nexus.
Sent from my GT-I9100 using xda premium
joshnichols189 said:
1. No, updates are pushed out in batches so your batch must not have received it yet.
2. If you have Google Wallet it will work just fine, it does on the Nexus.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
As stated in the other threads, I'm able to download Google Wallet but it says that it is not available in my region (SE United States). I'm wondering why the Nexus and other phones are able to use Wallet on AT&T but the international/unlocked version of the One X isen't.. Strange..
In regards to the update, has anyone in the US been able to upgrade past 1.5?
Thanks all!
brashebb said:
As stated in the other threads, I'm able to download Google Wallet but it says that it is not available in my region (SE United States). I'm wondering why the Nexus and other phones are able to use Wallet on AT&T but the international/unlocked version of the One X isen't.. Strange..
In regards to the update, has anyone in the US been able to upgrade past 1.5?
Thanks all!
Click to expand...
Click to collapse
Same thing with me and Google Wallet.
It says not available or certified in my country. (USA)
Anyone got it working in the US?
brashebb said:
I'm on firmware version 1.5 and am unable to get the phone to update.
Click to expand...
Click to collapse
The shipping version was 1.26 and the current version is 1.28. The earliest version is 1.20. Are you sure you're on 1.5?
http://www.filefactory.com/f/7cc7b2fbdd03c031/
Is there an APK or something I can load that will allow google wallet to work?
Click to expand...
Click to collapse
Yes. Do a Google search as that's how people got it working on the VZW GN early on. A word of caution. Using the hack leaves all of your GW data open to any apps you have running on your phone. I want GW but, IMHO, it's not worth the risk.
just tried to download. installs, but won't open - not yet certified on device/carrier. i'm on at&t prepaid. wonder if anything will change once at&t lte is widely sold? not a biggie for me personally, but something to think about when it comes down to deciding on which version of the one x to purchase.
1earful said:
just tried to download. installs, but won't open - not yet certified on device/carrier. i'm on at&t prepaid. wonder if anything will change once at&t lte is widely sold? not a biggie for me personally, but something to think about when it comes down to deciding on which version of the one x to purchase.
Click to expand...
Click to collapse
Really, how are you speeds on At&T prepaid?
Are you on the $50 unlimited dumbphone plan?
Can you send and receive MMS?
Thank you.
methodz said:
Really, how are you speeds on At&T prepaid?
Are you on the $50 unlimited dumbphone plan?
Can you send and receive MMS?
Thank you.
Click to expand...
Click to collapse
i am too much of a noob at this to have truly useful info. i'm in hawaii. i bought a micro-sim off amazon and signed up for the minimal $2/day when used unlimited talk/text plan plus a small data package, because i don't talk/text very much and i'm usually at home, where i have my own wi-fi set up. so having at&t is a fallback for when i'm out and about. that being said, phone calls are clear. checking email and, for example, pulse news service via at&t has been excellent. the one x is notably faster than my acer tablet. haven't tried mms, but i think it should work pretty well; email with a downloaded file that had been pdf'd whizzed through to my laptop, as did a screen cut of photos using dolphin, though that was off home wi-fi. don't see why at&t wouldn't work as well. what i'm waiting for now is to find out if i can get a good bluetooth headset to work (voice commands and all). if so, i may move to another plan so i can use the phone more extensively and downgrade my landline service to the absolute minimum.
All right. Sent a couple of photos via mms from my net10 phone to the one x w/ home wi-fi off. Net10 is running off Sprint in Hawaii. No problemo. Everything came through fine - and quickly.
Looks to me like the big issue for some of the non-techies like me who aren't about to fumble with rooting might be accessing U.S. only apps. Hoping that won't apply to bluetooth headset usability too.
Sent from my HTC One X using XDA
BarryH_GEG said:
The shipping version was 1.26 and the current version is 1.28. The earliest version is 1.20. Are you sure you're on 1.5?
http://www.filefactory.com/f/7cc7b2fbdd03c031/
Yes. Do a Google search as that's how people got it working on the VZW GN early on. A word of caution. Using the hack leaves all of your GW data open to any apps you have running on your phone. I want GW but, IMHO, it's not worth the risk.
Click to expand...
Click to collapse
Thanks for the heads up. I got my One X directly from a contact at HTC and it has been in a closet for a while I think... I have firmware 1.15.401.1. Should I include a screenshot or am I on some beta ish? It still won't let me manually update.
brashebb said:
Thanks for the heads up. I got my One X directly from a contact at HTC and it has been in a closet for a while I think... I have firmware 1.15.401.1. Should I include a screenshot or am I on some beta ish? It still won't let me manually update.
Click to expand...
Click to collapse
Kinda makes me wonder what bootloader you have on your device.
Bxsteez said:
Kinda makes me wonder what bootloader you have on your device.
Click to expand...
Click to collapse
Let me know how to find out and I'll let you know. My build number is also 1.15.XXX.
methodz said:
Really, how are you speeds on At&T prepaid?
Are you on the $50 unlimited dumbphone plan?
Can you send and receive MMS?
Thank you.
Click to expand...
Click to collapse
I have an international GSII on the $50 unlimited Go Phone plan.. yes I can send/receive MMS. I plan on cutting my sim down for my One X when I get it
joshnichols189 said:
I have an international GSII on the $50 unlimited Go Phone plan.. yes I can send/receive MMS. I plan on cutting my sim down for my One X when I get it
Click to expand...
Click to collapse
Uhh..I want that too . Any way to do it w/o losing your number?
brashebb said:
Uhh..I want that too . Any way to do it w/o losing your number?
Click to expand...
Click to collapse
I don't know, I was on T-Mobile prepaid but switched to Go Phone for the sgsii/hox but I know for T-Mobile you couldn't pick your number for prepaid.. I would assume the same for Go phone
Sent from my GT-I9100 using xda premium
i updated the other thread re non-availability of certain apps on non-us htc one x, but for those on at&t like me with unrooted phones, i will add the info here as well. i managed to download google voice on my one x (at&t prepaid) by using dolphin hd browser to google search "google voice." when the results page came up, i clicked the link that took me to the play store and downloaded. the app opened and seems to be working fine. i was unable to download it by going to the play store directly, so the browser may add some kind of filter which makes this possible?
i can't be totally sure that all google voice options will work, because i chose to install the "lite" version - i only wanted my voicemail kicked back to my phone to avoid having to use the phone to check voicemail. (i'm on the $2/day unlimited text/talk plan and if i have to use the phone only to check a random voicemail, i'm throwing my money away.) called my one x from my landline phone and a still-in-use net10 phone and left messages. seems to work. i used my gmail account as the voicemail recipient. no google phone number.
additional info for anyone planning to use a sophisticated bluetooth headset like blueant q2. i purchased one that was at&t branded. does not function completely. the most critical features - voice commands, voice dialing - are not supported in ics, so while the blueant will pair and one could presumably answer an incoming call, the other key features are unavailable. this appears to be a function of ics and not of at&t, though i assume at&t could tweak its own branded htc one x's to overcome that? i have a jawbone era coming in maybe next week and plan to purchase one of the apps available in the play store to test both headsets at the same time. the app's developer told me he has been trying to get his app to work smoothly with ics. it already handles the blueant in other versions of android.
1earful said:
i managed to download google voice on my one x (at&t prepaid)
Click to expand...
Click to collapse
It must be unique to pre-paid accounts. It showed up in the market for me (post paid) and installed without issue.
additional info for anyone planning to use a sophisticated bluetooth headset like blueant q2. i purchased one that was at&t branded. does not function completely. the most critical features - voice commands, voice dialing - are not supported in ics.
Click to expand...
Click to collapse
I'm using a Q2 also. The problem isn't ICS; it's HTC. They left "voice dialer" out of thier ROM. I found APK's from other ICS devices but they don't work. Either a dev has to create one or HTC has to include one for native voice dialing to work. In the meantime I'm using Vlingo. When you use the "in car" mode the phone listens for commands over BT after you say "hey, Vlingo." You can also dictate texts and have incoming texts read back. When you activate it on the Q2 by saying "phone command," it starts up and is listening even though the Q2 says "feature not available." It's not too battery friendly though. Not perfect, but workable.
thanks for the info. is your phone rooted?
everything i found on the net elsewhere says it's android that is the problem re voice dialing - that development was dropped even before ics. does vlingo support announcing incoming caller id on the q2? and follow through on the answer/ignore response? (really, for someone who doesn't use the call function much, i am being very picky. but sophisticated means it should do all things well.)
1earful said:
thanks for the info. is your phone rooted?
everything i found on the net elsewhere says it's android that is the problem re voice dialing - that development was dropped even before ics. does vlingo support announcing incoming caller id on the q2? and follow through on the answer/ignore response? (really, for someone who doesn't use the call function much, i am being very picky. but sophisticated means it should do all things well.)
Click to expand...
Click to collapse
I'm stock. Vlingo lite is free in the Market so play around with it.
mine will hopefully be here Fri, Mon, or Tue. i didn't think to try to get on a free phone's plan, so i'm getting robbed every month paying $70 (7% student discount wow thanks) for 2 GB, 450 mins (over 400 of which i don't use), and zero text. as soon as i can, i'm switching to Red Pocket. i also thought there was some way ATT was catching people with smartphones on gophone cards and turning their data off or something, to force them to come in and get the 4G sim and pay more. if not, good deal. i stay on wifi, but if i'm out and need data and it's too slow, then i won't be happy.
Hello,
First, let me express my deepest thanks in advance for those of you who may be of assistance. I have visited this site many times over the years when I needed to find the answers to smartphone related issues (mostly rooting..etc). I have usually found the information that I needed via reading posts and trial and error; however, I am having a problem that I cannot find the answer to and it is frustrating the crap out of me.
So, here goes:
I bought a LG LS980 off of Ebay. It was locked to Sprint and I had a friend of mine root it (since I couldn't figure it out and it ended up being that the firmware had to be downgraded since a patch was bumped to it) and unlocked (or so i was told, but I do not know how to find out). It is currently running Cyanogenmod 12.1. I wanted to use my old phone's SIM and pop it into my new phone so that I could enjoy it (the old phone was a Nexus and ran hella slow). So, anyway.... I contacted NET10 customer support since that is my carrier and explained what I wanted to do. They let me know that as long as it is unlocked that I would be able to just swap the SIM into the new phone and should be good to go. They checked my IMEI and said that the phone was, indeed, compatible and as long as it is unlocked it should just be a matter of a simple ROM swap. Not the case. I put the SIM in and booted it up. It went from No Service to saying "Sprint" on the upper left hand corner. I try to make a call and it states that, "The code or number that I am dialing is incorrect, please try the code or number again". I looked this up on the internet and didn't find a focused answer. I talked to my friend and he stated that I may have to set up a new APN profile.
I have checked the APN settings on it and all of the APN profiles have the prefix "Verizon". I used this mini tutorial at http://forums.androidcentral.com/goo...-settings.html along with the NET10 settings to try and make a profile. Both of their workarounds don't seem to work. I can enter about half of the information and then either click BACK or SAVE and then the profile is gone. I am not sure this is the reason that my phone is not working, but I thought I would give it a try. I have also tried to use this tutorial: http://forum.xda-developers.com/show....php?t=2798566 as a loose guide, TWRP installed. Keep in mind that I believe that my firmware was rolled back to ZVE. and not ZVD. When I have tried to edit the build.prop values at the tutorial states it does not save. Also, there are two lines that are not even in my build.prop (ro.build.target_operator and persist.service.crash.enable). When I have tried to edit or add it adds them but does not save and definitely does not persist through reboot. I feel as if I am close to getting the phone to work, but I am unsure where to go from here. I really do NOT want to have to go back to a stock ROM and all of that because....well.... my friend did the rooting and installing of cyanogenmod and I don't want to risk undoing all of his work and having to pay $ to have it done all over again (I have rooted phones..etc, but this G2 was a MOFO because of the firmware patch for me). NET10 CS and TS was of no help and they gave me a ticket number (and to tell you the truth the are outsourced and I can't understand what their reps are saying). So, does anyone have any advice or threads that I can look at? Like I said, I feel as if it is close, but no matter what number I call it says that recording. I get no incoming calls (although it rings when listening to the incoming calling phone's speaker). I am also unable to send or receive SMS or MMS messages. Any help would be greatly appreciated. I am not the most technically savvy person, but I can answer your questions to the best of my ability and I am good at following directions. (I have about 5-6 phone root/ROMS under my belt and even 2-3 SPRINT to NET10 activations, but this one is just perplexing the crap out of me) . Could it be that the phone is not unlocked???? How do I check this??? Is there a way??? When I put in the NET10 SIM it never asked me for an unlock code so I am assuming that my friend unlocked it? I have also tried "Turn the phone ON and type 2945#801# If nothing happens, type 2945#802# or 2945#*803#" and no hidden menu appears asking for an unlock code.
You can unlock your Sprint phone for GSM but you can't activate it to Verizon or its MVNOs.
Has anyone else experienced the same problem? Is there any way to get them to reactivate it?
I had an an XT1955-5 that was fully functional on the AT&T network, including voice over LTE. I bought this phone because XT1955-5 was on their list of approved phones. I even checked the sim status to verify that it didn't kick down to 3g/H+ when I made a call, and it had the HD symbol on the call screen.
Despite this, AT&T disabled it because they were shutting down the 3g network. I got them to reactivate it and it worked again for several months. Then, when they sent me the cheap replacement phone and sim card, they deactivated my old phone and I couldn't get it to work again. I tried calling them and talking to their technical support to explain the situation that VoLTE was fully functional on it. They didn't seem to know much other than "the computer says this phone isn't compatible." They said they would try changing my provisions, but they ended up making it much worse so mobile data wouldn't even work anymore.
Do they just go by an IMEI whitelist that can't be overridden? My best guess is that they seem to be shutting down all phones that weren't AT&T branded, so this one gets the axe because it was unlocked from another carrier. This is very disappointing because I really liked this phone for a combination of several factors that I can't seem to find in any others.
Unless I'm misreading the list, this is a whitelisted device on the AT&T network.
Correct, the model number is on their whitelist. That's why I chose this phone and why it's so frustrating that it was deactivated. I guess there's a subset of whitelisted IMEIs within that list, but isn't published. This particular one must not have been on their whitelisted IMEI list because it was unlocked from a nother carrier. Do you know if there's any way to get ATT to add it of am I SOL?
They say nothing about IMEI number limitations.
As long as it's not blacklisted there shouldn't be an issue. This list was just revised so your phone may not have been previously whitelisted.
There's quit a bit of confusion is what I gathered.
Some of the AT&T features like vid calling won't work without the AT&T software maybe firmware. Guess we'll both find out on the 22nd.
Call AT&T advance tech support as this is the game that moves as you play it.
I have a development:
I flashed back to stock/RetUS ROM from LineageOS 18.1 to try to fix wifi calling on T-Mobile since I was trying to switch to them due to this hassle. While I was at it, I read a post on a forum for another phone, where the person said they reflashed stock to reprovision the sim. I figured it's worth a try, so I popped in my AT&T sim card while on stock ROM and to my surprise, it fixed it. The LTE network is fully functional, at least for now. I didn't think Lineage did anything to change the radio firmware or whatever it is that controls how it interacts with the cell carrier. I guess I was wrong.
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
MotoMan1955-5 said:
Now, I wonder if I'm stuck with the stock ROM because AT&T will detect a change and shut it down, or if I can get away with switching back to Lineage. I'll try it soon.
Click to expand...
Click to collapse
AT&T isn't witch hunting. As long as it's firmware is compatible with their protocols it will work.
I have no clue what those protocols are though.
(deleted, mistook carrier)
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
MotoMan1955-5 said:
I've pretty much lost hope at this point but I might as well share some more of this madness I'm experiencing. Maybe you'll even get some amusement out of my struggles.
VoLTE continued to work with the stock ROM. I flashed LineageOS again last night and was pleased to see VoLTE still worked. It went fine all day until someone in person mentioned to me that they texted me yesterday but I didn't respond. I never received the text, and I tried sending them one and they had not received that either. Since I was on the stock ROM when that text had been sent, I figure it was something still incorrectly configured with the carrier. I tried messages to several other people. They would all say "sent" but only a couple actually made it to the recipient, and likewise I could not receive messages from most people.
When I got home, I switched the sims around in a couple of phones to narrow down whether it was my phone or my sim that was causing the issue. It turned out to be the sim, as evidenced by successful messaging with a different sim in my phone but not my sim in a different phone. I happened to have the SIM in the AT&T Callypso when I called ATT customer support to see if they could fix the problem. Ultimately they did. VoLTE worked. Messaging worked.
I switched the SIM back to the G7 (currently running LineageOS 18.1). I made a quick call to confirm VoLTE still worked. It did. Great success! Then right after that I got the dreaded message saying they're updating the network and the phone I was trying to activate will not work. Now, it drops from LTE to H+ any time I have an incoming/outgoing call again, and mobile data doesn't even work now. At least messaging works now.
To make things worse, now it isn't even automatically reprovisioning when I put the sim in a new phone so I can't automatically get those privileges back like I did before. To make it double-worse, the sim for my spare line got the same screwed up status from being inserted into the G7 that it now has the same troubles.
Blackhawk, I agree that they probably aren't witch hunting or intentionally making this difficult, but obviously its network is changing my privileges when I put the SIM card in this phone. It seems to be that switching a sim to a new phone sends that phone info to the carrier, and if they have it on their list they automatically adjust the types of services available to that line to fit the phone. I suspect that info it sends also includes some software info, considering how it worked as intended when I had the stock software but not with Lineage which it probably did not recognize. My best guess is that I got away with flashing Lineage yesterday because my line was already configured correctly from when I had the stock rom, and since the SIM didn't change with the Lineage flash, it kept that same configuration. Moving it to another phone and back made it see the G7 as a new phone again, and it sent the info but the software wasn't recognized so I didn't get the good privileges.
ffdm, unfortunately you seem to be correct about just getting the runaround if your issue isn't common. The tech support people don't seem interested in anything other than their pre-scripted instructions, and it doesn't help that the support has clearly been outsourced to another country so they are hard to understand.
I have one last hope which is to put the SIM into the G7 totally stock, call customer support and have them reset the provisions for this line, then flash Lineage again and hope it never triggers the automatic provisioning ever again.
I just want a phone with a long battery life and AOSP not bloated with spyware that sends all my information to third parties that profile me. It shouldn't be this hard.
Click to expand...
Click to collapse
If these apply to you try:
Clear system cache
Clear Sim Toolkit data
Reset network setting
Get a new sim card from AT&T, handle like a stick of ram as they can be damaged by ESD.
From what is described, it does sound like a provisioning issue, and calling to get it fixed would probably be the correct solution. But why is it flagged as incompatible? Why would that status be persistent for that line? It's weird.
FWIW, AT&T kicked me off for switching from a OnePlus 6 (not a 5g phone) to a OnePlus N10 (5G phone). They were nice enough to disable my account on a Friday night when I switched sims, and was without cell service all weekend since they apparently don't want to do customer service outside banker's hours. Couldn't use the old one either (on 4G), I was completely blacklisted.
T-Mobile happily accepted my porting on Monday .
I'll save my unkind thoughts past "maybe consider firing them" as I don't want to sound like a loonie.
Man, I wish I could switch. I actually tried switching to a T-Mobile MVNO. They provisioned my SIM correctly, but unfortunately their coverage was insufficient in my rural area. I considered sticking with them and using wifi calling at home if that would work, but that feature was broken on lineage and I thought I got this to work correctly with AT&T.
I did get it working by flashing stock again, calling ATT to have them correctly provision it, then flashing LineageOS again. It has been working properly for about a week so with any luck I'll get to continue using the phone.
The 22nd came and went. I'm noticing some vids pause occasionally. May be just a random glitch otherwise no change. I may eventually try a network reset and have AT&T do it on their end.
Long live 4G LTE