I have a new arrival, a new S21 Ultra 256 (SW-G998B). A dbrand black swarm grip case is on the way. (thanks for the recs). It replaces an ancient Nexus 6 whose battery was starting to swell. Now, I will have something current to hack on once I give it some time to make sure everything is settled. I'm curious how much control Flutter can exercise on the cameras, but that's another topic not related to this one. Nova Launcher 7 (prime) is working well as is DroidCamX from my Surface Book 2. Most things with the S21 Ultra seem to be working well.
The biggest issue at the moment is with the 5GHz wifi. It just doesn't appear in the list and manually trying to join doesn't work either. It's a ZTE router with both 2.4 and 5GHz active. Multiple devices are on both. The phones, ipads, and laptops are on the 5GHz while the Roomba and a Mi LED light are on 2.4. With the other devices using it okay, I'm guessing that's not the issue. I tried some solutions with the S21, wiped the cache partition, played with the hotspot band, and enable/disable wifi scanning for location. I set the hotspot to 5GHz preferred and was able to join it from my iPhone 11 Pro. The S21 can join the iPhones hotspot. It both cases, I don't know specifically what was used, 2.4 or 5. But, with all of this, the 5GHz SSID from the ZTE router still will not show in the list and cannot be used. I had seen mention of a WiFi band frequency selector, but that doesn't appear to exist any more. On the router, the channels for both are set to auto, but the status shows SSID1 (2.4) is on channel 1 and SSID5 (5) is on channel 100. From what I've read about how advanced the S21 Ultra wifi is supposed to be, in theory, the S21 should not be limited on which channels are supported. Any thoughts on why other devices can connect and use 5GHz wifi, but the S21 cannot? Any ideas on what I might check/test next?
Thanks
Tim
Did you try other routers? That's the only way to make sure it's your phone's fault or your router.
The issue is solved.
I did not test other routers. With the Covid/quarantine situation, I don't visit other homes and thus don't have easy access to other routers. I would have to stumble across one.
But, thanks for the impetus to check something. I pulled out my ancient Nexus 6 to test with. It did not see the 5GHz SSID either. But, it did have Wifi Analyzer installed. With that, I was able to filter for 5GHz only and saw another SSID appear. When I ran Wifi Analyzer on my S21, I saw that same 5GHz SSID. So, the phone was seeing 5GHz. Wifi Analyzer also provided a crucial bit of information to the puzzle. On the graph across the bottom, it was only showing channels 34 to 50. So, the channel 100 the router selected when on 'auto' was way outside of the range. I had even selected channel 100 in Wifi Analyzer, but that did not help it appear. I updated the router and changed the channel to one near the middle of that range that was not being used by other nearby SSID on either band. Now, the S21 was able to see my router's 5GHz SSID in the list and joined it with no problems.
As advanced as the S21 Ultra is, it does not appear to support channels in ranges as high as either the iPhones, iPads, or my laptops. Since the Nexus 6 had the same issue, it's possible this is an Android limitation and not specific to the S21.
TimButterfield said:
The issue is solved.
As advanced as the S21 Ultra is, it does not appear to support channels in ranges as high as either the iPhones, iPads, or my laptops. Since the Nexus 6 had the same issue, it's possible this is an Android limitation and not specific to the S21.
Click to expand...
Click to collapse
Glad you got it sorted out. But my wifi is configured to auto select channels based on traffic, and it is currently running on Channel 149 without any issues. So assuming that the S21U cannot utlize channels that laptops or ios devices can may not be entirely correct. Also, this is not an android limitation. My wife's 3 year old OnePlus also uses the same 5GHz network without any issue.
My suggestion would be to look at your router settings again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
enigmaamit said:
Glad you got it sorted out. But my wifi is configured to auto select channels based on traffic, and it is currently running on Channel 149 without any issues. So assuming that the S21U cannot utlize channels that laptops or ios devices can may not be entirely correct. Also, this is not an android limitation. My wife's 3 year old OnePlus also uses the same 5GHz network without any issue.
My suggestion would be to look at your router settings again.View attachment 5374593
Click to expand...
Click to collapse
Hmmm. Thanks for that info. That was the only setting changed. Perhaps I need to play with other channel values to be sure.
I played with the channels some more. This ZTE has a drop down selector for channel choice. There are steps of 4 from 100 to 128. If any of those is selected, that 5GHz SSID does appear in the list on the S21. There is a gap in the selection between 64 and 100. If manually set to 64 or lower or if a 64 or lower channel is chosen by auto, then that 5GHz SSID is listed and can be used on the S21.
I'm not quite sure what else to make of this yet. The only thing being changed is the channel and that seems to control the S21 working or not, though the other devices are fine. The router belongs with this rental apartment. So, I'm reluctant to hack too much on it.
I think it's mostly due to FCC regulations (if you're in the US). I know that there are more 5 GHz channels available in other countries that are not available here because of previous allocations. Probably your router/hotspot isn't running US specific firmware and when set to auto it might use frequencies that your phone has locked out. Your doing the right thing by manually assigning an unused channel on the router/hotspot. Just check it occasionaly to see if someone else is using the same channel should your signal degrade.
TimButterfield said:
I played with the channels some more. This ZTE has a drop down selector for channel choice. There are steps of 4 from 100 to 128. If any of those is selected, that 5GHz SSID does appear in the list on the S21. There is a gap in the selection between 64 and 100. If manually set to 64 or lower or if a 64 or lower channel is chosen by auto, then that 5GHz SSID is listed and can be used on the S21.
I'm not quite sure what else to make of this yet. The only thing being changed is the channel and that seems to control the S21 working or not, though the other devices are fine. The router belongs with this rental apartment. So, I'm reluctant to hack too much on it.
Click to expand...
Click to collapse
Seems to be an issue with the router then. We've established that older as well as newer phones can use higher channels successfully. The only variable here that needs changing is the router (or its settings). Without that, I'm not sure how we can investigate further.
But if you've found a temporary fix for your issue, I'd suggest leaving it at that for now, till you get access to a newer or more capable router. I'm using an Asus RT-AC86U btw, if it's any help.
blaacksheep said:
I think it's mostly due to FCC regulations (if you're in the US). I know that there are more 5 GHz channels available in other countries that are not available here because of previous allocations. Probably your router/hotspot isn't running US specific firmware and when set to auto it might use frequencies that your phone has locked out. Your doing the right thing by manually assigning an unused channel on the router/hotspot. Just check it occasionaly to see if someone else is using the same channel should your signal degrade.
Click to expand...
Click to collapse
I have no knowledge of legal requirements for WiFi bands or channels on phones in the USA, so you might be right. In which case, I'd withdraw my conclusion about the router. But he mentioned that other devices are able to use the 5GHz including iPhones and iPads. So I'm not sure why a 2021 phone shouldn't be able to do the same.
Yeah, I don't keep up with the changes that they make, but it's likely it has something to do with that.
Thanks for the ideas. I'm US, but this issue is not US related. The S21 Ultra is Exynos/SW-G998B/SER (Russia) and the router is in Belarus (2nd location on profile). So, no US limitations between these two. The iPhones, iPads, and laptops are US that I brought with me. If anything, it seems they would be the devices that would not work, but they work fine. It kind of makes me wish I had my Google wifi to test against. Since the ZTE is now working with the S21, finding a different solution is not required. It is an interesting puzzle, though.
TimButterfield said:
Thanks for the ideas. I'm US, but this issue is not US related. The S21 Ultra is Exynos/SW-G998B/SER (Russia) and the router is in Belarus (2nd location on profile). So, no US limitations between these two. The iPhones, iPads, and laptops are US that I brought with me. If anything, it seems they would be the devices that would not work, but they work fine. It kind of makes me wish I had my Google wifi to test against. Since the ZTE is now working with the S21, finding a different solution is not required. It is an interesting puzzle, though.
Click to expand...
Click to collapse
You've done the easiest fix for the problem without flashing firmware onto your router or phone!
Related
German G1, stock firmware CRC37, 2.6.27-00393-g6607056
Well, I am in the process of upgrading to 802.11n routers. At my family's place this turned to be a Linksys WRT160N, here at home it's a Buffalo WZR-HP-G300NH.
With both routers, I am having trouble establishing reliable connections. I've been looking a bit more into it with my Buffalo router: the phone connects to the WLAN, but finally, varying from a few seconds to several minutes, i receive timeouts resulting in UnknownHostExceptions. Toggling wifi will restore connectivity, just to run into the same problem again.
I have had no problem with my Linksys WRT54G, nor with any other devices in my place (two 802.11n devices, a MacBook Pro and an AppleTV). There's also a Wii (802.11g/b?!) and an HP 2133 (802.11n) I haven't tried yet.
The Buffalo router operates on a custom Linux, 40MHz bandwidth, WPA2/AES in the 2.5MHz spectrum, 3 Antennas, 300MB (mimo).
All in all, googling makes me believe that a fair amount of people have problems in similar settings, but none of what I found could point directions into a solution.
Router setup is not the issue (i have been able to reproduce in two totally different setups that work with any other devices I have tried). Neither do I believe that a mix of 802.11g and 802.11n devices necessarily causes these kind of problems (at my family's place a 802.11g imac works flawlessly alongside of my 802.11n MacBook in an 802.11n network).
I am attaching a logcat that I captured while producing the problem. It only illustrates the problem a little.
In the end, probably the broadcom WLAN chip/driver gets stuck at one point and android cannot do much against it. If this is the case, posting a bug report against google/android open source developers probably won't help much, as it seems to be an issue of the driver/wifi chipset combo HTC/TMo uses in the G1.
If you agree on this, in the end I am looking for a way to file a bug report either at htc or t-mobile, but contrary to Android/Google, I haven't found anything on the net that I can file a bug report into... 1.0 companies *sigh*
What other ideas do you have? While I could leave the G1 just on 3g while at home, I don't have reception in every corner and the whole point of having it is being online essentially most of the time in order to catch my mail (it is set to keep wifi on while charging).
Regards
Interestingly, if I start streaming after connecting to WIFI, like speedtest or YouTube, the connection stays alive for the time being...
I just junked a netgear router with misbehaving wireless and nabbed a new one (Linksys WRT120N if you're curious) with N capability last night. I was hoping to get my SGT to connect at N speeds but unfortunately it keeps wanting to connect at G speed (54mbps). I've tried setting the router to N-only mode and the tablet still sees the AP, but it attempts to connect for a moment then goes back to scanning for APs. Yes, I've got great signal strength since I am sitting ~5 feet from the AP (the SGT icon shows full blue icon, my dbm is -34 for those of you that understand what it means).
Is the tablet's N capability disabled? I double checked the specs of my SCH-I800 on Verizon and Samsung's site and both say that the tablet has b/g/n wifi capability.
If you're nosy and want to know why in the world I'd even need N speeds, I have half a dozen computers in my house and some of them (thank you Microsoft) can't see the others for file transfers, so I copy the files over to my tablet from the source, then to the target. Not the best solution but I'd rather not toss up applications on all the computers and I haven't bothered buying equipment for a NAS device yet.
So... any revelations?
Samsung product info page: http://www.samsung.com/us/mobile/galaxy-tab/SCH-I800BKAVZW-features
Verizon product info page: https://www.verizonwireless.com/b2c...tail&selectedPhoneId=5565&deviceCategoryId=12
Dunno, I've got mine running on N just fine... Some of the lower end linksys routers have issues with N. You might look into dd-wrt and see if your router is compatible..
Sent from my SPH-P100 using XDA App
I've got a Linksys E3000 running Tomato, and my Tab connects. Notably, however, the Tab only supports some of the 5GHz channels and not others.
manekineko said:
I've got a Linksys E3000 running Tomato, and my Tab connects. Notably, however, the Tab only supports some of the 5GHz channels and not others.
Click to expand...
Click to collapse
Pretty sure it only supports the 2.4ghz range of N. I could be wrong, but I doubt they would have included the 5ghz range of N wireless capabilities..
pvtjoker42 said:
Pretty sure it only supports the 2.4ghz range of N. I could be wrong, but I doubt they would have included the 5ghz range of N wireless capabilities..
Click to expand...
Click to collapse
No, it supports 5Ghz range as well, just not all channels as I stated. My router is dual radio, and I have one SSID running at 2.4 and one SSID running at 5, and the Tab is connected to the 5 one.
It noticeably scans the 2.4 range before the 5 range, so first the 2.4 access points appear, and then the 5.
My personal experience was that I was able to achieve much much better download speeds by setting my router (WRT310N) to G mode only.
Before hand, when it was set to mixed I was getting speeds of like 1mbps download tops. Now I get 15+.
manekineko said:
I've got a Linksys E3000 running Tomato, and my Tab connects. Notably, however, the Tab only supports some of the 5GHz channels and not others.
Click to expand...
Click to collapse
Would you mind mentioning 'some' of these channels so I don't have to manually go through all of them one by one to see if it'll work with my SGT?
LycaonX said:
Would you mind mentioning 'some' of these channels so I don't have to manually go through all of them one by one to see if it'll work with my SGT?
Click to expand...
Click to collapse
Sure, no prob, I've got mine working on channel 36.
You can also take a look at my other post on this topic:
http://forum.xda-developers.com/showthread.php?t=1158878
Since my Chromecast updated to 16664 (official) last week, I have had a bear of a time having any device see the Chromecast. Prior to the upgrade, I didn't have any issues with connectivity. Now the only way I can get the device to work is to do a reset to defaults and go through the setup procedure. The CC will generally work until the next power-up, then the same thing.
When this happens, the ChromeCast's home screen indicates it's connected to my WiFi network, however no Chromecast enabled program, including the Chromecast app on my phone, sees the device.
There have been no changes to my wireless network settings since it worked last. Given that I've not seen anyone else post about this, I must be the only one seeing the problem. Anyone?
I've seen some similar reports over at Plex but not here...
I myself am on 16664 and have no issues seeing my device.
try a Factory reset and see if reconnecting helps at all.
I've had a similar experience. My Galaxy SII and Galaxy tab 3 can see my Chromecast, but when I run the Chromecast app from my Kindle Fire HD, I get the message "No Chromecasts found on <network>". If I do a factory reset on the Chromecast, then the KFHD will find it, but once it's setup, I won't find it again. For me, the solution was to unplug my TiVo Premiere and TiVo Roamio from my network. Then the KFHD can find and cast to the Chromecast. But if either TiVo is connected to my network, the KFHD can't find the Chromecast. It's weird that this only affects the KFHD and not my other android devices.
SFDave said:
I've had a similar experience. My Galaxy SII and Galaxy tab 3 can see my Chromecast, but when I run the Chromecast app from my Kindle Fire HD, I get the message "No Chromecasts found on <network>". If I do a factory reset on the Chromecast, then the KFHD will find it, but once it's setup, I won't find it again. For me, the solution was to unplug my TiVo Premiere and TiVo Roamio from my network. Then the KFHD can find and cast to the Chromecast. But if either TiVo is connected to my network, the KFHD can't find the Chromecast. It's weird that this only affects the KFHD and not my other android devices.
Click to expand...
Click to collapse
TiVos use mDNS advertising for their services.
Recent Chromecast firmware also seems to be using mDNS as well.
Try running Bonjour Browser and see if Chromecast is visible before/after reset or reboot.
Not sure if related but it may help.
My router has 2 channels, 2.4ghz and 5ghz, the chromecast is connected to the 2.4ghz of course, the issue is when another device is also using the 2.4ghz it wont see the chromecast for some strange reason, the second I connect that device to the 5ghz network it will see it and everything will work flawlessly.
kishke said:
Not sure if related but it may help.
My router has 2 channels, 2.4ghz and 5ghz, the chromecast is connected to the 2.4ghz of course, the issue is when another device is also using the 2.4ghz it wont see the chromecast for some strange reason, the second I connect that device to the 5ghz network it will see it and everything will work flawlessly.
Click to expand...
Click to collapse
If your router has a WMM option, try toggling it - on some routers WMM implementation is broken and makes things worse when it tries to kick in and make your media streaming better.
Also, if you're streaming local content from another wireless device you may be exceeding the available bandwidth on the band - see WiFi Bandwidth and Router Considerations for diagrams on how the bandwidth usage can multiply depending on how content is being accessed.
bhiga said:
If your router has a WMM option, try toggling it - on some routers WMM implementation is broken and makes things worse when it tries to kick in and make your media streaming better.
Also, if you're streaming local content from another wireless device you may be exceeding the available bandwidth on the band - see WiFi Bandwidth and Router Considerations for diagrams on how the bandwidth usage can multiply depending on how content is being accessed.
Click to expand...
Click to collapse
Streaming is fine (using plex with pc as dlna) it's just a weird issue that used to happen, haven't noticed it in a while because our phones always connects to the 5ghz network. WMM is on so if it happens again I'll try playing it.
Also I doubt I'm even getting close to the wireless bandwidth cap.
Thanks for your reply tho!
kishke said:
Streaming is fine (using plex with pc as dlna) it's just a weird issue that used to happen, haven't noticed it in a while because our phones always connects to the 5ghz network. WMM is on so if it happens again I'll try playing it.
Also I doubt I'm even getting close to the wireless bandwidth cap.
Click to expand...
Click to collapse
Weird... Might also be a more general network thing like a rogue device with a static IP causing a collision that Chromecast doesn't gracefully recover from, or a multi-interfaced device causing some kind of loop
But yeah, since you have 5 GHz, best to use that and keep your 2.4 GHz usage to a minimum to maximize available bandwidth for Chromecast..
Let me try a few of the suggestions here. I've not had any luck using 2.4 or 5GHz bands on my network...behavior is the same. Also, my router is an ASUS router with Merlin firmware. There is a new thread I've only glanced over, but I'll try some of the things there as well:
http://forum.xda-developers.com/showthread.php?t=2599515
I had to do the factory reset trick again last night so we could watch video on the Chromecast...it obviously hasn't gotten annoying to the point where I'm stopping all other activity until I get it fixed, though. Strange this only started happening after the Chromecast update, but I can no longer remember the sequence of events that go me here (chromecast update, router update, wireless AP added for better wireless coverage, etc).
I've seen similar behavior when there are just too many devices connected to the WiFi at once.
My router maxes out at around 9-10 devices...
Doesn't matter which band they are on either.
But to be sure it isn't an IP conflict I suggest setting DHCP reservations for all your regularly connecting devices to ensure they never get a different IP (especially important to do for servers like Plex) and remove that possibility from the equation.
Just to Add I believe the new 802.11AC Standards solve this problem, But you will need to buy a new router to get it.
Using a bonjour browser, I can see the entry for the Chromecast :
_googlecast._tcp.local.
Bedroom.local.:8009
/192.168.254.193
st = 0
ve = 02
md = Chromecast
ic = /setup/icon.png
id = [a very long number]
fn = Bedroom
ca = 5
Click to expand...
Click to collapse
I'm running the browser that sees that from a Samsung tablet, which is also running the Chromecast setup app that says it can't find the Chromecast.
EDIT: I've tried the factory default recovery method a number of times now. I see the bonjour record go away, then come back after the setup app says I'm ready to cast. All apps can see the Chromecast at that time, then after 3 to 5 minutes, they no longer see the Chromecast. I don't see any difference in the bonjour record when it working from when it's not working.
troycarpenter said:
Using a bonjour browser, I can see the entry for the Chromecast :
I'm running the browser that sees that from a Samsung tablet, which is also running the Chromecast setup app that says it can't find the Chromecast.
Click to expand...
Click to collapse
Just a longshot....But do you have any security software that could be blocking some Apps from communicating with the Network?
It sounds an awful lot like what happens when an AntiVirus Application Monitor has denied access.
Hmm, No, I don't think so.
But I found something interesting. My laptop CAN see the Chromecast, and I can cast Chrome tabs just fine. So far it's only the Android devices that can't see the Chromecast (and at the same time the laptop can). I'm looking for my iPad (I don't use it enough to keep track of it as close as I should) to see if it sees the Chromecast or not.
troycarpenter said:
Hmm, No, I don't think so.
But I found something interesting. My laptop CAN see the Chromecast, and I can cast Chrome tabs just fine. So far it's only the Android devices that can't see the Chromecast (and at the same time the laptop can).
Click to expand...
Click to collapse
That's really odd. Your network has only the ASUS router for wireless, no repeaters or extenders?
-= this post enhanced with bonus mobile typos =-
bhiga said:
That's really odd. Your network has only the ASUS router for wireless, no repeaters or extenders?
-= this post enhanced with bonus mobile typos =-
Click to expand...
Click to collapse
I do have an extender (not a wireless repeater) in place, but it didn't make any difference before the latest Chromecast update. My next step is to try removing the extender, but I don't know if the Chromecast will see the signal coming from the other side of the house (the reason the extender was put in to begin with).
troycarpenter said:
I do have an extender (not a wireless repeater) in place, but it didn't make any difference before the latest Chromecast update. My next step is to try removing the extender, but I don't know if the Chromecast will see the signal coming from the other side of the house (the reason the extender was put in to begin with).
Click to expand...
Click to collapse
It's quite possible that the update changed something about the WiFi connection that your network simply does not like. People have noted similar "introduced issues" with HDMI before. Definitely submit a report with them if you haven't already, and request that updates NOT be forced to avoid issues like this. Being able to dismiss, postpone or even roll back an update would prevent this type of thing.
If it's not the build, I'm not sure what else it might be, unless your router has somehow quarantined your other Android devices on another band or SSID somehow.
bhiga said:
It's quite possible that the update changed something about the WiFi connection that your network simply does not like. People have noted similar "introduced issues" with HDMI before. Definitely submit a report with them if you haven't already, and request that updates NOT be forced to avoid issues like this. Being able to dismiss, postpone or even roll back an update would prevent this type of thing.
If it's not the build, I'm not sure what else it might be, unless your router has somehow quarantined your other Android devices on another band or SSID somehow.
Click to expand...
Click to collapse
Looks like I switched off TKIP and just went AES on that network at some time. I went back and turned on AES+TKIP and now the Chromecast shows up on my mobile devices again. I'll keep an eye out in case that theory doesn't hold out.
Hi everyone,
I have a problem with my new P30 Pro. When I create a Hotspot in 5ghz frequency, no other device can find that Hotspot. If I change frequency to 2.4ghz then other devices can connect to the network. Maybe others have the same problem? Or my device is faulty ?
BTW when I'm connecting to Wi-Fi, either 2.4 or 5ghz, everything works fine
Maybe it uses a channel, that your other devices do not see. I think different regions use different wifi channel ranges. Maybe you find an option for that somewhere in advanced wifi settings.
I just tried on mine. My laptop pics up the hotspot on the P30 Pro no matter if it's 5 or 2.4GHz, no problem.
schriss said:
Maybe it uses a channel, that your other devices do not see. I think different regions use different wifi channel ranges. Maybe you find an option for that somewhere in advanced wifi settings.
Click to expand...
Click to collapse
I didn't find any advanced settings regarding channel ranges / regions.
BTW my phone is C431 if it's good or not, I don't know. I remember C432 used to be the best region code, if you could say so. My P20 pro is C432.
How the problem started, I bought P30 Pro, opened phone clone app, I wanted to transfer data wirelessly from one phone to another. But devices didn't connect, tried multiple times. After that I started experimenting with 2.4 ghz or 5ghz Hotspot. And found out that other devices can't find 5ghz frequency.
jacobtf said:
I just tried on mine. My laptop pics up the hotspot on the P30 Pro no matter if it's 5 or 2.4GHz, no problem.
Click to expand...
Click to collapse
My laptop sees 5ghz Hotspot, but can't connect to it. P20 Pro, honor 8, nexus 6P can't even see that. Samsung S10 can connect to 5ghz. It's very strange
EMUI 9.1.0.153 resolved the issue
Nope, it didn't. I'm still having problems - my notebook can see the hotspot, and can connect to it, but the phone just won't share the internet connection.
Bluetooth is turned on, and bluetooth tethering as well, 2.4 or 5 GHz.
I tried USB tethering. Tried apps from the store. Always the same thing - notebook can see the hotspot, but internet is not working. Any ideas? The notebook is Asus Rog G751. I'm on 9.1.0.1.178.
Same here. Laptop works on home 5ghz, but wont even see p30 pro 5ghz, its strange
Worst part is, 3 months ago it was working. Since I don't use it except when travelling, I have no idea what could have changed in the mean time.
In my case, max user connections was limited.
- press "Show advanced options"
- press "Max connections allowed"
- increase the value
augis0211 said:
Hi everyone,
I have a problem with my new P30 Pro. When I create a Hotspot in 5ghz frequency, no other device can find that Hotspot. If I change frequency to 2.4ghz then other devices can connect to the network. Maybe others have the same problem? Or my device is faulty ?
BTW when I'm connecting to Wi-Fi, either 2.4 or 5ghz, everything works fine
Click to expand...
Click to collapse
Hi guys,
what network cards are your PC using?
Mine has a Killer Wireless 1535 built in and I can confirm this problem:
P30 (pro) switched to 5 GHz hotspot mode and PC cannot find it.
I think I may have found a reason for it, which needs to be resolved by a manufacturer (Huawei or a network adapter manufacturer - no idea if only Killer is affected):
The Huawei P30 (pro and normal model) seems to default the broadcast channel to channel #149 (5.745 MHz) when switched to 5 GHz hotspot mode.
This is a DFS channel in the only recently approved new upper channel range.
Apparently the killer 1535 cannot or cannot use these channels yet.
Actually it won't see it first. Then, when changing connection mode in the adapter property, it is found.
But after inserting the ssid password, access is not allowed and ssid vanishes from list.
Just like a restriction to invalid channels.
The broadcast on 5 GHz itself works, which I proved with another P30 which can access the AP of the first one.
However my notebooks (all using Killer Wireless cards) as well as a Samsung tablet can't.
So resolution could be:
1. Killer adapts its drivers or
2. Huawei defaults to a 5 GHz broadcast channel in lower, more common, 5 GHz band between ch7 and ch60 e. g.
(Or adds a user-accessible menue allowing selection of broadcast channel.)
I've been getting a slow to fair connection on Steam Link, which really bothers me. I have 1GBPS WiFi from Xfinity with 40MBPS upload speed, both of which should allow me to connect to my computer very well. My computer is hardwired via ethernet, so that's not a problem, however Steam Link never labels my connection "Good." I have heard that this is the result of the WiFi on board Android opting to pick 2.4Ghz, and I've been looking to disable it. I couldn't get the package to install on Fox's Magisk for the 2.4Ghz WiFi disabler add on, so I searched around the forums and checked both my settings, as well as developer options. I even looked in data/misc/wifi, but there wasn't anything there I could tinker with to help with this. I did turn WiFi safe mode on in hopes to improve the stability of my device's WiFi, but this is as far as I've gotten.
Does anyone have suggestions for disabling 2.4Ghz or otherwise increasing my WiFi speed on here? I would really like not to have to seperate the bands manually, as last time that caused a host of problems with other people's devices in my household.
For what it's worth, and I'm aware this doesn't answer your question directly, nor help you right away, but my router allows me to use a single SSID for both 5GHz and 2.4GHz, and it automatically connects at the highest frequency a device can handle.
My point is that I don't think the issue is Android, because I've consistently gotten 5GHz Wi-Fi on my Pixel and Samsung devices in the last four years I've had this router.
I know you already discount this possibility but just for anyone else who comes across this...
Other than possibly buying a different router (I use Synology routers, and they just came out with a new one that I might upgrade to sometime), another potential workaround is for you to configure your router to use different SSIDs for the two frequencies, and then just never connect from your Tablet to the 2.4GHz SSID. I know this might be a PITA or possibly even just not a realistic solution, depending on how many other devices (smart devices) you already have configured to connect to your existing SSID.
roirraW edor ehT said:
For what it's worth, and I'm aware this doesn't answer your question directly, nor help you right away, but my router allows me to use a single SSID for both 5GHz and 2.4GHz, and it automatically connects at the highest frequency a device can handle.
My point is that I don't think the issue is Android, because I've consistently gotten 5GHz Wi-Fi on my Pixel and Samsung devices in the last four years I've had this router.
I know you already discount this possibility but just for anyone else who comes across this...
Other than possibly buying a different router (I use Synology routers, and they just came out with a new one that I might upgrade to sometime), another potential workaround is for you to configure your router to use different SSIDs for the two frequencies, and then just never connect from your Tablet to the 2.4GHz SSID. I know this might be a PITA or possibly even just not a realistic solution, depending on how many other devices (smart devices) you already have configured to connect to your existing SSID.
Click to expand...
Click to collapse
I mean, the two seperate SSID's is a valid solution, just one I'm not currently willing to use.
Here's something strange that made me believe that it's an Android issue. I previously used Steam Link on an IPad and got a good connection, I then moved over to Android and don't. It's very bizarre. I also can't backspace in Chrome Remote Desktop on Android for some reason. Also bizarre.
I do totally want a new router, but I'm tapped out of money for the foreseeable future anyway. We have the most up to date Xfinity router though, which I think is from 2018 or some such thing, to its credit, the internet almost never disconnects, and when it does, it fixes itself within around 60 seconds. Previous xfinity routers would disconnect frequently, and would require a reset to get working again.
Easiest is to have two different SSID's and different password for each. That way your galaxy tab will only connect to 5GHz and won't use 2.4GHz as long you don't connect to it with password for it.
Since if you name 2.4GHz and 5GHz same SSID then it will connect to 2.4GHz or 5GHz and keep switching since both have same SSID and password.