adrnsoh / websmsdroid

Automatically exported from code.google.com/p/websmsdroid
0 stars 0 forks source link

Multipart sms not recieved #844

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install SMSdroid.
2. Install Websms.
3. Install and configure fishtext connector to fishtext user account (don't 
think this matters as it's an incoming message problem but this is my setup 
process).
4. Set as SMSDroid as system default SMS app, and for it to use fishtext via 
Websms. For this phone (HTC One M7 android 4.4.2 )there is a menu item 
specifically for this: system settings / wireless & networks / more... / 
Default SMS app.
5. Receive a multi-part sms (>160char long)

What is the expected output?
message length >160char. Also I expect one audible notification.

What do you see instead?
message truncated to 160chars, and TWO audible notifications (might be separate 
issue).

What version of the product are you using? "Last" is not appropriate.
Make sure you tell at least which app you are using.
v1.6.1

On what operating system?
android 4.4.2 (HTC One M7)

Please provide any additional information below.
I have been using this setup without issue on a previous phone (HTC Sensation 
XE android 4.0.4 ICS). I originally bakcup/restored to teh HTC Once via 
Titanium backup and had problems so I tried a re-install from market and 
manually reconfigured all settings in that did not fix it either.

By a process of elimination I have tried going back to the system sms app (i.e. 
without smsdroid/websms installed) which is OK, then step by step, installing 
SMSDroid and WebSMS and it is only when I set SMSdroid to be the system default 
sms app that incoming messages become truncated.
Viewing sms messages in the system sms app still show them truncated if they 
were recieved when SMSdroid was the default app. Similarly viewing sms messages 
in SMSDroid that were received when the system app was default shows the 
complete message, so it appears that it the the receipt of a new messages by 
SMSDroid that is the problem.

Original issue reported on code.google.com by tony.ton...@gmail.com on 30 May 2014 at 3:13

GoogleCodeExporter commented 8 years ago

Original comment by f...@ub0r.de on 1 Jun 2014 at 1:54