As much as I love my HTC Desire Z (or Vision for the US guys), it had one major flaw from day 10 or so.
For about 90% of the incoming calls, when I answered them (drag, or click on the <Answer> button), the phone would not really answer the call, it would keep ringing... and the other party would continue to get the ringback tone. After 7 or 8 or so rings, it would finally put the call through. Sometimes it would take too long, and I'd lose the call.
Annoying.
Very annoying.
Well, my dear friend V. noticed this behaviour the other day on my phone (granted, after a couple of beers) and told me there was one of those creepy #*codes that would switch of some networking stuff and make it work normal.
So while he was searching his archives to find this code, I also did some googling myself and found this behaviour described like this:
So I gave it a try, removed all my Facebook contacts, had a co-worked call me (a couple of times) and it seemed to work.
3 hours later, V. sent me the code.
(and got a "CFU query when camp-on is off" message... talk about non-cryptic :))
It still works fine.
Only problem now is, ... Against everything I learned and preached when I was working in software support decades ago, doing heavy problem determination work... never ever change two parameters at the same time, when you want to get to the problem source... never ever ... you understand?!
Well I here did... So I still don't know what made the phone work, removing Facebook contacts or V.'s cryptic CFU-query-when-camp-on... code.
So if anyone else runs into this problem, please try only one of them, and report back here.
Thanks
Anyway... my phone is now back to its basic functionality, taking calls.
For about 90% of the incoming calls, when I answered them (drag, or click on the <Answer> button), the phone would not really answer the call, it would keep ringing... and the other party would continue to get the ringback tone. After 7 or 8 or so rings, it would finally put the call through. Sometimes it would take too long, and I'd lose the call.
Annoying.
Very annoying.
Well, my dear friend V. noticed this behaviour the other day on my phone (granted, after a couple of beers) and told me there was one of those creepy #*codes that would switch of some networking stuff and make it work normal.
So while he was searching his archives to find this code, I also did some googling myself and found this behaviour described like this:
If you sync your Facebook contacts (on an HTC Desire) this could happen; and the solution - delete the Facebook contacts - seemingly did help a couple of users.Well, it was a convincingly high number of users that reported both the problem and the success through removing the Facebook contacts.
So I gave it a try, removed all my Facebook contacts, had a co-worked call me (a couple of times) and it seemed to work.
3 hours later, V. sent me the code.
Enter the following code in the dialer screen. *#*#2347#*#*So I did.
(and got a "CFU query when camp-on is off" message... talk about non-cryptic :))
It still works fine.
Only problem now is, ... Against everything I learned and preached when I was working in software support decades ago, doing heavy problem determination work... never ever change two parameters at the same time, when you want to get to the problem source... never ever ... you understand?!
Well I here did... So I still don't know what made the phone work, removing Facebook contacts or V.'s cryptic CFU-query-when-camp-on... code.
So if anyone else runs into this problem, please try only one of them, and report back here.
Thanks
Anyway... my phone is now back to its basic functionality, taking calls.
Subscribe
No comments:
Post a Comment