Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update and rename cm.dependencies to android_device_samsung_klte-common #1

Open
wants to merge 32 commits into
base: cm-12.0
Choose a base branch
from

Conversation

OwnDroid
Copy link

never mind, wrong button...

Albinoman887 and others added 30 commits December 1, 2014 00:03
Change-Id: I628ff53c4a72cc37b3fc479502e1607773f4af71
* SELinux is not set up right now and this is causing the device to fail
to boot.

Change-Id: Ie2ba7a0c2f652073bdafaf6ab783ef13af54a7fa
* Support CDMA and GSM
* Kanged from jflteRIL

Change-Id: I222b33dd879d1c8cdaf24fb550ce835384c49050
Change-Id: Ic142f2d6ea2f48835ab73a9f22a766d0acd5a55d
* Failure to mount any partition in fstab file results in failure
to launch late-start class.

* This fixes some stubbern phones from booting, mainly those on
older bootloaders

Change-Id: I98bca4bf064b7c80e0c02152a78e4bae8487ab34
* this flag is depreciated

Change-Id: I0009934c86746c94c8a57a93be85009cd3f72ff5
its now set in qcom-common 'Telecomm'

Change-Id: Ie148e3301400402d27671754c3b9e74cf37b13c5
dlsym on gps_geofence_get_interface should check NULL,
and gmtime return should also check NULL

Change-Id: I23ab17f016ad9f4667ac197c12f016433c48af90
CRs-Fixed: 674884
A new QMI LOC msg is introduced which injects into
the modem a value that determines whether or not
the version of XTRA is to be checked

Change-Id: I0ef579332d064713ce73d80e66dc8c6fef1c1638
CRs-fixed: 649860
There is a race condition where when startFix is
called right at the time when modem or griffon
subsystem is down, GPS HAL doesn't get the correct
error code, and therefore the right handling.

Mapped ENGINE_DOWN to ENGINE_OFFLINE, as they are
the same; and modified loc_eng_start_handler to
update the state upon the right error code.

There is a one problem though. General failure is
also handled as SSR. This is because of an unhandled
race condition in the kernel, so the error code
returned and propagated is not deterministic enough
for us to tell if this is SSR. Until that fix is in
place, we might have to treat general failure as SSR
although the side effect should be none. Only
semantically incorrect.

Change-Id: If93823f08428275da171bb22d73a06e38365585b
CR-Fixed: 692085
loc timer util stop() routine may have race condition
with the timer thread, when timer expires at the same
time stop() routine tries to lock mutex.  The race
condition can go 2 ways:
* timer thread expires, unlocks mutex, context switch,
stop() thread acquires lock, context switch, timer
thread destroys mutex.  Destroy will fail, resulting
mutex leak.
* timer thread expires, unlocks mutex, destroys mutex,
stop() acqures lock, signal, and releases lock. Would
be super rare conditions though.

Fix is that we give 5 seconds for stop() thread to
give up the lock when destroy. After that the timer
thread will release the mutex and go on destroy.
Meanwhile the stop() thread would check the lock
return to move on with signal and unlock.

Change-Id: Iff9e34d08a1faf0828049de2fede2e7a5d15b161
CRs-Fixed: 699856
eLOC_CLIENT_FAILURE_INTERNAL returned from loc_api_v02 was mapped
to LOC_API_ADAPTER_ERR_FAILUR, however in loc_eng_start_handle it
is LOC_API_ADAPTER_ERR_GENERAL_FAILURE that is being checked for.
Created a new error ID LOC_API_ADAPTER_ERR_INTERNAL specifically
for this error case.

Change-Id: Ib2ad6e983d6c598ec57f1a2584166da2be95946b
CRs-Fixed: 706520
Changes to include "auto" option as well for ro.baseband property.
submitting on behalf of Madhanraj Chelladurai

Change-Id: I96abaea799df34d375a6a5db7341c17b99c94675
Change Summary:
* Structure definitions for GNSS SV Measurement and GNSS SV
  Polynomial to report it to ULP and to external DR module;
* New function additions in LocApiBase, LocAdapterBase and
  LocEngAdapter to report SV Measurement and SV Polynomial;
* definition and changes to detect "auto" platform in loc_target;
* enable SV Measurement and SV Polynomial report for "auto"
  platform;

Change-Id: I0611023197ce58f5d083588809c2f18922738357
*Added logic to remove xtra1.gpsonextra.net from URLs
received from modem.
*Added logic to override modem URLs with those configured
in gps.conf
*Replaced all instances of xtra{1,2,3}.gpsonextra.net domain URLs
in gps.conf with xtrapath{1,2,3}.izatcloud.net URLs.
*Replaced all commented instances of xtra.bin in gps.conf with xtra2.bin.

CRs-fixed: 643816

Change-Id: I803b26bce22f06910dcaa1ee057902b9381667bf

Conflicts:
	gps/etc/gps.conf
GpsLocation memory will now be cleared inside the
Loc Api handler itself, so no need to do it a second
time before calling into the Loc Api handler.

Change-Id: Iec37624621d6eb4806eb8e13c807bb4e40584e39
CRs-fixed: 726800
Change-Id: Ifba9198a902a022c1da56c7041d65d5994762f2b
Change-Id: I89da84d33e9c2f64fe95526bf6eb46af8a30b246
* Make sure radio is on for setCdmaSubscriptionSource and
  getHardwareConfig

Change-Id: I61d96233d7a6dac018553cc7c636c3c2681ea273
Change-Id: Ie1180fa38456ddf202d4b15fd9aaf19119e6bc0b
Change-Id: I0bb47c4e7af39f8e5d1a5ceedc84807e6b78a34c
Change-Id: I55af2f87b1fc06a9870c96bad86c7bab19d85999
Change-Id: I025ab9f2602cc873f97969d4055c33265bd4cd7d
Change-Id: I38a2488daafb900d5272f013db121fcfcdd671c7
@Albinoman887 Albinoman887 force-pushed the cm-12.0 branch 2 times, most recently from 4104210 to e31aba2 Compare January 20, 2015 05:10
@Albinoman887 Albinoman887 force-pushed the cm-12.0 branch 2 times, most recently from 7e5fc15 to 9e6440e Compare February 9, 2015 07:10
@Albinoman887 Albinoman887 force-pushed the cm-12.0 branch 2 times, most recently from eff440f to 630b727 Compare February 27, 2015 07:01
@Albinoman887 Albinoman887 force-pushed the cm-12.0 branch 3 times, most recently from 975f053 to d460453 Compare March 23, 2015 04:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants