Re: [APP] - version 4.35.+ ( 06/2026 )

[Gerhard57]

New function in 4.35.0

pin the chart on the track detail screen so only the chart and the map stay visible;

doesn't shrink the detail windows any more since last 3 or 4 beta versions

[Tapio]

I don't like surface/way types to be pinned with it, but that's personal preference.

A click on the arrow as in screenshot, also in the pinned state, tends to CTD LM.

Happened also in the last beta. I think it's happening with self-created tracks, which may include some fake values? Screenshot2 shows such a track, where sometimes it crashes. I can see it only building the top 2 graphs, then crashes.

[Gerhard57]

@Tapio
I only have silver status, so no way types are shown, Don't know if that's the reasonYou cannot view this attachment.

[slarti76]

Reproducible bug observed in 4.35.0.8:
In track editor, "Insert/Edit trackpoint" will remove all gaps in the editable area.

[Cyklo Miro]

@Cyklo Miro
Please check the app settings > Geocaching > Your (owner's) name option. It still use the old way - manually defined name.

Yes, the problem was in the settings. I entered my nickname and it's fine now. But I definitely hadn't deleted it before...

[Cyklo Miro]

My wish:
I often need to show or hide an entire folder of caches. Currently, this requires two clicks:
1. Click the "eye" button.
2. Click "Display all" or "Hide all."
It would be faster to simply long-press the "eye" button to toggle the state. Without moving my finger 

Thanks

[Menion]

@Christian
sorry to read about your experience. It may be a memory problem. S7 is quite old and on the edge of what may be enough to run the app. It is not just about "some charts...". In the background, the code has grown together with external libs etc. It is a natural progression that can't be stopped.

Anyway, back to the problem > what I need is ... something. A log? The best is a long-click on the main menu > "Upload to support" at the moment, any problem happens. Without it, I have nothing to check, sorry.

@Gerhard57
I'm unable to simulate your issue with the empty space below the charts. In some of the recent Beta versions ws a change in how this is computed, so it is probably already solved.

@Tapio
any track that leads to crash > share it please with Track detail > Share > Share by link. Thanks.

@slarti76
missing gaps > thanks, fixed

@Cyklo Miro
lost "owner name" > I need to remove this setting and use simply the logged-in user. Later
long click on the eye > well, it won't be clear what this action will do without looking at the stats to see if anything is already loaded or if all is already loaded. So rather now for now.

[Gerhard57]

@Gerhard57
I'm unable to simulate your issue with the empty space below the charts. In some of the recent Beta versions ws a change in how this is computed, so it is probably already solved.

I have now installed beta 4.35.0.8 on second device
Samsung Tab S9+ ONE UI 8.5 Android 16 security patch 5.8.2026 => error as described
Nokia 7.1 Android 10 security patch 1.11.2021 => pin the chart o.k.

[Christian]

@Christian
sorry to read about your experience. It may be a memory problem. S7 is quite old and on the edge of what may be enough to run the app. It is not just about "some charts...". In the background, the code has grown together with external libs etc. It is a natural progression that can't be stopped.

Anyway, back to the problem > what I need is ... something. A log? The best is a long-click on the main menu > "Upload to support" at the moment, any problem happens. Without it, I have nothing to check, sorry.

Sorry, the app was not responsive in this particular moment. So no log
May be it will not happen again in the near future. I ordered a Bike Computer for testing.

In 4.35.0

Draw a route in route planner -> call guidance from within route planner -> 'guide reversely' is hidden in settings by default  -> start guidance -> stop guidance -> track is gone.

Guide reversely is not a setting. Its an option and should not be hidden.

Track should stay in Route Planner as long as not deleted by the user.

@Menion - did you read this?

[Graf Geo]

Hello Menion, this change was introduced in version 4.35:

" chg: the auto-pause and 'Record only when moving' options are now a single 'Movement detection' setting (record continuously / drop points whilst stopped / auto-pause)"

I've been testing 'auto-pause' for the first time over the last few days. In principle, it works perfectly, but:

I've noticed that there are numerous gaps in my recorded tracks, even though I haven't taken any breaks. At least, none that I would describe as such. 😉 The reason is that even a very brief stop triggers the pause. I checked it out and it happens after just about 15 seconds! That means briefly reading a sign, taking a photo, tying your shoelaces, waiting at a traffic light, etc. – all of these are interpreted as a pause. And suddenly I've got a gap in my track. In my opinion, that's not the point of the feature.

I'd suggest increasing the time limit to at least one or two minutes – the point at which you can actually call it a proper break.

What do you (or the others) think?

[Andrew Heard]

and finally incorporate the accelerometer sensor for more accurate detection of being paused/ stationary/ no movement - could then be extended to avoid unnecessary & disorientating rotation when paused - compare to Google Maps which makes it look so beautiful

[slarti76]

Hello Menion, this change was introduced in version 4.35:

" chg: the auto-pause and 'Record only when moving' options are now a single 'Movement detection' setting (record continuously / drop points whilst stopped / auto-pause)"

I've been testing 'auto-pause' for the first time over the last few days. In principle, it works perfectly, but:

I've noticed that there are numerous gaps in my recorded tracks, even though I haven't taken any breaks. At least, none that I would describe as such. 😉 The reason is that even a very brief stop triggers the pause. I checked it out and it happens after just about 15 seconds! That means briefly reading a sign, taking a photo, tying your shoelaces, waiting at a traffic light, etc. – all of these are interpreted as a pause. And suddenly I've got a gap in my track. In my opinion, that's not the point of the feature.

I'd suggest increasing the time limit to at least one or two minutes – the point at which you can actually call it a proper break.

What do you (or the others) think?

Yeah, I also noticed the trigger time to be rather short. Not sure about 15s, but it any case should be customizable.

[Cyklo Miro]

@Cyklo Miro
Later long click on the eye > well, it won't be clear what this action will do without looking at the stats to see if anything is already loaded or if all is already loaded. So rather now for now.

My idea is the same as the one for showing/hiding waypoints for a cache: a single long click shows or hides all waypoints,  regardless of whether some are already partially visible or hidden.. BTW, that was a request of mine, too, and I use it often 

[freischneider]

@Cyklo Miro
Later long click on the eye > well, it won't be clear what this action will do without looking at the stats to see if anything is already loaded or if all is already loaded. So rather now for now.

My idea is the same as the one for showing/hiding waypoints for a cache: a single long click shows or hides all waypoints,  regardless of whether some are already partially visible or hidden.. BTW, that was a request of mine, too, and I use it often 

But then I don't know which function a long press will trigger. It's clear when they alternate, but I can't remember the last action.
Suggestion: If some are shown, a long press should hide them all.
If none are shown, a long press should show them all.

[Cyklo Miro]

@Cyklo Miro
Later long click on the eye > well, it won't be clear what this action will do without looking at the stats to see if anything is already loaded or if all is already loaded. So rather now for now.

My idea is the same as the one for showing/hiding waypoints for a cache: a single long click shows or hides all waypoints,  regardless of whether some are already partially visible or hidden.. BTW, that was a request of mine, too, and I use it often 

But then I don't know which function a long press will trigger. It's clear when they alternate, but I can't remember the last action.
Suggestion: If some are shown, a long press should hide them all.
If none are shown, a long press should show them all.

Good idea! Yes, that is exactly how cache waypoints currently respond to a long press - for example, 3/4 -> 0/4 -> 4/4 -> 0/4.
The same approach could be applied to managing the entire cache directory.