[Moto G4 Play Questions & Answers] nick_white:
I reread your posts. You only ambiguously mention that it "can read the syntax". What syntax? And how is it interpreting it differently than prop files? I downloaded & installed CM File Manager, and gps.conf shows as any other text file. I attached a screenshot. Can you attach a screenshot of how your editor shows the file?

I'm not aware of any "conf" file format. The syntax looks exactly the same as build.prop or any other "properties" file, for which there is a "specification" (for example, https://en.wikipedia.org/wiki/.properties).

I also pointed to the Android source code that reads the gps.conf file, and it reads it as a "properties" file: https://android.googlesource.com/pl.../server/location/GpsLocationProvider.java#611

So how does it not apply?

Not EVERY line is commented. For example, mine has 3 non-commented lines.

Not EVERY conf file. Here are some examples of files that have plenty of non-comment lines: xtwifi.conf, sap.conf.

The commented lines in these files (including gps.conf) are either explanations, or disabled things by the developer, just like commented out code. I see this nearly every day as a dev: some are only temporarily commented, some are leftovers, some are there because the lines were copy - pasted by the dev and he didn't know / care about them...

By the same line of reasoning, check these lines from the stock file:

# supl version 1.0
#5UPL_VER=0x20000

- Why does it say 1 in the comment, while the value is actually 2?

- Why is it incorrectly put as "5UPL" instead of "SUPL"?

Devs are not perfect...

I tested by deleting all the commented lines in the file and rebooted.

I also cleared and (successfuly) redownloaded the AGPS date through GPS Status.

It works, just as before, same accuracy.

The gps.conf file might only override some configurations that are hardcoded in the driver, kernel, firmware, source code etc.

I understand, but it's not the effort in question, but the validity of the method...

It's just not consistent with:

- The fact that those lines are commented according to the "properties" file spec and according to the source code

- The fact that I can even delete those (commented) lines and it works the same

I think you can agree with me that there are plenty of "fixes" for GPS, touch response, "CPU cooler", "RAM booster", "Battery defrag" apps with plenty of personal testimonies saying that they work and they can definitely see a difference. I just apply a healthy dose of skepticism...

You might see better results with changing commented lines, but there are so many variables involved that it can me mistakenly interpreted:

- It should be the same route.

- It depends on the weather.

- It depends on the sattelites that are in your vicinity (not always the same).

- It depends on interferences with different things.

- It can also depend on mechanical / heat / other stuff. For example, in previous posts, one claimed to improve the accuracy by touching the antenna, one by putting the SIM in the 2nd slot etc.

- It could also depend on software stuff like background apps, Google etc.

I can take the same route using the same app and still have different 3D fix time, different accuracy, different deviations - all without changing any config line...