Messages

Clear map cache (mapsOnline) in settings/miscellanous doesn't clear it (but says process successful).

Hello, I have an idea for this addon.
I am just a basic member so I cannot put caches to ignore list, but there are quite many caches in proximity of my HC that I know I will probably never get (mostly the T5 ones or some unsolvable mystery caches). From time to time I update my geocaches via this addon in Locus so I have fresh logs and fresh caches since some of them might have been disabled or archived. But if I delete those T5 caches, they come back after downloading caches in the area.
So what I propose, is an ignore list based on GC codes, these caches would not be downloaded and some other cache would be downloaded instead of it.
What do you think?

Yeah, whereyougo integrated in locus, that's the way to go!

[edit:]

With 4.0.4 you have Locus (with apps2sd) at /sdcard/external_sd/Locus. With 4.1.2 it is/storage/extSdCard/Locus. Maybe the problem is here?

Yes, I noticed the change of paths as well. But if that was the problem, it wouldn't work at all, right? But it works correctly for more than a week so... looks like the problem fixed itself?

edit:
Oh, well, just now it happened again. After inserting a new point into a category - crash. But then, I saw the point was inserted properly (it was not checked to show on map intially) and everything was working okay. So I checked it (the other points were already checked), gone from points screen back to map and then exited Locus. After starting Locus again, all points from that category were unchecked (points from other categories were left intact).

edit 2:
Now I was adding two points using coordinates - the same steps for both. First point was inserted OK, second crashed. Then I renamed the point and it was renamed OK, however, checkboxes of other points got lost. I got up (to list of categories), where I saw 1/49 - that was the number of "checked" points under my category. I entered the category again, chose Select all which checked the checkboxes of all points. Then I got up to list of categories again and there I saw 1/49 - expected 49/49. After opening the category, only the one (freshly added) point was checked.

Well, most of the time it works now but yesterday it didn't. I didn't test other operations at that time (like deleting points etc)... so it must have been some random stuff. Or perhaps a hidden bug in that custom ROM, who knows... So no bug in Locus, to be more precise. That's what I needed to know

When trying to add a point via the Coordinates menu item, after naming it and touching OK, Locus crashes with error:

Code Select Expand

USER_COMMENT=
ANDROID_VERSION=4.1.2
APP_VERSION_NAME=2.8.3
BRAND=samsung
PHONE_MODEL=GT-I9100
AVAILABLE_MEM_SIZE=1616162816
TOTAL_MEM_SIZE=2113748992
CUSTOM_DATA=
STACK_TRACE=java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=12027, result=-1, data=Intent { (has extras) }} to activity {menion.android.locus.pro/menion.android.locus.core.gui.dataManager.DataManager}: android.database.SQLException: Failed to insert a waypoint into category:4
at android.app.ActivityThread.deliverResults(ActivityThread.java:3205)
at android.app.ActivityThread.handleSendResult(ActivityThread.java:3248)
at android.app.ActivityThread.access$1200(ActivityThread.java:140)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1285)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4921)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1038)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.database.SQLException: Failed to insert a waypoint into category:4
at menion.android.locus.core.geoData.a.g.a(L:545)
at menion.android.locus.core.gui.dataManager.DataManager.onActivityResult(L:472)
at android.app.Activity.dispatchActivityResult(Activity.java:5390)
at android.app.ActivityThread.deliverResults(ActivityThread.java:3201)
... 11 more
android.database.SQLException: Failed to insert a waypoint into category:4
at menion.android.locus.core.geoData.a.g.a(L:545)
at menion.android.locus.core.gui.dataManager.DataManager.onActivityResult(L:472)
at android.app.Activity.dispatchActivityResult(Activity.java:5390)
at android.app.ActivityThread.deliverResults(ActivityThread.java:3201)
at android.app.ActivityThread.handleSendResult(ActivityThread.java:3248)
at android.app.ActivityThread.access$1200(ActivityThread.java:140)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1285)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4921)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1038)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805)
at dalvik.system.NativeStart.main(Native Method)

BUILD=BOARD=smdk4210
BOOTLOADER=unknown
BRAND=samsung
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=GT-I9100
DISPLAY=[ZERO]BUG ROM
FINGERPRINT=samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/I9100XXLSJ:user/release-keys
HARDWARE=smdk4210
HOST=SEP-111
ID=JZO54K
IS_DEBUGGABLE=true
MANUFACTURER=samsung
MODEL=GT-I9100
PRODUCT=GT-I9100
RADIO=unknown
SERIAL=unknown
TAGS=release-keys
TIME=1352135821000
TYPE=user
UNKNOWN=unknown
USER=se.infra
It did not happen before I upgraded to Jelly Bean ROM from Gingerbread. I used Locus Backup manager to migrate my settings only, the data stayed the same on external sd card. Is anything migrated in wrong way or this error does not have to do anything with that?

No, I thank you for prompt response and quick fix. Good luck in future development!

Yeah, I will definitely upgrade but not sooner than Christmas... so much stuff that needs to be done
Anyway, attaching logcat output. The stack trace can be seen there as well.

edit from gynta
attachment saved, thx

USER_COMMENT=deleted a category of points and clicked on it before it disappeared from the list.

Why are you doing this??

Because this is how the problem can be reproduced with empty category. Now I tried deleting a category with 200 points, and it is still displayed after 2 minutes. Now I clicked on ANOTHER category and locus crashed as well. So it's not a problem of user workflow.

ANDROID_VERSION=2.3.6

Why do you use an old OSversion?

Because it is a custom ROM and I didn't have time to upgrade yet.

APP_VERSION_NAME=2.7.3

Why do you use an old Locus version? plz try it with the current google play versions?

Didn't know there was a newer version, Locus is updated so often, you know... but now I tried the same in latest version and the crash is still there.

...and it took like 2 seconds for it to disappear from the list

...and why your SGS2 is soooo slow?

I can assure you my SGS2 is fast enough However, it seems to me like if the busy indicator was hidden before Locus has finished its work? Dunno...

Yesterday I tried it again. I deleted an empty category and it took like 2 seconds for it to disappear from the list. Then I tried deleting a category again and clicked on it before it disappeared - this is the step that leads to the crash. Exception was generated and wanted to be sent so I am pastng it here. I guess logcat is no longer neccessary

Code Select Expand

USER_COMMENT=deleted a category of points and clicked on it before it disappeared from the list.
ANDROID_VERSION=2.3.6
APP_VERSION_NAME=2.7.3
BRAND=samsung
PHONE_MODEL=GT-I9100
AVAILABLE_MEM_SIZE=1575710720
TOTAL_MEM_SIZE=2113748992
CUSTOM_DATA=
STACK_TRACE=java.lang.NullPointerException
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1372)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:7039)
at android.widget.FrameLayout.draw(FrameLayout.java:357)
at android.widget.ScrollView.draw(ScrollView.java:1703)
at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:6936)
at android.support.v4.view.ViewPager.draw(L:1923)
at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.buildDrawingCache(View.java:6693)
at android.view.ViewGroup.onAnimationStart(ViewGroup.java:1259)
at android.view.ViewGroup.drawChild(ViewGroup.java:1505)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:6936)
at android.widget.FrameLayout.draw(FrameLayout.java:357)
at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:6936)
at android.widget.FrameLayout.draw(FrameLayout.java:357)
at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1917)
at android.view.ViewRoot.draw(ViewRoot.java:1530)
at android.view.ViewRoot.performTraversals(ViewRoot.java:1266)
at android.view.ViewRoot.handleMessage(ViewRoot.java:1868)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3691)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:907)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:665)
at dalvik.system.NativeStart.main(Native Method)

BUILD=BOARD=GT-I9100
BOOTLOADER=unknown
BRAND=samsung
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=GT-I9100
DISPLAY=UltraToxic ROM v8.1 XWLA4
FINGERPRINT=samsung/GT-I9100/GT-I9100:2.3.6/GINGERBREAD/XWLA4:user/release-keys
HARDWARE=smdkc210
HOST=DELLBUILDER01
ID=GINGERBREAD
MANUFACTURER=samsung
MODEL=GT-I9100
PRODUCT=GT-I9100
RADIO=unknown
SERIAL=unknown
TAGS=release-keys
TIME=1326809369000
TYPE=user
UNKNOWN=unknown
USER=root


In recent version of Locus Pro (on google play), crash occurs when deleting whole category of points.

Hello - I downloaded cache GCW43N but hint at Locus is different from hint on GC.com. I tried to update it but still at Locus is "U2" and on GC.com "H2" - why? I use version 1.4.2.2.

That is because Locus automatically decrypts the hint using ROT13, but GC.com website displays it encrypted by default.

[edit]

Hi,
there seems to be a problem in the Geocaching addon.
I have it set to download 200 caches, 30 logs per cache, in 10km radius (and then import them to Locus). The download was working correctly until 50/200 caches downloaded, then stopped for a while and crashed with error message "Network unavailable. Please check your connection". I tried it 5 times - 3 times yesterday and 2 times today. It always failed at this same spot 50/200. Then I restarted my phone and I was able to download more than 50, it failed somewhere on 130 (don't know because I was not watching the display at that time). My connection is working fine. How can I diagnose the problem in-depth and analyse what's going wrong?

edit
Now I tried doing the same on my friend's wifi network and it downloaded like 180 caches successfully. Then it asked me for a category to import them into, and I picked one. It started importing the caches up until 50 caches and then whole Locus crashed. I chose the Report option but before that, I looked inside the report and saw that there was an Out of memory exception. So it looks like problems with it are not solved in latest version of geocaching addon (as written in changelog).

Thanx for the very quick fix, it's working excellent 8-)

Yes, the "Update cache" functionality does not work (and I am not using Live). :roll: