Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D device_buzztime_common
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • scorpio
  • device_buzztime_common
  • Issues
  • #3

Closed
Open
Created Jun 26, 2017 by Mark Stevens@mstevensOwner

WIfiConfiguration cannot change config from BTCore

Android M: WifiConfig can only be changed by the apk that configured it

In Provisioning, Wifi is configured by Provisioning apk, but then when BTCore runs, the WifiService cannot configure that SSID because it is a different apk. There is a permission (OVERRIDE_WIFI_CONFIG ) but it is systemOrSig and would need to be on BTCore.

From thread online (https://github.com/shouldit/android-proxy/issues/15) ::

I don't know if it's useful but I noticed this in the "Behavior Changes" document from Google : "Your apps can now change the state of WifiConfiguration objects only if you created these objects. You are not permitted to modify or delete WifiConfiguration objects created by the user or by other apps." http://developer.android.com/preview/behavior-changes.html#behavior-network

Resolution to be determined: Option 1: provisioning removes it's config on completion and lets BTCore reconfigure and then own it from there. Option 2: relax restriction in WifiStateMachine Option 3: allow BTCore to request that Provisioner remove config through broadcast.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking