Background on the Jack
"It's universal for all brands of phones, so it must have a name" it actually isn't. There have been many phones over the years that have used various connectors. The "standard" technology is not a formal standard like what you consider things like any of the IEEE standards. The industry has just evolved over time to tend to use what we all know as a audio jack.
The typical audio only jack has 3 rings, usually call Tip, Ring, Sleeve (TRS). These typically map to Left, Right, and Ground. Phone manufactures wanted to make this jack work with existing headphone so they used a connector with 4 rings, called Tip, Ring, Ring, Sleeve (TRRS). These map to Left, Right, and ground just like the 3 ring, but the final connector maps to a microphone. This makes it so that if you plug an audio only cable into it, the microphone input gets connected to ground so nothing is hurt. It also means that if a headset with microphone is connected to an audio only device, the microphone is connected to ground, also hurting nothing. There are similar connectors in 2.5mm (used on some phones to save space), 3.5mm (for phones, mp3 player, etc) and .25" (for larger headphones, guitars, etc).
Data on the Jack
As far as what "data" travels over this, it is purely analog. Some people have reused these cables to pass serial data over them, but they are very application specific. For the case of devices using the jack for other purposes, they can do whatever they want as long as the signal on the line is band-limited, meaning that there isn't any high frequencies being used. The reason for this is that there are filter on the input that block frequencies too high. This frequency will change depending on the device itself but is usually around 12 KHz or so.
The method that people send data over this are usually all pretty similar to how phone line modems work. The general concept is that there is a mapping between the frequencies being transmitted and serial data. If you wanted to reverse engineer a system, you would need to record the line and look at what frequencies there are. The hard part is to figure out what the resulting data is supposed to mean.
2 Way Communication
I would also like to note that 2 way communication is possibly in these systems. The microphone line is used to send information to the phone and the audio out lines are used to send information back to your external device. If you are trying to reverse engineer a device, you will want to look at Mic, Left, and Right to see if there appears to be any bi-directional communication.
Reverse Engineering
I mentioned that reverse engineering would be the difficult part. Here is the method I would go about doing this:
- Check to see what lines have data on them. You can use a computers audio jack to capture your data with. This will probably be the easiest method to look at the data.
- Determine the symbol rate. Basically when you look at your captured data you should see very specific points that the frequencies change.
- Look to see if there are discreet frequencies being used, and how many are used at the same time. For example, there could be 6 KHz, 8 KHz, 10 KHz, and 12 KHz. These could map to 4 bits per symbol. So if you see 6 and 8 at once it may mean 1100 (or maybe 0011). Look a the next symbol and it could be 6, 8, and 12 and could mean 1101. Of course if it is a custom protocol, it could really mean anything they want it to. But this will at least give you a start.
- Assuming you collected the data running a card that you know the data for, you can look for patterns. Here is the information included on the cards. You could do things like if your card has a short sequence that repeats look to see if your symbols have a similar repeating pattern. Once you get some of these patterns worked out, you should be able to do a 1 to 1 comparison for the rest of the numbers, You should eventually be able to get a pretty good idea of what is being sent.
There may be some data sent that has nothing to do with your card and you may never know what it means, but as long as you know the position of the data you care about, that is all that is needed. You just have to hope that the hardware manufacture didn't put any "anti-hacking" or "anti-reuse" measures in place. Potentially the designer could have used bi-directional communication to provide encryption. It is also possible for them to just mix all of the data up so it is hard to figure out what is what. I would say it is unlikely that they have done any of this though.
You have a lot of questions in this post. Next time, I recommend splitting them into a separate posts, or at least numbering them.
1) Yes, you can get 5V from charging USB cable. This will work just fine.
2) Yes, two-resistor approach you are describing is good, as long as you use it with right kind of output (push-pull or open collector). The schematics you have shown assume push-pull outputs, while FT-330 is open collector (you can tell because they require pull-up resistor). It is not clear what kind of output adafruit meter has, but presumably push-pull, since there is no mention of pull-up resistors.
3) I am not sure why you need op-amp at all. It will not hurt, but you should be able to just connect output to microphone's input. The output voltage will drop a bit, depending on phone's input resistance, but this may not be a problem. Only add op-amp once you have established the phone provides too much of a load.
4) The reason your op-amps do not work is because you made an wiring error. From your schematics, your Vcc should always be 5 volt. If you do not see it, triple-check you have assembled everything properly.
extra: from your screenshot, it is clear you have a capacitor on your microphone input (likely inside the phone). As you can see, this has an effect that an 'average' voltage one the input will be 0 volt. You can see it on the graph -- if you give, say +5V volts, then in few tens of ms, the capacitor will charge to +5V and the input will see 0 volts(+5 - +5). If you now give 0V on input, the card will see -5 volts (0 - +5V). But soon, capacitor will discharge and you will see 0V again.
Best Answer
The Android spec. gives details
This article shows some good ways to make a volume control. Basically it is just some buttons switching in different resistors between a couple of pins of the 1/8" TRRS headphone connector. Normally these buttons would put the resistor across (in parallel with) the microphone.
A standard microphone needs two wires: The mic output signal and GND. But the mic also needs power, and this is provided on the same wire as the mic output signal. Inside the phone there will be a resistor between the mic signal and power. Our remote volume control will switch in a resistor between the mic signal and GND. These two resistors will form a simple resistive voltage divider, where the resulting voltage depends on which button is being pressed.
Inside the phone this mic signal goes into a simple analog-to-digital converter (ADC) that will measure the voltage and figure out from there what button is being pressed.
Doing it this way is a little tricky and creates some compromises. First thing is that you can't use the mic and the buttons at the same time. Most of the time this is not a problem, but occasionally you'll want to mess with stuff. The phone has to mute the mic whenever a button is pressed. Otherwise there will be a loud pop in the audio. Even if this wasn't an electrical problem, most remote volume controls also house the microphone and you would get a lot of mechanical handling noise in the mic just from moving your fingers around.