Added com.vonglasow.michael.satstat (SatStat)

Signed-off-by: Michael von Glasow <michael@vonglasow.com>
This commit is contained in:
Michael von Glasow 2013-09-03 13:21:05 +00:00
parent 246812a7fa
commit 85ea0b0260

View file

@ -0,0 +1,78 @@
## See http://f-droid.org/manual for details
Category: Development;Navigation;System
License:GPLv3+
Web Site:https://github.com/mvglasow/satstat/wiki
Source Code:https://github.com/mvglasow/satstat
Issue Tracker:https://github.com/mvglasow/satstat/issues
# A dedicated web page with donation buttons is preferred
#Donate:
# See http://flattr.com
#FlattrID:
# Add a comment about how to verify, such as URL for an issue
#Bitcoin:
# Scripts will try to put the app's name here. Don't need to edit it
Auto Name:
# Only changes the name in the index. Not generally required
Name:
Summary:GPS, sensor and network status
Description:
A diagnostic tool that displays data reported by sensors in the phone.
GPS:
* Location, speed, bearing and error
* Satellites in view and satellites used
* Time to first fix and time of last fix
Sensors (as supported by your phone):
* Accelerometer (acceleration and gravity)
* Rotation
* Magnetic field
* Orientation (azimuth, pitch and roll)
* Ambient temperature
* Pressure
* Relative humidity
* Ambient light
* Proximity
Networks:
* GSM/CDMA cells in range
* WiFi networks in range
* Signal strength
Known limitations:
* Some phones will report only the network cell with which they are currently
registered. On such phones you will only see one cell under "GSM" or "CDMA".
This is a limitation of the phone's radio firmware, and SatStat has no way of
getting more information from the device.
.
# Yes is the only possible value
#Requires Root:
## Repo and Build Version only apply to apps with source-built versions
Repo Type:git
Repo:https://github.com/mvglasow/satstat.git
# Versions/Codes of each Build Version must be different from the others
# Any jars or prebuilts should have references, preferably in the README
# The following contains all possible parameters in the best order
Build Version:1.1,1,V1.0
# A more recent version i.e. one with a greater version code
#Build Version:
## Comments on what to watch for when adding new Build Versions (BVs) go here
# This field is best used at the discretion of the repo maintainers
Auto Update Mode:Version V%v
# One of Tags, RepoManifest, Static, Market or None (in that order of preference)
# If None or Market, describe why the other methods don't work
# Tags and RepoManifest (RM) are automatic but check that the mechanism works
# Use Static if you plan to let the maintainers know in person (so to speak)
Update Check Mode:Tags
# These two values are usually in the AndroidManifest of the current release,
# but may be automatically updated, depending on the value of the previous field
Current Version:1.0
Current Version Code:1