Jelly Bean Encryption Negatively Affects Paid Apps

 


While the Android platform tries to be the best OS in the game, there are minor problems that plague it such as rampant piracy issues—- specifically with developers of various apps in the Play Store. While Google has addressed piracy issues with each new OS release such as with Jelly Bean’s App Encryption, its solution has ended up being worse for developers. Apparently developers are claiming encryption (the location of installed and encrypted apps from the Play Store) makes their apps completely unusable because account information is removed after a device reboot. Because of this— Google has disabled the security feature for the Play Store on Jelly Bean smartphones and tablets.

 


It looks like the issue has been pinpointed to a specific area too. When users download a paid app and install it to an encrypted folder at /mnt/asec, instead of the normal /data/app folder, which almost completely erases potential piracy. While it’s great in theory, some or all of the apps that register with the Android Account Manager has information completely erased after a device reboot. As of now, there is no official solution, though developers came up with a minor alternative before Google disabled the encryption feature. Simply put, developers encouraged customers or users of apps to use secondary authentication stores and apps like Amazon’s Appstore, which sideloads a paid app and places them back in the /data/app directory.

While this is only a minor fix, the hope is that Google will certainly address this as soon as possible… especially as it will see more and more Jelly Bean devices surfacing in the next year or so.

source: Android Police

 

 


About the Author: Roy Alugbue

Conceived as Spock’s 4th cousin, Roy has had quite the life. He was born in beautiful San Jose, California, raised in Los Angeles, California and now resides in the greater New York City area. He has always been fascinated and obsessed with technology, especially the continuous advancements of mobile platforms. He was a Blackberry slave since his undergrad days at the University of Southern California until realizing in Feb. 2011, there were greener pastures in the land of Android. His first Android phone was the Motorola Atrix 4G, and he hasn’t looked back. He currently works in corporate media, enjoys following media and technology trends, reading a good book, weightlifting, playing on his XBOX 360 and conversing with total strangers.