The alternative I'd have would be a polling background service, which is a lot more battery draining and very easy to bypass - then you could also use no applock at all. I'm all for more security and better performance/battery life for Android devices, but Google is focusing on the wrong fronts. Google is getting more and more hostile against their developers, destroying the flexibility/modability which made Android so powerful and successful. I hope Google reverses their decision on not allowing the accessibility service for anything else than accessibility, but I don't really think they will. The thing is, it's still not used for accessibility, but for detecting window changes (to show the lockscreen if a locked app is opened). I did everything that Google requested in the email for now, setting a summary and description in the service xml, telling users in my Google Play description how the accessibility service is used, etc. I spent countless hours optimizing the accessibility service implementation, to provide an alternative for users who don't have Xposed installed and don't want to or can't install it. Well fuck, my applocker MaxLock also got this, even though the accessibility service feature is only in the beta right now. Status recently passed a million downloads! I am very proud, or. While the permissions policy states not to request information that isn't needed for the app to function, this. Their user data policy has no restrictions on the use of accessibility services for purposes other than accessibility That said, I wish they would find a another way to go about resolving this that didn't involve the removal of hundreds of good, useful apps from the Play Store.Ī little more information not shown in the screenshot of the email: Unfortunately, like their decision to remove system overlays on Oreo, this makes all too much sense when you consider that they're doing this to get a tighter hold on the functionality that Android apps are allowed to have preventing apps from stealing users data without their knowledge is a pretty important issue for them. Sufficient to say that if they enforce this, a lot of apps are going to be either unpublished or lose some pretty useful features. I'm sure there are more, but I'd rather not spend my time making a list of them. that's not the reason it needs the permission). And yeah, my own app, Status, is kind of screwed unless I'm able to pull off "it makes the status bar more readable" as an excuse (well, it does, but. You can pretty much say goodbye to being able to customize your bixby button. This handy app lets you create shortcuts to open specified apps in multi-window on Nougat. The unread notification plugin for Smart Launcher uses it as a workaround to listen for notifications. This seems like a reasonable decision at first glance, until you consider the sheer amount of apps that need this permission to function. A couple minutes ago I received this email, which can pretty much be summarized to "If your app doesn't use accessibility services for what they're intended to be for, you might as well unpublish it because we're going to take it down in a month anyway".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |