WAI
Status Update
No update yet.
Comments
il...@google.com
I have the same issue. If I come back home with WiFi on the pgonencan detect my network but won't connect.disabling and re enabling WiFi fixes the issue.
ph...@bayfmail.com
This is reported in many fora as the biggest nexus 5 problem. I suggest raising the priority
il...@google.com
I have the same problem
It seems that a connection to wifi is only possible when there is no LTE/3G connection. either after reboot before entering pin or in flight mode
successful connect after reboot:
I/wpa_supplicant( 856): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
I/wpa_supplicant( 856): wlan0: Associated with xx:xx:xx:xx:xx:xx
I/wpa_supplicant( 856): wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP]
I/wpa_supplicant( 856): wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed (auth) [id=12 id_str=]
unsuccessful attempt:
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-REENABLED id=12 ssid="xxx"
I/wpa_supplicant( 847): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
D/CommandListener( 177): Clearing all IP addresses on wlan0
I/wpa_supplicant( 847): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=12 ssid="xxx" auth_failures=1 duration=10
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
E/wpa_supplicant( 847): current_ssid == NULL
It seems that a connection to wifi is only possible when there is no LTE/3G connection. either after reboot before entering pin or in flight mode
successful connect after reboot:
I/wpa_supplicant( 856): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
I/wpa_supplicant( 856): wlan0: Associated with xx:xx:xx:xx:xx:xx
I/wpa_supplicant( 856): wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP]
I/wpa_supplicant( 856): wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed (auth) [id=12 id_str=]
unsuccessful attempt:
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-REENABLED id=12 ssid="xxx"
I/wpa_supplicant( 847): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
D/CommandListener( 177): Clearing all IP addresses on wlan0
I/wpa_supplicant( 847): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=12 ssid="xxx" auth_failures=1 duration=10
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
E/wpa_supplicant( 847): current_ssid == NULL
ku...@google.com
Sale issue here.
When i go home from a 3g connection, i cant access WiFi automatically. I put Nexus 5 plane mode, i quit plane mode, and i entre Ok in my WiFi network.
When i go home from a 3g connection, i cant access WiFi automatically. I put Nexus 5 plane mode, i quit plane mode, and i entre Ok in my WiFi network.
pe...@gmail.com
I am also having this issue
[Deleted User] <[Deleted User]>
Same issue here. With LTE on I cannot connect to WiFi.
il...@google.com
[Comment deleted]
[Deleted User] <[Deleted User]>
Note that comments are for discussing the bug. A "me too" can be signified by starring the bug.
il...@google.com
Thanks for opening a specific thread on this issue for Nexus 5/4.4 and posting logcat data, etc.
When experiencing this problem the phone will seemingly still have detected that the network is in range. Then, when trying to manually re-connect, the UI reports it's attempting to connect, the signal indicator drops to 1 bar, and after a few seconds it gives up, and the network continues to be listed as in-range. As stated, resetting WiFi connection fixes the problem immediately.
I started seeing this problem upon setting-up a new Nexus 5 (no root, noting fancy). I tired a number of things discussed in other forums regarding this issue under v4.3 (remove and re-add Google account, toggle various wifi settings, etc.) to no avail. I tried a factory rest a couple times as well without luck.
However, on one of my factory resets I chose NOT to let setup automatically restore my apps/settings, thinking I'd just do that manually to rule-out any issues with a specific app. Since then I've re-installed all my apps one-by-one, and have yet to see this problem re-surface. I'm wondering if it might be related to the auto-restore process grabbing some wifi settings data (specific to the NIC or to individual saved networks) from my old phone that are somehow incompatible/conflicting with the Nexus 5/4.4.
When experiencing this problem the phone will seemingly still have detected that the network is in range. Then, when trying to manually re-connect, the UI reports it's attempting to connect, the signal indicator drops to 1 bar, and after a few seconds it gives up, and the network continues to be listed as in-range. As stated, resetting WiFi connection fixes the problem immediately.
I started seeing this problem upon setting-up a new Nexus 5 (no root, noting fancy). I tired a number of things discussed in other forums regarding this issue under v4.3 (remove and re-add Google account, toggle various wifi settings, etc.) to no avail. I tried a factory rest a couple times as well without luck.
However, on one of my factory resets I chose NOT to let setup automatically restore my apps/settings, thinking I'd just do that manually to rule-out any issues with a specific app. Since then I've re-installed all my apps one-by-one, and have yet to see this problem re-surface. I'm wondering if it might be related to the auto-restore process grabbing some wifi settings data (specific to the NIC or to individual saved networks) from my old phone that are somehow incompatible/conflicting with the Nexus 5/4.4.
Description
Version used: 1.0.0-alpha01
Devices/Android versions reproduced on:
An activity has a NavHostFragment and a BottomNavigationView. Then, I call `setupActionBarWithNavController(navController)` and `bottomNavView.setupWithNavController(navController)` and when I switch away from the home fragment, it applies a back button on the Toolbar, but it shouldn't because I just switch the section. It changes the title properly. Additionally, if I navigate away from the home fragment and hit back button, it goes back to home fragment, but according to the guidelines for BottomNavigationView, it should close the screen, rather then first getting back to home (require 2 clicks to exit).
As I have checked the code, I found it has a check only against DrawerLayout, but not against BottomNavigationView:
androidx.navigation.ui.NavigationUI:
@Override
public void onNavigated(@NonNull NavController controller,
@NonNull NavDestination destination) {
ActionBar actionBar = mActivity.getSupportActionBar();
CharSequence title = destination.getLabel();
if (!TextUtils.isEmpty(title)) {
actionBar.setTitle(title);
}
boolean isStartDestination =
controller.getGraph().getStartDestination() == destination.getId();
actionBar.setDisplayHomeAsUpEnabled(mDrawerLayout != null || !isStartDestination);
setActionBarUpIndicator(mDrawerLayout != null && isStartDestination);
}
Check the screenshots: