There can be several reasons reasons for this.
- -The gist of a phone using GPS is that it needs to know where every satellite in the GPS constellation is and it usually - wants to use your data connection to do this. The GPS satellites do broadcast this information at different intervals; - specifically, each satellite broadcasts almanac data and ephemeris data.
- -The almanac is not very precise and gives a rough overview of the constellation and their positions over the next few months. - A GPS receiver can use this to get a rough idea of where it is and which satellites to select. When a phone has been off - for a long time, or suddenly shifted to a new location, it needs to reacquire almanac data.
- -The ephemeris data is more precise; it is broadcast more frequently and goes stale quite quickly. It's only once a GPS - receiver has its almanac data that it knows to look for the ephemeris data. Once the phone has both of these pieces of information, - it can then figure out where it is. This process can take around 12 minutes and is known to be very flaky; any interference - or interruption in the process means that the GPS receiver in the phone needs to start over. The satellites only broadcast at - 50 bytes/second.
- -Because it takes so long, to assist with this, many mobile operators deploy aGPS servers; - these servers have already downloaded the almanac and ephemeris data and your phone can download it from them at a faster rate then - from the satellites. But it does mean that your phone has to be on a familiar network. Being on roaming or with a restricted - data plan will prevent this from happening.
- -All in all, there are a lot of factors at play. The problem could be anything from missing almanacs to data to hardware. GPSLogger simply waits for the OS to be ready with its information.
- - -It all comes down to your hardware, settings and environment. The accuracy is only as good as your phone's GPS chip. - Some phones may have 4 meter accuracies, some have 500 meters. Also, using GPS satellites will give you better accuracy but take a longer time; using network location will give worse accuracy but is quicker. You may also want to check your environment, as there can be inaccuracy due to clouds, buildings, sunspots, alien invasion, etc. -
- -There are two possible reasons for this.
-The standard when logging points is to use UTC. Since this is the standard, it would be wrong to use the the local time zone. Instead, it is the responsibility of the software you use the log file on (Google Earth, GeoSetter, etc.) to adjust for your timezone. - Any application that deals with GPX or KML files will have a setting that allows you to specify your own timezone.
- -The imperial units are only for display purposes and nothing else. When logging, the units are always in SI units - meters and seconds.
- -You can connect your phone to your computer and mount the SD card, then copy the - file from the GPSLogger folder. That's the default folder, but you can change it in the settings. Note that while your SD card is mounted, GPSLogger can't write to the - card, since it's in use. To view it on the phone itself, if you have a file explorer, then you can go to /sdcard/GPSlogger > Long - press file > Open as > Text
- -If the app is logging, and you make changes to the settings, the changes will - take effect after the next point is logged. This means that if you've set - your interval as 1 hour, you have a long wait ahead of you. If you want the - changes to take effect immediately, then stop logging and start it again so that - the changes are refreshed.
- -GPSLogger provides a Start logging and Stop logging shortcut. Your automation app can invoke these shortcuts.
- -Mainly, turn wifi off, turn mobile data off, turn background synchronization off, turn bluetooth off. If you turn data off, you'll probably want to inject aGPS data regularly, there are apps that can do it for you. - You can also try going into airplane mode which turns many things off. When it comes to choosing between location sources - GPS vs network - GPS will be more battery hungry while network location is easier on the battery.
- -It's how the Android OS has implemented its GPS system. When you say you want a - point every 60 seconds (for example), that's actually a suggestion rather than an - imperative, and so the time interval between GPS points is never guaranteed. - GPSLogger has logic that checks the time difference, though, and will make sure - that at least 60 seconds have passed before logging again.
- -As of newer versions of Android, removing the notification will cause the service to be killed. As a result, the notification now needs to stay there. - You may have seen a recent increase in the number of apps that need to sit in the notification bar for the same reason - to perform background services without being killed.
- -I work on GPSLogger in my spare time and I don't always have the time or resources to implement a feature. However, GPSLogger is open source. You are encouraged to contribute or get someone else to contribute a feature.
- -On Github
- -On Crowdin
- -It's meant to be more battery efficient. A lot of other apps, such as MyTracks, - usually go with the assumption that you have a data connection available and your - routes won't be very long. They use CPU wakelocks and log points extremely frequently with high accuracy. - The aim of GPSLogger is to log points and stay quiet.
- - - - \ No newline at end of file diff --git a/gpslogger/src/main/java/com/mendhak/gpslogger/Faqtivity.java b/gpslogger/src/main/java/com/mendhak/gpslogger/Faqtivity.java index 46ddbba7d..770c095c9 100644 --- a/gpslogger/src/main/java/com/mendhak/gpslogger/Faqtivity.java +++ b/gpslogger/src/main/java/com/mendhak/gpslogger/Faqtivity.java @@ -24,10 +24,13 @@ import android.webkit.WebView; import org.slf4j.LoggerFactory; +import java.util.HashMap; +import java.util.Map; + public class Faqtivity extends Activity { - + WebView browser; private static final org.slf4j.Logger tracer = LoggerFactory.getLogger(Faqtivity.class.getSimpleName()); /** * Event raised when the form is created for the first time @@ -42,13 +45,25 @@ public void onCreate(Bundle savedInstanceState) setContentView(R.layout.activity_faq); - WebView browser = (WebView)findViewById(R.id.faqwebview); + browser = (WebView)findViewById(R.id.faqwebview); WebSettings settings = browser.getSettings(); + settings.setLoadWithOverviewMode(true); + settings.setUseWideViewPort(true); + settings.setBuiltInZoomControls(true); settings.setJavaScriptEnabled(true); - browser.loadUrl("file:///android_asset/faq.html"); - } + Map