Database Users

GPS Control Plane settings.. Possible GPS fix

Hello,
I was wondering if anyone was familiar with the control plane option in SUPL settings.
The reason I ask is that I was playing around in the secret code area of SG Tools and noticed an area marked GPS
SGS Tools -> Secret Codes -> ServiceMode, Debug, Netz, Audio, Common -> Common -> GPS -> Display and Change CP Status.
I enabled the Control Plane and then set SUPL settings in lbstest to supl.google.com etc and change SUPL Mode to Control Plane. My gps has been crazy awesome since then. Also change application settings Accuracy to 25.. I do have the jupiter file gps fix installed but GPS would still loose me until I made these changes. I was hoping someone could explain Control Plane and or someone would test these settings for themselves and let me know how it works. I am running Axura Beta 5 with Setiron Kernel 1.4.2

None of those settings "fix" GPS.

Thanks for the reply. Are you aware of what the control plane setting is for?

Not that I'm actually interested in this "fix", but is your "crazy awesome" GPS just giving you faster initial position locks?
Getting a position lock is one thing, but having the GPS actually be able to track your movement and be accurate is different...which many overlook when they say their GPS works. If you were to use to Captivate in the car to navigate with, would it be accurate? If you can say yes to that, you could consider your GPS working then.

norcal einstein said:
Not that I'm actually interested in this "fix", but is your "crazy awesome" GPS just giving you faster initial position locks?
Getting a position lock is one thing, but having the GPS actually be able to track your movement and be accurate is different...which many overlook when they say their GPS works. If you were to use to Captivate in the car to navigate with, would it be accurate? If you can say yes to that, you could consider your GPS working then.
Click to expand...
Click to collapse
I am getting faster locks.. more sattelites.. I also tested while driving and it stayed good the entire time.. I am going to test again on my hour drive home tonight..
Sent from me to you over wires using only 1's and 0's

Also my main interest is in finding out more information on what this setting does as well. It is my opinion that this has helped and I wanted more imformation and also to see if it helps qnyone else..
Sent from me to you over wires using only 1's and 0's

+1
I dunno why but set as control plane gives me more sats and faster locks even better tracking.
This is the first thing i do every time after flashing a new rom to my cappy.
ms base mode, google supl sever with control plane mode and secure socket off.
Sent from ATT Captivate operated by Perception build 5

drancid said:
+1
I dunno why but set as control plane gives me more sats and faster locks even better tracking.
This is the first thing i do every time after flashing a new rom to my cappy.
ms base mode, google supl sever with control plane mode and secure socket off.
Sent from ATT Captivate operated by Perception build 5
Click to expand...
Click to collapse
Have you checked to see if the control plane is enabled via sgstools?
Sent from me to you over wires using only 1's and 0's

mpencexda said:
Have you checked to see if the control plane is enabled via sgstools?
Sent from me to you over wires using only 1's and 0's
Click to expand...
Click to collapse
nope but i'll check it now..
Sent from ATT Captivate operated by Perception build 1

Control Plane is an alternative method of accessing the AGPS server from User Plane (SUPL). Control Plane goes over the cellular providers Control Plane (fancy that!) whereas SUPL goes out over the GPRS network (HSPA, 3G, etc.)
For Control Plane to work, the cellular provider has to have in place specific technology intended for use with AGPS. All older AGPS solutions prior to the deployment of SUPL use Control Plane. Basically it's "the old way"
Note that you can obtain the exact same AGPS data through a SUPL connection to the same set of servers AT&T maintains. This is the default setting for "Server FQDN Type" - AUTO Config.
Basically, setting it to AGPS Mode - Control Plane (regardless of other server settings) is the same as setting AGPS Mode - SUPL, SUPL Secure Socket - ON, Server - h-slp.mnc410.mcc310.pub.3gppnetwork.org, Server Port - 7275. AND is also the same as using "Server FQDN Type" - AUTO Config, providing your cellular provider is AT&T (MNC 410 MCC 310).
Note that the specifications for AUTO Config will read the MCC/MNC of your network provider (in my example above, AT&T) and change the mncXXX.mccYYY part to match your providers MNC/MCC. Per the 3gpp SUPL spec, when in a home network, the URL to access for SUPL services is h-slp.mncXXX.mccYYY.pub.3gppnetwork.org, which breaks down to:
h-slp - Home SUPL Location Platform
mncXXX - MNC of the current network the phone is parked on
mccYYY - MCC of the current network the phone is parked on
pub.3gppnetwork.org - A (purposefully) un-registered domain name free for use by cellular providers.
When you are roaming, the URL changes to:
v-slp.mncXXX.mccYYY.pub.3gppnetwork.org
where v-slp instead means Visiting SUPL Location Platform.
So, to sum that up, if your cellular provider is following 3gpp SUPL recommendations properly, when you attempt a SUPL connection to h-slp.mncXXX.mccYYY.pub.3gppnetwork.org, your cellular provider should connect you to THEIR provided SUPL server. In the case of AT&T this is fully functional. Note that this will NOT work on Wi-Fi, the DNS will not resolve (since you aren't connected to a cellular network, the ISP you're on will not maintain a SUPL server for you, unless they are just THAT nice)
Note that if you use a program like MarketAccess to change your MNC/MCC to allow access to other markets, the SUPL address will also change (to reflect the altered MNC/MCC) and thus be broken in automatic mode.
Anywho, all of this only affects the initial lock time, when set to MS-Based. (Defaults on the stock ROM to standalone, which doesn't use AGPS at all, and sane people will use MS-Based)
Tracking once you have a lock should NOT be affected by any of these changes.
In case you're wondering where I got my information, it's not my first go-round to this particular party. I did all the legwork for this a bit over a year ago, and put up a compendium post about it in March 2009: http://forum.xda-developers.com/showthread.php?t=489887 All the info I reference from the SUPL specifications is obtained by spending hours reading the actual, incredibly boring whitepapers.
I haven't had time to properly devote to the GPS problem for captivate like I have for previous WM devices (I just got the cappy), but i'm guessing there's some errors in either the satellite correlation done in the baseband, or in the driver's interpretation of the output in the kernel code. It might also be the case that the phone is relying on a clock generator that isn't putting out the exact cycles they have it programmed for, thus introducing clock drift into the correlation algorithm. The clock has to be precise and synced up to the GPS clocks in order to properly trilaterate location. This might explain the drift over time and then snapping back to a real location once the clocks are properly synced again. (GPS satellites send the complete information required to sync a clock accurately every 12.5 minutes.)
Do note that the clock i'm referring to is the internal GPS reference clock, which is not related in any way to the time set on the device. Internally, the device does keep track of the offset between GPS time and Device Time, but Device Time is not used in the GPS calculations (a different internal clock is used, and synced to the satellites themselves with each transmission) - Previously it has been suggested that ensuring the phones clock is as accurate as possible would make a difference, but that is not the case (due to it not being the same clock)
Either way, any changes to gps.conf or secgps.conf aren't gonna cut the mustard with this particular issue. Initial fix time and number of initial sats, sure. But once the GPS is fired up and running, and has time to pick up a constellation update from the satellites, you're in the same boat as anyone else.
BTW. You can read the adb logcat output to easily see if your phone is utilizing AGPS. You will get an initial fix with an accuracy of appx. 1500m and the log will show that it is not a GPS fix but instead a network provided location. It will then show this location being injected into the GPS driver (AGPS)

Thanks for the info.. that was amazing. I really hope that you get some time to devote to this as you seem informed
Sent from me to you over wires using only 1's and 0's

Thanks
DA G,
Thanks for the information, glad to have you in cappy land!

Da_G said:
Control Plane is an alternative method of accessing the AGPS server from User Plane (SUPL). Control Plane goes over the cellular providers Control Plane (fancy that!) whereas SUPL goes out over the GPRS network (HSPA, 3G, etc.)
For Control Plane to work, the cellular provider has to have in place specific technology intended for use with AGPS. All older AGPS solutions prior to the deployment of SUPL use Control Plane. Basically it's "the old way"
Note that you can obtain the exact same AGPS data through a SUPL connection to the same set of servers AT&T maintains. This is the default setting for "Server FQDN Type" - AUTO Config.
Basically, setting it to AGPS Mode - Control Plane (regardless of other server settings) is the same as setting AGPS Mode - SUPL, SUPL Secure Socket - ON, Server - h-slp.mnc410.mcc310.pub.3gppnetwork.org, Server Port - 7275. AND is also the same as using "Server FQDN Type" - AUTO Config, providing your cellular provider is AT&T (MNC 410 MCC 310).
Note that the specifications for AUTO Config will read the MCC/MNC of your network provider (in my example above, AT&T) and change the mncXXX.mccYYY part to match your providers MNC/MCC. Per the 3gpp SUPL spec, when in a home network, the URL to access for SUPL services is h-slp.mncXXX.mccYYY.pub.3gppnetwork.org, which breaks down to:
h-slp - Home SUPL Location Platform
mncXXX - MNC of the current network the phone is parked on
mccYYY - MCC of the current network the phone is parked on
pub.3gppnetwork.org - A (purposefully) un-registered domain name free for use by cellular providers.
When you are roaming, the URL changes to:
v-slp.mncXXX.mccYYY.pub.3gppnetwork.org
where v-slp instead means Visiting SUPL Location Platform.
So, to sum that up, if your cellular provider is following 3gpp SUPL recommendations properly, when you attempt a SUPL connection to h-slp.mncXXX.mccYYY.pub.3gppnetwork.org, your cellular provider should connect you to THEIR provided SUPL server. In the case of AT&T this is fully functional. Note that this will NOT work on Wi-Fi, the DNS will not resolve (since you aren't connected to a cellular network, the ISP you're on will not maintain a SUPL server for you, unless they are just THAT nice)
Note that if you use a program like MarketAccess to change your MNC/MCC to allow access to other markets, the SUPL address will also change (to reflect the altered MNC/MCC) and thus be broken in automatic mode.
Anywho, all of this only affects the initial lock time, when set to MS-Based. (Defaults on the stock ROM to standalone, which doesn't use AGPS at all, and sane people will use MS-Based)
Tracking once you have a lock should NOT be affected by any of these changes.
In case you're wondering where I got my information, it's not my first go-round to this particular party. I did all the legwork for this a bit over a year ago, and put up a compendium post about it in March 2009: http://forum.xda-developers.com/showthread.php?t=489887 All the info I reference from the SUPL specifications is obtained by spending hours reading the actual, incredibly boring whitepapers.
I haven't had time to properly devote to the GPS problem for captivate like I have for previous WM devices (I just got the cappy), but i'm guessing there's some errors in either the satellite correlation done in the baseband, or in the driver's interpretation of the output in the kernel code. It might also be the case that the phone is relying on a clock generator that isn't putting out the exact cycles they have it programmed for, thus introducing clock drift into the correlation algorithm. The clock has to be precise and synced up to the GPS clocks in order to properly trilaterate location. This might explain the drift over time and then snapping back to a real location once the clocks are properly synced again. (GPS satellites send the complete information required to sync a clock accurately every 12.5 minutes.)
Do note that the clock i'm referring to is the internal GPS reference clock, which is not related in any way to the time set on the device. Internally, the device does keep track of the offset between GPS time and Device Time, but Device Time is not used in the GPS calculations (a different internal clock is used, and synced to the satellites themselves with each transmission) - Previously it has been suggested that ensuring the phones clock is as accurate as possible would make a difference, but that is not the case (due to it not being the same clock)
Either way, any changes to gps.conf or secgps.conf aren't gonna cut the mustard with this particular issue. Initial fix time and number of initial sats, sure. But once the GPS is fired up and running, and has time to pick up a constellation update from the satellites, you're in the same boat as anyone else.
BTW. You can read the adb logcat output to easily see if your phone is utilizing AGPS. You will get an initial fix with an accuracy of appx. 1500m and the log will show that it is not a GPS fix but instead a network provided location. It will then show this location being injected into the GPS driver (AGPS)
Click to expand...
Click to collapse
Da_G? In my Captivate thread? This brings me back to playing with with GPS on the HTC Touch Pro...
It's crazy that was 2 years ago.

Hi, CLShortFuse, long time no see
Actually i've been lurking for a while now, just trying to learn things before I get down to the nitty gritty of modding source code (and writing some new stuff of my own!)
To be fair, I was a GPS fan before I became a PDA fan I remember doing firmware hacks to the SirfStar III chipset to enable functionality above 18,000m, faster than 515m/s, and bypassing the acceleration and motional jerk limiters Why? Because my GPS should work to its full ability, dammit!
As I understand, we don't have access to any of the baseband source. This is probably where a large amount of the GPS calculations are handled (It is so with Qualcomm, at least) and so it may not be something we can address. But a good thorough look at the kernel driver(s) should answer that question.
I wonder if the chipset is even SBAS Capable (WAAS/EGNOS, i'm quite sure it doesn't have a receiver for any land based solutions). The accuracy reminds me of GPS back in the days when Selective Availability was up (artificial GPS accuracy limitations put in place by the military) before DGPS came about.
Ironically, my hacked bluetooth GPS from 2005, a Globalsat BT338 remains the most accurate consumer level GPS I have used to date, with accuracies down to .3 meters in ideal conditions. (During normal in the field conditions like stuck in a backpack, in the back seat of a car, with perhaps a 5 degree view of the sky, and wicked multipath from skyscrapers it's accurate to around 2 meters) - basically, you can count on it to be accurate down to what lane of traffic you are in
The same chipsets are made available to smartphone manufacturers. (The current model being the SirfStar IV, and capable of even better accuracy than that older one) - I only wish more manufacturers would actually use them!
I actually currently use that BT GPS for any navigation I do. But nonetheless, we don't have such a nice platform to work with, so let's see what we can do with what we have Perhaps tomorrow i'll take a drive with 2 captivates, both loaded to stock firmware (updated to the "gps fix" build) + the samsung GPS fix on the market (which we know is worthless, but just for S&G)
I'll record raw NMEA output from both GPS units (Captivate using internal GPS, and Captivate using BT-338 GPS through bluetooth serial NMEA), and post that up along with a google earth .kml for easy comparison. The difference between the two is quite striking. I'll be using that GPS unit as my baseline for "great performance" when the hackery begins
(edit: taking a quick look at the kernel source it looks like we have a BCM4751 and i'm fairly certain all the relevant calculations are handled in the baseband. The good news is that chipset does support SBAS. I doubt it's properly handling it however, as it doesn't even perform up to the level of a GPS without SBAS. If everything IS being handled in baseband, i'm going to need to get my hands on source code to the radio to fix it, which won't be the easiest thing ever )

Getting interesting now...

Did anyone come across this yet? Is this real or a joke?
Samsung Captivate And Vibrant Finally Get GPS "Fix" Via GPSSamsungRestore App
The Galaxy S phones are, without a doubt, among the best Android phones out there, but for some time now, the handsets have been plagued by one potential showstopper – malfunctioning GPS capabilities. Worry not, though – in addition to an update that rolled out a few months ago, Samsung has developed an app called GPSSamsungRestore which is now available from the Android Market for all users of AT&T’s Captivate and T-Mobile’s Vibrant. So what does it do? It undoes any modifications to the GPS and basically reverts it to its original state. While it remains to be seen how reverting the GPS to its original, broken state fixes it, I suppose it can’t hurt to give it a shot if you’re a Captivate or Vibrant owner.
Note: The app only shows up in the Market for Captivate and Vibrant owners, so if you’re looking for it just for kicks, you won’t find it unless you’ve got one of those devices. It isn’t listed on AppBrain, either.
Click to expand...
Click to collapse
Quote from Android Police

Is there a validity with that GPSSamsungRestore fix.
and +1 on awesome person joining this awesome group!

Wow..very informative read there. Looks like we've found our Cappy GPS fixer-upper! Nice to have you aboard.
Sent from my couch on my phone.

Da_G I'm glad to see you have a captivate. Used your roms all the time on my Touch Pro. Glad to see another great dev on this phone. Looking forward to any work you do with it.

Amazing explanation, we are all aware of the AGPS -GPS relation but we like to lie to ourselves that some of these tweaks are actually working and that our devices are as good as any other. The truth is that our device is waaaay better with the latest developments than any other device on the market, and mine is simply perfect.
Honestly, I've been running Cognition 2.3b6 with the Jupiter v6 tweaks and had no problems with the GPS on a trip in the mountains, between trees and under heavy snow (300km round trip). Absolutely none! A bit slow lock but great tracking.
Now I'm using 2 different tweaks, the JM9 GPS drivers + this control plane thing on the same rom, Cog 2.3b6. Got a lock in 10-15 sec on 7 sats (tested for about 10 mins) but didnt have the chance to take it for a test drive. Hopefully will get the same results like before. If not, I'll just revert back to "stock" Cog with jupiter tweaks, that was the best.

GPSfix

I have found some interesting stuf for GPS on Galaxy 3, here it is:
Settings\Parameter Settings\Address\Server Type: UMTS SLP
Settings\Parameter Settings\Position mode: option2
Settings\Fix Request Settings\Session Operation: MS based
Settings\Fix Request Settings\Server Option: Local default: Default
gpsOne XTRA\Xtra Enable: Disable

mmhhh,
whats better now? Discussion starting? See:
http://forum.xda-developers.com/showpost.php?p=14206731&postcount=4618
I'm not sure - Kyrillo's settings are good for me.
What do others say?

I simple open gps2 setup by using the code...on back against it fix me with 9-10 satellites within few seconds..
Sent from my GT-I5800 using XDA App

I know that I now have fix in my living room
With kyrillo's settings, sometimes I had to wait 10 and more minutes to get fix, under clear sky or in my car driving.

Hi Sidzim,
checked out your settings and can't see a difference. My experience
is that it depends on if there's a data connection, because of "A-GPS"
(download the actual paths of the satellites from a ntp server).
With data connection is always fast, if you've set the right ntp server for your region.
Without data, first fix takes between 1 & 3 minutes and the following go much faster.
Without data connection the phone has to download the actual paths of the satellites from themselves. That takes long.
The longer the break between switching GPS off and on again the longer it will take to get the fix.
However for me it's okay usually... others seem to be very unlucky with it.

Location services don't work?

I remember why I sold my original Optimus 7 now, I bought a new one yesterday as it was on offer, but for the life of me I can't get location services to work, my iPhone instantly find me, this phone just sits searching and gives and error it can't find me. It seems to be using GPS which when in doors isn't going to find me, it doesn't seem to use WiFi or Cell Towers. Outside its hit and miss if it finds me. I'd say it was a dodgy phone if the original phone I had didn't have the same problems.
Anyone any ideas? Its not that the location is off a bit, it just simply can't find me via wifi or cell

Vodafone's Optimus 7 firmware is broken - I worked out this works:
In MFG, navigate to Engineer Menu / Device Test / Sensor Test / GPS Test / GPS Setting
In User Setting, use following values:
Operation Mode: MS-Based
Accuracy: 100
Aiding Data: Hot Start
Auto Answer: Disable
Interval: 1
Number of Fixes: 9999999
Intermediate Data: On
In System Setting:
URL: supl.google.com:7276
Posnode: 255
2G: Loc Estimate
3G: Loc Estimate
Use Security: Use Security
MO Method: User Plane
PLEASE sign up on the Vodafone e-forum to add your voice to the request to get this fixed on this thread:
http://forum.vodafone.co.uk/t5/Othe.../GPS-Fails-after-WP7-Mango-Update/td-p/872141
Thanks

Thanks for this, Going to flash a generic European ROM and see what happens

Not working for me.
LG E900 Vodafone

I flashed the unbranded European ROM and they still don't work. I am thinking it a bug with all E900 phones.

Tried Nokia maps and it found me instantly in the house, The Weather Channel also found me instantly, so I think it all comes down to the app.

gps problems

anyone else having a problem where gps wont lock?
the icon just keeps flashing and cant fomd location

No problems here. You have checked your location with google maps?

Me too. 0 satellite found, 0 lock. Tried on stock flashed with odin and custom like Alliance.
I've searched on the web, it say the hardware is broken.
Great, I take to myself, flashing roms is a risk.

Doghan13 said:
Me too. 0 satellite found, 0 lock. Tried on stock flashed with odin and custom like Alliance.
I've searched on the web, it say the hardware is broken.
Great, I take to myself, flashing roms is a risk.
Click to expand...
Click to collapse
nope, ive got the problem on stock.
its wierd change location setting between high and gps only etc and it sometimes works.
im not happy with this, im rooted so its not as simple as taking phone back

did u find a fix

I have the exact same problem. Stock ROM, but I may have let water in. GPS test shows 18 or 19 satellites in view, but cannot fix on any of them. Tried all the usual little stuff, stumped.

DrivenKeys said:
I have the exact same problem. Stock ROM, but I may have let water in. GPS test shows 18 or 19 satellites in view, but cannot fix on any of them. Tried all the usual little stuff, stumped.
Click to expand...
Click to collapse
Have you tried gpsfix from play store.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5

Same results with GPS fix, it sees them, but never ever fixes on them. I don't even think this is due to water, it worked perfectly once dried and rice-bagged. I dropped the bare phone a lot, I think that may have shaken something loose. I lived in Socal, and it worked great. I drove to Norcal and Oregon, and it can no longer fix. Dropped it plenty during those times. I've tried several apps that do the same thing clearing and refreshing the data. This phone simply never gets a GPS fix anymore. Frustrating as it still sees the satellites.
I'm really trying to avoid my deductible here, but may just cough it up to have gps for emergency notifications.

DrivenKeys said:
Same results with GPS fix, it sees them, but never ever fixes on them. I don't even think this is due to water, it worked perfectly once dried and rice-bagged. I dropped the bare phone a lot, I think that may have shaken something loose. I lived in Socal, and it worked great. I drove to Norcal and Oregon, and it can no longer fix. Dropped it plenty during those times. I've tried several apps that do the same thing clearing and refreshing the data. This phone simply never gets a GPS fix anymore. Frustrating as it still sees the satellites.
I'm really trying to avoid my deductible here, but may just cough it up to have gps for emergency notifications.
Click to expand...
Click to collapse
Ok, this has about .00001 chance of being correct but.. I had a similar problem once , again not at all saying this resolve anything and may have be pure coincidence, but when i reflashed my rom I had not checked the opening samsung setup options which have some gps options in it. I reinstalled the rom, checked the samsung options to on and gps started working.
Hope this helps, but I doubt it, it's a last resort anyways.. Good luck. ?
You could also try odin to reflash stock rom.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5

I just did a factory reset, and skipped the most intrusive prompts. Good idea to let it all on before paying for a replacement...
I'm not rooted, do you think it may help to do so and proceed from there? I'll be paying tmobile's deductible for a damaged phone anyway, so don't see any warranty issues at this point.
I'm comfortable with rooting and flashing, did it with my last 2 phones. If anybody wants to point me to the best roms/back to stock recovery, that's cool. I will search when the time to flash comes, but I'm really pressed for time, atm.

DrivenKeys said:
I just did a factory reset, and skipped the most intrusive prompts. Good idea to let it all on before paying for a replacement...
I'm not rooted, do you think it may help to do so and proceed from there? I'll be paying tmobile's deductible for a damaged phone anyway, so don't see any warranty issues at this point.
I'm comfortable with rooting and flashing, did it with my last 2 phones. If anybody wants to point me to the best roms/back to stock recovery, that's cool. I will search when the time to flash comes, but I'm really pressed for time, atm.
Click to expand...
Click to collapse
Why not try using odin and flashing back to original stock, sammobile.com is a good place to get original.
SM-G900W8, 0x1
A recovered flashaholic since Aliance Rom 5.5

i managed to fix mine by installing sygic(the free truck version on play), it fixed mine dont know how maybe some type of driver?
here is link
http://forum.xda-developers.com/gal...rmware-gps-t2819249/post56855149#post56855149

to be honest i found a fix, the gps settings were wrong for my country.
i just needed to add it to the config file and it works now.
agps helps as well
i live in the uk i fixed it by adding the 4 #uk server ones to my gps settings conf file. a quick google will find the gps settings for your country (check you csc is right first though)
go to
system/etc/gps.conf
this is the contents of my conf file
#Uncommenting these urls would only enable
#the power up auto injection and force injection(test case).
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
# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0
#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
#uk server
# NTP_SERVER=0.uk.pool.ntp.org
1.uk.pool.ntp.org
2.uk.pool.ntp.org
3.uk.pool.ntp.org
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
# If DEBUG_LEVEL is commented, Android's logging levels will be used
DEBUG_LEVEL = 4
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000
# GPS Capabilities bit mask
# SCHEDULING = 0x01
# MSB = 0x02
# MSA = 0x04
# ON_DEMAND_TIME = 0x10
# GEOFENCE = 0x20
# default = ON_DEMAND_TIME | MSA | MSB | SCHEDULING | GEOFENCE
CAPABILITIES=0x37
# 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.host.com or IP
# SUPL_PORT=1234
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
####################################
# LTE Positioning Profile Settings
####################################
# 0: Enable RRLP on LTE(Default)
# 1: Enable LPP_User_Plane on LTE
# 2: Enable LPP_Control_Plane
# 3: Enable both LPP_User_Plane and LPP_Control_Plane
LPP_PROFILE = 0 # Sensor R&D : This will not be injected to MODEM
################################
# EXTRA SETTINGS
################################
# NMEA provider (1=Modem Processor, 0=Application Processor)
NMEA_PROVIDER=1
##################################################
# Select Positioning Protocol on A-GLONASS system
##################################################
# 0x1: RRC CPlane
# 0x2: RRLP UPlane
# 0x4: LLP Uplane
A_GLONASS_POS_PROTOCOL_SELECT = 0x0
##################################################
# Delete only Ephemeris files
##################################################
#0 : off - default
#1 : on - Erase only eph files when we use 'delete aiding data' function.
DEL_EPH_ONLY = 0

Yeah will probably have to go back to stock ROM is there Android 5 out for s5 guess time to leave this world lol

UMI Super issues - touchscreen and GPS

I am one of the loosers regarding this high-end phone and I wanted to share some experience with you guys here.
I was running (and also OTA updating) my UMI Super for around 2 weeks and except GPS and not a real good 3G connectivity all was good. GPS isn't just really working and it hops around most of the times. All fixes like Developer mode etc. applied and didn't work.
After 2 weeks now the touchscreen went crazy and one can't control the phone anymore. There is no fix and also doing a factory wipe or a fresh install of the firmware (even the oldest one) doesn't fix this issue >>> the UMI isn't usable anymore. Many people reporting the same in the UMI forums btw.
Got no response from their Support via Email and no fix or advice as well. Now my phone is dead and i regret this decision to have bought this device. Simply it isn't even worth a single USD (for me) and my recommendation is if you want to go with it just buy it from a trusted dealer who offers reliable money-back or replacement policies.

Hello, that a pity man.
I had bought my Super on igogo.es some weeks ago and had serious issues with the GPS signal as you described. I sent the phone back to China (I had to pay 25 euros) and received a new phone. I can tell you that the GPS signal y 85 % better but not perfect
Sent from my UMI_SUPER using XDA-Developers mobile app

i'm located in europe and bought the UMI Super at Gearbest and can't use this smartphone :
got 3G/4G signal issue (no or low signal)
got GPS issue (almost not working)
got Wi-Fi issue (poor signal)
got camera issue (horrible "quality")
got battery issue (draining very fast and hard believe it's a true 4000mAh)
got temperature issue of the metal body after only few minutes of use
got fingerprint recognition issue sometimes
got compatibility issue: some third party apps from Google store are not working properly (crashing or cannot run properly)
i've reported those bugs on the official support forum community.umidigi.com and an admin removed my posts and banned me without warning !
i did some research and it seems they often remove bad reviews and ban members who post such topics !

Hi. Does anyone knows how to solve the problem with the GPS? I'd returned back to China my first Super. I received a second one but the GPS signal is really bad
Sent from my UMI_SUPER using XDA-Developers mobile app

cimoblas said:
Hi. Does anyone knows how to solve the problem with the GPS? I'd returned back to China my first Super. I received a second one but the GPS signal is really bad
Sent from my UMI_SUPER using XDA-Developers mobile app
Click to expand...
Click to collapse
I have found the partial solution. Could you or anyone to try that?
You need to root your phone. Don't ask me how to do it. Then configure your phone to use GPS only 'Settings > Location > Mode > Device only'.
Then disable battery optimization for your app you want to use with GPS 'Settings > battery > battery optimization'.
An finally try this gps config. You need to have '/system' partition writable. How to do that, just google. Then change /system/etc/gps.conf to something like this:
DEFAULT_AGPS_ENABLE=TRUE
ENABLE_WIPER=0
DEFAULT_USER_PLANE=TRUE
REPORT_POSITION_USE_SUPL_REFLOC=1
NTP_SERVER=cz.pool.ntp.org
QOS_TIME_OUT_STANDALONE=80
QOS_ACCURACY=5
QOS_TIME_OUT_AGPS=95
QosHorizontalThreshold=10
QosVerticalThreshold=5
# 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
# ON_DEMAND_TIME = 0x10
# ULP = 0x20
# default = MSA | MSB | SCHEDULING | ULP | ON_DEMAND_TIME
CAPABILITIES=0x17
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=5
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.host.com or IP
# SUPL_PORT=1234
# 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=
#ACCEL_RANDOM_WALK_SPECTRAL_DENSITY=
#ANGLE_RANDOM_WALK_SPECTRAL_DENSITY=
#RATE_RANDOM_WALK_SPECTRAL_DENSITY=
#VELOCITY_RANDOM_WALK_SPECTRAL_DENSITY=
# Sensor Sampling Rate Parameters for Low-Data Rate Filter (should be greater than 0)
SENSOR_ACCEL_BATCHES_PER_SEC=2
SENSOR_ACCEL_SAMPLES_PER_BATCH=5
SENSOR_GYRO_BATCHES_PER_SEC=2
SENSOR_GYRO_SAMPLES_PER_BATCH=5
# Sensor Sampling Rate Parameters for High-Data Rate Filter (should be greater than 0)
SENSOR_ACCEL_BATCHES_PER_SEC_HIGH=4
SENSOR_ACCEL_SAMPLES_PER_BATCH_HIGH=25
SENSOR_GYRO_BATCHES_PER_SEC_HIGH=4
SENSOR_GYRO_SAMPLES_PER_BATCH_HIGH=25
# 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 sensor provider interface(1=Sensor1 API, 2=Android NDK)
SENSOR_PROVIDER=2
# Bit mask used to define which sensor algorithms are used.
# Setting each bit has the following definition:
# 0x1 - DISABLE_INS_POSITIONING_FILTER
# 0x0 - ENABLE_INS_POSITIONING_FILTER
SENSOR_ALGORITHM_CONFIG_MASK=0x1
################################
# Indoor Positioning Settings
################################
# 0: QUIPC disabled, 1: QUIPC enabled, 2: forced QUIPC only
QUIPC_ENABLED = 0
################################
# EXTRA SETTINGS
################################
# Enable or Disable Wiper (1=Enable, 0=Disable)
ENABLE_WIPER=0
# NMEA provider (1=Modem Processor, 0=Application Processor)
NMEA_PROVIDER=1
####################################
# LTE Positioning Profile Settings
####################################
# 0: Enable RRLP on LTE(Default)
# 1: Enable LPP_User_Plane on LTE
# 2: Enable LPP_Control_Plane
# 3: Enable both LPP_User_Plane and LPP_Control_Plane
LPP_PROFILE = 0
Click to expand...
Click to collapse

Camera in UMi super is not audio great camera sub standard

Hi all,
I got a different problem regarding the touchscreen.
Mine got broken and I bought a replacement one, problem is that the screen doesn't seem to be calibrated and everything is misaligned, like the top bar drops when you slide from the middle of the screen.
The buttons work on the top middle of the screen...
Is there any workaround ?
Cheers

Anybody with a dead umi Super Euro edition that the screen, touchpad and battery are still good should please contact me on [email protected].
Mine exploded while I was charging it and it destroyed the screen.

You can buy a whole screen with touch and digitizer for about 27 bucks on aliexpress.
I have ordered mine because min got cracked on a drop.
Is this GPS issue solved on nougat firmware?
thx
pOpY

Here we will specify basic UMIDIGI A1 Pro issues and fixes can be trusted basically as they have been tried. It would be best for you to remember it that you are not liable for any issue caused to the cell phone due to your carelessness while following strategies.
To keep up the speed simple towards this, you will be acquainted with the best potential arrangements and strategies against every one of the issues which are normal with this cell phone.
SIM Card related issues:
With a double SIM Slot, you get 2G, 3G, 4G help also in the UMIDIGI A1 Pro.
2G: GSM B2/B3/B5/B8
3G: WCDMA B1/B2/B4/B5/B8
4G: FDD-LTE B1/B2/B3/B4/B5/B7/B8/B12/B17/B19/B20
TDD-LTE B38/B40/B41
There is a double SIM support with Nano+Nano or miniature SD. Since SIM cards will in general assume the most fundamental part in any Smartphone, any issue with respect to the equivalent can influence you an excessive lot. So on the off chance that you run over any such thing, here is a reference:
Check whether the SIM Card is anyplace actually harmed.
Go to the Phone Settings and pick network physically.
Check for the Compatibility issues, assuming any.
Know whether you have embedded the SIM card appropriately into its individual opening or not.
On occasion, the card may have a working recurrence which doesn't will in general match the handset.
There may be an opportunity that the SIM Card space is harmed genuinely.
Watch that you are not utilizing your telephone in the telephone mode.
Impair the Flight Mode if it's on.
The issue can likewise happen because of low sign strength.
Change or all the more precisely I would recommend you supplant your SIM Card if nothing else works.

I was running (and also OTA updating) my UMI Super for around 2 weeks and except GPS and not a real good 3G connectivity all was good. GPS isn't just really working and it hops around most of the times. All fixes like Developer mode etc. applied and didn't work.
After 2 weeks now the touchscreen went crazy and one can't control the phone anymore. There is no fix and also doing a factory wipe or a fresh install of the firmware (even the oldest one) doesn't fix this issue >>> the UMI isn't usable anymore. Many people reporting the same in the UMI forums btw.

I am one of the loosers regarding this high-end phone and I wanted to share some experience with you guys here.