Obsolete
Status Update
Comments
tc...@gmail.com <tc...@gmail.com> #2
Hi,
I see in the Issue 36949180 that "This issue has been fixed in the latest Wear 2.0 developer preview 2, and will be in the final release."
Any news about Android TV? Can we expect that this will also be fixed for TV soon?
I see in the
Any news about Android TV? Can we expect that this will also be fixed for TV soon?
sa...@google.com <sa...@google.com> #3
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
this is an identical bug report as
On Android 6 for phones, the SYSTEM_ALERT_WINDOW permission can be granted to an app by the user going to the correct system Settings window and toggling the switch for the app in question. This Settings window doesn't appear to exist on Android Tv. So, since there's no place for the user to grant this permission, any app which uses it (and targets SDK level 23) will crash on a permission failure.
Further, on a phone, an app can open this Settings window for the user (to grant the permission) by calling
startActivity(new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION));
This call will fail on Android Tv(the intent doesn't resolve), indicating that the Settings window in question does not exist (it yields an ActivityNotFound exception)