[B2G][Helix][sms][zhaotao]phone number can not be recognized in some cases

RESOLVED WONTFIX

Status

P3
normal
RESOLVED WONTFIX
5 years ago
2 years ago

People

(Reporter: lecky.wanglei, Unassigned)

Tracking

unspecified

Firefox Tracking Flags

(tracking-b2g:backlog)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; aff-kingsoft-ciba; Zune 4.7)

Steps to reproduce:

1.use another phone to send sms:00123123123!+123123123#123-123123
Test(123)123123123 to ffos phone
2.open the sms and check the phone number that can be recognized


Actual results:

in step 2,only 00123123123,(123)123123 can be recognized



Expected results:

00123123123,+123123123,123-123123,(123)123123 should all be recognized
(Reporter)

Updated

5 years ago
Component: General → Gaia::SMS
Priority: -- → P3
(Reporter)

Updated

5 years ago
blocking-b2g: --- → hd?
Looping Gaia folks.
does this work on Android and iphone ?

recognizing numbers is hard, you know.

Comment 3

5 years ago
Phone: ZTE phone.
Firmware: V1.01.00.01.019.120

Same problem.
Moreover, it is inconsistent.
Messages sent from the same phone without any change of configuration will sometimes be recognised, sometimes not. Once recognised one message is recognised, the previous messages appear in the dedicated thread; however it doesn't mean that the next message will be recognised directly.
Are these in the body of the message?

Comment 5

5 years ago
No. There are the numbers I receive messages from.
So they are at the top of the screen, where the contact usually is.
Same problem in the notification. Sometimes the contact's name is written, sometimes it's just the number.
Victor: I believe your comment does not really belong to the same bug. This bug is about phone number recognition in the body of a message.
Your bug is unfortunately known on version 1.0.1 but the good news is that we fixed it for the next version 1.1 !

Comment 7

5 years ago
Sorry about that then. Thanks for the good news.
Now I have to find a way to update the firmware to 1.1 on the ZTE Open...
Victor: it's unfortunately not ready yet, I know we're working with them to have it quickly as an update but I don't have much more information.
(Reporter)

Updated

5 years ago
Severity: normal → blocker
Priority: P3 → P2
still the question in comment 2.

And I think we'll WONTFIX this anyway.
Flags: needinfo?(lecky.wanglei)
(Reporter)

Comment 10

5 years ago
hi,julien,

these phone numbers can be recognized on android phone.

So,the issue still WONTFIX anyway?
Flags: needinfo?(lecky.wanglei)
The problem I see with this is that it's not a real-world use case to me. But maybe it's easy to fix and in that case we should do it.

Let's investigate but I think this should not block the release. Joe, can we add this to the backlog ?
Flags: needinfo?(jcheng)

Comment 12

5 years ago
I experience this problem everyday on my ZTE phone.
It's a problem if people travel or use several sim cards/phones (cheaper, mostly seen in developping countries and near borders).
It would be great if it was solved, but it's not major so don't delay the release for that.

Although, and that's probably another bug but just to mention it, if you attribute two (or more) numbers to one person, the texts are not concatenated. It's number specific rather than person specific which, in my opinion, would be better.
Cheers,
Victor: the phone and url matching algorithms already greatly improved in v1.1 (see bug 870711 and bug 887737). But this specific bug is for edge cases.
Please file a bug for the second issue you have, with detailed STR (Steps To Reproduce) and I'll have a look, maybe it's already fixed in 1.1 too but here I can't say because I don't understand it ;-)

Comment 15

5 years ago
(In reply to Julien Wajsberg [:julienw] from comment #14)
> Please file a bug for the second issue you have, with detailed STR (Steps To
> Reproduce) and I'll have a look, maybe it's already fixed in 1.1 too but
> here I can't say because I don't understand it ;-)

https://bugzilla.mozilla.org/show_bug.cgi?id=911938
(Reporter)

Comment 16

5 years ago
hi,julien,

do you mean that the issue may not be fixed on V1.1?
lecky> I really think this is not a blocker. Do you see this problem often in real life with current 1.1 code ? I think our current limited time is better used in other bugs.

Even if we have a patch, it would need to get a blocker flag like "leo+" for the v1.1 branch or "hd+" for the v1.1hd branch, and such blocker flags are usually not set for non-critical problems.

However feel free to investigate and even provide a patch, if the fix is simple and easy we may include it.
Severity: blocker → normal
I agree with Julien. This is not a blocker. Overall because the scenario that you describe it's more a feature than a bug, because my Android is making the same (it does not matter if I have '123' & '456' tied to a single contact, because messages received/sent to '123' and '456' are in different threads).
add to backlog bug 891754
Blocks: 891754
Flags: needinfo?(jcheng)
This is not a blocker for v1.1 given its nature and that we will only take critical fixes now for v1.1/hd.

Anyone that thinks necessary can nom this koi? with rationale for triage.
blocking-b2g: hd? → ---
(Reporter)

Updated

5 years ago
Priority: P2 → P3
blocking-b2g: --- → backlog
(Assignee)

Updated

4 years ago
blocking-b2g: backlog → ---
tracking-b2g: --- → backlog
We don't reconize these phone numbers because we have the "safe start" algorithm that does not include these characters. I don't know if we should do it, I don't exactly remember why we did this "safe start" algorithm and this would need some bug archeology.

I can keep this bug open though.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Mass closing of Gaia::SMS bugs. End of an era :(
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
Mass closing of Gaia::SMS bugs. End of an era :(
You need to log in before you can comment on or make changes to this bug.