Related
Is it possible to make the phone button open the contacts app, at the moment it opens a screen where its gt all sorts of numbers, facebook contacts i dont want and all sorts,
mmm i agree.. that phone list is really annoying. it's got recent incoming and out going, then favorites, that all contacts including facebook.
i just want my google contacts in alpha order!
yh hope they add some options to change that up soon
Hide the keyboard and you get all your contacts
EddyOS said:
Hide the keyboard and you get all your contacts
Click to expand...
Click to collapse
what i mean is, the list that comes up in the "phone" menu should be the same as contact one, but its a misture of missed calles, dialed calls and facebook peeps
no, it shouldn;t be.
the call history is at the top as it is on all htc sense phones (Android and WM) so you can immediately dial your last few calls.
otherwise, you start typing the name of the person you want to dial, and up they come nice and quick.
Smart dialling like this has been in winmo since pocket pc 2002. of course they brought it across to android.
however, yes, the facebook stuff is bloody ridiculous.
Only thing that I find annoying is having 3 vesion of a phone number as it syncs Google, Facebook and Phone - surely it should merge new data and not duplicate it? I just want the data from Outlook's address book and then have them linked to Facebook if need be. It was cool that it did it automatically though
i think u can link them up manually
Back in September I read the original thread in our forums related to this missing feature: here
I've searched high and low in the contacts application and still cannot find this feature. Did I just completely overlook it or is it still missing in TouchWiz for EC05?
The option is still missing from TouchWiz. I use the app "Group to Voicemail" to accomplish this. Another option, if you have Launcher Pro, you can (from the home screen) hit menu/add/Shortcuts/Activities/Call settings/Auto reject list. This will put a shortcut on your home screen to this hidden setting. From within the Auto Reject List, you can add numbers from your contacts, call logs, or manually type them in. Remember to remove any symbols or hyphens from the phone numbers you add or it won't work.
Thanks for the response. Yea, I read up on that application before I made this post. I'm just not sure how I feel about paying $2 for the app when it's an Android native feature being disabled by Samsung. (Though, I know the app has way more features than simply send to voicemail that would warrant the fee.)
I may just try out "Mr. Number Call Block" for a bit.
When I call people, it's almost always voip or messaging via a bunch of different options.
I really really want to integrate these into one place.
I imagine a dialer that has different and quick to access options (if you can be bothered to open the attachment you'll see what I mean). HA! the upside down attachment
So, I want a list of contacts. I tap a contact and a menu of ways of contacting appears. then I can tap the method, maybe skype call, and it will call the number stored via skype. I tap video and it video calls via skype. Maybe I tap we chat or whats app or QQ or msn and then I can message them or send a voice clip, or whatever.
Calling from phones is really changing and the dialer is not keeping up.
I can't see anything that fits with what I want...
Any ideas?
Hi all, just a strange issue I am having I hope you can help me. I noticed when dialing by name when new, this phone kept wanting to bring up the home number when I want to dial the mobile by default. So, I headed into the contacts and discovered I could set the "default" number by either long pressing the desired number and selecting "set default" which then puts a blue check mark next to it, or I could be in the contact, press menu, then "mark as default" which opens a window where I can select the default email, phone number, etc which also will put a blue check next to the number.
Now then, all my contacts are stored on Google, nothing on the phone or SIM itself. For some reason, the default number for one of the most frequently called people in my address book will not "stick". I mark it as default, I can dial by name and it shows up correctly, but then the next time I go to do it (sometimes even 5 minutes later), it will be back to having no default number set and gives me the home number instead of mobile.
Oddly enough, the three other numbers I marked with a default number never do this to me and work every time, only the one contact entry doesn't work. I can't think of any other reasons why this is happening. My ONLY thought was that for some reason when syncing, Google keeps over-riding the marked default number. But why would it do it for JUST this one contact and not the other 3?!
Any ideas? Looking forward to thoughts. Kind of an embarrassing problem since it's so simple, but I can't figure it out...
www.google.com/contacts
Do you have more specific of a suggestion than simply giving me the site which I have already been to a couple times? The Google contacts interface doesn't seem to support "default numbers" and there is no way I could find to set a default number via the web interface. I believe the default number is an "on phone" setting. Thus, I am confused why it works on some contacts and not all.
Update: I noticed this same contact also won't upload changes to phone numbers, addresses, etc made on the phone for some reason, so this could be more of a Google sync problem. Again, it's only this one contact.
If I make changes to other contacts, they are reflected on Google's servers correctly. If I make a change to the phone number of this specific contact, after a few minutes, it goes back to what it previously was. It seems it's always pulling down from Google's servers and replacing the changes I made on my phone. It's like somehow only this contact was set to only pull down information, not upload it also. I also could not find any settings for changing the location of the "master" when there are changes or conflicts or anything like that on Google's website.
Anyone else have any suggestions? Thanks in advance.
Bump to the top, still have this issue.
Not much help here, as I'd love to know how to do this at a higher 'Google' level than just on my phone too. Are you syncing contacts with any other applications? For example, Facebook?
No, it's a stock Galaxy S4. Although you bring up another question I have had. When I have my contacts on Facebook synced "only with existing contacts", friends on Facebook still show up when I try to dial by name even though they do NOT show up in my address book. What's up with that? Is that the fault of Facebook? I seem to remember my HTC phone doing this as well, so I disabled syncing with Facebook contacts completely.
Today I tried removing the Google account, clearing the data and cache for contacts and contact storage, then adding the Google account again and letting contacts sync. I then set default numbers for 5 phone numbers. 10 minutes later, all but the one contact I have had problems with still had the default number set. The one contact cleared the default number - again. I just don't get it...
02CWRX said:
Hi all, just a strange issue I am having I hope you can help me. I noticed when dialing by name when new, this phone kept wanting to bring up the home number when I want to dial the mobile by default. So, I headed into the contacts and discovered I could set the "default" number by either long pressing the desired number and selecting "set default" which then puts a blue check mark next to it, or I could be in the contact, press menu, then "mark as default" which opens a window where I can select the default email, phone number, etc which also will put a blue check next to the number.
Now then, all my contacts are stored on Google, nothing on the phone or SIM itself. For some reason, the default number for one of the most frequently called people in my address book will not "stick". I mark it as default, I can dial by name and it shows up correctly, but then the next time I go to do it (sometimes even 5 minutes later), it will be back to having no default number set and gives me the home number instead of mobile.
Oddly enough, the three other numbers I marked with a default number never do this to me and work every time, only the one contact entry doesn't work. I can't think of any other reasons why this is happening. My ONLY thought was that for some reason when syncing, Google keeps over-riding the marked default number. But why would it do it for JUST this one contact and not the other 3?!
Any ideas? Looking forward to thoughts. Kind of an embarrassing problem since it's so simple, but I can't figure it out...
Click to expand...
Click to collapse
I have the same issue and it ticks me off every time, and it happens with any contact that has multiple numbers. There doesn't seem to be any way to choose the alternate numbers when you do search by name from the dialpad. you have to do it from the favorites or the contacts tab instead.
Does yours clear the default from EVERY contact that has multiple numbers? Mine only clears the set default number from ONE SPECIFIC contact, and I can't figure out what the difference between that contact and any other contact is. Or, if you are saying you can't figure out how to set the default numbers at all, I gave instructions on how to do it two different ways in the post you quoted.
As for selecting an alternate number from the dial pad, I figured that out too. So, let's say you want to call Mike. Dial 6453 (MIKE) and you should see the name pop up. To the right of the name is a down arrow with a number above it. The number is telling you how many contacts what you have dialed matches. Tap the down arrow and you will see a list of people and their numbers under them (or just the one person if that's all that matches). If you tap again on the name, you will in fact be given a choice on which number to dial (assuming the contact has more than one number saved for them).
So basically, it's a long annoying process that shouldn't have to happen, but it is possible to do it. You have to start dialing by name, then make a screen selection, then another selection, then another, then finally the dial pad is pre-filled with the number, but then you have to remember to hit the actual call button at the end of all that crap. I find it's easier to find a text from the person and swipe the screen to dial them that way sometimes (or from within the text tap the call icon), or from the call history tap the call icon. Or of course as you said, favorites or contacts.
My HTC used to just let you dial by name, tap the number you wanted, then it would start calling. Easy peasy.
Bump to the top again... Still trying to figure this out. So annoying.
Bump. I dial this number every day...
Some stupid questions: 1. Do you have more than one contact details of the same person? 2. Did you delete and re-add the contact. Also delete from all other syncs?
Sent from my Nexus 7 using Tapatalk 4 Beta
The contact is only listed as a Google contact, and has no other links or connections from other sources. Facebook is not synced, nor is anything else. It's only Google contacts. I haven't tried deleting and re adding yet. I guess that's a simple thing to try, its just that there is a lot of info in there, haha.
Ok, via web browser on the PC I exported the contact, deleted it, and synced my phone. Contact was gone. I then added a contact via web browser, typed in all the same info, synced the phone, and the contact is back. I then selected the mobile number, marked it as default, synced the contacts again, and there was no longer a default check mark next to the mobile number.
I have at least 3 other contacts where I don't have this problem at all. They are all stored on Google, they are all friends on Facebook (even though they aren't linked to FB in the contacts because of the above listed problem where everyone on FB shows up when dialing by name), they are all in circles on Google Plus. I can't figure this out at all. What the heck...
I'm trying to solve a problem for Google Voice users, and looking to pick the brain of someone who may know a thing or two about how Android handles SMS, particularly how an app can be set to be the "default" for messaging.
What is my goal, you ask?
Make it possible for Android users to default all new messages from their Google Voice number, rather than the carrier. Yes, you can just remember to initiate a message inside the Google Voice app, but when responding to a missed call or clicking on message from a contacts screen, it will open the system's default SMS app and send from the carrier number instead. Confusion often ensues when the recipient doesn't recognize the number. We're trying to avoid that, as many of us GV fans use it as our primary number and don't know or care what the carrier # is. In other words, we want to avoid sending from the carrier if at all possible.
But doesn't Hangouts do this already?
It did. While Hangouts supported SMS, we could set it as the default app and then tell it to use Google Voice as the default for all new messages (rather than the carrier). This worked pretty well... anywhere in the OS that you want to initiate a message (call log, contacts screen, etc), it would open hangouts screen with GV as the sending service. But now that they are killing SMS support in Hangouts, it seems they are also removing the ability for it to be the default for all messages. They're actively pushing users to switch to another app for SMS, and you can't set it as the default currently unless you install an older version first. Eventually it will probably stop working altogether.
Why not just set the Google Voice app as the default for messaging?
It seems Google does not want us to be able to do that. The app does not have the option to. I'm wondering if it is because it doesn't actually support carrier SMS messages, and perhaps that would create a conflict in OS experience design? I'm not sure.
What is your proposed solution? Making a new SMS app from scratch is a lot of work, and Google's third party support for Google Voice is very limited...
I understand. Realistically, what I'm wondering is, would it be feasible to create a very simple forwarding app. In other words, a small third party app that could be set as the default for messaging, which could just forward the new message request to another app? Google Voice shows up as an option to send messages from other screens, such sharing an image or link. Heck, so does Hangouts (which will still support Google Voice integration, just not the ability to be the default app). The problem is when initiating a text from the dialer, contacts, or call log, it doesn't give us a context menu to choose from. It only goes to the default app. What I want is the ability to intercept that request and then choose the app to default to ourselves! Preferably the Voice app, but even Hangouts would be acceptable... or if possible let the users decide!
Possible pitfalls are
1) Do apps that support being set as default messaging require being able to actually handle carrier SMS? I could understand if that was a requirement from a UX design perspective, but is it actually an OS limitation or is it possible? I recall hearing once that the FB messenger app supports being set as default for messaging, but I don't understand how that could work, and I haven't found reference to it yet (don't use FB messenger personally).
2) If the Android OS would allow it, would it actually break carrier SMS? I know setting Hangouts to be the default moves all carrier SMS into Hangouts, and if switching to another app it would move the messages to that one. If my proposed forwarding app works, would carrier SMS messages just go nowhere? Occasionally the carrier does send a service announcement or bill reminder, etc, and I think it might be important for those to go somewhere. Or maybe not... I'm not sure how the OS handles this.
3)When a request for a new SMS is made, is the request done in a way that can be re-parsed for another app to handle? I really can't find much or any documentation on how this is handled, but I know the information is out there since Android supports third party SMS apps.
I have had trouble finding documentation about how any of this works from a developer's perspective, so I'm hoping someone where could shed some light on whether or not my idea is dead in the water before I pour too much effort into trying to figure this out. Thanks!
Did a little digging after I posted this and found some info on some dev forums elsewhere.
Seems, as I feared, that in order for an app to be supported as "default" for messaging, the requirement is that it include the handlers for SMS/MMS. This appears to be because whatever app is set as default for messaging is the app that is responsible for receiving and storing said messages. So if my app proposed above were simply to forward messages to another app, and not actually handle carrier SMS/MMS at all, any messages that DO actually come in from the carrier (notifications, payments and outages, etc, which I get from time to time) wouldn't go ANYWHERE and cause a great big user experience flaw.
So that answers some of my question. The next bit is... can incoming messages be forwarded to another app, such as the Android Messaging app that they are trying to make the new standard? Then perhaps this idea could still work. It might make more sense for a pre-existing Messaging app to simply support forwarding to google voice on new messages (or heck, Google should add GV support to Messaging), but I'm not sure how realistic that will be.
I've been thinking about this problem for a while, too. Both Hangouts (for those who have GV linked to it) and the GVoice app probably still have specialized intents to receive message data, so that they can forward them along; the key is to find out what to send to these apps.
I see the problem as only one-way: basically, capturing SMS intents as the default messaging app, then sending the user either to the message-entry screen in the target app (GV/Hangouts) or sending the message directly if that was in the intent. And I thought that there might be a less hair-pulling way to do it, by creating a messaging "shim" app:
* Use an existing, plain vanilla SMS app as a basis. For instance, just pull the one from AOSP. In addition to the new functions below, it will take care of carrier SMS.
* Offer a setting to choose where outbound SMS goes by default: in-app (carrier), GV, Hangouts, etc.
* Add a screen banner saying something like "Carrier SMS" or showing the carrier's phone number.
* If the default outbound app is not in-app for carrier messaging, add a screen icon for jumping into that default-messaging app set by the user.
In this simplified setup, there's no need to handle _inbound_ SMS via GV/Hangouts at all -- because that app will pop up its own notifications, and jump into its own app when its notifications are tapped. Similarly, notifications raised by this customized SMS app, from carrier SMS, would go into that app. No special logic required for any of this, simplifies things a lot.
The end goal from a UI perspective would be, _if_ the user chose a default outbound app other than this one, then the following behaviors would be received by this app and forwarded along to the target outbound SMS app:
* selecting the SMS icon for a contact would, via this app, open GV/Hangouts with that number ready for message entry;
* sending a fully formed SMS via any app, e.g. voice entry via Google App or Assistant, would be forwarded to GV/Hangouts for immediate sending.
(EDIT TL;DR: The problem, distilled, is how to make *initiating a new message from elsewhere* use the real desired app; the desired app will handle it from there.)
The UI problem here is that it will be sort of a "dummy" SMS app. It will handle carrier messages, but there will be people who don't even get carrier messages (FreedomPop comes to mind), so it's another app icon to ignore. Still, it would be the fastest path to resolution and, for most users, would act as a "shim" between native SMS handling and GV/Hangouts (or maybe even other messaging apps?).
---------- Post added at 07:14 PM ---------- Previous post was at 07:11 PM ----------
FWIW, I do understand Android development, though I'm totally green on UI elements. So if you already have some technical know-how here, I'm happy to collaborate to help make this happen. I think this would be soooo much better than having to shove in Xposed (which slows down Lollipop and later) and use XVoice++.
i have just started developing on android. am a new bee with very little knowledge. i have read you post and it had given me some food for thoughts for my messaging app. i liked your idea and wanted to know about your progress. i want to collaborate in your project if you are interested.