Forums - Why does the Android-SDK require permission CHANGE_WIFI_STATE?

3 posts / 0 new
Last post
Why does the Android-SDK require permission CHANGE_WIFI_STATE?
Martin L.
Join Date: 9 Dec 14
Posts: 10
Posted: Wed, 2016-01-27 12:07

Hi there,

I'm wondering why the AllPlay-protocol requires the permission 

<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />

inside its manifest-file?

Can this be safely removed if none of the UI if the SDK is used?
I cannot detect any direct error if this permission has been removed via:

<uses-permission
    android:name="android.permission.CHANGE_WIFI_STATE"
    tools:node="remove">
</uses-permission>

 

Looking forward to your results.

 

Kind regards,

Martin L., AirAudio

  • Up0
  • Down0
daniel.tai Moderator
Join Date: 19 Oct 15
Location: San Jose
Posts: 32
Posted: Wed, 2016-01-27 18:55

Hi Martin,

You may safely remove CHANGE_WIFI_STATE.  This was inherited from the Controller SDK, which allows you to switch to AllPlay speaker AP for onboarding to home network.  This permission is not used in Click SDK.

Thanks

Daniel

  • Up1
  • Down0
airaudio
Join Date: 29 Dec 15
Posts: 1
Posted: Thu, 2016-01-28 01:13

Thanks Daniel for the quick & clear feedback, I have removed the permission via the mentioned command.
Other users may do the same if they'd like to remove the additional permission.
 

Best regards,
Martin

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.