Sample not working about mad-location-manager HOT 8 CLOSED

@al-t
Hello.
There is some misunderstanding here, my fault. Sorry for that.
It's not possible to use just accelerometer. We need TYPE_ROTATION_VECTOR (it uses magnetometer and accelerometer as I understood from sources) OR we need accelerometer+magnetometer+gyroscope(optional) for Madgwick filter.
These two ones are used for getting phone orientation. With phone orientation we can use accelerometer as INS.

If you don't have these sensors (magnetometer at least) you can use GPS only based solutions, just using realtime geohash filter (class in current solution). It will remove "jumps" from route at least. Also you can use this solution.

from mad-location-manager.

Hello there :)
Seem's like something wrong with sensors : there is no any information about acceleration in logs. So could you check that application has rights to get data from linear accelerometer , magnetometer and gyroscope sensors?

from mad-location-manager.

Yes, thanks - you are quite right!
I checked for the sensors that I've got on the phone and found out that I have only the TYPE_ACCELEROMETER sensor, but not the TYPE_LINEAR_ACCELERATION (the types are taken from here). Could the TYPE_ACCELEROMETER be used instead of the TYPE_LINEAR_ACCELERATION sensor?
Also, there are no magnetometer or gyroscope sensors installed in the phone.
Which means - the phone is not suitable for the Mad Location Manager?
Could you please write - what are the minimal requirements for using it?

from mad-location-manager.

You don't have "TYPE_LINEAR_ACCELERATION" , right? That mean that you have really old phone :))
We use TYPE_LINEAR_ACCELERATION and TYPE_ROTATION_VECTOR. So there is a lot of work if your phone has not these sensors.
We can use high-pass filter with usual TYPE_ACCELEROMETER.
Also we can use Madgwick filter (as I wrote in (article)[https://blog.maddevs.io/reduce-gps-data-error-on-android-with-kalman-filter-and-accelerometer-43594faed19c]) or some good alternatives with older phones.

from mad-location-manager.

Hey @Lezh1k i face the same issues with some old phones.
Is there any configurations with which i can use this phone
https://www.devicespecifications.com/en/model/bd123fc8
It is a Tp link neffos y50 with Proximity and Accelerometer sensor.
I guess we are missing magnetometer and gyroscope for TYPE_ROTATION_VECTOR?

Could you please write - what are the minimal requirements for using it?

This would be very helpful and would avoid future issues on this subject.

Thank you for your awesome work 🖖

from mad-location-manager.

@spiritinlife , @al-t
Thank you for feedback.
I'll add minimal requirements to readme.md.

Right now these sensors should be available:
TYPE_ROTATION_VECTOR, TYPE_LINEAR_ACCELERATION .

It's possible to use just TYPE_ACCELEROMETER with high-pass filter. Also it's possible to use Madgwick filter instead of rotation vector, but gyroscope and magnetometer should be available in that case.

from mad-location-manager.

Thank you very much for you help!

You wrote that It is possible to use just TYPE_ACCELEROMETER with high-pass filter.
I'm considering adding such an option for the low-end phones segment. I gather, for that I need to filter out the acceleration due to gravity from sensors output and use the refined linear acceleration in Kaman filter as if it was received from TYPE_LINEAR_ACCELERATION sensor. But as I see it in onSensorChanged method of KalmanLocationService, the data is passed to SensorGpsDataItem along with magnetic declination, which I believe can not be obtained without magnetometer. Am I right? So, how can we actually use the Kalman filter with only a general accelerometer? Will it be possible to use your library with minor tweaks in it or it will be a whole new story?

from mad-location-manager.

Great, thank you!

from mad-location-manager.