locked-fg / signalcoverage Goto Github PK

Authentication against server should be doable with google/android login

http://stackoverflow.com/questions/16772383/how-to-detect-fake-gps-coordinates-in-android

Could be solved already.
Check in latest version

Independent of the regular location updates, an update should be requested when the signal strength changes.

Maybe change the UI to make 2 toggle buttons (passive / active listeners)

The shared prefs are lost under some cuircumstances. Maybe when the app was killed.

Create an option to allow receiving /saving the IP (possibly anonymized).
Unfortunately this always requires an external call - otherwise we'll measure a lot of internal IPs.
Private IPs will hardly be interesting.

Evaluate the use of Alarmmanager instead of thread sleep.
Might only make sense if the pause is long enough.

See http://en.m.wikipedia.org/wiki/Mobile_phone_signal
For explanation and formulas of asu.

Is it really better than just the signal strength?

Use an easy or mapper like ormlite to read / write the objects.
Or just use
http://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html#insertOrThrow(java.lang.String, java.lang.String, android.content.ContentValues)
http://developer.android.com/reference/android/content/ContentValues.html

Restriction to age of location might be too strong.
Increase threshold and save age to DB

Update db: http://stackoverflow.com/questions/8133597/android-upgrading-db-version-and-adding-new-table

http://developer.android.com/reference/android/telephony/TelephonyManager.html
GSM, LTE, HS(D)PA, ...

If saved in shared prefs:
/data/data/your.app.package.name/shared_prefs

Upload does not work.
Show error message!

The progress bar used in saving and uploading should be realized as a notification.

You should import signalcoverage-share-3.0.0-SNAPSHOT.jar from a public maven repo (jcenter, mavenCentral) or build it from source like you do with ActionBarSherlock.

Also, you could ipmort ABS from a maven repo and that would be much easier than what you do now.

http://stackoverflow.com/questions/6822319/what-to-use-instead-of-addpreferencesfromresource-in-a-preferenceactivity

Is this usual behavior or is it just a certain way that the service has to be flagged? Service.START_STICKY might be not appropriate

Default profiles for fine and long term recording would be great

When the phone shows no signal (in the top bar), does the app really save the correct state or just the last signal before we lost signal?
Sometimes there seems to be signal strength >0 but no carrier.