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
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
I have the Moto G4 Play (XT1607) (Harpia) and I have decided to flash LineageOS (lineage-14.1-20170131-nightly-harpia-signed.zip) on it using TWRP v3.0.2 r5. After getting it installed I noticed that it was not connecting to my 4g LTE Internet (I have Ting). So I figured I needed to make some changes to the APN settings. So I go to Settings>... More> Cellular Networks and the moment I click on "Cellular networks" I get an error message saying "com.android.phone has stopped". After reflashing and trying again a few times with the same result, I tried using a completely different ROM. AOKP. (aokp_harpia_nougat_nightly_2017-01-31.zip) and I ran into the same exact problem I was having with LineageOS.
I then tried to see if I could force my way into the APN configuration using an app called "Change APN". This worked, but now I see the message "Access Point Name settings are not available for this user". I decided to ignore this and click on the + to create a new APN. After filling the correct info out for Ting APN, I click on "Save"... and it doesn't save at all.
I decided to revert to the stock rom, and everything works perfectly fine with the stock rom. 4G LTE on Ting works fine. Whenever I try using a custom ROM of any kind, I run into the problem I described above. I don't know if I am forgetting to do something, or completely doing something wrong. I could use some help with this guys.
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
Yes. Ting is a Sprint service. Well either way LTE isn't working and the 3G keeps randomly turning on and off whenever I use a custom ROM. However, when I use Stock firmware, everything works perfectly fine. I am unsure what is causing the issue.
It seems nearly all custom ROMs at this point are having data connectivity issues. I'm trying to find a nandroid of the original xt1607 rom so I can just go back until its all sorted out.
mkollersms said:
Isn't Ting a Sprint service? I didn't think CDMA-based networks had APN settings to configure. Verizon and US Cellular have always used *22XXX for programming, as far as I can remember.
Click to expand...
Click to collapse
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.
n76 said:
With Ting you can choose to use Sprint or T-Mobile. I am using the T-Mobile side of Ting and you do need to add Ting's APN settings for it to work. I am still on factory ROM but watching closely to see what others are experiencing with custom ROMs.
Click to expand...
Click to collapse
I haven't noticed any issue with my GSM ting service on lineage. I get LTE and the WiFi/LTE handoff seems to work. I don't install many apps and don't let them run in the background, so perhaps there's a conflict between them that's shutting down LTE service. This is just a guess.
Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
I looked around in the file system and in /data/data/com.android.phone/ there is no files, no .db files or anything. I don't know of there's supposed to be either. But like OP stated, stock rom is flawless.
Would I be and to copy com.android.phone from stock and restore after flashing? I don't know what to do but this is with every single custom ROM out right now on every release. Data and everything works fine as far as I can tell but just no way to configure the settings. Any help would be greatly appreciated!!!
[email protected] said:
Anyone have any information pertaining to this subject? I've searched hours on hours to no avail. I run U.S. Cellular and on the newest RR-5.8.1-OMS after I go to Settings>More>Cellular Networks>Crash. Every time. Resets my radio and picks right back up again. Everything works until I'm in my house, then I'm roaming and there's no way to manage in settings because of the crash.
Click to expand...
Click to collapse
Just out of curiosity, have you tried the *22XXX thing yet?
EDIT: Just so we're clear, with you all who have CDMA phones, when you go into "IMEI Information," it does show both an IMEI and an ICCID, right? Because if not, I think I figured out why your LTE isn't working.
I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?
[email protected] said:
I tried, I tried dialing *22999 (guessing that the x stood for the 9 button in T9 language) and pressed the make a call button. Am I wrong about the "XXX" part? Because I did try that when I seen it previously in the thread earlier but had the same thoughts.
So to make that novel a shorter version, what exactly should I dial?
Click to expand...
Click to collapse
It depends on the carrier and the model of the phone. For most Tracfones, it's *22890. For US Cellular, I've seen it as *228 and *22894. You may have to call your carrier and ask what their phone programming code is.
Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)
[email protected] said:
Aaah ok I got you now. Yes I've tried that on nearly every ROM. Matter of fact I just noticed I posted a little off topic almost, but I'm here for the relevance of com.android.phone crashing EVERY SINGLE TIME I try to open Cellular Networks. The only ROM I will say it doesn't force close on is the Slim Nougat ROM, but I don't run that because instead of Cellular Networks settings making com.android.phone crash its when you place a call and then it force closes the UI part of the call but still carries the call through. I forgot to mention that by the way, whatever it is in Slim that is the making the different reason for force closing com.android.phone could probably be a pretty easy red flag for someone better equipped for this Lind of troubleshooting than myself!
Thank you for the suggestion though on the *22(8 in my case)
Click to expand...
Click to collapse
After I posted that, I went back to try and see if Lineage was able to pick up my phone's MEID (even though I use a GSM SIM, the MEID is still tied to the phone hardware). For some reason, Lineage is not reading it, and I think all of your problems are being attributed to that fact.
The way CDMA phones work (and god, do I hate this), is your 2G/3G network is tied to the phone MEID, while the LTE SIM is data only. The OS needs to read both the 14-digit MEID (sometimes shows as a 15 digit IMEI where last digit is 0) as well as the 20 digit ICCID (SIM Number). A phone may also use the SIM number itself as an IMEI (BYOP SIMs do this) by dropping the first five digits of the 20 digit SIM number.
If you phone is showing only one 15 digit number in the system settings, then it's either the MEID OR the SIM, not both. So either you have calling and no LTE, or LTE and no calling. You can't program APN settings because the phone has no idea what ID number to tie APN settings to. This is actually a rather serious conundrum.
Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!
[email protected] said:
Ok ok, makes sense. I checked my Status info, every ROM has dual SIM capability by the way so I don't know if that would effect anything for xt-1607, but I looked at SIM slot 1 info and it reads my MEID correctly with 14 digits. I couldn't find anything about ICCID. My head pounding question here though, why in the hell (pardon the language) is everything flawless on stock, but on every ROM this problem occurs? Here's my next killer, everything works like it should for me, LTE, 3G, Calls, SMS/MMS, just can't change any of the settings due to a force close, AND I put my friends Straight Talk SIM in and it fired right up with no force close when going to change Network settings...?!
Click to expand...
Click to collapse
I think you just answered your own question. As stated in PCMag back in 2015, "Nobody makes a Dual-Sim phone compatible with Sprint or Verizon." It legitimately believes your MEID is a GSM-based IMEI, and is attempting to cross the streams, so to speak. And the only way your friend's StraightTalk SIM would work is if it was piggybacking off ATT or TMo's networks (the MEID would have been paired to the other phone causing a mismatch).
If you look at the stock ROM for this phone, you will see a BUNCH of system apps for programming Sprint and Verizon network information. They never made it into the custom ROMs we're using. FWIW, here's my thoughts on the matter. Someone needs to go back and make a single-SIM variant of these ROMs, as well as a flashable ZIP containing the necessary APKs for Android to detect the necessary information correctly. And if that doesn't happen, then everyone who bought an XT-1607 has to ditch their carrier and move to a GSM carrier.
That makes complete and total sense! Because I wasn't thinking this while time of it but I was in Oklahoma at the time where the main towers are AT&T, matter of fact Sprint and U.S. Cellular lose almost all signal right when you hit the county line where I was at. Verizon only gets signal because it's Verizon, lol. Reason I say that is because I was wondering why this whole time I has full signal with LTE coverage and completely list everything when I went hone, because where I live is complete opposite, there is hardly any GSM coverage, we don't even have an AT&T store, just Verizon, Sprint, USC.
So, with that being figured out, my laptop just recently kicked the bucket on me so I'm out for the most part, I do have a trick to swap files in and out of a compressed archive without extracting it in any way! But, it takes a while, not too much longer I guess but nowvi just remembered everything is pretty much .dat files so nevermind that.
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.
[email protected] said:
Not that this thread isn't the most popular, but where would be the best place to take this request too to get the most attention from it? I mean if I had to go back to stock, so be it, but I'm a little spoiled to the custom life. Lol.
Click to expand...
Click to collapse
IIRC, there is a Verizon thread with 80ish replies, but I think a developer like Squid might need to be made aware of this, so I might copy this into the Lineage thread.
A bit of good news. While reflashing all the time that were force closing when opening cellular networks, I looked in /data/data/com.android.phone/ and was looking, now remember to go back to that directory after I say all this, I found that directory was empty, on all of the Roms. Was curious so I flashed back to stock. Went to the same directory, BOOM! com.android.phone was not empty, in that folder I found 2 folders that were now populated with in:
1: (/files/ )I now had a file named carrierconfig-com.android.carrierconfig- (and after the dash was my ICCID number) so for this directory I need /data/data/com.android.phone/files/carrierconfig-com.android.carrierconfig**ICCID** (replace **ICCID** my ICCID number)
2: then there was this /data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
and
phone/shared_prefs/com.android.phone_preferences.xml
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.
[email protected] said:
These files are missing on all the Roms, I know this doesn't since everything, but I know for almost a fact it's a good chunk of something that needs to be available. Can I copy these files and move them into place, and set permissions how they were? I ran out of time tonight, and am busy all week so this is mainly for reference I guess. More research told me these files can be edited to change what is available to configure in cellular network settings like option to change from 2G, 3G, LTE, APN, and so on. Sorry for the mess, that's all I have for right now.
Click to expand...
Click to collapse
That is definitely a major find! My only concern is even if you do that, there might be further missing components that would cause Dialer to crash on startup or some other wacky side effect. However, if you can make it work, then it's possible the proper APN settings will load by default and you'll no longer need to change them.
If you can, go into the System Apps on the stock ROM and look for any APKs branded by/with Sprint, VZW or USCellular, or anything CDMA related. They might be necessary for reading the SIM's ICCID.
That's what I was thinking too, and sadly for me I don't really know EVERYTHING to look for so it'll be mostly out of trial and error for me to figure it out. I wish they didn't compress Roms into .dat so I could use a root explorer to swap between tabs rather than copy, flash the rom, paste files and then if that didn't work start all over on restoring stock, so on and so forth. I miss my laptop. =(
Updates?
Has anyone looked into this further? I'm experiencing the same problem with the latest LineageOS nightly. US Cellular Prepaid with an XT1607.
I noticed that in my case i had to skip the Insert Sim thing on 1st boot. It never did whatever it wanted to there. (Maybe because I have no signal or weak roaming where I live?)
I'm seriously considering trying it from an area that I have good service in..