Related
IGNORE ME!!! Waste of a post, seems this is not only not a new idea, but already implemented (just not used apparently).
I know this might not be the best place to put this but I do not know an official way to suggest this to google.
Background info: I have been testing out latitude and it has been failing. I spent a few hours (really) reading a forum on google about other users having the same problems (where it sometimes will not update your location for hours or days at a time). I started thinking what if there was an api to get the location instead of a direct gps read.
My idea is what if every time an app got a gps lock if the OS were to record it in a db somewhere as "last known location" (lkl from here on) and "last location time" (llt). Apps that need an immediate fix (maps) could turn on the gps and get it (which would then update the lkl and llt), but apps that need a recent location (locale, latitude, google local search etc) could check the llt and see if it is recent enough for them. If for example, locale needed a lkl from 5 minutes or less it could check to see if one is recent enough to use. If not it could turn on gps and get one. If so, it would use the lkl that was recorded and be done. In this example one gps location fix every 5 minutes could satisfy 20 different apps, with the app that needs the most recent updates doing most of the polling. For example, say most of your apps want a 30 minute llt but locale wants a 5 minute llt. Locale would probably be doing all of the polling, but the rest of the apps would not need to since 5 minutes is recent enough for them. This could potentially save battery and make apps like latitude work better since not all apps need an exact fix.
I know this was long and might not fit in here, but I figured if I put it here maybe someone of importance (or someone who knows the right people) could pass it on. It is one of those things that I would forget if I do not get it out.
This is already built into the Android APIs. You can get the last location known to the device, the time of the location, for any of the location providers.
yeah, was just talking to someone who told me the same thing. waste of 10 minutes of my life. I am a little pissed now that I know latitude and other apps could be using this and are not.
Has anyone else been having issues with there gps? I have it turned on and often times maps will only be like 1000m accurate. Sometimes it gets like 10m accurate, but it can take forever to get a fix. And sometimes it doesn't.
Sent from my ADR6400L using XDA App
are you rooted? if so, what ROM?
I am rooted, but on the stock ROM still. I have location services on all the time. Could that be messing with it?
do a search...there are threads that offer some "tips" to cure the GPS problem
Two quick things:
I did two quick things, both suggested elsewhere on this board, and now get gps lock within seconds.
First, I disabled the Google location services, but saw no appreciable difference in lock speed.
Second, I downloaded "GPS Status" app. Menu > Tools > Manage A-GPS state > select 'Reset', then follow the menus again and select 'Download'. This resolved the issue for me.
I am also running a custom ROM that changed the GPS setting to US from North America (again, as suggested elsewhere here), but that alone did not fix the problem for me.
Nobody's Hero said:
I did two quick things, both suggested elsewhere on this board, and now get gps lock within seconds.
First, I disabled the Google location services, but saw no appreciable difference in lock speed.
Second, I downloaded "GPS Status" app. Menu > Tools > Manage A-GPS state > select 'Reset', then follow the menus again and select 'Download'. This resolved the issue for me.
I am also running a custom ROM that changed the GPS setting to US from North America (again, as suggested elsewhere here), but that alone did not fix the problem for me.
Click to expand...
Click to collapse
+1 Same things fixed it for me....
I fixed mine. It needed to be flashed with a gps file to fix it. I think the file can be found on one of the forums. I'll try to post it tomorrow.
Sent from my rooted Thunderbolt, Das BAMF
What has helped for me is to change the servers back and forth in the instructions for the GPS fix in the dev section... ie the GPS.conf file... Switch it to the suggested server to fix... Reboot... Test your locks with GPS Test app... If still not working... Switch back to North America server, reboot, and test again. Right now I'm on Virus rom, which comes with the server in the GPS fix... But i was still having lock issues... Switched back to the North America server and rebooted... Now it locks quickly and with 6.6 feet accuracy.
Sent from my Thunderbolt using Tapatalk
Ok cool. Thanks guys. I'll try this out and see if it fixes it.
Sent from my ADR6400L using XDA App
Hi
I did what u say, but my gps still a bit off. But better than before....
thanks
You are welcome... Secondly, if your GPS is still flaky and you're running a 09 rom might want to flash a 06 rom and see if that helps. Best of luck...
Sent from my Thunderbolt using Tapatalk
Nobody's Hero said:
I did two quick things, both suggested elsewhere on this board, and now get gps lock within seconds.
First, I disabled the Google location services, but saw no appreciable difference in lock speed.
Second, I downloaded "GPS Status" app. Menu > Tools > Manage A-GPS state > select 'Reset', then follow the menus again and select 'Download'. This resolved the issue for me.
I am also running a custom ROM that changed the GPS setting to US from North America (again, as suggested elsewhere here), but that alone did not fix the problem for me.
Click to expand...
Click to collapse
This did it for me too. However, you MUST wait for the swirling circle to stop spinning and get a "lock on" which will then show your lat/lons. Be advised this can take several minutes! Be patient.
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!
I was searching around for solutions to help me with my massive battery drain in CM10 A4 for these 2 days and I realised little emphasis had been put on "wakelocks" in our i9003 forums; so I thought some discussion here would be nice to help all of us, especially relatively new people like me.
A detailed explanation can be found in ahalford's thread; and also in the XDA wiki. Below is just what I managed to sort out for our device, specifically CM10 A4 (not sure about applicability in other ROMs).
Wakelocks are identifiable via BetterBatteryStats and I would like to mention a few of them that I could identify (and if possible, solve). My purpose here is just to share some info that I managed to find and if possible provide some guide based on my own experience.
In CM10 A4, I uninstalled:
Google Search
Google Maps
News & weather
Google Backup Transport
CM Wallpapers
Android Live Wallpapers and its associated LWPs
Spare Parts
GTalk
Movie Studio
Certificate Installer
Wakelocks identified:
1. RILJ
Easiest way to solve: Flash the fixed kernel by loSconosciuto. Personally tested it on CM10A4, and SlimBean v3.1; both worked. Just screen off/on and the signals will return.
Alternatively, put the phone to Airplane Mode (I left my WiFi on), reboot. Then leave it to screen off for some minutes, and turn off the Airplane Mode. The signal bars may not return as of yet; so just DC and reconnect the WiFi. Signal bars return, RILJ stopped. :victory:
2. GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice UNSOLVED
Attempts: Removed GTalk (but problem persisted); Auto-Sync off; and disabled location settings.
Also worth to mention it occurred only when WiFi was on; didn't test it on mobile data (I don't have one).
Attempts of freezing apps: (Still investigating)
Search Application Provider
Network Location
com.android.backupconfirm
Google xxxx Sync (Contacts, Calendar, etc)
* Others recommended to sign out from Google account, and re-add (but I have no experience on this).
* Also somebody was talking about disabling GTalk-related services in Google Framework Services using Autorun Manager (or similar); but it didn't work for me.
3. AudioOut_2
Perhaps not a wakelock. If the time matches time of you opening any games/app that produce sound; it should be normal and should stop after exiting application.
* Saw a thread that this may happen if the app did not exit properly (e.g. here)
Any input/discussion would be greatly appreciated.
Will update more whenever I have time! Thanks!
cheeyeen said:
2. GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice[/B]
Solution: Removed GTalk (but problem persisted). Stopped it by freezing a few apps via TitaniumBackup but the exact way to do it is still unknown, currently trying to rule out the below one by one.
Click to expand...
Click to collapse
I think for 2nd wakeclocks you have to turnoff Auto-sync from setting.Double check your setting.Though there is not perticular button to turnoff Autosync in CM10 you have to use widgets to turnoff autosync.
And go to Play store settings disable all tick.That may be solve second one.
nicsptl said:
I think for 2nd wakeclocks you have to turnoff Auto-sync from setting.Double check your setting.Though there is not perticular button to turnoff Autosync in CM10 you have to use widgets to turnoff autosync.
And go to Play store settings disable all tick.That may be solve second one.
Click to expand...
Click to collapse
Thanks. Actually it was solved, but I forgot to mention that. I just didn't know how it went solving lol :laugh: And yeah, Auto Sync off via power buttons in notification drawer and verified from the account settings.
Hi guys,
I run PA 4.4 for like 10 days now. Since a week ago I have strange locations in my Google location history - constantly, when not moving - and rather accurate when I am outside (maybe has something to do with the wifi connection when stationary at home or at work?)...
One interesting part of it is: the first days of my new PA experience everything was fine. So probably it does not have anything to do with it. That first day I had the issue my phone crashed earlier while I was outside and I had to do a reboot. Maybe some settings were changed during that!? Or... maybe it doesn't and it's just a coincidence after some apps where updated (Google Search or so)...
I tried quite some settings to figure out what happens here - and it is not trivial - to my mind:
I did another clean install of the ROM; had the same issue again
I changed between "high accuracy" and "battery saving" mode in the location settings; no change
I went to the developer settings and unchecked "accept mock locations" (is that how the option is called in English?); no change
I have a Nexus 10 also running Android 4.4.4 and started to record my location history from that device with different settings: all are fine and accurate! When I record from both devices I can actually see my history jumping in 5-minute-mode...
Any ideas, any suggestions?
Please...
Two more findings, which make this issue even stranger:
When I move in the house - e.g. 2nd instead of ground floor - I get different locations, some 100 or 200 meters away, but both far from home.
I turned wifi off for one and a half hour - that resulted in perfect locations!! Locations were inaccurate after turning wifi on again...
What is wrong here?? So I get more inaccurate locations when connected to wifi!?
i always run straight gps and never wifi. imo its a conflict of interest.
gps is dead accurate, so the only time you could benefit from wifi is when you are in a building with no gps signal, and frankly, why would i need 100% accurate gps if im already in the building.
again imo, what is happening is, it can only reference wifi that it knows the exact location of. it has no way to tell how far from that wifi you are, so its guessing based on a limited gps signal and known wifi points.
i think its a waste of battery to be scanning wifi points all the time any ways, unless you have a constant use for it.
bweN diorD said:
i always run straight gps and never wifi. imo its a conflict of interest.
Click to expand...
Click to collapse
Thank you for the answer! And I sort of agree...
But the question is:
what did change that day when my location started to be different? I never had problems for more than two years of using the location history. Even after moving in April everything was fine with the wifi locations. I get one accurate reading like every one to three hours - so the location jumps from time time. Why is that? Is that a gps reading?
Plus: how could I change the settings? The only thing I can chose from is: "battery saving" (cell towers and wifi) or "high accuracy" (the same plus gps). I selected the second option but obviously still the Google location service does not really use it. When I turn off wifi it can only use cell towers plus gps... but obviously I want to be connected to the wifi when being at home.
I can't say why it started acting up.
If you use WiFi you are kinda stuck.
I only have GPS on and denied anything that wants to use WiFi for any reason.
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Click to expand...
Click to collapse
I guess that option is the "use wifi for location detection although wifi is turned off" which can be found in the wifi advanced options. But I turned that on and off, no change.
But one more test from myself:
I let wifi on but disconnected from my home network. The result is: accurate locations! So the problem is not the wifi itself but a connected wifi!? And it is not only the home network because I had the same issue at work.
Plus: we just had a thunderstorm, that could have been the reason why cell towers and/or gps reacted differently: my location was at some new place about more than a mile away. The worst thing is: accuracy of that location point was about half a mile -- which means: my real location was not inside the accuracy cycle (that blue cycle when using location history)!!
The accuracy cycle is always very small when I get the real readings at home and always about half a mile in radius when somewhere else...
that is basically the problem with using wifi to help. there are too many variables. location needs to know the location of the wifi, but then there is a broadcast radius that decreases accuracy. there is also the question, what does it do when you are connected to a wifi it doesnt know the location of?, that could cause inaccuracy. maybe it makes an uneducated guess, who knows. there is also the issue, what if it thinks it knows the location but its actually wrong?
the list of possible scenarios could go on and on as to why it isnt reporting correctly.
the only way to truly know why it is wrong is to find out why exactly it thinks you are where you are when its wrong. there has to be some exact source of information its using to base your wrong location on. unfortunately, i doubt there is any way for the common user to get this information, let alone take corrective action so its not inaccurate in the future.
wrong locations only when wifi is connected, only on one device
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...
Tho-D said:
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...
Click to expand...
Click to collapse
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
On my phone I can force it to use GPS only, I have the option anyways.
Under location I have device only or something like that, it says it only uses GPS when that option is selected.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
Click to expand...
Click to collapse
I thought about that, too. Means to installiert something else, CM11 vor so...
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
Ohh OK, I didn't know that. Thanks for the info
Sent from my LG-VS980 using XDA Premium 4 mobile app
Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
so i did a little test today on the way home from work, as i took a different route than normal to avoid traffic.
when i started "maps" i had to allow google location services to navigate. so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
last week i navigated a 3 hour trip, on a different rom, with no issues. today, maps couldn't seem to start gps to find my location to start navigating. so i turned on "high accuracy", more to test than anything else, and it found my location and we were navigating home .
i knew where i wanted to go but at some points that varied from where maps wanted me to go. for a while it did good at making quick corrections to my path. about 20 minutes in, i didn't follow its directions again. well this time, it didn't recognize that i didn't turn, then advised me to make a subsequent turn onto a road that was off the road i didn't turn onto. now, the road i am on is about 1/4 mile from the road it thinks im on, the 2 roads are parallel. well it took maps over a mile, after i made another turn towards the road it thought i was on, before it realized it was wrong and made corrective instructions. after that, i made a quick stop to grab some liquid refreshment for the night and turned off navigation, as i was close to home.
this really goes to prove nothing more than "high accuracy" is not always highly accurate. i traveled across 3 states last week for 3 hours on "device only" and never once was it wrong about my exact location.
just wanted to share my experience, really doesn't help or fix your problem, but may shed some light on the possible inaccuracies across multiple devices.
bweN diorD said:
so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
Click to expand...
Click to collapse
I tried this and yes, Maps works with the "device only" setting. But when using Now it said that location-based cards (weather, traffic, ...) only work with "high accuracy" or "battery saving". So for me this setting is useless.
I guess I'll do another clean install and try CM11 or so...
it's not ROM related
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?
Tho-D said:
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?
Click to expand...
Click to collapse
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.
bweN diorD said:
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.
Click to expand...
Click to collapse
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).
Tho-D said:
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).
Click to expand...
Click to collapse
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.
bweN diorD said:
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.
Click to expand...
Click to collapse
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format /data". Should I try this one?
Tho-D said:
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format data". Should I try this one?
Click to expand...
Click to collapse
I'm pretty sure it says data/media. I don't have cwm on right now or I would check, but I think it is under mounts and storage. It was in the same dir where you can format system and such if I remember correctly.
Its also possible someone removed that option from your version, but I don't know why they would unless your phone doesn't have that partition.
Sent from my LG-VS980 using XDA Premium 4 mobile app