Related
Could the devs create a something so we can specifiy our location for the gps.conf
1. in the startup.txt
2. or a script at startup where we only need to fill in X => X.pool.*
3. or I could make a map with ALL countries, for example
- Belgium
---gps.conf
- Germany
---gps.conf
- Estland
---gps.conf
and so on. and then at startup maybe someone can make a file selector, android asks you which file it should use for gps.
is any of these options possible? I guess this would be a great help for much people.
sometimes builds crash, all my apps fail when I startup after editing the gps.conf
other times my gps just gets useless, this is all because the root access is not always as easy to get, and when you have it, there can still be consequenses like appcrash of the system each time on startup.
Thanks For the post I'm having GPS issues also - Flashed 4 NAND Roms Changed GPS.Conf and still not getting Sat Fix on GPS
HectiQ said:
Could the devs create a something so we can specifiy our location for the gps.conf
1. in the startup.txt
2. or a script at startup where we only need to fill in X => X.pool.*
3. or I could make a map with ALL countries, for example
- Belgium
---gps.conf
- Germany
---gps.conf
- Estland
---gps.conf
and so on. and then at startup maybe someone can make a file selector, android asks you which file it should use for gps.
is any of these options possible? I guess this would be a great help for much people.
sometimes builds crash, all my apps fail when I startup after editing the gps.conf
other times my gps just gets useless, this is all because the root access is not always as easy to get, and when you have it, there can still be consequenses like appcrash of the system each time on startup.
Click to expand...
Click to collapse
An easy way I found from another thread is to use FasterFix, an app that lets you select the correct X.pool script line based on your location. No need to go and find the correct folder and edit the script. FasterFix even has a custom feature so that you can create your own script to get more specific a fix to the satellites in the region you are in. No more hunting to edit the script line! Also, for the other poster in the United States, I found that if you add the number and period 0. in front of us.pool.ntp.org script line, so it would look like: 0.us.pool.ntp.org, your phone will lock onto the satellites within 20 seconds (at least for me) from a cold start. Use the custom feature in FasterFix to do this. Doing this and using GPS Status first to obtain the AGPS information, the next GPS lock will be within a second or two. Here is a link to FasterFix, hope this helps.
FasterFix: http://forum.samdroid.net/f10/fasterfix-1747/
with the cm7, my gps are very slow, +/- 5 -> 10 minutes for fixing, event with ten satellites 'green' on gps status.
With the "Ogo rom" ( thx man ) this operation is realized in ....5 secs !
with the help of "google" and this adress : http://android.modaco.com/topic/331446-mod-all-roms-gps-fix/
i have made a gps.conf for my usage in Belgium : here is :
NTP_SERVER=0.be.pool.ntp.org
NTP_SERVER=1.be.pool.ntp.org
NTP_SERVER=2.be.pool.ntp.org
NTP_SERVER=3.be.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=1
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=5000
# Report supl ref location as position, 1=enable, 0=disable
REPORT_POSITION_USE_SUPL_REFLOC=1
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_NO_SECURE_PORT=7276
SUPL_SECURE_PORT=7276
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
#################################
##### AGPS Carrier settings #####
#################################
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE
the result is a fix in 10 secs ! the important parameters in this case is ACCURACY_THRES=5000 and INTERMEDIATE_POS=1, it decrease the necessary time to fix completly.
These parameters reduce the precision to make a faster fix but the precision grows after this.
It's not a scientific approach, but it works on this config :
Legend [email protected]
CM7 nightly 125
Radio rom : 47.51.35.17U_7.13.35.05
If that help anyone, is cool , sorry for my (very) bad English !
Alain
Used it and work´s very good!
I have Root Explorer , navigate to \system\etc , mount r/w and open in text editor, and i am able i edit the gps.conf file, saved the file and everytime it crashes the os and reboots me... when i check again , it didnt save my changes...
Using GPS Faster Fix utility also gives me the same problem.. it let me chose the server but when i save, it reboots...
I am running Blayo ROm with the A2SD with data ext... not sure if this is related.
Any ideas
Thanks
well, try with adb to push this file on the system !
I open the file zip on my computer. Then edit the gps.conf by inserting my local servers. Then save changes and put zip file on sdcard and in cwm recovery choose zip from sdcard and just flash.
Went ok. Just try.
Cheers
Sent from my Legend using XDA App
I couldnt edit while the phone was on... and i tried using the flashing method to install it.
I couldnt find any difference with the new gps.conf though...
My test was to open GPS Status and Reset the aGPS Data, then reboot the phone to make sure im testing the GPS without any aGPS or wifi.
Once rebooted, first thing i open the GPS Status, it took forever to get a fix... at least 15 mins... i had a blue sky ...
Is this how you guys test to see if it is quick?
But once fixed, it is quick for subsequent tries... as long i do not reset the aGps data.
It's perfect, finally working as it should. Getting a fix in 3 seconds
The easiest way is just install the .zip by cwm recovery, instead of editing gps.config manually.
sirpasztet said:
It's perfect, finally working as it should. Getting a fix in 3 seconds
The easiest way is just install the .zip by cwm recovery, instead of editing gps.config manually.
Click to expand...
Click to collapse
can you tell mw when you said getting a fix in 3 seconds... how you timed/test it?
1. Did you use GPS Status apk from the market?
2. Did you delete all AGPS Data (Menu>AGPS>Reset AGPS data)
3. Reboot phone and try GPS Status and get your fix in 3 secs?
I downloaded the .zip and modified it to accommodate my location: ca.pool.ntp.org. I then flashed it (also cleared my dalvik cache, this may help) and booted into CM7.1, like usual.
Then I went into my GPS test app, GPS Test and it got a lock instantly. What baffled me however was that it locked me to 0m accuracy and no satellites were in view. I was indoors. I then went into Google Maps and once again it locked me instantly, but to Winnipeg, Manitoba, a city 1500km away from Edmonton, my city.
Then I rebooted once more and went back into GPS Test. The GPS lock icon was flashing for a few seconds, trying to acquire a fix, but then stopped altogether.
This is strange, and doesn't work for me apparently.
EDIT: Figured out the solution to my latter problem, the permissions were all effed up. I'm still instantly locked to Winnipeg though.
EDIT2: Nope, both problems still persist. Permissions did nothing.
EDIT3: Oh God, I left my GPS to fix all by itself and when I came back, the accuracy is getting less accurate! It was 1700m when I started typing, now it's at 2700m! WTF IS GOING ON?
EDIT4: It lost its fix after 4996m accuracy, it's finding some satellites now and will probably do the same damn thing again! "Fix-loop" is what I'm starting to call it. For now, I'm gonna download my Stock ROM (unrooted) and find the gps.conf file in there, then flash it.
QkSi1ver said:
can you tell mw when you said getting a fix in 3 seconds... how you timed/test it?
1. Did you use GPS Status apk from the market?
2. Did you delete all AGPS Data (Menu>AGPS>Reset AGPS data)
3. Reboot phone and try GPS Status and get your fix in 3 secs?
Click to expand...
Click to collapse
First I cleared and downloaded new agps data, using GPS Test app. Then I launched Google Maps and my accurate location has been set in few seconds.
Asovse1 said:
I downloaded the .zip and modified it to accommodate my location: ca.pool.ntp.org. I then flashed it (also cleared my dalvik cache, this may help) and booted into CM7.1, like usual.
Then I went into my GPS test app, GPS Test and it got a lock instantly. What baffled me however was that it locked me to 0m accuracy and no satellites were in view. I was indoors. I then went into Google Maps and once again it locked me instantly, but to Winnipeg, Manitoba, a city 1500km away from Edmonton, my city.
Then I rebooted once more and went back into GPS Test. The GPS lock icon was flashing for a few seconds, trying to acquire a fix, but then stopped altogether.
This is strange, and doesn't work for me apparently.
EDIT: Figured out the solution to my latter problem, the permissions were all effed up. I'm still instantly locked to Winnipeg though.
EDIT2: Nope, both problems still persist. Permissions did nothing.
EDIT3: Oh God, I left my GPS to fix all by itself and when I came back, the accuracy is getting less accurate! It was 1700m when I started typing, now it's at 2700m! WTF IS GOING ON?
EDIT4: It lost its fix after 4996m accuracy, it's finding some satellites now and will probably do the same damn thing again! "Fix-loop" is what I'm starting to call it. For now, I'm gonna download my Stock ROM (unrooted) and find the gps.conf file in there, then flash it.
Click to expand...
Click to collapse
once you get the gps.conf of the stock rom, post it here.. i want to compare with the modded one... is it a bell/virgin legend?
than ks
QkSi1ver said:
once you get the gps.conf of the stock rom, post it here.. i want to compare with the modded one... is it a bell/virgin legend?
than ks
Click to expand...
Click to collapse
It's a Bell Legend. And this is from the Eclair ROM (so I couldn't get Froyo's, doubt there would be updates/changes to gps.conf):
Code:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.wireless.bell.ca
SUPL_PORT=7275
SUPL_TLS_HOST=supl.wireless.bell.ca
SUPL_TLS_CERT=/etc/SuplRootCert
Haven't tried it yet, I haven't been able to find the time. How did modifying it work for you if you've tried it already?
By the way, Bell and Virgin probably used the same Eclair ROMs, a Virgin CSR told me that they both had the same Froyo, so I'm thinking that 2.1 would also be identical.
mmm i may change mine to add those instead... because when i reset the gps cache it takes forever to get a fix... like 15 - 30 mins...
Asovse1 said:
It's a Bell Legend. And this is from the Eclair ROM (so I couldn't get Froyo's, doubt there would be updates/changes to gps.conf):
Code:
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.wireless.bell.ca
SUPL_PORT=7275
SUPL_TLS_HOST=supl.wireless.bell.ca
SUPL_TLS_CERT=/etc/SuplRootCert
Haven't tried it yet, I haven't been able to find the time. How did modifying it work for you if you've tried it already?
By the way, Bell and Virgin probably used the same Eclair ROMs, a Virgin CSR told me that they both had the same Froyo, so I'm thinking that 2.1 would also be identical.
Click to expand...
Click to collapse
I have instaled the last cm7 nightly and the gps.cnf back to original state. i have now the new cwm i i get a error. cant flash. now i dont know if is the cwm mod who does not support or if is the nightly. anyone knows something?
Hmm, let me get this straight. You get a big red sign over the whole screen saying just:
ERROR
Hmm, weird
BlaY0 said:
Hmm, let me get this straight. You get a big red sign over the whole screen saying just:
ERROR
Hmm, weird
Click to expand...
Click to collapse
LOLOL... i will write in here what was saying!
Edit: here we go!
"Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the Clockworkmod 3.0 Gingerbread based recovery. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages."
So i believe that when update cmw from 2.x.x to 3.x.x is no longer possible to flash that gpsfix.zip. If that so, anyone with older version to do fake flash to try again this fix.
You can use both fake-flash versions whenever you like. Just copy the old one (2.5.x) to SD card naming it update-old.zip instead of update.zip. Boot to recovery, load 3.x fake flash update.zip (standard procedure). After that load update-old.zip from 3.x recovery and you'll end up with 2.5.x. Load update.zip from 2.5.x again and you'll be back on 3.x.
BlaY0 said:
You can use both fake-flash versions whenever you like. Just copy the old one (2.5.x) to SD card naming it update-old.zip instead of update.zip. Boot to recovery, load 3.x fake flash update.zip (standard procedure). After that load update-old.zip from 3.x recovery and you'll end up with 2.5.x. Load update.zip from 2.5.x again and you'll be back on 3.x.
Click to expand...
Click to collapse
But i have deleted the old cwm. i need the zip file to do that. can you get that for me? i can´t find it!
thanks in advance!
Edit: i think i´ve found in this threath: http://forum.xda-developers.com/showthread.php?t=1057072
Edit2: try to fake flash the that and receive a message saying that original recovery was changed by this one. Of course, does not.
I need cwm 2.5.x zip file to work.
Anyone?
ICavalera said:
But i have deleted the old cwm. i need the zip file to do that. can you get that for me? i can´t find it!
thanks in advance!
Edit: i think i´ve found in this threath: http://forum.xda-developers.com/showthread.php?t=1057072
Click to expand...
Click to collapse
Old CWM? 2.5 something? That comes with the ROM Manager app in the Market, doesn't it? (nooby answer )
Are you saying to open rom manager, flash the recovery menu, and then install zip from sdcard?
Sent from my Legend using XDA App
Hi!
I Cannot find solution to connect to company's hidden Wifi 802.1x network
I tried almost anything to make it work .... but without success
I have had various wpa_supplicant bin files.
I have edited 100x wpa_supplicant.conf file.
I was reading forums with "SOLVED" solutions ... for other phones ... but cannot find solution to work on Huawei IDEOS X5 U8800.
I also have tried it with various ROMs: MIUI 1.8.x and 1.9.x, VOID, B135, B136,B160, cm7-100911, Oxygen ...
But every time with no success ...
Hints:
a) All other colleagues connect without problem (they have HTCs, Samsung Galaxy S I,II, iPhones 3,4 ...) while my friend and i cannot connect
b) I connect to my home Wifi (WPA/PSK) without a problem!
Anyone have similar problem?
BTW: MY wpa_supplicant.conf file looks like:
ctrl_interface=wlan0
update_config=1
network={
ssid="mySSID"
scan_ssid=1
key_mgmt=IEEE8021X
group=WEP104 WEP40
auth_alg=OPEN SHARED
eap=PEAP
identity="[email protected]"
password="zzzzzz"
phase2="auth=MSCHAPV2"
}
Brgds,
S.
HELPPPPP
Have had sporadic issues myself, and found that setting ap_scan=2 in /system/etc/wifi/wpa_supplicant.conf was helpful but not flawless. I reverted back to a CWM of MIUI 1.8.19 which I recalled seemed to connect without issues. On reviewing the wpa_supplicant.conf files in system and data, I noticed that the ctrl_interface was different.
ctrl_interface=DIR=/data/misc/wifi/wpa_supplicant GROUP=system
rather than ctrl_interface=wlan0
I haven't yet tried moving back to the latest version of MIUI to test these changes, but will do so when I get the time.
Modify below files and ensure permissions dont change
Both /data/misc/wifi/wpa_supplicant.conf
and /system/etc/wifi/wpa_supplicant.conf
also create a new folder wpa_supplicant in /data/misc/wifi/
mkdir /data/misc/wifi/wpa_supplicant -m 750
haydnlj said:
Have had sporadic issues myself, and found that setting ap_scan=2 in /system/etc/wifi/wpa_supplicant.conf was helpful but not flawless. I reverted back to a CWM of MIUI 1.8.19 which I recalled seemed to connect without issues. On reviewing the wpa_supplicant.conf files in system and data, I noticed that the ctrl_interface was different.
ctrl_interface=DIR=/data/misc/wifi/wpa_supplicant GROUP=system
rather than ctrl_interface=wlan0
I haven't yet tried moving back to the latest version of MIUI to test these changes, but will do so when I get the time.
Modify below files and ensure permissions dont change
Both /data/misc/wifi/wpa_supplicant.conf
and /system/etc/wifi/wpa_supplicant.conf
also create a new folder wpa_supplicant in /data/misc/wifi/
mkdir /data/misc/wifi/wpa_supplicant -m 750
Click to expand...
Click to collapse
The control interface is changed so that it works with other versions of wpa_supplicant. If you change it to the way it was in the older Miui then wifi won't work at all.
If it never worked (even on stock) then the issue probably isn't with wpa supplicant, and could be a problem with the wifi driver, or the hardware itself. This really needs someone who knows what they're doing and access to a hidden 802.1x network to look into it.
stockwell said:
If it never worked (even on stock) then the issue probably isn't with wpa supplicant, and could be a problem with the wifi driver, or the hardware itself.
Click to expand...
Click to collapse
Was there a driver change between 1.8.19 and later MIUI versions? The supplicant seems like the same version (v 0.6.10)?
On returning to 1.8.19 have had 3 days without issues. When on 1.9.30 the change to ap_scan=2 definitely improved and seemed to make a connection on reboot flawless, but reconnection from sleep was sporadic (probably <30%). Watching wpa_cli output when waking phone from screen off on 1.9.30 showed a failed connection attempt, and then a series of timed scans (CTRL-EVENT-SCAN-RESULTS) - these continued after CTRL-EVENT-CONNECTED (something that didn't occur after toggling wifi on/off/on and connecting).
stockwell said:
This really needs someone who knows what they're doing and access to a hidden 802.1x network to look into it.
Click to expand...
Click to collapse
Agree
haydnlj said:
Was there a driver change between 1.8.19 and later MIUI versions? The supplicant seems like the same version (v 0.6.10)?
On returning to 1.8.19 have had 3 days without issues. When on 1.9.30 the change to ap_scan=2 definitely improved and seemed to make a connection on reboot flawless, but reconnection from sleep was sporadic (probably <30%). Watching wpa_cli output when waking phone from screen off on 1.9.30 showed a failed connection attempt, and then a series of timed scans (CTRL-EVENT-SCAN-RESULTS) - these continued after CTRL-EVENT-CONNECTED (something that didn't occur after toggling wifi on/off/on and connecting).
Agree
Click to expand...
Click to collapse
Thanks for you feedback, that really helps. Even though the version number is the same they aren't the same file.
I'll get in contact with you via pm to try and sort this out.
Thanks guys for trying!
So there is no solution yet?
Any news ?
Thanks!
Any news ?
I have same problem with that.
I also have the same problem, and looking for a solution. I am using Redmi 4a MIUI 8.2.6.0
Hi guys.
I've flashed PURE Android image on Nexus 4.
The image is that I've built from AOSP. (branch: android-4.2.2_r1.2)
And I've flashed CWM recovery and install GAPPS. (gapps-jb-20130301-signed.zip from goo.im/gapps)
Everything is OK.
But I have some problems about the Network Location.
Google Now always says "Location Service is off."
And 3rd-party maps cannot find my location.
I checked the following.
Settings > Location access
- Access to my location is ON
- GPS satellites is CHECKED
- Wi-Fi & mobile network location is CHECKED
Settings > Accounts (Google)
- Maps & Latitude > All items are CHECKED
- Location > Let Google apps access your location is ON
I attach Log.
W/LocationProviderProxy(526): com.google.android.location resolves service com.android.location.service.v2.NetworkLocationProvider, but has wrong signature, ignoring
W/LocationManagerService(526): no network location provider found
W/GeocoderProxy(526): com.google.android.location resolves service com.android.location.service.GeocodeProvider, but has wrong signature, ignoring
How can I fix it ?
Thank you
Hi,
Apply the following patch in frameworks/base:
diff --git a/core/res/res/values/config.xml b/core/res/res/values/config.xml
index cb7804c..9b91387 100755
--- a/core/res/res/values/config.xml
+++ b/core/res/res/values/config.xml
@@ -645,7 +645,8 @@
-->
<string-array name="config_locationProviderPackageNames" translatable="false">
<!-- The standard AOSP fused location provider -->
- <item>com.android.location.fused</item>
+ <item>com.android.location.fused</item>
+ <item>com.google.android.location</item>
</string-array>
<!-- Boolean indicating if current platform supports bluetooth SCO for off call
This will allow the framework to use NetworkLocation.apk from gapps as well as the AOSP FusedLocation.apk.
medialaxis said:
Hi guys.
I've flashed PURE Android image on Nexus 4.
The image is that I've built from AOSP. (branch: android-4.2.2_r1.2)
And I've flashed CWM recovery and install GAPPS. (gapps-jb-20130301-signed.zip from goo.im/gapps)
Everything is OK.
But I have some problems about the Network Location.
Google Now always says "Location Service is off."
And 3rd-party maps cannot find my location.
I checked the following.
Settings > Location access
- Access to my location is ON
- GPS satellites is CHECKED
- Wi-Fi & mobile network location is CHECKED
Settings > Accounts (Google)
- Maps & Latitude > All items are CHECKED
- Location > Let Google apps access your location is ON
I attach Log.
W/LocationProviderProxy(526): com.google.android.location resolves service com.android.location.service.v2.NetworkLocationProvider, but has wrong signature, ignoring
W/LocationManagerService(526): no network location provider found
W/GeocoderProxy(526): com.google.android.location resolves service com.android.location.service.GeocodeProvider, but has wrong signature, ignoring
How can I fix it ?
Thank you
Click to expand...
Click to collapse
Sorry for the late reply.
It's perfect on android 4.3
Thank you!!!
Sent from my AOSP on Mako using Tapatalk 2
medialaxis said:
Sorry for the late reply.
It's perfect on android 4.3
Thank you!!!
Sent from my AOSP on Mako using Tapatalk 2
Click to expand...
Click to collapse
Can you describe the procedure to patch frameworks/base? Also will it work on a nexus s with the same problem?
antipasti said:
Can you describe the procedure to patch frameworks/base? Also will it work on a nexus s with the same problem?
Click to expand...
Click to collapse
1.
you can just modify config.xml using your editor directly.
and rebuild, flash, check whether it is working
2.
i don't have nexus s.
but i believe it will work.
good luck
medialaxis said:
1.
you can just modify config.xml using your editor directly.
and rebuild, flash, check whether it is working
2.
i don't have nexus s.
but i believe it will work.
good luck
Click to expand...
Click to collapse
Hi, I can't seem to find that config.xml file. Where is it? After editing it, should I flash the ROM and gapps again?
Thanks, i'm new to that stuff
filipeglfw said:
Hi, I can't seem to find that config.xml file. Where is it? After editing it, should I flash the ROM and gapps again?
Thanks, i'm new to that stuff
Click to expand...
Click to collapse
1. you can find here. $AOSP_PROJECT/frameworks/base/core/res/res/values/config.xml
2. i think you don't need to do. just update system image. but i don't know exactly... sorry
Hello,
First of all, I need to say I searched for weeks to solve this issue. I found no other way than posting a question. I hope someone could help me solve it. I checked the logs using "aLogcat" but nothing is relevant to the GPS. Any kind of help is welcome, I am not asking for a full step-by-step guide
* Issue: GPS cannot find my location, even when kept for long periods under clear sky (20 minutes). I tried "Faster GPS" and "GPS Status" apps to debug the thing, but useless. I simply can't get a fix.
* Infos:
Device: SGH-I337M
OS: Android 4.4.2 (Samsung Stock ROM)
Baseband: I337MVLUFNE1
Kernel: 3.4.0-1529758
Build: KOT49H.I337MVLUFNE1
Location: France
* /etc/gps.conf
##################################################
ENABLE_WIPER=1
LPP_PROFILE=0
DEFAULT_AGPS_ENABLE=TRUE
A_GLONASS_POS_PROTOCOL_SELECT=0
SUPL_VER=0x10000
CAPABILITIES=0x37
NTP_SERVER=fr.pool.ntp.org
INTERMEDIATE_POS=1
XTRA_SERVER_1=(a link to xtra1 (dot) gpsonextra (dot) net (slash) xtra2.bin
XTRA_SERVER_2=(a link to xtra2 (dot) gpsonextra (dot) net (slash) xtra2.bin
XTRA_SERVER_3=(a link to xtra3 (dot) gpsonextra (dot) net (slash) xtra2.bin
ERR_ESTIMATE=0
DEBUG_LEVEL=4
CURRENT_CARRIER=common
NMEA_PROVIDER=0
##################################################
Thank you
Ever since I upgraded to KitKat months ago I've had the same problem. Location is found, but satellite will never fix which means no turn by turn navigation.
I've downloaded every GPS app that exists, calibrated the compass countless times...and still nothing. In that time, I've installed and run at least 10 different ROMs and odined to stock as well.
I'm thinking it's a hardware problem and might exchange my phone for a replacement S4. Searched for GPS/KitKat/S4 problem, but never found anything significant.
kevinco1 said:
Ever since I upgraded to KitKat months ago I've had the same problem. Location is found, but satellite will never fix which means no turn by turn navigation.
I've downloaded every GPS app that exists, calibrated the compass countless times...and still nothing. In that time, I've installed and run at least 10 different ROMs and odined to stock as well.
I'm thinking it's a hardware problem and might exchange my phone for a replacement S4. Searched for GPS/KitKat/S4 problem, but never found anything significant.
Click to expand...
Click to collapse
Normally, the GPS should be able to fix satellites even without Data (In Airplane mode) and without AGPS data also. But I get zero fixes whatever I try. I am trying to keep the "hardware possibility" a last resort. I am trying to find a software solution to a software triggered problem (the upgrade, it seems...).
koutheir said:
Normally, the GPS should be able to fix satellites even without Data (In Airplane mode) and without AGPS data also. But I get zero fixes whatever I try. I am trying to keep the "hardware possibility" a last resort. I am trying to find a software solution to a software triggered problem (the upgrade, it seems...).
Click to expand...
Click to collapse
The fact that I have done everything possible and it still will not fix to any satellite makes me convinced this is a hardware problem.
However, since this only started when I first upgraded to KitKat (didn't take any OTAs) I'm holding out hope there is some type of fix that we're overlooking.
Any additional help or advice from anyone else would be much appreciated, thanks in advance!
I finally resolved my issue
Current situation: GPS fixes 8 satellites out of 25 even between high buildings.
Short solution: set the right CSC for your device.
Advice: Always set the right CSC for your device, even if you happen to mess with it (which is arguably your own right as you own the device...).
Long solution:
- Backup your data and your apps. During the procedure, the device !!!WILL PERFORM A FACTORY RESET!!!
- Root your device.
- Open a terminal emulator on the device.
- Type the following commands (let the terminal application gain root access when you get prompted):
$ su
# am start -a android.intent.action.MAIN -n com.sec.android.Preconfig/com.sec.android.Preconfig.Preconfig
- You will get a window with a list of CSC codes. Select the one corresponding to your device and stock firmware, and push the button INSTALL.
- The device will reboot, and !!!WILL PERFORM A FACTORY RESET!!!
- That's all folks.
- (Now go mess up things again, and again...)
koutheir said:
I finally resolved my issue
Current situation: GPS fixes 8 satellites out of 25 even between high buildings.
Short solution: set the right CSC for your device.
Advice: Always set the right CSC for your device, even if you happen to mess with it (which is arguably your own right as you own the device...).
Long solution:
- Backup your data and your apps. During the procedure, the device !!!WILL PERFORM A FACTORY RESET!!!
- Root your device.
- Open a terminal emulator on the device.
- Type the following commands (let the terminal application gain root access when you get prompted):
$ su
# am start -a android.intent.action.MAIN -n com.sec.android.Preconfig/com.sec.android.Preconfig.Preconfig
- You will get a window with a list of CSC codes. Select the one corresponding to your device and stock firmware, and push the button INSTALL.
- The device will reboot, and !!!WILL PERFORM A FACTORY RESET!!!
- That's all folks.
- (Now go mess up things again, and again...)
Click to expand...
Click to collapse
Thanks Bro. Appreciate your help.
ive been having gps issues as well and attempted to fix by using the android terminal csc but nothing comes up after i enter those lines..
Anybody?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
GPS Fix
koutheir said:
Hello,
First of all, I need to say I searched for weeks to solve this issue. I found no other way than posting a question. I hope someone could help me solve it. I checked the logs using "aLogcat" but nothing is relevant to the GPS. Any kind of help is welcome, I am not asking for a full step-by-step guide
* Issue: GPS cannot find my location, even when kept for long periods under clear sky (20 minutes). I tried "Faster GPS" and "GPS Status" apps to debug the thing, but useless. I simply can't get a fix.
* Infos:
Device: SGH-I337M
OS: Android 4.4.2 (Samsung Stock ROM)
Baseband: I337MVLUFNE1
Kernel: 3.4.0-1529758
Build: KOT49H.I337MVLUFNE1
Location: France
* /etc/gps.conf
##################################################
ENABLE_WIPER=1
LPP_PROFILE=0
DEFAULT_AGPS_ENABLE=TRUE
A_GLONASS_POS_PROTOCOL_SELECT=0
SUPL_VER=0x10000
CAPABILITIES=0x37
NTP_SERVER=fr.pool.ntp.org
INTERMEDIATE_POS=1
XTRA_SERVER_1=(a link to xtra1 (dot) gpsonextra (dot) net (slash) xtra2.bin
XTRA_SERVER_2=(a link to xtra2 (dot) gpsonextra (dot) net (slash) xtra2.bin
XTRA_SERVER_3=(a link to xtra3 (dot) gpsonextra (dot) net (slash) xtra2.bin
ERR_ESTIMATE=0
DEBUG_LEVEL=4
CURRENT_CARRIER=common
NMEA_PROVIDER=0
##################################################
Thank you
Click to expand...
Click to collapse
Install SELinuxModeChanger app from google play and change the permission from enforcing to permissive. Should fix your gps problem.