i got the unlocked version of fire phone, but doesnt seem to be working on airtel/vodafone India
i can see the network connected, but cant make/receive any calls ; same with sms
data seems to work though
calling 911, works i.e. atleast gives me a network operator error that the number is invalid; all other number the call just ends
any idea, how to get this working ? i have even tried to factory reset but doesn't help
amazon support, was not able to help; they just said its US compatible only and asked if i wanted to return the device
The phone supports the following frequencies and bands: UMTS/HSPA+/DC-HSDPA (850, 900, 1700/2100, 1900, 2100 MHz), Quad-band GSM/EDGE (850, 900, 1800, 1900 MHz), 9 bands of 4G-LTE (Bands 1, 2, 3, 4, 5, 7, 8, 17, 20), supports carrier aggregation
What frequencies are used by the carrier your having problems with? Also, make sure the SIM is inserted correctly. The contacts go down and the cutout faces away from the phone.
facing the same issue
Hi,
I am also facing the verify same issue, I am able to see the carrier and get signal but am unable to make/receive calls.
Any help would be very much appreciated.
Is there any settings that need to be changed ?
:crying:facing the same problem, if there are someone really out there who can help us please do....
CAll Amazon
I called up amazon with the same issue. They accepted the fact that there are many with same problems in India. They are working on a fix and will keep me updated. They added my serial number and registered account to the internal Ticket created for this issue. I recommend you all to do the same and get added.
Moreover, they took some debugging data from my phone after approval so I belive you guys should do that to provide them with more data to fix this issue.
Will it not get activated automatically for Indian users
Rather than providing data to them
Nano Sim
Did you try using a new nano sim from the carrier? There may be an issue if older micro sims are used after cutting into nano sims.
Got a new nano sim from vodafone
I got a new nano sim from vodafone and its still the same .
Now only daru666 can help by letting everyone know what feedback he has from Amazon and if it works.
What should we do ? I am sure some update from Amazon technical team can fix this issue....
Anyone tried it in Delhi. Even if voice works, I am fine with the phone.
I can return it it next few days, so any confirmation would be very helpful...
ashchand said:
Anyone tried it in Delhi. Even if voice works, I am fine with the phone.
I can return it it next few days, so any confirmation would be very helpful...
Click to expand...
Click to collapse
An issue could be that the IMEI code of fire phone is not under registered or under whitelist category of Indian operators. Hence not able to make calls.
For this to happen, amazon will need to give IMEI list to the operators here to add to whitelist. Or it can also be checked with the operators if they recognize the IMEI nos of fire phone.
That would be helpful to us
Did anyone try flashing an android ROM to make it work in India?
Or is this lock hardware controlled?
Same Problem
Same problem....... :crying::crying::crying::crying::crying:
Not working with INDIAN SIMCARD.
Loved the mobile But .....................
Shall i return it (or) keep it..........?
Hello Guys,
Please send an email to [email protected] with the below details.
Amazon needs the following details to find a solution to this issue.
1) Name of network SIM used
2) Did the store/anyone cut the SIM to get it to nano size?
3) Help us by providing logs of your Fire Phone.
To send us logs, please follow below steps:
1. Press the Home button.
2. Swivel your phone or swipe down from the top of the screen to open the Quick Actions panel, and then select the Search icon (magnifying glass).
3. Type ";dm" (without quotation marks) into the Search field. You can find the ";" key by tapping the “?123” key.
Tip: If ";dm" is auto-corrected by your device, tap "dm" in the word choices that appear above the onscreen keyboard.
4. Tap the Search key (magnifying glass), and then wait 60 seconds.
5. Connect your device to your computer using a micro-USB cable. When your device is plugged into your computer, it appears as a removable mass storage device.
6. Open the Fire phone folder (titled "Fire") on your computer, and then open the "Internal storage" folder.
7. Open the “KindleLogs” folder. Drag each of the files within this folder to your desktop.
Note: If you only see "DCIM" and "Pictures" in the "Internal storage" folder, this means your computer recognizes your device as a camera. To change the USB connection type, open the Quick Actions panel on your Fire phone, tap the "Connected as Camera" notification, and then select File Transfer.
8. Reply to this e-mail and include the logs as an attachment.
The total size of the attachment(s) must be less than 6 MB. You will need to send separate e-mails if the size exceeds 6 MB.
After you've e-mailed the log files, delete them from your Fire phone.
LET ME KNOW WHAT RESPONSE YOU HAVE FROM AMAZON ON THIS.
What is the response from Amazon???
I am also facing a similar situation
Amazon is casually asking me to return the phone and get a full refund. The refund process also looks too complex. Why it isnt working in India alone? They told me that
Although, the Indian carriers provide the network bandwidth which is required for the Fire phone, IMEI's of the Fire phones were not added to the carriers outside the US, so currently the Fire phone will not work with the carriers outside US.
When pressed if they would even rectify it by mid next year, they said that currently they arent working on it. They call a phone which doesnt work with any sim other than the U.S. an unlocked one. Still they are selling the phone at $449 calling it unlocked and when people face an issue they say its Unlocked only in the U.S. This looks like a complete fraud.
Any updates?
coolnikin said:
i got the unlocked version of fire phone, but doesnt seem to be working on airtel/vodafone India
i can see the network connected, but cant make/receive any calls ; same with sms
data seems to work though
calling 911, works i.e. atleast gives me a network operator error that the number is invalid; all other number the call just ends
any idea, how to get this working ? i have even tried to factory reset but doesn't help
amazon support, was not able to help; they just said its US compatible only and asked if i wanted to return the device
Click to expand...
Click to collapse
Did you return the device? Even the return procedure looks pretty complicated.
iamviv said:
Amazon is casually asking me to return the phone and get a full refund. The refund process also looks too complex. Why it isnt working in India alone? They told me that
Although, the Indian carriers provide the network bandwidth which is required for the Fire phone, IMEI's of the Fire phones were not added to the carriers outside the US, so currently the Fire phone will not work with the carriers outside US.
When pressed if they would even rectify it by mid next year, they said that currently they arent working on it. They call a phone which doesnt work with any sim other than the U.S. an unlocked one. Still they are selling the phone at $449 calling it unlocked and when people face an issue they say its Unlocked only in the U.S. This looks like a complete fraud.
Click to expand...
Click to collapse
We should press amazon to find a solution to this and deliver a fix ASAP considering how big the Indian market can be for them for their inventory of fire phones that are unsold. Moreover, Motorola had similar issues with Moto E And Moto G and they had worked out a solution in 15 days. Amazon can also do the same provided they are serious on fixing the issue.
From what I understand, they need to give an update list of fire phone IMEI's to the Indian carriers who will update their systems accordingly.
The more all of us push, the more we have a chance that Amazon acts faster.
Related
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 everyone!
i just got my HTC One X last night.
This morning i got a new sim from T-Mobile and popped it in.
Everything was well except for the data. When I go to access point name menu it says sim card not detected but i can make calls and text.
I don't know what's wrong. I'm am running NRGZ rom if that helps. Yet to try it with the stock rom. I'm running it on the T-Mobile US network.
I tried rebooting and re flashing, but it still isn't detecting the sim card in the access point names menu.
I have no idea what to do.
Whenever i enter the T-Mobile APN settings, it does not save. it says APN Saved, but it does not show up in the list.
Thanks in advance for any help
So i was browsing through the Q and A here
and i found this link
http://forum.xda-developers.com/showthread.php?t=1699347
does this apply to me?
Exact same issue here!
AndG404 said:
Hello everyone!
i just got my HTC One X last night.
This morning i got a new sim from T-Mobile and popped it in.
Everything was well except for the data. When I go to access point name menu it says sim card not detected but i can make calls and text.
I don't know what's wrong. I'm am running NRGZ rom if that helps. Yet to try it with the stock rom. I'm running it on the T-Mobile US network.
I tried rebooting and re flashing, but it still isn't detecting the sim card in the access point names menu.
I have no idea what to do.
Whenever i enter the T-Mobile APN settings, it does not save. it says APN Saved, but it does not show up in the list.
Thanks in advance for any help
Click to expand...
Click to collapse
I have been experiencing the exact same issue.
Yesterday I went to T-Mobile store and picked up a micro-SIM. Tried programming the APN by hand but had the same results as you described.
When I interacted with T-Mobile support last night, they tried to send in a message that supposedly would auto-configure the phone, but the message never arrived.
I got in touch with the ebay reseller, who suggested that the phone does not work on 1700MHz network provided by T-Mobile. I think it's not exact that, it has to do with the SIM itself.
I will pester T-Mobile store clerk tomorrow and post you results.
Guys, you have to fully read these threads. This issue has been discussed over several threads now.
The current micro SIM cards provided by T Mobile do not play nice with our One X. You have to search the retail stores for a non GBA micro SIM. The non GBA micro SIM cards allow for voice and data and your One X will auto configure.
The newer micro SIMs from T Mobile will only allow for voice. I don't exactly know why that is but that's what it is. Don't bother calling customer care as they cannot order the older/non GBA micro SIM for you. You have to call the physical stores and ask.
Also, you will currently only get 2g data until T Mobile USA switches 3g data to the 1900 MHz band in your area.
Good luck with your search!
AndG404 said:
So i was browsing through the Q and A here
and i found this link
http://forum.xda-developers.com/showthread.php?t=1699347
does this apply to me?
Click to expand...
Click to collapse
Dude, you quoted a thread that I started, and you posted on that thread and I gave you a reply there and now here.
Take the time to read the post. Some of us may be going through what you are going through and are willing to share advice and experiences that may help you but you have to read the post/reply's.
Good luck with your One X.
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.
I thought I'd share this Tasker routine to easily and quickly swap between eSIM and physical SIM on the Pixel 3 XL running Android 10. Subject to the usual 'I'm not being blamed for killing your phone' caviats, this should also work on other Android 10 devices (regardless of language). Routine is here: https://taskernet.com/shares/?user=...1gNPa0H1P6JuqwklZxdYH5H7VOY3&id=Task:Swap+SIM
Credit to @itskapil for pointing me in the direction of this article: https://www.theandroidsoul.com/android-10-switch-from-esim-issue/
It simply launches phone app, opens the dialler, dials *#*#794824746#*#* and then goes back to the home screen. Simples!
I tried to register an eSim on my P3XL but the carrier asked for a "IMEI 2", which the P3XL does not have. How did you manage to install an eSim?
quera said:
I tried to register an eSim on my P3XL but the carrier asked for a "IMEI 2", which the P3XL does not have. How did you manage to install an eSim?
Click to expand...
Click to collapse
iirc, it doesn't show up in your about device section when there isn't a registered eSIM already; however, it is printed on the retail box of your device.
edit // didn't notice that was sent that long ago earlier, didn't mean to bump..
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