Original topic:
Local Connection fails in Android 17
(Post creation time:
10-16-2026 04:03 PM
)
431 Views
W
WdC
Asteroid
This is the bug report I just sent.
The new version of Android 17 requires a new permission called Access_Local_Network.. This permission is needed by applications needing to reach local resources. This includes Samsung Email and Gmail applications to reach local email servers. The Samsung implemented Android 17 does not include this permission in Permission Manager nor set it for any applications. This has been verified by android developer docs and sniffer traces
-ed
Samsung_Moderator
Community Manager
10-16-2026 05:03 PM
in
Hello, WdC, and Welcome to the Community! Thank you for sharing your report, and we want to offer help in resolving any issues this may cause.
Are you having issues getting your phone to connect to local internet-connected devices or are you having issues with apps on your phone showing that this permission is needed?
Have you tried any troubleshooting to resolve this?
Here are some things we'd recommend trying:
Checking app permissions are updated to allow/enable this setting
Updating apps to the latest version
Clearing affected apps' cache and data
Rebooting your phone
These guides provide more of the how-to for these:
http://www.samsung.com/us/support/troubleshoot/TSG10001558/
https://www.samsung.com/us/support/answer/ANS10001372/
We appreciate that you've shared this with us, and we look forward to hearing back with any updates or questions you may have.
WdC
Asteroid
10-16-2026 06:28 PM
in
0 likes
Samsung_mn5wtCP
Constellation
10-17-2026 11:23 PM
in
fyi I fixed this by allowing "nearby devices" permissions in the browser. spent three hours troubleshooting for it to be this. thanks android!
0 likes
WdC
Asteroid
10-17-2026 11:48 PM
in
0 likes
JaMMi01202
Constellation
11-7-2026 04:20 PM
in
I have this issue. I have lost access to my Virgin Mobile router (192.168.0.1 by both http and https) and e.g. my Marantz Cinema 50 receiver 192.168.0.160. Works fine from S23U to access either IP from Chrome app. It's a defect in Samsung Browser. Enabling permission for local devices has no bearing on the issue. Clearing cache for Samsung browser has no bearing. Same for uninstall Samsung browser and reinstall. I have added a "Me too" to this post because this issue is identical and I want to add my voice to this issue. This is a ridiculous defect to have got through QA. Access any local device on the local network, or merely use "Access router" in wifi - nothing will work.
0 likes
userUOMPLerPCL
Constellation
11-8-2026 03:43 AM
in
I also have the same issue with accessimg local resources on my network via Samsung browser. Chrome with "nearby devices" permissions works but Samsung browser does not.
userJ2yZdX0XQI
Constellation
11-8-2026 09:52 AM
in
Same issue here, local access works in Chrome, Hermit, Firefox. Samsung Browser doesn't work, even with the Nearby Devices permission
0 likes
dancem
Astronaut
11-8-2026 06:00 PM
in
Checking app permissions are updated to allow/enable this setting
Updating apps to the latest version
Clearing affected apps' cache and data
Rebooting your phone
I did all this and even got another firmware update via PC, but Samsung Browser still cannot open local addresses even with nearby devices permission set. Had to switch to Edge for now.
0 likes
ww1900
Astronaut
11-8-2026 07:28 PM
in
What fixes it for third-party browsers (Brave, Edge):
After that, local network access and WebRTC LAN connections work.
On One UI 8.5 (Android 16), Brave worked without any of this on identical hardware (another A55 and a Galaxy Tab).
Why Samsung Internet works without it (most likely): under Android 17, apps that still target SDK 36 or lower keep an implicit local network grant, while apps targeting SDK 37 must request ACCESS_LOCAL_NETWORK, which falls under "Nearby devices". So Samsung Internet probably still targets the older SDK, and Brave and Edge already target 37. It doesn't look like preferential treatment, but the user experience is still poor: third-party browsers lose LAN access silently after the update, there's no prompt and no clear error, and Samsung's Permission Manager doesn't show the new permission by name. Samsung Internet will likely hit the same issue once it targets SDK 37. A clear prompt would save users hours of troubleshooting.
0 likes