To expedite resolution of your issue, please provide as much relevant and specific information as possible. This will probably require some work from you. Most reports should include at least the following:

* Which version of the SDK are you using? The latest.

* Which Android build are you using? (e.g. MPA44G) MPA44I

* What device are you using? Nexus 9 (and others)

* What steps will reproduce the problem? (Please provide the minimal reproducible test case.) Write an app that attempts to change the configuration of a network created by the Settings app. When you attempt to save it, the save call will fail with a return value of "false".

* What is the expected output? Something that actually indicates why the save failed! Usually you can figure it out if you hook the device up to adb and watch the logcat, but how do you tell your users to do that!? Worse, even in the case that you can use logcat to see why it failed, often times the error message is very obtuse and requires messing around with your code, or digging around in the Android source to figure out what is going on. In a nutshell, the Wireless APIs on Android are INCREDIBLY unfriendly! This REALLY needs to be fixed! On every other (non-Google) platform out there, you can at least get SOME idea of why something like this failed.

* What do you see instead? A useless "false" message.

* Relevant logcat output.

* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.) * Optional: Link to captured Android bug report (shared privately in Drive.) * Optional: Link to your APK (either downloadable in Drive or in the Play Store.)

To avoid leaking private information, please share screenshots and downloads only in Google Drive. Share files with android-dev-preview- bugreport@google.com and include only links in your bug reports. Attachments can not be included directly in issue reports.

Note that this behavior is documented in the Behavioral changes section of the M Preview - http://developer.android.com/preview/behavior-changes.html#behavior-network. It says

"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."

However it is not clear what the compatibility behavior is. Does this restriction kick in even if the targetSdkVersion is < 23?

In my opinion the API should allow the developers to modify any WifiConfiguration.

I guess this change is some sort of security enforcement to avoid that malicious apps to modify the WifiConfiguration without the users being aware of. So, for few malicious apps, you introduced a change into the API that break irreparably lot of good and successful apps.

Changing the WifiConfiguration objects created by others should always be possible, maybe introducing some special new permission that needs to be granted run-time, so the users are happy but also more conscious about what their apps are doing.

Issue 3195 has been merged into this issue.

Apps like proxysettings save developers a lot of time - we need this!

It is critical to retain this functionality. Apps such as Proxy Settings are vital for developers and testers to be able to quickly modify a WiFi configuration for use with software like Charles Proxy.

Ditto, apps such as proxy settings are vital for my work flow when testing across multiple devices. This functionality needs to stay

I'd like to edit my wifi proxy which is a function important for me, and I think, for a lot of other guys too. Please keep the function there!!!

I would like to keep being able to edit my proxy settings for WiFi because it's extremely important to me and it helps me stay secure on public WiFi.

We have reproduced the issue and informed to engineering team for solution. Inconvenience caused is regretted, we will update you with more information as they become available with most priority. Thank you.

Comment deleted

Please share the test apk to test this issue through google drive to this id, android-dev-preview-bugreport@google.com. And mention the shared link here.

Just shared the test APK with the development team. If you need the source code I can also share it on GitHub or simply attach it somewhere.

Please mention the shared link here.

Also please share the source code on Github and mention the link here if possible.

As you requested, the APK link:

https://drive.google.com/file/d/0B3J3Ic1vzy7aa1ZiMVVpaW5tUVU/view?usp=sharing

And the GitHub project link:

https://github.com/lechuckcaptain/TestIssue3196

Thanks for sharing the apk and source code. We have passed this to engineering team for further investigation.

Your are welcome. Please let me know in case you need anything else

It is one essential thing I am using everyday to edit the proxy settings

Please keep proxy settings in Marshmellow otherwise...

I join the previous comments too.

Comment deleted

Hey there -- Android Marshmallow has been released publicly and our M Developer Preview has ended. If you would like to provide feedback on public releases of Android, please file a bug at https://code.google.com/p/android/issues/list. Thanks for helping to make Android better by participating in our preview!

Please add the feature back to edit the WiFi proxy!

Comment deleted

Comment deleted

Please add the feature back!!!!

Even though I disagree with the request (in my opinion if the issue has been recognized as a bug, shouldn't be closed, or at least should be automatically moved), I just opened a new ticket on the issues list for public releases of Android (as requested).

Here is the link: https://code.google.com/p/android/issues/detail?id=191713

Anyone interested please move its star to the new issue item.

We want justice. Don't turn into Apple. Please!!!!!!!

This is essential for new security apps that use proxies!