In-depth understanding of android:wi-fi, nfc, and GPS volume Errata

Source: Internet
Author: User
Tags ack function prototype goto wpas
<span id="Label3"></p><p><p><span style="font-size:24px;color:#ff0000;">Download updates for resources (i don't know why it's blocked by a 115 network Disk)</span></p></p><p><p><span style="font-size:24px;color:#ff0000;">Get an insight into Android it Wifi-nfc-gps<br>115 Network Tray gift Pack code: 5lbee5qn4g5g<br>http://115.com/lb/5lbee5qn4g5g</span><br></p></p><p><p><span style="font-size:18px;"><br></span></p></p><p><p><span style="font-size:24px;color:#ff0000;">and 115 after communication,</span></p></p><p><p><span style="font-size:24px;color:#ff0000;">http://115.com/lb/5lbdugrdt4r Recovery Use</span><br></p></p><p><p><span style="font-size:18px;"><br></span></p></p><p><p><span style="font-size:24px;">Brother Changchangzhi read it several times carefully. And all the feedback to focus on the Next. Thank you very much, a real good book is the need for the author and the reader to work together to build talent enough to create! Thank you, Brother.</span><span style="font-size:18px;"><br></span></p></p><p><p><span style="font-size:18px;"><br></span></p></p><p><p><span style="font-size:18px;">Thank <span style="font-size:24px;">Changchang</span> for his careful feedback. No matter how careful the previous period, the writing process still has some mistakes.</span></p></p><p><p>Here to organize the next brother's feedback Error.</p></p><p><p><span style="font-size:18px;">The time is slightly tight, and then reply to the bug Here.</span></p></p><p><p><span style="font-size:18px;"></span></p></p><span style="font-family:Calibri;font-size:18px;"><span style="font-family:Calibri;font-size:18px;"></span></span><p><p>P21</p></p><p><p>Bottom line 4th</p></p><p><p>"then Check to see if there are any other <span style="BACKGROUND: yellow"></span> hosts inside the network."</p></p><p><p></p></p><p><p>There's a typo here, "again."</p></p><p><p></p></p><p><p></p></p><p><p>P43</p></p><p><p>There is a spelling error in the middle of the page that describes the pseudo Terminal.</p></p><p><p>"pseudo Terminal (psuedo terminal)"</p></p><p><p>It should be pseudo terminal.</p></p><p><p></p></p><p><p>Psuedo this word from Youdao dictionary only can find the network interpretation, i Baidu the next Unix pseudo terminal, found that spelling is indeed wrong, should be pseudo terminal</p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p>P65</p></p><p><p>The translation of the LLC is less accurate when speaking 802.11c and 802.11d.</p></p><p><p>Here to translate the LLC into Link connection control</p></p><p><p>The full name of the LLC on the agreement is logical link control, which is generally translated into logical link controls</p></p><p><p></p></p><p><p></p></p><p><p>P69</p></p><p><p>In line 5th below in Figure 3-3, say "the length of the data frame to be sent in the RTS frame", and in the following line, "also attach the length of the data frame to be sent by station A in the CTS frame (copy the secondary data from the RTS into the cts)"</p></p><p><p></p></p><p><p>however, I do not know the length of the data frame mentioned here in the detailed RTS and CTS Frames.</p></p><p><p>RTS frames such as the following:</p></p><p><p></p></p><p><p></p></p><p><p>Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvsw5ub3n0/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70 /gravity/southeast "/></p></p><p><p>CTS frames such as the following:</p></p><p><p></p></p><p><p>According to the protocol (IEEE STD 802.11-2007), in the RTS frame format also found no data transmission length of the representation field, but found a duration field, but this field represents the time, That is, how much time this RTS has reserved for transmitting data or managing frames, plus CTS frames and ACK and SIFs Time.</p></p><p><p></p></p><p><p>The detailed agreement is so descriptive (on page 72 of the agreement):</p></p><p><p>For all RTS frames sent by Non-qos STAs, The duration value was the time, in microseconds, required to transmit the pending Data or management frame, plus one CTS frame, plus one ACK frame, plus three SIFS intervals.</p></p><p><p></p></p><p><p>CTS is also the same, there is no data transmission of the frame length of this field, the same duration field, also represents the Time.</p></p><p><p>My translation is not good, the detailed agreement is such descriptive narrative (agreement 73 page):</p></p><p><p>For all CTS frames sent in response to RTS frames, The duration value is the value obtained from the Duration field of the Immediately previous RTS frame, minus the time, in microseconds, required to</p></p><p><p>Transmit the CTS frame and its SIFS interval. If the calculated duration includes a fractional microsecond, That's value is rounded the next higher integer.</p></p><p><p></p></p><p><p>In addition, you also describe the RTS in the P91 of this book, where the descriptive narrative is described in terms of the Agreement.</p></p><p><p></p></p><p><p>P83</p></p><p><p>Line 6th</p></p><p><p>"in Non-qos cases, It is clear that the higher <span style="BACKGROUND: yellow"></span> data is given priority."</p></p><p><p>This is a typo. it should be "just."</p></p><p><p></p></p><p><p></p></p><p><p>P87</p></p><p><p>On line 4th below the Address field (3):</p></p><p><p>"0~23 bit is the manufacturer to the IETF and other institutions to represent the Manufacturer's code", checked the information, found that the Mac Oui should be to the IEEE application it.</p></p><p><p>I found the agreement and Baidu Encyclopedia information such as the Following:</p></p><p><p>There is a sentence on the P128 page of the IEEE std802.11–2007:</p></p><p><p></p></p><p><p></p></p><p><p>In the Baidu Encyclopedia for example the following address:</p></p><p><p></p></p><p><p>url=uag8niziyqtnjzypmrdgqrssll00nmqmhkyzws73g3emy7ibanoluw7nefansf4k "><span style="color:#0000ff;">http://baike.baidu.com/link?</span></p></p><p><p>url=uag8niziyqtnjzypmrdgqrssll00nmqmhkyzws73g3emy7ibanoluw7nefansf4k</p></p><p>Said In:<span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">Organization unique marker</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">(OUI)</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">the Association of Electrical and Electronic Project Engineers</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">(<span style="BACKGROUND: yellow">IEEE</span>)</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">assigned to a unit organization, it includes the</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white"></span> -</span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">bit</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">(3</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">bytes</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">)</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">. Each organizational unit is assigned a global management address in turn</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">(</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">bit, or</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">3</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">of bytes</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">)</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">. This address is unique for each NIC that the manufacturer Produces.</span></span><span style="color:#333333;BACKGROUND: white"><span style="color:#333333;BACKGROUND: white">. </span></span></p><p><p></p></p><p><p><span style="color:#333333;BACKGROUND: white"></span></p></p><p><p><span style="color:#333333;BACKGROUND: white"></span></p></p><p><p><span style="color:#333333;BACKGROUND: white"></span></p></p><p><p>P105</p></p><p><p>At the bottom of the page, in the second half of the "hint", " <span style="BACKGROUND: yellow">because</span> <span style="BACKGROUND: yellow">wi-fi</span> <span style="BACKGROUND: yellow">takes air as the transmission medium</span> "</p></p><p><p>The expression here is not rigorous.</p></p><p><p>Wi-fi is the use of radio frequency transmission, that is, electromagnetic waves. electromagnetic waves can travel through air, vacuum, Cement and other objects, only these objects are not the same attenuation caused by electromagnetic waves.</p></p><p><p>For example, satellite communications, also used electromagnetic waves, but space is already a vacuum, and then for example, Mars sensor on Mars to transmit signals to the Earth.</p></p><p><p></p></p><p><p></p></p><p><p>P106</p></p><p><p>In the 1. The WEP introduction says "WEP is the elder of the 802.11 specification, which was born in 1999 ..."</p></p><p><p>The specification came out in 1997.</p></p><p><p></p></p><p><p></p></p><p><p>P107</p></p><p><p>Line 10th of the text on this page</p></p><p><p>"the data after the XOR operation is the encrypted part of Figure <span style="BACKGROUND: yellow">3-29</span> "</p></p><p><p>Reference error, from context understanding and check figure 3-29, found that the reference here should be figure 3-31.</p></p><p><p></p></p><p><p></p></p><p><p>P109</p></p><p><p>In the third line below the "specification reading tip", "WPA uses a new mic algorithm"</p></p><p><p>The mic here should be interpreted as a message Integrity Code,</p></p><p><p>See Protocol (802.11-2012) on page 21st with MIC explanation: message Integrity code</p></p><p><p>It is generally translated as "message integrity verification code"</p></p><p><p>The proposal is still in accordance with the Agreement.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P112</p></p><p><p>Figure 3-36 The parentheses in the first line below:</p></p><p><p>"eap over lan, lan-based extended EAP protocol"</p></p><p><p>The E in EAP itself is the meaning of the extension, and P is the meaning of the Agreement.</p></p><p><p></p></p><p><p>This should be interpreted as "lan-based eap". this feels awkward, rather than saying "lan-based extended authentication protocol".</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P117</p></p><p><p>The first "rsne" appeared in the penultimate line, which was not explained in the previous Article.</p></p><p><p>According to the 802.11-2012 agreement Rsne is robust Security Network element</p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p></p></p><p><p>P162</p></p><p><p>In Figure 4-11, when the struct wpa_supplicant is interpreted:</p></p><p><p>a). when explaining l2, it is said that L2 is the abbreviation of link layer. That's right. but for those who have just started learning may not understand why L2 is a link layer. I think the explanation L2 is layer 2, that is, "layer 2" is better. and then explain that Layer 2 is the data link layer, Layer 3 is the network Layer.</p></p><p><p></p></p><p><p>b). when explaining own_addr, the number of Eth_alen is 16. But Eth_alen represents the MAC address length, which is 6 bytes, 48bit.</p></p><p><p></p></p><p><p>c). when explaining the 9th member variable bssid, There is a typo. say "elements for eth_alen", should be "number of elements" bar.</p></p><p><p></p></p><p><p>d). when explaining the 12th member variable disconnected, there is a typo "link" that should be "connected".</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P163</p></p><p><p>The 5th line explains countermeasures by referring to the mic, which is said to be (Message Integrity Check), which is explained on page <<802.11-2012>> 21st:</p></p><p><p></p></p><p><p>We usually call the MIC message integrity check code, here C should be the meaning of Code.</p></p><p><p>It is advisable to refer to the above agreement for Instructions.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P188</p></p><p><p>In Figure 4-19, the member variable own_addr is interpreted as saying "eth_alen, value 16":</p></p><p><p>Eth_alen is the length of the Mac address, which is 6 bytes, 48bit.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P199</p></p><p><p>In the first gaze section below [àstate_machine.h], EAP SM is written as the EAP SSM, for example the Following:</p></p><p><p>"and State_machine_data is also a macro. for the EAP <span style="BACKGROUND: yellow">SSM</span> ".</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P225</p></p><p><p>The last few words in line 7th:</p></p><p><p>" <span style="BACKGROUND: yellow">all</span> , direct view"</p></p><p><p>This is supposed to be "so."</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P242</p></p><p><p>The middle part of the wpa_supplicant_set_state () after this sentence of the Lord is in <span style="BACKGROUND: yellow"></span> the "set wpa_sm as wpa_associated"</p></p><p><p>There's a typo Here.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P244</p></p><p><p>Second line of gaze in the latter part:</p></p><p><p><span style="BACKGROUND: yellow">"</span> <span style="BACKGROUND: yellow">a series of actions of the state machine</span> "</p></p><p><p></p></p><p><p>Here feel the sentence is not smooth, guess half a day is not clear what meaning.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P244</p></p><p><p>Line 11th, When analyzing eapol_sm_notify_portenabled, the function prototype is missing the left Parenthesis. it should be.</p></p><p><p><span style="font-size:14px;">void eapol_sm_notify_portenabled<span style="BACKGROUND: yellow">(</span>struct EAPOL_SM *sm, Boolean enabled)</span></p></p><p><p><span style="font-size:14px;"></span></p></p><p><p><span style="font-size:14px;"></span></p></p><p><p><span style="font-size:14px;"></span></p></p><p><p><span style="font-size:14px;">P248</span></p></p><p><p><span style="font-size:14px;">First line</span></p></p><p><p><span style="font-size:14px;">"ie Information for nl80211 ........."</span></p></p><p><p><span style="font-size:14px;">There is no sense here, should be in the "ie information" after the comma. you start by reading the feeling from the last line of the previous Page.</span></p></p><p><p><span style="font-size:14px;"></span></p></p><p><p><span style="font-size:14px;"></span></p></p><p><p><span style="font-size:14px;">P264</span></p></p><p><p><span style="font-size:14px;">In the 6th line of the 4.6.1 Chapter summary</span></p></p><p><p><span style="font-size:14px;">"the process actually includes far <span style="BACKGROUND: yellow">more</span> code than the book"</span></p></p><p><p><span style="font-size:14px;">Here the statement is not fluent, should be "far more than the book to give more."</span></p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p>P276</p></p><p><p>In line 10th, There's a comma when explaining Rssi in a block stare.</p></p><p><p>The Wpas supported RSSI information includes: receive signal strength, connection speed noise intensity (noise) and frequency "</p></p><p><p></p></p><p><p>There is less comma behind the link speed</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P278</p></p><p><p>Line 19th, When you talk about Wifiapconfigstore.</p></p><p><p>"configuration information stored in/data/<span style="BACKGROUND: yellow">/</span>misc/wifi/softap.conf"</p></p><p><p>There are 2 of them after/data</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P279</p></p><p><p>The 12th line in Wifi_start_supplicant ()</p></p><p><p>"//p2p _prop_name value is ...."</p></p><p><p>There's a space after the Peer.</p></p><p><p></p></p><p><p></p></p><p><p>P286</p></p><p><p>Line 2nd</p></p><p><p>finally, a period is missing.</p></p><p><p>I'm against the rest of the place and I really need a full stop here.</p></p><p><p></p></p><p><p></p></p><p><p>P303</p></p><p><p>Line 18th</p></p><p><p>In 5) place the following line</p></p><p><p>"initializing <span style="BACKGROUND: yellow">WPS</span> -related information, setting wifistate"</p></p><p><p>I feel the WPS is misspelled here. since I researched this function, I didn't find any wps-related code, it should be wpas.</p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p>P323</p></p><p><p>Third line</p></p><p><p>"and add a wireless device to the wlan"</p></p><p><p>There's a space here.</p></p><p><p></p></p><p><p></p></p><p><p>P336</p></p><p><p>In the middle of the bottom 7th line:</p></p><p><p>"this process <span style="BACKGROUND: yellow"></span> involves m1~m8-related knowledge."</p></p><p><p>Here is a typo, it <span style="BACKGROUND: yellow"></span> should be</p></p><p><p></p></p><p><p></p></p><p><p>P355</p></p><p><p>The 7th line concludes:</p></p><p><p>"w<strong>pas_wps_ssid_wildcard_ok"</strong></p></p><p><p>Here the function is bold, but the first letter W is not bold.</p></p><p><p>The format is Inconsistent.</p></p><p><p></p></p><p><p></p></p><p><p>P362</p></p><p><p>Line 19th</p></p><p><p>The second half of the 5th line below case Eap_code_request</p></p><p><p>"esc_start belongs to Extended EAP protocol"</p></p><p><p>The question is raised in the previous chapter that EAP itself is the meaning of an extended authentication protocol,</p></p><p><p>Here again, the extended EAP protocol is a bit Repetitive.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P366</p></p><p><p>The middle section describes wps_get_msg the following sentence in the Wpas spelling the wrong. I used to spell it wrong.</p></p><p><p>"we've covered M1~M8 in the previous section." in <span style="BACKGROUND: yellow">WAPs</span> 's code ... "</p></p><p><p></p></p><p><p></p></p><p><p>P627</p></p><p><p>Figure 6-7 the first paragraph below</p></p><p><p>"although EAP-WSC finally ends with a eap-fail frame, ..."</p></p><p><p>Here is a whole paragraph, I say my understanding.</p></p><p><p></p></p><p><p>The specification says that the last eap-fail frame is useful to terminate the interaction of EAP and also to notify the upper layer that the EAP interaction has Ended. station will have to actively disconnect from the AP after receiving this frame. then use the password to get it, and then start the normal connection and the Four-step handshake again.</p></p><p><p></p></p><p><p>The following is an excerpt from the Specification:</p></p><p><p>P31 (wps Specification Version 2.02)</p></p><p><p></p></p><p><p></p></p><p><p>P58</p></p><p><p></p></p><p><p>Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvsw5ub3n0/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70 /gravity/southeast "/></p></p><p><p></p></p><p><p>P62 page</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P365</p></p><p><p>Bottom Line 7th</p></p><p><p>"if (data->state = = Wait_frag_ack) <span style="BACKGROUND: yellow">{...//mf</span> <span style="BACKGROUND: yellow">flag bit processing</span> <span style="BACKGROUND: yellow">}"</span></p></p><p><p>It's not quite right to stare here, it should be dealing with Wait_frag_ack things.</p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p><span style="font-family:Calibri;font-size:14px;"></span></p></p><p><p></p></p><p><p>P383</p></p><p><p>Table 7-4 OUI Subtype values</p></p><p><p>In the 2nd column to the right of the table is also listed in the 4-peer invitation response This field of introduction, because the left column has been listed at the End. this is Repeated.</p></p><p><p></p></p><p><p>When I saw this, I looked carefully at the 2 Differences.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P384</p></p><p><p>Line 3rd</p></p><p><p>Talking about Go Intent.</p></p><p><p>"the Word is 1 bytes in length and is only used for the first eight bits of the byte"</p></p><p><p></p></p><p><p>here, a byte is not 8 bits, so the description here is described as "using the first eight bits of this byte" feeling Inappropriate.</p></p><p><p>According to the protocol, this byte is really not full, with the lowest bit of a bit to represent the tie breaker, with 4bit for intent, because the maximum value is 15, because 4bit is Enough.</p></p><p><p>Is my go Intent, the value of this byte is 0C, so go Intent is 6,tie breaker is 0</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P384</p></p><p><p>Bottom Line 3rd</p></p><p><p>"the Tie Breaker is a random value, so the tie breaker of the two devices has the same probability of being low"</p></p><p><p>I feel that the same probability of value is not too low ah.</p></p><p><p>Tie Breaker is only 1bit, the value can only be 0 and 1, then there are the following 4 kinds of values</p></p><p><p>00 01 10 11</p></p><p><p>From the above, the device will take 0 and take 1 of the situation is 50% Probability.</p></p><p><p></p></p><p><p></p></p><p><p>P407</p></p><p><p>Bottom Line 6th</p></p><p><p>In the latter part "it is processed in p2penabeldstate, and WPA<span style="BACKGROUND: yellow">s</span>_supplicant will launch the peer-to discovery process ..."</p></p><p><p>This place wpa_supplicant the wrong spelling.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P412</p></p><p><p>The type and length of dev_addr are mentioned in the p2p_config descriptive narrative in figure 7-29.</p></p><p><p>DEV_ADDR is a Mac address, so the type is definitely char, and the code shows the u8, which is unsigned char, which is 6 bytes in Length.</p></p><p><p>So the descriptive narrative in the book is an int array and the length is 8 bytes is not correct.</p></p><p><p></p></p><p><p></p></p><p><p></p></p><p><p>P424</p></p><p><p>In Wpas_start_llisten's commentary, line 3rd</p></p><p><p>"calls Deriver_nl80211.c's Wpa_driver_set_ap_wps_p2p_ie function, which is used to probe response frame information and association response frame information."</p></p><p><p>The above sentence does not make sense, said half of it is gone. so I can not understand what the meaning.</p></p><p><p></p></p><p><p></p></p><p><p>P388</p></p><p><p>In the "tips" column of this page, it is mentioned that when the peer device receiving the PD request does not support the Sender's WSC Config methods, Why not set the Config methods to its own WSC method in the PD response frame?</p></p><p><p></p></p><p><p>After analyzing the code and research, I found that for example the following reasons, his design is Reasonable.</p></p><p><p></p></p><p><p>first, when the peer device sends the PD request, it lists all of the WSC Config methods that it supports, that is, it is sent out in this Frame. this property is in peer Device info in the PD request frame, for Example:</p></p><p><p></p></p><p><p>Build the code for this peer Device info such as the following:</p></p><p><p>P2p_buf_add_device_info ()</p></p><p><p></p></p><p><p>From here, it is exactly the same as the config methods caught in the empty message order above, that is to say, the party issuing the PD request gives all the methods that it Supports.</p></p><p><p></p></p><p><p></p></p><p><p>So what does the peer device that receives this PD request handle?</p></p><p><p>See for example the following function:</p></p><p><p>P2p_process_prov_disc_req ()</p></p><p><p></p></p><p><p>Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqvsw5ub3n0/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70 /gravity/southeast "/></p></p><p><p>In this function, the device that receives the PD request will match the Config_methods in the request with all of the methods supported by it in the process of the PD request to see if there is a way to Match.</p></p><p><p>Assuming that none of them match, then this goes to goto Out. then look at Goto out:</p></p><p><p></p></p><p><p>, assuming that all of the Device's own methods of receiving the PD request cannot match the sender, the config_methods is filled in 0 when the build PD resp.</p></p><p><p></p></p><p><p>Because all of their methods do not match, it is not necessary to give their own methods of Support.</p></p><p><p></p></p><p><p>From the mechanism, the sender gave their own all the methods of support, then the recipient with their own all the way to match, found that the match is not, so here directly to the end of the 0. give your own support method, the sender can not solve the Problem.</p></p><p><p></p></p><p><p></p></p><p><p>P433</p></p><p><p>There's a typo in the line above the 7.4.4 Title.</p></p><p><p>"let's look at this chapter's last- <span style="BACKGROUND: yellow">to</span> -peer process."</p></p><p><p></p></p><p><p>Thanks to the friends on the blog ...</p></p><p><p><span style="line-height: 20px;">The P450 page of Figure 8-6 above TNF should be 3bits instead of 2bits.</span><br style="line-height: 20px;"><span style="line-height: 20px;">A description of table 8-5status for the p453 page, 7th bit 0. Represents the Utf-8 Encoding. It seems that the book is Counter-written.</span><br style="line-height: 20px;"><span style="line-height: 20px;">The string of text in Figure 8-8 of the p453 page should be "hello,world!" , let's say "Hello Word". It seems that the payload length field is Incorrect.</span><br></p></p><p><p><span style="font-family:Calibri;font-size:18px;"></span></p></p><p><p><span style="font-size:18px;"></span></p></p> <p style="font-size:12px;"><p style="font-size:12px;">Copyright Notice: This article blog original articles, blogs, without consent, may not be reproduced.</p></p> <p><p>In-depth understanding of android:wi-fi, nfc, and GPS volume Errata</p></p></span>
Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.