[APP][2.2+] Backitude - General info and discussion - Android Apps and Games

Greetings fellow developers and/or Android enthusiasts,
I wanted to take a moment to start a thread on for the Android application (2.2+) Backitude: Configurable Background Location Tracking. I would like a place to discuss the app publicly, discuss troubleshooting solutions, bugs, or motivate ideas and improvements.
Check out the Full version, ad-free available for free in the Android Market/Google Play store:
Download here: Backitude: Configurable Background Location Tracking
EDIT: Google Latitude shutdown their API on Aug 9, 2013 which completely changes the makeup of the application. Its sole purpose was to send locations to Google in order to maintain an accurate and timely history with Latitude. Now, it will be more geared towards keeping its own history and integrating with a number of systems or personal custom servers.
Backitude provides a bundle of extended features and functionality for updating Google Latitude locations from your Android device. If you are a Google Latitude user or once had interest in the concept of Google Latitude, then Backitude is an essential addon. Background gps location updating at your own specified time interval is now within your realm. Backitude expands your updating options, accuracy, and even allows you and your friends to force updates on eachother when needed, all seamlessly behind the scenes.
I created this app about a couple years ago to address two issues: I wanted to fix the short-comings of Google Latitude and make it a plausible application for users to enjoy and utilize effectively and efficiently. Also, I wanted to provide Google Play Store with such functionality free of charge. At the time, no such free application existed.
Google Latitude is somewhat inadequate on its own, but this is of no fault of the Google developers. They designed the application with battery efficiency as a number 1 priority. The conserve battery, Latitude on its own does not update locations in the background using GPS for accurate reporting. Instead it relies on Wi-Fi and cell tower triangulation to determine your location. Since many users refrain from enabling Wi-Fi when not stationary in their own network, or since Wi-Fi cannot be obtained while travelling, the resulting location updates are large, inaccurate "blue circles" on the map. Cycling through your Latitude friends, I mostly would see large, city-wide, inaccurate location readings- like I said, therefore truly defeating the purpose of Latitude. Latitude also fails to give the user any configurable options to location reporting. What good is a location history if majority of the values are city level and inaccurate? Backitude, to the rescue.
Backitude was designed to address all of this and put the power back into the hands of the user. You have complete control what, when, and how to update. Power can be a dangerous thing however. Google chose not to give the user a chance to configure their settings and risk draining batteries and having Android or Google products labelled as "battery drainers." Backitude is for the intelligent user, to know how to manage their battery, know their priorities, and know the effect of such functions. GPS polling is a very battery-intensive maneuver!
The final issue and gap Backitude inspired to bridge is updating a friend's location. It is great to have control over your location updates and allowing your friends to see exactly where you are, but what if they haven't updated recently or exactly when you needed to know their location? Backitude has an answer for that. "Fire an Update on a Friend" is the newest feature which utilizes SMS messaging to receive requests from other Backitude users. If your friend is also using Backitude and has this option enabled, you can send a request to their device which will in turn trigger an update at that very moment.
Additionally, there are many, many more features that all serve to give the user complete control of Latitude updates and battery consumption (in the context of Latitude updating). Thank you for checking it out, and I look forward to supplying any troubleshooting information right here for all to find, and hear ideas and feedback from those other enthusiasts out there.

Troubleshooting Topics
Location Updating using Backitude: the application utilizes oAuth2 authentication which is very easy and very convenient for the user. The user is able to grant permission for Backitude to integrate with their Google Latitude account at a click of a button without even having to enter their credentials.
The issue is, some users on some devices have experienced trouble obtaining this permission. It is important that users do one of the following before using Backitude, however, for some users it is required that they do both:
1) Use the Maps application to "activate Latitude for this device" by signing into Latitude. (Additionally, it is suggested that the user change their Latitude location reporting to "set your location". By manually updating your location and selecting an arbitrary position, you will prevent Latitude from wasting unnecessary battery life on updating your location, but still allow your friends to see your location. Backitude can do all your updates for you instead.)
2) From a PC or computer, visit Google Latitude and sign in from your browser. (And not from a tablet or smartphone browser) I do not know why this is required, but for some, to fully opt into the Google Latitude agreement and conditions, this is required.
After doing so, 99% of users are able to update using Backitude. An extreme minority, still have to perform some additional steps. This would include resetting your Google 3rd party authorizing sites, by revoking access from all, and then trying the process over from start. Signing into Maps. Activating Latitude. Installing Backitude..etc Any issues, I am always available via forum or email. Thanks!!

I just started using this app a few days ago after realizing how often Google Maps is polling for location information just to update latitude... Hundreds of times a day, even when I'm not moving!
So far, I'm liking what this app has to offer

Troubleshooting Topics: Location Updating using Backitude
If all else fails to get you updating, the following detailed description may help get you going as a last resort. Again, I'm not sure why oAuth2 can be so difficult for a small handful, and so convenient for so many others.
Start fresh by trying the following steps to reset your Google Latitude permissions
* From your android device, launch the Maps > Latitude application and Sign out. On the latest version, this is accomplished by going to Latitude > Menu > Location settings > Location reporting > Latitude location sharing > Sign out of Latitude
* Next, go into Android > Settings > Applications > Manage Applications > Maps and click the "Clear data" button.
* Similarly, uninstall the Backitude application by completing the following: Android > Settings > Applications > Manage Applications > Backitude and click the "Uninstall" button.
Now, follow these steps from a PC browser to remove access (so that we can then add them back)
* Visit google.com
* Sign into Google using the account you are trying to configure for Backitude
* Go to Google Account settings, or click "Account". (I will post a link directly there when I have the ability too)
* Scrolling down, you see the option to "Visit the previous version of the Account settings screen" which takes you to My Account.
* Under Security, select the link for "Authorizing applications & sites" (accounts.google.com/b/0/IssuedAuthSubTokens)
* Revoke access to any applicable "Android Login Service" entry including those such as "Full Account Access" and "Google Latitude"
Everything is now successfully reset, so perform the following steps in order.
* Sign into Latitude from a PC browser. (It is very important to sign in from a PC browser and not your android device at first). This is required by some devices for authentication purposes, to "opt" your Google account user into Latitude.
* Enable Google Latitude on your device using the Latitude app. If multiple accounts exist on your device, you may have to select the appropriate account by going to Maps > Menu > Settings > Switch Account. Then, or otherwise, sign-in to Latitude from your android device.
* Finally, you can try to re-install Backitude and successfully update your location to Google Latitude.
And that always seems to get the last 0.01% of users updating successfully who couldn't before. Annoying, yes!
Other similar 3rd party Latitude apps appear to be using a variant of oAuth1 authentication, which requires entering your password. I have contemplated implementing the same, to avoid this issue but perhaps future versions of Maps and Android will better activate permissions on those devices.

Backitude: My settings
How do I configure Backitude to run? Personally, with battery efficiency in mind while leaving the highest priority features enabled.
Enable Service: on (this is essentially the on/off switch)
Advanced Settings
Set Priority: Wi-Fi, with GPS/Tower Triangulation backup (One of the most overlooked but favorite options. This setting will abort GPS polling if a Wi-Fi network is present and the Wi-Fi location is accurate. So, in a real-life situation, my phone is indoors at work or at home with Wi-Fi enabled. GPS is enabled but not going to be able to get a fix indoors. Instead of polling for the entire extent of the Polling Timeout, Backitude will abort polling, and update using the Wi-Fi location value, which is all it ever would've gotten anyways. Beyond that, if I am outdoors and away from a Wi-Fi network with the same setup, the GPS will still poll and run its course as normal.)
Settings
Time Interval Option: 30 minutes (if my friends need a more recent update, they can ping me and have backitude fire off an automatic update seamlessly in the background)
Location Polling Timeout: 15 seconds (The longer GPS is allowed to run, the more potential battery gets burned if you can't acquire an easy fix)
Latitude Re-Sync Rate: off (this feature is only needed to prevent Latitude from overwriting your Backitude location update. However, I put my Latitude location reporting to manual so Latitude is no longer detecting my location. Battery saver too!)
Min. Change in Distance: off (I'm not a Location History keeper, so eliminating repeat updates is not a concern for me)
Location Steals: On (This is one of my favorite features. If you're using an app such as Maps, Navigator, or even the Internet, which polls your GPS, Backitude will steal this location and use it to update your location. The battery-intense function is already on-going thru another app, you might as well steal the location value and update your Latitude at very little expense.)
Accurate Update Only: On (You have to think about location "circles" for this option. Circles coming from inaccurate location readings. If your previous location value was more accurate then the current location reading, and the previous location is within the location perimeter of the newest location, it will repeat the more accurate location.
Real-time Enabled: Off (This is for individuals wanting to update at a faster rate when charging their device or docked. Personally, I just change my update interval when I want to update faster)
Real-time Interval: n/a (Users tend to want to poll location and update at a faster rate when their device is docked and battery is no longer a concern)
Real-time Timeout: n/a (When real-time updating, there is a separate timeout value for GPS polling versus the normal timeout. Users may have a different preference if their device is docked so there is a separation configuration for that)
Push Enabled: On (Allow friends to force an update to Latitude on my device by simply texting "Force Backitude update". I can get away polling at a slower rate and save battery because all my friends and fellow Backitude users know they can force an update on me when needed)
Display Message: off
Display Push Notif: off
Status Bar Icon: never
Display Update Message: off
Display Update Failed Notification: off

EP2008 said:
I just started using this app a few days ago after realizing how often Google Maps is polling for location information just to update latitude... Hundreds of times a day, even when I'm not moving!
So far, I'm liking what this app has to offer
Click to expand...
Click to collapse
Thanks. I'm currently working on fixing a couple known issues, and hoping to get a new release out this week. Nothing earth shattering though. I noticed you were running ICS... have you noticed any issues? I have not tested ICS compatibility yet, so I was always curious. Using a Bionic myself, I'm still hoping to get an update later this year and try it out myself. Thanks!

backitude said:
Thanks. I'm currently working on fixing a couple known issues, and hoping to get a new release out this week. Nothing earth shattering though. I noticed you were running ICS... have you noticed any issues? I have not tested ICS compatibility yet, so I was always curious. Using a Bionic myself, I'm still hoping to get an update later this year and try it out myself. Thanks!
Click to expand...
Click to collapse
No issues that I've seen.
I did have a bit of frustration when testing it as I had it set not to update unless my location changed more than 100m, so when I fired a manual update, I assumed that would force an update regardless of the location setting. It wasn't until after I turned that setting off did the manual update refresh with a new location timestamp.
Not a huge issue, but for some time I didn't think that the app was working because the timestamp on the history log never changed after manual updates.
Sent from my Galaxy Nexus using Tapatalk 2

EP2008 said:
I assumed that would force an update regardless of the location setting.
Click to expand...
Click to collapse
I never thought of that. That is probably a fair assumption. I may have to consider re-working that logic, so that like you said- if "Fire Update" is launched, you do not consider skipping the update because of minimum distance rules. Thanks!

backitude said:
I never thought of that. That is probably a fair assumption. I may have to consider re-working that logic, so that like you said- if "Fire Update" is launched, you do not consider skipping the update because of minimum distance rules. Thanks!
Click to expand...
Click to collapse
The reason I made the assumption was because I use an app called FolderSync, which helps manage cloud file storage services. With it, you can setup rules to sync your files, like what time a backup should be made, if you are plugged into a charger and if you are on wifi, etc. The app has an option for the user to initiate a manual sync, which basically ignores all scheduling rules over the users desire to sync right now. That's why I thought it might be the same for Backitude.

EP2008 said:
...The app has an option for the user to initiate a manual sync, which basically ignores all scheduling rules over the users desire to sync right now. That's why I thought it might be the same for Backitude.
Click to expand...
Click to collapse
I like the idea. I am going to change that for the next release. The settings for Backitude are pretty intimidating, even for novice Latitude users. I want to make it as user-friendly and straight forward as possible. Thanks for the help!

Still no way to see other people on Latitude? I'm sure it must be an API you don't have access to or something of that nature, but I still don't get the point of this app if it's "write-only". You can't see anyone, only they can see you.

You're correct in that the API is very limited. It only allows you access to your own location and location history, so there is no way to retreive your friends' locations, or even your list of friends. The purpose of Backitude is not to replace Google Latitude, but simply help correct its short-comings. Using backitude, and having your friends use backitude, ensures accurate locations, battery efficiency, and a means to update your friends' locations when you need their location. Once configured, Backitude runs in the background and can remain fairly transparent to your day to day Latitude use.

I'm using your app too in ICS 4.0.4 if you need some feedback. It's working quite well, even better than the other one! Keep the good work.

(Currently testing 2.7) Here is the change log, let me know if there's any more bugs I need to iron out last minute. Thanks!
Backitude: Update release 2.7 Changelog
1. Reported Issue: Backitude just stops running after a couple hours of use. (Unconfirmed but occasionally reported bug) I haven't been able to duplicate, however this could be the result of Android's memory management as an operating system, or the result of a Task Manager, task killer type of process. Users who experience such an issue should add Backitude to the ignore list on their task managers. However, I have made some changes in the code that may help.
2. Enhancement: For IOException, SocketTimeoutException, Read timed out, Unresolved host name. Backitude now has a re-attempt feature that will retry update after 60 seconds from a failed update due to these network congestion exceptions. (As directed to do by Google)
3. Enhancement: Implemented notification for users who cannot update due to permissions problem. (403/503 exception) Instructing user to first login to Google Latitude from a PC browser to "opt user into Google Latitude" and/or reset their Latitude location manually again. Google sometimes implements new terms and conditions and it may be required to re-opt into their agreement.
4. Enhancement: Updated Java Client libraries and Google Latitude libraries. I am hoping this shows improvements with efficiency, speed, memory, and issues.
5. Issue: (GUI) Steals option is not disabling if the Time Interval is under 5minutes. Likewise, it should then enable if the Time Interval is switch to greater than 1minute, similar to the behavior of the Re-Sync Rate option.
6. Reported Issue:*Wifi turns off after an update when Wifi Wake lock is enabled. Backitude now checks to see if Wi-Fi is connected (and therefore not sleeping) before acquiring a Wi-Fi wake lock.
7.* Change: "Fire Update" does not update location if minimum required distance is configured and new location is not outside of the bounds of previous location. Fire Update, since it is a manual update, has been changed to not consider the minimum distance configuration and bypass this validation.
8. Issue: Steals and manual updates (Fire Update) are not resetting the Time Interval clock after a successful update. This issue has been resolved.
9. Issue: Minimum distance calculation not taking into consideration changes in accuracy. If accuracy changes greatly from one location poll to the next, the location centers could be drastically far apart although the device has not moved. Offsetting the accuracy changes will result in better results for calculating change in distance.
10. Change: Push Update notification labels have been updated.

Well thats a nice application. Just starting to use it.
I have a suggestion. As my phone goes at night in a kind of sleeping mode - Wifi off, 3G off, Wifi Off, etc. - i would like to have a function to disable Backitude for certain hours or much better a Tasker Plugin.
What do you think ?

Thomas_BA said:
Well thats a nice application. Just starting to use it.
I have a suggestion. As my phone goes at night in a kind of sleeping mode - Wifi off, 3G off, Wifi Off, etc. - i would like to have a function to disable Backitude for certain hours or much better a Tasker Plugin.
What do you think ?
Click to expand...
Click to collapse
Thanks, glad you like it so far!!! It's funny you mention that because I have two main goals for the summer. Tasker integration and off-line storage/sync. I looked into Tasker once before over the winter and it turned out to be a lot more work then expected so I put it off, as this is just sort of a hobby in my free time. But with baseball season upon us, I do a lot of coding with the games on. Go Sox!
In the mean time, there is a setting for wake locks in Advanced Settings for Backitude. You can turn disable the wake locks and Backitude will not run once your phone goes into sleep mode. This means that the gps will not run while sleeping..etc Hope this helps

Nice to read hat you planning a Tasker integration/plug-in.
Yes for the time being i have disabled both wake locks. Disadvantage is that my phone sleeps a lot . I have my display timeout set to 1 minute, so sometimes my phone is sleeping for an hour while walking around in Buenos Aires or Argentina. Anyway for now this is the only solution. Looking forward to your next developments.
Thanks.

Thomas_BA said:
Yes for the time being i have disabled both wake locks. Disadvantage is that my phone sleeps a lot . I have my display timeout set to 1 minute, so sometimes my phone is sleeping for an hour while walking around in Buenos Aires or Argentina.
Click to expand...
Click to collapse
Actually, it shouldn't be that bad. Backitude will only cease functioning without wake locks once the device goes into a "deep sleep mode." I am not sure about the specifics of when this occurs, but it's separate then just display timeout. Can even take up to an hour or more from what I read, so as long as you're using it every hour or so, it should continue functioning. Please post your findings though, I am intrigued now.

I will observe the pushing frequency to Latitude and keep you informed.

I've been using Backitude for a few months now.
However, even with WiFi Wake Lock enabled, it seems the accuracy of my updates does not improve. However, when I open google maps with WiFi already on, the accuracy is few meters (I work and live in a dense WiFi area).
Do you think that Backitude for some reason is not turning on the WiFi, or is WiFi based localisation not being picked up by latitude?
Thanks for a great app!

Related

GPS Settings: Performance Options (improvement)

Ok, There are a lot of posts and information regarding the GPS issue that some are experiencing. I am starting (yet) another post in the interest of compiling and maintaining information regarding that information in one location. As users/devs find out information I will update this post so everyone doesn't have to go looking everywhere for the information. I am hoping that the Moderator will sticky this post.
Some users are experiencing very long lock times for their GPS. Everyone, after reading A LOT of posts/threads it seems to be the consensus that this is a software/settings issue - NOT, a hardware issue. However, results from tweaking the following settings are very mixed. Most seem to get great results by tweaking the following settings while stationary - but, moving is a whole different ball game. I use the below settings and have great results while stationary. However, my G1 blows the Captivate completely out of the water!!! My G1 gave 3-10m accuracy while driving. This device can barely keep me on the correct highway and always seem lagging behind my current location. The G1 was spot on no matter what. What hasn't been determined is if these issues are hardware or software. For whatever my opinion is worth - I think it is a firmware/software issue. Here are some things to try.
Here is the info:
To get to your GPS settings open you dialer and dial the following number. This will not call anyone - it is a code shortcut to the settings:
*#*#1472365#*#*
Once entered you will observe a screen that has five buttons:
Get Position Test
Application Settings
SUPL/CP Settings
Test Application
Delete GPS Data
We will be interested in three of these initial buttons.
Get Position Test: This will be what one uses to test the results of your changes.
Application Settings: Exactly what it says.
SUPL/CP Settings: settings that determine specific data connectivity with the satellites.
In Application Settings the following are some that you might consider adjusting:
Operation Mode - Standalone, MS Based, MS assisted, Network Provider
Accuracy - defaults to 50. Don't set it below 10 (and only use increments of 10's)
SkyHook - not sure what it does. But, someone on a thread mentioned it and it DOES effect satellite lock times.
In SUPL/CP Settings one we'll be interested in the following:
Server FQDN Type
Server
Server Port
The following are the options provided on other threads:
Original/Stock Settings:
SUPL/CP Settings/SErver FQDN Type/Custom Config
Application settings/Operation Mode/Standalone
SUPL/CP Settings/Server/www.spirent-lcs.com
SUPL/CP Settings/Port/7275
Second suggested setup (from other posts and claimed to have great results):
SUPL/CP Settings/SErver FQDN Type/Custom Config
Application settings/Operation Mode/MS Based
SUPL/CP Settings/Server/supl.google.com
SUPL/CP Settings/Port/7276
Other settings that I have played with:
Application settings/SkyHook/On (and Off)
SUPL/CP Settings/SErver FQDN Type/Auto Config (and Custom Config)
You can play around with these to see what gives you the best results. If your GPS doesn't work better with whatever changes you made - than you can always put it back to the orginal settings above.
However, it has been recommended and I concur (for whatever that is worth) that you NEED TO SET THE FOLLOWING BEFORE YOU START PLAYING AROUND: Settings/Location and security/uncheck (turn off) "Use Wireless Networks). Most likely this won't really effect anything while your testing within the GPS settings - however, this will effect your results if you test using Google Maps, etc.
Now, having duly noted all of the above and having played around with the settings for several hours I found the best results FOR MY DEVICE IN MY AREA AT ONE LOCATION was the following:
Note: I adjusted these settings from earlier as the earlier settings proved to be very accurate when stationary - but, very inaccurate while moving. The latest settings I'm using are below. Also, look to the bottom of this post regarding changing your gps configuration file. That also helped A LOT. The bottom section of information is from the Official websites that run the time servers(effects GPS performance).
Application Settings/Operation Mode/MS Based
Application Settings/Operation Mode/SkyHook/ON (VERY IMPORTANT)
SUPL/CP Settings/Server FQDN Type/Custom Config
SUPL/CP Settings/Server/supl.google.com
SUPL/CP Settings/Server Port/7276
SUPL/CP Settings/SUPL Secure Socket/Off
Turning "SkyHook" ON assisted in faster locks with ALL of my tested settings when stationary!
My test results with the above would lock on up to three satellites in under four seconds and between 7 and 10 by eight seconds. Google Maps would locate me in about 6-8 seconds.
Using "Get Position Test" the settings in the three lines above consistently gave the not only the fastest locks and the most locks - but, also STRONGER SIGNALS!
I used at least seven different combinations of the above settings and some of them were just as quick - but, not as strong. Most of them were slower.
If anyone has better information to add then please PM me and I will add it to this top post.
LASTLY, I will make some guesses as to what some of the other settings do as I have heard different information:
Application Settings:
Session Type: Tracking or Singleshot - obvious (use Tracking)
Start Mode: Hot or Cold Start - someone posted on a thread that Hot uses data from your last read to get started. Cold start will start all over. So, Cold start SHOULD increase the time for you to get a lock unless you went left the area to an area that had different satellite to look up.
Test Application:
Performance Test: worked for me - but, I found the test above to work faster and give me quicker results for what I wanted.
Hardware Test/Sensitivity Test: Pretty cool - went on forever and I stopped it.
CNO Test: Seemed to test the average satellite signal strength.
Antenna Test: Never worked for me and I received errors.
H/W Test Settings: Settings for the above tests - I didn't mess with them.
NOTE: WANT TO SEE HOW ACCURATE YOUR ACCELEROMETER/COMPASS/ORIENTATION settings are? Check this out:
Test Application/Show Sensor Data - there is no way to calibrate it here... But, you can see just how sensitive your instruments are!!
Delete GPS Data - I didn't select this button and I don't recommend anyone else doing so either unless someone from Samsung tells us what it does. LOL!
FINALLY: Keep in mind that if you are seeing GPS lock times that are in the 3-8 second range (which was what I was getting) this WILL NOT be how long it takes for Google Maps to get the GPS data! Expect 8-15 seconds or a little longer (but, under 30 seconds) for Google Maps to pick up your location. Although the GPS sensors might pick up the satellites - you still have to give the software time to evaluate the data and apply it to the software.
Hope this helps someone out there.
Update/Additional Information (http://androidforums.com/1194187-post197.html):
Hot Start - The GPS receiver remembers its last calculated position and which satellites were in view, the almanac used, and the UTC Time. It then performs a reset and attempts to acquire satellites and calculate a new position based upon the previous information. This is the quickest re-acquisition of a GPS lock.
Cold Start - The GPS receiver dumps all information and resets. It then attempts to locate satellites and then calculate a GPS lock. This takes the longest because there is no known information. The GPS receiver has to attempt to lock a satellite signal from all of the satellites, basically like polling, which takes a lot longer than knowing which satellites to look for. This re-acquisition of a GPS lock takes the longest.
Thanks to Shadow77895 for the link to this info. I altered the settings above. Doesn't effect my results much at all.
MSBased Operation Mode(http://www.vzwdevelopers.com/aims/public/menu/lbs/LBSFAQ.jsp#GenQues11):
What is MS-Based mode of operation?
In MS-Based mode, the network provides the satellite information to the device, based on a rough estimate of where the device is located, and the device acquires the GPS signals from the satellites and calculates its location. After the initial fix, the device operates like an autonomous GPS receiver, until the satellite information must be refreshed, at which time the device goes back to the network to update the satellite information. MS-Based mode is appropriate for applications that require the device location to be updated rapidly, such as a navigation application.
And email thread regarding using the Google settings for GPS(http://osdir.com/ml/android-platform/2009-08/msg00386.html)
NEW INFORMATION!!!
ALSO! Check out this page: http://www.pool.ntp.org/en/use.html:
As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone might not exist for your country, or might contain only one or two timeservers. If you know timeservers that are really close to you (measured by network distance, with traceroute or ping), time probably will be even better.
Find your optimal pool server here: http://www.pool.ntp.org/zone/north-america
For US the optimal server is: us.pool.ntp.org
Reference other threads I (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=731462) I recommend you do the following:
Use Root Explorer or some other method (I use Root Explorer as it has a built in Text Editor and automatically backs up the altered file.) to go to here:
system/etc/gps.conf
Use the text editor to alter the gps.conf file to this (if you are in the US):
NTP_SERVER=us.pool.ntp.org
XTRA_SERVER_1=north-america.pool.ntp.org
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
If you are NOT in the US go to here: http://www.pool.ntp.org/en/use.html and look at the links in the center of the page to navigate to the closest pool to your geographical location and use that pool for the top server entry.
REQUEST FOR ADDITIONAL INFORMATION:
Many are suggesting that we do NOT leave the Secure Socket ON. How will this effect data security with our devices? I don't understand how it could hurt us... But, there must be a reason for it. If someone could let me know I would appreciate it.
Good, guide, think you meant hot start should be faster though.
I'll be linking to this.
Sent from my Samsung Captivate using XDA app
Great, but doesn't address the problem
I need to point out that while this information is helpful it doesn't really address the problem that the GPS is facing.
What the above settings are doing is enabling multiple different A-GPS technologies to help compensate for the Galaxy S's poor GPS performance. A properly functioning GPS unit would not need these crutches except to acquire a faster fix.
I had my GPS outdoors today, with the first set of recommended settings, and was unable to achieve a fix while seven satellites were in view (according to it) with sufficient signal strength. This is a GPS firmware issue!
The above post is very helpful for people to get some better performance - however - the core GPS issues need to be addressed by Samsung.
I hope people will refrain from saying "It's perfect now!" and let up on Samsung. Unless you know what what the following are you're tweaking settings blindly and declaring victory: ephemeris, PDOP, SBAS, WGS-84, 2D fix, 3D fix (And the conditions one is chosen over the other.) and finally SA
I'm betting this phone would never achieve a fix in an SA environment! It's also clear that the person(s) who originated this information knew exactly what they were doing..!
If anyone is interested in learning how GPS works there are tons of great resources on the web that Google will point you to. Of course they're written for all sorts of different levels.
In short, the above settings may help, but please don't become convinced that things are "fixed"!
I'd suggest you read my posts on the subject:
http://forum.xda-developers.com/showthread.php?p=7244888#post7244888
http://forum.xda-developers.com/showthread.php?p=7289539#post7289539
@haydonxda - I agree that this does NOT address the potential problem that the firmware and/or hardware is inadequate! And, we should put pressure on Samsung to fix this issue. However, the phones have already been produced and I'm just trying to do the best with I have.
@Shadow77895 - thanks for the info. Added a bunch of further information after looking into your posts and references from them.
Try this fix (from 4pda.ru), working on Galaxy S, root access required:
$su
#cat /data/gps/secgps.conf > /sdcard/secgps.conf
#rm /data/gps/secgps.conf
#reboot
After reboot, new (correct) secgps.conf appears.
At your own risk!
shaneaus said:
NEW INFORMATION!!!
ALSO! Check out this page: http://www.pool.ntp.org/en/use.html:
As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone might not exist for your country, or might contain only one or two timeservers. If you know timeservers that are really close to you (measured by network distance, with traceroute or ping), time probably will be even better.
Find your optimal pool server here: http://www.pool.ntp.org/zone/north-america
For US the optimal server is: us.pool.ntp.org
Reference other threads I (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=731462) I recommend you do the following:
Use Root Explorer or some other method (I use Root Explorer as it has a built in Text Editor and automatically backs up the altered file.) to go to here:
system/etc/gps.conf
Use the text editor to alter the gps.conf file to this (if you are in the US):
NTP_SERVER=us.pool.ntp.org
XTRA_SERVER_1=north-america.pool.ntp.org
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
If you are NOT in the US go to here: http://www.pool.ntp.org/en/use.html and look at the links in the center of the page to navigate to the closest pool to your geographical location and use that pool for the top server entry.
Click to expand...
Click to collapse
How do you use the text editor in Root Explorer. I can see the text but it won't allow me to edit it.
Hello, the code:
*#*#1472365#*#*
starts a GPS Test Application.
The settings inside this application are only for this application.
You can test your GPS in different modes.
But the settings are not relevant for other applications.
It is a simple illusion that it helps to manipulate this settings.
GPS is very time-dependent.
And:
I don't know where we can change the default GPS Mode/s...
So when I walk outside my office there are like 7 satellites, and I still cannot get a lock. This is sad.
Out of the box it worked great, navigated from BB to my house with relative ease. Inside my house when I showed my parents it worked great. I rooted and deleted some ATT apps. I have yet to get a lock.
I have also changed the NTP servers and no dice. This is pretty saddening performance.
I still don't get why my Nexus One, sitting right next to my Samsung Captivate, is able to get a aGPS location (via My Location in maps) that is pretty damn accurate despite not having a GPS lock and my Captivate is unable to even get an aGPS location and just says my location data is temporarily unavailable.
Nexus One: Can get approximate location very easily
Samsung Captivate: Cannot even get approximate location using WIFI/Cell Towers.
Foursquare never knows where I am until I go outside in the middle of a parking lot. This is BS.
Won't anyone try GPS NMEA MONITOR App and see if the data sentences are correct? If the GPS chipset is putting out the correct Lat/Lon, then you can fiddle and fiddle what Captivate does with the information
Has anyone tried to contact Samsung about the issue yet? I tried yesterday and was on hold for an hour and half and then my call dropped. I'm joint to try again today.
SkyHook isn't a "feature" persay, it's a corporation: http://www.skyhookwireless.com/
Same one Apple uses. Not sure exactly how it works but they do wardrive and use WiFi and triangulation to pick up your position as well, so leaving that OFF will perhaps be better for calibrating your GPS settings, but you certainly want it back ON when in normal use.
TexUs said:
SkyHook isn't a "feature" persay, it's a corporation: http://www.skyhookwireless.com/
Same one Apple uses. Not sure exactly how it works but they do wardrive and use WiFi and triangulation to pick up your position as well, so leaving that OFF will perhaps be better for calibrating your GPS settings, but you certainly want it back ON when in normal use.
Click to expand...
Click to collapse
What kind of aGPS does the Nexus One use? I tried to dial the code and it didn't bring up the same menu on the Nexus (it may be different). My Nexus is great at figuring out where I am without a GPS signal.
I changed all my settings last night and it seemed to fix the issue. I was getting a lock within 10 seconds or less. Now I cannot get a lock with the exact same settings and reboot. Has anyone contacted Samsung over this? Anyone get an answer from them? I love this phone but the GPS issue sucks.
Every time I try one of these new fixes it seems to work but then when I go somewher else it is broken again they need to fix this asap. I use that feature a lot
superscientific said:
I changed all my settings last night and it seemed to fix the issue. I was getting a lock within 10 seconds or less. Now I cannot get a lock with the exact same settings and reboot. Has anyone contacted Samsung over this? Anyone get an answer from them? I love this phone but the GPS issue sucks.
Click to expand...
Click to collapse
I just got off the phone with Samsung galaxy s support. They knew nothing!!!!!! Said I was the first one to call with the issue.
I'm thinking about returning the phone... GPS is the most important part of a smartphone to me... I'm very disappointed
Jreitnauer7 said:
I just got off the phone with Samsung galaxy s support. They knew nothing!!!!!! Said I was the first one to call with the issue.
I'm thinking about returning the phone... GPS is the most important part of a smartphone to me... I'm very disappointed
Click to expand...
Click to collapse
I don't know about most important but I agree, it's very important. This HAS to be fixed
Jreitnauer7 said:
I just got off the phone with Samsung galaxy s support. They knew nothing!!!!!! Said I was the first one to call with the issue.
I'm thinking about returning the phone... GPS is the most important part of a smartphone to me... I'm very disappointed
Click to expand...
Click to collapse
Don't give up hope, i'm sure that guy doesnt know anything. Engadget and a few sites are aware of the issue and i'm sure Samsung took notice. i'm sure a firmware fix is in the works.
Location
I have tried all the settings. And I don't really notice any difference. I live in the heart of Manhattan, NY., so I am sure roaming around int he concrete jungle trying to get a lock surely has a lot to do with my GPS issue. I do however, get a lock in every setting that has been written up in this forum, and other forums. The difference to me is hardly any, since it always takes many minutes for me to get a lock. I never have used any other GPS device since living here in the city, so I would like to ask other who live in a large city if it is taking them several minutes as well? Because it seems as though people are saying it is taking them only seconds to lock on. Hmmm.....

[Q] Custom Stripped Dedicated Tracking OS for Long Life GPS Tracking

I have a need for tracking my vehicles remotely in case of theft. I have tried Lojack which failed miserably because after the thief deactivates the unit there is no way to recover the vehicle. There is a buffer time between finding the vehicle stolen and being able to activate Lojack of about 3 hours, which is plenty enough time to search the vehicle and deactivate the unit. The best solution is something that records the location of the vehicle to a remote server. The location log can be viewed even after the unit on the vehicle is deactivated which should show the location of the chop shop, garage, etc.
The most reliable and user-friendly product available is a cell phone using Google Latitude wired into the vehicle’s constant 12V+ using a car charger. Google Latitude Location History must be enabled so all past logged locations are viewable with a timestamp on a map.
Some downsides to Google Latitude are:
Location update intervals not configurable
Android OS has many unneeded features that waste battery
Android phones last 8 hours max when GPS tracking set to update every 10 minutes and with sync disabled and never turning on the screen (based on my tests with various Android phones after fully charging the batteries)
Proposed Solution:
Strip the Android OS down to bare minimum (linux kernel, no GUI, only cellular and GPS support) with configurable location update frequency that updates to Google Latitude. This would be a dedicated tracking device not usable as a normal phone, but should extend battery life.
Questions I have:
How many people would be interested in testing/using this customized OS?
Do people with experience customizing Android think this is worthwhile?
Is anything like this already being worked on?
Would anyone be willing to help me when I need an experienced guide?
I’m not interested in charging money and will release the source code.
Update:
Latify for Android updates the phone's current location using the Google Latitude API and lets you set the update interval and can auto-start when the phone is turned on. Latify makes a dedicated tracking OS less important but I'm still curious what the community thinks of the idea.

[Q] SmartLock almost never works

Since a while I'm having big problems with SmartLock Trusted Places. When I'm @ home and having the home address from Google Maps enabled, it almost never works.
If I manually add my neighbors addresses as well it works for the moment but that result does not last.
If I go into the settings and add something it updates my location to the very address that is added automatically by enabling Home from Google Maps.
Location and location history is enabled on the device.
High accuracy, battery saving & device only all get the same result, it does not work.
Running 5.1 with Google Play services 7.0.97 (-438).
Does it work for you?
I actually just logged on to ask the same thing. It's been this way ever since 7.x dropped. It's so frustrating all the issues this new play services has caused.

Google Location Accuracy cannot be enabled

I'm trying to switch on Location - Google Location Accuracy, but it cannot be enabled. I leave the setting screen and it's off again!
Anybody??
Google Services installed, Framework frozen.
Be happy about it.
That Google thing does not improve YOUR location accuracy, it improves Google's data collection, by capturing all WiFi networks in range and sending those data back to Google, so Google can establish a map of WiFi networks all around, serving you just nothing except higher battery drain because your GPS will be switched on even if you switched it off, permanently exposing your position even if you don't know about, and wasting mobile data for sending your findings to Google.
A while ago, Google even tried to force us activating this rubbish feature to be able to use Google Maps at all - but fortunately, they rowed back, now try lies about better accuracy to make you switch on that feature only they benefit from.
It's a feature that should be OFF at all times. It's misleading because Google babbles about improved accuracy - but never clearly states it improves YOUR location accuracy. Not without a reason.
Klosterbruder said:
Be happy about it.
That Google thing does not improve YOUR location accuracy, it improves Google's data collection, by capturing all WiFi networks in range and sending those data back to Google, so Google can establish a map of WiFi networks all around, serving you just nothing except higher battery drain because your GPS will be switched on even if you switched it off, permanently exposing your position even if you don't know about, and wasting mobile data for sending your findings to Google.
A while ago, Google even tried to force us activating this rubbish feature to be able to use Google Maps at all - but fortunately, they rowed back, now try lies about better accuracy to make you switch on that feature only they benefit from.
It's a feature that should be OFF at all times. It's misleading because Google babbles about improved accuracy - but never clearly states it improves YOUR location accuracy. Not without a reason.
Click to expand...
Click to collapse
Yes, but Timeline in Google maps doesn't work without this setting. Is there a way to force enable it?
viamal said:
Yes, but Timeline in Google maps doesn't work without this setting. Is there a way to force enable it?
Click to expand...
Click to collapse
Only if you un-freeze GSF it will work.
I would rather have my notifications back and lose timeline. No timeline, for me, is a small price to pay
Sathelp said:
I would rather have my notifications back and lose timeline. No timeline, for me, is a small price to pay
Click to expand...
Click to collapse
You see, I've had it for 10 years now on various phones. It shows me all the cities in the world that I visited, i remember the best restaurants, etc. And in your Timeline, you also see the photos you took in various places. They are attached to timeline itself.

Privacy: Does Android upload your home AP SSID/BSSID/GPS if the home AP broadcast beacon is "hidden?"

Privacy: Does Android upload your home AP SSID/BSSID/GPS if the home AP beacon is "hidden?"
Does hiding your home AP broadcast beacon prevent UPLOAD of your SSID/BSSID/GPS to Google?
If so, how?
Background:
Anyone navigating on Android who drives by my home after they pressed OK to the Google Maps query is likely automatically uploading to Google my private information without my consent.
To continue, turn on device location, which uses Google's location service. [No Thanks or OK]
By default, this simple act turns the Android phone that drives by my home into a spying device for Google:
Android11-Settings > Location > Location services > Google Location Accuracy = ON
​Google's location service improves location accuracy by using Wi-Fi, mobile networks, and sensors to help estimate your location. ​ Google may collect location data periodicaly and use this data in an anonymous way to improve location accuracy and location-based services. ​ Turning this off will result in your device only using GPS for location. ​ This may impact the accuracy of location used by apps such as Maps and Find My Device.​
All I'm asking with this question is whether turning off the home access point broadcast beacon (aka hiding the SSID) prevents those phones from UPLOADING my information to Google servers (and to other servers) by default.
Please be advised this question has nothing to do with using "_nomap" as part of the SSID. ​The question is independent of whether _nomap is used because the upload to Google by phones driving by your home of your SSDI/BSSID/GPS still occurs with or without _nomap on a broadcast SSID.​
I'm interested in this as well. I've lowered the signal strength so you can't connect to it from the street, hidden SSID, but I'm pretty sure that [Forgot to not be evil] Google will collect all and any data it can get hold on. For example, if using an app to check signal strength, it recognizes the WIFI signal, so I'm guessing it's getting picked up by G as well. It's only a guess... and a history knowledge from them getting high on personal data
Марија said:
Notice that this is BENotice that this is BEI'm interested in this as well.
Click to expand...
Click to collapse
Thank you for letting me know the solution will also be useful to you as that's why I asked it.
We want a definitive solution for people like you and me (we can't be the only ones who care about our home AP privacy).
I think anyone who is concerned about their home privacy wouldn't want their SSID/BSSID/GPS in a public database if they didn't expressly opt IN on purpose.
The default assumption by Google (and many others) is, I suspect, that if you publicly broadcast your SSID in the clear, then you're opting in.
Even though I disagree with this default assumption I have to understand the logic which is why I don't broadcast my SSID.
By not broadcasting my SSID I'm (hoping) it's signaling my intent to opt OUT.
Марија said:
I've lowered the signal strength so you can't connect to it from the street, hidden SSID, but I'm pretty sure that [Forgot to not be evil] Google will collect all and any data it can get hold on.
Click to expand...
Click to collapse
I thank you for that idea of lowing the signal strength (which only some routers will allow, I think) but I need all the signal strength I can get.
And more to the point most people need all the signal strength they can get, I think.
Even so, while lowing the signal strength may help, it still won't work for the Android devices that walk close enough to your front door to access your signal after using Google Maps.
Pragmatically, all it takes is the postman or the Fedex guy or the UPS guy to have his Android phone on with his "Google Location Accuracy" turned on.
It's even worse if they have "Improve accuracy" turned on, as that adds additional "Wi-Fi scanning" and "Bluetooth scanning", which is another can of worms we'll stay out of for this thread.
Speaking of Google Maps, you can "fix" the problem of Google Maps secretly turning on "Google Location Accuracy" but you have to go into your Android settings to find the special Google Maps (Google Play Services actually) "activity" named
com.google.android.location.settings.GoogleLocationSettingsActivity​
Actually the activity Google Maps used is a secret undisclosed activity one step BELOW that com.google.android.location.settings.GoogleLocationSettingsActivity activity since the "OK" in Google Maps automatically secretly toggled it on.
Nonetheless, I set a shortcut to the com.google.android.location.settings.GoogleLocationSettingsActivity which allows me to turn the "Google Location Accuracy" toggle off (while leaving the "Location" toggle on) after I say "OK" to the Google Maps query to turn on location.
BTW, the undisclosed hidden secret activity is a specific Google activity that only Google does, as far as I know.
No other program that I know of secretly toggles "Google Location Accuracy" on other than Google Maps which is one reason Google is being sued in Arizona as we type for their secret tricks to get our private data uploaded to their public servers.
Марија said:
For example, if using an app to check signal strength, it recognizes the WIFI signal, so I'm guessing it's getting picked up by G as well.
Click to expand...
Click to collapse
Here is where our little secret lies!
I have absolutely no doubt that the phone's radio picks up the hidden BSSID (because I can see the hidden BSSIDs on my phone when I use any decent Wi-Fi graphing app).
However........
It's my understanding (which I need to find a reliable source to back it up) that someone's phone that is typically set to upload the SSID/BSSID/GPS by default will NOT upload that BSSID if it's hidden.
What's important is that sentence assumes that the typical upload of the SSID/BSSID/GPS requires the SSID to be broadcast in the clear.
If that's true, then simply HIDING the SSID broadcast beacon will stop other phones from uploading your SSID/BSSID/GPS to not only Google servers, but potentially Mozilla, Kismet, Wigle, Netstumbler, and other servers.
Note that I'm not saying it can't be done by a determined program. What I'm saying is that it's my understanding that it isn't done.
Notice the profound implications?
If I'm correct, then HIDING THE SSID broadcast is far BETTER than using _nomap (although I'd still use nomap also) simply because hiding the beacon broadcast is making it clear your intent to even those public databases that do not respect the nomap.
I think this is the way the Android SSID/BSSID/GPS upload typically works.
Of course ... there's more to the story...
One problem with hiding your SSID is that it kicks the privacy can down the road because now your phone is constantly asking by name for that SSID when you're not connected and your Wi-Fi is on.
Of course, there's a simple fix for that secondary problem (which works in Android 11 at least), which is to set your Wi-Fi on your phone to stop asking for your hidden SSID when you're out of range of it.
That don't-ask-by-name-for-my-hidden SSID setting on Android 11 is
Settings > Connections > Wi-Fi > (select an SSID) > gearicon > Auto reconnect = OFF
Марија said:
It's only a guess... and a history knowledge from them getting high on personal data
Click to expand...
Click to collapse
I would like to find a reliable source that backs up that guess that Google and Mozilla and the others (Kismet, Netstumbler, Wigle, etc) "don't" get your SSID uploaded to their servers by default if your home AP SSID beacon broadcast is hidden.
Notice I said "don't" which I think may be the case only in the default situation, as I'm well aware any determined person "can" upload even your hidden home AP BSSID/GPS information manually to any public server they want to.
In the end, I have a solution that I'm constantly honing to improve it where I want to accomplish two things here.
I want others to be able to do what I can do, and
I want others who know more than I do add to what we can all do in terms of keeping our SSID/BSSID/GPS out of Google's hands (and that of Kismet and the rest).
To clarify things: Android OS is developed by a consortium of developers known as the Open Handset Alliance and commercially sponsored by Google. It is free and open-souce software. It's source code is known as AOSP.
Android OS isn't collecting data as Google Mobile Services ( GMS ) do.
If you do not need any GMS applications or services, a high-quality AOSP ( like LineageOS what is just a modded version of AOSP ) protects your privacy at 100%, IMO.
jwoegerbauer said:
If you do not need any GMS applications or services, a high-quality AOSP ( like LineageOS what is just a modded version of AOSP ) protects your privacy at 100%, IMO.
Click to expand...
Click to collapse
I agree with you that I should switch to aosp given that I have no need for gms services.
But the phone is still technically owned by T-Mobile for two years (it was free) so I am under the impressions (see below links) that I can't add aosp yet (is that true?).
Question Does anyone know how to root the Samsung Galaxy A32 5G?​
Question Any chance that a Samsung Galaxy A32 5G can get aosp?​

Categories

Resources