Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - joeloc

#31
Quote from: CabrioTourer on August 07, 2022, 22:21:54
Quote from: joeloc on August 06, 2022, 07:36:52
Sharing points as KML doesn't work since a few versions. The menu entry simply does nothing.

Works for me.At least with these steps:
- Select a point
- Click on share at bottom of screen
- Select file explorer (X-plor in my case)
- Select target folder
-> Kmz created
This menu entry is not operating for me, it simply does nothing. It worked fine for a few years.and stopped working a couple versions ago.

#32
Sharing points as KML doesn't work since a few versions. The menu entry simply does nothing.
#33
The new copyright button on top right is super horrible. Is there any way to disable that pretty please? Like a "I have acknowledged the Copyright for this map, remove the button" link when you first display the message for each map?

Besides of getting in the way visually and being hit accidently (moving bicycle on bumpy roads..
not while sitting in a chair...), it WILL cause OLED burn in with its super high contrast. Other parts of Locus UI have done that as well for me and are now permanent on my current phone... and my previous phones. Which reminds me... any chance of slightly moving the whole UI around by a few pixels every now and then somehow? If you run Locus outdoors, display will always be super bright and maybe always on and burn in will occur after a while for power users. All my Samsung devices going back to at least the S8 suffer from burned in Locus UI actually. S10 does, my GFs S20 does, my current S20FE also does (after 16 months heavy Locus use).

Obviously it's Samsungs fault, not Locus. But anyway... Locus is the only App that runs at 1000 nits many hours a day, so it causes by far the most stress for your Display.
#34
Quote from: Menion on April 26, 2022, 08:41:29
@joeloc
thanks for the logs related to the app killing. These are logs directly made by Locus Map right? They are useful for some debugging and testing tasks, but in case, the system kills the app, the app has no chance (no time) to write any info about this crash into these logs. So in case, we try to debug some "crash", it is necessary to create a system log which should be! everything.

Ok, will do a system log next time. Shouldn't be too long, Locus died twice today already. 30MB zipped is a lot though... Samsung/Google really put a lot in there.

Did you find out why Locus retries live tracking every second when offline? Doesnt this prevent device sleep and all other good battery saving things? I usually go airplane mode when I need to save battery, this works nicely to shut up all social media crap. But if it makes Locus use more power than less, I have to reconsider this tactic :-)

Btw, thanks for max scale setting per map. Works fine and makes Overlay-Heatmap-Life a lot better.
#35
Here are my logs when Locus was killed by Samsung Camera today. Sorry for size, can't really edit huge text files properly on the road.

The log is filled with thousands LiveTracking failed due to offfine events every second or so. A possible problem in Locus, unrelated to killing? At least it pollutes the log... but does it really need to be tried every second? Shouldn't it just wait for online status change or something? Interval is configured to 3 minutes.

17:33:37.457   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:37.460   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
17:33:38.473   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:38.477   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
17:33:39.487   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:39.554   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
17:33:40.466   D   LiveTrackingCustomService   sendNewEvent(false)
17:33:40.471   W   LiveTrackingCustomService   handlePendingEvents(), device is not online, send later
#36
Regarding sharing names... not sure I get what you meant. I want to web search for any names on the map with the least hassle possible. Tap a POI, select share, select websearch. Tap a track, select share, select websearch, long tap anything on the map, select share, select websearch.

How would I do this in current Locus? To get from any name on the map (eg Refugio Coolplace) to
https://www.google.com/search?q=refugio+coolplace

websearch meaning: send whatever "name" to default browser default search engine.
#37
@menion, i understand that scaling too much doesn't make much sense for anything else. For a Heatmap though, resolution doesn't really matter much. And things that magically disappear are just irritating :-). I am only bothering you with this btw because the Heatmap has become the tool of choice for finding my way. It beets OSM hands down even in places where people maintain OSM nicely... and especially where they don't. You can even judge the difficulty of a trail easily... it's almost magic for mountain biking.

Maybe the hardcoded zoom limit could be turned into something in providers.xml for the future?

Speaking about disappearing things besides the  max zoom issue: the overlay disappears way too often when internet is bad and I zoom around. I know you like blaming the server, but really... there is just no reason for something to disappear when it was loaded just minutes ago. It's especially frustrating when this is your main source for navigation because your offline maps contain nothing. Are you sure your tile caching works correctly? It seems to me you invalidate the cache too early, like when you send the http request for new data (at new zoom level). All cached things.should remain valid until new data is successfully received obviously, not just requested. Just an idea... that's how it "feels" here.
#38
Planning my future route, I scroll through the map in my intended direction and find an interesting looking place. First thing is setting a waypoint, name is mostly correct due to Locus query magic. Now I want to Google that place... and juggle with edit/clipboard/copy/paste/madness to get the name.into a web browser. Could you add "google search" to the sharing menu in Locus? It should work for points/tracks/everything that has a "name" basically.

Would make life a bit easier on the road.
#39
Is the overlay not rendered at all when it's max zoom differs too much from current zoom? My Strava Heatmap has a max zoom of 11 (the russian server doesn't serve more at the moment I guess). Locus at Zoom 16, all is fine. Locus at Zoom 17, overlay is not rendered at all. See pics.

Or do overelays disappear at Zoom 17 in general? Can I prevent this? I'd always like to see the Heatmap,.no matter what.
#40
Quote from: CabrioTourer42 on April 22, 2022, 21:48:26
"Wasn't there a web page with the beta APKs. somewhere?"

Link is at the bottom of every menion post. Check the one on page 6.
Thanks for helping a blind guy :-)

To make this posting worthwhile, menion, please look at the two pics. Can you make the altitude text under the arrow not clip so aggressively? It disappears completely when only one pixel is invisible, why? Also, if there are spaces, remove them. And replace the / with a space maybe? All that saves pixels without harming visibility. Maybe even render the units in fontsize/2?

I know I can make fonts smaller, but that's counter productive on a bumpy mountain bike in bright sunlight wearing dark glasses :-).

PS, the red and blue stuff on the map is the Strava Heatmap Overlay. Right here in Andalucia it shows about 300% more tracks and trails than OSM even knows about. Extremely useful... might be even worth askin Strava for an official agreement to include that somehow?
#41
Quote from: Andrew Heard on April 22, 2022, 00:30:18
Quote from: joeloc on April 21, 2022, 16:53:32
...I run a "watchdog" since a few months that checks for Locus every minute and restarts it when it's gone.
@joeloc sorry to read of your troubles - I don't have those problems, will keep 2017 Samsung phone as long as possible, but could you possibly share more details of your "watchdog" - just curious. Best wishes Andrew.
My watchdog is a super simple macro for MacroDroid. It checks periodically for the presence of Locus notification (since apparently direct check for running apps is forbidden in newer Androids). If there is no Locus notification, it plays some warning text and simply starts Locus. Locus resumes track.recording nicely in this case, which is really all I care about.

@menion, I'd love to do logs n stuff, but apparently play store refuses to deliver beta versions (even though it says it does). So atm I'm still running public 4.8. Wasn't there a web page with the beta APKs. somewhere?

Camera is the main culprit when it comes to killing Locus, today it happened again. Just once though. It also happens to me when web surfing though... or when using the booking.com app. Anything really. Whenever Locus is in the background, it is in grave danger.

Funny though, only Locus gets killed. I never have problems with other background stuff, like Audible, VLC-Player for radio streams, etc.
#42
Since a couple of years now, Locus dies frequently and silently on current Samsung devices. This happens 3 times a day at least for me at the moment (Samsung Galaxy S20FE), mostly while I do other stuff with the phone. For example, when I take a few pictures or videos with the Samsung Camera App, you can almost bet on Locus (and its track recording) either dying or more likely being killed by Samsungs aggressive OS. NONE of the messy Android options on this will help, nor will running Locus as a service change things. Locus simply dies silently and will obviously no longer record any track.

This is a real shame... and it's basically getting worse with every OS update. I run a "watchdog" since a few months that checks for Locus every minute and restarts it when it's gone. That kind of works against losing tracks, but is really an ugly solution.

It happens to me and to a friend as well (Galaxy S20 Ultra), we both have comparatively large databases. Maybe that makes Locus use more memory and Samsung more likely to kill it when running other apps? I have no clue really, and I can't make any suggestions on how to fix this. I just wanted to point out that this long standing problem is far from being solved... and it's a major nuisance if you cannot rely on your track being recorded.
#43
When Locus force-quits (unfortunately still happens, I blame Samsung) while I track is being recorded, recording continues after restarting. However, the Icon (green arrow, red button) does not reflect this and keeps showing green instead of red.
#44
I can't pinpoint it exactly, but since a couple of weeks I seem to suffer from disappearing points. Sometimes, or more likely quite often, whenever I create a new point (with long tap), the previous point I added simply goes away. The new point is fine, the previous point disappears completely from the database.

Happens quite a lot, but not always apparently. Probably also is related to what I do in-between adding points. No more clues yet, but maybe you can think of something already.
#45
Long tap on map content to toggle last two maps is nice! A little problem though: I believe when Locus restarts and maybe also when I select a new overlay map, you forget the previously used map and replace it with the overlay map. That doesn't make much sense, I never want the overlay to move into one of the toggle spots.