values-v23.xml file shows error : "Error:(2) Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Inverse'." [37057298]

WAI

Bug

Migrated-Tools-Studio

Status Update

No update yet.

Description

ak...@gmail.com

created issue #1

Aug 18, 2015 01:20PM

I am developing with SDK 19, but got below error and in MainActivity.java show "R" as error.

/Users/aravind/AndroidStudioProjects/Email01/app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/23.0.0/res/values-v23/values-v23.xml
Error:(2) Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Inverse'.
Error:(2) Error retrieving parent for item: No resource found that matches the given name 'android:Widget.Material.Button.Colored'.
Error:Execution failed for task ':app:processDebugResources'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Users/aravind/android/Android-SDK/sdk/build-tools/22.0.1/aapt'' finished with non-zero exit value 1

Comments

ch...@google.com <ch...@google.com> #2Aug 18, 2015 02:03PM

Status: Won't Fix (Intended Behavior)

Chrome Diagnostics Report of following results:

The DNS diagnostic test in Chrome Diagnostics Report is known to have some issues in some configuration. Internal bug id is b/353448388. This problem is fixed starting from m130.

Here the diagnostic failure could indicate a real problem. Jason, Jie, what m126 bugs could this report be a duplicate of ?

ri...@gmail.com <ri...@gmail.com> #3Aug 18, 2015 02:28PM

what m126 bugs could this report be a duplicate of ?

Not anything off the top of my head now (maybe Jason knows other). Since the device is not enterprise-enrolled according to the information in #1, I assume it should not hit the diagnostic DNS issue in b/353448388.

But I assume the reporter also encountered the issue of "no connection to gateway" in the diagnostic app, which is partially fixed on M128 in b/277696397 (internal link). Before M128, the diagnostic app will wrongly report gateway connection issue if there is IPv6 on the network, while on M128+ this issue will only happen on IPv6-only (no IPv4) networks.

Re #1,

Thanks for reporting the issue and sorry for the late reply here. A few questions to help us understanding the issue bettter:

Are you still experiencing this issue? If so, could you file a feedback report (alt-shift-i, and put "b/360530624" in the textbox so that we can search for it easily) when you are seeing it again?
Does it only happen on a certain WiFi network? If it's the case, do you by chance have other devices (not Chromebook) to see if they work on the same network?

Thanks!

ba...@gmail.com <ba...@gmail.com> #4Aug 18, 2015 07:15PM

This might be a dup of the internal bug of b/344462428 (may show up as unreliable WiFi, b/347596358). This issue is fixed from platform version 15886.77.0 (M126).

As Jie mentioned, if this is still reproducible, a feedback report would help debug the issue further. Thank you!

le...@gmail.com <le...@gmail.com> #5Aug 18, 2015 09:07PM

rainy@littlebearcoffee.com, would you be able to try to reproduce this issue on a more recent ChromeOS release and provide a feedback report (shift + alt + i) if you can ? Thanks

am...@gmail.com <am...@gmail.com> #6Aug 18, 2015 11:17PM

Bugjuggler: wait 8w -> hugobenichi

Screenshot from 2015-08-19 02:07:57.png

185 KB

View

Download

sc...@gmail.com <sc...@gmail.com> #7Aug 19, 2015 12:43AM

Hi. I've received your bug and will wait until 2024-12-04 16:58 +0900 JST and then assign the bug to hugobenichi.

ka...@gmail.com <ka...@gmail.com> #8Aug 19, 2015 04:11AM

Thanks for getting back to me on the issue. In response to

comment #3

:
It is still happening, so I will report the next instance with the requested text. It doesn't happen on a specific network, but all networks I am connecting to. It's not repeatable on other non ChromeOS devices in at least two of those, but is repeatable on the exact same device of another owner. I can ask them to also report with the reference number if that is helpful. Let me know if I can provide any additional information or troubleshooting.

I am out of the office for a few days this weekend, but should be able to repeat issue by eod Monday.

ak...@gmail.com <ak...@gmail.com> #9Aug 19, 2015 08:42AM

Wanted to update that I have sent several feedback reports with the issue #. It didn't seem to be happening for a few days and today it is back to happening at least every few hours (have changed location/wifi 3 times) If I should continue to provide feedback reports, let me know, otherwise I will just keep an eye on updates to this thread.

zu...@gmail.com <zu...@gmail.com> #10Aug 19, 2015 10:39AM

I looked at 2 reports, in both case we see that the WiFi network service state is eventually changed to "failure".

Rerouting to WiFi component to take an initial look if this is a WiFi issue.

pv...@gmail.com <pv...@gmail.com> #11Aug 19, 2015 11:29AM

The 3 feedback reports:

ve...@gmail.com <ve...@gmail.com> #12Aug 19, 2015 02:09PM

The client device disconnected from wifi_psk_6 due to "no remaining endpoints", and disconnected from wifi_psk_8 due to reconnect timeout. The connection to wifi_psk_36 was unstable, link monitor failure occurred and PREV_AUTH_NOT_VALID error observed during reconnection.

my...@googlemail.com <my...@googlemail.com> #13Aug 19, 2015 02:10PM

<tirage> Kevin to take a look, figure out if it is L2 or L3 issue.

bo...@gmail.com <bo...@gmail.com> #14Aug 19, 2015 02:25PM

I am not sure if I can jump on this one, but I would like to add a log from our HP G9 MK EE editions that seem to have DNS check issues. We will be using the Chromebook and all of the sudden it disconnects from WIFI and then sometimes fails to reconnect other times reconnects fine. In this it starts at 2024-11-01T16:27:01.538619Z in the log. Suddenly DNS checks start failing and the CB is disconnected. This happens on all of our G9's randomly.

There are no issues seen on the firewall or with any other models of Chromebook at this same time. I also notice that instead of do53 query to DNS 9.9.9.9 its says Do53 query to (IPv4: 1) and (IPv4: 2) and fails.

Hope this is maybe related. Otherwise I can file my own report.

my...@googlemail.com <my...@googlemail.com> #15Aug 19, 2015 04:55PM

Adding one more attachment that shows a similar issue at 2024-10-30T17:52:08.595534Z in the net.log file

vc...@gmail.com <vc...@gmail.com> #16Aug 19, 2015 07:37PM

deleted

AS_Fail.png

116 KB

View

Download

mo...@gmail.com <mo...@gmail.com> #17Aug 20, 2015 05:03AM

I do not believe that this is an L2 layer issue. Indeed we see the Wi-Fi state reach "Failure" in all three feedback reports, but I believe that all three are explained by intended behavior. In https://listnr.corp.google.com/report/92062230053 the failure is shortly preceded by an indication of significant RSSI drop. (Internal-only link to sample log). This looks like the user walked away from their access point and lost connection.

In the other two reports, we see a pattern where the device suspends, resumes, then fails to reconnect to the AP is was connected to prior to the resume. This could be explained by the user closing their device, traveling out of range of their AP, then re-opening their device. (Internal-only link to sample log).

So, I believe the Wi-Fi failures are reflective of expected device behavior in response to user activity. I do believe there is some indication of L3 layer issues though. For example in http://listnr/product/208/report/92051793504 where we see repeated dnsproxyd errors while we are in the "online" state. (Internal-only link to sample log).

Handing this back to the networking team to take a look.

ASDK.png

200 KB

View

Download

av...@gmail.com <av...@gmail.com> #18Aug 22, 2015 04:56PM

I do believe there is some indication of L3 layer issues though. For example in http://listnr/product/208/report/92051793504 where we see repeated dnsproxyd errors while we are in the "online" state.

As discussed many times internally, dns failures happen both because of link issues and L3 issues and therefore dns failures can't be used to rule out link issues. Actually dns health checks and dns queries are the first thing expected to fail when the link fails as a packet transport.

je...@gmail.com <je...@gmail.com> #19Aug 22, 2015 05:23PM

Added clarification from this user in response to #17: The device stays open, and unmoved during these occurrences. In most instances the device is in the same room as the access point. After sending the feedback reports, I typically restart the computer which will usually grant me access to the network for at least a little while. Hope that helps in clarifying conditions, feel free to ask for more information as needed.

la...@gmail.com <la...@gmail.com> #20Aug 25, 2015 02:14AM

Thanks all for the investigation and #19 for providing more information.

I took a quick pass at the 3 reports in #11, the DNS failures always came together with the NUD_FAILED logs, which means that the gateway was not reachable on L2. This usually means something went wrong on the network side (i.e., due to some reason the device did not get the ARP responses), but the weird thing is that, if I read the logs correctly, these 3 feedback reports are from 3 different networks, and the NUD_FAILED is shown on all the 3 networks...

Questions to the user:

Were you using the device at the same physical location to connect to these networks? (just want to rule out some random effect from the physical environment...)
If it's possible, could you try connecting the device to the same router(s) with Ethernet cable to see if it works? (this could help us understand if the issue is at the network layer or the wifi layer).

Questions to the wifi team:

In this case, will it be helpful to do some OTA packet capture?

Thanks!

la...@gmail.com <la...@gmail.com> #21Aug 25, 2015 09:04AM

Re #20 If I remember correctly 1 report was from my work connection, but I believe I submitted the other two in the same day on my home connection. I can connect by Ethernet cable later this evening to test at home. I can't promise conclusive results from just one session though, as the issue really doesn't seem to follow any kind of pattern of when it does and doesn't work... I can do this over the span of the rest of this week though if you think that would be more helpful. Do you want me to submit feedback reports while I am connected? Or only if the issue arises?

Thanks for all of y'all's help!

av...@gmail.com <av...@gmail.com> #22Aug 25, 2015 09:48AM

Re #21,

Do you want me to submit feedback reports while I am connected? Or only if the issue arises?

Only if the issue arises is fine. Thanks!

Re #14 and #15,

Sorry for the late reply -- I checked the two logs and they showed the same pattern -- there were a lot of NUD_FAILED in the logs. Not sure if the root cause is the same with #1 . Would you mind also filing a feedback report (alt-shift-i, and put "b/360530624" in the textbox so that we can search for it easily) when you are seeing it again (same instruction as in #3)? Thanks.

cr...@gmail.com <cr...@gmail.com> #23Aug 28, 2015 12:37AM

You may not know the answer to this, but usually I gather logs
remotely through the admin console when I notice the behaviour through our
Meraki wifi system. It has these couple options I can select when
collecting logs. Can I do it this way? or another way remotely. Hopefully
this picture comes through.

[image: image.png]

On Tue, Nov 5, 2024 at 8:43 PM <buganizer-system@google.com> wrote:

- Show quoted text -

--
Erik Jeffery
Brown Deer School District

--

Confidentiality Notice: This e-mail message, including any
attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies
of
the original message.

dr...@gmail.com <dr...@gmail.com> #24Aug 29, 2015 02:35PM

Also, we are moving our HP MK G9 EE editions up to 130 from 129 and monitoring there. It is looking like maybe 130 fixes the issue for the majority of the time with some instances still happening at random times, but I don't want to speak to soon.

Would you like me to only gather logs on devices already updated to 130 that have this issue or do you want logs from 129 devices as well?

mm...@gmail.com <mm...@gmail.com> #25Sep 1, 2015 01:04PM

Hello

I think this issue seems to be mostly taken care of with 130, but still seems to occur sporadically.

All of our clients are remote, so the best I can do is collect system logs through the admin console.

Here is a netlog.txt from a OS130 client that has this issue occur at 2024-11-12R13:44:49. Also, you can see this issue occurring for a much longer duration at timestamp - 2024-11-1120:37:50 There is no indication on the firewall that this client had any issues through us.

I have the entire support bundle if uploading that would provide more information.

Please let me know what I can do to help.

kr...@gmail.com <kr...@gmail.com> #26Sep 2, 2015 05:01PM

Re #23 ~ #25:

Thanks for the additional information (and sorry for the late reply).

Hopefully this picture comes through.

Unfortunately we can only see a [image: image.png] :)

I'll defer to Kevin to check if there are any other logs we can collect for better debugging. (Logs in #25 still shows the NUD_FAILED issue)

lb...@gmail.com <lb...@gmail.com> #27Sep 3, 2015 06:47AM

I am going to add these logs as well to see if they are any help. I do not see in these logs the same DNS issue, but this user has the same HP Chromebook 11MK G9 EE and experienced the disconnect issues at around 2024-11-12 18:44 or so. Hope these logs will show something interesting.

The computer was restarted at around 18:47 and you can see it connect right away.

Also, if you would rather have me create my own issue I can.

he...@gmail.com <he...@gmail.com> #28Sep 5, 2015 05:33PM

Hey,

I am going to upload one more netlog. This user is on Chrome OS 130 and is experiencing the issue multiple times of the day in multiple classrooms. It can be seen at timestamp 2024-11-18T17:40:58.026051Z

I have a log packet from the computer - Google Admin Console if needed/

Thanks

he...@gmail.com <he...@gmail.com> #29Sep 7, 2015 05:31PM

Thank you for all of the logs, this is very helpful in working towards a diagnosis. Here's what I've got so far:

We see a repeated pattern of failed authentication attempts in all of your recent log submissions. We attempt to authenticate, and a couple seconds later the attempt times out, seemingly without any response from the AP:

2024-11-12T18:43:53.297881Z DEBUG wpa_supplicant[784]: nl80211: Authentication request send successfully
2024-11-12T18:43:53.298209Z DEBUG wpa_supplicant[784]: nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
2024-11-12T18:43:53.298233Z DEBUG wpa_supplicant[784]: nl80211: New station ea:9e:38:7f:e0:10
2024-11-12T18:43:53.311360Z INFO shill[1162]: INFO shill: [wifi.cc(2659)] WiFi wlan0 StateChanged inactive -> authenticating
2024-11-12T18:43:53.333510Z INFO patchpaneld[1974]: INFO patchpaneld: [shill_client.cc(262)] Service /service/1 was not connected
2024-11-12T18:43:53.338577Z INFO patchpaneld[1974]: INFO patchpaneld: [shill_client.cc(262)] Service /service/1 was not connected
2024-11-12T18:43:56.017781Z DEBUG wpa_supplicant[784]: nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
2024-11-12T18:43:56.017823Z DEBUG wpa_supplicant[784]: nl80211: Delete station ea:9e:38:7f:e0:10
2024-11-12T18:43:58.299255Z DEBUG wpa_supplicant[784]: wlan0: SME: Authentication timeout

One possibility is that the auth request was malformed in some way such that the AP didn't recognize it. Perhaps the device tried do authenticate using an unsupported method. Looking at the authentication request details, nothing stands out as erroneous. Another possibility is that the AP did send an authentication response, but that was somehow ignored by the device.

2024-11-19T14:02:00.401322Z DEBUG wpa_supplicant[800]: wlan0: Starting radio work 'sme-connect'@0x580617abf0 after 0.040791 second wait
2024-11-19T14:02:00.401402Z DEBUG wpa_supplicant[800]: wlan0: WPA: clearing own WPA/RSN IE
2024-11-19T14:02:00.401423Z DEBUG wpa_supplicant[800]: wlan0: RSN: clearing own RSNXE
2024-11-19T14:02:00.401481Z DEBUG wpa_supplicant[800]: wlan0: Automatic auth_alg selection: 0x1
2024-11-19T14:02:00.401510Z DEBUG wpa_supplicant[800]: wlan0: SAE enabled, but target BSS does not advertise SAE AKM for RSN
2024-11-19T14:02:00.401533Z DEBUG wpa_supplicant[800]: RSN: PMKSA cache search - network_ctx=0x5806180fb0 try_opportunistic=0 akmp=0x0
2024-11-19T14:02:00.401548Z DEBUG wpa_supplicant[800]: RSN: Search for BSSID (MAC OUI=ea:9e:38 IFACE=8)
2024-11-19T14:02:00.401563Z DEBUG wpa_supplicant[800]: RSN: No PMKSA cache entry found
2024-11-19T14:02:00.401583Z DEBUG wpa_supplicant[800]: wlan0: RSN: using IEEE 802.11i/D9.0
2024-11-19T14:02:00.401604Z DEBUG wpa_supplicant[800]: wlan0: WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2 proto 2
2024-11-19T14:02:00.401622Z DEBUG wpa_supplicant[800]: wlan0: WPA: Selected mgmt group cipher 32
2024-11-19T14:02:00.401642Z DEBUG wpa_supplicant[800]: wlan0: WPA: clearing AP WPA IE
2024-11-19T14:02:00.401670Z DEBUG wpa_supplicant[800]: WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
2024-11-19T14:02:00.401687Z DEBUG wpa_supplicant[800]: wlan0: WPA: clearing AP RSNXE
2024-11-19T14:02:00.401707Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP group 0x10 network profile group 0x358 driver supported ciphers 0x381e; available group 0x10
2024-11-19T14:02:00.401726Z DEBUG wpa_supplicant[800]: wlan0: WPA: using GTK CCMP
2024-11-19T14:02:00.401747Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP pairwise 0x10 network profile pairwise 0x358 driver supported ciphers 0x381e; available pairwise 0x10
2024-11-19T14:02:00.401766Z DEBUG wpa_supplicant[800]: wlan0: WPA: using PTK CCMP
2024-11-19T14:02:00.401786Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP key_mgmt 0x2 network profile key_mgmt 0xc000d42; available key_mgmt 0x2
2024-11-19T14:02:00.401804Z DEBUG wpa_supplicant[800]: wlan0: WPA: using KEY_MGMT WPA-PSK
2024-11-19T14:02:00.401825Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP mgmt_group_cipher 0x20 network profile mgmt_group_cipher 0x0; available mgmt_group_cipher 0x0
2024-11-19T14:02:00.401844Z DEBUG wpa_supplicant[800]: wlan0: WPA: not using MGMT group cipher
2024-11-19T14:02:00.401874Z DEBUG wpa_supplicant[800]: WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 8c 00
2024-11-19T14:02:00.401889Z DEBUG wpa_supplicant[800]: RSN: Set own RSNXE default - hexdump(len=0):
2024-11-19T14:02:00.401903Z DEBUG wpa_supplicant[800]: WPA: Set PMK based on external data - hexdump(len=32): [REMOVED]
2024-11-19T14:02:00.401951Z DEBUG wpa_supplicant[800]: RRM: Determining whether RRM can be used - device support: 0x30
2024-11-19T14:02:00.401966Z DEBUG wpa_supplicant[800]: RRM: Adding RRM IE to Association Request
2024-11-19T14:02:00.402027Z DEBUG wpa_supplicant[800]: Added supported operating classes IE - hexdump(len=24): 3b 16 79 51 53 54 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 00 82 80
2024-11-19T14:02:00.402050Z DEBUG wpa_supplicant[800]: EAPOL: External notification - EAP success=0
2024-11-19T14:02:00.402070Z DEBUG wpa_supplicant[800]: EAPOL: External notification - EAP fail=0
2024-11-19T14:02:00.402084Z DEBUG wpa_supplicant[800]: EAPOL: External notification - portControl=Auto
2024-11-19T14:02:00.402101Z DEBUG wpa_supplicant[800]: wlan0: Cancelling scan request
2024-11-19T14:02:00.402170Z NOTICE wpa_supplicant[800]: SME: Trying to authenticate with (MAC OUI=ea:9e:38 IFACE=8) (SSID='(SSID: 1)' freq=5680 MHz)
2024-11-19T14:02:00.402194Z DEBUG wpa_supplicant[800]: EAPOL: External notification - portValid=0
2024-11-19T14:02:00.402213Z DEBUG wpa_supplicant[800]: wlan0: State: SCANNING -> AUTHENTICATING
2024-11-19T14:02:00.402253Z DEBUG wpa_supplicant[800]: wlan0: Determining shared radio frequencies (max len 2)
2024-11-19T14:02:00.402276Z DEBUG wpa_supplicant[800]: wlan0: Shared frequencies (len=0): completed iteration
2024-11-19T14:02:00.402301Z DEBUG wpa_supplicant[800]: P2P: Add operating class 81
2024-11-19T14:02:00.402321Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=11): 01 02 03 04 05 06 07 08 09 0a 0b
2024-11-19T14:02:00.402335Z DEBUG wpa_supplicant[800]: P2P: Add operating class 115
2024-11-19T14:02:00.402350Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=4): 24 28 2c 30
2024-11-19T14:02:00.402363Z DEBUG wpa_supplicant[800]: P2P: Add operating class 116
2024-11-19T14:02:00.402378Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 24 2c
2024-11-19T14:02:00.402391Z DEBUG wpa_supplicant[800]: P2P: Add operating class 117
2024-11-19T14:02:00.402405Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 28 30
2024-11-19T14:02:00.402420Z DEBUG wpa_supplicant[800]: P2P: Add operating class 124
2024-11-19T14:02:00.402457Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=4): 95 99 9d a1
2024-11-19T14:02:00.402471Z DEBUG wpa_supplicant[800]: P2P: Add operating class 125
2024-11-19T14:02:00.402488Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=5): 95 99 9d a1 a5
2024-11-19T14:02:00.402502Z DEBUG wpa_supplicant[800]: P2P: Add operating class 126
2024-11-19T14:02:00.402516Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 95 9d
2024-11-19T14:02:00.402529Z DEBUG wpa_supplicant[800]: P2P: Add operating class 127
2024-11-19T14:02:00.402544Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 99 a1
2024-11-19T14:02:00.402558Z DEBUG wpa_supplicant[800]: P2P: Add operating class 128
2024-11-19T14:02:00.402584Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=8): 24 28 2c 30 95 99 9d a1
2024-11-19T14:02:00.402611Z DEBUG wpa_supplicant[800]: P2P: Add operating class 130
2024-11-19T14:02:00.402632Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=9): 24 28 2c 30 95 99 9d a1 a5
2024-11-19T14:02:00.402649Z DEBUG wpa_supplicant[800]: P2P: Update channel list
2024-11-19T14:02:00.402697Z DEBUG wpa_supplicant[800]: P2P: channels: 81:1,2,3,4,5,6,7,8,9,10,11 115:36,40,44,48 116:36,44 117:40,48 124:149,153,157,161 125:149,153,157,161,165 126:149,157 127:153,161 128:36,40,44,48,149,153,157,161 130:36,40,44,48,149,153,157,161,165
2024-11-19T14:02:00.402716Z DEBUG wpa_supplicant[800]: P2P: cli_channels:
2024-11-19T14:02:00.402749Z DEBUG wpa_supplicant[800]: nl80211: Authenticate (ifindex=2)
2024-11-19T14:02:00.402844Z DEBUG wpa_supplicant[800]:   * bssid=(MAC OUI=ea:9e:38 IFACE=8)
2024-11-19T14:02:00.402859Z DEBUG wpa_supplicant[800]:   * freq=5680
2024-11-19T14:02:00.402900Z DEBUG wpa_supplicant[800]:   * SSID=649433bbcd6b
2024-11-19T14:02:00.402914Z DEBUG wpa_supplicant[800]:   * IEs - hexdump(len=0): [NULL]
2024-11-19T14:02:00.402927Z DEBUG wpa_supplicant[800]:   * Auth Type 0

Another possibility is that the AP did send an authentication response, but that was somehow ignored by the device. Unfortunately, none of these possibilities are observable in the limited logs that we have. Really, we're going to need additional information to actually make a diagnosis, since there isn't anything conclusive in the device logs.

ejeffery, if you're able to provide some additional diagnostics, it could go a long way to helping understand the behavior. Here are some things that would help me debug, listed in order of usefulness. I understand that you might not be able to complete some or all of these steps, but anything you can provide could be useful.

An OTA packet capture on the AP's operating frequency, showing a reproduction of the event. This is definitely an advanced step that requires additional hardware so no worries if this isn't viable, but it's certainly the most useful option.
Logs from the AP that you're trying to connect to. This could potentially inform me of misalignment between the Chromebook and AP.
A full feedback report from the Chromebook, gathered using Alt-Shift-I immediately after a failure. Feedback reports contain additional logs and information that isn't available in the net logs.

If you're able to complete items 1 or 2, it would still be really helpful if you could provide an accompanying feedback report that lines up with the packet capture or AP logs.

Let me know if you're able to provide any of this additional information. Thanks again for working with us to help diagnose this issue.

Best, Kevin

se...@gmail.com <se...@gmail.com> #30Sep 14, 2015 03:47AM

Hello,

1. I can try to do this. It would be like a monitor mode capture? I can try but most of the time it isn't necessarily happening when I am around. I just hear about it later with the time stamps.

2. One of the problems here is that we use Meraki APs. Don't have a lot in logging capabilities. I can attach some screenshots of dashboards here if you want.

3. Is there any specific logs you need. I usually do not get to see the user in person and must rely on log gathering from the admin console, but I can get a support bundle from there and upload any logs you may need if you want. That is where I got the netlog.txt from.

Thanks very much for helping me with this.

wx...@gmail.com <wx...@gmail.com> #31Sep 16, 2015 02:34AM

In addition I started looking at some of the other logs I have access to from the CB and I am going to uplopad the messages log - in it I see some references to kernel warnings that appear to be releated to the wifi chip - Atheros. You can see an example at timestamp - 2024-11-18T14:33:12.873027Z.

Does this help at all?

sr...@gmail.com <sr...@gmail.com> #32Oct 3, 2015 11:56AM

Sorry for the multiple messages but I am going to attach a log packet that I currently have. These are the basic logs that that get sent into the admin console. I can pull a much more detailed log set on demand that includes the following logs. See Attached Screenshots:

00.PNG

145 KB

View

Download

ro...@gmail.com <ro...@gmail.com> #33Oct 18, 2015 03:37AM

Sorry again. Wanted to mention when I export the logs in the pngs I have these options to export if this helps? See Attachment:

lb...@gmail.com <lb...@gmail.com> #34Oct 18, 2015 05:13AM

Has there been any development on a fix to these issues?

da...@misena.edu.co <da...@misena.edu.co> #35Oct 28, 2015 10:39PM

Hola alguien me puede ayudar con este error no se ya cambie la versión de compilacion

errordmrda.png

180 KB

View

Download

bs...@gmail.com <bs...@gmail.com> #36Dec 8, 2015 09:24AM

Error:Execution failed for task ':app:preDexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\java\jdk1.7.0_79\bin\java.exe'' finished with non-zero exit value 1

after follow #7 it again shows one error.plz anybody help me to clear.

lb...@gmail.com <lb...@gmail.com> #37Dec 8, 2015 09:29AM

Why is this marked as "userError" ?

[Deleted User] <[Deleted User]> #38Dec 8, 2015 04:27PM

@#33 robert.e...@gmail.com
You're a life saver. Tnx! Couldn't get my app working in no way, till I read your comment and updated my other module to v23 as well :s

Then ran into to same issue as #36 bsharmil...@gmail.com
but then adding " multiDexEnabled true" to my defaultConfig allowed me to run the project

cv...@gmail.com <cv...@gmail.com> Dec 29, 2015 06:58AM

Android error.JPG

145 KB

View

Download

jw...@gmail.com <jw...@gmail.com> #39Jan 9, 2016 07:53AM

Tried #7, here's what I'm getting after hitting clean.

Screen Shot 2016-01-09 at 2.52.53 AM.png

132 KB

View

Download

og...@gmail.com <og...@gmail.com> #40Mar 25, 2016 09:24PM

Thanks for

comment #7

.
I need to keep my build for Sdk version 21, so changing to v23 is not possible.
I got the solution after following

comment #7

.
Remove the support library v23 folder, then make a build.
The error shown that Google Play services v8.4.0 requires support library v7:23.
Replace this:
compile 'com.google.android.gms:play-services:+'
With this:
compile 'com.google.android.gms:play-services:8.3.0'
Then clean project, and it works!

The reason is using compile 'com.google.android.gms:play-services:+'
will make Android Studio uses the latest (8.4.0 as of today).
DO NOT DO THIS.

se...@gmail.com <se...@gmail.com> #41May 26, 2016 11:56PM

#41 is what I needed! thanks.

th...@gmail.com <th...@gmail.com> #42Jun 15, 2016 01:03PM

Thanks for

comment #41

.

However, the version of play-services is 9.0.2 today.
And 8.3.0 can not support some libraries recently added to Google, such as Firebase in my case.

I've tried method of

Comment #33

. Problem of either v23 or org.apache.http comes out.

Anyway, this bug still exists.

ka...@gmail.com <ka...@gmail.com> #43Jul 19, 2016 07:20AM

#41 is working! thanks.

sm...@gmail.com <sm...@gmail.com> #44Aug 26, 2016 01:58AM

Funcionoooooooou aeeeee, depois de 2 dias tentando! vlw gente!

sr...@gmail.com <sr...@gmail.com> #45Oct 5, 2016 09:36AM

Hack alternate to #7 & #41
Create a new styles.xml file under v23 folder with the following and you are done!
<resources>

<style name="Base.TextAppearance.AppCompat.Widget.Button.Inverse">

<item name="android:textColor">#000000</item>
</style>

<style name="Base.Widget.AppCompat.Button.Colored">

<item name="android:textColor">#000000</item>
</style>

</resources>

pr...@gmail.com <pr...@gmail.com> #46Oct 13, 2016 05:57PM

#46 great work around. Worked for me.

al...@gmail.com <al...@gmail.com> #47Jan 4, 2017 10:07PM

Greetings! Please help solve the problem!

.jpg

198 KB

View

Download

Issue 37057298

Description

Issue summary

Comments

ch...@google.com <ch...@google.com> #2Aug 18, 2015 02:03PM

ri...@gmail.com <ri...@gmail.com> #3Aug 18, 2015 02:28PM

ba...@gmail.com <ba...@gmail.com> #4Aug 18, 2015 07:15PM

le...@gmail.com <le...@gmail.com> #5Aug 18, 2015 09:07PM

am...@gmail.com <am...@gmail.com> #6Aug 18, 2015 11:17PM

sc...@gmail.com <sc...@gmail.com> #7Aug 19, 2015 12:43AM

ka...@gmail.com <ka...@gmail.com> #8Aug 19, 2015 04:11AM

ak...@gmail.com <ak...@gmail.com> #9Aug 19, 2015 08:42AM

zu...@gmail.com <zu...@gmail.com> #10Aug 19, 2015 10:39AM

pv...@gmail.com <pv...@gmail.com> #11Aug 19, 2015 11:29AM

ve...@gmail.com <ve...@gmail.com> #12Aug 19, 2015 02:09PM

my...@googlemail.com <my...@googlemail.com> #13Aug 19, 2015 02:10PM

bo...@gmail.com <bo...@gmail.com> #14Aug 19, 2015 02:25PM

my...@googlemail.com <my...@googlemail.com> #15Aug 19, 2015 04:55PM

vc...@gmail.com <vc...@gmail.com> #16Aug 19, 2015 07:37PM

mo...@gmail.com <mo...@gmail.com> #17Aug 20, 2015 05:03AM

av...@gmail.com <av...@gmail.com> #18Aug 22, 2015 04:56PM

je...@gmail.com <je...@gmail.com> #19Aug 22, 2015 05:23PM

la...@gmail.com <la...@gmail.com> #20Aug 25, 2015 02:14AM

la...@gmail.com <la...@gmail.com> #21Aug 25, 2015 09:04AM

av...@gmail.com <av...@gmail.com> #22Aug 25, 2015 09:48AM

cr...@gmail.com <cr...@gmail.com> #23Aug 28, 2015 12:37AM

dr...@gmail.com <dr...@gmail.com> #24Aug 29, 2015 02:35PM

mm...@gmail.com <mm...@gmail.com> #25Sep 1, 2015 01:04PM

kr...@gmail.com <kr...@gmail.com> #26Sep 2, 2015 05:01PM

lb...@gmail.com <lb...@gmail.com> #27Sep 3, 2015 06:47AM

he...@gmail.com <he...@gmail.com> #28Sep 5, 2015 05:33PM

he...@gmail.com <he...@gmail.com> #29Sep 7, 2015 05:31PM

se...@gmail.com <se...@gmail.com> #30Sep 14, 2015 03:47AM

wx...@gmail.com <wx...@gmail.com> #31Sep 16, 2015 02:34AM

sr...@gmail.com <sr...@gmail.com> #32Oct 3, 2015 11:56AM

ro...@gmail.com <ro...@gmail.com> #33Oct 18, 2015 03:37AM

lb...@gmail.com <lb...@gmail.com> #34Oct 18, 2015 05:13AM

da...@misena.edu.co <da...@misena.edu.co> #35Oct 28, 2015 10:39PM

bs...@gmail.com <bs...@gmail.com> #36Dec 8, 2015 09:24AM

lb...@gmail.com <lb...@gmail.com> #37Dec 8, 2015 09:29AM

[Deleted User] <[Deleted User]> #38Dec 8, 2015 04:27PM

cv...@gmail.com <cv...@gmail.com> Dec 29, 2015 06:58AM

jw...@gmail.com <jw...@gmail.com> #39Jan 9, 2016 07:53AM

og...@gmail.com <og...@gmail.com> #40Mar 25, 2016 09:24PM

se...@gmail.com <se...@gmail.com> #41May 26, 2016 11:56PM

th...@gmail.com <th...@gmail.com> #42Jun 15, 2016 01:03PM

ka...@gmail.com <ka...@gmail.com> #43Jul 19, 2016 07:20AM

sm...@gmail.com <sm...@gmail.com> #44Aug 26, 2016 01:58AM

sr...@gmail.com <sr...@gmail.com> #45Oct 5, 2016 09:36AM

pr...@gmail.com <pr...@gmail.com> #46Oct 13, 2016 05:57PM

al...@gmail.com <al...@gmail.com> #47Jan 4, 2017 10:07PM

Add comment

Issue metadata