Database Users

[Q] Unlocked G2 on emergency calls mode only.

Hi all,
This is my case with the hope of getting any help or lead in order to solve my problem:
After a long research I bought an brand new LG D800 already sim unlocked in the US and brought it to my country (Costa Rica). I made sure the frequencies supported by the D800 are the ones used in my country. In fact 2 years ago I bought another phone that uses same frequencies and had had no problems ever.
As soon as getting in my country I placed the SIM card I'm using in my current phone into the G2 and it recognized the signal and connected to the operators network. I started to make and receive calls almost immediately, and also SMS' without issues. So I started to migrate all my data from the current phone into the G2. I used Titanium Backup for this, so I rooted first the phone using the guide I found here, and basically what I did is installed the apps from Google Play and then restored data using Titanium.
After the second day of use suddenly I found out that I wasn't able to make or receive calls since the phone lost connection to the operators network only allowing emergency calls but the signal bars were full (see scren capture). Sometimes when restarting the phone I get "Phone not allowed MM6" message just after the phone tries to connect to the operators network.
Went to the phone company offices and they tried to help me and made some simple tests, without changing anything inside, such as checking Android's network configurations, checking in their system to verify the IMEI wasn't blocked or reported (the IMEI is clean), also checked the sim configuration and after more than 45 minutes they were not able to find anything wrong in their system or with the phone itself. They also made a final test taking a working sim and put it into the G2 and gatting same emergency calls mode, and took my sim from the G2 and put it in another phone and that phone was able to make and receive calls. So they concluded that the phone has a "built-in" configuration or damage that impedes the phone to connect to the network. They finally suggested to ask the seller to apply the waranty, which is not a viable option since I'm not in the US anymore. This G2 is using the stock ROM (see screen captured).
I've been in close contact with the seller, and he had shown interest in this case but unfortunately hasn't been able to provide much support or help to solve the issue. He reports that he has contacted other buyers of this same phone, also sim unlocked by him, and they all are using their G2s normally. Didn't provide where their locations are tough.
My own conclusions here are that the G2 IMEI is not blocked by the phone company, that there is some kind of fault in the phone that when trying to connect to the network, the network doesn't "like" and rejects connection, althought it worked at the begining, and I'm not able to determine if the fault is software or it's in the hardware of the phone.
So I'm trying to understand what my options are at this moment:
Try to return the phone to the seller, or ask an LG representative in my country to change the unit. Which seems to be very difficult.
Reflash the unit with a stock ROM and reestablish the warranty. But being unsure if this will solve the issue.
Reflash the unit with a new ROM and loose the warranty, and again, being unsure the issue will be solved.
I'm really frustrated and at this moment and have no idea on what to do.
Any ideas or insight will be appreciated.
Thanks.
NOTE: I reinitialized the unit and lost any signal (see screenshots) but received update notifications from Google Play and was able to upload the screenshots into my Dropbox although no signal is shown in the status bar and no WiFi connection is established, only data connection thru APN (I Assume).

Go into status, what's IMEI say?
Sounds like EFS issues. I take it you didn't back it up after setting up on carrier and flashing?
Of so, you have some manual work to do with diag mode and a couple apps via pc.

Hi Steamer;
Under status I see 3 items:
1) Phone Number: shows"Unknown".
2) IMEI: shows the number printed on the box, on a sticker on phone's back.
3) IMEI SV: shows"03".
Where can I learn more about EFS issues? Are there tutorials?
As you say I haven't done any backup thing.
Sent from my LG-D800 using xda app-developers app

Steamer86 said:
Go into status, what's IMEI say?
Sounds like EFS issues. I take it you didn't back it up after setting up on carrier and flashing?
Of so, you have some manual work to do with diag mode and a couple apps via pc.
Click to expand...
Click to collapse
Hi again Steamer:
After reading quite a bit about EFS issues now I understand much better what you meant with your post.
And as you said I didn't back up efs folder, I even didn't flash any ROM yet in the unit. The only thing I did was a 'hard reset' to the unit using the Power + Vol. Down method, after having several 'com.android.phone' errors due to backing up data from Titanium.
The phone went to factory state, I put the sim card and everything went back to normal again, meaning that I was able to make and receive calls. Like 4 hours later the phone went to emergency calls only mode, and from then on I'm not able to take it out of that mode.
So I wonder if the efs folder could corrupt after that factory reset. Is it possible?
Thanks again and any light is greatly appreciated.

It is not in its own partition on this device, but in system. A hard reset shouldn't have caused corruption, but it is not impossible. Your IMEI is intact then, that is good. From what you said about it working partially, your EFS is most likely fine as well. There is a thread here to get files with custom recovery zip file, or you can use adb commands to do it yourself. I don't have guides off hand, but Google is your friend, just specified this phone in searches. Try a new SIM. Sounds more like SIM /carrier issue now as you are out of "activation". That is why emergency is popped and unknown number. The SIM itself may and most likely is bad(or carrier has an issue with your account), in turn it can't communicate with the server causing non activation on network search. Priority to SIM.

franz_cr said:
Hi again Steamer:
After reading quite a bit about EFS issues now I understand much better what you meant with your post.
And as you said I didn't back up efs folder, I even didn't flash any ROM yet in the unit. The only thing I did was a 'hard reset' to the unit using the Power + Vol. Down method, after having several 'com.android.phone' errors due to backing up data from Titanium.
The phone went to factory state, I put the sim card and everything went back to normal again, meaning that I was able to make and receive calls. Like 4 hours later the phone went to emergency calls only mode, and from then on I'm not able to take it out of that mode.
So I wonder if the efs folder could corrupt after that factory reset. Is it possible?
Thanks again and any light is greatly appreciated.
Click to expand...
Click to collapse
Hi i have similar issue with my LG G4 H818P dual sim... after factory reset i often face emergency calls only issue despite full signals... sometimes i able to make and receive calls but most of the time despite my sim registered on network and i get full signals when someone tries to call me he get message as my cell is off.... really annoyed and i flashed latest rom v10e but same issue. Same sim when i use in note 3 then no issue what so ever
Sent from my SM-N9005 using XDA Free mobile app

I had the same issues. Bought in Us using now in India. Go to settings..tethering&networks.. mobile networks... international data roaming and select standard data. Switch off and switch on your phone .
This will happen when you use, internet over gsm. If you disable internet or if your phone loses signal while switching between edge and 3g/4g data, this is tend to happen.

Similar Problem
I have an lg vs980 and I was using it with H2O wireless and later I changed to Simple Mobile. I'm living in Puerto Rico. The phone was working all right and, suddenly, one day it was always displaying 'emergency calls only'.
I did factory reset, then I reflashed stock lollipop and it was like nothing happened, keeps displaying 'emergency calls only'.
Then I found this post http://forum.xda-developers.com/show....php?t=2394689 and applied the patch but didn't seem to resolve the problem.
As a last resort I tried flashing cm 12.1 and before first boot applied the patch from the cited thread but no result, keeps displaying 'emergency calls only'.
Has anyone found a solution to this problem?

[Q] Need help - Unlocked Japanese Note 3 no longer works!

Hi All,
Please help. I'm a rookie at rooting and have an unlocked Japanese Note 3 through AU (my Japanese service provider). I was in a rush and paid someone to unlock it before heading back to the States last year. The phone works with my AT&T sim card but when I am back in Japan (with Japanese sim) I am constantly being dropped from the network. 4G service usually works for internet, etc, but I cannot make/receive phone calls and only occasionally can send/receive text messages. I need to know if I should re-root the phone (and leave it rooted) or just do a factory reset (or perhaps change some other setting to get things working again)? The problem with a factory reset is that it will probably re-lock the phone and I don't have a code.
Strange Detail:
Whenever I try to dial a number, the name of a Chinese Province shows up under the Contact's Name. This suggested to me some network issue where the phone somehow thinks it's in China (though texts still kinda work...) and doesn't connect correctly to the Japanese network.
Details:
Model: sm-N900J (per the download screen) i believe this means it has a SnapDragon Processor
Knox warranty has been tripped (apparently by the guy I paid to unlock it originally - is that bad?)
Android 4.3 (looks like I'm still in the original version of Jellybean. Should I upgrade to Kitkat or Lollipop?)
Other Issues:
As of two days ago, the phone now restarts after about 5 minutes of use. Like many Note 3 phones, it's always done the occasional random restart (another reason to root?) but now it's making the phone almost unusable. Also, since having the phone rooted/unlocked/re-rooted I always get a series of warnings upon start-up. Typically, standard Samsung apps like S Planner, Calendar Storage, Keyguard and Index Service have stopped. I have never been able to use the Calendar (or other basic apps) since it always crashes. Is this an issue with Knox clashing with something from the original root (I still see SuperSU loaded -but "turned off"- in the apps menu)?
Idealy...
...someone can help me decide the best course of action (Root, Reset, Other), and how to make sure I can connect back up to my Japanese network properly. I think I'd prefer to root since what I want is an unlocked phone that works smoothly, with good battery life, little to no bloatware, a custom theme and a working S pen. If I root, what's the best method (already have SuperSU apparently) and which ROM and version of Android would be the most stable?
Main Issues Recap:
No connection to phone network (or limited 4G internet).
Phone restarts every few minutes.
Many Apps crash upon Start-up.
Thanks in advance!

So, here's an update that someone with a similar problem might find useful...
Japan uses CDMA for voice and GSM for LTE Data. Somehow (probably through using my phone in the states on a GSM network) the phone was no longer connecting to the CDMA network. Since I'd gotten no responses and felt like there was a good chance that a factory reset would not reverse the sim-unlock I'd stupidly paid to have done, I did a factory reset. Despite appearing to have solved my Index Service, Calendar Storage, S Planner crashing issues, I was still having the exact same problem of LTE working but no CDMA network.
Somehow I stumbled on to this website...(well, I'm unable to post as a new user but searching for "How To Fix Samsung Galaxy error while searching for network" should bring it up).
There, I found some really odd directions that solve network error issues. The only part of the instructions I was really able to carry out was take out the battery and simultaneously press the home and power buttons 10 times. I restarted my phone and miraculously was able to place a call for the first time in a year in Japan!
But then I no longer had any data. I figured it had to do with the APN settings being wiped in the strange reset I just tried. But when I went into Settings>More Networks>Mobile Networks there was no longer an Access Point Names option in the menu. There is no longer a "Network Mode" option either. I used to have that set to LTE/WCDMA/GSM but now I only see a System Select option that simply lets me change my CDMA roaming mode from Automatic to Home Only.
I tried searching everywhere for the missing Access Point Names menu to no avail (and almost attempted to try flashing CyanogenMod for the time hoping this would bring back the APN settings menu) but then I realized that I could do a search in the settings app. I searched APN and the option came right up (though it's frustrating that this now appears to be hidden). Using the following settings (copied below) from the AU by KDDI website I created a new APN profile. Now mobile date appears to be working just fine too!
So, now I just need to decide if I want to keep running Touchwiz in Jellybean or use my new found confidence to try rooting and custom roms...
I'm also kind of curious to see that the next phone bill comes in as expected and I'm not being charged for a bunch of crazy usage! Also, any suggestions to help explain how I got into this problem in the first place, or how to clean up any loose ends would be appreciated.
APN Setting for LTE NET for DATA
APN name au.au-net.ne.jp
User name [email protected]
Password au
Authentication type CHAP

AT&T WiFi Calling on SM-G935F

I have been trying to get wifi calling with AT&T is working on my International S7 edge. I have made headway.
1. First of all I told AT&T I had their branded S7 edge and gave them an IMEI that will show up that phone. So I can activate my phone.
2. I have narrowed down the required apks to the following, but some are obviously for the Wifi Calling, and other's I am not sure. If people know what some of these apks do, please let me know.
3. I have used the Note 7 Port and flashed TTKG CSC selection and chosen the ATT CSC, we are still working on getting it working in the S7 and Edge CSC.
4. The following APK's I feel are related to Wifi Calling are.... If you can help me eliminate some that aren't. They are deodexed, and I have uploaded them, you will need to change the permissions to match the ones in the system folder.
atfwd
ATTVoWifiSPG
com.quicinc.wbcserviceapp
NSDSWebApp
VolteSettings
vsimservice
WAPPushManager
Wispr_ATT
AppSelect_ATT
5. I am unsure if I need to make Buildprop changes or I am missing other system files. I was able to activate wifi calling and turn it on, but it doesn't work.

Psyscope said:
I have been trying to get wifi calling with AT&T is working on my International S7 edge. I have made headway.
1. First of all I told AT&T I had their branded S7 edge and gave them an IMEI that will show up that phone. So I can activate my phone.
2. I have narrowed down the required apks to the following, but some are obviously for the Wifi Calling, and other's I am not sure. If people know what some of these apks do, please let me know.
3. I have used the Note 7 Port and flashed TTKG CSC selection and chosen the ATT CSC, we are still working on getting it working in the S7 and Edge CSC.
4. The following APK's I feel are related to Wifi Calling are.... If you can help me eliminate some that aren't. They are deodexed, and I have uploaded them, you will need to change the permissions to match the ones in the system folder.
atfwd
ATTVoWifiSPG
com.quicinc.wbcserviceapp
NSDSWebApp
VolteSettings
vsimservice
WAPPushManager
Wispr_ATT
AppSelect_ATT
5. I am unsure if I need to make Buildprop changes or I am missing other system files. I was able to activate wifi calling and turn it on, but it doesn't work.
Click to expand...
Click to collapse
Did you ever get this resolved? So far I can not for the life of me, get WiFi Calling working on my S7 Edge exynos. Basically throws an error stating the activation failed, and never brings up the screen to enter in my emergency contact address like AT&T is supossed to re-direct you to.

The activation fails because AT&T doesn't have an AT&T wifi capable phone on your account which then allows you to activate the wifi. I have two imei's that are linked to AT&T s6 and s7. I can give you the imei. Go to att tech support give them the imei and tell them to update your account to be able to get visual voice mail and wifi calling. After you do this, they will alow you to activate it. However I gave up after a while. If you flash the custom csc, you must do it before your phone boots up after a factory reset and flash a custom rom. I am waiting as I am on Nougat now, so until ATT updates it's apps again.

Psyscope said:
The activation fails because AT&T doesn't have an AT&T wifi capable phone on your account which then allows you to activate the wifi. I have two imei's that are linked to AT&T s6 and s7. I can give you the imei. Go to att tech support give them the imei and tell them to update your account to be able to get visual voice mail and wifi calling. After you do this, they will alow you to activate it. However I gave up after a while. If you flash the custom csc, you must do it before your phone boots up after a factory reset and flash a custom rom. I am waiting as I am on Nougat now, so until ATT updates it's apps again.
Click to expand...
Click to collapse
Thanks, although I'm a bit confused on the steps your outlining here. I assume you're stating that I'll need to somehow modify a ROM (in this case SAC's N7 ROM for S7 Edge Exynos), and inject an IMEI? I'm not entirely sure how to do that to change the IMEI (this would be my first time attempting to do that). Then I would reflash that image, and then re flash the CSC update to AT&T? Maybe I'm not understanding, but my iPhone 6 is on my account and fully capable of wifi calling. In fact we have 2 iPhone 6s on the account. What exactly did you give up on?
Hate to sound like a newb here (although in a way... I am), but can you step me through the process so I can follow your line of thought? Appreciate the help!

So first of all an Android WiFi Calling and IPhone Android WiFi calling are different you will need to tell at&t you have an AT&T branded Android phone that has WiFi calling. This will lead at&t to add the ability to add wifi calling on your account.
Have you rooted your phone and installed a custom rom? If so then you would flash ttkg84's csc package and choose att. Which will flash most if not all the files. I got all the way to confirm my address and enable wifi calling, but it never worked.
Do not insert another phones imei into your phone, you will brick it and will have a expensive paper weight.
I have given up for now and am waiting for a full release of Nougat.
PM my I can give you am imei to give AT&T to enable video calling, visual voice mail and give the ability to activate WiFi Calling, but it's not likely to work. Some things are still missing.

You may never get wifi calling working because at&t uses a slightly different method then everyone else. I think they will standardize with Nougat.

Psyscope said:
You may never get wifi calling working because at&t uses a slightly different method then everyone else. I think they will standardize with Nougat.
Click to expand...
Click to collapse
That's what I thought.... So what about the King of Nougat ROM that's lingering out there currently? I realize Nougat is still beta, but have you tried the beta?

I haven't tried King of Nougat. I am currently using Nougat? Are you on telegram?

Psyscope said:
I haven't tried King of Nougat. I am currently using Nougat? Are you on telegram?
Click to expand...
Click to collapse
So... Interestingly enough. I just got WiFi Calling to work this morning...
Basically, I did the following steps:
1. No SIM Inserted into Galaxy S7 Exynos - SD Card only
2. Reboot to Recovery
3. Wipe
4. Download and Install SAC23's Full n7 ROM located here: http://forum.xda-developers.com/s7-edge/development/rom-n7-rom-port-romcontrol-t3430358 - I did the V8 Debloated version
5. When prompted - Wipe Dalik
6. Insert SIM Card from AT&T iPhone (ensured WiFi Calling was turned OFF on the iPhone prior to removing from iPhone)
7. Reboot first time into N7 ROM
8. Go through the setup and connect to a WiFi location that you know WiFi calling works at.
9. Download a browser (Chrome or whatever) at a minimum
10. Eat a Bacon, Lettuce, and Tomato Sandwich :good:
11. Reboot to Recovery
12. Flash CSC for the N7 located here --> http://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911 - Grab the CSC snapdragon the Exynos zip
13. Reboot
14. Status bar will indicate VoLTE enabled up at top eventually.
15. Try going to the pull down from the top, and clicking WiFi Calling option a couple times.... no dice.
16. Try going to the phone app --> Click Settings --> Note WiFi Calling is off --> Try clicking it on a few times.... you'll get an adroid app stopped working.
17. After sitting on this sceen for a few minutes, note the VoLTE dissapears, and the icons on the phone app screen (The Call Start Button and the Call End button) switch to WiFi magically.... Try making a call with 0 zero cell reception, and indeed, the call is being made through WiFI on AT&T's network.
Now.... I have absolutely zero idea what's going on with the VoLTE icon disappearing.... and the WiFI calling suddenly working. If you reboot the phone, the same thing occurs. It starts in VoLTE.... and then eventually disappears, and eventually after a couple of minutes being connected to a WIFI connection, switches auto-magically to WifFi calling.
I'll take some screenshots.

Usaf-lt-g said:
So... Interestingly enough. I just got WiFi Calling to work this morning...
Basically, I did the following steps:
1. No SIM Inserted into Galaxy S7 Exynos - SD Card only
2. Reboot to Recovery
3. Wipe
4. Download and Install SAC23's Full n7 ROM located here: http://forum.xda-developers.com/s7-edge/development/rom-n7-rom-port-romcontrol-t3430358 - I did the V8 Debloated version
5. When prompted - Wipe Dalik
6. Insert SIM Card from AT&T iPhone (ensured WiFi Calling was turned OFF on the iPhone prior to removing from iPhone)
7. Reboot first time into N7 ROM
8. Go through the setup and connect to a WiFi location that you know WiFi calling works at.
9. Download a browser (Chrome or whatever) at a minimum
10. Eat a Bacon, Lettuce, and Tomato Sandwich :good:
11. Reboot to Recovery
12. Flash CSC for the N7 located here --> http://forum.xda-developers.com/note-7/development/utility-flashable-csc-selection-v1-0-t3450911 - Grab the CSC snapdragon the Exynos zip
13. Reboot
14. Status bar will indicate VoLTE enabled up at top eventually.
15. Try going to the pull down from the top, and clicking WiFi Calling option a couple times.... no dice.
16. Try going to the phone app --> Click Settings --> Note WiFi Calling is off --> Try clicking it on a few times.... you'll get an adroid app stopped working.
17. After sitting on this sceen for a few minutes, note the VoLTE dissapears, and the icons on the phone app screen (The Call Start Button and the Call End button) switch to WiFi magically.... Try making a call with 0 zero cell reception, and indeed, the call is being made through WiFI on AT&T's network.
Now.... I have absolutely zero idea what's going on with the VoLTE icon disappearing.... and the WiFI calling suddenly working. If you reboot the phone, the same thing occurs. It starts in VoLTE.... and then eventually disappears, and eventually after a couple of minutes being connected to a WIFI connection, switches auto-magically to WifFi calling.
I'll take some screenshots.
Click to expand...
Click to collapse
Followed the method above using Superman 1.16 and CSC selector 1.86.
Haven't been able to test wifi calling since I haven't found an area with wifi and no cell reception, but so far everything looks like it's working.
Important to note that the AT&T account probably does need to be provisioned for a G935A rather than G935F, which is done by reporting a G935A IMEI to AT&T (and not changing it on the device itself) as mentioned previously.

aramisathei said:
Followed the method above using Superman 1.16 and CSC selector 1.86.
Haven't been able to test wifi calling since I haven't found an area with wifi and no cell reception, but so far everything looks like it's working.
Important to note that the AT&T account probably does need to be provisioned for a G935A rather than G935F, which is done by reporting a G935A IMEI to AT&T (and not changing it on the device itself) as mentioned previously.
Click to expand...
Click to collapse
Hmmm, gotcha.... but if you report a G935A they typically want you to power off and power on the phone to check the provisioning while on the phone with them. And what happens if someone calls in and then tries to re-provision the same IMEI on another account? What happens to my SIM in my G935FD? Thanks!

Usaf-lt-g said:
Hmmm, gotcha.... but if you report a G935A they typically want you to power off and power on the phone to check the provisioning while on the phone with them. And what happens if someone calls in and then tries to re-provision the same IMEI on another account? What happens to my SIM in my G935FD? Thanks!
Click to expand...
Click to collapse
Far as I can tell they don't check IMEIs against different accounts.
I can't say for sure, but I haven't had an issue as my phone has a different IMEI (or IMEIs--G935FD) than the one listed on my account (which reads as a G935A).
In short, asking AT&T to change the IMEI on the account hasn't affected or changed the IMEIs on my phone, or caused any problems.
As far as provisioning, I told them I was on the phone, so they called me back a few minutes later and didn't report any issues or discrepancies to me.
It'd be just as easy to tell the rep the phone isn't available though, so just ask them to change the IMEI and you can call them back later if there are issues if that's a concern.

Looks like great news. I was happy I was able to activate my 935F via AT&T (I gave them the actual IMEI and they activated it). I'm on Superman ROM and flashed ATT CSC. I get visual voicemail and the WiFi calling button, but it doesn't actually work. I'll see if I can get a valid 935A IMEI and ask them to activate again. Hopefully that will do the trick. I get a horrible signal at home, and the 4G/LTE icon is constantly flickering on and off... AT&T Video call option shows up in settings, but won't turn on... no wifi calling setting in the settings menu, just the quick settings button.
Any guidance appreciated!
mike
aramisathei said:
Far as I can tell they don't check IMEIs against different accounts.
I can't say for sure, but I haven't had an issue as my phone has a different IMEI (or IMEIs--G935FD) than the one listed on my account (which reads as a G935A).
In short, asking AT&T to change the IMEI on the account hasn't affected or changed the IMEIs on my phone, or caused any problems.
As far as provisioning, I told them I was on the phone, so they called me back a few minutes later and didn't report any issues or discrepancies to me.
It'd be just as easy to tell the rep the phone isn't available though, so just ask them to change the IMEI and you can call them back later if there are issues if that's a concern.
Click to expand...
Click to collapse

G935V on Android N 7.0 issues with receiving calls/texts [Total Wireless]

I have been going through a weird issue on Total Wireless. When I use Android 6.0.1 and below, I have no issues with my service at all, everything works as it should. The issue comes into play when I use any Android 7.0 ROM, be it official or custom. Outgoing calls/4G data are fine, but I cannot receive any phone calls or send/receive texts. The only way for me to be able to receive calls and send/receive texts is to dial out once. After this, everything works as it should, that is until I reboot. Then I it goes back to the partial working state until I dial out again.
The issue persists whether I am using CDMA/LTE or Global Network modes. I have tried every single possible combination of starting with a fully working 6.0.1 firmware and upgrading through Smartswitch, with and without a full Wipe performed afterwards, doing a full 7.0 firmware flash. The issue is always present, and I am not sure if TW has issues with Android 7.0 or if there is a problem with my account. Their CS is absolutely useless in helping me with the issue, and our chats always end with if I can make a phone call, then the issue is resolved. They don't understand that the issue is still present, but it only crops up after a reboot of my device.
I have tried 3 different SIM cards and they have deleted and re-added/reprovisioned my device/number to their system but nothing seems to help this issue. APN is the usual TRACFONE.VZWENTP. It's really weird that it happens on two separate devices that I activate with my mobile number.
My only thought as to what it could be is maybe some weird provisioning error with the number coming from Verizon. Total Wireless doesn't have any type of VOLTE capabilities on their network, yet I was able to use a rooted Note 4 device and activate Advanced Calling/HD Voice and I believe Wifi calling as well and use it fine on their service. One oddity I noticed is that when the phone is in the initial 'Searching for Service' state on a fresh boot when I dial out while connected to Wifi, sometimes I will see Mobile Network Type change to IWLAN, whereas it usually says LTE. After dialing everything works correctly.
Any ideas on further troubleshooting steps I can take? If nothing can be done, maybe there is some way I can have a boot up script that makes a ghost phone call to any random number and immediately disconnects so I don't have to remember to dial out whenever I reboot my device?
Thanks

I don't have a solution yet, but you're not alone. I have a stock G935V (running Nougat) with Tracfone service running over Verizon's network. Whenever I start up the phone, the phone will indefinitely remain in a "Searching for Service" status until I initiate one phone call. Then the network instantly switches to "Verizon Wireless" and everything works correctly for as long as the phone remains on.
A long phone call with Tracfone and Verizon yielded no solution: They indicated everything is configured correctly in my account. Various replacement SIM cards didn't change anything either.
This issue happens with both stock Samsung S6 phones and the Samsung S7 phone in my household. All are running Nougat.

Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.

dbldown7 said:
Any update here? My girlfriend's phone has the same issue since moving from Verizon to StraightTalk.
Click to expand...
Click to collapse
Tracfone tried, half-heartedly, to solve the problem by sending me 3 different sim cards. The problem never went away. I just got in the habit of initiating a call to voicemail whenever I restarted my phone.
The problem went away when I upgraded my S7 Edge to Android v8 Oreo.

I have flashed the Nougat "U" firmware on my Verizon S7 Edge. I had VoLTE, hotspot, HD voice when calling someone on Verizon (but the HD symbol doesn't show on my dialer, only on theirs).
Only issue was that. when I introduced the TW SIM, the APN was auto set for Tracfone (and it wasn't working), so I had to manually change it to the TotalWireless one.
Since then I had received the Oreo upgrade and the following security update... and it's still OK.

I337 Unlocked was getting 4G Data with no issues, Now I only get 2G/EDGE?

Hi every one,
As the title says I've been using an Unlocked i337 with Simple Mobile carrier for the better part of a year now with zero issues, and happy with my 4G data working fine for a very long time until today when I seen my phone was only showing Edge data with the "E" indicator. I have tried searching and troubleshooting it, and nothing comes up. I recently rooted but 4G data was working just fine even after root. I have checked APN settings and toggled off and on. I went into the test menu and GSM/LTE is selected. I don't have any option in the settings menu to turn 4G off or on. What seems to be the problem?
Also for the record I have called Simple Mobile customer service for help but they can barely understand me let alone help me but they did check my account to see if any thing got adjusted and they resent OTA signal to my phone and every thing checked out fine. They just kept telling me restart my phone about 10 times.
Model: i337
Android Version: 4.2.2
If I haven't included any other crucial details let me know. Thanks