You can contact an Android Developer Relations person: https://plus.google.com/+AndroidDevelopers/posts
It appears that the circle for that group are all DevRels. I may be wrong in that. You may recognize one or more of the people there. Usually, it's easy to find their email and contact them directly about such a thing. You may never get a response but it's certainly worth trying. I've found DevRels to be responsive and helpful in the past. -John Coryat On Monday, January 28, 2013 12:43:54 PM UTC-6, jeka wrote: > > I reported the app twice, both times without so much as an acknowledgement > email, meanwhile, the app is getting downloads... > > Here is hoping someone from Google sees this. > > > > On Monday, January 28, 2013 1:28:49 PM UTC-5, Kristopher Micinski wrote: >> >> Morally, it's basically decompiling, you can fiddle with the bytecode >> too, decompiling is just the next step.. >> >> As for your second question: this forum isn't monitored by the Google >> play people. However, you might get lucky and have someone from the >> dev team forward it along. The best I've heard is people getting >> responses from Google's "report an app" button. >> >> Kris >> >> On Mon, Jan 28, 2013 at 12:55 PM, jeka <[email protected]> wrote: >> > You don't need to decompile anything to achieve what I'm describing. >> Your >> > APK can have another APK as a "payload" and simply execute its own >> activity >> > before starting the one from another APK. I won't get into details >> simply >> > because I don't want to give anybody the wrong ideas, but it is easy to >> do. >> > >> > But that is besides the point. The point here is this: now that I know >> this >> > is being done with my app, who, if anybody at Google can take the >> knockoff >> > down? At best, it is stealing from me. At worst, it is planting >> Trojans... >> > >> > >> > >> > >> > On Monday, January 28, 2013 12:36:14 PM UTC-5, Nobu Games wrote: >> >> >> >> I noticed that Proguard is able to produce obfuscated code which makes >> >> Java Decompiler crash. >> >> It's a reasonable step to obfuscate any app (also free ones) in order >> to >> >> make it harder to figure out where to apply these changes or how to >> crack >> >> them. >> >> >> >> More advanced protection steps are described here. To sum it up: on >> top of >> >> code-obfuscation you need to add hidden self-integrity checks to your >> app >> >> that try to validate the package signature. >> >> >> >> >> >> On Monday, January 28, 2013 11:27:00 AM UTC-6, Johan Appelgren wrote: >> >>> >> >>> Just decompile, add ad activity, change manifest and recompile. >> Haven't >> >>> tried but can probably be automated for most apps. >> > >> > -- >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Android Developers" group. >> > To post to this group, send email to [email protected] >> > To unsubscribe from this group, send email to >> > [email protected] >> > For more options, visit this group at >> > http://groups.google.com/group/android-developers?hl=en >> > --- >> > You received this message because you are subscribed to the Google >> Groups >> > "Android Developers" group. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit https://groups.google.com/groups/opt_out. >> > >> > >> > -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
