| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
http://review.cyanogenmod.com/#/c/18206/2 was
missing a few QCOM_HARDWARE #ifdefs even though its origin
was CAF. So far, 18206 has only had positive effects on
certain QCOM devices, and is a noop or breaks things on
non-QCOM.
Per discussion with arcee - #ifdef the rest as QCOM
Change-Id: I46684ef5e6c580137104ad81b4faf58858bbfdd3
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* The Samsung RIL will sometimes send up an UNSOL_AM
request which is to be handled by the "am" service.
(For example when the RIL resets)
Change-Id: Ifc8ead91f2dbc39456c4a502b9623c608c796224
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add a new RIL class with responseCallList that handles the Samsung video call
field. Fixes stuck on hangup and missed incoming call on d2att.
Change-Id: I3204283876a0d1c8af4c6df1c04d8c34c3a6131f
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Import the fix from SamsungRIL to fix the 'Phantom ringtone' (or 'Ring of Death').
See source for comments about the fix.
Change-Id: I0da6586e6a5b47abc9a7ceba45c4c71a5c9052f6
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Extend volume preference to be able to intercept volume changes
- Add settings to provider
Change-Id: Iec36c1ea0c9cc389e0c752d74a80694d62055fd1
|
| |/
|/|
| |
| |
| |
| |
| | |
play music via headset -> notification comes in -> music volume gets set to 0 ->
notification gets played -> music resumes with wrong (much lower) volume
Change-Id: I3961ed48d0687bacb60ee8d4ddc82575f06c908e
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
During setPreviewWindow call camera_preview_window instance will
be passed to the HAL. camera_preview_window instance will never change when
ANativeWindow is updated. Hence HAL tries to use old preview window
handle not knowing that the preview window is updated. Added the
check in camera interface to reset the preview handle based on
whether ANativeWindow instance is changed or not.
CRs-Fixed: 341892
Change-Id: I6743f24cbd4467025d6fe21098c7ce6813017d5e
Frameworks: Allow CameraService to set window when preview is not running
Change-Id: Iab3f652ed3a7639c660e85c98a837215985a3296
Camera: Enable metadata callback after snapshot
Change-Id: I734fc596b7549d4dcc00aee466e1c4be02e38c8d
CRs-fixed: 346728
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I9fe94cc036c15cdba0eccd3c5778687a3c6eee98
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Android 4.0 cannot form multitouch events from multiple input
devices. So it is not possible to report one touchpoint from the
stylus position and, at the same time, another touchpoint from a
finger touch. Instead, when a new input device starts up the currently
active input is cancelled. This is highly undesirable while writing
with the pen.
The easiest solution is to ignore non-stylus touch events while the
stylus is within range (hovering) of the touchscreen. For example,
N-trig digitizers implement this in hardware. But wacom digitizers do
report pen data simultaneously with touch data. This patch disables
(non-stylus) touch input within 50ms of stylus data. On my Galaxy
Note this is necessary to make stylus input usable.
Change-Id: I9f458d85d8bf83d6cf03b467d46ce066fd55b7e0
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Removes a lot of unecessary code, and does not limit toggles by 6 but dinamically adds the views to layout
patchset 2: remove tab
Change-Id: Id125605791d2de353e7466c4dfe135c32fb80df6
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Having the symbol picker options in resources allows a change to be made for
a specific device, and even for a specific locale (change in overlay).
Change-Id: If39eafc7d0766d28ef6bee0ff61bf234a6654f38
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
in the code that parses the NITZ string, someone made the assumption that if
any data follows the DST flag, it must be be the android emulator appending
an actual timezone string in "Area!Location" format. However, it seems that
some carriers or perhaps in some locations, the carrier sends an additional
field in the NITZ string. For example, this is a string from AT&T:
12/07/01,09:37:43-16,01,310
The extra field is "310" above. This patch will only assume that the field
in question is a textual timezone if and only if it contains an exclamation
point. Otherwise, the extra field is ignored and the timezone is parsed
as it should be.
Change-Id: I6cc4278027a6de5545d76b803f5359923e60878a
Signed-off-by: Gary Dezern <garyd9@gmail.com>
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
bars" into ics
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Math error in GSM level calculation gave high probability that 4
Samsung bars would be shown as 3 AOSP bars.
* Samsung sends # of bars in the signalstrength field of GSM and LTE,
indexes 0 and 7. But this is on a 0-5 scale where AOSP uses 0-4 scale.
The cutoff points for the bins are also different. Because of this
confusion, just pass the measured signalstrength to the framework
instead of computing signalstrength based on # of Samsung bars.
* For debug and experimentation, Samsung's bar method can be enabled
by setting telephony.sends_barcount=true
Change-Id: I8238af83f3a597b32eb99f42c71cbc263ad5bc82
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
hello ifdef hell
Change-Id: I76bede141dfd4fd4f32b5a5aa8987fb255c207a5
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: Icdd4f676ea15b933985a9505fcf316aeb7c50ce2
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | | |
button without lockscreen" into ics
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
without lockscreen
Contributed by Andrea Arcangeli <andrea@cpushare.com>
Change-Id: I8fe581ae51b38b65540eaefba6c051101fd63021
|
|\ \ \ \ \ \ |
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Enabled use of hardware switch for rotation lock
on android tablets containing this feature
such as the acer iconia a500
Change-Id: Iaaecf3c6e8ae74ae9f5aefffa2c9b7d547ef0119
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Change-Id: Ic80f59e7174932bb51bbefa9837635262feae8f1
|
|\ \ \ \ \ |
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Based off of this commit, updated for ics:
https://github.com/CyanogenMod/android_frameworks_base/commit/ebb5e47760cc156fba6d6a93ad0dfaeb562f4771
Allows keypads to have custom keymapping, and brings back www./.com key
function
Fixed: Corrected all wrong entries to api/current.txt,
including for those that already passed gerrit review
@hide used in java for all non aosp api
Change-Id: I0ffb35dae441e3ef7a4924492cc9168939551d3f
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
on msm8960." into ics
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Samsung CDMA RIL doesn't send CDMA NV in RIUM infomation format which causes
the CDMA RIL stack to crash and end up not being provisioned.
* Samsung put CDMA NV in GSM format. I forced the RIL stack to process CDMA NV
request as a GSM SIM in CDMA mode.
* Fix hangup bug, force drivercall class not to crash due to a malformed
response from ril. I suspect samsung rom ignores that. --FIXED properly JULY 3RD
* Workaround for signal strength.
* Properly fix drivercall which caused a regression in the previous attempt to
fix driver call because the ril is giving another request for videocall
infomation and causing drivercall to crash.
patchset 3, 4, and 7: Cleanup whitespace
patchset 8: wrapped commit message
Change-Id: I733a635edc645f4e7952083008e7eca12d7af015
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I16015d29a969dfe6ed6dac118db39230b1b77ea1
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: Ie67f15fd154dd0e64b6f3a007c938bf162e25e77
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Modify rotation animation to use a screenshot instead of a black screen.
Change-Id: I71563680f5d7cb355dd50b8873fa1b420a131512
|
| |_|/ /
|/| | |
| | | |
| | | | |
Change-Id: Ic715d1f7657d2ca99cc44d6b6971daeee176530e
|
| |_|/
|/| |
| | |
| | | |
Change-Id: I93d3d985d38a2b852023c3803eb2073dea989185
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds Quiet hours support and ability to configure the led if the
device supports multiple colors for the Light - enabled via overlay
with default as 'false'
Change-Id: I905dde400ba0780066f2b2a20142eaa27e158655
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I6c792b6f5f586cf40d4a9b834e793a68c1e458a7
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
based on http://review.cyanogenmod.com/#/c/18220/
Change-Id: I872221e58e89412fcecf67c7208ab2c89aac7c04
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Due to bug in GLRenderer stale FBO remains and can cause
corruption, clear layer fbo when fbo returned to cache.
CRs-fixed: 340481
(cherry picked from commit b01c082e12c4c4091016af1c95d851f29f5b7514)
Conflicts:
libs/hwui/LayerRenderer.cpp
Change-Id: I8624879b4adbf9438a8c065b78932d1a4a2a15d4
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a squash of the following change IDs:
I42b4ad02c4eb8b57a2f4cf51a31148c4b0546b81
I6f619740659cfedec3a3c9517fb55275f601d792
Iaee471b29b306e9ebcc6a81799f7e36872951002
Change-Id: I4e40d8e27b9bb11367e30223ffb8024985476e74
|
|\ \ \ \
| |/ / / |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I00a351311d0933fe326bda33f5c988a6232cca16
|
|\ \ \ \
| |/ / /
| | / /
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As the user (who controls the app behaviour after all) likely doesn't
see the PIN screen as a lock screen (he likely wants telephony) and the
PIN screen is not shown on a timer-driven basis, it should be treated
specially.
Change-Id: I6b029124311f93fb3ba57efbff85bd64aadfb81a
|
|\ \ \
| |_|/
|/| | |
|