Split SMSes with 4.4.2

Anmeldedatum: 29.12.2014 Beiträge: 5

Hi,

Been using MPE for ages (since I had a Galaxy S2) and loving it. Just got a new Huawei P7-L10 with 4.4.2 and have noticed that the SMS send feature is storing long messages in the phone as two messages.

The receiver gets the message 'properly' i.e. as one message, but when viewed in either 'messaging' on the phone or through the MPE messages section the sent message is shown as multiple messages split at 154 characters.

I know that KitKat has munged the SMS API, I used AppOps to enable 'WriteSMS' for the MPE client but it it showing the feature as 'never used'

The same version of MPE works fine on my S3 which is running the latest provided 4.3.

Log segment:

Code:

18:59:51.94 RunADBCommand: start-server
18:59:51.95 ADB CommandResponse:
18:59:51.95 RunADBCommand: devices
18:59:51.97 ADB CommandResponse: List of devices attached
7N2NEF1465017178 device
18:59:51.97 RunADBCommand: -s "7N2NEF1465017178" forward tcp:5210 tcp:5210
18:59:51.98 ADB CommandResponse:
18:59:51.98 Try connecting to 127.0.0.1...
18:59:51.98 Socket closed
18:59:51.98 RunADBCommand: -s "7N2NEF1465017178" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
18:59:52.87 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
18:59:53.02 Try launch USB connection
18:59:53.13 Connect to Android OK (127.0.0.1)
18:59:53.13 Settimeout: RT=2000 WT=500
18:59:53.13 bOpened=True
18:59:53.13 [TX]: AT+CGSN
18:59:53.15 [RX]: AT+CGSN
18:59:53.15 [RX]: 357456044255555
18:59:53.15 [RX]: OK
18:59:53.15 Settimeout: RT=15000 WT=1000
18:59:53.15 [TX]: AT*PIN=22770d5b39d401b9e43c9f5f31adfe30
18:59:53.15 [RX]: AT*PIN=22770d5b39d401b9e43c9f5f31adfe30
18:59:53.15 [RX]: *PIN: ACCESS OK,10
18:59:53.15 [RX]: OK
18:59:53.15 [TX]: ATI
18:59:53.16 [RX]: ATI
18:59:53.16 [RX]: HUAWEI P7-L10
18:59:53.16 [RX]: OK
18:59:53.16 [TX]: AT*APPVERSION=1.8.6
18:59:53.16 [RX]: AT*APPVERSION=1.8.6
18:59:53.16 [RX]: 19,1.0.34
18:59:53.16 [RX]: OK
18:59:53.16 [TX]: AT+CSCS="UTF-8"
18:59:53.17 [RX]: AT+CSCS="UTF-8"
18:59:53.17 [RX]: OK
18:59:53.17 [TX]: AT*ECAM=1
18:59:53.17 [RX]: AT*ECAM=1
18:59:53.17 [RX]: OK
18:59:53.17 [TX]: AT+CBC
18:59:53.17 [RX]: AT+CBC
18:59:53.17 [RX]: +CBC: 1,100
18:59:53.18 [RX]: OK
18:59:53.18 [TX]: AT+CSQ
18:59:53.18 [RX]: AT+CSQ
18:59:53.18 [RX]: +CSQ: 0,99
18:59:53.18 [RX]: OK
18:59:53.18 Alle Verbindungsaktionen beendet
18:59:53.18 [TX]: AT*SOPS
18:59:53.19 [RX]: AT*SOPS
18:59:53.19 [RX]: *SOPS: GLOBE,51502,ph
18:59:53.19 [RX]: OK
18:59:53.21 [TX]: AT+CMGS=?
18:59:53.21 [RX]: AT+CMGS=?
18:59:53.21 [RX]: +CMGS: TXTv2,PING
18:59:53.21 [RX]: OK
18:59:53.21 Settimeout: RT=30000 WT=1000
18:59:53.21 Settimeout: RT=40000 WT=1000
18:59:53.22 [TX]: AT+CMGS=+XXXXXXXXXXXX,TestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTest,0,1
18:59:53.22 [RX]: AT+CMGS=+XXXXXXXXXXXX,TestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTest,0,1
18:59:55.61 [RX]: +CMGS: 0
18:59:57.21 [RX]: +CMGS: 0
18:59:57.22 [RX]: +CMGW: 60
18:59:57.22 [RX]: OK
18:59:57.23 Settimeout: RT=15000 WT=1000
18:59:57.23 [TX]: AT+CMGR=60
18:59:57.24 [RX]: AT+CMGR=60
18:59:57.26 [RX]: +CMGR: 60,3,TXT,20141229T185954,+XXXXXXXXXXXX,estTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTest
18:59:57.26 [RX]: OK
18:59:57.26 Settimeout: RT=10000 WT=1000
18:59:57.28 SaveDatafile: SMS.dat (11068 Bytes)
18:59:57.28 SMS-Datenbank gespeichert. Dauer:16 SMS:58
18:59:57.29 NewMessage Window SaveWindowRect: L=198 T=198 W=463 H=336
18:59:57.29 Remove SMSWindow from Collection...
18:59:57.29 fNewSMS Unload finished
18:59:57.30 ShowBalloontip: MyPhoneExplorer - Message(s) sent successfully!
18:59:57.31 Unload fSMSProgress
18:59:58.21 [RX]: +CMTI: "ME",61
18:59:58.71 Settimeout: RT=45000 WT=1000
18:59:58.71 [TX]: AT+CPMS="ME","ME"
18:59:58.73 [RX]: AT+CPMS="ME","ME"
18:59:58.73 [RX]: +CPMS: 61,20000,61,20000
18:59:58.73 [RX]: OK
18:59:58.73 Settimeout: RT=15000 WT=1000
18:59:58.73 [TX]: AT+CMGR=61
18:59:58.73 [RX]: AT+CMGR=61
18:59:58.75 [RX]: +CMGR: 61,0,TXT,20141229T185958,+XXXXXXXXXXXX,TestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTest
18:59:58.75 [RX]: OK
18:59:58.77 SaveDatafile: SMS.dat (11676 Bytes)
18:59:58.77 SMS-Datenbank gespeichert. Dauer:0 SMS:59
18:59:58.77 Incoming SMS, Database saved
18:59:58.77 ShowBalloontip: New message from: XXXXXXX - TestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTest
18:59:58.81 Incoming SMS, GotNewMessage handled
18:59:58.81 Incoming SMS, Function End
19:00:06.19 Settimeout: RT=3500 WT=800

[/code]

Anmeldedatum: 17.06.2012 Beiträge: 3

I've the same problem with my Samsung S 5 - Android ver. 4.4.2

Anmeldedatum: 29.12.2014 Beiträge: 5

As per this post:

http://www.fjsoft.at/forum/viewtopic.php?p=108297#108297

This is a known issue with KitKat which I thought it might be.

Question: MPE client checks phone OS version and enables the 'switch SMS application' dialog if the version is KitKat.

Is it possible to change the MPE client so that instead of just checking for KitKat version it checks first to see if the AppOps SMSWrite permission is set? That way if we use AppOps to enable SMSWrite for the MPE Client it will work as normal, and for users that don't then the current dialog will pop up.

BTW screw whatever idiot thought this was a good feature to add to KitKat. Seriously. They can get right in there and suck it. Biggest pain in the neck I've ever seen.

Verfasst am: Fr Jan 16, 2015 00:15

I will check if its possible to detect the AppOps permission.

Informationen zum Datenschutz auf dieser Website