Messages

mounts and vold.fstab

New version 3.1.1 is really funny. It recognizes all links created by FolderMount as suitable locations for Root directory. The actual path to SD Card (/storage/external_SD/) is not in the list.

I have installed new version 3.1.0 and still unable to move root directory to the root of external SD Card.
Location /storage/external_SD is not in the list of available choices.

Hallo,
I cannot place Locus root directory on external SD Card.
My device is LG L90 D410 with Android 4.4.2.
Path to internal memory - /storage/emulated/0/ (Locus detects internal memory).
Path to external SD Card - /storage/external_SD/ (Locus does not detect external SD Card).
My device is rooted and platform.xml is altered to allow write access to external SD Card.
Is it possible to add detection of my external SD Card path (/storage/external_SD/) into future versions of Locus?

One more illustration for this bug.
Importing track (35 points, 5 km length) into Locus.
I have imported this track 6 times, before each import I have changed zoom of displayed map. The results of each import are different. One time Locus was able to import track correctly. Other 5 imports are false.
[attachment=0:3opoikzm]locus_bugs.jpg[/attachment:3opoikzm]
[attachment=1:3opoikzm]5km.gpx[/attachment:3opoikzm]

I use Locus Pro 2.10.2 on device with android 4.2.1. Display size is 5.7 inch, resolution 1280x720.

Scale indicator behave absolutely erratic on personal maps in SQL format. It shows random values. On attached screenshot scale length is 4 km at 17th zoom, while it's actual length should be ca. 180 m.
[attachment=0:fmxy5pku]1.jpg[/attachment:fmxy5pku]
Moreover Locus uses this erratic scale values for speed and distance calculation. So after a short walk (ca. 4 km in 1 hour) I got very funny recorded track with 65 km track length and average speed 67 km/h.

I guess, program uses BYTE data type for dpi value. Dpi of my screen is more then 256, so the program cannot process it.