| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Ensure wifi driver load failure status is compared with
valid string which has the failure/success information.
Change-Id: I3b619ad0c005fb793d127bd2a23b376ed961d0b7
|
|
|
|
|
|
|
|
|
|
|
|
| |
wifi.c gets sys/stat.h inherited from
private/android_filesystem_config.h it should
not rely on this in the future. The intent is
to move fs_config function into libcutils and
thus deprecate any need for sys/stat.h in this
include file.
Bug: 19908228
Change-Id: Ie84477137dba47af385163decbb41b03e2aeaed4
|
|
|
|
| |
Change-Id: I2259c5159f1f6cc770b3920bff00af2cf2594b6c
|
|\
| |
| |
| |
| |
| |
| | |
on crash"
* commit '9595dc8c8e07d40d606f11fedb7afb035bc87eb2':
Changes to restart supplicant on crash
|
| |
| |
| |
| |
| |
| |
| |
| | |
specify timeout value in poll to check if the supplicant
connection is active, if not we should indicate
terminate command to framework to restart supplicant.
Change-Id: I8e602b9cb07a13c3f0b96813b2fc89f46457473e
|
|\ \
| |/
| |
| |
| |
| |
| | |
event on primary interface."
* commit '384bd5d631a9d493d65afac4ce21a751e8cd2c68':
Indicate WPA_EVENT_TERMINATING event on primary interface.
|
| |
| |
| |
| |
| |
| |
| | |
Internal fabricated WPA_EVENT_TERMINATING events to restart
supplicant should be sent on primary interface.
Change-Id: I2d018e0707819614d9b092c6f3a812f04b5446ca
|
|\ \
| |/
| |
| |
| | |
* commit 'bfad19d2a12d0cc25ad74a58fe6838b0afe45776':
Wi-Fi HAL: fix supplicant start failed issue
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
init.svc.*(hostapd, p2p_supplicant) properties are set when starting
STA or uAP via Wi-Fi HAL, after sending ctrl.start command to
property_service, thread called wifi_start_supplicant will yield cpu
for android init process to get scheduled, then init.svc.* status
is read to check if supplicant status is running
there is a chance that after scheld_yield returned, init is not
scheduled, serial value is not updated, __system_property_read got
the "stopped" status, then init is scheduled to update service status
after that back to this loop in Wi-Fi HAL, serial is updated, but
status is not reread, still used "stopped", then Wi-Fi HAL will
report supplicant start failed
as the following schedule sequence:
process A(WifiStateMachine) process B(init)
1. ctl.start
2. scheld_yield
3. __system_proerty_read
/*serial1, value1*/
4. __system_property_update
/*serial2, value2*/
5. serial1 != serial2
6. value1 == "stopped"
So after sched_yield, first check if serial is updated, then read
service status
Change-Id: I5181e0d4504c525832c033b9a35bd58ec63e1de8
Signed-off-by: jiaguo <jiaguo@marvell.com>
|
|\ \
| |/
| |
| |
| |
| |
| | |
starting it"
* commit 'e5a16307ab7fdee029ea1fe0bfacd856f948b112':
wifi: check if supplicant is running before starting it
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Wrong property was used to check if wpa_supplicant was running.
Fix this
Change-Id: I6a5bd7a3acae84f5ba4bba317d04191e0e59b2e7
Author: Jonathan DE CESCO <jonathan.de.cesco@intel.com>
Signed-off-by: Jonathan DE CESCO <jonathan.de.cesco@intel.com>
Signed-off-by: Shuo Gao <shuo.gao@intel.com>
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
Signed-off-by: Jack Ren <jack.ren@intel.com>
Author-tracking-BZ: 66748
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ic487c3767a17299880e83080b79a91dbbaef1234
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ic487c3767a17299880e83080b79a91dbbaef1234
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|/ /
| |
| |
| |
| | |
Change-Id: Ib57a87ae1ef5953b1ddcf43974b07f091f298e74
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This helps to preapre for future updates from external sources.
Bug: 9298955
Change-Id: I4c63ad5fc1ea3564aab38cfce955de19bad75c0c
(cherry picked from commit 759cc323cb586192d591a815b0fb9d839536fcd6)
|
| |
| |
| |
| |
| |
| |
| | |
Hide the implementation of the property structures by using
an accessor.
Change-Id: Ic604935882f6085e3d082baa651bad9bafe0a54a
|
| |
| |
| |
| |
| |
| |
| | |
Bug: 9313188
Change-Id: I63784493c84ac4ffcc9810a7798b1c0de1b0f68b
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
| |
| |
| |
| |
| | |
Change-Id: I11e4438ec0b36575e1b5a563ac4da57303d028c7
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
| |
| |
| |
| |
| | |
Change-Id: I832bc51279e0fb7d3002298f87a35b816b666ad5
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
| |
| |
| |
| |
| | |
Change-Id: I24af9ec380e138f24864cd9359c6901b8b29e5ee
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We saw a case of config file being corrupted. Add a mechanism to
recover from this when wifi is toggled off and on.
Bug: 8569820
Change-Id: If2baceb065838d2adb5cde61772d25a05455fc90
|
|/
|
|
|
| |
Change-Id: I4759c26bf59f593650374ae4b205e8a1f83a8d68
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Bug: 7227463
Change-Id: I4576e223c69dd67bd714fefecf0a1047770362fd
|
|
|
|
|
| |
Bug: 7361130
Change-Id: Ia076b4ec84a4a0e05ba9eaa53ed732fa041fca6a
|
|
|
|
|
| |
Bug: 6404766
Change-Id: I8d2199fe2f4d48840a237b1ec2d085fe40c06517
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lihardware_legacy was ALWAYS re-writing the
wpa_supplicant.conf file's "ctrl_interface" entry to the
value specified as the property wifi.interface, whose value
was typically "wlan0". This was designed to allow the
wpa_supplicant service to be started with a "socket"
directive in its service description in an init.rc file.
Under these circumstances, the socket name is exchanged
between wpa_supplicant and its WifiService client through an
environment variable whose name is derived from
wifi.interface and a standard prefix.
However, since the "ctrl_interface" entry was always
re-written in this way, it broke the ability to use
"ctrl_interface" in its standard usage as a directory where
the (unix-domain) socket will be exchanged.
This change restores the ability to use the standard
directory-form ctrl_interface usage by limiting the
re-writing of the ctrl_interface entry to cases where it
does not look like an absolute path or the "DIR=" form of
directory.
Change-Id: I96c8656d144c1ea41e25ab0eb0807f7b49193b49
Signed-off-by: Paul Drews <paul.drews@intel.com>
Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
|
|
|
|
|
|
|
|
| |
Some system calls can be interrupted. wifi.c in particular was getting
into error conditions during bugreport because it doesn't handle EINTR
at all.
Change-Id: I7bec432a0b3dca7dcc5c03c5e9f5e9ed73fa3c4b
|
|
|
|
| |
Change-Id: Ia7251dc86184fff710234c70a8ad54a6b245809a
|
|
|
|
|
|
| |
Bug: 5534039
Change-Id: I28c41f896347963b0ded8415d1a51ff95cbf4b2d
|
|
|
|
|
|
|
| |
See https://android-git.corp.google.com/g/#/c/157220
Bug: 5449033
Change-Id: Idfcd2f2269080d92a621dc432c65f7cf244588af
|
|
|
|
|
|
|
| |
See https://android-git.corp.google.com/g/157065
Bug: 5449033
Change-Id: I86e4ce26d8fba68584d0a7fc17111b53c56d2932
|
|
|
|
|
|
|
| |
See https://android-git.corp.google.com/g/156016
Bug: 5449033
Change-Id: I9dfdc3f00a5f4f5b6ef4c75280ce2594ab018577
|
|
|
|
|
|
|
| |
Right now, everything goes over the primary interface socket connection.
Add support for a seperate connection over the p2p interface.
Change-Id: I09118f88cfaa201b2d62d27add410cfd441d4454
|
|
|
|
|
|
|
| |
See https://android-git.corp.google.com/g/#/c/143865
Bug: 5449033
Change-Id: I953e5eabaf5023a4dcd76339c336d9132f257f8c
|
|
|
|
|
|
|
| |
BUG: b/5321709
Change-Id: Iff4692f1f35b63136297261d1565bc16c854ede3
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: Id08c211102dabccff3e7d5a1373507f8d63ec70d
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
|
|
|
| |
Create a local pipe to track when socket connection times out
and send a terminate on the monitor thread
Bug: 5337272
Change-Id: I80ed3f8450b4d54d1b9e2bbc3cc84f10d0ae7a04
|
|
|
|
|
|
|
| |
Also, fixed a bug with config overwrite with ctrl_interface update
Bug: 5002384
Change-Id: I870c12ee58d60f696512c27deb4b9d35b4dc3b2a
|
|
|
|
|
| |
Change-Id: Ia9f5bf2a905c89126535a6c01c3af67189df6c32
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We stop supplicant by sending a "terminate" control command. init then
updates the system property init.svc.wpa_supplicant when the supplicant has stopped. The
framework gets notified of a successful supplicant stop through a supplicant event.
It can happen that the framework has been notified of a supplicant stop, but the init
process has not set the system property and thus when the framework tries to connect
to the supplicant again, it can immediately return saying the supplicant is already running.
Avoid this race, by ensuring the call from framework to close supplicant connection polls
for the update by init process that the system property indicates supplicant has stopped.
Bug: 5166494
Change-Id: Ie74a8cf39fa56ae557ea6bbbcba7865301620c42
|
|
|
|
|
| |
Change-Id: I3fdbd27e45536b9142e0ca88692270bac543177a
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: Iee92ee9fee15037cffde86b9cd2c9407afb8d2ca
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: I1c4afe43457a295c0ffe0a865c6c331109dce614
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: Ib9dc8ce84febb2fba045ee527838653d0d1ad11b
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: Ic63381fe037cd5aa1f3d419d7c253c2b17961a24
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: I249646845f0837c7cbf6c118d08aecb5b3ccaba5
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: I557a2ac10ebb226508ffccfbfeca7f326912ed04
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: Icaeac0ee2239333be5f3be10024824ada6da18d5
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
|
| |
Change-Id: Iea7432bd96df2c1474e5af1788225322c9b78307
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|