This post has been thanked 1 times. |
|
||||
Re: Lets talk about this radio ....
Quote:
__________________
|
|
||||
Re: Lets talk about this radio ....
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
|
|
||||
Re: Lets talk about this radio ....
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
|
This post has been thanked 1 times. |
|
||||
Re: Lets talk about this radio ....
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. Last edited by ruined; 11-13-2008 at 04:48 AM. Reason: Clarifications |
|
|
|