search

adrnsoh / websmsdroid

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

Cannot receive mulit-sms, #830

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.install smsdroid as default sms app (Nexus 4, 4.4.2)
2. send yourself a sms with more than 160 chars (e.g. 2 or more messages at 
once) / try to receive such a message from anywhere else
When I send myself a extra long sms via websms (and set smsdroid to default), 
two single messages will be stored to the database.

What is the expected output? What do you see instead?

All messages should be received, instead only the first part (160 chars) are 
received and displayed. Even if you change back to stock sms app.

When I use the stock sms app to receive such messages, anything is fine.

WebSMS 4.8
SMSDroid 1.6
Nexus 4, 4.4.2

Original issue reported on code.google.com by realgun4...@gmail.com on 11 Feb 2014 at 12:23

GoogleCodeExporter commented 8 years ago 
do these messages have some kind of special encoding? like any special 
character at the beginning or end of the messages?

Original comment by f...@ub0r.de on 13 Feb 2014 at 9:43

GoogleCodeExporter commented 8 years ago 
No, i recognized this problem when my wife has sent me an longer (> 160 Chars) 
message from her "normal" (non-smartphone) mobile and just the first part was 
received and stored.
To test this issue I've send myself a long message from cherry-sms 
(web-interface) just filled with 160 "1" and then some "2". Just the part with 
the "1" was received and stored.
After this I switched back to the stock sms-app and repeated the test and the 
whole sms was receiced, displayed and stored.

I even repeated this scenario using websms and the standard "sms-provider" from 
simcard (congstar). The same behavior. Additionally I can see the sent long 
message splitted into two "normal-sized" messages: two "bubbles", one filled 
with "1" and the second has the "2".

Original comment by realgun4...@gmail.com on 13 Feb 2014 at 9:57

GoogleCodeExporter commented 8 years ago 
Hi, I don't want to push... but are there any updates on this issue? Do you 
need some other information?

Original comment by realgun4...@gmail.com on 5 Mar 2014 at 10:15

GoogleCodeExporter commented 8 years ago 
I encounter the same problem using SlimKat 4.4.2 Build 3.6 on my i9300

Original comment by elhen...@gmail.com on 14 Mar 2014 at 2:38

GoogleCodeExporter commented 8 years ago 
I've came across the same issue on a Moto G with 4.4.2. Once SMSdroid is set as 
default SMS app received messages are truncated at 160 characters. They are not 
stored, so the truncated part is lost.

Sending a long SMS works fine (received ok, stored ok).

Original comment by Dominik....@gmail.com on 26 Mar 2014 at 7:44

GoogleCodeExporter commented 8 years ago 
I gave this issue a look and opened a pull request for a change that (I think) 
fixes this issue: https://github.com/felixb/smsdroid/pull/16

Please review it carefully, I'm not really familiar with SMS on Android, so 
this solution might be wrong. It works fine for me though, at least as far as I 
could test it.

Original comment by Dominik....@gmail.com on 27 Mar 2014 at 7:45

GoogleCodeExporter commented 8 years ago 
please verify this fix

Original comment by f...@ub0r.de on 31 Mar 2014 at 2:09

Attachments:

GoogleCodeExporter commented 8 years ago 
Ok, receiving a "oversized" sms seems to be working, I send myself such a 
message. 
But the sended "oversized" sms is still split up into multiple sms, which are 
stored seperatly.

Original comment by realgun4...@gmail.com on 31 Mar 2014 at 2:26

Attachments:

GoogleCodeExporter commented 8 years ago 
I'm wondering how you sent that SMS -- did you use the built-in SMS sender of 
SMSdroid? Using that I can send "oversized" messages just fine, and they are 
saved in the SMS database as expected.

Original comment by Dominik....@gmail.com on 31 Mar 2014 at 6:11

GoogleCodeExporter commented 8 years ago 
Yes indeed - I wrote an "oversized" SMS from WebSMS started from SMSdroid using 
the build-in SMS-Provider.
I' ve repeated that test right now with the same result.
But I also tested again using the "CherrySMS-Provider". 
Strange and confusing - but in this case, it works also for sended ("outbox") 
messages. Both (sended and received) are stored completely and as a single 
"oversized" messages.

Original comment by realgun4...@gmail.com on 31 Mar 2014 at 8:56

GoogleCodeExporter commented 8 years ago 
Since 4.4, android saves sms on its own, when sending them via standard api, 
like the websms sms connector or SMSdroid are using. 

I'd need to look more into that. But I'm traveling right now..

Original comment by f...@ub0r.de on 1 Apr 2014 at 11:53

GoogleCodeExporter commented 8 years ago 
Hi, will there be any updates to this issue? I'm still have problem with 
"oversized" messages and hope for help...

Original comment by realgun4...@gmail.com on 12 May 2014 at 6:42

GoogleCodeExporter commented 8 years ago 
Can you please be more specific? What are the problems you still have? Is this 
only when sending messages via WebSMS (as you already said in comment#10)? In 
that case I consider it a separate issue; this task talks about receiving SMS, 
not sending. It also might be a problem in WebSMS or the used provider, not 
SMSdroid.

Original comment by Dominik....@gmail.com on 12 May 2014 at 7:34

GoogleCodeExporter commented 8 years ago 
Yes, it is still the same problem as I described before (comment #10). I makes 
no different for me if the problem is caused by websms or smsdroid, both are 
supported in this issue tracker. In my view, all messages (sent / received) are 
stored into the same database and will be shown by smsdroid in a threaded kind. 
Feel free to split up this issue, if you need to.
I'm sorry if anyone felt pushed by me, that was not intended by me.

Original comment by realgun4...@gmail.com on 12 May 2014 at 7:47

GoogleCodeExporter commented 8 years ago 
I've been trying to reproduce this, and the problem indeed appears when using 
WebSMS' internal SMS provider. So this clearly is an issue of WebSMS (and since 
this task is marked as Product SMSdroid I believe it should be handled in a 
different task). Also, there is an issue in the Android tracker which describes 
exactly this problem (caused by the fact that WebSMS is not the default SMS 
app):

https://code.google.com/p/android/issues/detail?id=67531

Not sure if this actually can be fixed in WebSMS given that description.

Original comment by Dominik....@gmail.com on 12 May 2014 at 9:01

GoogleCodeExporter commented 8 years ago 
@Diminik: right. that is the problem here with websms.

my app relies on the fact, that the android api handles writing sent messages 
on it's own now. however, this mechanism is broken in android. not in my app.

any sms sent over web is not affected, because they are written by smsdroid.

Original comment by f...@ub0r.de on 16 May 2014 at 4:40

GoogleCodeExporter commented 8 years ago 
Issue 844 has been merged into this issue.

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

GoogleCodeExporter commented 8 years ago

Original comment by f...@ub0r.de on 4 Jun 2014 at 2:02