rmt_storage should not be automatically killed by Android during
shutdown since it is needed to actually process the peripheral
shutdown
Change-Id: I58a29fe86955f0abad944727bb4208dad89f495d
Upstream does not use these settings
Fixes: "Revert "lowmemorykiller: adapt to vmpressure""
"Revert "lowmemorykiller: Introduce sysfs node for ALMK
and PPR adj threshold"
Change-Id: Ifa2a8b2aaa0ab9c6326ded570ccaf91c2ad5b8e1
Implement a smarter system on whether to connect
to the provided 2Ghz or 5Ghz network.
Change-Id: Idd41e3d9a5e2bde3ea9b4873dffc4274d1530324
Signed-off-by: Alex Naidis <alex.naidis@linux.com>
Setting the beacon missed count threshold
with a difference of 10 to improve stability
of the WIFI connection.
Change-Id: Iea459ead3505bcea1a41f9b0e713957092bf4745
Signed-off-by: Alex Naidis <alex.naidis@linux.com>
* Checking numInts and numStrings for strict equality when
we're not looping is dumb, because Samsung is notorious
for sending extra information in their RIL
* Check if there's *enough* data rather than the *exact amount*
to fix a bunch of invalid response errors
Change-Id: I14bc37240e5760b4629fcb74b64f25ad95d4fdfc
* For search, the number of strings returned for
RIL_REQUEST_QUERY_AVAILABLE_NETWORKS should be defined in the system
prop ro.ril.telephony.qan_resp_strings
Change-Id: Ie5bb8ba80c5ac93b7502da3b1bb3d2b4404ecd5e
* Samsung added an int to the end of the RIL_SMS_Response
struct in some of the variants (like vzw) but not all
* The presence of this field was discovered by examining
the stock RIL.java, which conditionally read an extra
int from the parcel, based on the device specific
CscFeature_RIL_SmsErrorClassRetry feature
* This causes SMS messages to show as "failed to send"
in the app, when they actually suceeded in sending
* Allow Samsung's custom struct and AOSP's to fix it
* Forward port to ril-caf on lineage-15.1
Change-Id: I6b3e545c2c42ab2de2ac11e93dfdf9546248080a
* Sometimes, the modem is sending 1-2 extra fields with
the country mcc, which confuses ServiceStateTracker
* Drop the extra data here, instead of in our RIL class
[haggertk]: Forward port to ril-caf on lineage-15.
Change-Id: Ifbec67bb0dac271226bd8b5471deaf6a2ef33f2b
* This is based on how it was done in cm-14.1, but redone
because the old code completely ignored signedness
* Samsung, in their stock RIL.java, reads index as an int,
sets the first 8 bits to index, the next 8 bits to call_id,
and ignores the upper 16 bytes of the int parcelled up
* This emulates that behavior here, except it only sends the
first 8 bits so that AOSP's RIL.java doesn't get confused
Change-Id: I5c78447fdef7d5fd7fc39addb970300ee1188cd1
* A previous revision of this libril had 16 bytes of padding in this
struct for 64-bit platforms (due to word size and struct alignment),
but a change by me to use a long instead of a pointer and an int
broke this padding for 64-bit platforms because a long is still
just 8 bytes on 64-bit platforms, where 16 bytes is necessary
* Use two pointers as padding instead to make 64-bit great again
Change-Id: If599bdb625f7a45e083f5b30df512d12810be79b
***** SIGNAL STRENGTH HACKS NOT PORTED YET *****
[javelinanddart]: Redo this code from 14.1 to include
the proper RIL_Call fixes, no Samsung unsol/request
handling as it was unnecessary, and a extensible way
to remap RIL unsols if necessary for the device
Change-Id: I59bad9925d141e6cefbc24d4eefdc0c79017852a
* Due to "specialness" in our RIL library, ConnectivityService
doesn't seem to appropriately add the relevant directly-
connected routes, meaning that IPv4 mobile data is inoperable
due to lack of a default route. Let's reenable the legacy netd
behavior to get our connectivity back.
Change-Id: I59f8476ab36db0fb79856f74346e62e0dd4abae0
* Since someone was funny enough to label display.qservice
as 'service' instead of 'vndservice' in legacy qcom sepolicy
I'm forced to move these back to passthrough ;-;
This reverts commit a8fd5e61e0.
Change-Id: I4fb729fce584450499b55cc7b8815e9768dac846
The core SEPolicy for vendor_init is being restricted to the proper
Treble restrictions. Since this is a legacy device, it is tagged as a
data_between_core_and_vendor_violators and the needed permissions are
added to its device specific vendor_init.te
Bug: 62875318
Test: boot 8976 targets without audits
Change-Id: I13aaa2278e71092d740216d3978dc720afafe8ea
The new camera interface calls set_callbacks with a pointer
to it's internal CameraDevice and expects following calls to
the callbacks to use that pointer.
Store the pointer in the camera wraper and intercept the
callbacks calls to pass it along.
Change-Id: I99f02484e12a3f72cf1be13f1c724f474a452d7f
* This has now turned into a separate repository (maintained only
for legacy devices, those that never got official Orea updates).
Change-Id: I981b452b697bc3610d7aa97b74ed182c6b70ca30
Peter Wickenberg
syphyr
Bruce Levy
Srinivas Girigowda
Alex Naidis
LuK1337
Paul Keith
Martin Bouchet
Kevin F. Haggerty
Tom Cherry
Demon000
Bruno Martins
codeworkx