The main TB thread long ago, put some venom on my posts here. Expecially looking new users registering here just for pretend a request and leaving. Or persisting till banned.
Or blaming against this product as fake/steal money/ fraud.
Still happens.
Maybe the reason of my attitude here.
Apologizes if someone felt offended of my behaviour.
I'll try to post in a better way.
Yeah, it's me Dj Barth "One TrueBlue to rule them all, One Browser to find them,
One TB CFW to bring them all and in the Internal HDD bind them
In the Land of BarthMordor where Modding lie"
I'm trying to procure a copy of IDA Pro (through legitimate means), as I've been slowly increasing my knowledge in ASM, and overall Cell based architecture. Currently I've been playing on a co-workers station during his smoke breaks of all things.There are some references you can find through the unpacked, decrypted, update files, of 3.70+ that make reference to the additional hardware necessary. I've looked just maybe 10 minutes into it, but it looks like it'd be fairly simple to incorporate what you request into a repackaged 3.55 CFW. Since you are on True Blue, it may be a better route to create a solution you can mount in a dev_blind folder. I don't think the true blue would have an issue with the changes necessary. I don't own the dongle, and have never looked at it, though. The headset requires 3.70 for surround sound, as you have found out obviously. There are a few calls that are missing in the True Blue firmware (or any 3.55, though I haven't looked much through any update besides 3.55, 3.56, 3.70, and current firmware). A co-worker was able to borrow a headset and pull the device ID (for simplicity sake) and find multiple other references for me, but I haven't been able to look at them further.
It's a little odd though, because it seems this particular headset is referenced in a peculiar way, when compared to other random headsets, or my Logitech driving wheel. I'm going to purchase a headset later today if I can find one, and look a little more into it. But honestly, from the little headstart I've done, a competent developer more familiar with the PS3 than I am, could implement a workaround for you without much effort. Hopefully one will step up for ya, because I'm relying on a co-worker for now, and its still a learning project for me. If I (or my coworker) can help you out anymore, I'll respond back.
Thank you for you post and time.
Windows see usb transmitter device id: USB\VID_12BA&PID_0030&REV_01>?&MI_00 (device fully workable in Win7)
You read my mind, I was actually about to PM you to ask for any details of your headset when viewed in Linux or Windows. If you'd like to see something interesting, look at details of the headset when on a PS3 Linux Distribution, versus a regular Linux distribution. It's odd but interesting. Thanks for the information. I asked a ps3 developer a few questions regarding this, and he suggested that before tearing apart sprxs and firmware packages, to see if you can simply "clone" a similar headset, so the PS3 sees a early generation headset that works fully on the ps3. He mentioned having to do something similar while trying to get the older, Chinese PS3 controllers, that stopped working after updating to 3.55. It may limit the features of your headset, (whether you get real surround sound that's advertised, or just stereo/mono), but it could be a quick dirty solution to at least get the headset working for ya. He was able to get his older controller completely working, but never released anything, as each knockoff, even an identical one he bought at the same time, needed to be worked in manually. I'm hoping he'll let me look over his work on that, to see if I can just do a quick few changes and see the results.
You read my mind, I was actually about to PM you to ask for any details of your headset when viewed in Linux or Windows. If you'd like to see something interesting, look at details of the headset when on a PS3 Linux Distribution, versus a regular Linux distribution. It's odd but interesting. Thanks for the information. I asked a ps3 developer a few questions regarding this, and he suggested that before tearing apart sprxs and firmware packages, to see if you can simply "clone" a similar headset, so the PS3 sees a early generation headset that works fully on the ps3. He mentioned having to do something similar while trying to get the older, Chinese PS3 controllers, that stopped working after updating to 3.55. It may limit the features of your headset, (whether you get real surround sound that's advertised, or just stereo/mono), but it could be a quick dirty solution to at least get the headset working for ya. He was able to get his older controller completely working, but never released anything, as each knockoff, even an identical one he bought at the same time, needed to be worked in manually. I'm hoping he'll let me look over his work on that, to see if I can just do a quick few changes and see the results.
Uhm. Am i wrong or deank said he has this headset, and it's working without special sound features yet?
Agree, unbranded ps3 controller libraries reactivated could be awesome.
Yeah, it's me Dj Barth "One TrueBlue to rule them all, One Browser to find them,
One TB CFW to bring them all and in the Internal HDD bind them
In the Land of BarthMordor where Modding lie"
3.70+ and win7
This device works by usb transmiter (by self protocol) and provides all ingame sound and mic and speech, like no other bluetoth headset thot provides onli mic and speech
3.55 can work like other headset only for mic and speech on standard bluetoth protocol
so troble in missing usb transmiter drivers on 3.55
Not trying to derail your thread but Ive often wondered if it would be possible to import the old 3.41 Control Pad drivers. I lost 3 "OEM" controllers with the 3.55 update
They look exactly like my original controller but I bought them from DX in China and that update wiped out all those "dodgy OEM" controllers
Bring them back to life with MotionInJoy then, if you can that is.
Uhm. Am i wrong or deank said he has this headset, and it's working without special sound features yet?
Agree, unbranded ps3 controller libraries reactivated could be awesome.
There is an older, bluetooth headset that doesn't require a dongle (or USB transmitter). I believe this is the headset that he is referring too. But I could be wrong. Oops, ctmd gave a good explanation already. Nevermind.
I haven't been in contact with the guy helping me in the last 24 hours, to see if I could continue on his work with porting the controllers over. It sounded like it would involve having to create almost a device whitelist, which I'd have to personally add information from every individual controller into. I may have misunderstood him though. Even if I had to do that, it would be simple enough to have a post, where users can make a request, and a quick custom solution is sent to them so their individual controllers will work with their console.
Even if that is the case, it would be fairly simple for me to rig a problem up, where you could hook up the non-working OEM controller into your PC, and the program gathers the device ids required, and outputs a pkg file that can be run to enable that console to use that controller (or controllers) again. I'm assuming a similar solution could be developed for PS3 Linux, so a PC wouldn't be required. Later on, a crafty pkg could be developed that does the required reading and patching from GameOS. (think of the progression of how we had to enable the QA flag. Started with a lengthy, time-consuming process that was to difficult for some, to the super easy PKGs put out by Rebug and similiar.)
I may be naive, but I think there may be an easier way, in layman's term, to change accessory compatibility in 3.55 to the same as 3.41. It may make a few devices not introduced until after 3.41 stop working, but I doubt it. Even if it did, it'd be much easier to just patch in those few changes.
My co-worker has gotten intrigued by my snooping around, and decided to help me out more. I'm hoping my co-worker, the developer who I've been pestering for help, and my amateur talents may be enough to work out a viable solution for each item. As Dean said, I don't care if there's only one person who ever uses it, that's good enough for me.
If a pkg is able to reenable permanently ( either if loading this pkg is needed every time) unsupported devices , not touching our TB CFW but just as a plugin, well, would be amazing
Yeah, it's me Dj Barth "One TrueBlue to rule them all, One Browser to find them,
One TB CFW to bring them all and in the Internal HDD bind them
In the Land of BarthMordor where Modding lie"
Am i wrong or someone else open a thread weeks ago, about this
Just so you know, this is just a forum with some chit chat about TB, like billion others, not the TB Team forum. IF your request will not be accomplished, don't be surprised
I suggest you to try to ask this request to Deank, as a new feature for his MM. Higher chances to see your device working
Yeah, it's me Dj Barth "One TrueBlue to rule them all, One Browser to find them,
One TB CFW to bring them all and in the Internal HDD bind them
In the Land of BarthMordor where Modding lie"
Reply With Quote
Originally Posted by stock2255
Request for (TB Team) Wireless Stereo Headset
