Google encourages you to offload your own checks to an external server and I am considering how to do that. I'd like to have more than one way to track installations.
I totally agree that the documentation sucks donkeys. They say you should modify the code substantially to foil crackers but they don't provide anywhere near enough docs to do it! Google, if you are listening we need a secure, turnkey security system like iPhone. LVL isn't it. On Oct 31, 7:59 pm, jtoolsdev <[email protected]> wrote: > Isn't LVL locked to the user's Google email? I thought that was the > idea though they you can use device IDs as an option. Linked to the > account it allows the user to install the app again if they get a > different device. The ID option would be for a single device policy > though they could stand to flesh out the documentation on LVL a bit > more. > > On Oct 30, 3:01 pm, DanH <[email protected]> wrote: > > > Well, there's the IMEI, the IMSI, and the ANDROID_ID. Alas, the > > ANDROID_ID isn't unique (and is in fact identical on many Droid2 > > units). > > > On Oct 30, 12:41 pm, bagelboy <[email protected]> wrote: > > > > Hello Devs, > > > > I'm working on an LVL implementation and I want to use as many > > > different device identifiers as I can. I have considered using IMEI > > > numbers but I've discarded that because a) it's intrusive and b) not > > > all devices will have them. > > > > What might I use to fingerprint a phone for license verification? > > > > As an aside, how have your experiences with LVL been so far? Any > > > pitfalls? I'm not asking for anyone to share their implementation > > > details as that would give the hackers ideas. > > > > -BB > > -- 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
