IssueTracker

Just to elaborate on the issue.

I am using a HTC Magic from Vodafone UK on Cosmote GR.

I got an OTA update to 1.6 the other day.

In order to demonstrate the issue let's use an example number.
+306912345678  is a standard Greek mobile number.
I have my contacts stored in the following format: +3069xxxxxxxx
but on incoming calls, the number appears as 69xxxxxxxx and it doesn't match with the
contact.

If you change the contacts to exclude the country code in front, then you have an
issue with the text messages where the incoming number is identified as +3069xxxxxxxx
inclusive of the country code - and again it doesn't match with the contact.

Hello

I am having the exact same issue.  I am using a vanilla unbranded HTC Magic with
Turkcell in Turkey.  Before donut, everything worked fine.  Now however, incoming
calls are not recognized.

I store every number in the international format since I travel a lot.  +CC (XXX)
YYYYYYY is the format I use where CC is the country code, XXX the area code and Y's
the number.  In 1.5, incoming calls that were  XXX YYYYYYY did map correctly but now
they aren't.

I suspect it is an issue with the carrier putting a 0 in front of the number.

For example if I have  Bob stored as a contact and his number is +12 (345) 678 9012
and bob calls me,

Donut will display <Unkown> 03456789012

It cannot deduce that 03456789012 is the same as +12 (345) 678 9012

This was working fine and without a problem in 1.5

Hope this helps

Is there a particular reason for this issue to have medium priority? It practically
stops the user from knowing who is calling, a feature already available in
"brick-sized" mobile phones from 15 years ago. This issue has a very high priority
for all users who encounter it.

Indeed, I was forced to flash with unofficial firmware to overcome this issue.
Something that I am really not happy about.

However on the new firmware that I am running the locale that you are selecting
affects the way the number is displayed when you have an incoming call. Maybe someone
that encounters this problem and is still using the original firmware can confirm
whether or not changing the locale affects the bug.

It would be great if you could share which firmware you used to get your phone to
work again.  This problem seems to be present in a lot of countries but as another
person said, it must be areas that google deems 'unimportant' as a core feature of a
GSM phone does not work, and this is not getting any attention, replies or fixes.

As of now, Google's 1.6 Donut Version of Android performs worse than a basic brick
phone from the 90s, unable to recognize incoming number formats and map them to
contacts, and this core feature's shortcoming has been literally ignored and left
without a reply from anyone in Google for over a month.

Just FYI here is another location where this is being discussed.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=1491f65b23e01c49&fid=1491f65b23e01c49000478b74fabce5c&hl=en

I am having the same problem.
I am using the G1 Dev phone on COSMOTE GR.

I received the 1.6 upgrade OTA, and since then I am facing the problem with the
contact numbers. I used to store the contact telephone numbers as +30XXXXXXXXXX.
After the upgrade, the contacts did not show up in the call log. I changed all of
them and removed the +30. Now i have the contact in the call log but i do not have
them in messaging.
I tried to change locales to see if it has some effect on the issue, but it did not.
It is frustrating to lose basic telephone functionality after an upgrade...
Christos

I have the same issue, Romania, Vodafone HTC Magic, Android 1.6, kernel
2.6.29-00479-g3c7df37, Build no. DRC92
* I have my contacts defined with local format: 0722123456
* the SMS I received comes from +4072123456 and is not recognized as contacts
--
I tried to reverse: to define contacts with international format +40722123456, or
0040722123456 --> and SMS are recognized, but not anymore the incoming calls
----------
This is a standard, basic feature for any mobile phone which is expecting a minimu
respect from their users. It should be treated as a high priority bug.

Me and my partner have the same problem after installing 1.6.
Tired of Android bugs!!! It is unbelievable they haven't solved it so far.
I travel abroad frequently, therefore I also need to have every contact with the
country code in order to use the phone from and to any country, besides, now a days
there are people that have more than 2 thousands contacts in their phones, it is
unthinkable having to edit all of them and even if I did it the phone would still be
useless abroad.
Hope Android solves it soon. It’s been more than two months that we are using a
phone with no caller ID.
Nothing to do with this post but it’s been since day zero that G1’s Bluetooth it’s
useless for my car and many other cars. Totally regret having bought it.

I have this exact problem since 1.6.

My contacts with +(XXX)XXX-XXXX don't match caller id when receiving a call, which is XXX-XXXX without the
country code.

Cant remove the +(XXX) also, since that would mess up the messaging which includes the +(XXX).

Now maybe i have to put a duplicate entry on every contact without the +XXX country code also, which i don't
want to do.

I'd like to undo 1.6 and go back :(

I can confirm that the issue is fixed in Adroid 2.0

I've recently purchased a Motorola Droid phone that comes with android 2.0 and the
incoming calls work as they did in 1.5

It is baffling to have to wait this long for google to fix a 1.6 bug that is this
crippling to users (it IS a fundamental function of GSM phones after all).

1.5 works, 2.0 works.  Seeing as how this is lablelled 'medium' one can expect that
nothing will be done to 1.6 about this.  You will have to wait till 2.0 hits non
droid phones or downgrade back to 1.5

Does it mean that they will stop maintaining 1.6? This is ridiculous. G1 does not
support 2.0. And all the users that were early adopters of android will continue
suffer.

Hey guys,

I'm having the same problem, using a HTC Magic on Vodafone, RO.

A workaround is to have both phone number formats for each contact:
- the one with an international prefix
- the one without the prefix

PS
or to store the phone numbers without the international prefix and use another SMS software (like Handcent SMS)

[Comment deleted]

I think I have fixed it for RO
http://forum.xda-developers.com/showthread.php?t=606728

will only work if adbd daemon on your device is running as root, or you have a rooted
phone.

cannot use:
- adb remount
- adb root
- adb shell mount -o remount,rw /dev/block/mtdblock3 /system

Same problem for a HTC Hero here in Norway, It's really annoying and it must be fixed.

In Turkey, using Turkcell, we HTC magic 1.6 people still, still, still, having this
problem...

Will somebody from Google fix this 'medium coded(!)' issue?

Same problem. In Malaysia (using Celcom) with HTC Magic from Vodafone UK. Please fix it!!

Same problem on Turkcell network. Looking forward to a fix.

Yep, here too - Nexus One...

Same problem here in Brazil (VIVO network). I´m using a Samsung Galaxy with Android
1.5.. Could anyone give us a help?

YEP another Brazilian G1 owner with the same problem !!

It's unbelievable! Another Brazilian user with the same problem after update from 1.5
to 1.6. I hope a fix soon.

Im using Samsung Galaxy with android 1.6.

I have the same problem. OI Brazil network. I'm using a htc mytouch 3g!

Same problem: G1, 1.6, Romania, Vodafone RO

I can't believe nobody has come up with a solution yet!! I mean, people find ways to
unlock and to hack everything on phones but cant come up with a fix for such a
glitch?!?! This has to be done on purpose, otherwise i can't see the reason for not
fixing it yet!
Same problem: T-Mobile Unlocked G1, 1.6, Romania, Vodafone Ro

same prb
O2 Unlocked, Samsung Gaklaxy i7500, Romania, Orange

i am also having the same problem with HTC Dream aka Google G1 in Malaysia. What a
shame. its a very petty issue and yet it cant be solved. I ve browsed through so many
forums. None of them with answer...oh my. am i goonna google it again ?

Beating the same dead horse apparently.

Same issue with HTC Magic from Vodafone UK on Vodafone RO.
This is embarrassing.. over 6 months and still no answer or solution. And mind you,
for a bug that came with an UPGRADE...
How does google plan to impress customers with such response???

Will my next smart-phone be an android powered phone? hard to say.. for an open
source OS it sure seems that the developers have dropped the ball on this one..

Hi All,

Every country has its own phone number length, which causes matching numbers a
problem. To make it worse some carriers add prefixes on the numbers for sms services.
As far as I understand the android devices manufacturers should be the ones adapting
the number matching for the countries and/or operators which they sell theirs phones.
Any thoughts?

I agree with you, it's should be resolved by carriers customizations, but by
default android 1.6 should behave like android 1.5 and 2.x does. The most of
carries don't worry about or don't have enought technical knowledge to solve
that problem and the result you can see above: a lot of user around the world
complaining about that issue.
I've tested that against all versions of android and the 1.6 is the only one with
the problem. It doesn't make sense at all for me.

Guys the problem is that phones should only take into account the last six digits of
the incoming number. For some unexplainable reason 1.6 looks at the whole number
which is absolutely ridiculous because every carrier sends the numbers with
different formats and prefixes, the only thing that doesn't change worldwide are the
6 last numbers that belong to the line it self regardless of the prefix or country
code and that's why 10 years ago cell phone programmers realized caller ID systems
should only look at the last six numbers, or eight at the very most, when mapping
the incoming number with the phone directory.
Another thing that could be causing this issue is the fact that android 1.6
automatically puts hyphens separating the area code, because that change also came
together with this unbelievable irritating embarrassing and unacceptable issue.

Same issue in Lebanon, i Have an HTC desire with android 2.1 and have the same issue.
this is really annoying and the worst part about it is that no one from google cares.

Same issue I have in Lebanon. The phone numbers show as following:
0X 123456 (x=region)
+961 X 123456 (+961 being the country code)

I'm using HTC desire with Android v2.1-update1

Same issue in Mauritius (+230) on a HTC Desire running on Android 2.1-update1.

Phone are stored like this :
+230 XXX XX XX

Incoming calls are displayed like this :
XXX XX XX

Please update the version field for this bug because it does not only affect 1.6 but also 2.1

same issue on android 2.1 update 1   - motorola xt701

contacts are only recognized if they match exactly with the incoming ID.

this is such a basic funtion on a phone. please fix. I can't spent a week fixing all my local contact to have the international format just becouse your software isnt smart enough.

this really sucks

I have a motorola milestone with android 2.1 update and this problem doesn't exist. In my old galaxy with the pure android gaosp rom i had no problem too.
I don't believe this bug is present on 2.1 main code, it might be inserted on some specific rom.

@brunojcm :

Can you tell me if your operator includes the international prefix in the local incoming calls ?
It is not the case of my operator but I know that other operators includes the international prefix systematically (even for local numbers).

Maybe this would explain why some have the issue and some do not...

Having also the same problem with the prefix +230 on Android 2.1 up 1 (HTC Desire)

I always had to tweak my WM powered phone to fix this issue (7/8 digits issue)

I would have guessed the same tweak could be done with Android... Seems not, yet.

A fix/tweak would be very much welcome as it seems to affect quite a few users around the World.

Bruno, my operator Movistar Argentina sends 0-(Area Code)-(Phone Number) for SMSs and only (Area Code)-(Phone Number) for phone calls. I need to save the numbers with the country code +(Country Code)-(Area Code)-(Phone Number) because I travel internatially and otherwise I wouldn't be able to make calls from abroad.
Sorry to tell you guys, but I gave up after so much time waiting for a fix. I spend four days and edit my whole directory having to save every contact with the three formats in order to get caller ID and SMS sender ID. Now the only functional problem is that when I'm abroad SMS go to a different thread for the same person because I need to use a different format than the one I use locally and of course my "smart phone" wouldn't tell I'm talking with the same person, even though both numbers are the same number with different format and both belong to an only contact from the directory.

They don't give a .... about solving this problem :-) Good luck solving it yourselves, edit the numbers and so on...I have a G1 for sale :-) Anyone?

I moved back to iPhone. I recommend you do the same.

@xavier

My carrier use 0 (area code) (number) in both calls and sms, so putting the numbers is this format is enough to me. I don't know what would happen outside my contry because I've never been abroad with this cel phone.

I did some tests here and the phone keeps showing the names correctly even if I remove the 0 (area code) parts of the contacts. In the Android 1.6 phone I had before it didn't happen. I did another test: put a lot of random number as a prefix in one contact and asked him to call me. The contact name was shown correctly. It makes believe that at least my rom is considering only the last 8 (or 7) number to match the contacts, what seems fine to me.

@brunojcm

Could you please create a contact with a number having the international prefix (+XXXYYYYYYY) and ask the contact to call you ? You said it worked with the area code, but maybe the problem is only about international prefix...

Google, please set the version to 2.1.

Regards.

I just got an htc Legend and have the same issue , going back to iphone would not recommend any htc products as they dont really care about support

Same problem with 1.6 here in Brazil.....

Lol DOnt give up the fight cuz

[Comment deleted]

Timing Ca p tester zot 1 coup

I used to have this problem with 1.6, and it disappeared (!) when I changed provider... Now that's weird.

I changed from Base to Proximus (in belgium), and all of a sudden, I no longer get unknown numbers and all of my phonecalls to contacts (with or without international prefix) are recognized again.

Without a firmware change or anything...

I have the same problem with SE X10 mini and Cosmote GR.
have anybody try this solution?
http://forum.xda-developers.com/showthread.php?t=606728

same issue here, hopefully it will be resolved with Froyo update

Did anybody have the issue with 2.1 and has not with 2.2 ?

I am XPERIA X10 mini, with Android 1.6 (for sonyericsson), and..  I need to mod it for id to properly recognize my contacts in SMS messaging. As right now it recognized my contacts when someone calls but when they send me a SMS it just put the number not the contact name. Please HELP!

@hfurfaro

Do you store your contacts with or without the international prefix ?

When you receive a SMS, does the phone number displayed include the international prefix ?

please fix this issue, its realy annoying...

with or without international prefix code does not work. Or does the incoming calls or text messages. But never both. You've tried everything. It is a known problem. Someone fix this?

I can not believe this has not come to google. For months, some people with this problem. A shame.

I am on Android 2.2, and my country's numbering scheme requires Caller ID matching in SMS of 7 digits only and not 8. Android doesn't allow changing that. I used to do it in Windows Mobile by modifying the registry key: HKLM\ControlPanel\Phone\CallIdMatch.

Now all my SMS don't show a sender, and the problem has been there in Android for several years. This sucks...

Handsent SMS 3.2.8 solve this problem

I have the same problem with xperia mini x10
My country Costa Rica, area code 506

Same problem in Donut, with Samsung Galaxy i7500, in Romania, on Orange.
Its really annoying.

Same problem here in Iceland. Have HTC hero which I upgraded from 1.5 to 2.1. Worked like a charm before. Not at all after.

Same problem here on SE Xperia Mini Pro (v1.6) in Malaysia. Full international format number are sent for SMSs - like +60101234567, while for incoming calls only 0101234567 number is sent which eventually displays as 010-123-4567

This is my first Android phone (aka smart phone) and I am honestly surprised a smart phone cannot handle what my very first GSM phone light years back could do! Back in the days, this was one of the major extra features mobiles phones offered over landlines back in the days. Now we have phones which can connect to Facebook but they won't show a caller name - is that really evolution? :-S

Sam thing here. X10 running Android 2.1. I am really stunned by this...

I have Galaxy S I9000 (Android 2.1)

A-Contact is stored with international prefix.
B-I send message (OK)
C-Contact replied.(OK)
D-When trying to reply, I can't the number is stored WITHOUT the international prefix. (Fail).

Previous comment also appears as issue 36921437.  Replying to text message drops + from original number causing the text message to fail.  HTC Desire with 2.2.

htc legend on Aruba (+297)xxx xxxx. Android 2.1 and 2.2 same issue...  :-((

Can the title of this bug be updated?
I'm on 2.2 and having the same problem.
We've got to say that it affects Android beyond version 1.6

I have the same issue and I am on HTC Desire Z with Android 2.2:
- i send a message to a friend with international prefix, from france to italy (ok)
- he answers. if I reply the phone chooses the number with no prefix and calla fails!

I think it is related to Facebook. That is, the friend in question has a facebook profile with the mobile number on it, but it does not have the +.
Still I am not able to overcome the problem.

I don't know why you keep posting issues here, Google don't care about community feedback given here. This issue is open for years and nothing is done.

And considering this specific problem, Google can only provide good default strategy, because the final work should be done by the carrier, phone number matching varies from country to country.

Google developers, please close this issue as "WONTFIX" and don't make people lose their time.

I don't think this last comment is helpful.  There is definitely a problem with replying to text messages and it does not relate to the network or to Facebook.  It's just a silly bug that should have been fixed some time ago.

biskinis, nothing we do here is helpful. I'm watcher of some several android bug and never saw then fixed by Google, that's the reason for what I said before.

And I think you should open a new (useless?) ticket for 'problem with replying to text messages' because this ticket is about contact names not being shown on incoming calls and messages.

I didn't said it's network or facebook fault, I said its a carrier fault. The way the carrier configs their network to send the call or messsage sender can mislead the phone on contact recognition.

Comment 74 is a little off.  This is a bug introduced into android with 1.6.  It is not a carrier issue.  Prior to android 1.6 this issue did not exist.  It however has been present since 1.6.

It is not the carriers of the world that should change how their CID is sent, just so it complies with a cell phone on the market, it is the cell phone platform that should remove the bug caused in version 1.6 that narrows down number recognition and mapping to contacts making the used algorithm incompatible with a number of worldwide carriers.

Different means of sending CID have existed since CID has been introduced.  Yet cell phones developed efficient algorithms to map CID with carrier variations to stored contacts.  They have been doing so since 15 years or so.  

It is not a carrier problem.  It is an android problem.  Comment 74 is like saying, We made a TV with a non standard resolution so consumers complaining about their TV distorting the broadcast images should tell the networks to change the way they broadcast to match our TV.

> Comment 74 is a little off.  This is a bug introduced into android with 1.6.  It is > not a carrier issue.  Prior to android 1.6 this issue did not exist.  It however has > been present since 1.6.

It was not "introduced". Android 1.5 just have better default check algorithm, considering only the 7 most right digits.

> It is not the carriers of the world that should change how their CID is sent, just > so it complies with a cell phone on the market, it is the cell phone platform that > should remove the bug caused in version 1.6 that narrows down number recognition
> and mapping to contacts making the used algorithm incompatible with a number of
> worldwide carriers.

Agree, but the way Android is now, a lot of thing should be customized by manufacturer/carrier. The configuration of number matching is one of them.

I can provide you a lot of problems in the default way of matching, It's not a trivial task. Compare only the 7 most right digits can give a lot of false positive matching, so Google left this task to be done by the carriers/manufactures. If you read the posts here you see that not all models have this problems.

One more time, I agree Google should provide a better default algorithm, but it's impossible to cover all the world with 1 algorithm. This config should be locale-dependent or carrier-dependent.

I think it may not be a hard task to build the algorirthm for my country. Do you know how to get into the api and parse the number? We could then build a county-based repository or maybe even an app in market

AFAIK it's not possible to use custom apps with the default dialer. To modify that we need to change the whole dialer and calls apps. :(

I tried some hacks in the past with modified sqlite files, I guess they change the query on database to search for contacts. Unfortunately I don't have the links anymore.

I have 1 HTC Wildfire and 1 HTC Tattoo. WF works correctly but TT does not show name in sms after update to 1.6.

Could Google developers reproduce this problem and know the reason?

This issue is opened for 2 years and Google ever does not give us an answer :( this is so disappointed...

does anyone have unofficial way to fix this?

An app like Prefixer could help
http://www.253below.com/prefixer

Installed it but haven't got it to successfully add prefixes to my incoming calls.
On HTC Wildfire.

This is a duplicate of issue 36919417 and pretty annoying... :s

I just upgraded to 2.2 with my HTC Desire and the issue is still here :(.

The problem is that this issue is tagged as "Version-1.6" and the issue title states "Android 1.6 update issue", so Google developpers will not even read it.

Who can change the title and the version ?

Regards.

I am located in Iceland running 2.3.3 on a HTC Incredible S and I think it is disgraceful that this issue has not yet been solved.
Matching incoming/dialled phone numbers with stored contacts (stored with or without area and/or country code worked flawlessly on my first Nokia cell phone I had about 13 years ago.  
The first iPhone had issues with this at first but it was solved in one of the early firmware updates.
One has to wonder why a basic thing like this has not been amended in Android after all this time.

[Comment deleted]

I have a new galaxy S2 in Australia and I have the same problem and I note it has now been exactly 2 years (to the day) since this issue was first raised here - AND STILL NO SOLUTION.
What the ____ are those guys doing. FIX IT. It is disgracefull that you have let this problem go on for so long.
My previous phone was an old Sony Ericson K750 from 2005/2006 and it did not and still does not have this problem. Same Carrier, so 100% definetly not a carrier issue.
I have had to start storing all home, business and mobile (Cell for you Yanks) numbers twice each for every contact. Very time consuming to do and a waste of memory. Please FIX IT ASAP.

No update in sight. And I'm guessing that there won't be any.. If all carriers would just simply adopt the international notation..

@GregoryT, you can use an automatic prefixer instead of updating your whole address book..

Hmm, thanks for the tip michael.
Just Googled Automatic Prefixer
Looks like it might be useful, if it will match incoming calls lacking the country code to stored numbers with a country code.
That is will it add the country code (at least the current country code) to incoming call lacking the country code before it searches for a matching contact?
I, be default, enter all numbers with the country code.
I have had to re-enter new numbers without the country codes because of this bug.
If automatic prefixer will allow me to get rid of all stored numbers lacking a country code and still match local incoming calls with phone numbers in the contacts list then it will do the job. Will it do this?
While this may work, it is far from ideal. This is a simple problem and the android developers should fix it, after all they created a problem here where none previously existed.

Ah, No it won't.
In response to my previous comment, I have just read comment 83 and see that Prefixer will not prefix incoming calls.
So the problem continues.
The developers MUST fix it.

Perhaps they should adopt a 'First Do No Harm' policy when updating their products.
However I suppose a temporary loss of basic functionality in one area for overall improvements is probably acceptable in most cases, but a permanent loss of this functionality is not acceptable. This is especially true when the functionality in question is an integral part of the devices primary reason for existing .i.e. making phone calls to and receiving phone calls from contacts. This is what phones are all about - everything else is an add on.
Or do I now need two phones - one for web browsing and a second simpler phone so I will know who is calling me?

I have almost the same issue on my Galaxy Nexus running 4.0.1,  in Argentina the carriers will send the caller id as 0AAANNNNNNNN (A= Area Code N= Phone Number), but the SMS arrive as +54 9 AAANNNNNNNN, i store all my numbers in the international dialing format (same as SMS), on my previous Android Phone, a samsung i550 running Gingerbread that would not be a problem and it would always show the contact name, now with the Nexus i found out that i have to remove the "9" and store the numbers as +54AAANNNNNNNN for the Contact name to appear on incoming calls, unfortunately this causes the incoming SMS messages not to match the contacts.
Adding two phone numbers for each contact is out of the question when you have 500+ contacts and prefixer doesn't seem to work for incoming calls.

Same here with galaxy nexus 4.0.1

Same Problem here in the maldives.. HTC Rhyme. android 2.3.5 :(

As I see, Android try to match the full number for an incoming call with the phone number stored in the contact list. So in countries that you dial with a prefix in some cases and the network send without this prefix, we can´t see contact list.

If you call a mobile number in argentina you need to add 9 between country code and area code +54 9 11 cccc nnnn but when you received the incoming call +54 11 cccc nnnn. This is for identify a calling party call for internationals operators.

So how we can only try to macth less digit rigth to left? instead of the all number.

In the UK. Samsung Galaxy s2. Icecream sandwich 4.0.

Same issue. Contact have been saved in different format i.e. +44nnnnnnnnnn or 0nnnnnnnn. With the same digits after +44 or 0 within the country should be identified as the same contact. Unfortunately, does not happen. I don't understand why a SMARTPHONE with an advanced SMART operting system cannot pick up numbers SMARTLY. It does not deliver purpose of being SMART PHONE.

Please help (F1).

Dipak.

Same here, HTC one.
Incoming phone calls have the number only (no country code) and are not matched with the phone book. My numbers are stored with country code as most of my time is spent travelling.
No problems with my previous 2 Android phones the Samsung S3 or the Sony Z.

Very annoying

Not even the HTC One gets it right.  It just gets more and more disgraceful.

As I already wrote somewhere my son has an old LG (was back then the cheapest model from LG) and there incoming calls and SMS are mapped with contacts irrespective of saved with country code or not.

Also have a new htc one with the same exact problem. Htc support mentions that it`s not a device problem. All i can say is that i dont have the same problem with an iphone, s4 or jeez even an old nokia 3310!!

I am having the same problem with my HTC One.

My HTC One was originally a T-Mobile Phone. It is unlocked and I am using it in Ireland with the Vodafone Network. My numbers are saved in the format 0871234567. When I receive a call my phone recognises the contact, but when I receive a text the phone does not recognise the contact and just displays their number with the international prefix ie. +353871234567. I changed some of my contacts to be save their number with the international prefix and then the opposite problem occurs. My phone will recognise their texts, but not their calls, which show up without the international prefix ie. 0871234567.
It worked fine when i was in the USA distinguishing that +1 was the prefix for the USA and that both numbers (with or without the prefix) were the same person.
How do I resolve this problem?

#101 im in vietnam and same that issues with m8 tmobile

This is 4Q15 and same issue with Lenovo K50-T5 (Android 5.0) in Nigeria. I have used many Android phones before starting with Tecno F7 (Android 4.0) but this is the first time I am encountering such problem. My other Android 5.0 phone, a Lenovo Vibe Z2 Pro (upgraded from Android 4.4.2) does not have such issue. Has anybody figured out the solution to the problem yet?