[Q] Dialer autocomplete not working properly - Samsung Galaxy Nexus

Hello, I'm kind a new to Galaxy Nexus, to whom I switched from Samsung Galaxy S (GT-I9000). I used my SGS with 4.2.2 Xylon ROM 2.4.1, now I'm using Galaxy Nexus with Cataclysm ROM.
When I used SGS when typing on the dialer it gave my suggestions from my phonebook:
1. based on the letters coresponding on the numbers on the dial pad
2. based on the numbers of a phone number saved in the phonebook, no matter if I start from the beginning. For example if the number is 12345678, I could start typing 678 and still get the number as a suggestion from autocomplete.
Now with Galaxy Nexus the dialer suggestions are:
1. based on the letters coresponding on the numbers on the dial pad (same as above)
2. based on the numbers of a phone number saved in the phonebook, but only if I start from the beginning. For example if the number is 12345678, I must start typing 123 to get the number as a suggestion from autocomplete, I can no longer type any part of the number and still get it as a suggestion.
My question is: is this 4.3 issue, has the dailer been changed since 4.2.2, or is it a ROM issue. I do not have permission to write in Cataclysm ROM thread that is why I’m asking here.

No one has to comment something? At least share how it works for you.
I don't want to be misunderstand, I'm not complaining about the ROM. It works great for me, never had any issue at all. I just notice this one thing that is different and that I really miss. That's why I'm asking to share how it works for you. Thanks.

Related

[Q] [Sense 2.0 Roms] First digit/character ignored in HTC Dialer

ROMs affected for sure: iNsertCoin v2.0.0 and RCMixHD v3.5 (both A2SD)
Whenever I type in characters in HTC Dialer to search for a name (e.g. 846 for contacts named 'Tim') the first number gets ignored, resulting in search results starting with characters represented by the numbers '46', e.g. 'Ho...'.
Similarly, when I try to access the test screen via *#*#4636#*#*, the first character '*' gets ignored (it even disappears after putting in the first '#').
If I put in something, then remove it with backspace and start over, it does work.
Don't think it's relevant, but Baseband version is 32.49.00.32U_5.11.05.27.
What is happening here? Tried setting different locale in settings, different keyboards, no change. Thanks in advance.
Ok second post now. Maybe your phone is a little nakered, rom broke a little. It seems your just getting software errors which happen when you flash custom roms.
Posted this here in Q&A after iNsertCoin developer suggested me to do so. He heard of this problem before, but had no solution. Hopefully other ppl have found one, but an extensive search both here and on other forums did not give any result.
Solved
After (quite!) some more research, I've found a similar problem described in the topics below. The presented fix there also solved my problem (see quote):
With great help of some participants of xda forum a workaround for this issue has been found: just remove the dialer shortcut from the dock (set it to "blank") and then add it back in (a shortcut to "Phone" app). This will fix the problem.
Apparently, people who are not experiencing the issue are the people who already recreated their dialer shortcut while customizing the dock. Meanwhile, people who keep the initial dock (or, more precisely, the initial dialer shortcut) all experience this problem. The problem is not limited to Plus version - a plain LaucherPro has it as well.
It looks like LauncherPro, as shipped, uses some unorthodox way to launch the dialer (I wonder why), which is what's causing the latter to act up. Recreating it as an ordinary app shortcut fixes the problem.
Click to expand...
Click to collapse
Sources:
http://www.launcherpro.com/forum/viewtopic.php?f=14&t=5884
http://forum.xda-developers.com/showpost.php?p=10490200&postcount=15

Creating pauses for extentions?

Hello,
I normally put p for a puase -e.g. 212-555.1212 x 505 would be 2125551212ppp505 - that would pause about 5 seconds after dialing the main number before dialing the extention. This worked on my WM phone and even the EVO 3D. Is there something different for the Epic Touch 4G?
You might try commas instead of p. This seemed to work for me on htc thunderbolt but do not know if will work on Samsung.
Doc
Thanks, that did it. A p on other systems seems to be a longer pause than a comma on this system but it works if you just add more commas as necessary. I tried semi colon as well - this will pop up on your screen and ask you if you want to enter the extension that follows the semi colon.
Great! Thanks for sharing information about the semi colon. Seems there are things hidden that we can keep discovering about Android OS.

[Q] Help with special characters

I saw too many threads, but I dont found any solution.
When I send special characters like, "á,à,é,i,ã,ó,ç", the other phone doesnt see it, or in some cases show garbage. I cant understand it. If someone could help me, I appreciate it.
See the image - i40.tinypic.com/jgqps9.png (I cant put link because of post's limit.)
I had a similar issue both with special characters and other alphabets (Cyrillic one)... In my case it wasn't a problem with my phone but with both service provider (that was strangely resolved very fast) and the recipients phone (which didn't support those characters).
So, have you tried sending this type of messages to other phones and was the result the same?
I send to mate of mine.
My phone - "simão", his phone appears "imo".
Thank you for reply.
I would try to send such a message to some other (models of) phones just to be sure whether this character limitation is imposed by your mobile service provider (which is less probable) or is plain inability of that particular phone you are messaging to encode such special characters...
Impossible to be limitation of my mobile. I have 100% certainty that be ROM's problem. I change it on sunday.
ROM - Runnymede AIO V3.0.5
Last ROM - leedroid. I hadn't any problem until sunday.
I tested swype keyboard, HTC_IME mod, LatinIME. No solution.
Very well then, that clears it up... It could be ROM bound problem... Hopefully you'll solve it by reflashing to another ROM since it appears that your current ROM is faulty in terms of character encoding, it has nothing to do with keyboards...
Although i had run some of the previous versions of the Runnymede AIO and had no problems with texting characters such as č, ć, ž, š etc. Sorry that I can't help you...
While didn't have any solution, I disable special characters (Messages-Settings-SMS-SMS characters-off)
Thank you for all your replys.
Best regards

[Q] HTC Sense 4.0 - Similar numbers mix up

I thought HTC would fix this issue in Sense 4.0...but they dont seem to have done it still...Anyone have any workaround?
Here's the problem -
If I have two contacts with similar numbers,
Say Mr. A with a number 1234567890
and Mr. B with a number 2234567890
HTC Sense is not able to distinguish between the two. It offers to link the two contacts and even though I dismiss this request, thereafter if I send a text or call Mr. A, it will show Mr. B or vice versa.
Please help!!!
What about if you set one with your country code e.g. +44112345678 and the other without e.g. 2212345678. It might be enough to confuse Sense that they are different.
Sent from my HTC One X using Tapatalk 2
That won't help either... It's designed to match just the last few digits specifically to ignore the country code or IDD it calling cards prefix.
Even old school Nokias used to do this.
It's annoying when you get that one in a million match, especially if they are commonly used.
You bet...and in my case it's a husband and wife who have similar numbers, so half the time i message the husband but it shows the wife's name when its been sent...i have stopped sending cheeky messages to this friend of mine lest they get delivered to his wife by mistake!!!
By default the One X will mach tge last 7 digits. If ur stock, i dont think u can do anything. But if ur rooted, u can increase itto 8 or 9 by changing the following in build.prop:
ro.phone.min_match.HTC__J15=7
Click to expand...
Click to collapse
Where HTC__J15 is the CID number (yours might be different) & 7 is the minimum number of maching digits (change it 8 or 9 as you wish).

[Q] Contacts not recognized when first name contains Umlaut (ä, ö, ü) or ß

Hi,
if you want to phone somebody - let's call him Jochen Altmann - you can dial J-O-C... (5-6-2...) and the contacts get checked for matches. The more letters you type, the less possible hits are displayed. This also works when you start by typing the last name A-L-T...
Strangely, this does not work if the first name contains an Umlaut (ä, ö, ü) or a German ß. If that is the case, the contact won't be displayed. E.g. if I wanted to call 'Jürgen Altmann', neither typing J-Ü-R... (5-8-7...) nor A-L-T... makes the contact show up. The contact is totally ignored, as if it didn't exist.
This problem does NOT appear, if only the LAST name contains ä, ö, ü or ß.
Also, the problem does NOT appear, if the first name contains any other special letter like é.
The problem seems to affect a number of people, not only my phone. And it seems to be a Fairphone issue, not an Android issue.
Any solution available?
Best,
smartn
Hi,
smartn said:
Hi,
if you want to phone somebody - let's call him Jochen Altmann - you can dial J-O-C... (5-6-2...) and the contacts get checked for matches. The more letters you type, the less possible hits are displayed. This also works when you start by typing the last name A-L-T...
Strangely, this does not work if the first name contains an Umlaut (ä, ö, ü) or a German ß. If that is the case, the contact won't be displayed. E.g. if I wanted to call 'Jürgen Altmann', neither typing J-Ü-R... (5-8-7...) nor A-L-T... makes the contact show up. The contact is totally ignored, as if it didn't exist.
This problem does NOT appear, if only the LAST name contains ä, ö, ü or ß.
Also, the problem does NOT appear, if the first name contains any other special letter like é.
The problem seems to affect a number of people, not only my phone. And it seems to be a Fairphone issue, not an Android issue.
Any solution available?
Best,
smartn
Click to expand...
Click to collapse
This is really an Android problem. Also because the search only matches the begin of a word you can not search for "rgen" for example.
_keesj said:
Hi,
This is really an Android problem. Also because the search only matches the begin of a word you can not search for "rgen" for example.
Click to expand...
Click to collapse
1. No, as stated before, this is NOT an Android problem - it did not occur on other Android 4.2.2 mobiles that I've tried.
2. You're right, the search term has to match the beginning of a word. But this is the way it works, no matter what specific letters the search term contains, so it's not a bug but the way it's meant to be.
Hello
smartn said:
1. No, as stated before, this is NOT an Android problem - it did not occur on other Android 4.2.2 mobiles that I've tried.
2. You're right, the search term has to match the beginning of a word. But this is the way it works, no matter what specific letters the search term contains, so it's not a bug but the way it's meant to be.
Click to expand...
Click to collapse
I did not look at the code I tried entering a few name containing special chars and once I was able to reproduce the problem searched the web for an answer:
I found the following thread from 2009!
https://code.google.com/p/android/issues/detail?id=3732
Thanks for your effort, _keesje, but after flying over a good portion of the 235 entries on the website which you linked, it seems to me as if they were dealing with another bug in the search function: the problem that a contact search is only limited to the names, so you can't search by company etc.
Surely a problem worth mentioning, but not the least helpful in the matter I'm dealing with - or did I miss anything? If so, please provide the number of the entry.
smartn
In the meantime, Fairphone has replied to my direct request:
"Thank you for your email. Our development team is aware of this issue, and we hope to include a fix the future update.
Cheers,
Rick"
I hope so, too.
But meanwhile, I'm still thankful for any other approach...

Categories

Resources