The problem I was having before was a problem of getting the trip types from google with my 4 asynchronous tasks (figuring out if the trip is walking/biking/car/transit). The way i was tracking trips was in a way that allowed me to have say maybe 15 car trips although I only took 1 (which is why i thought my algorithm was working earlier). But because i put down too many points/trips on the map trying to send all that information online to google made the application time out and crash. the jist of my solution (which i will be testing) is that i will be using less points only when necessary. So this means i will be only putting down 2 points on the map if there is movement within 5 mins of each other instead of putting a point on the map every 5-10 seconds.
The problem I was having before was a problem of getting the trip types from google with my 4 asynchronous tasks (figuring out if the trip is walking/biking/car/transit). The way i was tracking trips was in a way that allowed me to have say maybe 15 car trips although I only took 1 (which is why i thought my algorithm was working earlier). But because i put down too many points/trips on the map trying to send all that information online to google made the application time out and crash. the jist of my solution (which i will be testing) is that i will be using less points only when necessary. So this means i will be only putting down 2 points on the map if there is movement within 5 mins of each other instead of putting a point on the map every 5-10 seconds.