- 浏览: 436181 次
- 性别:
- 来自: 北京
-
文章分类
最新评论
-
weiwu83：
为什么我在手机内访问127.0.0.1访问不了呀
NanoHttpd 构建android 手机端的HttpServer -
jiae：
为啥我的插入语句乱码？ 但是可以插入数据库 然后复制你 ...
SQLite3 在应用启动时初始化数据 -
lichenxiao77：
...
android 连接远程数据库 -
林源滔：
为什么我make clobber之后第一次执行make 可以。 ...
No rule to make target `out/target/common/obj/JAVA_LIBRARIES/bouncycastle_in -
cn23snyga：
new String(str.getBytes("I ...
android 平台上SQLite3中文乱码 --我的小bug
发送短信：radio.log
关键字 ：SEND_SMS
发送：（包括一条成功的和一条失败的）
11-27 14:50:11.751 D/AT ( 100): Channel3: AT< +CSQ: 12,99
11-27 14:50:11.751 D/RILC ( 100): [UNSL]< UNSOL_SIGNAL_STRENGTH {[ 12 99]}
11-27 14:50:11.751 V/RILJ ( 380): [1][UNSL]< [1]UNSOL_SIGNAL_STRENGTH {12, 99, 0, 0, 0, 0, 0}
11-27 14:50:15.131 D/SMS ( 380): SMS send size=2time=1353999015143
11-27 14:50:15.131 D/RILJ ( 380): [1][0774]> SEND_SMS
11-27 14:50:15.141 I/RILC ( 100): enter processCommandsCallback
11-27 14:50:15.141 D/RILC ( 100): PCB request code 25 token 774
11-27 14:50:15.141 D/RILC ( 100): [0774]> SEND_SMS ((null),110005810180f60008ff085929592975314e8e)
11-27 14:50:15.141 D/RIL ( 100): onRequest: SEND_SMS sState=4
11-27 14:50:15.141 D/RIL ( 100): channel4 state: '0'
11-27 14:50:15.141 D/RIL ( 100): get Channel ID '4'
11-27 14:50:15.141 D/AT ( 100): Channel4: AT> AT+CMGS=19
11-27 14:50:15.161 D/AT ( 100): Channel4: AT< >
11-27 14:50:15.161 D/AT ( 100): AT> 00110005810180f60008ff085929592975314e8e^Z
11-27 14:50:15.311 D/AT ( 100): Channel3: AT< +CSQ: 12,99
11-27 14:50:15.311 D/RILC ( 100): [UNSL]< UNSOL_SIGNAL_STRENGTH {[ 12 99]}
11-27 14:50:15.311 V/RILJ ( 380): [1][UNSL]< [1]UNSOL_SIGNAL_STRENGTH {12, 99, 0, 0, 0, 0, 0}
11-27 14:50:16.581 D/AT ( 100): Channel4: AT< +CMGS: 197
11-27 14:50:16.581 D/AT ( 100): Channel4: AT< OK
11-27 14:50:16.581 E/RILC ( 100): Inside responseSMS
11-27 14:50:16.581 D/RILC ( 100): [0774]< SEND_SMS {197,(null),0}
11-27 14:50:16.581 D/RIL ( 100): put Channel ID '4'
11-27 14:50:16.581 I/RILC ( 100): -->SmsDispatch [130] free one command
11-27 14:50:16.581 D/RILJ ( 380): [1][0774]< SEND_SMS { messageRef = 197, errorCode = 0, ackPdu = null}
11-27 14:50:16.581 D/RILJ ( 380): [1]SprdRIL:processSolicited: [0774]< send result: 2
11-27 14:50:16.581 D/SMS ( 380): SMS send complete. Broadcasting intent: PendingIntent{4063df28: android.os.BinderProxy@4058a610}
11-27 14:50:16.801 D/SMS ( 380): SMS send size=3time=1353999016809
11-27 14:50:16.821 D/RILJ ( 380): [1][0775]> SEND_SMS
11-27 14:50:16.841 I/RILC ( 100): enter processCommandsCallback
11-27 14:50:16.841 D/RILC ( 100): PCB request code 25 token 775
11-27 14:50:16.841 D/RILC ( 100): [0775]> SEND_SMS ((null),1100048100680008ff085929592975314e8e)
11-27 14:50:16.841 D/RIL ( 100): onRequest: SEND_SMS sState=4
11-27 14:50:16.841 D/RIL ( 100): channel4 state: '0'
11-27 14:50:16.841 D/RIL ( 100): get Channel ID '4'
11-27 14:50:16.841 D/AT ( 100): Channel4: AT> AT+CMGS=18
11-27 14:50:16.861 D/AT ( 100): Channel4: AT< >
11-27 14:50:16.861 D/AT ( 100): AT> 001100048100680008ff085929592975314e8e^Z
11-27 14:50:17.121 D/AT ( 100): Channel3: AT< +CMT: ,142
11-27 14:50:17.121 D/AT ( 100): Channel3: AT< 0891683108100005F00405A10180F60008211172410561237E60A8597DFF0C6211662F673A56684EBA5C0F0065FF0C5E0C671B80FD4E3A60A889E37B5479FB52A84E1A52A176F85173768495EE9898FF0C5EFA8BAE60A85C0695EE9898660E786E30017B80531663D095EE300260A8621653EF4EE556DE590D201C00310030003000380036201D8FDB516577ED4FE184254E1A53853002
11-27 14:50:17.121 D/RILC ( 100): [UNSL]< UNSOL_RESPONSE_NEW_SMS {0891683108100005F00405A10180F60008211172410561237E60A8597DFF0C6211662F673A56684EBA5C0F0065FF0C5E0C671B80FD4E3A60A889E37B5479FB52A84E1A52A176F85173768495EE9898FF0C5EFA8BAE60A85C0695EE9898660E786E30017B80531663D095EE300260A8621653EF4EE556DE590D201C00310030003000380036201D8FDB516577ED4FE184254E1A53853002}
11-27 14:50:17.121 D/RILJ ( 380): [1][UNSL]< [1]UNSOL_RESPONSE_NEW_SMS
11-27 14:50:17.121 D/GSM ( 380): SMS parsePdu
11-27 14:50:17.121 D/GSM ( 380): SMS getSCAddress
11-27 14:50:17.121 D/GSM ( 380): SMS SC address: +8613800100500
11-27 14:50:17.121 D/GSM ( 380): SMS SC timestamp: 1353999016000
11-27 14:50:17.121 D/SMS ( 380): New SMS Message Received
11-27 14:50:17.131 D/GSM ( 376): SMS parsePdu
11-27 14:50:17.131 D/GSM ( 376): SMS getSCAddress
11-27 14:50:17.161 D/GSM ( 376): SMS SC address: +8613800100500
11-27 14:50:17.161 D/GSM ( 376): SMS SC timestamp: 1353999016000
11-27 14:50:17.261 D/GSM ( 737): SMS parsePdu
11-27 14:50:17.261 D/GSM ( 737): SMS getSCAddress
11-27 14:50:17.261 D/GSM ( 737): SMS SC address: +8613800100500
11-27 14:50:17.271 D/GSM ( 737): SMS SC timestamp: 1353999016000
11-27 14:50:17.321 D/AT ( 100): Channel4: AT< +CMS ERROR: 313
11-27 14:50:17.321 D/RILC ( 100): [0775]< SEND_SMS fails by E_SMS_SEND_FAIL_RETRY
11-27 14:50:17.321 D/RIL ( 100): put Channel ID '4'
11-27 14:50:17.321 I/RILC ( 100): -->SmsDispatch [130] free one command
11-27 14:50:17.321 D/RILJ ( 380): [0775]< SEND_SMS error: com.android.internal.telephony.CommandException: SMS_FAIL_RETRY
11-27 14:50:17.321 D/SMS ( 380): SMS send failed
11-27 14:50:17.321 D/SMS ( 380): sms.send.retry.time:3
11-27 14:50:17.571 D/GSM ( 376): SMS parsePdu
11-27 14:50:17.571 D/GSM ( 376): SMS getSCAddress
11-27 14:50:17.571 D/GSM ( 376): SMS SC address: +8613800100500
11-27 14:50:17.571 D/GSM ( 376): SMS SC timestamp: 1353999016000
11-27 14:50:17.611 D/GSM ( 709): SMS parsePdu
11-27 14:50:17.611 D/GSM ( 709): SMS getSCAddress
11-27 14:50:17.611 D/GSM ( 709): SMS SC address: +8613800100500
11-27 14:50:17.621 D/RILJ ( 380): [1][0776]> SMS_ACKNOWLEDGE true 0
11-27 14:50:17.621 I/RILC ( 100): enter processCommandsCallback
11-27 14:50:17.621 I/RILC ( 100): PCC alloc one command p_record
11-27 14:50:17.621 D/RILC ( 100): PCB request code 37 token 776
11-27 14:50:17.621 D/RILC ( 100): [0776]> SMS_ACKNOWLEDGE (1,0)
11-27 14:50:17.621 D/RIL ( 100): onRequest: SMS_ACKNOWLEDGE sState=4
11-27 14:50:17.621 D/RIL ( 100): channel4 state: '0'
11-27 14:50:17.621 D/RIL ( 100): get Channel ID '4'
11-27 14:50:17.621 D/AT ( 100): Channel4: AT> AT+CNMA=1
11-27 14:50:17.631 D/GSM ( 709): SMS SC timestamp: 1353999016000
11-27 14:50:17.641 D/AT ( 100): Channel4: AT< OK
11-27 14:50:17.641 D/RILC ( 100): [0776]< SMS_ACKNOWLEDGE
11-27 14:50:17.641 D/RIL ( 100): put Channel ID '4'
11-27 14:50:17.641 I/RILC ( 100): -->CommandThread [504] free one command
11-27 14:50:17.641 D/RILJ ( 380): [1][0776]< SMS_ACKNOWLEDGE
11-27 14:50:19.321 D/RILJ ( 380): [1][0777]> SEND_SMS
11-27 14:50:19.321 I/RILC ( 100): enter processCommandsCallback
11-27 14:50:19.321 D/RILC ( 100): PCB request code 25 token 777
11-27 14:50:19.321 D/RILC ( 100): [0777]> SEND_SMS ((null),1100048100680008ff085929592975314e8e)
11-27 14:50:19.321 D/RIL ( 100): onRequest: SEND_SMS sState=4
11-27 14:50:19.321 D/RIL ( 100): channel4 state: '0'
11-27 14:50:19.321 D/RIL ( 100): get Channel ID '4'
11-27 14:50:19.321 D/AT ( 100): Channel4: AT> AT+CMGS=18
11-27 14:50:19.341 D/AT ( 100): Channel4: AT< >
11-27 14:50:19.341 D/AT ( 100): AT> 001100048100680008ff085929592975314e8e^Z
11-27 14:50:19.671 D/AT ( 100): Channel4: AT< +CMS ERROR: 313
11-27 14:50:19.671 D/RILC ( 100): [0777]< SEND_SMS fails by E_SMS_SEND_FAIL_RETRY
11-27 14:50:19.671 D/RIL ( 100): put Channel ID '4'
11-27 14:50:19.671 I/RILC ( 100): -->SmsDispatch [130] free one command
11-27 14:50:19.671 D/RILJ ( 380): [0777]< SEND_SMS error: com.android.internal.telephony.CommandException: SMS_FAIL_RETRY
11-27 14:50:19.671 D/SMS ( 380): SMS send failed
11-27 14:50:19.671 D/SMS ( 380): sms.send.retry.time:3
11-27 14:50:21.671 D/RILJ ( 380): [1][0778]> SEND_SMS
11-27 14:50:21.671 I/RILC ( 100): enter processCommandsCallback
11-27 14:50:21.671 D/RILC ( 100): PCB request code 25 token 778
11-27 14:50:21.671 D/RILC ( 100): [0778]> SEND_SMS ((null),1100048100680008ff085929592975314e8e)
11-27 14:50:21.671 D/RIL ( 100): onRequest: SEND_SMS sState=4
11-27 14:50:21.671 D/RIL ( 100): channel4 state: '0'
11-27 14:50:21.671 D/RIL ( 100): get Channel ID '4'
11-27 14:50:21.671 D/AT ( 100): Channel4: AT> AT+CMGS=18
11-27 14:50:21.691 D/AT ( 100): Channel4: AT< >
11-27 14:50:21.691 D/AT ( 100): AT> 001100048100680008ff085929592975314e8e^Z
11-27 14:50:22.011 D/AT ( 100): Channel4: AT< +CMS ERROR: 313
11-27 14:50:22.011 D/RILC ( 100): [0778]< SEND_SMS fails by E_SMS_SEND_FAIL_RETRY
11-27 14:50:22.011 D/RIL ( 100): put Channel ID '4'
11-27 14:50:22.011 I/RILC ( 100): -->SmsDispatch [130] free one command
11-27 14:50:22.011 D/RILJ ( 380): [0778]< SEND_SMS error: com.android.internal.telephony.CommandException: SMS_FAIL_RETRY
11-27 14:50:22.011 D/SMS ( 380): SMS send failed
11-27 14:50:22.011 D/SMS ( 380): sms.send.retry.time:3
11-27 14:50:24.011 D/RILJ ( 380): [1][0779]> SEND_SMS
11-27 14:50:24.011 I/RILC ( 100): enter processCommandsCallback
11-27 14:50:24.011 D/RILC ( 100): PCB request code 25 token 779
11-27 14:50:24.011 D/RILC ( 100): [0779]> SEND_SMS ((null),1100048100680008ff085929592975314e8e)
11-27 14:50:24.011 D/RIL ( 100): onRequest: SEND_SMS sState=4
11-27 14:50:24.011 D/RIL ( 100): channel4 state: '0'
11-27 14:50:24.011 D/RIL ( 100): get Channel ID '4'
11-27 14:50:24.011 D/AT ( 100): Channel4: AT> AT+CMGS=18
11-27 14:50:24.031 D/AT ( 100): Channel4: AT< >
11-27 14:50:24.031 D/AT ( 100): AT> 001100048100680008ff085929592975314e8e^Z
11-27 14:50:24.411 D/AT ( 100): Channel4: AT< +CMS ERROR: 313
11-27 14:50:24.411 D/RILC ( 100): [0779]< SEND_SMS fails by E_SMS_SEND_FAIL_RETRY
11-27 14:50:24.411 D/RIL ( 100): put Channel ID '4'
11-27 14:50:24.411 I/RILC ( 100): -->SmsDispatch [130] free one command
11-27 14:50:24.411 D/RILJ ( 380): [0779]< SEND_SMS error: com.android.internal.telephony.CommandException: SMS_FAIL_RETRY
11-27 14:50:24.411 D/SMS ( 380): SMS send failed
接收信息
D/RILC ( 141): [UNSL]< UNSOL_RESPONSE_NEW_SMS {0891683108100005F00005A10180F60008210162518313235060A8597DFF0C6211662F673A56684EBA5C0F0065FF0C53EF4EE54E3A60A863D04F9B79FB52A84E1A52A1548C670D52A165B99762768454A88BE2002C003200345C0F65F6606D501960A8768451494E34}
D/RILJ ( 374): [0][UNSL]< [0]UNSOL_RESPONSE_NEW_SMS
D/RILC ( 141): [UNSL]< UNSOL_SIGNAL_STRENGTH {[ 12 99]}
V/RILJ ( 374): [0][UNSL]< [0]UNSOL_SIGNAL_STRENGTH {12, 99, 0, 0, 0, 0, 0}
D/RILJ ( 374): [0][0356]> SMS_ACKNOWLEDGE true 0
I/RILC ( 141): enter processCommandsCallback
I/RILC ( 141): PCC alloc one command p_record
D/RILC ( 141): PCB request code 37 token 356
D/RILC ( 141): [0356]> SMS_ACKNOWLEDGE (1,0)
D/RIL ( 141): onRequest: SMS_ACKNOWLEDGE sState=4
D/RIL ( 141): channel1 state: '0'
D/RIL ( 141): get Channel ID '1'
D/RILC ( 141): C[locl]< SMS_ACKNOWLEDGE
D/RILC ( 141): function 1>>>>>
D/RIL ( 141): put Channel ID '1'
I/RILC ( 141): -->CommandThread [481] free one command
D/RILJ ( 374): [0][0356]< SMS_ACKNOWLEDGE
接收push信息：
12-07 16:08:43.227 D/AT ( 139): Channel0: AT< +CMT: ,50
12-07 16:08:43.227 D/AT ( 139): Channel0: AT< 0891683108100005F06405A12125F0000421217061802423220B05040B8423F00003300202BDE4BD93E9AA8CE6898BE69CBAE9A39EE4BFA1000101
12-07 16:08:43.227 D/RILC ( 139): [UNSL]< UNSOL_RESPONSE_NEW_SMS {0891683108100005F06405A12125F0000421217061802423220B05040B8423F00003300202BDE4BD93E9AA8CE6898BE69CBAE9A39EE4BFA1000101}
12-07 16:08:43.227 D/RILJ ( 388): [0][UNSL]< [0]UNSOL_RESPONSE_NEW_SMS
12-07 16:08:43.227 D/GSM ( 388): SMS parsePdu
12-07 16:08:43.227 D/GSM ( 388): SMS getSCAddress
12-07 16:08:43.227 D/GSM ( 388): SMS SC address: +8613800100500
12-07 16:08:43.227 D/GSM ( 388): SMS SC timestamp: 1354867722000
12-07 16:08:43.227 W/GSM ( 388): 1 - Unsupported SMS data coding scheme 4
12-07 16:08:43.227 D/GSM ( 388): z1471 septetCount = 22
12-07 16:08:43.227 D/GSM ( 388): z1472 cur = 37
12-07 16:08:43.227 D/SMS ( 388): New SMS Message Received
12-07 16:08:43.227 D/SMS ( 388): processMessagePart() msgCount2 cursorCount:1
12-07 16:08:43.238 D/SMS ( 388): pdus[0]:0891683108100005F06405A12125F00004212170618014238C0B05040B8423F00003300201320601AE02056A0045C6080C03662E31303038362E636E2F662F736A6678000103E689BEE69C8BE58F8BE38081E69FA5E5A4A9E6B094E38081E79C8BE5B08FE8AFB4E38081E79C8BE696B0E997BBE280A6E6898BE69CBAE9A39EE4BFA1EFBC8CE7AE80E58D95E4BDA0E79A84E7949FE6B4BBEFBC81E8B5B6E5BFABE4B88BE8BD
12-07 16:08:43.238 D/SMS ( 388): pdus[1]:0891683108100005F06405A12125F0000421217061802423220B05040B8423F00003300202BDE4BD93E9AA8CE6898BE69CBAE9A39EE4BFA1000101
12-07 16:08:43.268 D/GSM ( 388): SMS parsePdu
12-07 16:08:43.268 D/GSM ( 388): SMS getSCAddress
12-07 16:08:43.268 D/GSM ( 388): SMS SC address: +8613800100500
12-07 16:08:43.268 D/GSM ( 388): SMS SC timestamp: 1354867721000
12-07 16:08:43.268 W/GSM ( 388): 1 - Unsupported SMS data coding scheme 4
12-07 16:08:43.268 D/GSM ( 388): z1471 septetCount = 128
12-07 16:08:43.268 D/GSM ( 388): z1472 cur = 37
12-07 16:08:43.298 D/GSM ( 388): SMS parsePdu
12-07 16:08:43.298 D/GSM ( 388): SMS getSCAddress
12-07 16:08:43.298 D/GSM ( 388): SMS SC address: +8613800100500
12-07 16:08:43.298 D/GSM ( 388): SMS SC timestamp: 1354867722000
12-07 16:08:43.298 W/GSM ( 388): 1 - Unsupported SMS data coding scheme 4
12-07 16:08:43.298 D/GSM ( 388): z1471 septetCount = 22
12-07 16:08:43.298 D/GSM ( 388): z1472 cur = 37
12-07 16:08:43.308 D/GSM ( 386): SMS parsePdu
12-07 16:08:43.308 D/GSM ( 386): SMS getSCAddress
12-07 16:08:43.308 D/GSM ( 386): SMS SC address: +8613800100500
12-07 16:08:43.308 D/GSM ( 386): SMS SC timestamp: 1354867721000
12-07 16:08:43.308 W/GSM ( 386): 1 - Unsupported SMS data coding scheme 4
12-07 16:08:43.308 D/GSM ( 386): z1471 septetCount = 128
12-07 16:08:43.308 D/GSM ( 386): z1472 cur = 37
12-07 16:08:43.318 D/GSM ( 386): SMS parsePdu
12-07 16:08:43.318 D/GSM ( 386): SMS getSCAddress
12-07 16:08:43.318 D/GSM ( 386): SMS SC address: +8613800100500
12-07 16:08:43.318 D/GSM ( 386): SMS SC timestamp: 1354867722000
12-07 16:08:43.318 W/GSM ( 386): 1 - Unsupported SMS data coding scheme 4
12-07 16:08:43.318 D/GSM ( 386): z1471 septetCount = 22
12-07 16:08:43.318 D/GSM ( 386): z1472 cur = 37
12-07 16:08:43.388 D/RILJ ( 388): [0][0350]> SMS_ACKNOWLEDGE true 0
12-07 16:08:43.388 I/RILC ( 139): enter processCommandsCallback
12-07 16:08:43.388 I/RILC ( 139): PCC alloc one command p_record
12-07 16:08:43.388 D/RILC ( 139): PCB request code 37 token 350
12-07 16:08:43.388 D/RILC ( 139): [0350]> SMS_ACKNOWLEDGE (1,0)
12-07 16:08:43.388 D/RIL ( 139): onRequest: SMS_ACKNOWLEDGE sState=4
12-07 16:08:43.388 D/RIL ( 139): channel1 state: '0'
12-07 16:08:43.388 D/RIL ( 139): get Channel ID '1'
12-07 16:08:43.388 D/AT ( 139): Channel1: AT> AT+CNMA=1
12-07 16:08:43.408 D/AT ( 139): Channel1: AT< OK
12-07 16:08:43.408 D/RILC ( 139): [0350]< SMS_ACKNOWLEDGE
12-07 16:08:43.408 D/RIL ( 139): put Channel ID '1'
12-07 16:08:43.408 I/RILC ( 139): -->CommandThread [529] free one command
12-07 16:08:43.408 D/RILJ ( 388): [0][0350]< SMS_ACKNOWLEDGE
12-07 16:08:43.538 D/GSM ( 1005): SMS parsePdu
12-07 16:08:43.538 D/GSM ( 1005): SMS getSCAddress
12-07 16:08:43.538 D/GSM ( 1005): SMS SC address: +8613800100500
12-07 16:08:43.568 D/GSM ( 1005): SMS SC timestamp: 1354867721000
12-07 16:08:43.568 W/GSM ( 1005): 1 - Unsupported SMS data coding scheme 4
12-07 16:08:43.568 D/GSM ( 1005): z1471 septetCount = 128
12-07 16:08:43.568 D/GSM ( 1005): z1472 cur = 37
12-07 16:08:43.568 D/GSM ( 1005): SMS parsePdu
12-07 16:08:43.568 D/GSM ( 1005): SMS getSCAddress
12-07 16:08:43.568 D/GSM ( 1005): SMS SC address: +8613800100500
12-07 16:08:43.588 D/GSM ( 1005): SMS SC timestamp: 1354867722000
12-07 16:08:43.588 W/GSM ( 1005): 1 - Unsupported SMS data coding scheme 4
12-07 16:08:43.588 D/GSM ( 1005): z1471 septetCount = 22
12-07 16:08:43.588 D/GSM ( 1005): z1472 cur = 37
12-07 16:08:45.168 D/AT ( 139): Channel0: AT< +CSQ: 9,99
12-07 16:08:45.168 D/RILC ( 139): [UNSL]< UNSOL_SIGNAL_STRENGTH {[ 9 99]}
12-07 16:08:45.168 V/RILJ ( 388): [0][UNSL]< [0]UNSOL_SIGNAL_STRENGTH {9, 99, 0, 0, 0, 0, 0}
发表评论
-
Android.mk文件解析
2016-01-27 14:01 939以 tools/tradefederation/Androi ... -
NanoHttpd 构建android 手机端的HttpServer
2015-10-20 16:24 2948NanoHttpd是Github上的一个开源项目, 通过下载 ... -
permission denial : android.permission.INTERACT_ACROSS_USERS_FULL
2015-08-05 16:50 5046在android5.0上运行 Runtime.getRun ... -
android getprop() 和 java System.getPropety()
2015-06-04 14:39 63591 System.getPropety()是java中的方 ... -
android cts测试相关
2015-05-27 17:38 0example: -
android uiautomator 相关
2015-05-15 16:53 1695１ Runtime.getRuntime().exec 启 ... -
android UI test Espresso
2015-04-10 18:31 1204google android UI测试工具 espresso ... -
android 安全（转）
2014-12-26 12:37 722一 如何不被反编译解析１防止反编译工具的反编译 查看 ... -
nexus related
2014-12-17 15:29 7411 nexus drivers https://deve ... -
git related
2014-12-17 15:24 9671 see all detailed git info ... -
ubuntu android studio 配置和使用
2014-12-10 17:34 3627Ubuntu 64位，Android studio 的安装， ... -
eclipse+ADT+android配置相关
2014-12-05 16:40 14531 eclipse 过旧时，ant 运行不了，会报sdk. ... -
anroid 开发小知识点
2014-10-09 09:52 8241 1）代码 获取APK安装路径和包名 L ... -
androird 内存泄露 浅析
2013-06-19 17:52 1449主要是记录工作中出 ... -
mms 相关链接
2013-03-15 13:53 1396http://blog.chinaunix.net/uid ... -
No rule to make target `out/target/common/obj/JAVA_LIBRARIES/bouncycastle_in
2013-01-31 10:19 15781在android4.0源码中，mm编译apk时出现下面的错 ... -
java层堆栈调用的打印
2012-12-26 15:14 44721. 在指定的函数内打印相关java调用 Log.d ... -
mms 数据包相关
2012-11-26 14:51 22721 抓包 adb shell tcpdump -i any ... -
sms AT指令返回错误代码： CMS errors & CME errors 的区别！
2012-10-26 18:35 12027CMS的是短信中心的返回错误。 CME 是设备返 ... -
SQLite --函数
2012-09-03 18:22 1988一、日期和时间函数：原文地址SQLite主要支持以下 ...
相关推荐
在Android平台上，发送短信和保存短信记录是两个重要的功能，它们涉及到系统级别的权限以及与SMS相关的API交互。本文将深入探讨这两个主题，并提供相应的代码示例。 ### 1. Android发送短信 在Android中，发送短信...
Log.d("Sms", "短信发送成功"); break; case SmsManager.RESULT_ERROR_GENERIC_FAILURE: Log.e("Sms", "通用错误"); break; case SmsManager.RESULT_ERROR_NO_SERVICE: Log.e("Sms", "无服务"); break; ...
Log.d("SmsBroadcastReceiver", "短信发送成功"); // 在这里执行成功的操作 break; case SmsManager.RESULT_ERROR_GENERIC_FAILURE: Log.e("SmsBroadcastReceiver", "短信发送失败：通用错误"); // 在这里处理...
Log.i("SMS", "短信发送成功"); break; case SmsManager.RESULT_ERROR_GENERIC_FAILURE: Log.e("SMS", "通用错误"); break; case SmsManager.RESULT_ERROR_NO_SERVICE: Log.e("SMS", "无服务"); break; ...
1 打开radio LOG文件夹：\mobilelog\APLog 2 打开radio_log 3 查找 +CMT 4 将后面的一长串数字复制。例如：0891683110304105F0240D91688111167112F0000841603031543223089694819C81EA5DF1 5 双击执行这个html 文件。...
在Android系统中，"rilj"（Radio Interface Layer, 无线接口层）是与设备的基带处理器通信的关键组件，负责处理所有与无线网络相关的任务，包括电话、短信、数据连接等。"sms"（Short Message Service，短信服务）则...
一个位置区可以包含多个小区，且通常与一个或多个RNC（Radio Network Controller，无线网络控制器）相关联，但仅归属于一个MSC/VLR（Visitor Location Register，访问位置寄存器）。 5. **小区**：GSM网络中的最小...
7. **RIL (Radio Interface Layer)**： RIL是Android与底层通信硬件交互的接口层。虽然开发者通常不直接操作RIL，但理解它的工作原理有助于更好地理解Android Telephony的底层机制。 8. **Network Selection**： ...
- 呼叫日志（Call Log） - 扫描列表（Scan List） - 设置（Settings） - 蜂鸣音（Beep） - 背光（Back Light） - 背光时间（Light Time） - 频道名称（Ch. Name） - 键盘锁（Key Lock） - 关机（Power Off...
进行电话操作需要特定的权限，例如CALL_PHONE、READ_PHONE_STATE和WRITE_CALL_LOG。应用程序必须在Manifest文件中声明这些权限才能访问电话服务。 6. 网络切换： ServiceStateTracker监控网络状态变化，当用户在...
在Android系统中，RIL（Radio Interface Layer）是操作系统与无线网络硬件之间的接口层，它负责处理各种无线网络相关的操作，如通话、数据连接、短信等。本文将深入解析Android 4.4版本中RIL如何接收短信的流程，...
- **短信(SMS)**: 支持短信的编辑、发送、接收、转发及存储。 - **彩信(MMS)**: 同样支持编辑、发送、接收、转发、存储和配置彩信。 **1.1.3 电话本** - **名片管理**: 支持创建、修改、复制、转移、删除联系人信息...
� 基于 QEMU 开发的模拟器调试手段不十分丰富，只支持通话、ＳＭＳ等，速度慢。 � 暂不具备 Push Mail 和 Office(DataViz 、 QuickOffice 计划近期推出 ) 功能，目前主要面向的是普通消费 者 用户，对商业用户支持...