M8 can't receive calls, flashed wrong ROM? (4G problem) - One (M8) Q&A, Help & Troubleshooting

Yesterday I flashed my AT&T HTC M8 to a custom ROM (Wolla) because my phone was really laggy after the Lollipop update, and I noticed that although I am still able to make calls, I cannot receive calls anymore. I am wondering if it is possible that I messed up a step somewhere (especially step 3), or if I flashed my phone with the wrong ROM?
I also looked around on XDA more, and realized a few people also had this problem, and it was resolved by turning 4G data off. Apparently this is a problem with AT&T activating Voice over LTE, and the custom ROM not supporting/compatible. Is there a suggested fix to this problem (eg. flash back to the RUU on HTC's site)?
Here are the instructions that I followed to flash the new ROM:
Unlocked my phone via the HTCDev website
Installed TWRP
(Here is where I think the problem occured). I downloaded the Wolla Marshmallow ROM from the XDA thread, and took the boot.img image from the .zip into my fastboot folder.
Then in fastboot, I typed in "fastboot flash boot boot.img", then "fastboot reboot" to reboot my phone.
HOWEVER, my phone would be stuck in white Android booting screen, and wouldn't move for around 10 minutes, so I thought it was stuck.
I redid step 4 a few times, but the same thing always occured.
Finally, I decided to take the boot.img file from an RUU from HTC's website, and use that instead of the boot.img from the Wolla .zip file.
Now my phone boots, and everything seemed to work.
The only issue is that although I can make phone calls, I cannot seem to receive phone calls. It doesn't "ring" on the caller's end, and goes to voicemail in the end.
Does anyone have any experience with this?
My phone is an HTC One M8 bought from AT&T, unlocked about a year ago.

You're on the right track (AT&T's deployment of VoLTE is the problem), and there is one more suggestion I can make: call AT&T and have HD Voice (their branding of VoLTE) turned off for your account. Details here: http://forum.xda-developers.com/showpost.php?p=62001970&postcount=28
Not a true "fix" as obviously, you will not have VoLTE if you do this. But its not a bad compromise, IMO. Not may folks are going to miss VoLTE, and at least the above workaround will allow you to use the custom ROM you want, and have LTE data.
Your other option, is to use an AT&T-based ROM. But who the heck wants that?

I think I'll hit up AT&T chat support today to turn it off, thanks!
I'm sure there are a lot of other AT&T users using custom ROMs on the HTC M8 on this forum. Are all these people getting this problem too, or are they using a special ROM that doesn't run into this issue?
Edit: I'm also a little worried if this problem might occur on other 4G networks internationally? I tend to go abroad once or twice every year, and have a SIM card for the other countries I go to. Is this an AT&T specific issue, or would I run into this problem for every country that also uses HD Voice?

Kwkevinlin said:
I think I'll hit up AT&T chat support today to turn it off, thanks!
Click to expand...
Click to collapse
Note that the base level customer service probably can't turn off HD Voice (won't know what you are talking about, or even wrongly claim it can't be done). Ask to talk to a Tier 2 (or some such term) tech support.
Kwkevinlin said:
I'm sure there are a lot of other AT&T users using custom ROMs on the HTC M8 on this forum. Are all these people getting this problem too, or are they using a special ROM that doesn't run into this issue?
Click to expand...
Click to collapse
If you click on the full thread, for which my previous linked post is from, you'll see that there are a good number of folks that had the same issue. And that is just on that one thread, there have been others (like this one of yours).
Plus, there are other variables that will effect whether AT&T users (on "international" based ROMs) will see this issue or not, such as whether HD Voice has been deployed in their market or not (heck, lots of places don't even have LTE yet, much less HD Voice), or whether the HD Voice feature was ever turned on for their account.
Personally, I have yet to see this problem, despite being on several different non-ATT ROMs and frequently travelling to various US regions. So I'm guessing in my case, HD Voice was never activated on my account.
Kwkevinlin said:
Edit: [/B]I'm also a little worried if this problem might occur on other 4G networks internationally? I tend to go abroad once or twice every year, and have a SIM card for the other countries I go to. Is this an AT&T specific issue, or would I run into this problem for every country that also uses HD Voice?
Click to expand...
Click to collapse
From what I can gather, this is entirely an AT&T issue. Although nothing is a sure bet when travelling international, I'm sure you probably already well know if you travel abroad occasionally. In particular, LTE implementations seems a lot less standardized from one country to another than 3G or 2G. But falling back to 3G is not a bad option, if you end up needed to. Really, unless you are streaming video a lot, or downloading huge files, 3G is really all you'll need most of the time.

So I think I found might have accidentally found a way to deal with this problem without calling AT&T.
On my stock ROM, I turned of the VoLTE (HD calls or whatever) options under data connections.
Made a few calls to myself to made sure that it was dropping to 3G (ect...) when I called it.
Afterwards I flashed a custom ROM (the new sense 8 rom by sundream) and my phone could still receive calls as it dropped it for 3G.
While you don't have VoLTE you could avoid the hassle of calling AT&T.

Related

Debranded Desire won't connect to mobile operator

I bought a HTC Desire branded to Orange UK trough eBay when i was working there last month. The First thing i did was to debrand it using the 1.15.405.2 that i found on MoDaCa, and i bought a unlock key on eBay. This solution worked pretty well until the OTA update showed up, the i got the known WiFi issue. That was no biggie either, just installed the RUU of the 1.21.405.2 and the new Radio, and everything seemed to be perfect again
BUT THEN, two days ago, my phone suddenly lost it's connection to the my mobile operator . I tried to swap my sim card with another sim card, and the result was that my HTC Desire wouldn't get connection while my sim card worked well in the other phone. I also browsed trough my menus to try to find something that might be wrong, but no luck. If i tried to connect to my mobile operator manually, i got a message saying something like "SIM-card doesn't allow connection to this network".
Yesterday morning, i called HTC to try to find out if this might be a hw or sw malfunction, and he advertised me to do a factory settings restore and felt pretty confident that it only was the sw letting me down. I did as he suggested and boom, it worked...for about 5-6 hours, then it came back. As if that wasn't annoying enough, a factory settings restore didn't do the trick this time, and neither did a reflash with the goldcard. I even formated my mSD to be sure there wasn't any kind of virus on it.
So please, if anyone in here got a tip regarding sw, let me know. I'm helpless without my dear phone...
Hmmm this is my biggest concern... I'm just about to buy an ebay Orange Desire and flash it with a stock ROM and unlock it.... kinda worrying as I'm no Linux man really...
im not sure if its the same thing but i have lost conection to t mobile on my desire twice now. first time was fixed by re entering the apn. this time no change. the differance is mine is un branded. i also cant do mms any more.
Unbranded and debranded, same ****, isn't it? Niter means branded...
Seems like i'm not the only one with this problem: http://forum.vodafone.co.uk/topic/5...nt-re-connect/page__view__findpost__p__405655
Lots of Vodafone users in that forum has similar issues, but most of them seems to have a workaround by turn off the back on, or go by airplane mode to get signal back, tat doesn't work for me. I tried to flash my phone once more, but still no luck.
I'm considering a root operation and install android 2.2 aka froyo, but i'm not even sure if that is possible since i got the bootloader version 0.80...
ive just got mine working again by resting the apns to default.
mms still not working though. i hope its not a voda problem i just paid off t mobile a years contract to join voda due to terrible reception and crap tech support.
what is that, and how do you do it? I would guess that a reset to factory default and/or a complete reflash would take care of such, whatever it is...
Yep I was about to ask the same thing! what is it and how do you turn it on/off?
go to settings - wirless & networks - mobile networks - access point names - then press the menu key and hit reset to default.
hope this helps you
That did the same thing as a "reset to factory defaults", but still doesn't work
I've an unbranded unlocked desire on 3 UK with original firmware and mine does drop out occasionally but always comes back perhaps its a desire quirk !
-------------------------------------
Sent via the XDA Tapatalk App
Suppose so, but unlike you and many others, mine doesn't come back I was hoping for a fix for this issue, but i'm afraid were talking about hw malfunction, let's hope i'm wrong...
Little update, just followed this guide, but that didn't change anything. As far as i know, i now got some kind of rooted version of HBOOT 0.75 and fw.ver. 1.15.405.4, dunno about radio version. But it also says that i'm not able to install a custom rom with this rooted version, but i might be able to completely root it now and then install a custom rom?
Yet another update, i did install the 2.2 Froyo following this guide, and unlike the HTC roms, this one indicates that i do have full/optimal connection to my mobile operator, but it still won't let me call, just replies with 'Mobile network not available'.
I kinda courages me to scream out loud ****!!! Yes, i mean it...
Feedback would be nice
Just a thought, may i be that the guy i bought the phone from could have reported it as stolen with the intention of getting an insurance fee? And as a result of that, my phone have been closed by the operator? Don't even know if they mind doing such across the border. So the question would be: Is there any way to find out if my phone has been remotely closed?
Call your carrier.... they will be able to tell you if the phone is connecting to the nextwork correctly... ask them if not... why not?
I second that suggestion, try calling your carrier. Also I have found that switching the internet on directly through settings rather than using the widgets solved my connection problem.
-------------------------------------
Sent via the XDA Tapatalk App
Yep, i got contact with the seller from eBay, and he is very helpful, so he will do what he can while i will call my carrier first thing in the morning. Seems like there might be a glitch here, but i'll keep you updated on my progress.
argh, it seems like i wont get anywhere with my phone. I'm considering trying to change the IMEI, i know it's illegal, but i paid £360 for this device, and atm it's useless to me. If i only knew how tho change the imei, not exactly easy information to obtain, not even with google...
hulkhaugen said:
argh, it seems like i wont get anywhere with my phone. I'm considering trying to change the IMEI, i know it's illegal, but i paid £360 for this device, and atm it's useless to me. If i only knew how tho change the imei, not exactly easy information to obtain, not even with google...
Click to expand...
Click to collapse
So have you found out why your having problems?
ah, sorry, thought i already told u guys, lol. Well, for some reason the phone is IMEI locked. The seller says that he did call to lock a sim card when he lost his iphone, and it might be related since it's the sim that was suppose to be in my phone. however, i think he either claimed the phone stolen to commit insurance fraud, or it's simply stolen. Another thing i came across was that the operator might blacklist the phone if it's unlocked without their blessing, don't really know if they can do that.
Either way, the only way for me to make this phone work is to convince the police that it's not stolen (i need a recite for that which he won't provide me), or to change the imei code with my "awesome" hacking skills...

[Q] Call Answer Lag/Delay

Hi,
For long time i'm having some issue with calls voice.
Sometimes when i answer a call, i can hear the caller but he cant hear me for the first 5~ sec.
After that time (5~ sec) everything continue just as regular.
The issue is with me trough few Roms and Radio's.
Currently i'm with LeeDroid 2.0a and latest radio. non branded phone.
Anyone saw same ?
Bump
This sounds more like a problem with your provider (the phone company). Try finding a friend with a different company SIM, put it in your phone and see what happens: call people on your own provider, other providers, landlines, etc. assuming you know who is using what.
PS Since you rooted it, I assume you have also unlocked it if that was necessary, or maybe that comes for free, I really don't know, I bought mine unlocked
PS2 Putting a SIM in another phone may have the side effect of modifying some of its data (e.g. truncating contact names if they are too long for the new phone, deletion of non-standard data such as Calendar info). I don't know how the Desire behaves in this respect.
Hi,
A. I have SIMFREE device
B. Same provider worked like charm for 11 years now with every other phone.
C. I've saw some topics about same issue, just no one came to solution.

[Q] T-989 - No data network. Mobile Network State: Disconnected

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...?

[Q] S-Off, Rom Compatibility, and Root on Rural Carrier's HTC One M8

So I have the HTC One m8 on a small-town carrier called ChatMobility (formerly Cellular 29 Plus) out of rural southwest Iowa. It's a CDMA version, and although it seems hardware-identical to the Sprint version, I'm not 100% certain it has the same model number. I'm curious about how to go about unlocking and flashing custom ROMS to it, as the only information I've read is specific to the major carrier versions. I tried plugging it into WinDroid HTC Universal Toolkit, but it didn't recognize the device for some reason, no matter what I tried. Anyone have any suggestions? How do I go about achieving S-Off and root, and what ROMS/recoveries are safe to flash? Thanks in advance guys.
No one has any ideas? I thought XDA users knew everything
EDIT: Well, looks like Verizon ROMs are the way to go if you have Chat Mobility for a carrier. Unfortunately, as you might expect, this results in Verizonified themes and apps, as well as reaching Verizon customer service when dialing the usual customer service numbers. Anyone happen to know where I can get a stock dump for Chat Mobility for restoring purposes? I forgot to make a backup when I flashed to nV ROM.
Everything does seem to work fine, though.
EDIT2: Breaks your MMS doing this! It loads the default VZW pic messaging servers, not the correct ones from Chat Mobility.

G7 Power (XT1955-5) kicked off AT&T network despite being VoLTE compatible?

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

Categories

Resources