This is an interesting thread/conversation, but I think there is quite a lot of confusion.
When referring to wired connections, I'm guessing people are referring to USB
When referring to wireless connections (or remote connections) there are IR, RF, Bluetooth and WiFi as possibilities.
A universal remote today needs to support IR at some point because many devices are still controlled only using IR. that is why Logitech have produced the IR box for the PS3 and have now produced the IR link for Android and iPhone (the reason I ended up reading this thread)
HID is the name given to any device that is used for communicating with an electronic device. Traditionally, that is a mouse or a keyboard.
Modern controllers, that may not be anything like a keyboard or a mouse, tend to use the same commands as keyboard and mouse, simply because it is available and already supported.
But...
HID over Bluetooth is not the same thing as HID over USB. HID over Bluetooth uses the same commands as HID over USB, with a little bit of extra 'stuff', so it is technically similar.
An even bigger BUT...
These classes, like HID, are based on a client server model, where one side is the client and the other end is a server. In the case of HID, it is a bit like the behaviour of a Web Browser and a Web Server. Where there are relatively simple inputs, that have relatively complex results. Click on a link in a browser and potentially unlimited amounts of code could run on the server.
So... Android (and possibly iOS) devices have HID Servers in them. This allows HID clients to connect to them. For example, I can connect a mouse or keyboard or both to my android devices and magically a mouse pointer appears on the Android display and I can then track the pointer around using my mouse or touchpad.
This is the complete opposite of what I think this topic is about. To be able to use an Android phone or tablet as an HID Client, you would need to have the client class available to you. There are a number of reasons (no access to l2CAP) that this cannot be done today.
A rooted phone could have (and has had - see androhid) a HID client added to it.
The bottom line is some bluetooth Protocols are available to apps on android and these protocols could be used to provide communication between an Android App and another device. But all of the devices we are talking about are listening for a HID device or other proprietary protocol. So until a Bluetooth HID Client Class is made available within android, this isn't going to be possible.
the closest we are going to get is the solution already proposed and being trialed in USA at the moment - a Box with a bluetooth HID Client in it, that can also communicate with an Android device.
The clever thing for Sony to do would be to add a proprietary Bluetooth protocol to the PS3 and then an App with the same protocol for Android. But other than that being cool, I don't see Sony having any reason to do that. The most liekly thing sony would do is to put it into the ROM of their own phones ONLY.