Programmatically forward-lock an Android APK - android

Doing a bit of advance research, and am stuck on the point summarized
in the title. Namely, is there any way to forward-lock an APK
installed programmatically, from another app? I've not come across
anything beyond a hint in the following post:
http://groups.google.com/group/android-developers/msg/e39941389d4a4cf8
I can't see anything in the docs for PackageManager about forward-
locking, but I readily confess that this is an unfamiliar area of the
SDK for me.
[Cross-posted with the Android-Developers Google group]

If anyone looks at this again... I've since found out that it can't be done in modern versions of the Android SDK. Plus, forward-locking has since been deprecated anyway.

Related

Are the docs for setting up licensing good to use?

I am attempting to follow the links on the developer console site to implement licensing for my application and am concerned that the docs don't really line up with the current technology. In part of the documentation, I was directed to a page that said the utility for doing this was no longer valid. I am simply looking to get licensing (lvl) setup for my app and am hoping somebody can point me to a good resource.
Here is where I stopped at, as I am not familiar with the whole project library import process. It sounds I need to run a command line to continue the process but I am not sure what one of the values needs to be.
I am not sure what the target ID is or if I just need to update the above mentioned properties file or what?
Docs seem to be a little confusing on this topic, or I've just simply missed the boat.
Thanks!

What is SharpCat and where I can find it?

I found a nice, niche casual game engine. According to documentation, if I want to make Android build, I need tool called SharpCat. I googled it and bing it but I cannot find it. Is there anyone that know what tool is it?

Android: is correcting Lint warnings useful or not?

I have built and published my app on Google Play and everything works fine. But I am wondering how I can improve my visibility on the market, how to appear on the first page...
So here is my question,
Do I have to correct every little bug that appears in the Lint Warnings panel (in Eclipse) to be in a better position or is it useless?
I have been looking for resources about that on the web, but I can't find really interesting ones. Do you guys know a good blog that explains how to appear first on the market (or at least, not on the 1234555... page)?
Besides advertising, there are a few useful advices about "how to get your application featured" on this page, basically you have to make a flawless, polished application, which uses a lot of Google API features and is popular among users.
Correcting Lint warnings is good, because it makes your application more stable, but does not directly affect your Market visibility.
If you need more resources, search Google for "getting featured on android market", it might help.
Correcting Lint warnings will make you a better programmer. That's not useless.

Is "AndroidAnnotaions" reliable?

Is "AndroidAnnotations" reliable? I've searched it but couldn't find many articles on it(reviews or tutorials).
I've been considering using this library in my project which already has quite lots of users. Before adopting it, I need a good reputation on it. So my concerns mainly are,
Are there famous products using this library?
Can I say it's stable enough to adopt it for my big project?
Will it be maintained well? (bug fixes, etc)
Thanks in advance.
I am the lead developer of AndroidAnnotations. Let's answer your questions:
Can you rely on AndroidAnnotations?
I think so. AndroidAnnotations is a compile time framework which generates code. The generated code is readable java code, which means that if you need to understand what happens, you can. No magic happening at runtime => you are in control.
We try to maintain a list of external articles / tutorials here.
Are there famous products using this library?
Let's be honest: I don't know. Matthias Kaeppler from Qype talked about AndroidAnnotations at DroidCon London 2011. The frontpage lists the applications that we know for sure are using it. I know there are way more people using it because they ask for enhancements and report bugs, but they usually don't let us know when they publish an app. And of course, the idea of "writing clean and maintainable Android code" is not yet very common in the Android community.
Can I say it's stable enough to adopt it for my big project?
We are using it in our own apps, and we find it perfectly stable. So I would answer yes, but I think you should just try it :-) . Download the 2.2 RC2 (will be released stable soon), follow the instructions and see for yourself. You can do progressive enhancement, and start enhancing only one or two activities. See how it fits you, and let us know if anything goes wrong. And if you do release an app with AndroidAnnotations on the Android market, please let us know, we'll update the front page.
Will AndroidAnnotations be maintained?
Yes, it will. Although it started as a personal project, AndroidAnnotations is now sponsored by a company, eBusiness Information. This company employs people (including me) to work on AndroidAnnotations, with the aim of making it a major Open Source Android framework.
As you can see here and there, we are adding a lot of new features for the 2.2 release. And you won't find a lot of open Defects in the issues, because we concentrate on fixing any bug before adding new features.

Disassembling Android app

It turns out that Google recommends obfuscating your Android app.
In order to understand the problem, I would like to disassemble my own app and see what information I can extract from the code. How do I do this?
There are tools available for that, such as the pair linked to in this sentence. I have not used them and therefore cannot vouch for how well or easily they work.
Some tools are listed at What is a good android disassember that can produce infomative results
Also you can try undx http://undx.sourceforge.net/
Use them only for good :)

Categories

Resources