I see, thanks for your reply!
Den torsdag 28 april 2016 kl. 07:17:57 UTC+2 skrev Mohsen Mostafaei:
>
> hi,
> unfortunately until now i can install any apk without any hard work to do.
> but if you assign a code to user who have bought your app(if there is a way
> to do this by app market) you
hi,
unfortunately until now i can install any apk without any hard work to do.
but if you assign a code to user who have bought your app(if there is a way
to do this by app market) you can lock (programmatically) the app for other
user. just idea
thanks mohsen
On Thursday, April 28, 2016
Ok. So I will use only the licensing, you are right, u think that if
somebody want to
reverse engineering your app, they will find the way to do it, and its not
correct to
use deprecated methods.
Thanks.
El sábado, 15 de septiembre de 2012 17:44:50 UTC+2, Vidal Pérez Leida
escribió:
Hi.
If
Want to be rather safe? Encrypt the hell out of everything with
generated keys. Require always online state(like Ubisoft's DRM).
But the easiest thing is to make the thing server based. If they can't
get to your code physically then they can't pirate it. See WoW as an
example of a game that has
On 7 February 2011 10:53, JAlexoid (Aleksandr Panzin)
jalex...@gmail.com wrote:
Remember that if people get the code on their systems, there will be
someone to crack it. Even if it's hardware encrypted and in a
protected chip(see PS3 hacking example).
Side note: PS3 is example of lame
On Sun, Feb 6, 2011 at 12:20 AM, mmtbb mm...@hotmail.com wrote:
LVL is so easily bypassed that it doesnt seem to make any sense to use it
as it stands.
It's better than nothing. The point is not to prevent every attack, it's to
make it harder. Whether that has value to you is a cost-benefit
LVL is so easily bypassed that it doesnt seem to make any sense to use
it as it stands. I hope google creates a fix to this soon.
On Jan 18, 7:03 pm, TreKing treking...@gmail.com wrote:
On Mon, Jan 17, 2011 at 10:03 AM, mmtbb mm...@hotmail.com wrote:
Have there been any improvements to this
I don't think Google is al that good about letting us know when things like
that will be happening, their feature monkey can't type after all.
I just made the assumption that I needed to use the newer LVL system (which
is also not that great) and implemented it instead.
It was not hard to do :)
Just switch to LVL. Even plain LVL as provided as simple code with no
obfuscation will be better than the old forward locking. :}
On Tue, Dec 14, 2010 at 11:24 AM, Brill Pappin br...@pappin.ca wrote:
I don't think Google is al that good about letting us know when things like
that will be
That message has been there for at least the last 8 months.
On Dec 14, 11:17 pm, Fredrik Jonson fred...@jonson.org wrote:
Hi all,
I've noticed the following message on Android Market:
The copy protection feature will be deprecated soon, please use
licensing service instead.
I wonder, is
Hi,
Some information can be found here:http://developer.sonyericsson.com/
community/message/132088#132088
In short:
Everytime SE issued a new firmware they needed to register it with
Android Market, and that could according to their support not be
performed until after the firmware had been
unfortunantly not all shops supports Google LVL or Dynamic Licensing.
On Nov 19, 8:57 pm, Dianne Hackborn hack...@android.com wrote:
Forward locked copy protection is really fragile, as it requires that nobody
except approved entities get to the data (.apk). Thus you *must* trust the
device
What shops?
On Sat, Nov 20, 2010 at 7:48 AM, sblantipodi
perini.dav...@dpsoftware.orgwrote:
unfortunantly not all shops supports Google LVL or Dynamic Licensing.
On Nov 19, 8:57 pm, Dianne Hackborn hack...@android.com wrote:
Forward locked copy protection is really fragile, as it requires
It seems that the copy protection damage compatibility with android
market and many phones, why?
On Nov 19, 3:16 pm, sblantipodi perini.dav...@dpsoftware.org wrote:
Hi,
can you tell me please why if I set the Copy Protection ON from my
developer console,
my apps isn't available on many phones
On Fri, Nov 19, 2010 at 8:19 AM, sblantipodi
perini.dav...@dpsoftware.orgwrote:
It seems that the copy protection damage compatibility with android market
and many phones, why?
Among other problems, copy protected apps would not show up on unapproved
devices. Regardless, copy protection is
Thanks for the answer. What do you mean for unapproved devices?
I know that this isn't the safest way to proceed but since I'm in
business with a shop that use the same DRM protection,
I would know if this will cause compatibility problem on some devices.
On Nov 19, 3:32 pm, TreKing
no one can tell me here what are the unapproved devices and why they
are unapproved?
On Nov 19, 3:43 pm, sblantipodi perini.dav...@dpsoftware.org wrote:
Thanks for the answer. What do you mean for unapproved devices?
I know that this isn't the safest way to proceed but since I'm in
business
On Fri, Nov 19, 2010 at 8:43 AM, sblantipodi
perini.dav...@dpsoftware.orgwrote:
What do you mean for unapproved devices?
AFAIK, for copy protection Google has some list of devices that are
considered approved for copy-protected devices to run on. Usually this
meant that new devices would block
Thanks for the answer.
But I don't understood why a device is approved or not.
Is there a possibility that the injected DRM could prevent the app to
work on some devices?
Thanks.
On Nov 19, 5:49 pm, TreKing treking...@gmail.com wrote:
On Fri, Nov 19, 2010 at 8:43 AM, sblantipodi
Forward locked copy protection is really fragile, as it requires that nobody
except approved entities get to the data (.apk). Thus you *must* trust the
device you are delivering the .apk to, or else you have leaked the data and
blown the forward locking. For example, a phone running a custom
I recently did remove the copyprotection for the same reason. I waited
until pretty much everybody had upgraded and the pulled the trigger
without uploading a new version, just removing copy protection. This
way only a small number of people would get hurt...
So a few users did report fc issues.
After turning off copy protection and losing db and local files, are
there any way to restore them?
Regards,
Per Sandström
On Jan 15, 6:10 am, Kumar Bibek coomar@gmail.com wrote:
Hi Andrei,
If you don't care about dev phones downloading your app, and ripping
apart your db and local
Hi Andrei,
If you don't care about dev phones downloading your app, and ripping
apart your db and local files, then it's fine.
Kumar Bibek
On Jan 15, 6:34 am, Andrei gml...@gmail.com wrote:
I have Copy Protection turned on for my app, but now i want to
remove it
Will there be any problems if
Can dev phone download paid app?
On Jan 15, 12:10 am, Kumar Bibek coomar@gmail.com wrote:
Hi Andrei,
If you don't care about dev phones downloading your app, and ripping
apart your db and local files, then it's fine.
Kumar Bibek
On Jan 15, 6:34 am, Andrei gml...@gmail.com wrote:
I
No, Dev phones cannot see your application if they are copy protected.
Kumar Bibek
On Jan 15, 10:15 am, Andrei gml...@gmail.com wrote:
Can dev phone download paid app?
On Jan 15, 12:10 am, Kumar Bibek coomar@gmail.com wrote:
Hi Andrei,
If you don't care about dev phones downloading
I'd like to switch off copy protection for my app, too.
I think I have successfully managed to reproduce this issue on an 1.5
emulator _just_once_. What I saw from the logcat was that the process
couldn't access the preferences and the database because it ran under
a different UID than the UID
It looks like I spoke too soon, we've had a few users on the Hero (OS
1.5) that are having the copy protection problem (i.e. crashing on
startup). An uninstall/reinstall fixes the problem as before, but they
lose their saved data. I've had no reports from other phones of
problems yet. Could it be
A further update: We've removed the copy protection on an existing
game, and done a new release and no one has reported any problems. So
this bug does indeed appear to be fixed.
A related note: Once we removed the copy protection our game was
suddenly visible to Droid Eris users, whereas the
Just a note to say that the two bugs mentioned in this thread were
marked by an Android engineer as fixed in 1.5, so we've turned off
copy protection and so far so good. We'll be issuing an update to the
game and so we'll see how things go through that update process. I'll
update here when we find
I would also love to hear anyone's experience on 1.5+ handsets.
What I would really love though is a definitive answer from Google on
this issue. I don't know why this can't be addressed officially, we're
not asking for secret information to be revealed here - we have to
know these kinds of
It seems to me that these two Issues are identical. We submitted our
app with copy protection turned on. We would now like to turn it off
(so people with rooted and developer devices can download it), but we
don't want to cause crashes on all of our users on Android 1.5.
Am I missing something
It seems to me that these two Issues are identical. We submitted our
app with copy protection turned on. We would now like to turn it off
(so people with rooted and developer devices can download it), but we
don't want to cause crashes on all of our users on Android 1.5.
Am I missing something
These two Issues seem to be identical to me. We submitted our app
with copy-protection turned on (not aware of these issues, nor of the
fact that some people wouldn't be able to download our app as a
result). We'd now like to turn copy-protection off so everyone can
use our app. But before
So can I take that to mean that that the bug exists in all current
releases including 2.0? I could really use some concrete info on this
particular issue as it affects most of our apps and the enlarged
bundle size is becoming a real problem on Droid.
Thanks very much,
Matt
On Nov 12, 3:22 pm,
When a bug is marked as FutureRelease it usually means it will be
fixed in the next release at the time the bug is closed.
http://code.google.com/p/android/issues/detail?id=2263 was marked as
FutureRelease @ Mar 21, 2009 so it should be fixed in Android 1.5 -
that was the next version after
The issue (1) with turning copy protection on (or off) was in Android
1.0/1.1, and there's been no fix for it made on top of those versions.
I believe that it is fixed in 1.5, which means that you might be OK if
you deliver a copy-protected version with minSdkVersion=3 - I'm not
sure, though.
What is your goal here? The copy protection mechanism in Android isn't
strong, so if it's to try and mitigate piracy I'd not bother. It won't
work and will inconvenience your users.
In case you think I'm some kind of anti-DRM activist, I'm not. If
somebody produced a secure and convenient way to
Is the copy protection in 1.5 any more robust in 1.5?
On Apr 26, 2009 11:38 AM, Jean-Baptiste Queru j...@android.com wrote:
The issue (1) with turning copy protection on (or off) was in Android
1.0/1.1, and there's been no fix for it made on top of those versions.
I believe that it is fixed in
The AndAppStore licensing system isn't tied to AndAppStore, you can create a
license for a user using HTTP GET or POST via any website/store.
Full details about it are at
http://andappstore.com/AndroidPhoneApplications/licensing.jsp
Al.
---
* Written an Android App? - List it at
One thing I've learned over the years of selling products on the net is
to do unlockable demos. The unlockable ones were quickly hacked and
wound up as warez. The ones where I provided a crippled demo and the
real version was only available for purchase did not wind up as warez.
Pirates
40 matches
Mail list logo
