以下代碼的修改是針對android平臺研發(fā)的,另外如果沒有系統(tǒng)源碼的情況下,通過逆向修改ROM中的對應(yīng)文件,也是可以做到的。 之所以有這樣需求,是因為假如是你自己的ROM,需要對自己的某個APP授予SMS寫入權(quán)限,可以通過修改如下代碼中的OTHERSMS_PACKAGE_NAME,換成你自己APP的package name就可以了。 如果類似QQ通訊錄這種應(yīng)用,在可以獲取ROOT 的權(quán)限下,能不能做到呢,我認為也是可以實現(xiàn)的,可以在內(nèi)存中注入相關(guān)的代碼片段,嘗試分析了一下QQ通訊錄,發(fā)現(xiàn)它里面在獲取ROOT后,是有注入操作的,但不是實現(xiàn)下面的功能,QQ通訊錄當前的版本在Android 4.4 (KitKat)上,仍然存在問題。 不多說了,直接上代碼,自己研究嘍~ - diff --git a/src/java/com/android/internal/telephony/SmsApplication.java b/src/java/com/android/internal/telephony/SmsApplication.java
- index 0582df8..39dee4c 100644
- --- a/src/java/com/android/internal/telephony/SmsApplication.java
- +++ b/src/java/com/android/internal/telephony/SmsApplication.java
- @@ -49,6 +49,7 @@ public final class SmsApplication {
- static final String LOG_TAG = "SmsApplication";
- private static final String PHONE_PACKAGE_NAME = "com.android.phone";
- private static final String BLUETOOTH_PACKAGE_NAME = "com.android.bluetooth";
- + private static final String OTHERSMS_PACKAGE_NAME = "com.example.demo";
-
- private static final String SCHEME_SMS = "sms";
- private static final String SCHEME_SMSTO = "smsto";
- @@ -357,6 +358,20 @@ public final class SmsApplication {
- // No BT app on this device
- Rlog.e(LOG_TAG, "Bluetooth package not found: " + BLUETOOTH_PACKAGE_NAME);
- }
- +
- + try {
- + PackageInfo info = packageManager.getPackageInfo(OTHERSMS_PACKAGE_NAME, 0);
- + int mode = appOps.checkOp(AppOpsManager.OP_WRITE_SMS, info.applicationInfo.uid,
- + OTHERSMS_PACKAGE_NAME);
- + if (mode != AppOpsManager.MODE_ALLOWED) {
- + Rlog.e(LOG_TAG, OTHERSMS_PACKAGE_NAME + " lost OP_WRITE_SMS: (fixing)");
- + appOps.setMode(AppOpsManager.OP_WRITE_SMS, info.applicationInfo.uid,
- + OTHERSMS_PACKAGE_NAME, AppOpsManager.MODE_ALLOWED);
- + }
- + } catch (NameNotFoundException e) {
- + // No BT app on this device
- + Rlog.e(LOG_TAG, "3rd sms package not found: " + OTHERSMS_PACKAGE_NAME);
- + }
- }
- }
- return applicationData;
復(fù)制代碼
|