Mobile app: crash on GPS-tag dives

[Willem Ferguson]

On 20/12/2015 07:38, Dirk Hohndel wrote:
>
>> On Dec 19, 2015, at 4:16 AM, Willem Ferguson <willemferguson at zoology.up.ac.za> wrote:
>>
>> Galaxy S3 on Android 4.3
>>
>> On subsurface-mobile select "GPS-tag dives" (previous locations having been uploaded to server using subsurface-mobile).
>>
>> When I run adb logcat -s Subsurface:V I get a similar out put to Rick, suggesting an invalid font size???? No other error messges.
>>
>> When I do adb logcat there is a long log. Here is part of the log at what appears to be the first exception in the log:
>>
>> I/InputReader( 2355): Touch event's action is 0x1 (deviceType=0) [pCnt=1, s=] when=1123727013000
>> I/InputDispatcher( 2355): Delivering touch to: action: 0x1
>> F/libc    (10506): Fatal signal 11 (SIGSEGV) at 0x00000008 (code=1), thread 10536 (edivelog.mobile)
> I wasn't able to make any sense out of the crash report. But I just uploaded new daily binaries for Android. And they have an option to enable 'verbose' mode (under the Debug menu). And with this we should get a lot more info on the logcat that hopefully will show us what blows up and maybe even why.
>
> Thanks
>
> /D
>
>
Using Subsurface-mobile 4.5.2.468

SUGGESTION: please let Subsurface-mobile write the version number as the 
first item in the application log so that there is no ambiguity doing 
debugging ?? One can view it using the application manager in Android.

When doing GPS-tag dives, then control immediately returns to the dive 
list, NO crash any more. No idea if anything has happened since the 
coordinates are not visible on the mobile app. I then downloaded the 
dive log on the cloud to my desktop and there are no coordinates.

There is also no additional output in the application log.

I then GPS-tagged the dives again, saved the dive log back to cloud 
using the phone, and downloaded the dive log from the cloud on my 
desktop. Still no coordinates in the dive log.

Attached are two log files that represent opening up Subsurface-mobile 
and doing a GPS-tag operation.
Androidlog1.log is a raw log during the first attempt. It has a preamble 
using adb logcat -s Subsurface:V but I do not see an immediately obvious 
clue.
Then follows the printout for adb logcat which is longer than the 
terminal buffer, so the top lines cannot be seen.

Androidlog2.log contains the log for a repeat of the same exercise, open 
subsurface-mobile, get dive list loaded from cloud, do GPS-tagging. This 
time I inserted some empty lines by pressing the RETURN key in the 
terminal several times. After saving the text to a text file, I put in 
some comments into the empty lines that I had created in the adb output. 
But I am not sure that this necessarily inserts empty lines in the 
correct places. If the logging output is more than a second or two 
behind the actual UI events, then the empty line may be misplaced.

I hope this helps a bit, but I am pessimistic.
Kind regards,
willem







-------------- next part --------------
A non-text attachment was scrubbed...
Name: Androidlog1.log
Type: text/x-log
Size: 661586 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20151220/22aff071/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Androidlog2.log
Type: text/x-log
Size: 25003 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20151220/22aff071/attachment-0003.bin>