search

joelmap / websmsdroid

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

Names/photos of contacts sometimes are not displayed / galaxy note #689

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

Sending a SMS and looking at it in the list. The recipient is shown as 
"Lastname, Firstname" <+491234567890> here instead of Firstname Lastname 
<+491234567890> for SMS I'm receiving here.

I also noticed that whenever a recipient or sender name does not match the 
address book it is not displayed with name and photo. Also threads are ripped 
appart.

The default Android SMS app does handle this correctly.

What version of the product are you using? "Last" is not appropriate. Make
sure you tell at least which app you are using. On what operating system?

1.1.8 SMSdroid and 4.2.8 WebSMS. Device is a Samsung Galaxy Note with latest 
official ROM (Android 2.3.6).

Original issue reported on code.google.com by msebald1...@googlemail.com on 4 Apr 2012 at 9:59

GoogleCodeExporter commented 9 years ago 
just to be clear: messages sent with websms are not shown in the same thread as 
messages recieved with the phone, right?
can you please check the message details within smsdroid for a single message 
for each side of the split thread?
is the number (format) the same for both messages?

Original comment by f...@ub0r.de on 9 Apr 2012 at 10:09

GoogleCodeExporter commented 9 years ago 
No, not messages sent from WebSMS, all messages which are sent are in a second 
thread in SMSdroid. SMSdroid also does not show the contact picture.

The recipient of a message which is sent looks this most of the time: 
"Lastname, Firstname" <+491234567890>

The sender of a received message often looks this way: Firstname Lastname 
<+491234567890>
Sometimes the sender of a message uses a different name, this happens a lot for 
service messages from your voice mailbox.

It seems that SMSdroid has a problem if the sender name does not match the name 
in the address book. In my opinion you should completly ignore the sender name 
and just look for the sending/receiving phone number. The default Android SMS 
app works that way.

Original comment by msebald1...@googlemail.com on 9 Apr 2012 at 10:52

GoogleCodeExporter commented 9 years ago 
well, i think it is a bug within samsung's android implementation.

the list of conversations/messages is provided by the system, not by smsdroid.
i just run a query against it. that means: i'm not parsing all messages by 
number or name to get the threads.
in fact the contact is attached to a thread, i'm just showing it's details like 
name and number.

for now, i don't know how to get a workaround here.

Original comment by f...@ub0r.de on 11 Apr 2012 at 5:33

GoogleCodeExporter commented 9 years ago 
Hm then why do I see everything correct in the default SMS app? It seems that 
they can handle it some way...

This bug isn't a real show stopper, but looking through the messages is kinda 
hard. The threads are at least divided in two threads. One for incoming and one 
for outgoing messages. Sometimes even more threads when there are more 
different names than just the two described.

Original comment by msebald1...@googlemail.com on 11 Apr 2012 at 9:22

GoogleCodeExporter commented 9 years ago 
well, samsung does not only have a custom implementation of the sms content 
provider. it even have a custom implementation of the mms app showing the 
content.
there definitely is a workaround, but i can't see it.

Original comment by f...@ub0r.de on 13 Apr 2012 at 5:32