160Mhz channels are detected as 80Mhz only

[tsg2k2]

Describe the bug

UI displays 160Mhz channel as 80Mhz, both in the AP list and on the graph.

To Reproduce

1. Have a router running 160Mhz channel.
2. Open WifiAnalyzer and switch to Access Point view. Observe that router's SSID from Graph - Access Point details #1 is displayed having 80Mhz width.

Expected behavior
160Mhz width should be displayed (and properly reflected on the channel graph too)

Versions

Android 10 on OnePlus7 Pro 5G
WifiAnalizer 2.1.2 - 52GS(10-29)

Additional context
router's own status:

phy#1
        Interface wlan1
                ifindex 7
                wdev 0x100000001
                addr ...
                ssid ...
                type AP
                channel 100 (5500 MHz), width: 160 MHz, center1: 5570 MHz
                txpower 30.00 dBm

Intel AX200 (2x2 160Mhz wifi 6 card)

[VREMSoftwareDevelopment]

@tsg2k2 Please provide screenshot from the application: access points screen with full details per access point

[tsg2k2]

Here it is

…

On Wed, Jul 15, 2020, 4:30 PM VREM Software Development < ***@***.***> wrote: @tsg2k2 <https://github.com/tsg2k2> Please provide screenshot from the application: access points screen with full details per access point — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#301 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ4IXSPWXMGJG7YRMBVIVB3R3YGWFANCNFSM4OZ5SBIA> .

[VREMSoftwareDevelopment]

@tsg2k2 ???

[tsg2k2]

In my previous email i have attached a screenshot of 160mhz channel (SSID tsg51) which is shown as 80mhz only, as per your request.

…

On Wed, Jul 15, 2020, 5:12 PM VREM Software Development < ***@***.***> wrote: @tsg2k2 <https://github.com/tsg2k2> ??? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#301 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ4IXSM3NOF6TGJSH5UI473R3YLUPANCNFSM4OZ5SBIA> .

[VREMSoftwareDevelopment]

There are no attached screenshot in your previous comments/emails

[tsg2k2]

Attempt #2

…

On Thu, Jul 16, 2020, 9:05 AM VREM Software Development < ***@***.***> wrote: There are no attached screenshot in your previous comments/emails — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#301 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ4IXSNTFHALT65P4UDEFRTR333JTANCNFSM4OZ5SBIA> .

[VREMSoftwareDevelopment]

Still no attached screenshot

[tsg2k2]

Apparently github email handler strips images. Here is the one attached via web

[VREMSoftwareDevelopment]

Application is relying on the Access Point information provided by Android API.
https://developer.android.com/reference/kotlin/android/net/wifi/ScanResult

Based on the information you have provided, there are two possibilities:

• Android API returns incorrect channel width
• Android Device does not support 160Mhz width

Please connect to your router and check what is displayed as connection information in the router when android device is connected (80Mhz or 160Mhz width). This would help to determine whether it is an Android API or Android device issue

[tsg2k2]

The phone doesn't support 160mhz, it connects to this router at 2x2@80mhz (866mbit phy rate). I was under assumption that channel width is advertised by AP and this info is available for device irregardless of it's ability to utilize full width. Seems like it's happening via beacon packets https://www.engeniustech.com/wi-fi-beacon-frames-simplified/ This leaves only one possibility, it seems...

…

On Sat, Jul 18, 2020, 9:24 AM VREM Software Development < ***@***.***> wrote: Application is relying on the Access Point information provided by Android API. https://developer.android.com/reference/kotlin/android/net/wifi/ScanResult Based on the information you have provided, there are two possibilities: - Android API returns incorrect channel width - Android Device does not support 160Mhz width Please connect to your router and check what is displayed as connection information in the router when android device is connected (80Mhz or 160Mhz width). This would help to determine whether it is an Android API or Android device issue — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#301 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ4IXSNW3DIHS2VLBW2P5BDR4GPALANCNFSM4OZ5SBIA> .