I'll start off with background: I'm 16 and recently started driving. My parents are kinda paranoid and want me to text them every time I leave or arrive somewhere. I'm lazy and forgetful and they think I'm dead if I don't text them. See my dilemma?
I wanted to try and help myself out. I downloaded Ulysses speedometer thing and tasker. My idea is to have it so that tasker will catch when Ulysses is open and send my mom an sms saying I'm leaving and then when it closes say I have arrived. It would also be cool if it could enable/disable GPS and awesome if iit would tell her my location.
I tried just the basic part but couldn't get it to send the message when I opened Ulysses. My question is, can somebody who knows more about tasker than me (I know how it works but it gets confusing) help me get this working? It would be awesome and if my driving led to me getting a job I might be able to donate you some moneys or something. In the least I can give you a virtual cookie and/or hug.
Thanks!
Sent from my MIUI SCH-i500
Bump, I could really use some help with this.
Sent from my MIUI SCH-i500
Bump again, this is my last try. I got everything figured out to have it start GPS, get location and everything... I just can't get it to send SMS which is the main idea. Even making another profile whose only function is to send an SMS doesn't work. Am I doing something wrong?
Sent from my MIUI SCH-i500
I dont know Ulysses, but if you combine the "App" context with a GPS location context this could cause problems because the App context only becomes active in the instant where the app is started. So if you start the app and you are not at the location from where you want to send the SMS, then the profile does not become active and no SMS will be sent (clear ? )
I would not use the App context and GPS Location for this, but rather the "cell near" context. This context can be calibrated to a specific location by scanning the cell towers in range and it does not eat as much battery as the GPS. I use this for setting my phone to silent when I am at work, or switching of the keylock when I am at home.
With the cell near context it should be possible to use the "send SMS" action.
You can also try to combine it with a timer or set a flag to avoid multiple SMS in case you come close to some other cell tower for a short time and the profile switches on and off.
If you want your position to be included in the SMS you can use the "Get Location" action. It uses either GPS or net based location.
For GPS: When your profile becomes active (activated by cell near), set the GPS to be switched on, and use the "Get Location" action (which has to be set to GPS). Allow some timeout to get the fix, then your position should be stored in the variable %LOC, which you can use in your SMS text. Then send SMS and switch off GPS.
For net location: also use the "Get Location", but set it to "Net". You have to have Internet connection to get a location that way, and in your location settings (phone settings) "use wireles networks" (or something like this) has to be activated. Net Location is not as accurate as GPS, but normally its not as much of a hazzle to get a fix. I think the net location is stored in %LOCN afterwards...
Hope I didnt get anything wrong, just wrote that from the top of my head.. Just use the help buttons in the different action tabs to get the detailed info.
While I applaud the effort you are making to try and automate the process of letting your parents know that you are safe, I am sure that they would appreciate it more if the SMS came from you personally and not from a machine. Make an effort to consider their feelings of anxiety while you are a young driver, and take the time to text (or maybe even call them). Drive safely!
or just use latitude
Thanks for the replies guys. Will be trying that long one out. I have been trying to send personal texts, and usually I can remember when I'm leaving but I forget to send one when I arrive. Just trying to avoid trouble with this. And I've tried latitude but I use a GAFYD account as my default and it doesn't support check-ins with latitude. And latitude won't let me use my secondary gmail account.
Sent from my MIUI SCH-i500
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.