Subsurface-mobile, next round - Android 4.3

[Dirk Hohndel]

> On Apr 15, 2017, at 9:57 PM, Willem Ferguson <willemferguson at zoology.up.ac.za> wrote:
> 
> On 15/04/2017 17:16, Dirk Hohndel wrote:
>> 
>> It's more likely that your phone ran out of memory and killed Subsurface (which is pretty BIG). You might be able to see what's happening with
>> 
>> adb logcat
>> 
>> on a computer that is connected to that phone in USB debug mode.
>> 
>> 
>> /D
> 
> Below is a trace showing lines containing Subsurface. This is what I did.
> 
> (1) Start up Subsurface-mobile
> 
>    on dive list, select a dive for dive details view
> 
>    At bottom of screen, tap Location icon.
> 
>    This launched Google Maps
> 
>    Upon return from Google Maps, Subsurface had died.
> 
> (2) Manually start Subsurface-mobile again
> 
>    on dive list, select a dive for dive details view
> 
>    At bottom of screen, tap Location icon.
> 
>    This launched Google Maps
> 
>    Upon return from Google Maps, Subsurface automatically started up again.
> 
> (3) select Main Menu using hamburger icon
> 
>    tap Show GPS -> Show GPS fixes
> 
>    activate slider of one of the fixes on the list and select Location Icon
> 
>    This launched Google Maps
> 
>    Upon return from Google Maps, Subsurface automatically started up again.
> 
> =====================================================
> 
> 
> willem at FINS:~/Desktop$ adb logcat | grep -e "Subsurface"

I wonder if the logcat shows something without the 'grep', but I doubt it. None of this gives us an indication what's happening.
How much memory does your phone have (RAM, I mean)?

/D