(ECU) of motorcycles Triumph, KTM, Aprilia and Benelli.
This application requires an USB/OBD2 cable with FTDI chipset or a Bluetooth adapter ELM327 v1.4 or 1.5.
Warning, with bluetooth connection, the reading and reprograming functions are not available.
Models list compatibility :
Triumph Daytona 675, cable & bluetooth, up to VIN # 564947
Triumph Daytona 675, from VIN # 564948, bluetooth connection only
Triumph Street Triple & Street Triple R, cable & bluetooth, up to VIN # 560476
Triumph Street Triple & Street Triple R, from VIN # 560477, bluetooth connection only
Triumph Speed Triple 885, 955, 1050 & 1050 R (including 2014 models)
Triumph Tiger 800/800XC, 885 (900), 955, 1050 & Tiger Sport (including 2014 models)
Tiger Explorer, bluetooth connection only
Triumph Sprint ST/RS 955 and 1050, Sprint ST/GT (including 2013 models)
Triumph Daytona T595/955i Daytona (all models)
Triumph Rocket III (include 2014 models)
Triumph Daytona 600, 650, Speed Four, TT600 (all models)
Triumph Thunderbird 1600 & 1700 cc, except Commander et LT
Triumph America, Bonneville, Scrambler, Speedmaster, Thruxton (including 2014 models)
KTM 990 LC8 & 1190 RC8 (include 2012 models)
KTM 690 Duke (include 2011 models) (except Duke 4)
KTM 690 SMC & Enduro/690 Supermoto (including 2013 models)
Aprilia Caponord and Futura RST
Benelli Tornado (Sagem ECU)
Ducati 848, 1098, 1198 (ECU 5AM)
Ducati Monster 800 & 1000
Ducati Hypermotard 1100
It is highly recommended to visit the site www.tuneecu.com before using this application.
The application is capable of:
- reading the live data
- showing the fault codes and clearing them
- displaying the logged freeze frame data
The application requires the OBD II Bluetooth dongle (ELM327 based) to communicate with a car.
All the popular OBD II protocols are supported:
- J1850 VPW and PWM
- ISO 9141-2
- KWP 2000
- CAN (11 and 29 bits - both 250 and 500 kBit/s)
If you have any request, comment or suggestion, please don't hesitate to contact me.
It's quite simple. Select The vehicle manufacturer or Global, enter the Diagnostic Trouble Code DTC, then press search and in case it appears within the 100,000 Trouble Codes, the description will be displayed!!
In addition, by pressing the "Search Web" button, it will search within Google for the relevant Fault Code.
This app is an excellent tool, for those who obtain only the OBD-II Trouble Code, but do not know what it means.
Please note that using this app does not require connecting to ELM / ELM327 device, or any other scanner. this is a standalone application!
In order to access over 100,000 Trouble Codes, you must have an active internet connection!
This App supports the following:
1. More than 100,000 Extended DTCs !!! (Specific Manufacturer Fault Codes).
2. Powertrain, Body, Chassis and Communication DTCs.
3. Global Trouble Codes for all vehicle manufacturers in the world!!
3. Specific Trouble Codes for all vehicles belonging to these manufacturers:
* Chrysler + Dodge + Jeep (Select Chrysler in app)
* Ford + Ford Truck + Lincoln (Select Ford in app)
* Honda + Acura
* Nissan + Infiniti. (Select Nissan in app)
* Toyota + Lexus. (Select Toyota in app)
Please try the free app version before buying the pro app!
DTC, Trouble code, fault code, obd, obd2, obd-ii, obdii, on-board diagnostics, vehicle, automotive, elm327, scanner, automotive diagnostic tool, error code, cars, onboard, check-engine, check engine. warning code, warning light, ECU, Oxygen Sensor, Throttle, PCM, TCM, Ottotest, Blue Streak Electronics, Ototest, Maf, ECM, error code, obdi, obd1, coolant temperature, vehicle speed, Actuator, Cylinder, Injector, Exhaust, Fuel, Gear, Ignition, Immobilizer, Motor, Passenger, RPM, mph, kmh, pedal, Yaw Rate.
- Simple and easy software OBD diagnostics
- You need an ELM-based interface
- Mode 6, Misfire, O2 Test monitoring results >
- Multi-vehicle support
- Readiness flags for your emission
- Export Logs to KML/CSV/TXT
Raw/debug logs option. Freeze/Pending Codes, Mode6 , Misfire readings with analysis charts. GPS logging option with KML , Placemarkers for Max/Mins and path of log mapping. O2 diagnostics mode sensors layout are displayed with current voltages Instantaneous Fuel consumption sampling/logging. Boost sampling. English and Metric units. OBD command expert to access directly the ECUs with scripting capabilities
Engine parameters can be sampled and logged e.g.RPM, Ignition Timing Advance, Speed, Throttle etc, Logs can be plotted, exported to CSV, TXT Excel(Desktop format). Option to include a cloud copy(Dropbox)
Updates are posted often and we are starting to include some Hybrid readings.
You will need an ELM32x based Bluetooth interface. MAKE SURE the lite version runs on your setup before purchasing
The software connects to Auterra's Bluetooth OBD II adapter included in the A-303 Dyno-Scan for Windows Bluetooth kit. A demonstration mode is built into the software that simulates all vehicle data so you can test the software.
Auterra's Bluetooth OBD II adapter is required to connect to a vehicle. The product supports 1996 and newer US vehicles including American, European, and Asian brands such as Ford, GM, Chrysler, Toyota, Honda, BMW, VW, Volvo, etc… Outside the US many vehicles are supported also (see Auterra website FAQ page for specific details).
Auterra's Bluetooth OBD II adapter supports Auterra’s Windows and Android software. The Android software is optimized for both phone and tablet platforms. Common file formats means you can record on Android and open file on a Windows PC.
Live data is recorded with vehicle position using your Android’s built-in GPS. Open files on your PC using Dyno-Scan for Windows and see the vehicle data and your vehicle position within Google Earth.
Record vehicle power/torque and acceleration and display graphically.
Auterra manufacturers all hardware and software for the Android, Windows PC, and DashDyno SPD platforms so all the products work seamlessly together. This free software was designed for Auterra customers using Auterra's Bluetooth OBD II adapter.
The Android users guide is available on our Downloads page or in the link below:
Dyno-Scan for Android key features:
* Connects to Auterra's Bluetooth OBD II adapter.
* Wirelessly view and record data from your vehicle using Bluetooth.
* Android and Windows PC platforms supported.
* Read/clear vehicle diagnostic trouble codes.
* Integrated DTC database with thousands for trouble code definitions.
* Software supports 264 live vehicle parameters.
* CAN 6x mode for 600% faster data throughput (vehicle dependent feature).
* Record vehicle sensor data and GPS position.
* Measure horsepower and torque.
* Measure acceleration times such as 0-60MPH and 1/8mile times.
* Measure vehicle overall gear ratio.
* Open Android recorded data (live data, power/torque and acceleration) on your PC using Dyno-Scan for Windows.
* Recorded GPS location is displayed within Google Earth on your PC.
* Easily save and load your favorite screen configurations.
* Numerous screen layout options with meter and graph widgets.
* Dynamic portrait and landscape orientation changes.
* Full gesture support including pinch-zoom graphs, drag zoomed graphs, and double-tap zoom.
Changeable components include:
Other engine simulators exist but none are specifically designed for the Type 1 engine. This is why Dub-Dyno is the best tool available when planning an engine.
Welcome to OBDII Trouble Codes database. You will find the most complete list of OBDII trouble codes available (3000+). The code definitions are a good starting point when determining the cause of the service light and will help you repair the problem. Diagnostic Trouble Codes (DTC) for 1996+ models OBD 2, OBD II.
P = Powertrain (Engine and Transmission, example code P1267)
B = Body (includes Airbags, example code B0013)
C = Chassis (includes ABS brakes, example code C1234)
U = Vehicle Network codes, (example code U2023)
It reads the fuel consumption data from the car computer in real-time, improving the reading accuracy, since most fuel economy applications on the market estimates the fuel consumption rate by reading the air intake.
Fuel-saving behaviors like smooth acceleration make the leaf meter glow green, while inefficient driving behaviors will turn the leaf indicator to yellow or red.
You can also share your current status (ECO Avatar and ECO Rate) on the social networks, allowing family and friends to keep up with your current progress.
*PLEASE NOTE* that other NISSAN models may be supported, but the plugin was tested only on the following models:
* 350Z 3.5 (Z33)
* 370Z 3.7 (Z34)
* Altima 2.5/3.5 (L32)
* Armada 5.6 (TA60)
* Frontier 4.0 (D40)
* Juke 1.6/3.8 (F15)
* March/Micra 1.5 (K13)
* Maxima 3.5 (A35)
* Murano 3.5 (Z51)
* Pathfinder 4.0 (R51)
* Qashqai 1.6/2.0 (J10)
* Sentra 2.0 (B16)
* Tiida/Versa 1.8 (C11)
* Titan 5.6 (A60)
* Xterra 4.0 (N50)
* X-Trail 2.0 (T31)
EcoDrive for NISSAN requires the latest version of Torque Pro installed in order to function. This is *NOT* a standalone application and will *NOT* work without Torque Pro.
1) After purchasing the application on Google Play, make sure that you see it listed on your Android device installed applications list.
2) Launch Torque and go to "Settings"
3) Make sure that you can see the plugin listed also on Torque Pro by clicking "Settings" > "Plugins"> "Installed Plugins".
4) Mark the "Allow plugins full access" box, since EcoDrive for NISSAN needs access to the OBD adapter.
5) Click on the plugin icon and select your car model on the MODEL tab and confirm
6) The app will display the ECO Leaf real-time information on the ECO MONITOR tab
7) Timers and detailed trip information will be displayed on the TRIP DATA tab
More features/parameters will be added in further releases. If you have comments and/or suggestions please just let me know.
Once you have the Lite version running and telling you about your battery you can then purchase either the full version "Leaf Spy" or the more advanced version "Leaf Spy Pro".
The Leaf Spy application allows anyone with a Nissan Leaf electric vehicle, Android device with Bluetooth and an ELM327 OBDII Bluetooth adapter the ability to monitor their battery and other vehicle information normally visible only to the dealer. ELM327 OBDII Bluetooth adapters typically sell for $10-$20 on eBay.
User generated guide: http://www.mynissanleaf.com/wiki/index.php?title=Leaf_Battery_Application
Information displayed by Leaf Spy Lite & Leaf Spy:
* Voltage of each of the 96 cell pairs (highlighted if shunt active)
* Minimum, average, maximum cell pair voltages
* Histogram of cell pair voltages
* Battery Temperature readings (4 sensors for 2011/12 models, 3 for 2013 models)
* Battery AHr rating (this will decease with age and is an indication of remaining capacity)
* Number of Quick Charge connections
* Number of L1/L2 Charge connections
* EVSE Max available amps
* EVSE voltage
Additional information displayed by Leaf Spy:
* Battery energy level in GIDs & kWh
* Resetable energy usage meter (Wh resolution)
* Graphic display of SOC, GIDs and DTE (Distance to Empty)
* Remaining distance meter (miles/km) to Event (Low Battery Warning, Very Low Battery Warning or Reserve) based on user selectable energy efficiency
* Graphic display of battery temperature with min, avg, max temperatures
* Tire Pressure of each of the four tires with low pressure warning and delta pressure warning alarm
* Ambient Temperature
* Logging function that records most data and optionally GPS location to a csv file that can be easily imported into excel.
You may want to purchase the "Pro" version which adds the ability to perform functions normally requiring a visit to the dealer.
* Change automatic door lock/unlock settings
* Read Diagnostic Trouble Codes (DTC)
* Register Tire Positions (required after tire rotation or seasonal tire changes so your Leaf knows the correct location of each tire on the car)
* Future ability to reset selected DTCs
OBD2 Fahrzeugdiagnose mit Ihrem Smartphone: Kfz-Fehlerspeicher auslesen, Kraftstoffverbrauch, Kühlmitteltemperatur und weitere Live-Messwerte anzeigen.
Via Bluetooth erhält Ihr Smartphone direkten Zugriff auf die OBD2 Schnittstelle des Fahrzeugs und wird somit zum erweiterten Bordcomputer. Neben der Überwachung der wesentlichen Motor-Parameter liefert die Diagnose- Schnittstelle auch Informationen zur einfachen Bestimmung fehlerhafter Aggregate und Sensoren.
Hinweise zur Installation:
- Stecken Sie den OBD2 Bluetooth-Adapter in den Steckplatz an Ihrem Fahrzeug und starten den Anlasser
- Schalten Sie Bluetooth an Ihrem Smartphone / Tablet ein
- Starten Sie die App
- Gehen Sie in das Menü „Einstellungen“
- Drücken Sie auf den Pfeil rechts im Bereich „Pairing“
- Suchen Sie nach „dnt OBD2“ und geben den Code 1234 ein um das Pairing zu starten
- Starten Sie jetzt in den App-Einstellungen die Verbindung mit dem Smartphone
- Bei korrekter Verbindung leuchten jetzt alle 3 Sysmbole im Hauptmenü blau auf (Adapter, Handy, Auto)
Android system: 2.1 or above 2.1
Includes option to specify vehicle year, make, model, and engine prior to searching. Search results include code description and forum discussions matching your vehicle and OBDII code.
Future versions will include ability to submit resolutions to codes in order to build database of fixes.
Get the description and the possible cause of the check engine code by searching for the code for all of the major manufacturers and now with quick access to your search history and save results to for use at a later date.
Acura, Audi, BMW, Buick, Cadillac, Chevrolet, Chrysler, Dodge, Ford, GMC, Honda, Hummer, Hyundai, Infiniti, Isuzu, Jaguar, Jeep, KIA, Land Rover, Lexus, Lincoln, Mazda, Mercedes-Benz, Mercury, MINI, Mitsubishi, Nissan, Oldsmobile, Pontiac, Saab, Saturn, Scion, Subaru, Suzuki, Toyota, Volkswagen and Volvo all on the go.
Don't get cheated by your mechanic. Have the facts with you.
The applications include: expert diagnosis, service reset, connect, history and other functions.
[Read DTCs] read the whole car more than 80 system fault code and fault code details.
[Clear] clears trouble codes vehicle fault codes for all systems.
 Read vehicle dynamic data flow stream value for all systems.
[Vehicle information] read ecu version information.
[Service Reset] This feature also includes the vehicle mileage reading, maintenance light reset, maintenance and zero oxygen sensor lights.
[Connect] under your car a part of your new record, this record can record your car's systems are supported, as well as the testing process all the data records.
[History] query and delete your testing process in the preserved records.
Note: Before using the system need to contact the Company to purchase special edition iOBD2 vw diagnostic connector (www.iobd2.com).
To use, please download SenseView application.
Service for OBD2 / ELM327 bluetooth automotive interface - supports 17 readings (Speed, Throttle position, RPM, Average engine load, MAF air flow rate, Barometric pressure, Ambient air temperature, Intake air temperature, Hybrid battery, Engine coolant temperature, Fuel pressure, Run time since engine start, Distance traveled with malfunctioning indicator lamp, Engine oil temperature, Commanded EGR, Commanded evaporative purge, Fuel Level Input)!
Install only with SenseView application (https://play.google.com/store/apps/details?id=si.mobili.senseview).
In case of problems try to pair / un-pair!
Warning: there are hundreds of different adapters available - we cannot test our service with all - please think about that before posting a negative review!
More info about supported sensors: http://senseview.mobi/supported-sensors.html
The application uses the device ELM327 Bluetooth Adapter OBD connector and to communicate with different vehicles.
ELM 327 Bluetooth Adapter is a device for the cars of joining through the 16-pin OBD diagnostic connector.
This application is a simple terminal that supports all device commands ELM327.
- The application includes a ready list of basic commands.
- Possibility clearing the terminal window
- Ability to write the log to a file
- The ability to type your own commands
PerfMon offers you four categories of metrics:
- Foreground App
- Disk I/O
- Network I/O
PerfMon will also show you a new and unique-to-PerfMon performance metric: "CPU Capacity Usage". The CPU usage percentage traditionally used to measure and compare how much of the computational resources an app (or the entire device) is currently using does not make sense in a mobile multi-core setting. The capacity metric will take the CPU usage and scale it to what it would be if all cores were running at full capacity.
For example: if you have a 1.6ghz quad-core running a light app, it could be using 10% CPU with only one of the four cores active, and that core running at 200mhz. If you translate that to all four cores running at 1.6ghz, that app is using only 0.3% of total CPU capacity.
It's the only CPU Usage metric that makes any sense!
--- Foreground App ---
This window shows metric of the currently foreground (running and visible) application:
- Application title
- Application package name
- Memory usage total (in megabytes)
- Dalvik, Native, and Other memory usage (in megabytes)
- Overall CPU Usage (normal percentage and capacity)
- User and System CPU Usage (normal percentage)
--- CPU ---
This window displays overall CPU metrics:
- Capacity usage and current divider
- Overall CPU usage percentage
- Per-core CPU usage percentage and megahertz
--- Disk I/O ---
This window displays the disk I/O metrics of your MMC-based storage devices. Usually, mmcblk0 is your internal flash, and mmcblk1 is your removable SD-card. Please note that currently MTD-based storage is not supported by this display. Also note that the metrics displayed are raw I/O, so if the OS has I/O requests buffered/cached, you will not see anything happen here.
- Per-device read and write kilobytes/second
--- Network I/O ---
This window displays the network I/O metrics of your network interfaces.
- Per-interface transmit (Tx) and receive (Rx) kilobytes/second
If you do have a gyroscope, be aware that the quality of the drift compensations on the gyroscope sensor vary considerably among devices. In the case that your device has a gyroscope that doesn't work well, there is the option to fuse the gyroscope with the acceleration and magnetic sensors. This option, which uses a fusion of the acceleration, magnetic and gyroscope sensors via complementary filter to determine the rotation of the device, is far more reliable that the gyroscope sensor alone.
Gyroscopes measure the rotation of a device with a pair of vibrating arms that take advantage of what is known as the Coriolis effect, which is caused by the Earth's rotation. By measuring changes in the direction of the vibrating arms caused by a rotation and the Coriolis effect, an estimation of the rotation can be produced. The gyroscope is one of three sensors that are always hardware based (the other two are the magnetic and the acceleration sensors) on Android devices. In conjunction with the acceleration sensor, the gyroscope can be used to create other sensors like gravity, linear acceleration or rotation sensors.
If your device is equipped with Android 4.4 or higher, you *might* have the uncalibrated version of the gyroscope so you can see how drift affects the gyroscope sensor relative to the calibrated gyroscope.
The linear acceleration of an object is calculated as the acceleration of the device minus the force of the earth's gravitational field ( the tilt of the device). Gyro Linear Acceleration uses a complimentary filter to fuse the acceleration sensor and gyroscope sensor together to provide a measurement of the devices linear acceleration. The acceleration sensor alone is not capable of distinguishing true linear acceleration from tilt, or gravity. The gyroscope sensor is used to find the tilt of the device. The tilt angle of the device can then be used to calculate the gravity component of the acceleration that can then be subtracted from the acceleration to find the linear acceleration.
Most people will find that the end-result of this implementation is that, while linear acceleration can be measured while the device is static (not accelerating), linear acceleration cannot be accurately measured while the device is actually under linear acceleration. This is because the complementary filter, which is used to compensate for the drift of the gyroscope, begins to assume the acceleration of the device is actually tilt, skewing the rotation measurements from the gyroscope.
Related to the linear acceleration problem is that the gyroscope sensor can easily drift out of rotation with the device when it is experiencing vibrations or rapid rotations, even with the help of an acceleration sensor. If you modify the complementary filter to quickly compensate for gyroscope drift with the acceleration sensor, you increase the problem of the complimentary filter confusing linear acceleration for tilt when the device is actually accelerating.
Gyro Linear Acceleration may work well for determining linear acceleration for a static device, for instance, that moves a character or vehicle in a game by tilting the device. Gyro Linear Acceleration will not work well for determining the linear acceleration of a vehicle or other object that actually accelerates the device.
Gyro Linear Acceleration will plot the output of the sensor fusion in real-time and will also log the data to an external .CSV file that can be viewed at a later time on any spreadsheet application.
• Plot data in real-time
• Analog gauges to visualize the outputs
• Log the output to an external .CSV file
Discover how low-pass filters work on acceleration sensors by viewing the outputs in real-time. Acceleration Filter runs multiple low-pass filters at once so you can compare the results from a single input quickly and easily. The output from the filters is plotted with a line graph while the noise is plotted with a bar graph. There is also the option to view the acceleration as a two-dimensional vector. The user can select the sample period in units of seconds to apply to the different filters. This allows user to explore a large number of filter settings to quickly determine what is best for their application. Perfect for visualizing the effect of low-pass filters on digital signals. You can even log the output to an external .csv file.
• Graph acceleration in real-time
• View signal noise in real-time
• Compare multiple low-pass filter configurations simultaneously
• Define how the low-pass filter calculates alpha, or, set alpha to a static value
• Define windows for moving average filters
• Log filter outputs to an external .csv file
• Complementary IIR Low-Pass
• FIR Moving Average
An accelerometer can measure the static gravitation field of earth (like a tilt sensor) or it can measure measure linear acceleration (like accelerating in a vehicle), but it cannot measure both at the same time. When talking about linear acceleration in reference to an acceleration sensor, what we really mean is Linear Acceleration = Measured Acceleration - Gravity. The tricky part is determining what part of the signal is gravity.
It is difficult to sequester the gravity component of the signal from the linear acceleration. Some Android devices implement Sensor.TYPE_LINEAR_ACCELERATION and Sensor.TYPE_GRAVITY which perform the calculations for you. Most of these devices are new and equipped with a gyroscope. If you have and older device and do not have a gyroscope, you are going to face some limitations with Sensor.TYPE_ACCELERATION. Note that the implementations of Sensor.TYPE_LINEAR_ACCELERATION and Sensor.TYPE_GRAVITY tend to be poor and are skewed while the device is under periods of true linear acceleration.
A low-pass filter is a filter that passes low-frequency signals and attenuates (reduces the amplitude of) signals with frequencies higher than the cutoff frequency. The actual amount of attenuation for each frequency varies depending on specific filter design. To find the gravity component of an acceleration signal, a low-pass filter is used to pass the long term portion of the signal (which is assumed to be gravity) through the filter and to attenuate everything else. The gravity component of the signal can then be subtracted from the original acceleration signal to find the linear acceleration.
• Log all sensor data to a .CSV file
• Analog gauges display the tilt and acceleration of both the acceleration and linear acceleration sensors
• Plot sensor output to visualize data in real-time
• Visualize acceleration in two-dimensions with a vector view
• Adjust the time-constant of the low-pass filter to your needs
• Adjust the acceleration sensors output frequency to your needs
Acceleration Explorer allows the user to investigate the noise, offset and skew associated with the accelerometer sensor on Android devices. After a quick calibration process, Acceleration Explorer will calculate the magnitude of each axis and the noise associated with it. Acceleration Explorer also determines the minimum and maximum amplitudes of each axis along with the update frequency of the acceleration sensor.
Why would you want to know about noise, offset and skew?
We want to know about noise, offset and skew because they are aspects that make the sensor less accurate that we can partially compensate for. For example, you may want to implement a low-pass filter or mean filter to smooth the acceleration sensors output and knowing how much noise the sensor has is very useful. Or you may want to know how accurately your device measures gravity, tilt or acceleration.
Acceleration Explorer makes it easy to compare the performance of the acceleration sensors of multiple devices. Not every Android device is the same and knowing the range of how acceleration sensors perform can be very helpful.
Write better code!
Acceleration Explorer can help fine tune your acceleration sensor algorithms.
Linear Acceleration Sensor is intended to provide developers with code examples and an application to quickly test devices for an implementation of Sensor.TYPE_LINEAR_ACCELERATION. Some Android devices provide an implementation of linear acceleration with Sensor.TYPE_LINEAR_ACCELERATION, others do not. The implementation and performance of Sensor.TYPE_LINEAR_ACCELERATION varies from device to device. Some devices rely on low-pass filters, some fuse the magnetic and acceleration sensors, some fuse the gyroscope and acceleration sensors and others do not implement linear acceleration at all.
Almost all implementations of Sensor.TYPE_LINEAR_ACCELERATION are poor. The implementations succesfully isolate gravity from the acceleration under static conditions. However, while the device is actually under linear acceleration, the gravity compensation tends to be overestimated skewing the linear acceleration measurement. Linear Acceleration Sensor is ideal for discovering the limitations and performance of Sensor.TYPE_LINEAR_ACCELERATION.
• Log all of your data in real-time
• Analog gauges to display the outputs
• Real time sensor plots to visualize performance
The magnitude and sensitivity of these dangerous driving events can be defined by the user. Once a dangerous driving event is detected, the data occurring a short period before the event and the entire event are logged to a .csv formatted file and saved to a folder on the device. The data log can also be emailed to a Gmail account. Note that we do not collect any of the trip information, but the application can be set up to share trip information with yourself or other parties. This makes Acceleration Alert ideal for monitoring your own driving behavior or the driving behavior of many people.
Acceleration Alert supports linear acceleration optimized for vehicle use on all devices. This means that the application can operate in any orientation, there is no need to "level" the device or mount the device (although the device should always be secured while in a vehicle).
- Record your route and any dangerous events during the trip
- Define the magnitude and sensitivity of the dangerous events
- View acceleration data from dangerous events in real time
- Mount the device at any angle, no need for leveling
- Log the vehicle acceleration, speed, location and time during a dangerous event
- Email log files to a Gmail account
- Support multiple drivers
Continued use of GPS running in the background can dramatically decrease battery life.
Smarter than your average compass! Compass Geek can be calibrated to work in places most compass applications will not, like in a car, boat or plane. There are a number of compass applications available, but Compass Geek exists because I needed a compass that could be calibrated to work in a car and I couldn't find one. Compass Geek is capable of correcting for the hard and soft iron distortions in the local magnetic field caused by metals and electronics.
Compass Geek attempts to produce the most accurate compass possible by optimizing sensor fusions for your Android devices specific hardware. Compass Geek provides both hand-held and vehicle modes for vehicle-docks and can even compensate for hard-iron offsets produced by a vehicles metal frame and electronics. Compass Geek can be calibrated to work in most cars, planes or boats and works where many compasses will not.
In addition to a compass, Compass Geek supports Google Maps so you can see your location in Google Maps anywhere in the world!
Choose from up to eight unique gauge skins to get the look and feel you want. You can even graph the bearing in real time to see just how awesome your compass is working.
• Tilt compensation from the gyroscopes and acceleration sensors are used to compensate for the tilt of the device
• Magnetic declination compensation for earth’s magnetic field with the GPS sensor
• Hard-iron offset calibrations for vehicles like cars, planes and boats
• View the bearing from the magnetic field and GPS as well as the location
• Measure the rotation of the device and the magnitude of local magnetic field
• Alerts when the magnetic field is out of the expected range
• Select from 8 unique, super awesome hardware accelerated gauge skins
• View the bearing, magnetic field, rotation of the device, the location of the device and more