[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FVSantbrink:
I have an AT&T Samsung Galaxy S3 with two problems at hand.

First of all, my GPS does not lock onto any sattelites at all. I've come to realize that this is related to an incorrect configuration file. As far as I know, a # at the beginning of a statement means that that statement is a remark, and not actual code. Thus, it's ignored.

If you look at my gps.conf file below, you will notice that many of the lines contain a # at the beginning. I have a general idea of which should remain. However, I'd like to know all those of which should/can be removed. If someone could just rewrite it removing all the # which should not be included, that would be awesome!

#Test
NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
# NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin

# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 4

# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0

# supl version 1.0
SUPL_VER=0x10000

# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0

# GPS Capabilities bit mask
# SCHEDULING = 1
# MSB = 2
# MSA = 4
# ULP = 0x20
# ON_DEMAND_TIME = 0x10 // yunu.lee
# default = MSA | MSB | SCHEDULING | ULP
CAPABILITIES=0x16

# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000

################################
##### AGPS server settings #####
################################

# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.google.com
# SUPL_PORT=7276

# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234

################################
# Sensor Settings
################################

# Needs to be set explicitly based on sensor
# There is no default value.
GYRO_BIAS_RANDOM_WALK=0.00001

SENSOR_ACCEL_BATCHES_PER_SEC=3
SENSOR_ACCEL_SAMPLES_PER_BATCH=5
SENSOR_GYRO_BATCHES_PER_SEC=3
SENSOR_GYRO_SAMPLES_PER_BATCH=5

# Sensor Control Mode (0=AUTO, 1=FORCE_ON)
SENSOR_CONTROL_MODE=0

# Enable or Disable Sensors for GPS use (0=Enable, 1=Disable)
SENSOR_USAGE=0

# Choose GSIFF sensor provider (1=DSPS, 2=Android NDK)
SENSOR_PROVIDER=2

################################
# Indoor Positioning Settings
################################
# 0: QUIPC disabled, 1: QUIPC enabled, 2: forced QUIPC only
QUIPC_ENABLED = 0

################################
# EXTRA SETTINGS
################################

My second problem has to do with the power_profile.xml file. It was noted that certain S3s had a problem with an incorrect value in the power_profile.xml file, which resulted in Cell Standby topping the list for battery drainage. I have taken a look at that file on my S3, and noticed that I am affected by that incorrect value (34 instead of 3.4).

The problem is that the fixed XML file available for download seems slightly different to the one currently in my S3, in more ways than just that value. I'd like to know whether it's safe to make the switch. Or, does anyone have a fixed power_profile.xml which they wish to share with me, that definitely works on the AT&T S3?

I'm sorry if this has been posted before, but I wasn't able to find anything completely answering my questions. Thanks in advance for the help, and it's much appreciated! :)