I upgraded to the new DCD Beta 2.0 and when I try to connect to the mobile internet I get an error stating it cannot connect for an unknown reason. It also states Error Code: 11 - PPP Connection Error.
I am on Verizon and dialing #777, this still happens when I manually enter my username (ph#@vzw3g.com) and vzw password. I've tried a hard reset, but still the same issue.
Any ideas or does it look like a call to Verizon?
Ok, So I called Verizon and talked to the for a long time. They think it's a bad phone and I should try and get a warranty replacement.
I'm pretty sure there has to be a setting in the rom that I can change from when I originally had the Sprint ROM on there.
Any ideas?
I have Verizon also. I pay as you go so I normally do not connect with the data connection. So I put in your settings and had no problem connecting or surfing the web. I am also running the new rom. Hope this helps.
I think my main problem is that I installed the Sprint 3.16 "unofficial" rom onto my phone. When I went back to the Verizon rom I had to manually load a PRL to get back on the Verizon towers. Now I need to figure out what else to change to get Data Back.
Data/MMS OTA download resolved
Good news I got it fixed. I had to call Verizon. It's a problem on their network, something to do with the way the account is provisioned. This is an issue that shows up for folks that don't have an unlimited data plan and are only setup for pay as you go. I wish I could give you more detail about what to say but as usual with tech support it depends on who you talk to. I would just keep calling back until I got to the right person.
Data Connection Resolved
I also had a similar problem on the VZW network. Tried many setting changes last weekend to no avail, I needed to get a new A-key so I downgraded to 1.6.10 because of the 3.27 radio issues. The Data connection still didn't work, so I called and got a new A-key, then once that was working, chased the Data connection with a different tech support group, they tried the usual resets and programming. Finally, the tech guy exhausted his list and pushed the problem to network support, an hour or so later the data connection was working again. Network support called later to check to see if my problem was resolved, which it was. He said they had to reset the local switch, something about a hung data session.
I've on Sprint, and I've been having problems getting my data working again with the new 3.16 ROM. I called tech support, and after verifying all the settings, they looked for outage reports.. and found a global Sprint vision provisioning issue currently logged. We'll see if things improve in a few hours..
I already started this at the end of this thread:
http://forum.xda-developers.com/showthread.php?p=1881093#post1881093
but now I'm in real trouble so I'm starting a new thread hoping for help.
I was using 3.16 ROM on my mogul and all seemed fine until today I got an authentication error while voice roaming(edit: I said data roaming initially by accident). I called sprint to get an HLR reload becasue the above thread indicated this was helping people.
My phone quit making calls and quit data connections. Data ended with "cannot connect for unkoww reason". Calls simply disconnecte imediately. I could call *2 though.
Sprint had me rest my phone a few times and the checked the MSN/MSID info (which was fine) and evenutually sugestet I try the official rom (yes I was honest with them). I tried this, flashed 2.17 same deal.. after an hour with a tech he eventually told me the 2.17 is an "upgrade" rom and that it won't overwrite everything and that I should reload the original rom... so I just loaded 2.09.. checked MSN and MSID... in fact checked every setting in the EPST stuff against my touch. Everything is the same... except the security section (which doesn't exist on the touch) had the wrong username was my [email protected]nt... instead of sprint email) and some giberrish for a password.
I'm not sure what this should be, but actually I doubt it's the issue.
I'm stuck though. My phone is effectively bricked(it plays bubble breaker well at least) and I'm at a loss. Please advise if you can.
I just got off the phone with sprint. I have reverted to the 2.09 ROM. With the sprint reps help I did "master reset" which i didn't know existed. This is deeper than both a soft reset and a hard reset. It resets all the EPST data like MDN and MSID. We then set these back to what they should be. But no dice. She told me the phone radio must be broken and claimed that the *2 call uses a different radio. (really? does anyone believe that?) So her advice was to go to the repair center (which is 40 miles from here). OH.. and she put a diferent MSID which I find strange. It's no longer my phone number. I asked her if this was right and she said it probably changed when I asked for the HLR reload but that it was correct... weird. I'm in bad shape.
I called back becuase after forcing the phone to roaming I got an interesting message from verzion sayign they would transfer me to their operator where I could pay money to make a call... doesn't sound like a broken radio to me.
So I told the guy this but this time I got someone who knew what he was doing and before I could finish telling him about it he had it fixed. Aperently there was a setting in there system called HSA_Roaming_only that was set incorrectly and was forcing to try to connect to other networks. He checked it (I think.. or maybe unchecked it..) and voila... after several hours and three roms... it works.
The same thing happened to me when I did an HLR reload. I called sprint and told them my symptoms and they fixed it within 3 minutes. I didnt reinstall anything. You got totally whored by sprint, I feel for you.
dagurasu said:
I called back becuase after forcing the phone to roaming I got an interesting message from verzion sayign they would transfer me to their operator where I could pay money to make a call... doesn't sound like a broken radio to me.
So I told the guy this but this time I got someone who knew what he was doing and before I could finish telling him about it he had it fixed. Aperently there was a setting in there system called HSA_Roaming_only that was set incorrectly and was forcing to try to connect to other networks. He checked it (I think.. or maybe unchecked it..) and voila... after several hours and three roms... it works.
Click to expand...
Click to collapse
Did this allow you to EVDO roam? I cant data roam on EVDO and my girlfriends phone can. She is on the 2.17 official and i am on the 3.17 unofficial.
dagurasu said:
With the sprint reps help I did "master reset"
Click to expand...
Click to collapse
How do you do a master reset?
In the end I did get everything working again. I did get voice roaming working on 3.16 and I do have 1x roaming. I don't believe I have evdo roaming, but I probably won't know for sure until I go into work tomorrow.
I don't think the master reset was needed in the end.. but I could see that it might help someone someday. There is I think a ##something# code to get to the full epst settings, but I just go to \windows\EPST.lnk (edit: this is wrong.. see my next post)
Run it, select edit.. enter you MSL.. please don't ask how to find it.. search. Then under the menu tab... right soft key there is a reset option that I never noticed before. This will reset all the radio setup options to some default values and will do hard reset... erasing your data as usual. I have no idea where these defaults live on the phone... It seems like some roms end up changing at least the MSID and MDN, but some don't. I don't know what else they might change or how they affect what the defaults are that this resetting does.
In summary to my issue, there were two problems:
1) MSID was changed (during the hlr reload) in sprints system to something other than my phone number, (and now it likes to go back to phone number in my phone during upgrades thus not matching with what sprint has)
2) the HSA_ROAMING_ONLY flag in SPRINT's system (not my phone) was set wrong.
You got totally whored by sprint, I feel for you.
Click to expand...
Click to collapse
oh well.. not the first time.
dagurasu said:
In the end I did get everything working again. I did get voice roaming working on 3.16 and I do have 1x roaming. I don't believe I have evdo roaming, but I probably won't know for sure until I go into work tomorrow.
Click to expand...
Click to collapse
keep us updated on the evdo roaming. this is a big deal to me and i hope this isnt like this in the final version of the rom...
First.. I'm wrong about the reset.. it seems you must do the ##something# to get the epst that has the reset option in the menu tab. Opening through the windows link doesn't give that option. (edit: it's ##786#.. some googling found it.. doesn't seem terribly common information though plus google won't take "##".)
I am not getting evdo roaming and I'm pretty certain there should be verizon evdo coverage here... in fact I occassionally see the evdo symbol briefly when I switched to forced roaming, but it goes away immediately.. I suspect it doesn't authenticate.
Being that verizon seems to have much more evdo coverage than sprint, and that they make like $40 a month off their own customers for access to it(last I checked), it wouldn't be at all surprising if sprint can't pay/provide them enough (with all these sero plans) to get them to allow it. But I speculate.
Did anyone ever have this working? I never did.
well mine wont evdo roam on the new leaked rom. But my girlfriend has the same phone in the same house with the 2.17 rom and can evdo roam just fine... so it is baffling me
Something about the new rom is causing the problem, because having these two phones side by side and them acting differently is strange. mine also roamed fine on evdo before i installed the leaked rom btw
Everything else seems to function as normal, but the no evdo roaming is driving me mad. i really hope this isnt an issue in the official rom when it comes out.
we are also both on sero plans and roaming on alltel towers here.
Masater Reset Code
in order to do a master reset you need your MSL# then type ##MSL# and then you can do the master reset this will reset everything and i mean evereything to factory defaults. you will have to go through the sasme initial setup as when the phone was activated the first time. so make sure you have all your correct MSN/MISD numbers
tlhop911 said:
in order to do a master reset you need your MSL# then type ##MSL# and then you can do the master reset this will reset everything and i mean evereything to factory defaults. you will have to go through the sasme initial setup as when the phone was activated the first time. so make sure you have all your correct MSN/MISD numbers
Click to expand...
Click to collapse
Hmm .. when I go in there I still do not see where I can do a master reset. All I can do is change the MDN and MSID and then select OK.
Cool. I haven't been able to roam on Verizon's towers since I added the leaked ROM either. If I can manage to get through to tech support (the CSR in chat said she couldn't help me) I will have them reset the HSA flag to allow high speed digital roam.
well mine wont evdo roam on the new leaked rom. But my girlfriend has the same phone in the same house with the 2.17 rom and can evdo roam just fine... so it is baffling me
Click to expand...
Click to collapse
I'm on sero too, but again it's verizon roaming here.. so may be related to why it never worked for me in the first place. You could dare to just call sprint and ask why it's not working.
tlhop911 said:
in order to do a master reset you need your MSL# then type ##MSL# and then you can do the master reset
Click to expand...
Click to collapse
This is wrong.. this won't get you there, at least not on my phone.. and actually you DON'T need an MSL... BUT you better have it handy to fix things after you do the reset.
Just do ##786# as I stated above (sorry for the confusion the first time) and then look in the menu soft key.
EDIT: After you do the master reset... then you can do the ##MSL# and fix your MSID and MSN to what they should be.
To neodorian... please read what I wrote... this flag DID NOT do anything for my data roaming (and I am in verizon territority) This didn't even fix the usual voice roaming problem as far as I can tell (that's something else unknown which is fixed by the HLR reload, this only fixed my rather unusual problem where I could ONLY roam... and furthermore had to supply a credit card number to do so! This was something sprint broke for me just because they liked me better than you.
I had the authentication issue on my VZW XV6800 - I called in to tech support and after talking to the first person, and mentioning a HSL reset, she transferred me to level 2. The guy had me do basic troubleshooting, and examined some settings, then had me remove the battery for at least 1 minute. reload phone, try over the air programming, and test calls. all to no avail. he then had me go in and edit the settings using ##778 (VZW default password for editing is 000000) you don't need to use the hex code and program designed to give you the password, especialy since I tried this, and it didn't work.
Anyway, he generated a new A(uthentication) code on his end, had me manually input it, and he also had me change my Home SID/NID. Mine said 30/65535. He said it should be 30748/65535.
I then did another *228 #2 and was now able to make a test call. After hanging up I went back and looked, and the Home SID/NID #1 was 30/65535 again. Not sure if those extra numbers did anything, but the phone got rid of them.
I am able to call out and receive calls now, and the data seems to be zipping right along. When I tested gps last night it had me miles from where I was located.
UPDATE:
GPS seems to be working fine. I'm guessing the tower I was "connecting to" was miles away, since I live at the base of a butte, and have terrible reception. Most likely that WAS the closest tower to where my phone was.
I cant pinpoint exactly when this started happening as i rarely go into roam...but i believe it was after the 3.16 radio install. Anyways whenever my phone tries to roam now i get a Verizon operator messages saying i am unauthorized. My carrier is Sprint
Hax0rpunk said:
I cant pinpoint exactly when this started happening as i rarely go into roam...but i believe it was after the 3.16 radio install. Anyways whenever my phone tries to roam now i get a Verizon operator messages saying i am unauthorized. My carrier is Sprint
Click to expand...
Click to collapse
call or email sprint tech support to have them look into this. they solved mine after rom upgrade.
Hax0rpunk said:
I cant pinpoint exactly when this started happening as i rarely go into roam...but i believe it was after the 3.16 radio install. Anyways whenever my phone tries to roam now i get a Verizon operator messages saying i am unauthorized. My carrier is Sprint
Click to expand...
Click to collapse
DO NOT Call Sprint if you have upgraded your Radio or ROM to anything else that Sprint hasn't released. This can result in you voiding your warranty if you aware them of your upgrades.
If you installed a new radio and ROM are you sure that you installed the Sprint version not Verizon's? What some have done to fix roaming issues is call *228 and program there roaming capabilities from there.
Also maybe your A-Key for Sprint just needs to be refreshed / re-entered. check your MSID and make sure that it is displaying your phone number, and that you have the current PRL installed on your phone.
To reach these settings dial ##778.
[email protected]$ said:
DO NOT Call Sprint if you have upgraded your Radio or ROM to anything else that Sprint hasn't released. This can result in you voiding your warranty if you aware them of your upgrades.
If you installed a new radio and ROM are you sure that you installed the Sprint version not Verizon's? What some have done to fix roaming issues is call *228 and program there roaming capabilities from there.
Also maybe your A-Key for Sprint just needs to be refreshed / re-entered. check your MSID and make sure that it is displaying your phone number, and that you have the current PRL installed on your phone.
To reach these settings dial ##778.
Click to expand...
Click to collapse
So i tried the few things you said, *228 says invalid feature code, my MSID is correct, had Sprint update my PRL and no luck. But one thing i noticed is that my A-Key is blank...how can i go about obtaining this
---back story---
I updated my vogue from 6.0 to 6.1 and it would not turn on.
After many different attempts (and changing my radio a few times because it kept saying no radio) I got it to load with a rom from a foreign country, then I tried us cellular then sprint and all of them said I was roaming.
I then updated to a kitchen 6.5 rom and it still says I'm roaming.
---------------
My carrier is Inland Cellular (when roaming it is through the Verizon Network)
I'm not actually roaming but the warnings are quite annoying.
So my question is would changing my radio again fix it?/What radio would I use or would it matter?
In one of those updates, if you let any of their customizations run it may have changed the PRL file (roaming file). The only way to get rid of the roaming triangle would be to get one for your carrier (Inland Cellular). I would no recommend placing calls on your phone, you could be roaming on who-knows network.
I'm trying to track down a PRL for your network, but I am totally not finding one. I'll keep an eye out though. If you know a forum for people with the same carrier as you, you might want to look into getting a PRL from them. ^^;
To update your PRL after you have the file, dial ##PRL# on your phone, type your MSL (use MSLGrabber if the code is not 000000), and then hold the box with an empty file name until a selection box comes up, tap it, then find the PRL file on your phone... blah blah blah select okay. Commit the change to the phone, restart...
Now to just find one. -_-
Thank you so much!
Turns out I was roaming on some random network so I did have a few roaming charges, but when I went up to pay the charges I explained to them (the part they would not get mad about) and he said that if I bring it back tomorrow he could fix the PRL, and due to the fact that they don't tell their customers about only updating with download from their site I am not the first person to do this. Thank you for your insight TheXev!
Awesome, glad to be of service.
So turns out my carrier decided not to help... Not because I am running a kitchen rom or anything like that, but because I had an unofficial battery in my phone. (I bought it as a refurb from them and they still said my warranty is now void)
THEN IT HIT ME. I grabbed my old inland cellular titan and extracted the PRL and loaded it onto mine! NO MORE ROAMING!
Problem solved!
Good idea. I've had to do that before. You should post your PRL file somewhere online so others can download it. I don't think you can do it on XDA until you have 10 or more post.
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..