Database Users

Is GPS data?

I am going to Ireland and would like to use TomTom on my Verizon phone. Does the GPS signal work over the data line? I won't have service while I am there - will the GPS work?

Try turning off your data in the comm manager and see if it works for you. I may be mistaken, but I think aGPS uses a tiny amount of data and regular GPS doesn't.

yep the whole concept of GPS is based on communicating directly with satellites
aGPS is with the towers

You can only use standalone gps in Ireland. So you have to be running a custom rom on a Verizon phone for this feature. agps (Vahalla) will not work in Ireland.

I am running a custom ROM. I can use the standalone GPS by just turning off the data connection, right?

No. You must change gps mode to 2 and turn off agps. Look here for my settings. Also the gps on the Titan sucks and getting a standalone outside of CDMA service sucks.
http://forum.xda-developers.com/showthread.php?t=458923

I read through the thread you sent and a few others. These are the reg changes I found:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:EnableAGPS = 0
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:EnableGPSSmartMode = 0
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:GPSMode = 1
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:QoSAccuracy = 25
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:QosPerformance = 89
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:TimeBetweenFixes = 1000
Then in QPST, only Autonomous and GPS/AFLT Hybrid are checked.
And phone is in flight mode.
Is this right?

Yes that should be about right.

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.

YotaPhone 2 GPS issues

Hi there Yota fans! I own this device for several months now and first time i used GPS couple weeks ago on my snowboarding holidays. I used the SKI+ app and through the whole week there was no single day when all my runs were tracked - either the speed or part of runs were missing so i blamed the application (though my good old HTC One X was behaving way better and gave better details when using exactly same app same amount of time).
So couple days ago i've installed Endomondo on my Yota 2 device. First and second day it tracked my bicycle run and walk okay but today during bicycle run GPS signal was lost several times. Then bit later i went for a walk (same route as a day before) and GPS signal was again lost several times and that makes me bit worried. Does any of you experience similar issues?

smekla said:
Hi there Yota fans! I own this device for several months now and first time i used GPS couple weeks ago on my snowboarding holidays. I used the SKI+ app and through the whole week there was no single day when all my runs were tracked - either the speed or part of runs were missing so i blamed the application (though my good old HTC One X was behaving way better and gave better details when using exactly same app same amount of time).
So couple days ago i've installed Endomondo on my Yota 2 device. First and second day it tracked my bicycle run and walk okay but today during bicycle run GPS signal was lost several times. Then bit later i went for a walk (same route as a day before) and GPS signal was again lost several times and that makes me bit worried. Does any of you experience similar issues?
Click to expand...
Click to collapse
I was having the same problem for a month now and I've tried so many solutions. Ultimately, I ended up factory resetting but the gps signal was still not working properly. After messing around with the mobile network APN settings it finally worked!
Try resetting yours to default or google your carrier's APN settings and enter them manually.

Good point! Have you noticed if using "Device Only" mode in the Location settings worked better than High Accuracy mode? Before reading your reply this morning i tried using the "Device Only" mode and it didn't lose the GPS signal.
Will try resetting the APN settings and use "High Accuracy" mode next time.

Your tip helped with GPS signal, I have manually set the APN and it didn't lose the GPS anymore. Thanks!
Sent from my YD201

GPS lose signal each 30 seconds for 30 secods: inusable!
Hi all,
unfortunately the work around that you have proposed (setting manually the APN or setting Positioning to "device only") seems useless to resolve the bug.
I'm using 5.0.0-EU1.1.124b.
Have anybody else discovered some solution? Further more I can't go to LTE but only in H+...
Thank youuuuu!!!

similar situation here after resetting to factory defaults
Hi, I have tried to follow the advice that I have read here in this thread and re-set to factory defaults. This, unfortunately, has not solved the problem. I think that the APN settings are not the crucial aspect here, as the GPS is dysfunctional even when I opt for using the GPS/GLONASS receiver alone, without the support of WiFi or 4G networks.
For what is worth, my feeling is that my Yota 2 loses (3G, 4G) signal more often that it should, based on where I am located and the availably of signal on other phones nearby and on the same carrier. I am unsure whether waiting for an Android fix, if that is the case, or sending the phone for service, but that would take a long time as I bought it online.
Cheers, Massimo
Android 5.0, patch 2016-09-05, kernel 3.4.0.g922ab0da-02044-.... of Wed, Oct 5
rociredef said:
Hi all,
unfortunately the work around that you have proposed (setting manually the APN or setting Positioning to "device only") seems useless to resolve the bug.
I'm using 5.0.0-EU1.1.124b.
Have anybody else discovered some solution? Further more I can't go to LTE but only in H+...
Thank youuuuu!!!
Click to expand...
Click to collapse

GPS lose signal resolved!
Hi guys,
I've resolved the issue by simply installing the last firmware available for Yotaphone2.
You have to install the last russian ROM (here there is a very usefull guide but it's in italian)
forum.hdblog.it/index.php?/topic/40292-yotaphone-2-official/?p=866997
Once installed the "5.0.0-RU1.1.124.zip" (as described) an update should start to install the ROM ".....1.1.134" which resolves the gps bug! Oh Yeah!
:good::good:

Can't resolve...
Hi to all,
I have a similar issue: for some weeks I tried the GPS without luck, but today, making a pic of the telephone because my vendor wanted one, the GPS magically worked. This was the first time I switched on the phone without the nano SIM. But... after I restarted again the phone without the SIM, it didn't show again the satellite status. Even after some other tries switching off or restarting the phone. I don't understand this crazy behaviour...
Can anyone help me?
PS: actually I'm using the last RU firmware.

I have the exact same issue and I have to be suspicious that it is the hardware.
Fortunately I own a GPS re-radiating aerial which is identical to this http://ebay.to/2iF9u15 and guess what, if I use this I get fantastic reception, but otherwise it is terrible. This is a good solution if you happen to have a power source nearby like a car.. these seem to also be quite expensive, although I got mine from Zopo in a flash sale for not much money.
Instead you can use an external bluetooth GPS. I have a couple of these from Holux - the 235 and 1000, both recommended - you can probably buy a second hand one really cheap.... and you also need a bluetooth GPS provider app..(and the app called exactly that is what I have used) Set mock locations 'on' in the developer menu and you're away. Only problem with this is that not all applications work with mock locations. The advantage of this is that you can put your BT GPS under your ski boarding hat and forget about it, while getting excellent reception.
As the GPS seems to be able to see the satellites, (just exceptionally poor signal strength), I have to believe that it could just be that it has a really bad physical aerial in the box, or it is not connected properly. Could still be the code though as the signal levels with the booster still look a bit low...

All of you did have problem with gps, can u write down radio/baseband version. Either it is RU or CN. Maybe related.
Thanks.

Hi, there, Yotaphone 2 friends!
I bring wonderful news, in case some of you hasn't update yet to Marshmallow: it is now possible to have your GPS/GLONASS working perfectly -- it even almost worked inside a 1km tunnel, berried in some 100/200m of granite!!
Unfortunately, I lost track of my claims, but I'll leve here the info, in case some of you want to research.
1. The Problem:
The GPS problem in Yotaphone 2 comes from Lollipop, not from the device, modem or firmware.... It happens that Lollipop tries to inject the AGPS data in a wrong format, which causes the GPS daemon to segfault -- and this affected other devices as well, which, BTW, have published a fix, different from our case with Yotaphone.
The bug happens every 5 minutes when you have the mobile data enabled. Meaning: every five minutes, your GPS connection is dropped, the GPS daemon process is restarted, a GPS lock has to be acquired... sometimes you don't have time to lock before another 5 minutes have passed and the GPS daemon is killed again; other times, you'll experience some time with a good GPS reception, until 5 minutes since the last drop gets by... you got it.
If you want to check these claims, put your phone in airplane mode or disable data and you'll see that you'll run GPS applications with no issues -- maybe you won't be able to run Waze this way, but...
2. The solution
A simple edit on /system/etc/gps.conf solves the issue.
To edit this file, however, you'll have to:
a) have your phone rooted;
b) mount /system in read-write mode, to be able to edit this file;
c) edit the file using the terminal and the editor called "vi" or by using another tool like "ES Explorer".
Remember two important things:
- I tested it only on Lollipop (I still didn't upgrade). I hope the bug is solved for Marshmallow and this fix isn't needed, however one might find some settings worth, specially the enabling of GLONASS reception.
- Please make a backup of your old gps.conf in case something goes wrong.
At the end of the post, I'll transcribe my whole gps.conf file, which has fixes for the mentioned bug and other improvements -- including a working GLONASS reception, which seems to have been ingnored in Lollipop (!?)
If someone wants to know how these kind of things happens in the software world, please bear in mind that the Yotaphone 2 engineers, who made a wonderful piece of hardware, probably did a hard work on testing their software the first time (on kitkat), but probably did not repeat their comprehensive quality assurance process and test cases for Lollipop or even Marshmallow. Who could have imagined google would provide a buggy release, after all?
No more talking, here goes my gps.conf file in the hope that it will be useful:
#Uncommenting these urls would only enable
#the power up auto injection and force injection(test case).
#XTRA_SERVER_1=http://xtrapath1.izatcloud.net/xtra2.bin
#XTRA_SERVER_2=http://xtrapath2.izatcloud.net/xtra2.bin
#XTRA_SERVER_3=http://xtrapath3.izatcloud.net/xtra2.bin
# the standard data servers
AGPS=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_1=http://xtra3.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra4.gpsonextra.net/xtra.bin
# enable the agps parsing
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_USER_PLANE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# we declare the quality we need
QOS_ACCURACY=50
QOS_TIME_OUT_AGPS=95
QOS_TIME_OUT_STANDALONE=80
QosVerticalThreshold=500
QosHorizontalThreshold=1000
# better and faster aGPS
AssistMethodType=1
AgpsUse=1
AgpsServerType=1
AgpsServerIp=3232235555
AgpsMtConf=0
AgpsMtResponseType=1
#Version check for XTRA
#DISABLE = 0
#AUTO = 1
#XTRA2 = 2
#XTRA3 = 3
XTRA_VERSION_CHECK=0
# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0
#Test before using any of those servers!
#NTP_SERVER=time.gpsonextra.net
# Brazil
NTP_SERVER=br.pool.ntp.org
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
# NTP_SERVER=north-america.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 = 2
# Intermediate position report, 1=enable, 0=disable
#INTERMEDIATE_POS=0
INTERMEDIATE_POS=1
# Below bit mask configures how GPS functionalities
# should be locked when user turns off GPS on Settings
# Set bit 0x1 if MO GPS functionalities are to be locked
# Set bit 0x2 if NI GPS functionalities are to be locked
# default - non is locked for backward compatibility
#GPS_LOCK = 0
# supl version 1.0
SUPL_VER=0x10000
# Emergency SUPL, 1=enable, 0=disable
SUPL_ES=1
#Choose PDN for Emergency SUPL
#1 - Use emergency PDN
#0 - Use regular SUPL PDN for Emergency SUPL
USE_EMERGENCY_PDN_FOR_EMERGENCY_SUPL=1
#SUPL_MODE is a bit mask set in config.xml per carrier by default.
#If it is uncommented here, this value will over write the value from
#config.xml.
#MSA=0X2
#MSB=0X1
#SUPL_MODE=
# 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
#CAPABILITIES=0x31
# the modem capabilities, using 3G,
# using Glonass via 3G,
# using standalone LG method
CAPABILITIES=0x37
LPP_PROFILE=0
A_GLONASS_POS_PROTOCOL_SELECT=0x2
LGE_GPS_POSITION_MODE=0
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000
ACCURACY_THRES=3000
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.host.com or IP
# SUPL_PORT=1234
# we replace the not working supl.google.com
# with the more geo-friendly nokia
SUPL_HOST=supl.nokia.com
SUPL_PORT=7275
SUPL_NO_SECURE_PORT=3425
SUPL_TLS_HOST=supl.nokia.com
SUPL_SECURE_PORT=7275
SUPL_TLS_CERT=/etc/SuplRootCert
REPORT_POSITION_USE_SUPL_REFLOC=1
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
# Bitmask of slots that are available
# for write/install to, where 1s indicate writable,
# and the default value is 0 where no slots
# are writable. For example, AGPS_CERT_WRITABLE_MASK
# of b1000001010 makes 3 slots available
# and the remaining 7 slots unwritable.
#AGPS_CERT_WRITABLE_MASK=0
####################################
# 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
################################
# EXTRA SETTINGS
################################
# NMEA provider (1=Modem Processor, 0=Application Processor)
NMEA_PROVIDER=1
# Mark if it is a SGLTE target (1=SGLTE, 0=nonSGLTE)
SGLTE_TARGET=0
#indoor
QUIPC_ENABLED=1
##################################################
# Select Positioning Protocol on A-GLONASS system
##################################################
# 0x1: RRC CPlane
# 0x2: RRLP UPlane
# 0x4: LLP Uplane
#A_GLONASS_POS_PROTOCOL_SELECT = 0
#general
PHONE_TYPE=UMTS
CURRENT_CARRIER=common

zertyz said:
- I tested it only on Lollipop (I still didn't upgrade). I hope the bug is solved for Marshmallow and this fix isn't needed, however one might find some settings worth, specially the enabling of GLONASS reception.
Click to expand...
Click to collapse
I upgraded my Yotaphone 2 YD206 to MM and was still having the known GPS issues.
So I modified the gps.com file and everything works great.
Thanks

zertyz said:
Hi, there, Yotaphone 2 friends!
I bring wonderful news, in case some of you hasn't update yet to Marshmallow: it is now possible to have your GPS/GLONASS working perfectly -- it even almost worked inside a 1km tunnel, berried in some 100/200m of granite!!
Unfortunately, I lost track of my claims, but I'll leve here the info, in case some of you want to research.
etc etc
Click to expand...
Click to collapse
I'm on Marshmallow 6.0.1 (Build MMB29M.6.0.1-RU1.1.47) but also here GPS is very troublesome.
Have had it working on Lollipop without any problems, but now it does give me serious problems.
Both TomTom Go and Navigon lock on me when navigating.
TomTom Go loses gps-fix every 5 mins or something, and gets a fix after a few minutes.
Navigon loses a fix waaay less than TomTom Go, but every now and then I get a red bar on top.
Just yesterday both did just lock on me, with no way to get it working again.
I think it has something to do with the AGPS data, is there a way to get a reset on that?
My Yotaphone is not rooted (yet!)
Instructions on doing that will be on XDA I guess ?

Baseband version for gps issue
My gps drops every few minutes when using google maps in my car.
The phone slows down very much as well.
Model #: YD201
Android version: 6.0.1
Baseband version: S01_003_4240_RU1_M05
Build #: MMB29M.6.0.1-RU1.1.47
dmix_shinri said:
All of you did have problem with gps, can u write down radio/baseband version. Either it is RU or CN. Maybe related.
Thanks.
Click to expand...
Click to collapse

My GPS issues resolution
Hi,
I was having long time issues with the GPS, and editing the gps.conf manually wasn't really solving them. I even jumped between android 5 and 6 and always ended up with the same problems.
I have the phone rooted and wasn't until a few days ago that I found this: https://github.com/Magisk-Modules-Repo/optmizedgpsconf
And the issues are no more
Cheers!

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.