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.


Messages - joeloc

Pages: 1 [2] 3 4 ... 21
16
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 13, 2017, 22:49:49 »
@joeloc , @slarti76 : what should I do to simulate this issue ( how to simply change DPI ), any app from Google Play?
Afaik, it's only possible to do this with root and XPosed framework - very Android-nerdy stuff. ;) For me, it's not important, and I don't think it's worth spending time on. There's much more important things...
Theres more important things indeed. I just thought maybe the bug is obvious... like using a different DPI value for cursor calculations/scaling and the rest of the UI. Testing will unfortunately require a rooted Android, xposed framework and the "app settings" module. Very nerdy indeed.

Anyway... Locus UI is just a tad small for moving bike-usage... but very well suited for couch-usage... or for while-being-stopped-usage. And I understand that the latter has preference and nobody really cares about moving bikes. It would be nice though if Locus had a simple "scale" setting that scaled everything at once... buttons... fonts... cursors... maps... just everything. Similar to what you accomplish by changing its DPI value with ugly hacks :).

17
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 13, 2017, 22:40:24 »
Ok, guys, I will eat my hat and 3.24.xx is good. After some serious logging and emailing with Menion I found out that the track style on the map in combination with a quite big track, creates the slugginess I see at higher zoom levels.
Erm... I think I reported this bug more than two years ago... and menion already acknowledged the problem and did some profiling and blamed rendering code in Android. But basically, track styles were completely unusable since the beginning because they slow down Locus to a crawl (1 fps and less) at higher zoom levels. Since I quite often use high zoom levels to scout for campsites on sat maps, I had to stop using styles completely. Shame really, but cannot be helped until rendering is fixed, either in Android or in Locus.

A dead simple ten-second-workaround (also suggested back then) would still be:
if (zoom > X) style=0;

But obviously that would make more people complain about what happened to styles at high zooms. Performance isn't really such a big topic for most.. so what if rendering takes a second... or deleting track point takes five :-).


18
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 11, 2017, 08:39:52 »
Found the reason. I fake the DPI for Locus App to 620 (instead of default 540 on a Note 4). This works nicely to scale your UI (buttons and everything) to something more reasonable on a moving bicycle, but seems to mess up the cursor calculations somewhat. Weird, because all other parts in Locus scale absolutely fine.

@joeloc: hi ... hmm not sure where may be a problem. This is a "cursors zoro" right? I'm trying it scaled to 200% and it works as expected. On your screenshot is looks moved only few pixels. Center cross seems to be ok. Did you tried different set of cursors?
The GPS position (blue circle) no longer matches the center of the cursor image. No idea when this happened really, but I've been using cursor_zorro for years without problems.






19
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 11, 2017, 08:29:02 »
@joeloc: hi ... hmm not sure where may be a problem. This is a "cursors zoro" right? I'm trying it scaled to 200% and it works as expected. On your screenshot is looks moved only few pixels. Center cross seems to be ok. Did you tried different set of cursors?
The GPS position (blue circle) no longer matches the center of the cursor image. No idea when this happened really, but I've been using cursor_zorro for years without problems.






20
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 08, 2017, 15:00:10 »
Possible that a recent update killed custom Cursors? Seem no longer centered...



21
Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: April 11, 2017, 08:12:18 »
:) ... I've just yesterday reduced font size a little, so it should help. And it's more love in "same everywhere". Dialogs usually had all uppercase, full screen not.
Don't understand. So far, my tracks were windowtitled correctly, for example rmx_2009-08-08_MoabPorcupineRim. And now it changed to RMX_2009-08-08_MOABPORCUPINERIM. And that is better because... ?

But never mind... there are far bigger issues with the whole view/edit separation mess. A little uppercasing really can't destroy much :).

22
Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: April 10, 2017, 08:07:01 »
All window titles are upper cased now. Not only does it look ugly, it also shortens the number of visible letters of a track name considerably. Also it doesn't represent the real track name. Unintentional bug? Or did Locus UI team suddenly develop a love FOR SHOUTING :)

23
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: October 11, 2016, 14:40:27 »
Since the latest beta was labeled "release candidate" already if I remember correctly, I once again want to point out the super weird strangeness of the new map items interface:

I'm really not a Locus beginner, but I have a seriously hard time figuring out how this is working. I navigate to some folder with my kmzs in the new map items dialog. Then I load a file by clicking on the "eye". Then Locus blocks and I wait for half a minute while it loads. Then I click on the three dots sub menu of the same file and select "center element" to actually see it displayed on my map. Not really a funny procedure to start with.

It gets even worse when I want to hide the file again though. Because apparently, I need to remember the exact sub directory and name where I loaded it from and navigate there manually(!) from some root folder. Only then I can turn off the "eye icon" to hide. Thats really pure horror if you deal with more than just one overlay and have them sorted in nested directories.

Apparently there is also a separate new "sidebar" menu for map items that shows all the loaded overlays. But strangely, the sidebar thingy cannot unload anything. I can "dive into" a kml/kmz and hide specific elements, but not simply unload the whole thing.

This whole process seems completely unlogical to me. I just cant understand how it's supposed to work. Maybe I am missing something very obvious here?

24
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: July 05, 2016, 19:54:16 »
I just noticed Locus mobile data usage for the first time. In the last seven days, it was 60MB "foreground data" and 5MB "background data" according to Android. Can you explain what this means? Is this with the app in front and screen on? And background is with screen off or app in background? Or does it have to do with separate tasks inside Locus... like live tracking and online maps?

60MB feels a lot to me, since I normally never use online maps. Is it possible that the new Panoramio layers eats loads? Then again, I used that just for testing :-).

Live tracking traffic should be miniscule, right?


25
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: July 05, 2016, 19:47:23 »
menion.android.locus folder and thus the image caches are always created on /externalSd/Android/data on my system. Is there any reason to put these on external sd card? I would assume writing to internal memory is orders of magnitude faster and much more suited for things like caches.

Can I can somehow influence this folder? Or does Locus want to be on externalSd specifically?
 
Locus folder itself is on internalSd obviously.

26
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: July 01, 2016, 18:25:33 »
Here is proof... break at restaurant... phone was not touched... not even turned on display... continue riding... blam... no more points recorded. And there never will be... unless you manually pause and unpause the track. I can reproduce that every time. Android 5.1.1, wasn't changed in a year. Only Locus changed... and some time in the last weeks it turned from a reliable work horse into a random fun house :)



27
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« on: July 01, 2016, 11:36:32 »
Is there a new secret but horribly misguided gps auto pausing mode in Locus?

I am recording a track. I have a break for a few minutes (not moving... not touching the smartphone at all). I continue riding.

No more points will be recorded from here on, even though there is a perfect gps fix and everything!

That's very bad... I need to manually pause and unpause the recording whenever I stop a bit longer. Otherwise I will lose the days track.

This behaviour is reoroducable with latest Betas and latest pros. No difference. Please investigate... losing track data is serious business.

28
Versions / Re: [APP] - version 3.17.x (16. 5. 2016+)
« on: June 24, 2016, 15:54:53 »
@balloni55: thanks, I'll check it

@joeloc: 10.000+ tagged photos, heh ... I'll be thinking about it.
And performance. Are you willing to share with me your current point & track database? There were no changes in how Locus load data from database. Only difference is, that your database grow and grow, nothing more. Seems that it will need some improvements in structure of database because from tests, 95% of time is spend on database query.
I'll gladly share it... I just cant seem to find a working email address of yours.

As for the querys and a horribly performing database solution (remember deleting track points?)... too bad... but that's not an excuse that works for your users :-).

But seriously... I am in track list... I tap on a track... I tap the back button. Not a single bit in the database has changed. Why then is the complete track list rebuilt/reloaded/requeried/rewhatevered? These extra five seconds really make it hard to browse... very hard. And if it was just one second... still way too much for simply closing a window in a snappy UI.

Even if I edit/change a track and then go back to the list... you'd only have to reload/update this one track. Not the whole hundred. Not over and over again. My poor battery...

29
Versions / Re: [APP] - version 3.17.x (16. 5. 2016+)
« on: June 24, 2016, 15:08:56 »
3.17.2.8:

I know I always complain about performance... but really... it seems to get worse with every new beta version :-). I have long since come to accept the sad fact that it takes 2 seconds plus a "working..." dialog to open a track from a track list. But with 3.17.2.8, it now takes about 5 (five!) seconds to just see the bloody track list! And also 5 (five!) seconds when you close a track (and go back to the track list). These 5 (five!) seconds pass without any visible sign, Locus just seems dead.

This is on one of todays fastest smartphones with just around 100 tracks in the folder, so nothing obnoxiously out of the ordinary. Can we at least focus a tiny little bit on efficient code and performance in general? Soon? Stuff like that is exactly what makes Locus user interface cumbersome and sluggish and unresponsive. And I am currently sitting in a comfy armchair at home just fooling around... it will feel much worse outdoors on a bike.

30
Versions / Re: [APP] - version 3.17.x (16. 5. 2016+)
« on: June 24, 2016, 14:45:28 »
@joeloc: this directory is used for caching of all downloaded images from internet in format, they are downloaded. Images from Panoramio and cached local photos in miniaturized version should be already cached on different place in /sdcard/Android/data/menion.android.locus/cache . Anyway 5000 is quite nice number ... seems I'll have to reduce some older files here as this may also slow down access to these files. Thanks for info
Interesting... that cache seems to be on /extSdCard/Android/data/menion... for me. A bit weird... and not good... since access to /extSdCard is a lot slower. Oh well... will try to move it.

Anyway... I have a geotagged_photos folder there which seems to get horribly huge... like two files per image. one for image and and extra one for metadata?!

I have >10.000 geotagged pictures on my phone. Android is already struggling sometimes with its own media library caching. But is it really strictly neccessary for Locus to implement an extra cache on top of that?! Thats like 20.000 additional files for the sdcard... in a single directory. Can you not use the media store for this somehow? Maybe I have a wrong idea of what the media store does on Android... but I thought thumbnails would be part of it. If every app did its own image caching, I imagine my phone suffering badly.

If this extra locus cache is 100% neccessary, it might be better to put it into a database instead of 20.000 single tiny files. Normally I am always in favor of file system vs databases... but basically tripling the number of files on my sdcard justs smells like a way too high price.

Pages: 1 [2] 3 4 ... 21