Lets talk about this radio ....

**jakdillard** · #1 (**permalink**) 11-07-2008, 10:12 PM

Ok so I have took a couple of attempts to try to get the radio going I've gotten as far as initializing the radio getting it to search for stations and yes even had a successful lock the problem now is there is no sound from the internal speaker or the headset .... In my opinion it has been locked by the carrier or htc .... if you use my rom as a base you will see that I have the fm radio driver and initializing file in there .... do I think there is a way around getting the radio fully operational yes I do but at what cost .... will a rom do this NO at least not on the surface ... I think that this may be one of those wild goose chases like trying to get the wifi to work on the vogue .... where the hardware supports it but the carrier doesn't ... Now the diamond on the other hand I had no problem getting it to work on it but the sound was low but why .... maybe sprint forgot to lockup the function ..... so where is it locked down its not in the rom is it in the kernel or the spl .... huhmmmm

**no2chem** · #2 (**permalink**) 11-07-2008, 10:37 PM

Quote:

Originally Posted by jakdillard

Ok so I have took a couple of attempts to try to get the radio going I've gotten as far as initializing the radio getting it to search for stations and yes even had a successful lock the problem now is there is no sound from the internal speaker or the headset .... In my opinion it has been locked by the carrier or htc .... if you use my rom as a base you will see that I have the fm radio driver and initializing file in there .... do I think there is a way around getting the radio fully operational yes I do but at what cost .... will a rom do this NO at least not on the surface ... I think that this may be one of those wild goose chases like trying to get the wifi to work on the vogue .... where the hardware supports it but the carrier doesn't ... Now the diamond on the other hand I had no problem getting it to work on it but the sound was low but why .... maybe sprint forgot to lockup the function ..... so where is it locked down its not in the rom is it in the kernel or the spl .... huhmmmm

either the physical hardware is locked down, or the SPL is preventing access to the chip.

leoiden · #3 (**permalink**) 11-07-2008, 10:41 PM

what about comparing the spl from sprint diamond and touch pro ??

**jakdillard** · #4 (**permalink**) 11-07-2008, 11:14 PM

Quote:

Originally Posted by no2chem

either the physical hardware is locked down, or the SPL is preventing access to the chip.

humm ok no2 how can we go about checking the spl to see if its there because I don't think the hardware is locked because we can get it to initialize just by adding files to the OEMDrivers folder but it can't find stations so correct me if I'm wrong but the spl has to do with the radio's functions right ? is it possible to rewrite the SPL or at least do some reverse engineering to it

**jakdillard** · #5 (**permalink**) 11-07-2008, 11:47 PM

also what about nk.exe could it have a line in there to do with it

**no2chem** · #6 (**permalink**) 11-08-2008, 04:55 AM

Quote:

Originally Posted by jakdillard

also what about nk.exe could it have a line in there to do with it

nope, its the spl/ hardware lockdown, nk has nothing to do with it.

**hibby50** · #7 (**permalink**) 11-08-2008, 09:57 AM

i tried to cook it into my rom as well with the same results as jd

**jakdillard** · #8 (**permalink**) 11-08-2008, 12:16 PM

Quote:

Originally Posted by no2chem

nope, its the spl/ hardware lockdown, nk has nothing to do with it.

ok no2 when do you wanna attempt to brick this device ( tamper with the spl to see if we can come up with something ) I got insurance I'm game ... thats if its possible

ls3mach · #9 (**permalink**) 11-09-2008, 05:17 PM

Someone fix this please.

ruined · #10 (**permalink**) 11-13-2008, 04:30 AM

Just a little note: I have been playing with this and I could be way off but it appears FMS.DLL calls BTHCI.DLL to communicate with the FM portion of the 6350. The touch CDMA uses version 1.43 of this and the touch GSM uses 1.90, any chance this might be some driver mismatch in the bluetooth section causing the error? (it does appear the, chip initalization files are all the same "TIInt_x_x_x.bts") Both BTHCI.DLL versions do call HCI_FMXXXX but possible there are some other differences or supporting DLLs, or the CDMA has the 6300 which has no FM radio, there is an init file for this chip....

Just changing BTHCI breaks the radio completely, so there do appear to be differences, though I am not sure my method on this was correct.