Related
#WombatPhoneRoam.mscr
#
#Change Log:
# 0.8 Initial Beta Release
# 0.8.3 Improvements made to Dialup switching and Operator Logo Shown (Work still needs to be done)
# 0.8.4 Added routine to periodically try to scan for 3G operators when phone is in E and G network modes
# 0.8.5 Improved Switching of modes and scanning. Added removal of popup connection windows, Added Automatic repair of lockup of DUN
# 0.8.6 Rewrote parts of the script to streamline logic and improve speed. Improvements made to CPU usage
# 0.8.7 Added Debugging Option to turn off debugging and set variables to debugging settings
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL to
# https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#
#Wombat's PhoneRoam Version 0.8.7
# This Mort Script Came about as I am with "3" Network in Australia and this has Rediculous Hefty Data Charges when it roams on the
# Telstra Network (THREE Uses the Telstra network when Roaming).
# To Combat this I wrote this script to keep the Phone connected to Data to the 3G and HSDPA Modes wherever possible
# When it drops back to Telstra Network on Edge or GPRS it Disables Data usage
# It Should work with any network where you only have one 3G or HSDPA Carrier Available:
# NOTE: It will try to connect to any HIGH SPEED NETWORK AVAILBLE
#
# The script will set the mode to WCDMA (High Speed Data Only) when it CAN reach a High Speed Network to keep it from flip flopping between networks.
# When the WCDMA network is not available (No 3G or H available) it will switch to AUTO mode and allow the phone to Roam onto NON High Speed Networks.
# This is so that you can still make/recieve calls when you are not in a 3G or HSDPA coverage area.
# When High Speed is available again it will switch back a short time after the WCDMA network is again available. (Radio will turn off for short time)
#
# NOTE IT WILL NOT CHANGE MODES OR DISCONNECT WHEN YOU ARE MAKING A PHONE CALL!!!.
# IF THE CALL IS MADE OR RECEIVED While WCDMA ONLY IS ENABLED you may experience phone dropouts if in a fringe High Speed data area.
#
# Whenever it is on a network that DOES NOT provide 3G or H data speeds it will automatically kill the Data connection whenever it is attempted.
# It should do a good job to eliminate Roaming charges but there may still be some small charges due to delays when speeds are switched.
# This script works quite well but still has a few bugs due to the Dialup Networking in WM6 being quite flakey and is prone to locking up.
# NO GUARANTEES that it will not keep you from being charged for DATA on the lower speed networks BEWARE!!!!
#
# Disclaimer: I WILL NOT BE HELD RESPONSIBLE FOR ANY DATA USAGE OR COSTS INCURRED BY THE USE OF THIS SCRIPT OR ANY DAMAGE CAUSED!!!
# BEWARE THIS SCRIPT ATTEMPTS TO KEEP YOU CONNECTED TO THE INTERNET WHENEVER POSSIBLE. YOU ARE RESPONSIBLE FOR ALL DATA COSTS INCURED!!!
# USE AT YOUR OWN RISK!!! YOU HAVE BEEN WARNED!!! SEVERAL TIMES!!!
#
#
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL to
https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#
# Usage: YOU MUST INSTALL VJVolbilis first. You can get it from http://www.vijay555.com/?Releases:VJVolubilis
# It also requires Mortscript to be installed. You will need to set the variables below to point to the install folder
# Place this script in a directory on your WM6 device and create a shortcut in the Startup folder of your PDA
# or just place the script in your startup folder
#
# This will cause the phone to automatically connect to the internet whenever a 3G or H data service is available and stay disconnected
# whenever a G or E network is detected.
#
# The Operator Logo will change to the following
#
# e.g.When Connected to a highspeed network 3 I:HSDPA
# When Disconnected and Roaming Roaming D:Edge
#
# Operator Logo (Sometimes will show a Number which is the Signal Strength not sure why?) or U for Unknown at startup
# ?: = I=Connected, A=Available D=Disconnecting,F=Failure,S:Searching,
# The next shows the Data mode it is on or is available H=HSDPA, 3G=3G, E=Edge, G=GPRS (else it shows the Unknown mode value)
#
# You can create a Terminate Script like this below to kill the running script if you need to. (Included in Zip File)
# TerminateWombatPhoneRoam.mscr
Regards
Wombat
[Script] Wombat's PhoneRoam Script (Stay Connected to High Speed Networks Only)
This is BRILLIANT!! Thankyou so much, there should be some paypal dollars on the way for you mate. Kudos!
seems perfect for me, as I'm on three mobile. I have an HTC Touch HD running Windows Mobile 6.1
I installed VJVolbilis. Then I installed Mortscript. Next, I tried to run wombatphone script which I have on my sd card. Nothing happens. Do I need to do something first?
edit: just realised it is working on the today page. However, quite quickly I get a crash with VJVolbilis causing me to enter my pin again and essentially making my phone stuck
edit2: it appears to also cause scummvm and shell32 to crash (the former is strange as scummvm isn't running)
Just noticed that data still goes out even if roaming if I press 'update now'.
Thanks this is exactly what I needed - will install and see how it goes as I'm heading out to a Three non-service area next week.
Is it possible to get back the standard Operator Logo?
I am back from holidays today so I will look into some of the problems you have been getting.
There is some issues with VJVolbilis as it does sometimes locks up trying to kill the dialup session. Windows Dialup is rather unstable anyway.
Just noticed that data still goes out even if roaming if I press 'update now'.
Click to expand...
Click to collapse
It will still try to dial but it detects this and should kill the dialup session within a few seconds of it starting. I am looking at doing this a better way maybe with the NODATA program to disable the dialup session all together?
However, quite quickly I get a crash with VJVolbilis causing me to enter my pin again and essentially making my phone stuck
Click to expand...
Click to collapse
I too have seen this sometimes. I think it is caused if VJVolbilis runs twice and tries to dial at the same time another session is tring to dial. I have done some things to reduce this in this version but it is still there sometimes. I will look at what I can do to improve it.
Is it possible to get back the standard Operator Logo?
Click to expand...
Click to collapse
I will look at adding a menu system in the future that will allow you to set this Operator functions. I have enabled it in this version as it is a beta and I needed to get some feedback on how it is working so left it enabled. In the Meantime You can disable it by commenting out the following lines
Code:
# RegWriteString( "HKLM", "System\State\Phone", "Current Operator Name", WriterString )
Well I tested the script whilst in a non-roaming area (about 70km outside the CBD, I'm also on the Three network in South Australia) and it worked a treat. I was mainly concerned about Push Email which I use for work. I sent myself a test email and the phone did not receive it.
I did, however, get prompted to enter my username and password for Planet3 numerous times (assume this was whenever ActiveSync tried to access the Exchange server).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I was back with normal metro area, I knew was non-roaming as I had been checking the coverage to see when I went onto roaming, it did not reconnect to Three. I left it a while but still nothing. I had to eventually terminate the script.
I also am running across a problem with VJVolubilis - but this seems only to happen when I soft reset my phone.
I'm now at home which I know is within the Three HSPDA coverage area (as it was previously showing this). However, with the script running again, it's showing "T:OFF". When looking at my Network settings you can see in the top menu bar it's showing the standard HSPDA logo but I'm not sure what "T:OFF" refers to??
*edit*
On a side note I get no sound playing when I do receive an email with your script running.
squibly said:
I was mainly concerned about Push Email which I use for work. I sent myself a test email and the phone did not receive it.
Click to expand...
Click to collapse
I will try to work out how to turn on the push email when the data connection is up this should keep the data flowing. When you are in a Roaming State (i.e. in only an E or G area) you wont be able to recieve emails.
This is whole purpose of this script to stop you from getting charged heaps by Tel$tra when roaming. It should however reconnect once you are back in a Three Coverage area and allow you to receive your emails.
squibly said:
I did, however, get prompted to enter my username and password for Planet3 numerous times (assume this was whenever ActiveSync tried to access the Exchange server).
Click to expand...
Click to collapse
I too have seen this as well. Am working on a way to disable the connection altogether when roaming. This should stop the issue with the password prompt comming up.
I have found the registry keys I need to use I am just working on the logic.
I should have another version available in the next few days.
squibly said:
When I was back with normal metro area, I knew was non-roaming as I had been checking the coverage to see when I went onto roaming, it did not reconnect to Three. I left it a while but still nothing. I had to eventually terminate the script.
Click to expand...
Click to collapse
This I also know about. It is caused by the multple disconnections it needs to make to the connection whenever anything trys to connect to the internet. Hopefully the changes I have made to disable the connection altogether should rectify this.
squibly said:
I also am running across a problem with VJVolubilis - but this seems only to happen when I soft reset my phone.
Click to expand...
Click to collapse
Again this should be reduced in the next version.
squibly said:
it's showing "T:OFF". what does "T:OFF" refers to??
Click to expand...
Click to collapse
This refers to that it is connected but there is no data networks available. I think this may also be related to the crashing of Windows dialup. Hopefully I should have this reduced in the next version also.
squibly said:
*edit*
On a side note I get no sound playing when I do receive an email with your script running.
Click to expand...
Click to collapse
This one puzzles me. I am not using sound at all so there should not be any reason that the sound is effected by my script. I have not seen this as yet here and still get the email received sounds from my device. I will keep an eye out for it. let me know if you narrow down when if it occurs in the next version.
Hey just FYI: Three only uses the Telstra network when "Roaming". When you are in Three Mobile Broadband coverage, it's actually on Three's own infrastructure
WombatPhoneRoam Version 0.8.5 Beta
Released Version 0.8.5 Beta.
#WombatPhoneRoam.mscr
#
#Change Log:
# 0.8 Initial Beta Release
# 0.8.3 Improvements made to Dialup switching and Operator Logo Shown (Work still needs to be done)
# 0.8.4 Added routine to periodically try to scan for 3G operators when phone is in E and G network modes
# 0.8.5 Improved Switching of modes and scanning. Added removal of popup connection windows, Added Automatic repair of lockup of DUN
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL by going to following Address
#https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#Wombat's PhoneRoam Version 0.8.5
# This Mort Script Came about as I am with "3" Network in Australia and this has Rediculous Hefty Data Charges when it roams on the
# Telstra Network (THREE Uses the Telstra network when Roaming).
# To Combat this I wrote this script to keep the Phone connected to Data to the 3G and HSDPA Modes wherever possible
# When it drops back to Telstra Network on Edge or GPRS it Disables Data usage
# It Should work with any network where you only have one 3G or HSDPA Carrier Available:
# NOTE: It will try to connect to any HIGH SPEED NETWORK AVAILBLE
#
# The script will set the mode to WCDMA (High Speed Data Only) when it CAN reach a High Speed Network to keep it from flip flopping between networks.
# When the WCDMA network is not available (No 3G or H available) it will switch to AUTO mode and allow the phone to Roam onto NON High Speed Networks.
# This is so that you can still make/recieve calls when you are not in a 3G or HSDPA coverage area.
# When High Speed is available again it will switch back a short time after the WCDMA network is again available. (Radio will turn off for short time)
#
# NOTE IT WILL NOT CHANGE MODES OR DISCONNECT WHEN YOU ARE MAKING A PHONE CALL!!!.
# IF THE CALL IS MADE OR RECEIVED While WCDMA ONLY IS ENABLED you may experience phone dropouts if in a fringe High Speed data area.
#
# Whenever it is on a network that DOES NOT provide 3G or H data speeds it will automatically kill the Data connection whenever it is attempted.
# It should do a good job to eliminate Roaming charges but there may still be some small charges due to delays when speeds are switched.
# This script works quite well but still has a few bugs due to the Dialup Networking in WM6 being quite flakey and is prone to locking up.
# NO GUARANTEES that it will not keep you from being charged for DATA on the lower speed networks BEWARE!!!!
#
# Disclaimer: I WILL NOT BE HELD RESPONSIBLE FOR ANY DATA USAGE OR COSTS INCURRED BY THE USE OF THIS SCRIPT OR ANY DAMAGE CAUSED!!!
# BEWARE THIS SCRIPT ATTEMPTS TO KEEP YOU CONNECTED TO THE INTERNET WHENEVER POSSIBLE. YOU ARE RESPONSIBLE FOR ALL DATA COSTS INCURED!!!
# USE AT YOUR OWN RISK!!! YOU HAVE BEEN WARNED!!! SEVERAL TIMES!!!
#
#
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL by going to following address:
#https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#
# Usage: YOU MUST INSTALL VJVolbilis first. You can get it from http://www.vijay555.com/?Releases:VJVolubilis
# It also requires Mortscript to be installed. You will need to set the variables below to point to the install folder
# Place this script in a directory on your WM6 device and create a shortcut in the Startup folder of your PDA
# or just place the script in your startup folder
#
# This will cause the phone to automatically connect to the internet whenever a 3G or H data service is available and stay disconnected
# whenever a G or E network is detected.
#
# The Operator Logo will change to the following
#
# e.g.When Connected to a highspeed network 3 I:HSDPA
# When Disconnected and Roaming Roaming D:Edge
#
# Operator Logo (Sometimes will show a Number which is the Signal Strength not sure why?) or U for Unknown at startup
# ?: = I=Connected, A=Available D=Disconnecting,F=Failure,S:Searching,
# The next shows the Data mode it is on or is available H=HSDPA, 3G=3G, E=Edge, G=GPRS (else it shows the Unknown mode value)
#
Working great so far, also on Three in Oz. Thankyou! Will wait for my next bill and donate.
At risk of off-topic which radio do you use and what battery life do you get? I use the radio from the latest three rom update (but different rom) and my battery lasts the working day just about
cheers
Russ
bigruss said:
Working great so far, also on Three in Oz. Thankyou! Will wait for my next bill and donate.
At risk of off-topic which radio do you use and what battery life do you get? I use the radio from the latest three rom update (but different rom) and my battery lasts the working day just about
cheers
Russ
Click to expand...
Click to collapse
Hi Russ,
I use a Kaiser TYTN II on Three (Not originally a Three phone) running WM6.1
These phones chew power like no end and i'm lucky if it lasts the whole day. I have to charge it at home and at night. (and that's without using the GPS.) If I use the GPS or the wireless features it actually discharges faster than it charges especially with the GPS running.
As Mentioned in the read-me I cant guarantee that it wont have any roaming charges they just shouldn't be anywhere near what they would have been if you didn't run the script. Keep an eye on it because if the script stops running it may still connect to the lower speeds. I have limited testing abilities here to make it roam (pretty much the only place is the Restroom ) I have tried to think of as much as I can to prevent it but it is Windows so all bets are off!!!
Wombat
Hi All,
To alleviate some of your fears, I will give you my example of my roaning data usage.
The script has saved me heaps.
I will give you my example of my roaming data usage. I use roughly 100MB - 200MB of data most months on Three.
Last month it was $1.77 (around 1mb) of roaming charges last month (December) This was while I was writing the first version of the script and I had been trying to break the script and sometimes did
Many improvements have been made since then.
On the months that I did not have the script prior to this it usually cost me around $50 for the leakage data when it roamed. Then I learned that you can set the phone to stop lower speed data but the downside of this was that there was times that I did not have phone coverage (when out of three network there was no service). That's why I started to write this script.
I am still waiting for this months bill as I have been continuously testing my script (9th Feb) but I believe it still will be very low roaming data usage. Only time will tell and Im hoping for some good feedback from you all so that I can make this a success and save you some money $$$
Regards
Wombat
Sounds good, I got $100 of roaming data over the last few months. My work (UNSW Campus) has patchy reception so I am constantly in and out of 3's 3g network. So far your script is working beautifully when it roams onto Telstra, at least when I am watching or try to manually activesync for example when roaming.
btw I have a diamond, my previous phone was a kaiser and I think it had slightly better battery life than the diamond. Can't wait for the next leap forwards in battery technology, I too am tied to my charger!
Good stuff Russ.
Keep me posted on the performance you are getting.
I suspect that you may get some higher Battery usage by using the script. This is not so much from the script it will be due to the switching of bands/disconnecting etc and the fact that it is using 3G and HSDPA more often (uses more power for these data types). I have mine connected to Active Sync Exchange syncronisation across the net constantly and get quite a few emails over the day. So far i dont see too many issues with my battery life (other than usual this phone sucks the juice anyway)
I hope to hear from more of you on your experiences and improvements you would like to see in this script. Eventually I would like to make it into an APP.
Thanks to all of you for trying this script and hopefully It will save you money.
Regards
Wombat
Battery Usage
Hi Russ,
I am posting this PM here for all to see as it addresses some good points.
I really appreciate the feedback from you.
I have decided that it needs to be in the thread as you make some good points.
bigruss said:
Hey Wombat,
I sent this by PM because if this is a one off I don't want your script to be tarnished! Feel free to post this and reply into the thread if you would rather keep discussion there.
Click to expand...
Click to collapse
This is really helpful and something that I need from you all to make this a better application. whether it be good or bad. I hope that the people reading the comments wont be too put off by any criticism of the script and will keep in mind that it is still an early Beta version and is not yet finished by any means.
I need more of you to try it out and give me your feedback as this will help me to improve it and add the features that are most wanted and iron out any bugs that I am sure it will have some.
bigruss said:
It seems to be hammering my battery today, task manager (dotfred) shows mortscript processor use at 25-70% all the time! I am in a roaming zone with weak signal (basement).
Click to expand...
Click to collapse
I have not yet had the time to address battery usage properly. As my phone is a heavy usage device as it is I havent really noticed the extra usage of it. (or cared that much at this stage) I have been more concerned at the moment with getting it working properly than battery life. I will definitely look at it to see where I can improve on it in this next version I am writing at the moment. Are you able to try the suggestion below and let me know if the cause of the CPU usage is due to the network scan it does every 40 seconds when in roaming? if so this should be improved by setting it to 240 seconds or more.
I have installed this task manager on my phone now and I am looking at what is using the extra power. I suspect it may have allot to do with the new features that I added to keep the phone online whilst it was roaming.. I had changed quite a bit around in the latest version 0.8.5.
I am wondering if you are getting this same problem if you run the older version? 0.8? that may give me something to work off.
bigruss said:
Can I
1) run a script (don't know how to write) to run manually that will terminate your phoneroam script and deactivate the data connection. I could then use this when I am in the basement (no chance of 3g signal) and run your normal script when I am not? I could possibly automate this with phonealarm depending on cellid I guess.
Click to expand...
Click to collapse
Well hopefully you wont need to disable my script (thats my intention anyway) I just need to address the cpu usage for the next version.(see improvement below) Unfortunately with Windows Mobile it doesn't seem to be anyway to actually disable the auto dialing features easily. I am learning new things about it daily and have asked this same question on other forums on here but I have not gotten a answer on how to actually achieve it.
The NoData program seems to do this but I haven't yet worked out all of the things that need to be done to prevent it from connecting I am trying to avoid using third party programs if I can help it but had to succome to Vjvobilis as it was quite reliable at killing the connection. I am still working on this one I have added some things but still needs more work.
bigruss said:
2) adjust the frequency that this script runs at, maybe so it checks the connection status every 10 minutes, I would rather 'lose' ten minutes of possible 3g connection than have my battery go.
Click to expand...
Click to collapse
I have most of those variables built into the script already however I have them quite low at the moment so that I can test more thoroughly I will look at what I can do to improve this in the next version. This is possibly the reason you are getting such a high CPU usage.
I also will be adding a configuration menus into it later in order to allow tweaking of the settings but this may still be a little while off.
bigruss said:
The problem may be the weak signal, as I posted yesterday it seemed to be working great, then I was mostly in 3g reception and occasionally it would move to roaming. Or could be that I am roaming all day and it keeps searching every minute or so if there is a 3g connection available.
Click to expand...
Click to collapse
This definately appears to be where I may have not set the variables high enough. if you change the following variable in the script
Code:
;Number of seconds before it will check if WCDMA network is available
RescanTime=240
you can set the time it will wait to do a scan of the networks 240 will make it check every 4 minutes easy fixed.
As for putting the discussions in the main forum I probably prefer it as it keeps the thread near to top on the front page. This forum is very busy and threads get burried very quickly on here so the more comments we get in this thread the more people will see and use the script and comment on it and the better it will become.
So people give it a try and give me some feedback on what you like, Dislike or want improved. I will try to do what I can to help
hope This helped you Russ
cheers
Wombat
Will try you suggestion and let you know in the thread, though I may not be back into dodgy reception areas for a week or so. In the meantime I have been trying to use phonealarm, and it does deactivate the data connection quite nicely but it doesn't always switch to my 'roaming' profile when roaming and so I still get some data transfer. You could try phonealarm, backup the registry with the 'data connection active' (wincereg I think is the name of the registry software), change the data connection to inactive and backup the reg again then compare to see what the change did?
Just had a quick go. I am in good HSPDA reception area, the connection is staying active and there is no flipping to roaming at all. The 0.8 script gives me 8% mortscript CPU usage constantly, The 0.8.5 script gives me 40-50% mortscript CPU usage.
I usually disconnect the data connection after 1 minute inactive to save battery. Is there a way to allow this in the script? So the script is only called if an application attempts to make a data connection, then if there is 3g the connection is allowed but if there is only roaming then the connection is killed? Maybe then the script can just be called and doesn't have to run constantly?
btw I'm not daft but I am not a programmer either so forgive me for impossible/useless suggestions :-D
bigruss said:
Just had a quick go. I am in good HSPDA reception area, the connection is staying active and there is no flipping to roaming at all. The 0.8 script gives me 8% mortscript CPU usage constantly, The 0.8.5 script gives me 40-50% mortscript CPU usage.
I usually disconnect the data connection after 1 minute inactive to save battery. Is there a way to allow this in the script? So the script is only called if an application attempts to make a data connection, then if there is 3g the connection is allowed but if there is only roaming then the connection is killed? Maybe then the script can just be called and doesn't have to run constantly?
btw I'm not daft but I am not a programmer either so forgive me for impossible/useless suggestions :-D
Click to expand...
Click to collapse
I haven't looked at that as I need a nailed up connection most of the time I will look into this soon.
From your previous post I have determined where the issue is with the high CPU usage it seems that Mortscript has a tendency to hog cpu when doing checks for tasks and active window checking. I have improved it quite a bit by re-adding the sleep statement near the beginning of the script (under the first while statement) This brings it back to the 10% but it slows it down quite a lot and the timings are out. I will need to look further into this. I have my next version almost written and it will have a major rewrite of some of the routines. Once I have finished testing I will release it. If you want to improve the latest version uncomment the sleep statement under the while. That should reduce the CPU allot.
Code:
While (Initialized = 1)
Sleep (1000)
Hi wornbat,
Does this work only when we are in roaming..... can we make use of it when we are in home network.
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.
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.
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
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!