yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
I just got thru doing a complete recovery, starting with stock 6.0.1 due to snowballing problems that began with the camera not working any more.

When it booted and was setup I stopped Play Store auto updates and then checked the /system/app/tycho folder. There were 2 items in that folder: Tycho.apk and folder 'oat'. The folder had sub folder arm64 and in it was file 'Tycho.odex'

The phone activated PFi and only the original 1.4.0.7 file was on the phone. I'm still running that version and haven't got the Playstore update yet.......so it sounds like it was ready to go on PFi when the phone left Project Fi. Not sure if that even matters though unless there is some major differences between the two.

Thank you for the detailed responses. Very interesting stuff in this PFi thing!!

More later.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
So it sounds to me that having the Project Fi SIM inserted enables the otherwise disabled Project Fi (tycho) app as I have factory restored MDA89E many times with the Project Fi SIM not inserted and tycho has always come up disabled by default.

The oat folder is the pre-compiled version of tycho.apk. It can be generated from tycho.apk
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Sounds about right.

The problem as I see is the missing settings>wireless>more>cellular>home/auto

The phone stays in the home mode and will not roam on cdma. I'm pretty sure it has roamed on GSM though....:confused:

Changing the setting in the tycho xml file or in the other location to enable those network settings causes things to break. So even though the phone roams with this change the routing of calls is affected. In the phone info tool *#*#4636#*#* show 2 different phone numbers. On GSM mode the actual # of the phone is shown. In CDMA however, there is a completely different # that is in the same area code as the other #.

So it seems that changing the phone roaming mode from home to auto affects the way cdma calls are routed and wifi calling also affected.

Also, the original setup allows the tycho app to use its own settings instead of the phone network settings:

<uses-feature android:name="android.hardware.telephony" android:required="false"/>

Changing from home to auto then seems to cause conflicting settings and problems.

Where are the actual phone network settings stored in android?? I haven't found them yet. Not sure what would happen if they were changed to match whatever tycho uses.
[Nexus 5X Q&A, Help & Troubleshooting] Voicebox:
A pure guess on my part, but I think you have stumbled on why the selection is disabled. Sounds like it screwed up something else when selected, so their fix was to disable it since CDMA roaming affects relatively few people. Functional wifi calling is way more important than CDMA roaming as an example.

I think they're going to have to work out a lot of bugs by the time they release (hopefully) a new set of phones later this year. I bought the inexpensive 5X in anticipation of upgrading when their next phones come up. Hopefully, with a year or whatever of actual experience from users, the next ones are more functional out of the box.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
Honestly I think they intentially disabled the default UI and this isn't a bug from their standpoint, though they could have disabled the UI and left CDMA roaming set to auto.

Are you saying there is one number in CDMA 4636 but it doesn't match your GSM 4636 phone # or are you saying there are 2 phone #s listed in the CDMA 4636?

My stock ProjectFi setup has a different phone # under CDMA 4636 than my actual phone # (actual # shows up in GSM 4636) so that part seems normal.

Have you looked in /data/data/com.android.phone (files and shared_prefs) for the xml files?

Dynamic stuff is probably in some sqlite db somewhere.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I think the MIN # is used for intermediate phone call routing. MIN # used to be the same as your Phone # before number portability.

Our phone #s are from TMobile's phone # pool. I wouldn't be surprised if Google is using the MIN # to do some special routing into Sprint's system as Project Fi members, our "phone #" needs to be good on to separate cell phone network infrastructure.

I am not exactly clear which method they are using to pull that off but there is some stuff going on underneath the hoods.

For example if we get an incoming call, how does it know which network we are on, do our phones register that information when they switch networks or is Fi just taking advantage of Google Voice infrastructure to call multiple #s for a single incoming. If the latter, do we have some "shadow" phone # on Sprint tied to our TMobile phone #.

The Tycho xml files look like configuration for the Project Fi app that you edited in the apk. I'm curious, what happens if you change the setting (in the xml file found in the /data directory rather than the one in the apk) to false?

<boolean name="hide_carrier_network_settings_bool" value="true" />

does that have different behavior than changing the setting in the .apk and repackaging? I know sometimes when the package signatures get messed up due edits, apps sometimes behave differently than when they were originally packaged.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
You must have read my mind. Just tried that and more.

FILE: \com.android.phone\files\carrierconfig-com.android.carrierconfig-89011201004001880640.xml

Line 16 <boolean name="apn_expand_bool" value="false" /> Change to True

FILE: \com.android.phone\files\carrierconfig-com.google.android.apps.tycho-89011201004001880640.xml

Line 8 <boolean name="force_home_network_bool" value="True" /> Change to False
Line 17 <boolean name="hide_carrier_network_settings_bool" value="true" /> Change to False

FILE: \com.android.phone\files\carrierconfig-com.android.carrierconfig-8901260971103773923.xml

No changes

FILE: \com.android.phone\files\carrierconfig-com.google.android.apps.tycho-8901260971103773923.xml

Line 8 <boolean name="force_home_network_bool" value="true" /> Change from True to False
Line 18 <boolean name="hide_carrier_network_settings_bool" value="true" /> Change to False

FILE: com.android.phone\shared_prefs\_has_set_default_values.xml No Changes

FILE: \com.android.phone\shared_prefs\com.android.phone_preferences.xml

RENAME EXISTING FILES TO BAK AND PASTE MODDED FILES INTO FOLDERS

Changed files, rebooted, no change in cellular settings or roaming.

Uninstalled the PFi app from the play store and reverted back to the original one in the tycho folder. Can now change the home/auto and get some roaming on cdma.

Rebooted and activated PFi. Settings now gone. Checked the modded files and they were back to original.

That one phone # may be my old Google Voice #....didn't use it much so don't remember. Somehow the numbers are routed together.

Under the hood you say??? Sounds more like PFM to me!

and the tycho app seems to do the magic.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
News from Google

Here's a post from the Project Fi forum related to this topic:
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
If the issue is just changing the default setting from Home to Automatic I can't believe it is really that difficult for them to fix.

Perhaps there are other issues though.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Yes, the problem does appear deeper than just changing a setting.

My attempts to force roaming seem to indicate a much more complicated problem that affects the phone's routing of calls when in automatic mode CDMA.

Hopefully all this can be resolved soon by Google. I really like the phone and wifi calling keeps me connected at home where the GSM and CDMA signals are weak. There is a very strong CDMA signal here but it requires roaming to work in order to use it.

Overall, this issue is not a deal breaker for me with Project Fi, but a fix of the problem would make a great idea for a phone and phone service live up to its potential.

Posts on the PFi forum indicate that the problem is just with the 5X, not PFi's system, since its reported that the N6 and N6P both function well on CDMA and roaming.

So, maybe the Big G will come through and get this straightened out.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
Wouldn't that problem be present for the Nexus 6 as well?

The routing of phone calls is not the responsibility of the Phone nor the Project Fi app. They should be done by the towers and switching equipment. The most the Phone or Project Fi should be doing is registering enough information for that to happen.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Most likely.

What about this?

CDMA

Nexus 5X	xxx

Nexus 6P	800, 1900 MHz

Nexus 6 xxx

-
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Or this:
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I guarantee 5x does 800MHz or it wouldn't work for Verizon users outside of Project Fi (and you would see a ton of complaints from Verizon users)

I know there is a long-standing roaming issue with Sprint Samsung phones where they won't roam on Verizon/800MHz even if you force roaming, but that isn't a matter of phone call routing, the radio on the phone just won't connect to 800MHz if they are on 1900MHz.

Sprint phone call service is still mostly on 1900MHz but they probably have added some frequencies after winding down Nextel service. Their main voice frequency is still 1900MHz, at least until they move to VoLTE.

I didn't read about your experiences incredibly closely but it seemed you were seeing delays in call routing to your phone rather than issues with connecting to roaming partners (after you enabled the setting to let users choose auto vs home) so it wouldn't be the same type of issue the Sprint Samsung phones were seeing as that was a problem with the phone radio/hardware.

BTW even as a Sprint customer (I have another phone) there is virtually no roaming on Verizon anymore. That got cut off a while back. Most of the roaming is with small partners. I'd have to check the PRL descriptions also to see which PRL Fi customers are getting that affects who you'll roam with (after you manage to get the roaming set to Auto vs Home) I think the Fi PRL is 5xxxxx range which is different than the corporate PRLs that have more extensive roaming enabled.

So I think there are multiple issues we are discussing:

1) why are the settings for CDMA roaming hidden

2) why are the settings for CDMA roaming set to Home vs Auto

3) even if you get the CDMA roaming set to Auto, is there a further issue with roaming itself

4) are the roaming issues with recognizing the roaming partner or is recognition ok, but calls themselves are not routing properly

5) what PRL are Project Fi users getting and what roaming does that allow
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
That's welcome news. I was wondering how non-PFi users were doing. At least the hardware is capable.

There were weird issues like the delay in calling, wrong number showing on receiving phone call i.d., and Wifi calling not working.

The original PRL on my phone was 55052 but I updated it to 55054. Didn't see much difference though.

In my location the roaming takes place on a very small regional carrier, but I think Verizon uses these towers as well. The small carrier covers 2 counties in a mountainous area and has done a good job of getting signal into difficult places due to the geography. That is the main reason for my interest in getting CDMA roaming working. But...at least the Wifi calling works at home to cover the weak Sprint/TMobile signal and the phone does roam on AT&T on the GSM side.

If the hardware is good as proven by non-PFi phones, and the routing of calls is good for those phones, then it comes down to the way PFi works. That leaves the PFi app and/or the involvement of Google Voice in the mixture of PFi as the likely problem areas.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Update

Here's an update from Google:

So it sounds like this may be resolved ....................soon maybe.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
That's good news. Sounds like the latest you'll get the fix is next month's security release.

I do wish they'd give an option to expose the cellular roaming settings instead of hiding them. I understand to hide by default but it is useful to have access in non-standard situations.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Here's an update on my roaming situation:

It looks like Google/Project Fi is working on the issue and may have the solution.

I have been in contact with PFi support via email and volunteered to test whatever they came up with. Not sure why, but my phone's CDMA is now working right. This is likely due to some changes on the backend by support since I still have the original PFi app installed and have no mods on the phone that I know of.

The phone can connect to Sprint and also roam on CDMA. It automatically switches to the roaming carrier and back to Sprint when there is a signal.

The cellular settings home/auto are available even with PFi app running and activated.

The GSM side is having some problems in my area. The cellular settings are not available in that mode and there is no phone # listed in the phone info tool in GSM mode. When it has worked the GSM roams on AT&T with no problems.

Not sure what's going on with GSM but there has definitely been some kind of progress made on CDMA.

It sounds like PFi is definitely making progress on the issue. Hopefully it will fully resolved soon.
[Nexus 5X Q&A, Help & Troubleshooting] tobewan:
Google just pushed out version J-2.5.12-all on 6/20, FWIW. [MENTION=4790704]rezz93[/MENTION], are you doing any testing with the new version? Interesting that without a new Fi app, they were able to expose the CDMA settings from the server side. Resolution of this may include android update, Fi update and server side changes.

Thanks

Toby
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Yeah, it seems to be a combination of things.

I'm back to square one now after doing a rom update. But at least it worked for a while to prove its possible.

The change that removes the home/auto settings takes place at the beginning of activation so..........

How to preserve the activation status when PFi app is uninstalled?? Have you seen any code related to that?
[Nexus 5X Q&A, Help & Troubleshooting] tobewan:
No haven't seen anything like that but haven't looked either. Since the Fi code does not mess up the 6/6P, I think that there is some android code that has a side effect on the 5X that switches the phone to Home. Adding US Cellular means they need to test roaming on Sprint + roaming on USC before they release an update.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
USC

U.S. Cellular started working for me 2 days ago. Right now it looks like 2g/voice only but that's okay for now. It seems to roam without in mods to the system.

So....the problem with Sprint roaming may be in the Sprint side of things.

Still waiting for the LTE update to the sim card. Hopefully that will come along soon.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
So you are saying it is "Roaming" on USC rather than native from recent update?
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
There is no native USC in this area so when the phone is on USC it roams on Sprint and also on a small regional carrier here.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I'm confused. Earlier you said USC started working, but now you have clarified there is no native USC in the area.

So are you saying if you force USC then it roams properly on Sprint and the small regional carrier, but if you force Sprint it doesn't roam on the regional carrier (but it is supposed to because Sprint has a roaming arrangement with them)?
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
There are now 3 carrier options on the phone, Sprint, T-Mobile, and USC.

There is no signal from USC at my location so if the phone is set to use USC it roams on Sprint>>>>since there is no USC signal.

It also roams on the small regional carrier here>>>>since there is no USC signal>>>when the phone is set to use USC.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Good News

Here's some good news about the roaming issue:

Jordan E. via Project Fi Help Forum <project-fi+APn2wQfAgQ6GpX9xbua74-JRZpwtWce98JZc3YE7FHYaS6iOKcZSB@googleproductforums.com>
2:03 PM (3 minutes ago)

to Project
Hi everyone,

We announced today that Android Nougat (7.0) will start rolling out and will continue over the next few weeks. The issue described in this thread - Nexus 5X device won’t roam domestically on the Sprint network as the setting switches to ‘home’ instead of ‘automatic’ - will be fixed with the Android N update.

Note that Android N has not yet started rolling out to Nexus 6, Nexus 6P or Nexus 5X devices but it should be made available soon. Please hang tight and I’ll let you know when you should expect it to your Nexus 5X device.

Thanks for your continued patience!
Jordan

More Here: https://productforums.google.com/forum/#!topic/project-fi/dceV0obfCUI
[Nexus 5X Q&A, Help & Troubleshooting] tobewan:
Thanks! I had heard from Jordan that it would likely be in Nougat so that's what I was expecting. She also said that the Fi app does not need to be updated, it will work properly (roam on Sprint) once the phone is on Nougat.

Toby
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
For future reference, I believe these were the changes they added to Android N to fix the problem.

https://android.googlesource.com/platform/frameworks/base/+/247e7f4^!/

https://android.googlesource.com/platform/frameworks/opt/telephony/+/9d3f7e2^!/

Apparently they were not setting the roaming based on the carrier config before.

Since Project Fi hides the roaming settings you can't change it manually easily, as you found, which is why they needed to fix the code to set it automatically. This code seems generic for 5x and 6p so I don't know if 6p ever worked on CDMA roaming with Sprint. Nexus 6 was reported to be working, but it is on different code base.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Thanks for the links.

Since U.S. Cellular was added my roaming issue has been pretty much resolved. USC roams on Sprint, Verizon, and a regional carrier here.

There is a very weak Sprint signal here and no USC, Tmobile is weak/none in most areas and roams on ATT which has fair coverage.

On a recent trip to Florida the phone performed very well, with very little time with no signal. Between Sprint, Tmobile, USC, and the roaming partners coverage was very good.

So overall, not bad for me.

Still waiting on the N update from Pure Nexus. Hopefully that will fix the issue with Sprint.

Now, if there was just a way to force roaming when needed.

Sometimes the phone wants to hang onto a weak Sprint/Tmobile signal when there is a strong roaming partner signal available. Also, there's a tendency to switch back to a weak Sprint/Tmobile signal when a strong roaming signal is available.

Still, even with the glitches, I really like the phone. :D
[Nexus 5X Q&A, Help & Troubleshooting] tobewan:
That's the behavior I see that is most annoying. I will actually lose coverage and then it tries to switch to another weak signal when there is good roaming coverage from ATT or VZ.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I cannot say for sure, but from the source, I'm guessing the mode they added/recognized

CDMA_ROAMING_MODE_AFFILIATED

would accomplish this. You would need to look into the carrier config stuff to see if it can easily be changed.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
The Android N update seems to have corrected the problem with Sprint not roaming on the 5X.

So far N works well with no problems and smooth running. Battery life seems better also with mine running Pure Nexus with the Franco kernel.
[Nexus 5X Q&A, Help & Troubleshooting] Austexcat:
I've had the 5x for almost a year and purchased it through the Fi network. I live outside of Austin where tower strength is weak. Therefore I rely on the wifi calling. But I was having all sorts of problems with the phone switching to wifi when I was home didn't have a tower signal. And like many others often times while on a tower at home the people I was speaking to couldn't hear me. When I got to investigating I found this is a real problem. I contacted the Fi people and they got a case file going and tried to help me to no avail. I had to send them bug reports and all sorts of stuff, but everything they tried to do didn't help. And then it got real interesting. I got on the Nougat beta program and when I told them that they said they couldn't help me any more because it is an "app driven service" and they didn't know whether it would work with Nougat. At that point they kind of disowned me. I never heard back from them. I have since downloaded an Fi update, but I don't know whether that was supposed to help with Nougat or not. I also downloaded an app called Fi Info. It tells me on all of my calls what tower I was transmitting through or if it was wifi. Even when i'm close in to Austin I never go through a Sprint tower. It's always T Mobile. Occasionally it will hit a Sprint tower. And the app tells the date and time of the call. My experience with Fi has been ok, but i'm not changing. My average phone bill is $26.00 per month. I can't beat that.
[Nexus 5X Q&A, Help & Troubleshooting] rezz93:
Do you have U.S. Cellular also??? You should. It will roam on Sprint, Verizon, and other regional CDMA carriers.

Do you have the app FiSwitch? It is very handy for switching between Sprint, TMobile, and USC. Its a paid app but well worth the 99 cents or whatever it costs.

If you don't have it, give it a try.

I also use signal check pro. It is better than Fi Info in some ways, but both are handy. Here's a screenshot of my phone. Thats FiSwitch in the center and FiInfo in upper left:

Give those apps and they may help you out some.

Yes, overall I am very happy with PFi and intend to keep using it as long as the price is right. I don't really need unlimited but its nice to have at a decent price.
[Nexus 5X Q&A, Help & Troubleshooting] Austexcat:
US Cellular

I don't know whether US Cellular is around the Austin area. I'll have to look up their tower locations. I'll give FiSwitch a call. I'll also look into signal check pro. Thanks for the heads up on these. The Fi experience has been ok, but there have been problems. I wish they would fix the switching problems though. The concept is great when it works.
[LG G5 Questions & Answers] ItBankRock:
Do the modules work for all variants or are they also region dependent? I have the Hong Kong variant (H860N) but I live in the Philippines, they sell the H860 here.
[LG G5 Questions & Answers] liquidzoo:
If you're referring to the "Friends" modules (the 360 Cam, Camera Plus, and B&O HiFi), if they're sold in the location where your variant is from (in your case, if they're sold for the G5 in Hong Kong) then it should work.

I know that those of us in the US are SOL when it comes to the HiFi Plus until LG and the FCC decide we can use it (everything I've read says the phone won't even turn on)..
[LG G5 Questions & Answers] ItBankRock:
Oh thank you. Looks like I'm worried with that too :/ Hopefully future 3rd party modules will be compatible with all the model numbers of G5.
[HTC One A9] quist80:
Hi,

My friend bought a brand new HTCOne A9 phone, he entered a gmail account which he uses on another htc phone after he synchronized the new phone he decided that he should use a different gmail account so he reset the phone and create a new gmail account and entered it but didnt the phone did not accept the new gmail account and instead it asks for the first email that he used and synchronized with in the begining. I have tried several email accounts and it didnt work the phone is stuck now as its shown in the picture and cant go further than that .......anyone knows what should i do????

my friend doesnt mind (unlocking rooting ...etc) his phone as long he gets it working

ps:- cant use adb or fastboot command cause the the USB Debugging is disabled

thanks in advance
[HTC One A9] Cashreedhar:
That is the security feature. What if you are not the owner and you are trying to put your hands over others phone. May be you can try clicking help me finding my account option on the screen.