Touch Pro 2 FM Radio Questions/Answers - Page 8

Borg561 · #71 (**permalink**) 09-26-2009, 12:55 AM

Quote:

Originally Posted by Dragon2

yes, the fm radio works great on my tmobile tp2..

Would it be possible for you to search the registry (skip the HKCR hive and start with HKLM) for "4325" to see if you've possible got some entries we don't on the CDMA models (or if they differ). A search for "fm" probably wouldn't hurt either.

Justin

gman4471 · #72 (**permalink**) 09-26-2009, 02:02 AM

I don't think this is something that the registry is controlling.

So far, the PDFs that have been posted are primarily marketing docs / block diagrams and not very useful for development.

What we would need to make this work is the full technical documentation that specifies how the developer is supposed to interface with the chip.

Here is an example from TI:
http://www.ti.com/lit/gpn/omap3530

And an even better one from NEC:
http://www.necel.com/cgi-bin/nesdis/...17987EJ2V0IF00

You will see in those examples how the spec documents almost everything right down to the pin. These docs can easily be over 100 pages in length which should help narrow down your search. Sometimes they will come in a .zip file with sample layouts and code, but to get that stuff you will usually have had to sign an NDA which would prevent you from distributing it.

If you can find something like that for this chip, or even one very similar to it, we could have a good chance at making this work.

Side note, isn't the 4325 also compatible with Bluetooth 3.0:

http://www.engadget.com/2009/04/23/b...ets-certified/

==Update==

Did some more digging and found out that the 4325 is used in Android devices and that source code for these drivers has been released. Here's a vid of someone using sample application that is provided to developers by Broadcom to operate the FM radio: http://www.youtube.com/watch?v=xgGXKJg8bOo http://i-miss-erin.blogspot.com/2009...n-android.html

This could help point things in the right direction

Mutiny32 · #73 (**permalink**) 09-26-2009, 04:06 PM

Quote:

Originally Posted by gman4471

I don't think this is something that the registry is controlling.

So far, the PDFs that have been posted are primarily marketing docs / block diagrams and not very useful for development.

What we would need to make this work is the full technical documentation that specifies how the developer is supposed to interface with the chip.

Here is an example from TI:
http://www.ti.com/lit/gpn/omap3530

And an even better one from NEC:
http://www.necel.com/cgi-bin/nesdis/...17987EJ2V0IF00

You will see in those examples how the spec documents almost everything right down to the pin. These docs can easily be over 100 pages in length which should help narrow down your search. Sometimes they will come in a .zip file with sample layouts and code, but to get that stuff you will usually have had to sign an NDA which would prevent you from distributing it.

If you can find something like that for this chip, or even one very similar to it, we could have a good chance at making this work.

Side note, isn't the 4325 also compatible with Bluetooth 3.0:

http://www.engadget.com/2009/04/23/b...ets-certified/

==Update==

Did some more digging and found out that the 4325 is used in Android devices and that source code for these drivers has been released. Here's a vid of someone using sample application that is provided to developers by Broadcom to operate the FM radio: http://www.youtube.com/watch?v=xgGXKJg8bOo http://i-miss-erin.blogspot.com/2009...n-android.html

This could help point things in the right direction

EXCELLENT information!

This issue brings something to mind about a similar issue where Verizon got caught disabling bluetooth features on their phones through the software. As I recall, the FCC didn't like this and they were also hit with a class-action lawsuit and lost. It was only a partial block of features, but an intentional and un-needed feature nonetheless. They had to pay hefty fines as well as not block certain bluetooth features on any phones in the future & make a software update available to all users of existing phones in which the block was in place.

Since it is known and advertised that the BCM4325 does Bluetooth 2.1+EDR (3.0 in the future), WiFi, and FM radio, we can file complaint. Especially since there is no FCC restriction on the use of FM radio in conjunction with Bluetooth, CDMA, or WiFi technologies in the US. To further strengthen this, the GSM (actually it does WCDMA through UMTS, which is CDMA as well) handsets sold in the US through other carriers have this capability. When you install the HTC FM radio cab on a CDMA device, the hardware is active, but there is a software disconnect somewhere. You can tell when you plug in headphone/antennas and it is detected. To take it even further, the registry for both the Sprint and Verizon phones have several references to init strings that appear to have missing key values to allow for complete functionality of the FM radio.

I'm not going to give Sprint, Verizon, or HTC any warning. They've all been asked and it's comes down to corporate marketing to discourage competition with their own OTA pay music services. I'm filing a FCC complaint and a complaint with the Kansas/Missouri Attourney Generals' Offices. I encourage you to do the same. I'm not sure if it falls under trade secret, but since Broadcom has released the source code for this chip, it is no longer under NDA or trade secret. I've had it with tech companies intentionally crippling hardware to force you to purchase something that would otherwise be free.

Since the FCC is currently investigating Apple/AT&T for disallowing Google Voice applications on its store because it would allow for cheaper competition, I'd say HTC/Sprint/Verizon might want to just appease us and turn bad press into great press.

Excuse me, a nerve just got struck. I've got so many devices that I am paying for that are capable of so much more and yet the provider chooses to block it with software to force me to pay for a service or feature that would otherwise be free to me. But I am filing the complaints.

transcend73 · #74 (**permalink**) 09-26-2009, 05:46 PM

Quote:

Originally Posted by Mutiny32

EXCELLENT information!

This issue brings something to mind about a similar issue where Verizon got caught disabling bluetooth features on their phones through the software.
--edited for brevity--
Excuse me, a nerve just got struck. I've got so many devices that I am paying for that are capable of so much more and yet the provider chooses to block it with software to force me to pay for a service or feature that would otherwise be free to me. But I am filing the complaints.

Well said! I agree 100%. =D>

Borg561 · #75 (**permalink**) 09-27-2009, 11:15 AM

Quote:

Originally Posted by Mutiny32

I'm not going to give Sprint, Verizon, or HTC any warning. They've all been asked and it's comes down to corporate marketing to discourage competition with their own OTA pay music services. I'm filing a FCC complaint and a complaint with the Kansas/Missouri Attourney Generals' Offices.

Excellent idea and I will consider doing the same. You can file a complaint with the FCC online, but you're limited to 1000 characters. I think you can submit more information via fax/e-mail/snail mail, but it's probably easier to type a letter and snail mail it. A little heads up too, it can take a while to get an acknowledgement back from the FCC, even if you file your complaint online. A while back I filed a complaint online about Verizon (billing/refund issue) and it took about 2-3 weeks before I got something back simply saying they had gotten my complaint and would look into it. Not trying to stop you from doing this, just letting you know not to expect to hear back right away.

PS. Don't forget that the FCC is already investigating AT&T and Verizon Wireless.

Edit: Might not hurt to include information from this post about HTC and Verizon's responses when asked about the issue (HTC saying Verizon wanted it disabled [indicates the hardware functionality is there] and Verizon saying Marketing decides what features to include [marketing wants you to pay for music from their service]). Heck, provide a link or printout from the FCC docs showing the Broadcom chip, and include information from Broadcom indicating it includes FM Radio functionality.

Justin

#76 (**permalink**) 09-27-2009, 05:43 PM

This is probably a stupid question but has anyone tried installing the FM Radio cab to see if it will work? There was one on http://forum.xda-developers.com/showthread.php?t=427040. I tried installing but it said it wasn't digitally signed. I figured it was worth a mention even if it is more than a long shot.

8notime · #77 (**permalink**) 09-27-2009, 06:50 PM

Quote:

Originally Posted by 12stringchap

This is probably a stupid question but has anyone tried installing the FM Radio cab to see if it will work? There was one on http://forum.xda-developers.com/showthread.php?t=427040. I tried installing but it said it wasn't digitally signed. I figured it was worth a mention even if it is more than a long shot.

Yes, and it was discussed several pages back. It does not work on the CDMA version of the TP2.

k0nker · #78 (**permalink**) 09-27-2009, 09:27 PM

hey people i got my fm radio work, i got a Touch Pro 2 T-mobile, im not sure if work on other or if somebody a http://forum.xda-developers.com/showthread.php?t=549601 lready leave the link but heres the link heres http://www.youtube.com/watch?v=YVh3F7_nrZA a video