Thought I'd post this issue since I've run into it since I got my new G1. Possibly if someone has a well read blog it's worth posting there for Google to index! There must be others who have this problem. Anyway..
I moved all my numbers across via my SIM card. It seems the SIM cropped all the pluses (+) from the front of all numbers with +447... in my contacts. (+44 is UK code).
Now, a +447.. number is valid, and a 07.. number is valid, but a 447.. number is NOT!!
This I did not know. Now I need to fix 100+ numbers in my contacts.
Further to this, and G1 specific:
In Messaging if I send a message to a 07.. number it goes in a new thread. The reply will always (I think) come back with +447.. as the prefix. This means it starts its own new thread! Annoying at best.
I would recommend everyone change their numbers to use the correct +blah.. country prefix.
Also, the Messaging app could be a bit cleverer with parsing number prefixes when it comes to threading up messages . Android dev team reading??
Anyone else had this problem? Any comments?
mafro
I have searched the forum and could not find anything about this in regards to the Android OS, but there is some discussion about it for WinMO.
Caller name Identification is offered by some carriers but is not supported by Android. I would love to hear an answer from a developer if this is even currently possible on Android or not. Every phone I have owned, Nokia's from around the world, have had the feature, and since OS 3.1 the iPhone can now do it too.
The following link shows some examples of what the HEX stream looks like for the 2 different CLI formats SDMF and MDMF.
www dot homeautomationindex dot com/cidinfo.html
Can one of the developers please at least comment if this is currently possible, or do we have to wait for Google/Android to open up the API's to make this possible.
Do you mean something like caller id? White pages does this and even gives names of cell numbers, plus reverse look up.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Though it's not a new thing, I was very surprised that nobody have or made such an application. There are several topics on XDA related to this subject, in none there is given an answer or solution.
What I am talking about? I am talking about the display of an indicator (graphic and/or text) to show if an incomming call is diverted from another number (say you have one number that is diverted on your actual one and someone is calling the first one) or if you call somebody and your call is "waiting" cause the other party is already in a call (and has call waiting function active on his phone).
These are two things that are present in most Nokia phones, some Samsung or LG have it and also some Sony Ericsson. But I never saw it on an Android phone (maybe the Samsung owners have it, I don't know)
Is there so hard to make such an application for Android? I'm sure alot of us needs it and will even pay for it (I will). There was something created for WinMo devices called O2 Plus V2.3 that offered this functionality, I can hardly believe there's noone that can make something similar for Android. I've created a similar topic in the Legend subforum but...nothing.
This can help alot for ex if you have two numbers, a business and a personal one, and after working hours you're closing the business phone and divert it to your personal number. In case someone is calling, it's good to know if it was calling on your personal number or maybe on your business one....and there are many samples like this.
If the guys made it for WinMo devices (PPC) I'm sure it can be made for Android as well.
Similar threads on this subject (all with no answer or solution):
http://forum.xda-developers.com/showthread.php?t=787706
http://forum.xda-developers.com/showthread.php?t=352688
http://forum.xda-developers.com/showthread.php?t=407725
http://forum.xda-developers.com/showthread.php?t=361384
Hope to hear something positive on this...
OK. So I've partially solved the issues. Or should I say it was solved by itself.
Doing some tests today, I saw that THERE IS an diverted call notification on my phone.
It's not included in the Android itself, nor in the dialer but I found that is showing when I receive a call made to one of my diverted numbers.
I think it is MIUI related, it is the only ROM on which this was happening. I've tested with CM7.1 right now and regardless of which number I call (the "active" one or the "diverted" one), the incoming call display looks the same. For MIUI though, things are different, there is an "Forward incoming call(s)" row below the displayed number.
I've made several tests and for sure it is indicating when you are called directly or on another number that is diverted on your number. I also attached two print screens for the normal call and the diverted one.
Maybe some other MIUI owners can confirm this, but till now no other ROMs are offering this (as far as I know) and this will make happy alot of people. Still there's no notification in case you are calling someone and you are "waiting" but that was not as important as this one.
you might want to ask a MOd to close the thread as its already solved.
Skanob said:
you might want to ask a MOd to close the thread as its already solved.
Click to expand...
Click to collapse
Indeed, you're right, forgot about this.
Please close the thread
i upgraded from minicm7-2.1.9 to minicm7-2.2 and its showing me 'forwarded call' line below
i think cm7-2.2 have this feature also
using x10 mini pro
Hello Friends,
I have recently installed new Android 4.1 on my HTC Desire Z and wished that simple issue had been finally added to the software. But I was wrong...
Maybe any of you know how to customize Calling In (and maybe Call out) screen to see other contact info if exist like. Company name, address, work title etc.
Most of us does not have only Name and Phone Number in Contacts. I have more that 2000 contacts and many of them are same name like John from Company A and John from Company B. Unfortunately when they are calling I see only Name and Phone number (and picture where normally I do not have )
Please if there is any customization possibility to see more contact info when calling please help to solve it.
I had similar requirement.
I zeroed on DW Contacts Pro. Has what you require and much more.
Its available on play store just search.
iSLaND7 said:
I had similar requirement.
I zeroed on DW Contacts Pro. Has what you require and much more.
Its available on play store just search.
Click to expand...
Click to collapse
Free version looks promising however little overloaded with functions and possibilities. The Free version made my phone hand few times.
Thx for hint, I will try Paid version also.
Br,
KK
I'm working on a personal modding project, where I take the AOSP Dialer and add some features that I'd like to have. Long story short, for a component of this, I need to figure out how Google has been able to inject arbitrary audio into the conversation/call audio stream.
For years, discussion online, and especially on Stack Overflow, has insisted that:
There are too many upstream limitations, this is impossible
This is impossible, you have to play it over the speaker and hope the microphone picks it up
You can't do this, even Google says so
Indeed, even Google's up-to-date MediaPlayer documentation clearly shoots this down and doesn't mince words:
You cannot play sound files in the conversation audio during a call.
Click to expand...
Click to collapse
However, we know this isn't true. At least, not anymore, and not on Pixel devices. Google's Call Screening feature can "talk" to someone calling your phone, but that synthesized audio is never played audibly to the user. In other words, Google has been able play a Text-To-Speech stream of audio to someone calling your device, doing so silently, clearly to the listener, and without requiring the handset speaker or user's microphone to be "on."
Despite the fact that this is "possible" by virtue of "it has already happened," I can't find any discussion, documentation, info, or anything helpful about how Google has been able to do this. So, what do you do?
The next logical step is to start decompiling the app, but that's easier said than done. I'm by no means an expert in reverse engineering Android apps. Admittedly, you could consider me a beginner. Still, I've found a few things that seem useful, so here's what I've been able to find:
First off, when compared to the AOSP Dialer, the Google Dialer requires an additional privapp-permission that may be of interest: android.permission.MODIFY_AUDIO_ROUTING. I can't find much about what this permission does or how it is used, but it's definitely used by the Google Dialer, and on a stock Pixel 3 XL ROM, that permission is defined in /product/etc/permissions/privapp-permissions-google-p.xml as a privapp-permission.
Next, when decompiling the app, one of the first things I noticed is that a special "IMPL" package containing a playInternal function is class injected/loaded dynamically, and it's adjacent to MediaPlayer code that seems to play audio over a certain channel. The class it tries to load is:
Code:
com/android/dialer/audio/impl/CallAudioPlayer
However, that package isn't present in the list of decompiled classes (there's no "audio" folder under "dialer"), and despite playInternal being explicitly called by a string, there aren't any other classes that seem to define the playInternal function.
I don't know where XDA stands on posting decompiled code, but if you're using JADX, the area of interest is in defpackage/bhk.java.
But if I'm correct, this means that:
You can use MediaPlayer to play over the call stream, contrary to Google's documentation; you just need a special IMPL that allows for that behavior
This (probably?) requires the aforementioned MODIFY_AUDIO_ROUTING permission
If one were to obtain/locate and re-implement CallAudioPlayer.java, you could probably reproduce this behavior in the AOSP Dialer, or any other system app with the necessary permissions
If I'm not correct, then chasing down CallAudioPlayer will be a dead end. Still, the fact stands that Google did this somehow, so the answer must be somewhere.
So... that's where I'm at with this. I don't feel like I'll get much further without some help from more knowledgeable people, since I don't know where this CallAudioPlayer class is located. If it's in the base apk, but obfuscated, I can't find it. And if it's in a system framework or overlay APK, it must be using a different name, since no instances of CallAudioPlayer or playInternal exists in any of the relevant .apks on my system.
If this requires more sophisticated Android system/API modifications, that's fine too. This will end up on a custom ROM, so even if part of this behavior extends outside of the APK, any potential solution can be implemented in an AOSP ROM to achieve this functionality.
If you have any advice on how this may have been done, I really appreciate any and all discussion I can get on this. And if you don't know, I encourage you to ask a friend or someone who might be more knowledgeable when it comes to reverse engineering. Even if no one outright knows the answer to this, I hope to get at least some recent discussion on this topic, so that people investigating this in the future will at least have some sort of starting point.
Thanks for reading!
Hi. I'm no expert on Android (far from that haha) or Reverse Engineering. Though, I'm making an assistant installed as system app in a rooted Android and can also be compiled with the hidden and internal methods and classes so they can be used, like ITelephony, for example (https://github.com/anggrayudi/android-hidden-api) - btw, have you tried to mess with those classes and methods? (Sorry for my ignorance, I've no idea how it is to code/recode a ROM, what you need to use and stuff.) And anyways, I found something you didn't mention up there, so I'm unsure if you already know or not. From what Google says here (https://support.google.com/phoneapp/answer/9118387) in the "Screen calls manually" section, "Your Google Assistant screens the call and ask who's calling and why. You'll get a real-time transcript of how the caller responds.". Though, if it's their assistant doing that, not sure why that permission is on Dialer and not only on the assistant. Anyways, maybe that could be a good place to look at?
EDIT: Maybe also you (or anyone, of course) could look at sending DTMF tones over the call (I only made a quick search on Google, but there may be more that could help on this?). I think it's the same thing as it's inserting audio into the call. Though I can't be sure - btw, if it's really sending audio, then any Dialer app can already do that! But may not be that simple, so no idea at all. Maybe that's hardware thing and not software (>95% probable?). Just trying to give to ideas on where more to research.
Here (https://issuetracker.google.com/issues/36906273#comment107) it's said "I found this app, that can send dtmf after the call is made and active: https://play.google.com/store/apps/details?id=mobi.drupe.app (...)" - name: "drupe - Contacts & Caller ID" (just in case the app gets deleted from PlayStore and then people don't have their name to search for, only the package). If it's audio that it's being injected then it's possible, since that app seems to do it already, and the answer could be there too and might be good to look for the keys' frequencies on the code? Again, sorry for my ignorance on anything wrong I said. As I said in the beggining, I'm far from expert/experienced on Android.
I'll also be trying to search on how to send DMFT tones over a phone call. Could help, maybe. And if only a frequency could be sent for any reason, at least it's already cool to send some beep haha (preferably different from the ones of the keys or it might be confused with a key press by the other side, depending on who we're calling).
Late reply, did you solve this? I would like to build call features on Aosp. Best!