A lot of people in the Project Fi G+ community (for now, only accessible if you are already a Project Fi member) have mentioned having issues with Project Fi not automatically switching between Sprint and T-Mobile, or making a poor determination of which network is the optimal network. For example, at home I know that I have good Sprint LTE service; yet for some reason Project Fi will often have me locked in to T-Mobile, giving me access only to sub-par HSPA speeds.
I ended up flashing the LVY47H image, which is the version that ships on the Nexus 6 if you bought it directly from Project Fi, and I think that helped some of my issues. I finally did see it lock in to a Sprint LTE "geofence" after about 30+ minutes of it switching back and forth. But others may not be so lucky.
Anyway, after some digging around in the Project FI app (Tycho), I came across these phone dialer codes (aka "secret codes"), which can be used to influence which network Project Fi jumps to:
DISCLAIMER: Use these codes at your own risk! I don't know if there are any side effects to these. I am not responsible for any disruption if it any of these break your Project Fi connection!
These are standard dialer codes, so to use them you just open up your (stock) dialer app and type the code. You should not actually hit the call button as if you are actually going to dial the number!
Force jump to Sprint:
Code:
*#*#34777#*#*
34777 = FI SPR
Force jump to T-Mobile:
Code:
*#*#34866#*#*
34866 = FI TMO
Force jump to the next carrier:
Code:
*#*#346398#*#*
346398 = FI NEXT
Re-enable automatic carrier switching:
Code:
*#*#342886#*#*
342886 = FI AUTO
NOTE: I don't know for sure, but I think you might have to do this code to reactivate the automatic network switching after using one of the above to force it to jump to a different carrier!
Attempt to perform an automated "repair":
Code:
*#*#34963#*#*
34963 = FI XME (or if you prefer, FIX ME )
I'm not yet exactly sure what this does to repair anything, but it throws up a dialog that says "Updating..." and adds a notification to the shade that says "Configuring your cellular network...". Presumably this is similar to clearing data in the Project Fi app and re-activating.
Get information about the current network:
Code:
*#*#344636#*#*
344636 = FI INFO
The info in here isn't really all that useful. You can get better/more interesting info elsewhere.
Can't wait to hear the results users have. I know for sure TMo is better in my area
Firsts
Awesome find!
Sweet, thanks posting!
Thanks for posting this. Where did you find the LMY47H Factory Image? I originally had LMY47D and then flashed to LMY47Z and am now having lots of trouble with network speed and getting caught on 3G. This shouldn't be happening where I am (SF Bay Area). Thanks!
rhahenderson said:
Thanks for posting this. Where did you find the LMY47H Factory Image? I originally had LMY47D and then flashed to LMY47Z and am now having lots of trouble with network speed and getting caught on 3G. This shouldn't be happening where I am (SF Bay Area). Thanks!
Click to expand...
Click to collapse
It's LVY47H. It originally only came shipped on Project-Fi-purchased N6's, but it can be downloaded from the "Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)" thread.
maejrep said:
It's LVY47H. It originally only came shipped on Project-Fi-purchased N6's, but it can be downloaded from the "Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)" thread.
Click to expand...
Click to collapse
Thanks! I flashed the LVY47H build to my phone (downgraded from LMY47Z) just now because I have been receiving dreadful download speeds on both T-Mobile and Sprint (Sprint is slightly better) in downtown San Francisco. I've used the codes you posted to try fixing Fi and switching carriers, but T-Mobile is still getting awful 0.03mbps DL speeds. Any other suggestions? Was hoping the Project Fi build would fix things.
rhahenderson said:
Thanks! I flashed the LVY47H build to my phone (downgraded from LMY47Z) just now because I have been receiving dreadful download speeds on both T-Mobile and Sprint (Sprint is slightly better) in downtown San Francisco. I've used the codes you posted to try fixing Fi and switching carriers, but T-Mobile is still getting awful 0.03mbps DL speeds. Any other suggestions? Was hoping the Project Fi build would fix things.
Click to expand...
Click to collapse
If you're getting bad service on both T-Mobile and Sprint, then these codes wouldn't likely help that. The main reason for knowing these would be if you know that T-Mobile is 10x better than Sprint in your area, but Fi is still choosing Sprint for some reason -- then you can force it to switch to T-Mobile (as an example).
I'd suggest you watch your device's logcat while you do some of these, and filter on the "Tycho" log tag:
Code:
adb logcat -v time Tycho
The Project Fi app dumps some pretty interesting information to logcat as it goes through network changes.
Did you try the FIXME code? That kind of tries to go through some kind of subset of activation again, and it might fix something that got messed up.
Also, when you installed the H build, did you factory reset (wipe data)? If not, try clearing data in the Project Fi app (settings > apps > Project Fi > Clear Data), and then reboot. It should try to go through activation again (should be super quick this time), and that might reset something that got messed up.
If that still doesn't work, you could try to do a factory reset. With the H build, the Project Fi activation is part of the factory reset onboarding flow, so that may help.
If that still doesn't help ... ¯\_(ツ)_/¯
maejrep said:
If you're getting bad service on both T-Mobile and Sprint, then these codes wouldn't likely help that. The main reason for knowing these would be if you know that T-Mobile is 10x better than Sprint in your area, but Fi is still choosing Sprint for some reason -- then you can force it to switch to T-Mobile (as an example).
I'd suggest you watch your device's logcat while you do some of these, and filter on the "Tycho" log tag:
Code:
adb logcat -v time Tycho
The Project Fi app dumps some pretty interesting information to logcat as it goes through network changes.
Did you try the FIXME code? That kind of tries to go through some kind of subset of activation again, and it might fix something that got messed up.
Also, when you installed the H build, did you factory reset (wipe data)? If not, try clearing data in the Project Fi app (settings > apps > Project Fi > Clear Data), and then reboot. It should try to go through activation again (should be super quick this time), and that might reset something that got messed up.
If that still doesn't work, you could try to do a factory reset. With the H build, the Project Fi activation is part of the factory reset onboarding flow, so that may help.
If that still doesn't help ... ¯\_(ツ)_/¯
Click to expand...
Click to collapse
Sweet, I'll try looking at the logs. Are you the one in the G+ community who posted that long message about Tycho logs?
rhahenderson said:
Sweet, I'll try looking at the logs. Are you the one in the G+ community who posted that long message about Tycho logs?
Click to expand...
Click to collapse
Yes
maejrep said:
Yes
Click to expand...
Click to collapse
Awesome, thanks for this. I ran through the activation again after clearing app data and rebooting. Interestingly these two logs happened (not concurrently, but one after the other):
06-11 16:07:12.003 I/Tycho (13368): [1501] c.a: Switch done. result:Success errorMsg: requester:EnabledProfiles pluginSwitchCause:0 srcNetwork:T-Mobile LTE destNetwork:Sprint LTE srcSignalStrength:-102 destSignalStrength:-87 currentTimeStamp:11Jun-16:07:12 startTimeElapsedMillis:328153 voiceAtachedTimeElapsedMillis:350173 dataAttachedTimeElapsedMillis:350173
06-11 16:08:02.962 I/Tycho (13368): [1530] c.a: Switch done. result:Success errorMsg: requester:EnabledProfiles pluginSwitchCause:0 srcNetwork:Sprint LTE destNetwork:T-Mobile LTE srcSignalStrength:-91 destSignalStrength:-102 currentTimeStamp:11Jun-16:08:02 startTimeElapsedMillis:375267 voiceAtachedTimeElapsedMillis:401133 dataAttachedTimeElapsedMillis:386586
Correct me if I'm wrong, but it originally switched to Sprint because it had a faster signal strength (-87) from T-Mobile (-102). But then later switched back to T-Mobile even though T-Mobile was still at -102 and Sprint was at -91. I am assuming that the lower negative number is a higher signal strength.
Is this similar to what you've been experiencing?
I can manually switch back to Sprint given the codes you provided, however, Sprint's (faster) connection is still only getting me 1-2mbps. Extremely subpar for LTE. Not sure what to do. Fi support doesn't know what to do, wish I could talk to a Fi engineer.
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
Just got this log:
Code:
06-11 16:19:00.491 I/Tycho (13368): [1538] c.a: Already on preferred network (310260([nMvLJSajLaqzQr8iujifQdNmIe0])); recommending STAY
Do you think T-Mobile is marked as a preferred carrier even if speeds are slower?
It definitely doesn't gauge only by speed (probably not even speed at all, since that would require downloading something and that would cost you data). The initial connection hopping is just to get more data before making a decision. It bounces between them multiple times before locking in.
maejrep said:
It definitely doesn't gauge only by speed (probably not even speed at all, since that would require downloading something and that would cost you data). The initial connection hopping is just to get more data before making a decision. It bounces between them multiple times before locking in.
Click to expand...
Click to collapse
Good point. Looks like the 342886 FI AUTO doesn't actually work. I get the Android alert that it has switched, but then in the log about a minute later I get this:
Code:
06-11 16:41:10.648 I/Tycho (13368): [1581] c.a: Plugin is locked for another 2:54:03.984
06-11 16:41:14.117 I/Tycho (13368): [1] ServiceStateReceiver.onReceive: Ignoring duplicate service state event: In service.
It seems when you manually switch carriers it locks the auto-switching for 3 hours.
All FI AUTO seems to do is reenable auto switching. If it was already locked, then it won't do anything right then. But it'll be eligible for switching after the lock expires. If you don't run FI AUTO, I believe it won't try to auto switch even after the lock expires.
That's all conjecture though, obviously, since they don't explain these details publicly
maejrep said:
All FI AUTO seems to do is reenable auto switching. If it was already locked, then it won't do anything right then. But it'll be eligible for switching after the lock expires. If you don't run FI AUTO, I believe it won't try to auto switch even after the lock expires.
That's all conjecture though, obviously, since they don't explain these details publicly
Click to expand...
Click to collapse
Hey, quick question. My service still sucks. I'd like to factory reset my device and unroot/relock the bootloader with the Project Fi H build so the device will be like it would if I would have ordered it through Project Fi (I didn't, so it's my last guess as to why I'm having issues before determining that service somehow just sucks in the Bay Area).
How would you go about doing this? I have a Mac, so I can't use Nexus Root Toolkit natively, but apparently can do it through a VM (I have Parallels). Do you know if this will wipe/reset/unroot/relock my device into the Fi H build or not? What route would you take?
As far as I can tell, you're most of the way there. If you flash the image mentioned in the other thread, wipe data, and flash recovery back to stock, that's it... I don't think anyone would be able to tell the difference, other than the bootloader being unlocked.
Thanks for providing these. I've been having issues receiving calls. Everything else works no issue. I tried the repair code. When inputting that code, the screen says "Updating" for a moment, then "Update successful" and the mobile signal icon goes "hollow" and then a moment later (15-20 seconds?), the icon fills in again. If I place a test call in the time that the icon is hollow, the call will go through with no issue. If I place a call after the mobile signal icon fills in, the call will NOT go through. I have tested this repeatedly from an AT&T line and a landline and it works each and every time.
This is super strange. I've forwarded that to Fi support on my ongoing case. Hopefully it will help some.
rhahenderson said:
Hey, quick question. My service still sucks. I'd like to factory reset my device and unroot/relock the bootloader with the Project Fi H build so the device will be like it would if I would have ordered it through Project Fi (I didn't, so it's my last guess as to why I'm having issues before determining that service somehow just sucks in the Bay Area).
How would you go about doing this? I have a Mac, so I can't use Nexus Root Toolkit natively, but apparently can do it through a VM (I have Parallels). Do you know if this will wipe/reset/unroot/relock my device into the Fi H build or not? What route would you take?
Click to expand...
Click to collapse
factory reset gave stock unrooted H [in settings]
norwoodesteel said:
factory reset gave stock unrooted H [in settings]
Click to expand...
Click to collapse
Thanks. I actually decided to just give it some time before doing anything drastic. I'm fine with it now. In pockets of bad service, I have WiFi anyway, so I'm just gonna let the Fi team work out the kinks.
I just wish project Fi would release the factory rom they use on their n6s. They stated it was the same but with minor tweaks for project Fi
Related
The following link is a very good read about how Project Fi works. Things touched upon:
1. The Google Fi SIM has two profiles
2. The active profile switches between networks
3. Switching networks is fast, but not instantaneous
4. Calls do handover from Wi-Fi to cellular…
5. …but not seamlessly…
6. …and don’t transfer back
7. Calls do not handover between cellular networks
8. Data does not handover between networks
9. The Google Fi SIM does work in other phones
10. Global roaming is done only through T-Mobile
http://nicholasarmstrong.com/2015/08/network-handover-google-fi/
All credit goes to Nicholas Armstrong.
Thanks for posting this. Great reading.... :good:
quailallstar said:
Thanks for posting this. Great reading.... :good:
Click to expand...
Click to collapse
Yeah, I had a basic idea of how it worked before, but this article definitely opened my eyes a bit. The tech behind it is pretty amazing actually. But I was surprised to learn that once it handsoff to cellular, it stays there until the call has ended. I thought it just kept switching.
Imagine if Google bought/absorbed bandwith/republic wireless....
Project salsa would add cell to WiFi handover.
Maybe more plan options?
I left them when I realized rom updates were going to take eons to happen. And I wasn't a huge fan of moto x.
Sent from my Nexus 6 using Tapatalk
One big quibble I have with the article's test methodology is that the tester enters the debug dialer codes to force switching between carrier networks, observes and times that switching behavior, and then jumps to the unsupported conclusion that automatic switching functions the same way.
interesting read, thanks for posting.
I just tested the SIM card in a 1 + one phone and I could make and receive call..
I will try the SIM in a window phone..
Worked fine on Blue cheap window phone, t-mobile was the carrier to place call where I'm..
Great..
What is exactly the Nexus 6 exclusive then?
pas7771 said:
What is exactly the Nexus 6 exclusive then?
Click to expand...
Click to collapse
There is a lot more to Project Fi functionality than just making a call on T-Mobile. It has dynamic switching between Sprint and T-Mobile, as well as WiFi.
Interesting. I thought Fi advertised cell call handoff to wifi when entering buildings.
boomerbubba said:
One big quibble I have with the article's test methodology is that the tester enters the debug dialer codes to force switching between carrier networks, observes and times that switching behavior, and then jumps to the unsupported conclusion that automatic switching functions the same way.
Click to expand...
Click to collapse
This is an excellent point
I have been entering the sprint code every couple hrs to get my calls to work. Project Fi support has no idea why or what is going on. The had me run a bug report. Hopefully that will get this resolved. Any one else on Project Fi having this issue?
Jayson
Still waiting to hear back from Project Fi team. I just spoke with the Nexus support team and was told there is no going back to 6.0 from 6.0.1. The tech I spoke with said that they have logged 7 calls with the same issue me. Mine now makes it 8.
Even though I am a bit frustrated with this issue Google support folks are 1000 times more knowledgeable and easier to work with than Verizon. This company gets how to treat and deal with customers.
Still not working yet. Google is going to give me credit for the inconvenience but I am beginning to lose faith in them getting this resolved. Switches back to T-Mobile and I keep missing calls. Uhhhhg. I really want to stay with Project Fi but I may be forced to look elsewhere for cellular service.
Have you tried *#*#34963#*#* ?
I had a similiar issue to you.
Where I live and where I work I get a stronger signal from Sprint than T-mobile.
After I updated my phone to 6.0.1 I had problems connecting to Sprint's network.
I used the "FI XME" dialer code and that seemed to fix my issue:
*#*#34963#*#*
I found a post in the Nexus 6 forums with the Project Fi dialer codes:
http://forum.xda-developers.com/nexus-6/general/project-fi-fi-dialer-codes-to-force-t3132393
Another reference for the Project Fi dialer codes:
https://productforums.google.com/forum/#!topic/project-fi/IkOy8ZGNyPk
Hope this helps.
I'm not on FI, got the sim card just haven't switched yet lol. Ummmmmm see my thread my phone is getting horrid LTE speeds, I put in a ticket. And I'm on T-Mobile this is crazy
Sent from my Nexus 6P using Tapatalk
Tried all the codes. Hopefully Google Tech support will have an answer soon.
jaysong said:
Tried all the codes. Hopefully Google Tech support will have an answer soon.
Click to expand...
Click to collapse
Does T-mobile service work where you are, did you have it before?
Yes. T mobile is strongest signal where I am . Worked great until the update.
Look up it may be related to this: http://forum.xda-developers.com/nexus-6p/help/lte-issues-6-0-1-radio-canadian-carriers-t3267270
Here's the google issue: https://code.google.com/p/android/i...tars Reporter Opened&groupby=&sort=&id=197102
jaysong said:
Yes. T mobile is strongest signal where I am . Worked great until the update.
Click to expand...
Click to collapse
Ah yes then that's a problem, the Google update to 6.0.1 has caused all kinds of radio problems so let's hope they fix it quickly.
My issue seems a different. The Data and texting works fine on WiFI only, Sprint and T-Mobile. The issue is calling in and out on T-Mobile. Instant failure.
I'm having the same problem but I think it only happens when the phone connects to band 12 LTE on T-mobile. It seems that VoLTE isn't working properly. Can you check what T-mobile band you are on using this app:
https://play.google.com/store/apps/details?id=com.blueline.signalchecklite
Says Provider: T-Mobile B4
I'm having the issue where my data speeds suck. Since update
Sent from my Nexus 6P using Tapatalk
Possible fix
Hey jaysong try dialing *#*#info#*#* enter phone information the upper right corner tap the 3 dots select the band and then select USA band. Once i did that my t-mobile calls starting working. Please let me know if this works for you.
toves75 said:
Hey jaysong try dialing *#*#info#*#* enter phone information the upper right corner tap the 3 dots select the band and then select USA band. Once i did that my t-mobile calls starting working. Please let me know if this works for you.
Click to expand...
Click to collapse
Be careful! I did this on my last 6P and it completely messed up my radio and prevented me from making calls on Sprint (no it wasn't because of the SIM card as I tried 3 of them) . I had to RMA my device. My advice is not to mess with that menu. I have done it on other devices without issue but it seems as though once selected it cannot be undone.
I just found out yesterday that the engineers have not even looked at my bug reports yet. They were sent to them yesterday from what I was told. They also had me order a new sim card as well to rule that out. The support or lack there of up to yesterday has be ridiculously unacceptable. I get the feeling that they are just trying to pacify me and not doing anything in hopes that a new release will come out an magically fix this issue. Very frustrating.
Problem Fixed. After dealing with this for several days I asked a supervisor how long was acceptable to leave a customer with an open issue affecting cellular service and to be missing calls. He provided me a RMA and a new phone was sent. All seems to be work with the New replacement phone they sent.
bigdave79 said:
Be careful! I did this on my last 6P and it completely messed up my radio and prevented me from making calls on Sprint (no it wasn't because of the SIM card as I tried 3 of them) . I had to RMA my device. My advice is not to mess with that menu. I have done it on other devices without issue but it seems as though once selected it cannot be undone.
Click to expand...
Click to collapse
Yes be very careful in that menu. I was just looking at the menu and my finger some how hit a different band. Took me about 4 hours to figure out how to fix it. There are some tuts here on that issue that will help. Also there's a way to get the international bands to show up
I purchased this phone from ebay, and of course the seller will not accept a refund/replacement..... arg.
Anyways, i tried to activate my google FI service on the phone, and i noticed it wouldn't connect to a cell network. I tried my google fi card in another nexus 6 (not p) and it works fine, so i tried another t-mobile sim in the 6p and that doesn't work either.
It seems that it will kinda connect to sprints network, SOMETIMES, if the moons align. i live in the middle of Minneapolis where my rooms mates phones both sprint and t-mobile, work with full signal.
My question, could the ebay seller have done something like messed with the phones modem/ROM/Radio that would cause this?
So far, i have unlocked the bootloader and re-flashed the angler-mhc19q-factory-f5a4e7a1.tgz 6.0.1 image , but that has not improved the situation.
Any one have any ideas?
For what it's worth file a claim with PayPal which trumps eBay's policies if you paid via PayPal. It may take awhile, you may initially lose but they have an appeal process which may allow you to return to seller for refund. The process may take some time and effort but give it a whirl.
Now, as far as the Fi, I rarely connect to Sprint as of late even if I force it using the codes. Join the project Fi community on Google plus!
It may not be the phone as it seems it may be a Fi issue. Here are the codes to force connections:
*#*#34777#*#*Sprint code
*#*#34866#*#* TMO code
*#*#346398#*#* Fi next
*#*#342886#*#* Fi auto
*#*#34963#*#* Fi fix
Copy one of them, open your dialer as if to make a call, paste the full code but don't make or complete the call. Just close the dialer.
You can also ask Fi to send a replacement sim card. Also, call their support team which is actually pretty good!
Sent from my SM-G935V using Tapatalk
Thanks for that information. I actually did try those codes while I was on the phone with tech support with Google Fi. Problem is it never fully switches over to the T-Mobile code. It's like it's almost stuck on Sprint mode.
I was thinking I'm filing a claim through PayPal, but course I'd much rather get the phone working been waiting all that time. Is it possible that the owner was messing around with ROMs and screwed something up that might be fixable? On that note, does flashing the file I mentioned in the original post reflash the modem or radio? Could I possibly flashing older ROM and modem/radio that might work?
Its possible the previous owner was in the service menu and changed some settings. Dial *#*#4636#*#* and have a look around. It could be set on the wrong band or roaming mode. I had a similar issue that I created myself by choosing the USA radio band by accident. I beat my head against the wall before I figured out it needed to be band 6 instead. It could also be set on LTE/CDMA auto prn like mine which works great for Verizon but I suspect would cause issues for Fi or any of the GSM carriers.
---------- Post added at 10:39 PM ---------- Previous post was at 10:34 PM ----------
When you reflashed the image did you do that via fastboot or recovery? The radio and bootloader can only be updated by using fastboot commands. Heisenberg has an excellent guide on how to do this in the general section. Its the first post.
File a claim with paypal.. They are real good in the resolution process
Does it connect on edge? I'm curious because after I upgraded my 6p to the mhc19q build I've had a lot of trouble getting anything but edge on t-mobile. Working with both t-mo and Google support now.
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..
Before I updated via OTA to 8.1 the Essential was connecting to LTE without issue. Since 8,1 I have to connect to CDMA and 3g in order to user my Dialer, otherwise Server Error is generated. No calls in or out.
I wanted to downgrade Yes rebooted, factory reset, etc.
I searched google up and down with no real answers that work. How do I get Sideload working again? It has to be a simple configuration or driver problem I will assume.
Thanks
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Exxeviant said:
Im in the same situation you are in also im on 3g at 1.50mbs up & down i have searched every where....
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
wolfu11 said:
Here you go
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
Click to expand...
Click to collapse
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Bigdny said:
Thanks. Still stuck using 3G. I can connect to 4G/LTE but cannot make phone calls as I still get the Server Error, Try Again.
Click to expand...
Click to collapse
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
wolfu11 said:
Well I reset my PRL via *228 and sure enough selecting 4G/LTE does put us at LTE/wcdma but my phone functions perfectly. I do notice the menus are changed and I got a couple other options though now. See attached
Click to expand...
Click to collapse
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
wolfhelm said:
Yep those are how the menu should look for a device that's not locked to sprint. It seems to me there are some firmware files that prefer sprint in these beta builds, because even on other carriers (and more than one person has said this) you can see 'sprint' pop up in the bar or in the settings even when you arent on sprint.
Interesting that yours gives you the option of 'wifi calling provisioned', I cant get that to not be greyed out on mine.
Click to expand...
Click to collapse
Yeah I've screwed with this phone so much I don't know what I did LOL but now it shows wifi calling even in dialer. I'm not sure if it really works cuz I have a good signal so it never switches. My e911 address is set up from my Moto z and I do have a wear24 watch tied to this phone not sure if that's what triggered it. ? I did get a new SIM card on Monday as well because I was fighting with the vzw crap so I don't know exactly what triggered the WiFi calling.
wolfhelm said:
I wrote that post that he referred you to, and while it worked in Oreo 8.0 it does not seem to work in 8.1 for me either.
Try this:
dial *228 and get a PRL update
reboot
*#*#4636#*#* (it may take a few seconds for it to come up if you do it right after a reboot)
set it to LTE/WCDMA
reboot
(you may have to check in mobile network settings that your APN is set to VZWINTERNET)
Let me know how it works out for you. I know that Verizon doesnt support WCDMA, but it forces you over to the Verizon LTE bands which is more or less the goal of this. For some reason this functions differently than any of the other settings that include LTE in them (believe me, I've tried them).
Click to expand...
Click to collapse
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?
wolfhelm said:
Are you on 8.0 or 8.1?
Click to expand...
Click to collapse
I upgraded to 8.1 via OTA. No root, no rom.
Bigdny said:
I upgraded to 8.1 via OTA. No root, no rom.
Click to expand...
Click to collapse
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
wolfhelm said:
That's where I'm at too... the one thing that might be different about this is I tried my old steps first before figuring out how to get it to work with these new ones... seems like a lot of effort, but it might be what is needed (or some amount of it) to get it all working. So try going through the old ones before the new ones (you probably dont need to *228 again since you just did)
My old steps linked here (these worked in 8.0, if they work for you in 8.1, more power to you, but they dont work for me):
https://forum.xda-developers.com/showpost.php?p=74920423&postcount=506
I'm still routinely messing with it because I feel like the setting I have now prevents me from falling back to CDMA if LTE is unavailable for some reason. Fortunately that is a rarity for me... but I maintain that Essential has something in the ROM itself that is preferring sprint and I think it's screwing with us using Verizon.
Click to expand...
Click to collapse
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
tech_head said:
There is something there.
I've done that procedure.
If I go into the menu and play around it will try to connect to sprint even with a Verizon SIM. Go figure?
Click to expand...
Click to collapse
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
wolfhelm said:
Exactly. If I leave it on certain settings it'll actually sit there and tell me I'm connected to Sprint.
Click to expand...
Click to collapse
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
That's a good point, I have reported as well.
tech_head said:
I just reported this to Essential in their beta feedback.
Others should report their similar issues.
It seems to be associated with them making a unified release.
If you look at some releases they are specifically for Sprint or Not.
Click to expand...
Click to collapse
Doing the same right now. Just glad Im not the only one having the problem.
Bigdny said:
Thank you for the steps but still cannot use 4G for phone calls, but it does work for internet, facebook, email,etc.
Have to go back to 3G for phone calls.
Very interesting why it happening and not widespread. No special configurations or setups on my phone.
Click to expand...
Click to collapse
Try turning off Enchanted 4G LTE Mode. It's possible going to 8.1 just reset this setting to on. This should only be on if you have HD Voice enabled on your line on Verizon (you'll have to call Verizon to enable it, it's a free feature).
This should fix server error on 4G, randomly connecting to Sprint is a separate issue.
UPDATE Now working
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Bigdny said:
Took the advice from someone on Reddit who had the same problem. Ran to VZW store and received a new SIM. Without any programming on my end or reboot, back to LTE without issue. FINALLY. As soon as the rep popped in the SIM the essential connected on its own.
Click to expand...
Click to collapse
Just wanted to second this post that a new sim card is the key to solving this issue. In my case, I was using Red Pocket CDMA (VZW network), and I ran into the same problem. Red Pocket rep explained to me that my sim got provisioned to 3g only and that I needed a new sim to connect to LTE. As soon as we switched to a new sim, I got LTE. I hope this helps others.