Messages

Is there any possibility to download the installation file? It would make it much easier to edit eight data.

Auto-pause: I still do not know what to think about it, cause I also noticed some malfunctions and see no space for some improvements on my side. Will test it, but from my point of view, it is currently not ready to release.

Hi Menione, autopause works quite well with shorter stops. What just add a feature that would check each minute according to GPS, whether the phone had not changed the position? And if so, it would cancel the autopause.

I did some tests with AutoPause. If the phone is in rest for a few minutes, the recording does not turn on even after 250 meters. I tried to make several SCR sensors.
Image "Start" - Recording is in Autopause.
Image "Finish" - after 250 m walk, Autopause is still active. The sensors are active and the GPS has turned on after the display is lit.
Note: The recording after a long autapuuse will start immediately if I make any Bixby command. The recording also starts the screenshot using the buttons on the mobile.

4.12.2.4: The new movement sensing/ auto-pause evidently (sometimes) isn't working for me - see screen cap of map where phone was perfectly stationary for 70 minutes with GPS still enabled.

During this 70 minutes it can be seen the GPS accuracy (from LM web planner) jumped from ~3m to ~40m accuracy, as expected in bottom of a multistorey concrete building.

I found that AutoPause only activated if the phone has a good GPS signal. If the recording is still jumping, Autopause does not succeed even when the phone lies on the table.

[@Josef Žajdlík]

@Josef Žajdlík
It may take a while till the system register and report the movement. You may check what activities the system currently detect in the top app toolbar. Did you tried it?

Hmm now I see that on my old Pixel 2, I still see only "Activity recognition: enabled" and not exact activities. This anyway works correctly on Pixel 5 A13, weird.

The A53 is shown. The problem is that I don't read them without glasses. But I will try to do SCR when I test it and the record does not start. Last time I waited about half a kilometer of walking and I really had to run it by hand.

[@freischneider]

@freischneider & @Josef Žajdlík
hmm long pause cause a problem ... will have to test but it may be a major problem 

Description of the situation: Start of the record already at home, the phone lay on the table. The record immediately switched to the pause. Leaving the house after about 15 minutes, but the record did not switch to the recording.

I had problems with the car break today.
Start recording
100m driven
Break (waiting for passengers, about 8 min.)
Continued driving but no more recording.
My settings in the picture. Do you need more settings ?

Same problem today. A short break is not a problem. If it is several minutes, the recording will not start again.

The autopause test during four hours of hiking turned out excellent. No unexpected lines.

Clicking on any Lopoint Locus crashes. Android 12 on the phone and 11 on the tablet.

Hi Menione, the first test "Autapause" on the Samsung A53 (A12). According to the upper bar is reading the activity OK. But there is no control when AutoPause is active. Upon arrival in the building and laying the phone on the table, "drift" was created in the record. See SCR.

"record only when moving" use speed reported by the GNSS unit. Anyway even if not moving, it still only ignores location data but does not pause recording at all. For this, I already have prepared a system using "Google activity recognition", but I was never able to finish it for some public test  . This should allow to detect of changes in movement style so react on pauses or inform about activity & paused recording.

I think the quality of the recording at stop is now the biggest problem of Locus records. The solution should not be dependent on the vote. Other applications with this have no problem with this.

Today all mobiles have an acceleration sensor. This should be used to detect movement. Or not?

you probably find only 0.01% of users use Presets, so far bigger fish to fry; maybe there are analytics behind the scenes to justify development in certain areas

Andrew Why do you think so? I think Locus Presets needs. Without them I can not even imagine using locus.

@Žajdlík Josef - LM4 5M+ downloads, LM3 probably even more, but just a few regular beta users in this forum. I agree with you Presets are a great power-user feature but it would be interesting to see how many out of 10M+ Locus users are aware of & use this feature. I'm just trying to say with limited developer resources there are possibly more important areas to develop that would give more bang-for-your-buck for more users.

In this review of 6 best navigation apps for bicycle touring https://wobblyride.com/2022/03/29/best-navigation-apps-for-bicycle-touring/ sadly IMHO Locus is not mentioned. I have experimented with all other 6 apps (long time ago) and settled on LM as the best. I would suggest every LM user who reads the review, adds a comment to promote LM and provide wider exposure.

All cyclists and tourists I know want a simple application of free Mapy.cz do not want to think about the settings and options that Locus applications offer. I think that the Locus team knows it and does not compete directly with them. Mapy.cz or Google have big teams of people.
I agree with Menion that the presets will have to be modified, but it takes more discussion on this topic.

you probably find only 0.01% of users use Presets, so far bigger fish to fry; maybe there are analytics behind the scenes to justify development in certain areas

Andrew Why do you think so? I think Locus Presets needs. Without them I can not even imagine using locus.

I also like the current situation. Perhaps it would be enough to add alerts for starting users when creating a new preset: "The current settings will change if you make changes to the preset settings settings. If you want to keep the settings, save it as a separate preset"