| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When multiple threads call WapPushManager functions simultaneously,
it might hit race that one thread is closing a SqliteDatabase object
while another thread is using it.
Following is an example:
Thread A Thread B
call getDatabaseLocked() ---
| |
mDatabase is NULL,so A create Database ---
| |
getDatabaseLocked() return the new ---
created Database ---
| |
--- call getDatabaseLocked() and return
--- the Database created by A
| |
Call SQLiteDatabase.close() ---
close() -> releaseReference() ---
the reference count is decreased to 0 ---
| |
--- Attempt to call any operation of Database
--- Object, but hit exception because this
--- Database Object's reference count is 0
For WapPushManager, seems it always close the database object right after
it open&query it, this is not necessary and would hit above race under multi-thread
environment.
Change-Id: I68fac046f806c8d9328fbe0d9c8a08e6bfddbef1
Signed-off-by: wangbo3 <bo.c.wang@intel.com>
Signed-off-by: chao.bi <chao.bi@intel.com>
Signed-off-by: Zhiquan Liu <zhiquan.liu@intel.com>
|
| |
|
|
|
|
|
|
|
| |
Bug 17969135
Use query (instead of rawQuery) and pass in arguments instead of building
the query with a giant string. Add a unit test that fails with the old
code but passes with the new code.
Change-Id: Id04a1db6fb95fcd923e1f36f5ab3b94402590918
|
| |
|
|
| |
Change-Id: I80204a2f3dc57cac875abeab390bb9db7a636ff7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These have been created to reduce the size and complexity
of frameworks/base.
mms-common was created by moving all of
frameworks/base/core/java/com/google/android/mms
to:
frameworks/opt/mms
telephony-common was created by moving some of
frameworks/base/telephony
to:
frameworks/opt/telephony
Change-Id: If6cb3c6ff952767fc10210f923dc0e4b343cd4ad
|
| |
|
|
|
|
| |
since before 1.0.
Change-Id: Ic2e8fa68797ea9d486f4117f3d82c98233cdab1e
|
|
|
The WAPPushManager is a new, optional service for handling WAP Push
over SMS messages. This service allows a carrier to designate a high
priority handler for specific WAP Push over SMS messages without
affecting other WAP Push over SMS, binary SMS, or SMS text messages.
It is also optional, so that it can be configured out of the target
image resulting in no change in the WAP Push over SMS handling
behavior compared to the current AOSP.
- This patch contains the WAPPushManager itself, the associated test
code, and the modifications to telephony to use the WAPPushManager.
Change-Id: I4f7fb5b68fc666da9bdeeea525e8797ae317e4b5
|
