[APP] - version 2.11.X+

[tramp20]

@tramp: I was reading it immediately you wrote it. Then I started checking it and found that function "save part" that is used for storing just a current recorded part do not work. So I started to fix it (and improve a little) and after that I completely forget on your post, sorry ...
- 1. so, why "stopped", when record is really just paused? Till you store record, track is really just paused, so when you cancel "save" dialog, recording will continue

Hi,
it is irritating because the two buttons are side by side:
if I press Pause I see "paused".
If I press Stopp I expect to see "stopped" so I am always in doubt that I have pressed the right button.

It could be made better :-)

[pmoravec]

The silent crash in native code still persists in 2.11.1. I was hoping it was fixed in 2.11.5 since it did not happen for some time, but after extensive moving around the borders when looking for broken woods polygons, it happened as well:

Code Select Expand

D/dalvikvm(12415): GC_CONCURRENT freed 1205K, 29% free 11834K/16656K, paused 6ms+16ms, total 219ms
D/dalvikvm(12415): WAIT_FOR_CONCURRENT_GC blocked 147ms
F/libc    (12415): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 31254 (Thread-12854)
F/libc    (12415): Unable to open connection to debuggerd: Connection refused
I/ActivityManager(  409): Process menion.android.locus (pid 12415) has died.
W/ActivityManager(  409): Scheduling restart of crashed service menion.android.locus/.core.services.PeriodicUpdatesService in 12632ms
W/InputDispatcher(  409): channel '40d4ef78 menion.android.locus/menion.android.locus.core.MainActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
E/InputDispatcher(  409): channel '40d4ef78 menion.android.locus/menion.android.locus.core.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
D/Zygote  (  100): Process 12415 terminated by signal (11)

Is there a way how to debug it? Maybe find a way to run debuggerd? It looks like a null-pointer to me (e.g. failed allocation), but it's hard to say.

[Menion]

@eccentric: thank you for perfect report. Problems should be fixed now. Only remain
- resizing images: only way is to search through page code and for <img> tags and change it's parameters. We'll see how this will work and in worst case, I'll try this ..
- encoded hint: hint is by default encoded on web page, just not to see it. But here, you have to press "hint" button, so I think there is no need to have it encoded by default
- images tab: these images are usually just images from listing on separate page. I think that it make sense to have them right next to listing

@hank: so here is a problem. Again problematic Netherland map ...hope you next device will have a little more RAM (or at least Android 4)

@tramp20: sorry, still cannot agree
button pause: display "Paused" and nothing more happen
button stop:  display "Paused" and display full screen window for storing a tracks.

it's huge different so in case you tap on wrong button, you still should see what happen. Also track is really paused till you close this saving dialog

@pavel: it's probably same problem as before right? I always hate if there is any problem in native code as I really have problems with fixing such issues (if it's even possible). I'll check it, thanks

... btw. RC version for test in first post. If someone has some serious issues that are not fixed in this version (except Pavel ), this is last chance

[pmoravec]

@pavel: it's probably same problem as before right? I always hate if there is any problem in native code as I really have problems with fixing such issues (if it's even possible). I'll check it, thanks

Yes, it is the same problem. If I find a way how to run debuggerd internally on the device (CM 10.1) and get more info out of it, I will let you know.

[pmoravec]

OK, I found out why the debuggerd is not running and include the trace [attachment=1:14clvs4l]native-crash.txt[/attachment:14clvs4l] when the problem happens. Hopefully it will help you diagnose the problem.


By the way, I remembered another issue I should mention - sometimes during the startup (of the current Pro version), i see "null" in the loading dialog, see [attachment=0:14clvs4l]null-load.png[/attachment:14clvs4l]

It happens for a few versions back, but not very often.

[Henk van der Spek]

@hank: so here is a problem. Again problematic Netherland map ...hope you next device will have a little more RAM (or at least Android 4)

Tried the latest RC version, all the same. Must be the RAM.  Because on my wife's Wolfgang AT-AS40SE  (Amoi N816) with:  1 GHz Dual-Core processor (MTK6577) and 512 RAM and Android 4.0 the same happens.
Ok, that one is faster but also crashes at lower zoom levels.
I am a bit worried here because we (outdoor people) do not walk around with the latest and biggest S4 and HTC one (I believe) because these crash too soon for mechanical reasons and have no battery life.

[Menion]

even on A4.0 with 512 RAM Locus crash with Netherland map? Damn, seems that I'll really have to check it more carefully and find some source of troubles.

Anyway topic is closing as new version is out. Thanks all for amazing support and help with debugging! Enjoy Locus 2.12.0