Unofficial AndrOBD in the Play Store?

[drws]

Describe the bug

@fr3ts0n only mentions the F-Droid availability and even explicitly stated that in #84.

But check this out. It seems there is an unofficial build distributed in the Play Store since this February.

I've compared the Play Store APK with the latest original and it is rebuilt, with changed classes.dex and resources.arsc. Exodus returns the same as with the original: 0 trackers, 8 permissions (the same ones). This is no guarantee, just as an indication. Even if the Play Store unofficial build is currently clean, the author could add malicious code anytime.

Is there anything that needs to or can be done about it? Will there be any effect if such apps are reported to the Play Store (based on similar cases)?

[fr3ts0n]

Hi @drws ,
Thank you for the information. It looks like it is a plain re-build, but I'll check on that.

I would have preferred to NOT have AndrOBD on playstore, because this also triggers 1st level support requests of some users with rather limited knowledge / interest of OBD diagnostics / adapters.
It also triggers potential signature problems if you mix up app- and -plugins between F-Droid and PlayStore.

As long as it it just a plain re-build, there is nothing about it.

• I don't intend to spend additional time for maintaining this unofficial release
• That is also what I'll communicate towards @cppox

If there are some changes/manipulations contained, then @cppox will have to ... :

• to provide public source code
• include all additional copyright notes
  ... to meet the GPL license

In such a case of license violations like vgate I'll try to claim a license infringement and make Google remove it from PlayStore, but this always takes a lot of time, effort and nerves ... 😢 (I still didn't succeed with vgate yet, which definitely violates the license ...)

[lefterisgar]

The app on Play Store has ads. A lot of them. It's a shame because AndrOBD is such a good FOSS app and @cppox takes advantage of it in order to make money.