We plan the following concrete steps:
- I will change the "[url removed, login to view]", that there are no messages anymore.
- app will only send coordinates to "[url removed, login to view]", if there is a locationUpdate (in combination with uuid and token, as it is now) new distance-values and time-values for the next determination are send back, as it is now.
- app must send current IP (variable "ip") to "[url removed, login to view]" always when it changed (in combination with uuid and token, as usual)
- Our server sends the notifications directly to the socket in the future.
At the moment, battery-drain is 10% per hour in normal-internet mode (HSDPA,GPRS,EDGE, NOT WIFI)
In WLAN/WIFI, battery-drain is "only" 5% per hour.
And the reason is NOT the locationupdate, but the httpconnection. I turned my localisation off at my phone AND blocked GPS,NET,PASS in the app.
Nothing changed. always 10% per hour in normal internet-mode (not WIFI).
That is far too much.
I'm sure, that the httpconnection every 6 seconds is to blame.
With the socket-thing, we have only http-connection if someone moves. But most of the time on a day, a person doesnt move. So, there are no http-connections most of the time.
17 freelancere byder i gennemsnit $13/time for dette job
Hello, sir. I read your job posting with interest. I am very interested in your job. I want to discuss in more details about this job. Looking forward your reply. Thank you. Best regards.