| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ibb5f4a6e8756b393f9d4f5ef5060aaf60bcaeade
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
data by default.
This was imported to Replicant 2.3 from commit:
https://gitorious.org/replicant/android_frameworks_base/commit/0817e4634116b7c8e574f9b72693c2b50098a508
|
| |
|
|
|
|
|
|
|
| |
Timestamp doesn't contain date info, therefore we need to construct it
and adjust it if daylight savings applies.
Change-Id: Ic6b5b3e2d773f637a99a80ef0998ee4f9989a8eb
|
|
|
|
|
| |
This also disables the SIM PIN entry screen, which is an unwanted
behaviour change that should be avoided before release.
|
|
|
|
|
|
| |
Move Simplified Chinese about shutdown opitions into strings.xml
Change-Id: I2894b19bd573bea54ae4038f46a1e0cb5437d809
|
| |
|
|
|
|
|
|
|
| |
default to 60 secs unless overridden by server's session-id response.
Change-Id: I7c3aff5b787dbb57cc0dccf9db3c75e5cf7e778c
related-to-bug: 5562303
|
|
|
|
|
|
| |
String unification, added messages for fingerprint usage.
Change-Id: I7e04c4db734ceec2a7ec31c1f8f4cb985825783a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unlike the other buttons, the lockscreen disable button keeps the state
(disabled/enabled) in it instead of just displaying it, so in order to
make it reliable, a few things needed to be fixed:
- The actual lockscreen blocker was a member variable while the state
information was static. This could lead to the two variables getting
out of sync.
- On orientation or theme change, all widgets were destroyed and
recreated. If that happened while the lockscreen was disabled, the
blocker instance was lost, thus, there was no way to enable the
lockscreen again. Fix that by only recreating the views, not the whole
widgets.
- The lockscreen disable state wasn't stored persistently, thus didn't
survive a reboot.
Fixes http://code.google.com/p/cyanogenmod/issues/detail?id=2978.
Change-Id: I6f619740659cfedec3a3c9517fb55275f601d792
|
|
|
|
| |
Change-Id: I466f623a9f6066228d0749be0b3afeec91502197
|
| |
|
|
|
|
| |
The settings app widget expects that to be done for working properly.
|
| |
|
|
|
|
|
| |
fixes SMS troubles for Chinese users
0x0b was not a Class 3 specification as the bit 4 was set to 0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the querying thread was faster than the DNS resolving thread startup,
resolving would crash with the following stacktrace:
FATAL EXCEPTION: WebViewCoreThread
E/AndroidRuntime(7160): java.lang.NullPointerException
E/AndroidRuntime(7160): at android.webkit.DnsResolver.resolveDnsForHostMap(DnsResolver.java:187)
E/AndroidRuntime(7160): at android.webkit.BrowserFrame.startDnsPrefetch(BrowserFrame.java:248)
E/AndroidRuntime(7160): at android.webkit.WebViewCore$EventHub$1.handleMessage(WebViewCore.java:1400)
E/AndroidRuntime(7160): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(7160): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime(7160): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:645)
E/AndroidRuntime(7160): at java.lang.Thread.run(Thread.java:1019)
|
|
|
|
| |
Fixes http://code.google.com/p/cyanogenmod/issues/detail?id=5290.
|
| |
|
|
|
|
|
|
|
|
|
| |
Fixes disappearing widgets on theme change due to clashing accesses to
the static map by the old and the new widget instance.
Also convert static to member variables at a few other places.
Change-Id: I42b4ad02c4eb8b57a2f4cf51a31148c4b0546b81
|
|
|
|
|
|
|
|
|
|
| |
Backported from CM9:
Clean up existing widgets before creating new ones to prevent
dangling references to the previous dialog's context, which
broke the insertion of a new widget set into recently created
ExpandedDialog views.
Change-Id: I16a3bab85bcc07dcdb3b189809f5dae528eff66a
|
|
|
|
|
|
|
|
| |
themes."
This reverts commit 42234e0a683b180b7be418d9f491d5c7dca23388.
Change-Id: I6ee2f3f57c8608a82896c14d6e168c6c1875b7a0
|
| |
|
|
|
|
| |
they were registered before.
|
|
|
|
|
|
| |
All dialogs and notifications should be covered now.
Change-Id: If93f81991361165a00b5b1b03ffc323e3ab42c0b
|
|
|
|
|
|
| |
notification patch (#11318)
Change-Id: I783b438449a63134ba0f6ae332dd7dc3ddbd5c81
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is an issue where users whose passwords are greater than 8 chars and
have quick unlock enabled will be unable to unlock their lockscreen.
This is due to the logic evaluating anything beyond 3chars as a password attempt.
This change modifies the quick unlock behavior so that when typing the password,
each character is considered an attempt, however if incorrect, is not reported as a failed attempt.
Only when the user presses enter is it considered an "explicit" attempt and a failed attempt is reported.
Change-Id: I02d436184d63c6880c7b1dc6b4b6119fba76e9a7
|
|
|
|
|
|
|
|
|
|
|
| |
As the theme engine works by replacing resources while loading the APK,
framework UI couldn't be themed so far. Workaround that by manually
creating a com.android.systemui package context and using that for
showing the UI. This attempt is a bit hacky, but should be safe as
a) systemui should always be present
b) if it isn't, we fall back to no theming
Change-Id: I644e2e8d7d4abf07bae639b606197d691f16adac
|
|
|
|
| |
This reverts commit e952e69b3177d3324696901a644160d4b24423be.
|
|
|
|
|
|
| |
It was only working for fingerprint and pattern lockscreens.
Change-Id: Ib4d4d28f80256fbe669aeb5681ef6056b8f5f3d4
|
|
|
|
| |
Change-Id: I8ad4ce8652325e2e10dd529a934c8928ee0b149c
|
|
|
|
|
|
|
|
|
|
|
| |
This normally shouldn't happen, but experience has shown that there are
some rare corner cases where it indeed happens. The exact conditions are
unclear, but it's likely related to an ACTION_CANCEL event being sent
out before the ACTION_UP event.
In order to not crash in weird, hard-to-debug corner cases, just check
whether we actually have an item to process.
This fixes http://code.google.com/p/cyanogenmod/issues/detail?id=4985.
|
|\
| |
| |
| | |
methods." into gb-release-7.2
|
| | |
|
|/ |
|
|\
| |
| |
| | |
gingerbread
|
| |
| |
| |
| | |
Change-Id: I8179aadaf78a3d492524c9aeadce09b32ae992b6
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Iedf357afd93611bf6e33f6513c69cdd914b625a6
|
|\ \ \
| | | |
| | | |
| | | | |
gingerbread
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Battery charging should be detected via the status intent extra
instead of merely checking to see if the phone is plugged.
See r.cyanogenmod.com/7986
Change-Id: I39f6caf6183a866d6061b07e0f62c21a4df71aef
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The RIL of those devices signals incoming forwarded calls incorrectly.
Instead of sending a supplementary service notification with type = MT
and code2 = 0, it sends code2 = 10.
This RIL class works around that.
Change-Id: I8654663daab084c486fe787e50b9dde01e67895f
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
telephony: Display Supplementary Service Notifications.
CallManager registers for supplementary service notifications
with Phone to notify Phone App.
Change-Id: I20c1c908200a9a2ced017e14821cb65249521708
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds a collection of CDMA device fixes to SamsungRIL. They include:
- Overriding ERROR_UNSPECIFIED fail cause with NORMAL_CLEARING, to prevent
far-end hangups from displaying the "Call Lost" dialog.
- Adding, and ignoring the RIL_UNSOL_GPS_NOTI request, which is also
ignored in the TW RIL, to keep the radio log clean of exceptions when the
GPS is active.
- Workaround for Samsung CDMA "ring of death" bug. See source comments for
details on this problem.
Change-Id: Ida4797718ad3463d073a6fc27246cc916526d487
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If users delete their fingerprint database and proceed to lock the
screen, let them in so they can configure another lock method.
Also fixes a typo
Change-Id: I006a86e5e0f72a3d08d5c0b3a96cc659fecbeede
|
|\ \ \ \ |
|