Related
Hello,
I have just upgraded to the official GPS ROM and I am on the Swedish 3 operator. I have noticed since the upgrade that the network connection is switching from 3G to HSDPA when there is a demand of bandwidth or simply when there is data in either direction.
I can see that the purpose of this was to make it possible and more reliable to place and receive calls during data sessions. I have figured out though, that with the old ROM, there was no such switching (but there was no distinction with the icon, so you really had no idea) and the connection speed was always constantly 1Mbits/s when using Internet Sharing for example. Now with the HSDPA/3G switching/throttling, the connection often drops down to 3G speeds and Skype-calls are lacking quality from this a bit when using Skype in the car which i do quite regularly nowadays using my Jabra JX-10 headset.
I also realize that there is still a problem with outgoing and incoming calls during these automaticly switched-on HSDPA-sessions. That is probably why HTC has decided to keep the HSDPA sessions as short as possible, that's fine, but what boggles me is the algorithm used for the switching. It seems to always kick in HSDPA in the beginning of a new data session, and after a short time of inactivity (while pondering what favourite page to open this time) the connection drops down to 3G and it won't kick back to HSDPA even when you start browsing again, until a certain period of "non-HSDPA-ratio" has been reached and the phone thinks it would be OK to kick in the highspeed again for a little while.
I also noticed that using Skype would keep HSDPA alive once you place a call from a fresh started data session and keep talking ;-)
This is not a particular problem to me, I was just wondering of anyone else here has noticed and had an idea of what the programmers had in mind?
BTW: I am running TomTom 6.010 and Franson GpsGate on the machine now and it works absolutely like a dream. I used to have a Blue-I Bluetooth GPS in the car (Trimble based chipset, only 8 channels but quite OK piece of hardware) but this is far superior when it comes to HOLDING a persistent fix also when moving indoors. The TTFF is quite fast as long as you are outdoors, most of the time i have a fix before i leave the parking space. I noticed there being a dynamic number of satellites of the receiver, sometimes i see 7 out of 8 satellites, and then sometimes i see 10 out of 12! Anyone noticed?
Thanks in advance! Cheers...
It’s not your phone that decide to change from HSDPA mode to normal R99 (384kbits) mode and vice versa. Everything are always controlled by the network. The behaviors that you describe are normal. Besides the HSDPA is quit new for the operators and new parameters needs to be tuned for best performance for every users.
BTW, the degradation that you notice. You are not alone that use HSDPA.... Its finally the big success for 3G
I use Phone Alarm profiles and BandSwitch to control my connection based on business hours. I get a poor singal unless on 3G where my office is located. I force it to GPRS otherwise to save battery.
I have similar problems, cannot receive or start calls when HSDPA connected. Shouldn't that be possible anyway, calling and transferring data at the same time? Or is this a network provider problem?
I too am on the Swedish operator 3. I have an unlocked, non-operator distributed HTC TyTN that I had updated the radio to 1.40xxx and the ROM to Black Dymond 3.5 and was having the exact same problem. I could reproduce the incoming call not getting through error every single time I got the phone to go into HSDPA mode.
After some initial searching I read somewhere it was network dependent (Nokia switches vs Ericsson) and the only way to solve it was to disable the HSDPA using e.g. HTweakC, which I did and it solved the problem, but then of course I couldn't take advantage of the high-speed data access, which was the major reason I got this phone.
I recently noticed that 3 released a new extended ROM with instructions to update the ROM to the latest (as is available on the ftp here) then install their ExtROM. I went to the trouble to try and breakdown what was in this extended ROM, but being a newbie to pocketpc it was all hyroglyphics to me, so I went ahead and installed it over my old HTC ext ROM (which I saved for later use just in case).
When I get around to it I may mount this extended ROM here (I have it, but don't have too much time to put it up right now, so someone may beat me to it).
Anyway, Black Dymond 3.5 didn't install the Extended ROM after a hard reset (assuming that was the intention), so I did it myself afterwards. One initial bug that showed up quickly was the Comm Manager not wanting to start saying it would only manage a max of 7 items (whatever that means). So I installed Schaps latest Comm Manager and it worked fine.
Well, guess what, now there's a daemond that starts on boot and the phone app is different (another bug is that the text on the phone app buttons remain in the 3 theme although I changed back to black, but that's minor), but now I cannot replicate the no incoming calls during HSDPA error.
Apparently they've added something that makes the phone connect properly to their 3G/HSDPA network for call handling. Now I've got full HSDPA speed and no problem on incoming calls (plus still have Black Dymond's great VOIP/SIP WM6 solution).
Ok, as a noob I of course missed the fact that the daemon starting at boot is Voice Commander. Still the actual phone app/dll is somehow different with this ExtROM and it's solved my problems.
Hi all. Sorry to start another thread about wifi on the Universal, but there seems to be no resolution in any of the others;
http://forum.xda-developers.com/showthread.php?t=322054
http://forum.xda-developers.com/showthread.php?t=292210
http://forum.xda-developers.com/showthread.php?t=321872
... and these are just the recent ones. It seems there are a lot of us having problems with wireless range/reception. I think the basic questions we're asking are:
1. Is it a problem with the router/ap or the phone?
2. If it's the phone, can it be resolved with a software fix?
3. If it's the phone, is it another problem in the vein of SD cards (some work, some don't, depends on your phone)?
4. Do any of the more experienced members have these issues, and if so, what did they do to overcome/circumvent them?
I know i'm asking a lot here, but I think we would be grateful of even a sticky thread saying "There's nothing you can do about poor WiFi range" - at least then we'd know.
Many thanks in advance,
Gurney Man
Okay - might be onto something...
As stated in another thread, I just installed Radio 1.18 to see if that'd help. Uni said I had a Wireless connection to my network as I was rebooting it... i'm in the other room, so that's promising. However, I now get a nice SDDaemon error on boot...
More on this exciting story as it happens folks.
*edit*
Next on the list - ActiveSync has decided it doesn't like the phone now. No contacts sync-ing... Ugh.
I think it becuase if speed
i checked the AP(router) when the ppc(universal)connects to it,and i realized that it connects only with 11mbps speed even when the signal is low but with laptop i can connect with other speed like 5 2 1 mbps i think if we could configure universal to connect with 1 mbps we can get the most range. does someone knows how to set the speed to 1 mbps?
Radio upgrade doesn't seem to have helped.
It's an idea at least. Could we not change the connection settings on the router itself? Probably a daft question, as I imagine we've tried the Universal at other APs and still got poor reception.
Continuing my voyage of discovery, after upgrading to Radio 1.18, my comm's manager doesn't work properly, and wireless still doesn't work very well. Should I try an earlier Radio version (1.15) before I put all of my contacts n' settings back on the device?
Regards
Gurney Man
My friend have a nokia N80 and I did some tests, some time ago.
The reception is better. for example universal couldn't connect to wireless AP and N80 it's able to surf on Internet. At the same distance.
What I remener is that the N80 was able to connect at slow perfermormance , connected at 1Mbps and Universal was 11Mbps or nothing...
As you now slow performance is better distance... But I can't tell this to my universal , it always try to get higher performance and not higher distance...
do you know any solution to get connected with 1 Mbps?
Louder!
lol - still don't think we'll get any help. I assume now that there's no fix to this issue. The senior members here jump all over solveable problems - they haven't even corrected our grammar
Regards
Success!
okay, so this is probably I couldn't connect. All I had to do was change the settings on the router to only use wireless B, and I got reception. I felt ballsy after that, so played with the channel settings too, and guess what - changing the channel gave me even better reception. I would recommend any of you guys having the same problems to tinker with your router settings - if you don't have a 'puter wired to the router be careful, you might end up having to hard reset it, but otherwise go for it!
... now to reflash everything and get all the settings back... and get a better browser.
Regards
and then...
when I re-flashed, I assumed radio 1.18 was the cause of the issues I was having, aside from the wifi. Re-flashed to 1.15... no wireless. Going back to 1.18 again. Sheesh.
is 1.18 better than 1.15 in wifi?
I think so...
I seem to get an extra couple of metres with 1.18 - still not exactly the free roaming wireless I was hoping for, but better than just putting the device next to the router to get a weather update for Spb and nothing else.
Very Strange. Mine work well
Radio 1.18. WM6 2.02.02
2 walls (30 cm). No poblem. I've not encoured such problem. (thanks god). In open space, I've got even 50 meters reception (from hotels). So, I'm kind of an alien here no?
Regards,
Cristian Nica
i thought 1.18 was weeker....
nlcluigi , did you always have that good reception, or did something fix it?
After flashing CM6.1 I got the notorious wifi connectivity issue that numerous people have been reporting around the web. The issue is the following:
1: Wifi discovers neighbor's AP but no longer home AP.
2: Wifi problem randomly fixes itself, but sometime comes back and home AP can't be found again.
Many random solutions on the web include removing all stored AP's on the phone, resetting the router, rebooting and power cycling the phone numerous times, etc. Most people report that wifi miraculously start working again after the above but there is no consistency to exactly why and what works.
I tried all of the above with no luck, and even flashed three different roms with different kernels, did wipes, formatted everything inculding boot partition etc.
Here is the ACTUAL problem:
Different regions use different wifi channels. North America uses the first 11, most of the world uses 13, and Japan uses all 14. After flashing CM6.1 it changed the regulatory domain on the phone to only scan the first 11 channels meaning my European router broadcasting on 13 wouldn't show up. This setting seems to be persistent and doesn't change just because a new rom is flashed.
The reason people report the problem to be randomly fixed after a few days (and sometimes coming back days later) is because most routers automatically select which channel to broadcast on and therefore might end up within the first 11 at occasion. If it changes to something higher after that however, the problem is back.
Solution:
Open Settings, Wireless & network settings, Wi-Fi settings. Press "Menu" and select Advanced. Press regulatory domain and change to 14 channels.
To learn more about this and understand which channels are used in which countries, look here: http://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4.C2.A0GHz_.28802.11b.2Fg.2Fn.29
Thanks man, even I still met an issue which was wifi disconnect frequently (usually after 12 seconds or less, it's re-scanning AP and trying to re-connect again) when I was trying to share my broadband internet from laptop to my legend.
BUT, after I update my wlan driver (now using 8.0.0.238 for my Atheros AR5XXX), the issue seems gone.
I found that by updating wlan driver to the very latest driver (for mine is 9.2.0.xxx) is not a guarantee to resolve this problem.
Now, by combining your suggestion and an "appropriate" driver version for my wlan, it work flawlessly until now
PS: driver version which will work varies from devices to devices. Do trial and error if you must
edit: well, not 100% gone, but much better . the connection is far more stable
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Rapier said:
My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause
Click to expand...
Click to collapse
I think you're right. Yesterday, I tried my friend's phone (which has a stock ROM), using the same AP and there was no dropped signal or disconnected in wifi. I also tried using other android phone brand (5 series from samsung) which also has a stock ROM and there was no problem at all. Drivers is the culprit
Work
Thanks u very much.worked on my milestone
Thanks. Actually worked.
Rapier said:
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Click to expand...
Click to collapse
Hello Rapier,
I have installed the CyanogenMod 6.1.1 (stable) on my HTC Desire (GSM / France) with latest radio image (32.49.00.32U_5.11.05.27) and taken some time to configure it. Now, everything seems to run well ... excepted the WiFi (and perhaps also the GSM). My problem is exactlw what you have described:
- on stock ROMs, the WiFi signal is stable and quite strong
- on Cyanogen ROM 6.1.1, the WiFi signal fluctuates, the connection is unstable and gets lost.
I like CyanogenMod ROMs very much. The WiFi issue is the only thing that I was not able to correct. You were speaking about WiFi drivers: would it be possible to extract the WiFi drivers from the latest HTC Desire stock ROM and copy them into the CyanogenMod installation?
My impression is that the CyanogenROM is scanning for networks in the background, even if a stable and strong WiFi network has been found and is currently connected. Perhaps there is a possibility to disable this scanning?
To finish, I have also the impression (I know, this is not very scientific ... but perhaps it could help to determinate where the issue comes from) that the GSM network is also fluctuating. I use WiFi Analyzer (available on the Android market) and when I plot a graph, without moving the phone or even without moving myself, the plot oscillates between -80dBm and -30dBm (I swear that there is nobody playing with the on/off button of my ZyXEL router ).
@sz1a: Thank you very much for your post: this helped me to discover these "hidden" settings, but my configuration is manual on the ZyXEL and everything was fine. Perhaps you should switch the thread to "unsolved".
I'n not a developer, only an ethusiast with a Legend. Also I'm not a Linux expert so I can only guess and experiment...threfore I cannot tell if porting HTC proprietary drivers is possible. I'd say not...if it was, we would have it by now. The main reason I think, is that those drivers are not open source, so nobody can port them since the sources are not available. I'm sure that if it was possible, they'll have been included in CM
Sent from my Legend using XDA App
pleaaaase help, im running CM 6.1 RC 1
wifi was working fine untill yesterday, i tried to connect to my friends router but couldnt.. i tried putting it in manually too.. then i couldnt connect to any router infact my phone wont even pick up any even my home one.. i tried switching to 14 channs like this said but no luck
any help please
Hello,
If you don't want the boring details of how I discovered the problem feel free to skip the next couple of paragraphs and go straight to the technical details.
I got my first Android phone (Motorola Defy) a couple of weeks ago and at first I was only using it with wifi because my data plan wasn't activated yet. While playing with it a little I realised that I saw a lot less ads than my boyfriend on his 6 month old Defy. I thougt it was weird but, well, seeing less ads is not a big problem.
Then when I got my data plan I saw that when I wasn't home I saw a lot more ads, so I began to suspect it had to do with how my phone was connected to the internet : wifi or 3G.
Next I wanted to try out Astrid and when I tried to log in using my Google account it failed repeatedly. Until I disabled wifi and it logged in fine using 3G.
Then I installed RTÉ DocOnOne to listen to documentaries while falling asleep. When wifi is enabled, it cannot start up because it can't connect (network timeout). Over 3G, no problem.
At first I thought it was my router blocking ports or something but it happens with different wifi APs and more importantly my boyfriend's phone, connected to the same access point, loads everything without a problem.
Let's sum up:
Some apps can't access the network using wifi but work fine when using 3G.
It happens regardless of the wifi AP (tried 4 different ones with different routers) and another phone using the same app connected to the same wifi AP can access the network just fine.
If I initiate the connection using 3G then switch to wifi (typically I launch the app with 3G, switch wifi on without closing the app), it still works after that (RTE DocOnOne has no pb streaming the documentaries once it has launched)
My phone is a Motorola Defy, French retail ROM, not rooted, no motoblur account (skipped the configuration), Froyo 2.2.2 (already on the phone when I got it), system version (if that means anything to you) Version.34.164.3.MB525.Retail.en.FR, kernel 2.6.32.9-g050ccf2, build 3.4.2-164
I can't give as much details about my boyfriend's phone (that doesn't have the problem) because he's not here right now but I can tell you that it is a Motorola Defy too, French retail (I think) ROM, Froyo updated from preinstalled Eclair (using the official Motorola update), not rooted, with a motoblur account
I have no idea if that's relevant or not, but my phone has the "google maps 5.7.0 crashes on Defy" issue (18446 in the android issue tracker) and my boyfriend's phone hasn't.
Has anyone encountered this issue before ? I couldn't find anything on this forum or with a google search.
Is there any tool I can use to try and find the cause of the problem ?
Thank you for reading all this, sorry if my message was long but I wanted to give as much detail as possible to help the nice people who may find what is wrong with my phone
I didn't read all..
but if your phone don't have problems then check this:
1. go to settings
2. Select "Location & security settings"
3. enable this "Use wireless networks" Location determined by WiFi and/or mobile networks
4. test does it work...
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Anne-Laure said:
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Click to expand...
Click to collapse
Hello, did you solve the issue?
Anyone having issues connecting to wi-fi networks on channels 12/13? On my device I'm unable to see SSIDs in these channels most of the time. Sometimes I can see networks in channel 13.
Am engaging with Google tech support, so will keep you posted.
What country are you in?
UK
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
TheReverend210 said:
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
Click to expand...
Click to collapse
Good good.
I'm wondering whether it's down to me not activating the SIM in the phone as yet? Like a double check that the phone should be allowed to use 12&13 (rather than just selecting English UK as the language).
TheReverend210 said:
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
Click to expand...
Click to collapse
There's really no difference in using that over channel 11 in your case with the co-channel interference.
YES!
It's not just me then. Home router (2.4Ghz) is on ch.13 and when i return home the device will not auto-connect until i toggle wifi off and back on again. Wifi works fine until i leave again. connects fine to my wifi network at work but that is different channel and on 5Ghz too.
RMA'd my device and the new one was bad. Wouldn't see my network at all, but wouldn't register my Sim card either so I have just returned this replacement device. Replacement number 2 is on the way.
I switched to ch.12 and the same thing happens at home. Didn't try any other channels as they are too noisy. So I wonder if this is a software issue? I'm in the UK and the router is made by technicolor for Plusnet.
j3di said:
YES!
It's not just me then. Home router (2.4Ghz) is on ch.13 and when i return home the device will not auto-connect until i toggle wifi off and back on again. Wifi works fine until i leave again. connects fine to my wifi network at work but that is different channel and on 5Ghz too.
RMA'd my device and the new one was bad. Wouldn't see my network at all, but wouldn't register my Sim card either so I have just returned this replacement device. Replacement number 2 is on the way.
I switched to ch.12 and the same thing happens at home. Didn't try any other channels as they are too noisy. So I wonder if this is a software issue? I'm in the UK and the router is made by technicolor for Plusnet.
Click to expand...
Click to collapse
If channel 11 is noisy, then so is 12 and 13.
Sent from my Nexus 6P using Tapatalk
TheReverend210 said:
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
Click to expand...
Click to collapse
You might want to change to channel 11. With the current setup you are not only killing your own data rates, but also the rates of everyone on channel 11. These channels are not supposed to overlap, because that creates interference. Switch to channel 11.
This is my WiFi situation. I'm normally on CH.13, but switched to 12 as a test.
My 2nd unit arrived last week, and unfortunately it's the same issue as before - no channels 12 or 13, not even visible. I'll be back in touch with Google today.
Hopefully this is a software issue rather than Google/Huawei spec'ing a duff wifi chipset.
Google spoken to and basically it's a case of tough-titty - some devices aren't going to work with channels 12 & 13.
For anyone else reading this, I had this problem and 'solved' it.
If you find that you can't see channels 12 and 13 then it's almost definitely caused by the Wifi country code restrictions.
I got my Nexus 6P here in Korea and initially tried it out with no sim card. Even though the location is set in settings, without a sim card it doesn't get the wifi country code set, and I couldn't see those channels. As soon as I inserted a Korean sim card, I was able to see them.
If you are in the UK or elsewhere, using a local sim card and you can't see those channels then chances are either your country doesn't allow it or the code is already set. Either way, your options are just accept it or try one of the 'not officially supported' ways to getting around it. That's likely why Google said you were out of luck. It's possible but involves rooting etc. I think. Just search for 'change wifi country code android'. Good luck.
throwawaynexus said:
For anyone else reading this, I had this problem and 'solved' it.
If you find that you can't see channels 12 and 13 then it's almost definitely caused by the Wifi country code restrictions.
I got my Nexus 6P here in Korea and initially tried it out with no sim card. Even though the location is set in settings, without a sim card it doesn't get the wifi country code set, and I couldn't see those channels. As soon as I inserted a Korean sim card, I was able to see them.
If you are in the UK or elsewhere, using a local sim card and you can't see those channels then chances are either your country doesn't allow it or the code is already set. Either way, your options are just accept it or try one of the 'not officially supported' ways to getting around it. That's likely why Google said you were out of luck. It's possible but involves rooting etc. I think. Just search for 'change wifi country code android'. Good luck.
Click to expand...
Click to collapse
I am afraid that the issue is not as simple. I also have problems with channels 12 and 13, however my phone can connect to those channels, but only for a while. I quote the report I filed in the AOSP bug tracker (not yet assigned, though):
Before I continue, I am based in Switzerland, use a Swiss mobile provider (Swisscom), and I bought my phone through Google in Switzerland. This is relevant because in Europe 802.11b/g/n channels 12 & 13 are allowed, while in the North America they are allowed only under "low power conditions" with the effect that, AFAIK, many devices simply do not support them. My Nexus 6P however should (and shall) support those two channels.
Now, the problem.
I have two access points at home, both in the 2.4 GHz band: one on channels 4+6 and the other (normally) on channels 12+13. What I noticed is that my Nexus 6P would initially connect to the strongest signal independently from the channel, as expected, but then after a while (a couple of hours, maybe) would just stop seeing the signal on channels 12 & 13. Not just my own WLAN, but also neighborhood WLANs on the same channels. This means that the phone can be sitting a couple of meters from the AP in my office (channels 12+13) and be connected to the AP at the opposite corner of the building (the one on channels 4+6). I checked with "WiFi Analyzer" and the phone really does not see any signal above channel 11.
Disabling and re-enabling WiFi will make the phone see channels 12 & 13 once again. However after a while the problem appears again.
At home this is just an inconvenience: I moved the frequency of the second AP to a different channel and that "solved" the problem. On the other hand this might be a much more serious problem when I am in an environment where I can't change the WiFi settings. Maybe I want to connect to a public hotspot broadcasting on the "wrong" channels or I am at the office in an area covered by APs on channels 12 & 13. Tough luck.
Incidentally, I saw at least one report of someone who had exactly the same issue: he had to disable WiFi and enable it again to get the phone to connect to his WLAN (on channel 12 or 13, I can't remember). I also have to say that in our household we have a few other Android devices (2 x Nexus 7, 1 x Nexus 9, 2 x Nexus 4, 1 x Moto X Play) running either 6.0.1 or 5.1.1 and a few other devices (iPhone 5S, iPhone 6, laptop, 2 x Kindle) and none exhibits this behavior. It seems to be specific to the 6P.
I suspect that after a while the WiFi driver simply reverts to its default regulatory domain ("US", I assume) and stops listening to channels 12 and 13. Why it might do so is anyone's guess. Maybe doze interferes with the driver.
Same problem here. The only way to reconnect to WiFi channel 12 or 13 is to manually switch WiFi off and on again on the 6p.
I'm in Hungary.
Guys, there is a thread in the Nexus Help Forum and I reported the issue in the AOSP Bug Tracker. Add your contributions to those threads and star them. Let's try to bring this to Google's attention, otherwise we will never get any action on this topic.
Edit: For some reason I can't add links to the post. Please search issue 197106 ("WiFi 2.4 GHz channels 12 & 13 not working properly on Nexus 6P running 6.0.1") in the AOSP Bug Tracker and the post "My Nexus 6P can't connect to Channel 12 or 13 WIFI's" in the Google Product Forums.
Roberto
I have been trying for a week to extract some information from Google and Huawei, but I must say that their support just doesn't know anything about this issue. It's even difficult to get someone to understand what the problem is: one Google support guy thought I was talkng about LTE channel 12, for example. Huawei support started talking about options in the WiFi settings that are not there, then they wanted to guide me through adding a new WLAN, and finally started clutching at straws, giving more and more fantastic explanations of why it might be so.
Bottom line is: nobody I talked to ever heard about this issue.
I would really like to understand if it could be a hardware issue (which I honestly doubt) because my RMA window is closing soon and I don't honestly know what to do: apart from this WiFi issue my 6P is absolutely flawless and I do not want to risk getting a new telephone only to find out that WiFi still does not work as expected and it's also got other issues. (And, yes, something like this already happened to me.)
robertototaro said:
I have been trying for a week to extract some information from Google and Huawei, but I must say that their support just doesn't know anything about this issue. It's even difficult to get someone to understand what the problem is: one Google support guy thought I was talkng about LTE channel 12, for example. Huawei support started talking about options in the WiFi settings that are not there, then they wanted to guide me through adding a new WLAN, and finally started clutching at straws, giving more and more fantastic explanations of why it might be so.
Bottom line is: nobody I talked to ever heard about this issue.
I would really like to understand if it could be a hardware issue (which I honestly doubt) because my RMA window is closing soon and I don't honestly know what to do: apart from this WiFi issue my 6P is absolutely flawless and I do not want to risk getting a new telephone only to find out that WiFi still does not work as expected and it's also got other issues. (And, yes, something like this already happened to me.)
Click to expand...
Click to collapse
Hello, I also have the same problem. As I can report it to Google? I have not found a way.
gmarti said:
Hello, I also have the same problem. As I can report it to Google? I have not found a way.
Click to expand...
Click to collapse
Did you call the Google Store Support? I hope that if they hear the same reports repeatedly they will take notice.
If your telephone is unlocked (and if you are on XDA chances are it is), flash Franco's kernel. I did it today and now my problems with WiFi are gone. Plus Franco's is known to be very battery efficient. It's a win-win situation.