I see, i would hard code the IMEI when i really want to make sure that only the devices i have built the software for can use the software. Though a more practical solution is to have a database on a server where you can edit the "safe" IMEI list or have a registration precess and code the app authenticate with the server before it will work.
Ne0 On 16 Mar, 10:55, jamesc <[email protected]> wrote: > Sorry, I wasn't clear. I'm asking whether that's the recommended > option. > > On Mar 16, 10:52 am, Ne0 <[email protected]> wrote: > > > Why dont you want to hardcode the IMEI? > > > On 16 Mar, 10:44, jamesc <[email protected]> wrote: > > > > Hi > > > > I'm looking for guidance on locking an .apk to a specific device (that > > > I have physical access to in order to install the .apk). Gotchas > > > (i.e. avoiding hardcoding IMEIs/ANDROID_ID etc.?) and the like? > > > > Cheers > > > > James -- 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
