Related
I have the Tmobile dash and want to run AT&T on it without having all the junky tmobile software (ESPECIALLY THE STARTUP ANIMATION). Is there a Rom that could be used to have software with AT&T stuff on it?
Just wanted to ask. Friend wants this phone but with AT&T stuff on it.
Flandrel
Flandrel said:
I have the Tmobile dash and want to run AT&T on it without having all the junky tmobile software (ESPECIALLY THE STARTUP ANIMATION). Is there a Rom that could be used to have software with AT&T stuff on it?
Just wanted to ask. Friend wants this phone but with AT&T stuff on it.
Flandrel
Click to expand...
Click to collapse
None that I know of. All of the ROMs besides T-Mo officials are gonna display either Rogers or HTC screens. Nothing with AT&T since AT&T doesn't carry the Excalibur.
HTC screen would work. just so long as not tmobile. will have to see what is a good rom to use that does not have the myfaves junk or the other stuff. any good recommendations on roms that work good for it?
Thanks for the help.
Flandrel
Try out Ricky's v23 ROM. It has a lot of programs on it, but they're *useful*. Also, it's Windows Mobile 6.1, which is hot hot hot.
Flandrel said:
HTC screen would work. just so long as not tmobile. will have to see what is a good rom to use that does not have the myfaves junk or the other stuff. any good recommendations on roms that work good for it?
Thanks for the help.
Flandrel
Click to expand...
Click to collapse
There's also some steps you can also perform to add custom startup splash screens, Now granted it will still show either the tmobile or htc first screen (depending on the rom you have) and then the windows mobile screen after that , but the 3rd screen, where applicable can be changed to whatever 320 X240 .gif image and the startup and shutdown sounds can also be changed too. So in other words, although you will have the HTC screen if you chooses kavana's or rick's ROM you can still create a custom At&t ( or find one) .gif image to be displayed at startup. Here's the link for instructions for that.
http://forum.xda-developers.com/showpost.php?p=1966277&postcount=322
both replies were extremely helpful. thank you. the phone is sim unlocked but not CID unlocked. need to get what I need to do that and get started. also want to do the same thing for my tmobile wing also and get a good rom for it and get it setup also.
Flandrel
Dont need to CID unlock
Flandrel said:
both replies were extremely helpful. thank you. the phone is sim unlocked but not CID unlocked. need to get what I need to do that and get started. also want to do the same thing for my tmobile wing also and get a good rom for it and get it setup also.
Flandrel
Click to expand...
Click to collapse
Read the stickys on upgrading. Jocky made a bypass for offical ROMs and 6.1 doesnt even need it
Got this all setup for my Tmobile Wing. Whohoo. Now looking at the Dash on trying to setup the AT&T settings for Internet and MMS, etc.
Any clues? Easy to do on Wing with touchscreen and more options to choose from.
I have it updated with the HTC 1.33.422.1 (Worldwide English, WM6) ROM. (Didn't want the Tmobile one)
Thanks,
Flandrel
Flandrel said:
Got this all setup for my Tmobile Wing. Whohoo. Now looking at the Dash on trying to setup the AT&T settings for Internet and MMS, etc.
Any clues? Easy to do on Wing with touchscreen and more options to choose from.
I have it updated with the HTC 1.33.422.1 (Worldwide English, WM6) ROM. (Didn't want the Tmobile one)
Thanks,
Flandrel
Click to expand...
Click to collapse
Have you tried the AT&T website? T-Mobile's site has the settings for MMS and Internet, so AT&T's may have the same.
They're also posted in the wiki. I've been looking for someone to test them out to see if they actually work with AT&T.
beartard said:
They're also posted in the wiki. I've been looking for someone to test them out to see if they actually work with AT&T.
Click to expand...
Click to collapse
Found the settings in the wiki. Gonna try them out and will let you know.
UPDATE: This is with Factory Tmobile WM6 ROM.
Going by these settings:
# MMSC settings for MMS:
#
Start > Messaging > Scroll to MMS > Menu > Settings > MMSC Settings
* Name is AT&T MMS
* MMSC is http://mmsc.cingular.com
* Data connection is The Internet
* Gateway is WAP 2.0 Gateway
* IP Address is 66.209.11.32
* Port is 80
* Encoding is Binary (DO NOT SEE THIS OPTION ANYWHERE)
* Click "done"
#
Then in Send Options
* Priority is normal
* Validity period is maximum (DO NOT SEE THIS AREA AT ALL)
* Deffered Delivery is immediate (DO NOT SEE THIS AREA AT ALL)
* Click "done"
#
Then in Receive Options (DO NOT SEE THIS AREA AT ALL)
* Home and roaming reception is automatic
* Allowed message types: informational, advertisement, auto
These settings from the Wiki are for the "From AT&T's settings support page for the Motorola Q Global"
Unless the MotoQ has alternate settings you can choose.
I even did not see alot of those settings using the HTC ROM for the Excalibur either.
Flandrel
Tmobile Owns At&t
WHY in the world would you want to switch from Tmobile to AT&T????!?!?!!!!: Well i guess some people.....
UMM I Am not sure why anybody would ever make something like that!!!!!
Tmobiledashluva said:
WHY in the world would you want to switch from Tmobile to AT&T????!?!?!!!!: Well i guess some people.....
UMM I Am not sure why anybody would ever make something like that!!!!!
Click to expand...
Click to collapse
Well if you live in LA Tmobile cell service is not the greatest great service for texting though. that's why I use AT&T. They were alot better when they were Cingular. AT&T are very arrogant, JMO.
Tmobiledashluva said:
WHY in the world would you want to switch from Tmobile to AT&T????!?!?!!!!: Well i guess some people.....
UMM I Am not sure why anybody would ever make something like that!!!!!
Click to expand...
Click to collapse
1. Tmobile in my area SUCKS!! Always has, always will. Customer service was rotten to the core. Even the local representatives were arrogant and not very helpful.
2. Tmobile told me before when I kept losing signal or had no signal that it was my phone. I unlocked it and kept Tmobile SIM card in and still had issues. Tried AT&T SIM card in it and got full complete signal. Tmobile didn't know what they were talking about.
3. AT&T has always been good to me. Not to mention I get a corporate discount of 25% off my bill and accessories. None of this with Tmobile.
4. Tmobile never, never would give any type of deal on phones. Had to beg and plead and they still wouldn't. With AT&T I got 4 phones (2 samsung, LG, and my Tilt) totaling $1500 for $50 after rebates, etc. Could not pass this deal up.
5. Tmobile been promising for last year and half for 3G. Still don't have it up and if they do it is just in the beginning stages. That was a condition I had when I signed up. Talked to local rep and even called customer service when I signed up in May 2007. They told me by end of 2007 that 3G would be available. It is just now getting there if even that.
6. But I would still like to be able to use my Wing as a backup in case. So still trying settings out to get it to work, even though it will never have 3G on it.
Flandrel
Hi there. I own an unlocked, rooted t 989 Samsung Galaxy SII which I bought in the US. I recently moved to the Netherlands, and got a new simcard with Vodafone. The problem: I can't get my data to work.
I have tried (almost) everything, so prepare for a read. Here's the list:
- Sim card is fine, I tried it in a old phone and 3G pops up instantly
- Rebooted, pulled battery, turned mobile connections on/off, handpicked network, etc, etc, all the basics.
- Got the APN settings from Vodafone. Tried them manually, resetted them, automatically, turned it on, turned it off.
- Going online through Wifi works.
- Under settings-Status it reads under Mobile Network State: Disconnected. But I know that the phone detects the network correctly. It can distinguish between UMTS and GPRS here.
- So there seems to be no trouble with the phone being incompatible with the network. I read online that other people had NO trouble using their T989 in Europe.
- I tried inserting my old American pre paid T mobile sim card and turn roaming on. No luck.
- A lot of other people with the same problem tried to link it to Easy Battery Saver. I tried updating, uninstalling and going into its settings to find out what it could be, but nothing.
The last thing I can still try is to factory reset, unroot and try to get the phone to its most original state and see what it does. But before I triple wipe all my contacts, pictures, apps, etc, I want to make sure I did absolutely everything to try and fix this beforehand. Being a noob here, I can't post any links but I trust you I tried.
The people at Vodafone are of no help whatsoever. I hope you geniuses could help me any further.
[Edit] And sorry for posting this in General Chat. If a mod could move my question to Q&A I'd be most thankful..!
I am having the exact same damn problem! it started with being unable to send a simple text message yet having data. now it says it is searching forever
thijsr said:
Hi there. I own an unlocked, rooted t 989 Samsung Galaxy SII which I bought in the US. I recently moved to the Netherlands, and got a new simcard with Vodafone. The problem: I can't get my data to work.
I have tried (almost) everything, so prepare for a read. Here's the list:
- Sim card is fine, I tried it in a old phone and 3G pops up instantly
- Rebooted, pulled battery, turned mobile connections on/off, handpicked network, etc, etc, all the basics.
- Got the APN settings from Vodafone. Tried them manually, resetted them, automatically, turned it on, turned it off.
- Going online through Wifi works.
- Under settings-Status it reads under Mobile Network State: Disconnected. But I know that the phone detects the network correctly. It can distinguish between UMTS and GPRS here.
- So there seems to be no trouble with the phone being incompatible with the network. I read online that other people had NO trouble using their T989 in Europe.
- I tried inserting my old American pre paid T mobile sim card and turn roaming on. No luck.
- A lot of other people with the same problem tried to link it to Easy Battery Saver. I tried updating, uninstalling and going into its settings to find out what it could be, but nothing.
The last thing I can still try is to factory reset, unroot and try to get the phone to its most original state and see what it does. But before I triple wipe all my contacts, pictures, apps, etc, I want to make sure I did absolutely everything to try and fix this beforehand. Being a noob here, I can't post any links but I trust you I tried.
The people at Vodafone are of no help whatsoever. I hope you geniuses could help me any further.
[Edit] And sorry for posting this in General Chat. If a mod could move my question to Q&A I'd be most thankful..!
Click to expand...
Click to collapse
Try flashing a different radio/modem then an american one?
@decko5 Nice to see I'm not the only one, but that doesn't help us yet .
@doug36 Besides the fact that I'm running a stock ROM that should be compatible with no issues, I'm not sure how I'd do that. I can flash a separate part of the kernel? That sounds like a very tricky thing to do.
thijsr said:
@decko5 Nice to see I'm not the only one, but that doesn't help us yet .
@doug36 Besides the fact that I'm running a stock ROM that should be compatible with no issues, I'm not sure how I'd do that. I can flash a separate part of the kernel? That sounds like a very tricky thing to do.
Click to expand...
Click to collapse
It's actually pretty easy. You can flash most radios via ClockworkMod Recovery. I couldn't find any threads with a list of Galaxy S-II radios here on XDA, but I found one over at RootzWiki for you. http://rootzwiki.com/topic/2725-radio-samsung-galaxy-s-ii-radios-updatezip-updated-20-aug-2011/
Just find the corresponding one to your geographical location and carrier (Google is your friend) and follow the steps.
Good luck and hope it helps!
(p.s. you should definitely look to see which radio you currently have so that you can download a backup of it before you go flashing radios.)
Thanks for that very helpful post! I've raped and butchered Google, but I'm still having trouble finding out which modem I should download. There seem to be so many and the post on RootzWiki gives no guidance to which is which. Any wisdom on this? I'm in the Netherlands, so Western Europe, on a Vodafone network.
By the way. I fully wiped my phone and installed Team Kang's Juggernaut 5.. No luck, same problem. What I found really, really weird is that it was instantly in Dutch. (Which is ok, I speak Dutch) But I don't remember ever selecting a language. How does it know? Besides, I'd rather have it in English .
What I did find out is that I'm still using a old firmware, UVKID, instead of UVKL1. So I'm restoring back to my previous ROM and trying to update. I'll see what happens. If that doesn't work, I'm going to restore my phone to stockest of the unrooted stocks and try and update.
If that doesn't work, I'll have no option but to send the phone to T-mobile.
I'll try the modem update as soon as I understand what I'm doing . But it does sound promising. Thank you so much for your help, it's greatly appreciated!
Hi guys,
I've updated my firmware to UVKL1, still no luck. Anybody who can tell me which radio I should try on this Vodafone network in the Netherlands?
I am from India and had faced this similer issue with many of my android phones specially with captivate and infuse.......Here what i always did to connect data network.
Just uncheck the use packet data network box in mobile network settings and try to move out from that area (say u are in ur office and going back home) and check the data in settings.
This thing has worked for me always, I don't knw if its related to the OS or to the network provider but this has helped.
Have u tried any other network sim card on ur phone ?
An update for other people that might be looking for a solution in the future. It turns out to be a clear Vodafone problem. I tried a different simcard from a different network (both T-mobile Netherlands and KPN), and they instantly worked without any trouble.
I went back to a different Vodafone store in Amsterdam, and they were much more helpful than the first one. The sales guy told me he had seen the same problem with AT&T iPhones on the Vodafone network.
I called Vodafone, and they have been very nice to me. But they haven't found a solution yet and are looking into it. They see me registering to the network, granting me access, but still my data doesn't work. They've also told me that they will let me cancel my contract for no cost if they don't find a solution.
So problem remains unsolved, but at least there's some light at the end of the tunnel. I was close to buying a new 500 dollar phone... Americans going to Europe: Beware with getting a Vodafone simcard. Sorry to the Vodafone guys, but as for now, that's the status.
So to give closure to this issue (I always hate it when people fix their problem without telling the interwebs..)
IT WORKS!
After an initial terrible experience at the Vodafone counter, the headquarter tech guys have really been great to me. So it is indeed a Vodafone problem. American phones always give them a headache. They don't know what causes the problem exactly, but they do have a fix. It turns out that when logging on to the data network, American phones (AT&T iPhones, my T989 SGsII, and some other Android devices) sent some gibberish along that make the Vodafone server go cuckoo.
The solution was, miraculously, to sign me up (for free!) to the WiFi hotspot service that Vodafone provides, and then logging on to a different APN, being: office.vodafone.nl in my case.
Hope this helps anyone who's having similar issues.
T-989 network solution SOLVED ?
thijsr said:
So to give closure to this issue (I always hate it when people fix their problem without telling the interwebs..)
IT WORKS!
After an initial terrible experience at the Vodafone counter, the headquarter tech guys have really been great to me. So it is indeed a Vodafone problem. American phones always give them a headache. They don't know what causes the problem exactly, but they do have a fix. It turns out that when logging on to the data network, American phones (AT&T iPhones, my T989 SGsII, and some other Android devices) sent some gibberish along that make the Vodafone server go cuckoo.
The solution was, miraculously, to sign me up (for free!) to the WiFi hotspot service that Vodafone provides, and then logging on to a different APN, being: office.vodafone.nl in my case.
Hope this helps anyone who's having similar issues.
Click to expand...
Click to collapse
ok the issue here is that some of the t989 are vodafone and some are USA network , now the other solution is that you flash with command prompt which there is a link to that tool im going to upload from the link i got it from . its also a clockrecoverymod , but this 1 asks you for deleting data user on the device and also resets the network includes USA/overseas though if your not customed roms
or any hacked roms , after flashing this device your basically removing any unwanted apps and cache that are hidden during network searching will be fixed bugs , put the simcard in slot but make sure that is a 3G/4G accounts, than its going to reboot the device automatically , it should be searching for service and also will be a circle with a slash on it where the service bar usually is , just wait about 1/2 hour to an hour maximum time let it do its thing , ok whats happening now to the phone is that is thinking with android network with usa and overseas market apps comparing both carriers network also gets the proper address for the custom rom or original kernel, froyo either 1 will get the correct network address and / VPN / and also will be adding both T-mobile/AT&T choose T-mobile dont go for AT&T cause it will research network configuration plus the phone its not unlocked for both its just a network passby to get correct WPN/VPN/clockworkrecoverymod .
Where is an fix?
Sent from my SGH-T989 using xda premium
@#11 That reads like gibberish to me
@#12 I think I posted a fairly extensive report on how I fixed this...?
Hello,
I have a Samsung Galaxy Note 2, SGH-M317i (Bell Mobility) and recently installed Cyanogenmod 12.1 (Lollipop 5.1.1). All is running well, the device actually seems to be running much faster...probably due to the lack of bloatware that originally came with it. Sure, I miss some of the "cool" features that the manufacturer had added (ie. hand swipe for screen capture), but overall I am extremely happy with the decision to flash the ROM. Although it does self-identify as a SGH-N7105 now. (About Phone > Device model)
Anyway, I have noticed that when I have my guest networks enabled on my home router (an ASUS RT-N66U running the latest Merlin firmware), my phone insists on connecting to the Guest networks (a2.4 and 5 GHz) instead of my full, "regular" network (hidden SSID, but a "Saved" network in the phone). Even if I go into the WiFi settings and tell the phone to forget those entries, it will still try to connect...even going so far as to say "connected" even though I know it does not have the proper credentials. I have no idea what is causing this as the problem was not present on the stock 4.4.2 KitKat that I had previously.
Sure, I could give it the credentials for those guest networks (all are WPA-Personal protected) but I have restricted those from accessing the intranet as they are primarily for guests who come by, so that is not really a viable option.
Does anyone have any suggestions? It seems strange that it attempts to connect and save these networks, so technically, I shouldn't have to do anything to keep the phone from connecting. However, since it insists, I had thought that Android would have a native (not requiring an app) method of blacklisting these networks. I have looked at apps such as WiFi Ruler, but again would've thought that there is a manual way of doing this. (I don't know if this is obvious by virtue of the fact that I am running a custom ROM, but the phone is rooted.)
Thanks!
used this code and off your wifi power saving mode and try *#0011# select wifi..u may need need press the botom left button to select wifi
Very odd. It seems that since installing CM12.1, my device no longer accepts or recognizes USSD codes. I guess I hadn't noticed since I had rooted and unlocked it prior to flashing Cyanogenmod over the stock ROM. I did some reading and I found that there is a patch to enable those codes (and SMS) on CDMA models of the Note 2. However, mine is LTE and does SMS, MMS, and it uses LTE without issue.
Here is a link to that page:
http://forum.cyanogenmod.org/topic/112400-solution-to-sms-and-ussd-code-on-cm121-cm12-cm11-cm10/
Is this something anyone else has experienced? Should I follow the instructions on that page and install the patch?
Again, my phone is a Samsung Galaxy Note 2, SGH-i317M but since the installation of CM12.1 the About Phone > Device model reports it as being a GT-N7105 with a Baseband Version I317MVLUDNH2.
I'd really like to try the solution to my WiFi problem, so if anyone else has had experience with the USSD codes not working please let me know if there is a solution.
Thanks!
To update my last post:
Some USSD codes do work, I watched the pop ups more closely this time and there is one before the "...invalid MMI code" that says "USSD code running". The main one that find interesting no longer works is the one I had used to unlock my phone *#197328640#. I had figured that it would not have disappeared simply by installing Cyanogenmod. Further, I also followed that thread I had posted the link to a little further, and I'm not comfortable flashing the "patch" it leads to as I cannot confirm it's original source and it does sound like it may be another full ROM.
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