GPS tracking and navigation wrong - Android 4.2.1.

[bomme...@googlemail.com]

Hi all,

I recently bought a new smartphone: Acer V370 ( Liquid E2 duo). The problem with OSMand+ and some other apps using GPS is, that the tracked and navigated distances are far too long. My last bike ride was, according to OSMand+, 220km. Actually it was only about 17. The same applies to my speed etc. I have read in several forums, that this is a known problem for Android 4.2.1 devices. 

As the summer gets closer and closer it would be absolutely fantastic, if anybody could provide help in this matter.

P.S.: Navigation with GoogleMaps and Navigon works fine. The wrong distance thing however occurs with Endomondo pro and Runtastic pro as well.

Cheers in advance.

[Victor Shcherb]

This could be problem related only to Logging (which could be fixed in external program).

I checked where it is used and this problem might be fixed in next release.

Victor

--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[bomme...@googlemail.com]

Cheers Victor. That keeps my hope alive that OSMand will be my favourite app in the future.

Looking forward to receiving the next update request in Playstore.

Seb

[bomme...@googlemail.com]

Just checked the Osmand+ beta 1.4. Unfortunaetly the problem is still the same. 

[JeCh]

I can also confirm the problem is still there. I somewhere read it is related to my chipset (MT6589) and Android 4.2.1. The strange thing is that some applications show the navigation information right and some not.

Which chipset do you have in your phone?

Vladimir

Dne sobota, 8. června 2013 10:06:44 UTC+2 bomme...@googlemail.com napsal(a):

[bomme...@googlemail.com]

According to the manufacturer ACER, the Liquid E2 Duo also has the MTK6589 and Android 4.2.1 in it. Indeed the strange point is, that other apps can process the data correctly whereas some can't.

[Max]

Seems to be related to:
https://groups.google.com/forum/#!msg/osmand/JLkYi1JjdDU/g0UvrwMeD9YJ

But I am not sure, if this is a CyanogenMod or an Android bug.
At least CyanogenMod fixed it:
https://github.com/cyanogenmod/android_dalvik/commit/6799723387fe725e5418a83d2762539530a8835c

Android bug report:
https://code.google.com/p/android/issues/detail?id=41911

Regards,
Max

[Max]

Now I am sure, it is an Android bug (not a CyanogenMod only bug).

This bug was introduced on November 30, 2012:
https://android.googlesource.com/platform/dalvik/+/c83353bc0d7ddfedd3bc06fdb12f25710191e1e6

CyanogenMod fixed it on January 06, 2013:
https://github.com/cyanogenmod/android_dalvik/commit/6799723387fe725e5418a83d2762539530a8835c

Google fixed it on April 26, 2013:
https://android.googlesource.com/platform/dalvik/+/4888a4b95e2f1b2cdeb6a0ca8dd75c784eb80256

Regards,
Max

[bomme...@googlemail.com]

Thank you Max. However, I am just a simple user and have no clue regarding coding etc. Do i now have to edit the code? Where do I find the file?

Thanks for your help and again sorry for my eagerness :) 

[Max]

You can wait until Acer releases a fixed Android for your phone and install this release.
Or you can try to install an other Android distribution like CyanogenMod (only latest versions, without this bug), but if you want to do that, you should really know, what you are doing.
Or you can wait until someone implements a workaround for OsmAnd, which avoids to trigger this bug:
https://android.googlesource.com/platform/dalvik/+/4888a4b95e2f1b2cdeb6a0ca8dd75c784eb80256

To make it clear:
The Android version on your device has a bug, causing miscalculations under mentioned conditions.
This potentially affects all apps, not only OsmAnd.

Thus, the best way is to use a fixed Android version, not to implement a workaround in every single Android app.

Regards,
Max

[bomme...@googlemail.com]

Thanks a milion. It is of course a pity that OSMand+ doesn't work properly, but I think I am going to survive till it is somehow fixed.

As I said before, it doesn't affect all apps, just some of them.

Anyway cheers again.

Best wishes

Seb

[Victor Shcherb]

Thank you Max!

I was wondering where do we use an Android API and apparently we use Java doubles :) Unexpectedly...

Victor

[Max]

Hi Seb and Vladimir!

Maybe Victor fixed that issue:
https://groups.google.com/forum/#!msg/osmand/qo0DCl9rz6E/HYWrrD6G6B4J

Please could you test the latest build and tell us, if the issue is fixed:
http://download.osmand.net/latest-night-build/OsmAnd-r1.5-default.apk

Regards,
Max

[Lieke V]

Same phone, Acer V370, same problem. First smartphone, new to Android, so no rooting for me.
Bought it for navigating on hikes, so it is an issue.
Would like to test latest build, downloaded it, but app won't install.
Got the warning about possible damage, told phone to download anyway.
What did I miss? Regards, Lieke

Bought the phone for navigation

Op donderdag 1 augustus 2013 12:42:34 UTC+2 schreef Max:

[Max]

Hi Lieke,

meanwhile, 1.5.2 has been released, this version contains the potential fix.
You can update via Google Play Store and test.

Now, you don't have to download it via osmand website and you should not have this problem anymore:

Would like to test latest build, downloaded it, but app won't install.
Got the warning about possible damage, told phone to download anyway.

Regards,
Max

[Lieke V]

Thanks Max,
Now it looks a lot better! Before I was told the bus stop at 1.4 km is an 8 hour walk.
Hopefully Acer will update anyway, but for Osmand the problem is solved.
Thanks again. Lieke


Op maandag 5 augustus 2013 10:27:15 UTC+2 schreef Max:

[ml]

This is a common issue in MTK6589 phones and to solve it you need to have :

1- Rooted phone (Example use faramaroot)

2- Install Xposed Farwork

3- Download Gravity Box from xposed framwork 

4- check the the GPS fix in MTK6589 fixs 

[Max]

It is a JIT bug:
https://groups.google.com/d/msg/osmand/1RlEPzEU2Co/5EoK14_IxJQJ

To avoid this issue, OsmAnd reimplemented location calculations, so that only floats are used, no doubles.

Regards,
Max