Thanks a lot @menion for your constructive approach
As you understand, the protocol is proprietary and need to be reverse enginneered
Which also rules out option 2 as it would put Locus at risk of a cease and desist suit from Shimano. They did it with bike GPS manufacturer Hammerhead who exactly did that. As of today, only Garmin is license.
So the method must keep the Shimano related code outside of Locus.
An separate app/service could handle that and call an Locus API that would be in no way related Shimano.
So 1st part for me is to investigate the protocol.
Then I will have to learn Android programming
Would you see that as a reason able approach ?
Still, the author from the STunlock and STride apps haven't seem to receive such C&D order but better safe than sorry.
As you understand, the protocol is proprietary and need to be reverse enginneered
Which also rules out option 2 as it would put Locus at risk of a cease and desist suit from Shimano. They did it with bike GPS manufacturer Hammerhead who exactly did that. As of today, only Garmin is license.
So the method must keep the Shimano related code outside of Locus.
An separate app/service could handle that and call an Locus API that would be in no way related Shimano.
So 1st part for me is to investigate the protocol.
Then I will have to learn Android programming
Would you see that as a reason able approach ?
Still, the author from the STunlock and STride apps haven't seem to receive such C&D order but better safe than sorry.