Android - Longitudinal Acceleration only shows "0.00 g"
Posted: Thu Dec 26, 2013 4:58 pm
Hi,
I've been doing some testing of HLT Android in normal traffic conditions and realized that the longitudinal acceleration is not recorded (and possibly calibrated) properly. In fact, the gadget in GPS screen and the recording only display "0.00 g" values.
I tried to force a calibration via the "Max G" gadget in the GPS screen. After that, lateral acceleration instantly showed realistic values, while longitudinal acceleration remained unchanged at 0.00 g.
I know that HLT is using hard braking manouvers to calibrate the acceleration sensor in longitudinal direction. So this might be one reason that the calibration did not finished. However, I tried to simulate the calibration by putting the mobile phone in a landscape upright position, triggered forced calibration and then tilted the phone in a horizontal position a few times for a few seconds each until the popup window closed automatically. THis was meant to mimic a 1 g braking manouver. Also, this didn't change the value of 0.00 g for longitudinal acceleration.
When I do forced calibration on my iPad HLT Grand Prix version (using the same "simulated braking procedure"), I instantly get longitudinal acceleration values. So possibly, is there some bug in HLT? Anyone else noticed the same problem?
I can exclude a defect accelerometer in the Android phone by some other apps.
BR,
MIchael
I've been doing some testing of HLT Android in normal traffic conditions and realized that the longitudinal acceleration is not recorded (and possibly calibrated) properly. In fact, the gadget in GPS screen and the recording only display "0.00 g" values.
I tried to force a calibration via the "Max G" gadget in the GPS screen. After that, lateral acceleration instantly showed realistic values, while longitudinal acceleration remained unchanged at 0.00 g.
I know that HLT is using hard braking manouvers to calibrate the acceleration sensor in longitudinal direction. So this might be one reason that the calibration did not finished. However, I tried to simulate the calibration by putting the mobile phone in a landscape upright position, triggered forced calibration and then tilted the phone in a horizontal position a few times for a few seconds each until the popup window closed automatically. THis was meant to mimic a 1 g braking manouver. Also, this didn't change the value of 0.00 g for longitudinal acceleration.
When I do forced calibration on my iPad HLT Grand Prix version (using the same "simulated braking procedure"), I instantly get longitudinal acceleration values. So possibly, is there some bug in HLT? Anyone else noticed the same problem?
I can exclude a defect accelerometer in the Android phone by some other apps.
BR,
MIchael