Age | Commit message (Collapse) | Author |
|
[b1c1/b4s4 share codebase]
Include all Android.mk under hardware/qcom/sdm845 when building B4S4
Bug: 123477980
Change-Id: Id78ba3fee5e7a51036fac197401b7c51c9762d65
|
|
am: 1522ec5c3b
Change-Id: I4b70b4db9dabdeac09cd58befa856f8d9a9f0d3e
|
|
Bug: 126125118
Change-Id: Ia35cd146203060870fd75c484eda33b5f214f548
|
|
'goog/qcom/release/LA.UM.7.8.9.C1.08.00.00.516.083'"
|
|
Bug: 120848293
Change-Id: Id644e7981ee187c426c4ff3b2788a5ad8514db0c
|
|
am: f1f858409c
Change-Id: I70656f95cdc04f379d4c1439f73f10cff4e29a96
|
|
am: 2f155b3f15
Change-Id: I1ea8248b2a1f04cc2f9ebd9864306048276c5f53
|
|
am: ac9c2678b6
Change-Id: I9b3cdbb19b0ab17e2898de3089eb51409267920a
|
|
This just makes the build noisy.
Test: build
Change-Id: I250387ed501d247ecd7f794d8791e51d4dfc30a2
|
|
Bug: 124397977
Change-Id: Ib9e35c848a06699cde4d6c704cb7cb284c8dc838
|
|
Conflicts:
ipacm/src/IPACM_Iface.cpp
ipacm/src/IPACM_OffloadManager.cpp
Bug: 121228685
Change-Id: I8c74e755102e2d238379e6d1bc490ea15870616d
|
|
Initialize pointer before use to fix KW issue.
Change-Id: I023d67c13528c33e625d60e030952b0377b5fd27
|
|
(PPRL.181205.001) into master am: c44dfdf5b2 -s ours am: c01a882b1f -s ours
am: 7b8fb0615e -s ours
Change-Id: I494203f629a6eb507a7b45c28166381765aa74d9
|
|
(PPRL.181205.001) into master am: c44dfdf5b2 -s ours
am: c01a882b1f -s ours
Change-Id: Ic75f5388f3bd8b0ed93a9eb9923c2772910f87ab
|
|
(PPRL.181205.001) into master
am: c44dfdf5b2 -s ours
Change-Id: Ide75143fb1cb611a5e61b98cb023b7faac425ced
|
|
(PPRL.181205.001) into stage-aosp-master am: 74a971a76f -s ours
am: 671bf751dd -s ours
Change-Id: I9c574c7247a58be34d3ae640fab1ebcb95e388ad
|
|
(PPRL.181205.001) into stage-aosp-master
am: 74a971a76f -s ours
Change-Id: Ic3caec52f7c24a21dbf7a8b2180217036234bae1
|
|
Bug: 120502534
Change-Id: I99d604b7725c681a658637784cca7973c059338d
|
|
stage-aosp-master
Bug: 120502534
Change-Id: Ibf2f1888921355552c5bb0eff8a5a89e5c835658
|
|
Insert fallthrough statement to fix compilation
error for unannotated fall-through between switch
labels.
Change-Id: Ibc5f3f0cdc29e8144a47059c31ce15441a90ddac
|
|
Change-Id: I6bb0fb88cf4e244b6fb43bb18fe659e2edb44640
|
|
Fix the ipv6 frag pkts going to sw-exception
issue. Update the TCP ipv6 fragment rule attribute
on LTE use-case.
Change-Id: I53dcdf624cbc29146a7e095e7cc043584e919795
|
|
Made the change to get usb_link_up from
usb-driver instead of using netlink
event to resolve the timing issue
between usb-driver and android framework.
Also not self-posting the usb-up from
downstream event which was used to support
ipcam restart phase 3.
Change-Id: I3549cfbfbb5f41fa5ed99a43f00c6d8b4333b8e5
|
|
d8e80683be
am: 6a4ba47bb6
Change-Id: I562563baed42f42fa4b1b8eab7fe052158e8d504
|
|
am: d8e80683be
Change-Id: Iebcf55fc9ce28cadba69059fc27a261c098cc6b5
|
|
am: 10e9835d0c
Change-Id: Iafa19075364cd147c88f7c4d754f76a05ad326ae
|
|
It will be a global error by default.
Test: make checkbuild
Bug: 112564944
Change-Id: I1a238297f83ebbab6b9dcae0130a009ca42c756e
Exempt-From-Owner-Approval: do not block on new warnings
|
|
MERGE am: 89c726ecaf -s ours
am: 6c3324a3b4 -s ours
Change-Id: I64d3307c76273b6117141196c24fff8310825056
|
|
MERGE
am: 89c726ecaf -s ours
Change-Id: Iab421e2dc7ebd4508f471f1bbd5567c25a660c9b
|
|
Change-Id: I5e774ae614188054a26b292bfea6c35c9efc316e
|
|
Update TCP fragment rule attribute for IPv6.
Change-Id: I6c2a7c1b6f6ed7638497eb220ad5f5d6462c838e
|
|
Handle WLAN FW SSR event for FW rejuvenate
scenario.
Change-Id: Ieceaf20a05dd645e56e3fb3b87ffd7cb97453cb0
|
|
In case of TCP, if the ipv6 packets are fragmented there
is a possibility that the second fragment packets match
TCP SYN/FIN/RST rules and packets are routed to apps.
This results in connection failure as the primary fragment
will be routed correctly to hotspot client.
Change-Id: I482b48c4786bda180b6f5d921149fed766c91fe0
|
|
pi-qpr1-release
Change-Id: I5ec6fa133282c7e1f65bc46bee0f50539ee823d8
|
|
am: 6486ef4a27
Change-Id: Id10a1950cd73edbc031dd7b7f4b4abfea8d0625e
|
|
am: 235525a98a
Change-Id: I60ee18ac8150ab8528317421d5c6a461b80d8854
|
|
This can fix duplicate module names problem
with other platforms
Bug: 112062468
Change-Id: I376f8037a42e8200aea856d7515f45887cc7452a
|
|
pi-qpr1-release
Change-Id: Id910996ff03bad8cfd39f2a2acd6415dc2be0f83
|
|
am: 4ea2ff7a0a
Change-Id: Ide811fdef0fb530bddad0a072a62e4b87e4ed20c
|
|
am: 3f56153259
Change-Id: Ie30d0ec61007cf95b9194dff5e7e61a3427aa259
|
|
The internal link up events clear up the cache of requests
from FWK causing offload to fail. This CL fixes not to post
internal link up events when IPACM is started from boot.
Test: WiFi tethering offload is verified on B1C1
Bug: 110913099
Change-Id: I4b310423e188923a3a251c29cc6f7e30edc05797
|
|
Make a change to not to post internal link up events
when IPACM is started from boot.
Bug: 10913099
Change-Id: I9438076f576271d164959996821df0b864dfe23d
|
|
Without ipacm-diag debug component, all
the debug prints will have NOFILE err_type
and overrides the kernel error codes. The fix
is to cache it onve we got error from
kernel.
Bug: 109872530
Change-Id: I222f0eceaff1c2f8e5d5c71556a3a1df0c053eaa
|
|
In case of HAL feature, currently UL rules
are installed without XLAT info. Install UL
rules with XLAT mux id.
Change-Id: Ib290d439e0775f647dcc4b600e67c500b2b24fde
|
|
Test: m checkbuild
Bug: 72330874
Change-Id: Idfb07aaa187ead24547cf54fe5a35e37c73f84cc
|
|
am: 03e44a691e
Change-Id: I2962acdd63f915b15cb189270c54abff3ef5eb04
|
|
am: f22064088b
Change-Id: Ie88da0bc588effb85688b89f26413d43539a3a20
|
|
Without ipacm-diag debug component, all
the debug prints will have NOFILE err_type
and overrides the kernel error codes. The fix
is to cache it onve we got error from
kernel.
CRs-fixed: 2265427
Bug: 109872530
Test: VTS Test PASS. Basic live sanity with TMO
Change-Id: I0cda8ae7a8075ef2f8caeead078296aa7e010e58
|
|
Currently when WAN comes up, value of
IPACM_Wan::ipa_if_num_tether_v4_total is incremented. But
it is decremented in both case when WAN or LAN iface goes
down. So if WAN is up but LAN tether iface goes down and
comes up, value of IPACM_Wan::ipa_if_num_tether_v4_total
is 0. In result later UL flt rules will not be deleted when
wan goes down. In case of HAL post wan_down event with 0
if_num_tether and add condition to delete tether iface only
if HAL feature is not defined.
Change-Id: I3289cd89e2fd4de135ef44f402345644477e37b0
|
|
'goog/qcom/release/LA.UM.7.3.9.08.00.00.385.376' into pi-dev am: 3d55bd42a1
am: 23422bada9
Change-Id: I7154afaaf6443522b642b97d70b6330ef9df69f3
|