Database Info

Latency when using sensor data?

Hey, guys!
I am working on a project using HTC magic which requires the data from the electronic compass, including both the accelerometer and magnetic sensor. But I find that there is a significant latency between the move of the phone and the trigger of the sensorChanged event. In other word, the acceleration and magnetic data obtained from sensor are updated about half of a second after my motion. And I have several questions about the problem as follow.
1. Are the orientation data computed by the acceleration and magnetic data? Or are there a physical sensor for orientation?
2. Does the latency result from the android API (using the event) or the physical limitation of the electronic compass?
3. It is said that the model of the electronic compass is AK8976A from Asahi Kasei. Does anybody have the datasheet or know the frequency of the sampling?
4. Any idea to improve the real-time experience?
Thank you in advance!

[Q] Difference - Gyro Sensor & G-Sensor

Hi,
Is there any difference between G-Sensor and Gyro Sensor?
HTC Sensation specifications states both sensors
Sensors
Gyro sensor
G-Sensor
Digital compass
Proximity sensor
Ambient light sensor

There is, but it's kinda subtle.
A G-sensor (accelerometer) can measure the change in acceleration of the device towards a direction. If you move the handset with a constant speed (no acceleration) then it shouldn't pick any signal. However, when moving their hand people change the speed slightly so an accelerometer picks that, but it will look sluggish.
A gyroscope can measure orientation, rotation and speed, so it can complement data collected from the accelerometer to smoothen out the reading of movement a great deal.
It's not the most important thing ever, but it's definitely a plus. Apps that use gyroscopes (mostly games and augmented reality apps) behave way more smoothly with it.

To put it more simply: The G-sensor measures the movement of the device. (By measuring acceleration). The gyro measures the tilt. They can work together to get more precise measurments of both.

Thanks for the explanations Guys...

[Q] What's the use of GYRO when we have Accelerometer and Compass?

My phone already has ACCELEROMETER and COMPASS. Why would I need GYROSCOPE? Can somebody give me example of practical applications that use Gyro sensor that the other two cant handle?
thanx

good question. Gyro is an extension to the accelerometer. It help you move with the devise in the same time. I see it being used on google street view (when u turn left/right the map is turning too) and in some shooting games.

Turn left right? Isnt that covered by the compass?

Bump!
Plus about the Atrix 4G...
Accelerometer, still no games utilises 6dof, if there is, not practical (like walking while holding the phone)
I guess the gyroscope mainly assists the GPS info + Compass...
Take it as like this:
Gyroscope assists Compass in rotation speed ( so u get real time)
Gyroscope assists accelerometer in pre-calibration proccess... (+ shaking games)
So I still argue with games like Asphalt 6 not working with accelerometers...
Both Gyroscope and Accelerometer are Fused, or Fusion proccess (combing the raw data map) so it will be enough real time...
Though 6DOF experience using a gyro is too useless for its accuracy... It comes hand when you buy a 400+ bux gyroscope Like headtracking systems...

[Q] How is navigation related data passed?

HI!
I am totally lost. I have several phones that have GPS and interial sensors like compass, gyro and g-Sensor. I have some older phones with cROMS that support navigation perfectly. Now I got a phone that picks up satellite data very fast, but I bet it does not correctly provide the sensor data to the navigation.
Result: It picks you up on gmaps, sygic or navigon, but if you drive and turn right at a crossing, the pointer on the map goes straight onwards. After some time it then jumps to your correct position. I tested different navigation apps and all of them behave a bit different as they use different alogorythms to keep you on track, but all of them fail, as they seem not to get valid g-sensor, compass and gyro data.
But if I start an app like androsensor, I can see that the show, roughly guessed, correct values...
So now I am puzzled! How does android provide sensor information to a navigation application? Is there a test framework in AOSP/CM to check if it works, is there a description or is there anyone who can help me a bit to find the right track in the software?
Btw. I checked NMEA strings and they do not inherit data about magnetic compass or bearing, velocity and accelleration. But they dont too in all my other phones, that worked really good with navigation.
Thank you in advance for any hint or trick
Astralix

improper sensors work

Hi
I have a problem with sensors. Sometimes they work, and sometimes they don't (Compass Magnetometer, Proximity sensor, Accelerometer, Ambient light sensor, Gyroscope). Checked also service tests (*#*#7378423#*#*).
I bought Z3 as used device. Had to replace microphone and week later LCD. Everything was working properly before and after replacing elements except sensors.
What can be the cause?
I have android 6.0.1 since I have Z3

When you check proximity sensor in service test does it works?
For me it seems like something was crashed or not connected properly because jack, microphone, proximity and ambient light is connected with one flex tape .
P.S. Today I had to disassembly Xperia Z3 because there was also problem with proximity sensor - at my case it works from time to time in service menu. Finally my problem was solved after revoming dust

If the sensors work, they work everywhere. Everything seems to be fine, also in service test. But if they don't work, also service tests are fail.
Proximity sensor and Ambient light sensor are on this element
gsmforyou.pl/files/313240969/tasma_gniazdo_zlacze_hf_czujnik_sony_z3_d6603 .jpg
but Compass Magnetometer, Accelerometer, Gyroscope are on mainboard.
So why they all don't work at this same time? I could change the element from the link but will this solve the problem?