Subsurface mobile 2.1.3(4.8.2.5) Pelagic data cable issues

[Bill Perry]

On 09/19/2018 11:37 PM, Dirk Hohndel wrote:
>> On Sep 19, 2018, at 8:54 PM, Bill Perry <bperrybap at opensource.billsworld.billandterrie.com> wrote:
>>
>> On 09/19/2018 09:13 PM, Dirk Hohndel wrote:
>>> How do you feel with signing your app with a different certificate. Did you change the name?
>> I have no feelings about it.
> Grr. Don't respond on the phone, Dirk.
>
> The question was supposed to be "how do you DEAL with signing your app"
>
> i.e., did you give your app a different name so you wouldn't have a signature conflict when installing it?
>
Auto correct can do funny things.

I didn't do anything special or any sort of signing.
I used the .apk file as named and created by the makefile down in subsurface-mobile-build-arm
I used "unknown sources" to side load it from a thumb drive.
As another test I installed my source built .apk  on another S4 and the first time it is loaded from the thumb drive there is a warning from the Play service
that this code is from an unknown developer. You can click on "install anyway" to install it.
You won't get the warning again on future installs. (I had forgotten about this)

It is strange since the current app installed from the play store works just fine on my S7 running Android 8.0.0 with the same datacable and divecomputer.
And gets the "select an application for the USB device" dialog with Subsurface being one of the applications.

As a side note, the USB device app dialog does come up on both phones.
Divemate is also installed on the S4 and the S7 and it shows up in the USB device dialog on both phones when the data cable is plugged in.
However, Subsurface only shows up in the USB device dialog with the 2.1.1(4.8.1.0) app built from source
and not when using the 2,1.3(4.8.2.5) app installed from the play store.

I'm still digging. It is driving me crazy.
I'll come back when I know more about what is going on.


>> Are you wanting to have multiple subversion apps installed at the same time?
>>
>> All I did to build the mobile app from sources was checkout the v4.9.1 tag and run the scripts as noted the INSTALL file in the subsurface tree.
>> Actually, after I modified any libdivecomputer files I manually ran make down in libdivecomputer-build-arm
>> and subsurface-mobile-build-arm as the subsurface/packaging/android/build.sh script didn't work for me beyond the first run as it didn't rebuild the libdivecomputer library
>> when source files changed and it rebuilt lots of things it didn't need to re-build.
>>
>> The name of the app created is subsurface-mobile-build-arm-debug.apk
>> Currently, I'm just using the samsung file manager to install it from a thumb drive rather than transferring it over using adb
>> as I wasn't intending to do very many builds & installs.
> What I'm wondering is if somehow Android now only delivers the connect Intent to your app and no longer offers it to the official one.
>
> In other words, I'm grasping for straws.
>
> /D
>