PlayStation 3 Controller On Android Devices 133
An anonymous reader writes "You can now use the PS3 Sixaxis Controller on Android phones and devices. This requires your phone to be rooted, however it is incompatible with most HTC devices and some newer Samsung devices due to the need of specific Bluetooth protocol. It can sync four controllers at once with buttons completely configurable."
Re: (Score:3)
HTC devices are supported, you just need to be running an AOSP based ROM. In the stock sense-based ROMs, HTC uses a different (incompatible) bluetooth driver.
Re: (Score:2)
I know some "normal" people that rooted simply to install adblock, and to delete bundled apps, and have no interest in not running stock.
Re: (Score:1)
I rooted and used a Virtuous ROM, I really liked the sense dialer and miss it still, but the bluetooth issue eventually annoyed me (I couldn't use my phone as a bluetooth keyboard and mouse).
Re: (Score:2)
If it's running Sense, it's not supported. If it's running an AOSP-derived build (such as Cyanogenmod), it should be supported.
Similarly, "newer" Samsung devices isn't correct.
If it came with TouchWiz, it's not supported. If it came with AOSP (basically, the Nexus S and no other Samsung device), it's supported. If it's a Samsung device with a Cyanogenmod port, it's supported under Cyanogenmod.
This is because HTC and Samsung broke their Bluetooth stacks.
Exception: Non-Touchwiz Galaxy Tab 10.1s work well.
Re: (Score:2)
Why is that "retarded?" Why add an extra device to the equation when the whole point is portability? I think this idea is actually pretty "retarded" and backwards. The controller is as the the device.
Re: (Score:1)
Does it (Score:1, Offtopic)
Interesting maybe kinda but not really (Score:1)
Re: (Score:1)
Re: (Score:2)
Does HTC really make 90% of the phones? I know they are a popular manufacturer, but I know Samsung and Motorola have some very popular models as well. Anyone know if this works on the Asus Transformer?
Re: (Score:1)
Re: (Score:2)
And on linux, you probably need a kernel module or allow writing somewhere on /dev/
Re: (Score:2)
It's GPLv2 open, not GPLv3 open.
Re: (Score:2)
It's just like Linux - you need root privileges to do some things. This is one of them.
Unfortunately most phones do not provide users with root access. With the exception of Tivoized devices (MOTOROLA!), Android is far more open than iOS - the amount of things you are permitted to do without root on Android is FAR more than what you can do without jailbreak on iOS.
Re: (Score:1)
Re: (Score:3)
Most likely you will be able to find it in many places, most obviously Google, when its released. You know, like all the previous versions of android.
Oh, I'm sorry, you wanted to be bitter.
Re: (Score:1)
Yes, for the subgroup of humans that have the means to travel back and forth through time.
Re: (Score:2)
So, what you're saying is that Android 2.x is open source and Android 3.x isn't? Got it.
Re:Interesting maybe kinda but not really (Score:4, Informative)
The AOSP git repository? Here's the announcement for 3.2: http://groups.google.com/group/android-building/browse_thread/thread/6a3b3a1c225a11f5/6f36c6c857cfe57f [google.com]
Re: (Score:2)
That only has the GPL components - all of the Apache-licensed components (90% of userland) is missing.
Re:But why? (Score:4, Informative)
When it comes to old 2D games the Playstation 3 controller is pretty much the best on the market, thanks to its solid dpad. Also there really aren't many alternatives to begin with. The Xbox360 controller doesn't talk Bluetooth and the Wiimote lacks a lot of buttons. A Wiimote and a ClassicController together would work, but would be rather bulky. And as far as normal PC controller go: There aren't many Bluetooth controller either, most wireless ones talk their own proprietary protocol.
Re: (Score:2)
When it comes to old 2D games the Playstation 3 controller is pretty much the best on the market, thanks to its solid dpad
Are you kidding? The Sony style disconnected arrow buttons have been the bane of 2d gamers for 3 generations of Playstation. Anyone who seriously wants to play 2d games on the PS3 (shmups or vs. fighters mostly) will go get a USB Sega Saturn pad. This is the finest digital game pad ever produced bar none. Make sure you get an original, because the clones will break with light use.
Re: (Score:2)
The 360 controller is pretty good, and I didn't mind the old x-box one. The sony duoshock is just ok... The Gamecube controller is great, although you look at it and go 'WTF?'
Re: (Score:2)
Oh come on. What about the Nintendo Powerglove? Or the Sega Activator? There are plenty of amazingly bad controller designs out there.
Re: (Score:2)
Have you tried holding an N64 controller? Those things were ridiculous.
The PS controllers were the first controller that actually felt good in my hands, due to the crude attempt they made at shaping it to fit human hands. The large XBox controllers were the first to first my rather-large hands properly.
Re: (Score:2)
The Xbox 360 D-pad has endemic design issues with diagonals.
The Sega Master System also had atrocious diagonals, as did Game.com.
The 5200, while technically a stick design, featured a non-re-centering joystick. Which meant you needed to estimate where neutral was, and hope you were right.
The CDi's gamepad felt like / was a bad PC 3rd party knockoff of a Gravis PC Gamepad. It felt sloppy and loose.
The PS1 gamepad had far less of the "rocker" design to the d-pad, resulting in lots of precise presses needed
Re: (Score:2)
If we're talking terrible peripherals, the U-Force has to top the list for least-likely-to-ever-respond-to-input-correctly.
The U-Force sure does make that list, but hardly at the top.
I'm pretty sure the Power Glove still holds #1 place.
The rolling rocker is way up there too, as is the Atari 5300 controllers.
Ironically, the U-force responds surprisingly well for a horrible terrible peripheral, in that it works a good 10% of the time compared to the rest of the list that can't even manage that.
Re: (Score:1)
Pounds Head Into Desk.... (Score:1)
Well, Shit.
I seem to have the unrootable phone now. This Nexus-S just won't do it, and I have done everything by the book, followed all the guides... Hell, I even watched the damned video just in case I was doing something wrong!
Must be something my provider does to them. Cincinnati Bell has a new obsession with doing interesting things to phones now.
Re:Pounds Head Into Desk.... (Score:4, Funny)
Good thing you bought a Google Experience phone. I hear they're very open. :)
Re: (Score:1)
Not as open as Apple's [jailbreakme.com]
Re: (Score:3)
Re: (Score:2)
I don't really know/care.
Posted from my Nexus S
PS3 fully supported, QWERTY still buggy as shit (Score:2)
Glad to see developers have solved the PS3 support problem, as my touch interface didn't give me enough analog options or virtual buttons. You still have to install all sorts of crappy 3rd party BT drivers and jump through various flaming hoops to get a BT keyboard to work on android.
Re: (Score:2)
2 days ago in reddit.com/r/android (Score:1)
http://www.reddit.com/r/Android/comments/ja2au/now_you_can_use_ps3_controllers_on_your_phone/ [reddit.com]
Probably more useful on tablets anyways....
I've had the wiimote working with mine for a while. sixaxis may be even better...
This could be useful in a way. (Score:1)
Some Aps just need a real controller feel to them, even if you're missing out on a majority of the market share(people with Android/iPhones and no PS3 controller).
Re: (Score:2)
Re: (Score:2)
I think it's considered a big deal because PS3 controllers aren't bluetooth HID devices like the wiimotes, they have a custom protocol.
Re: (Score:2)
'cos it's pretty cool, if you're travelling, to plug your phone into the hotel tv and run your genesis/SNES/MAME/whatever emulators, and have a neat little wireless controller, too.
Or at least it is on my N900 which has had thuis feature for over a year now.
Re: (Score:2)
And no "rooting" necessary on the N900, just power up and install.
But now the most open phones on the market all have to be rooted. Progress!
Yay? (Score:5, Funny)
Be more useful for me if I could use my Android phone AS a Sixaxis controller. Or at least a lot cooler.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
On Maemo you could do that, among other things:
http://maemo.org/packages/view/bluemaemo/ [maemo.org]
Re: (Score:2)
Err no, this is so you can connect one or several PS3 controllers to your phone, which is running an emulator displayed over HDMI. Thus turning your phone into a mini-console.
I don't see why anyone would want to use a phone as a controller for a PS3. It would be far inferior to an actual PS3 controller.
Re: (Score:2)
And I don't see why anyone would want to play games on their phone, even via HDMI on a TV. I don't think EITHER of these is in any way useful. I'm just saying using the phone as a controller would be somewhat cooler.
Re: (Score:2)
Heh, you make no sense. I mean, the attraction of having your phone be a full-on console is obvious. You can easily take it to other people's houses, on business trips, etc.
But there's no reason you'd want to use a phone as a PS3 controller - people who have PS3's tend to already have PS3 controllers, and they are much better!
Re: (Score:2)
Yeah, Angry Birds on a huge TV with a PS3 controller, that's just awesome cool fun.
I prefer to take a book on trips. I do a lot of things with my phone, but play games is not one of them.
Re: (Score:2)
Well now you're just changing what I said, which is as good as admitting you lost the debate!
Re: (Score:2)
Ok, you're saying phone games are as good as console games. I say maybe consoles from 5 years ago. I still have zero interest in playing them.
As I said originally, I don't really think either of these is a 'good' idea.
What is it with BT? (Score:4, Interesting)
I understand that, when one or both devices communicating are likely to be embedded ones for which driver update is impractical or impossible, the specification of assorted "Protocols" is desireable(and extremely convenient, as in the case of USB's "Classes"). What I don't understand, though, is why the various BT protocols seem to be so device/driver dependent. Some dongles support protocol X, others don't, others do with a cracked copy of BlueSoliel Y or higher...
Why is it up to the bluetooth device, or to its driver, to support high-level protocols(even on PCs) rather than just handling the low-level link stuff and letting the OS or userspace handle the clever stuff? It seems vaguely like discovering that your NIC is handling SIP in-driver, and if you happen to buy the wrong one, VOIP just won't work. I can understand why a maker of embedded chipsets might produce an IC combining a NIC with some VOIP-centered DSP stuff and an application processor, for the convenience of people building VOIP handsets and such; but encountering such a thing in a PC would be a bit of a shock.
Why is BT so weird?
Re:What is it with BT? (Score:4, Informative)
Can't answer the general case, but when it comes to the Playstation 3 controller the situation is basically this (at least as far as I understand it):
1) you connect the controller via USB to let him now the Bluetooth address of your computer/phone
2) you press the button on the controller to power it up
3) the controller now contacts your computer and says hello
4) your computer needs an application running to answer that call
The problem is step 4), the Playstation 3 controller seems to use well known ports for this (HID stuff I think) and your average OS already has an application listening on those ports, thus you can't just add another application to listen on the same ports and have to kill whatever is already running there to make it work. It's essentially the same thing as when you want to run two webservers on port 80, it simply doesn't work.
With the Wiimote in adhoc mode the situation is much simpler, as it is the computer that is contacting the Wiimote, not the Wiimote the computer. Thus there are no ports on the computer to worry about and you can simply run a Wiimote app on the PC and have that talk to the Wiimote. The Wiimote however can also be synced with the PC (when pressing the red sync button instead of 1+2), when that is done the situation reverses again, its now the Wiimote contacting the PC. Not sure what ports it uses for that and if there are any conflicts.
Re: (Score:2)
> your average OS already has an application listening on those ports
I don't think it is that in this case. The app describes the lack of support as a "missing protocol". Probably Samsung/HTC's bluetooth stack doesn't support HID... or something.
I've actually been trying to write an android sixaxis app, but bluetooth is pretty damn complicated and there are no good tutorials or documentation - they're all way too 'enterprise' and convoluted.
Re: (Score:2)
Aha! I found the real reason.
There is a bluetooth input code here: http://code.google.com/p/android-bluez-ime/ [google.com]
And they state "Wiimote support is ready, but many devices lack the L2CAP ability and thus cannot communicate with the Wiimote."
I imagine it is the same reason for the PS3.
Re: (Score:1)
It's essentially the same thing as when you want to run two webservers on port 80, it simply doesn't work.
Uhhhh...yeah it does. Host headers.
Uhhhh...no it doesn't. That would be one webserver running two web sites.
Re: (Score:1)
I believe the root of the problem is that Windows shipped without a bluetooth stack, leaving it up to the various bluetooth hardware makers to write their own drivers. Hardware companies are not very good at software - it's outside their core competency, and they view drivers as an expense rather than a way to improve their product. So some of them did things their own way, some of them licensed stacks from other companies, and we ended up with about four competing implementations each with their own bugs.
Another Option (Score:2)
Does not require root, as it physically pushes the keyboard buttons.
Re: (Score:2)
I've never understood... (Score:4, Interesting)
... why people just accept that in order to do anything cool with an Android phone you have to jailbreak it first.
Among my friends there's about a 25/75 split between Android users and iPhone users (disclaimer: I've got an iPhone). Honestly, I don't really get the fanboy fuelled 'hate-dom' that seems to flare up whenever we get into a debate about the respective merits of our devices, especially because we're arguing about the superior brand of telephone. Really...?
I do find it strange, though, that despite Android phones having superior cameras, consumer-friendly features including the ability to replace your battery, better and faster processors, more ram and physical keyboards (in all ways, physically, superior to iPhones), whenever a debate comes... it's inevitable that one of the main arguments (usually the first one) that's bought out by the Android users is "It's open and it's free as in freedom", usually said with this smug grin, as though the iPhone is not. They're right, of course, but...
But then I ask something like, "Can I replace the 'telephone' app freely then?" and they nod eagerly and say, "Yep, you totally can, you just jailbreak it like this and-" ...
I can accept that Android has a great deal many superior features to the iPhone, but I eventually went with iPhone because it had the best user interface, painless upgrade process, everything about it 'just works' (unless it doesn't, such as 3GS wifi-access-point-mode), and the app-store is by far the best. Some people say, "If you're not willing to tinker with your devices you're not a real geek", at which point I tell them that it's just a telephone and I expect it, and its apps, to just work, all the time. It should not need to be tinkered with.
I just don't understand why when the inevitable fanboy war comes, that the very first feature that seems to be produced is "It's open if you jailbreak!". I mean, isn't that the very definition of jailbreaking? Making something closed open? (and yes, iPhones can do it to...)
My second question is...
Awesome! Is there an iPhone port of this?
Re: (Score:3)
I don't know why they accept it. That's why I got a Nokia N900. Root available(just install an app) easily, unlocked, open bootloader(so you can dual, triple or quad-boot whatever the hell you want), and a full Linux stack.
Oh, and it's supported using the Sixaxis controller since at *least* January of last year... Not that I care, not having one, but...
Yea.
Re:I've never understood... (Score:5, Insightful)
I can accept that Android has a great deal many superior features to the iPhone, but I eventually went with iPhone because it had the best user interface, painless upgrade process, everything about it 'just works' (unless it doesn't, such as 3GS wifi-access-point-mode), and the app-store is by far the best. Some people say, "If you're not willing to tinker with your devices you're not a real geek", at which point I tell them that it's just a telephone and I expect it, and its apps, to just work, all the time. It should not need to be tinkered with.
No offense, but I can't stand the "it just works" cop-out. I have heard it so many times, it sounds like it was ripped straight from an Apple commercial. Of course "it just works"-- even Androids "just work," if you mean they can do all the basic functions, like making calls, storing contacts, showing the time, accessing webpages, etc., in some fashion or another without a ton of modification.
However, when given the ability to customize and personalize, some of us enjoy going the extra mile to upgrade a sufficient "just works" interface to an optimal "OMG check out what my smartphone can do" interface. Sure, the default Android browser works fine, but I want tabbed browsing, so I upgrade to Dolphin HD. The default gTalk app does what it's designed to do, but I'm a power chatter with five or six different IM accounts (which could require many different apps!), so to standardize the interface and save on the RAM, I grab eBuddy for an all-in-one solution. And that's not even getting into all of the cool stuff (and money-saving stuff) you can do if you root your phone.
I think that when a geek gains that ability to tinker, "just works" becomes "hmm... maybe I can do better." If you don't have any other options, you don't bitch about a lousy interface--you learn to adapt. For instance, every microwave oven I've ever owned has had a POPCORN button on it that always seems to burn any popcorn I give it. Naturally, I just ignore it like many others do. However, if I could take that button off and replace it with a +30 SECONDS button (in addition to the regular +1 QUICK MINUTE button) or a QUICK RECALL button or something other that would be more useful, I would do it in a heartbeat. But I can't, because the microwave's interface is locked and can't be modified. So you learn to adapt to the quirks and ignore the deficiencies.
However, as soon as you learn you have other options, the minor problems become glaring obstacles that can be overcome with a little bit of research and tinkering. Maybe that's not a big deal to some people, but I like it.
Re: (Score:1)
Exactly! Thank you for posting that.
I have an ipod touch (don't have money for a smart phone, no real alternatives that I've seen) and it hardly "just works" for me. I've jailbroken it, and I don't know how people can stand to live without the features I've added to mine. I use a case with a cover, so the lock screen is pointless for me. Turns out there's a cydia app to get rid of the lock screen. I thought it was a pain to take it out of my pocket, unlock it (before I jailbroke), and open the music app jus
Re: (Score:1)
Both iOS and Android have their good and bad points (to state the obvios). If you love the Apple interface, it would be a wrench to switch to something else. Apple certainly does 'slick' and a lot of the features are well implemented but a lot are not.
A work colleague got an iPhone 4 which I had a play with. It impressed me once I'd got the hang of the menu system but one thing that really put me off was the lack of peak and off-peak email schedules in the MS exchange implementation. I prefer push ema
Re: (Score:2)
The battery life was dire at the start but only due to the number of default apps which were trying to sync every quarter of a second or so (stock, news, email, gmail, weather, shoes, plates, cups, saucers etc.). Once I'd tweaked a bit and scheduled wif-fi to switch off during work hours when I don't need it, the battery life is fine. Of course, I can use someone elses adroid, blackberry charger if I run low on juice.
Battery life is one of the minuses of the HTC Desire HD so I always carry a USB to micro USB cable which I plug into my laptop whenever my charge level drops below 50%. Basically I only get about an hour gaming on the train and my battery normally goes down to 50%. Other than that I am very happy with my phone.
Traveling by car takes me well over an hour in peak traffic to get to where I am currently working hence the reason I take a train (less stress) when traveling in the city. In addition I can also pl
Re: (Score:2)
The problem is that "just works" implies a level of polish that a lot of geeks don't seem to care about. Doing basic
The point was... (Score:2)
Android devices "just work" if you pretend it is as locked down as an iPhone and don't go exploring possibilities that you wouldn't have had anyway. In so many cases something that has sensible defaults but lot's of power under the hood if you want it is decried as 'too complicated' even though without popping the hood you can't even tell the difference.
Re: (Score:2)
I've been outgeeked by microwave popcorn enthusiasts. I am deeply humbled.
Re:I've never understood... (Score:4, Insightful)
Awesome! Is there an iPhone port of this?
Yep, coming soon, you just jailbreak it like this and-" ...
This is actually one of my big misgivings about my iPhone. I have to jailbreak it to do a lot of cool things with it, and Apple goes way out of their way to make it obnoxiously hard. I skip most of the upgrades because it's a complete PITA to plan an upgrade path that won't lose my jailbreak.
I'm giving very serious thought to switching to an Android phone where I can jailbreak it once (possibly with vendor-blessing, or perhaps not), install Cyanogenmod, and be done with it.
If I wanted the best vendor-supplied experience, the iPhone has it, hands down. But I'm a tinkerer, and Android is calling.
Re: (Score:2)
Whoosh!
Re: (Score:1)
Rooting != Jailbreaking
Re: (Score:2)
I think you have the wrong understanding of "jailbreaking" and which type of operations require "jailbreaking".
"jailbreaking" on android is obtaining root access. The system does not really prevent you from having root access since plugging a USB cable on the phone give you root access. That is why the operation is called "rooting" the phone. Most people want to root the phone to install custom firmwares, but for most thing you do not need that.
Only applications that need a low level access require a rooted
Re: (Score:2)
Actually, jailbreaking is called such because under iOS you have to break out of a CHROOT JAIL. You don't jailbreak an Android because there is no chroot jail to break out of. It's called rooting because you're doing that...obtaining root.
Re: (Score:2)
I owned an iPhone not to knock it or anything if you are happy with it fine but I didn't realize how many calls it dropped until I switched. My 2cents is just to say I'm so glad I can connect my new phone on as many computers as I care to. iPhone is so closed that I can't understand how you put up with it, jailbroken or not.
Re: (Score:1)
My wife and I both had 3G phones, I have a 4 now. Neither of us, over the three phones, have ever had a dropped call. Ever. Did you switch carriers when you switched phones? Or, perhaps, just a sketchy radio in the phone. As to being closed, that's just silly. The reality of the situation is that you need to jailbreak/root either phone, or you're stuck in a shitty closed platform. Android talks open, but you're still beholden to your handset maker/carrier for OS upgrades (which may well never come)
Re: (Score:1)
One of the strongest arguments in favour of Andriod - the choice of hardware upon which to use it - is also one of the arguments against it. The new iPhone is realeased and everyone gets it - no watering down of hardware/compatibility. With Android, lots of vendors are competing hence the choice. It is this choice which I think is a good thing even though it may introduce incompatibility/instability.
Apple has a strong business model but it is not for everyone. Rather than berate one or the other, peop
Re: (Score:1)
You don't jailbreak an Android phone. You root it which is usually pretty simple. For my GT540 I simply Googled it. :SWIFT::GT540:
- Enter the code '3845#*540#'
- Select the option 'Module Test', then 'Stability Test' then 'Enable Root Permission'
- You will now be prompted for a password - enter
- A toast message will briefly appear saying 'OK' - your root access is now enabled!
That's all there is to it.
Re:I've never understood... (Score:4, Informative)
But then I ask something like, "Can I replace the 'telephone' app freely then?" and they nod eagerly and say, "Yep, you totally can, you just jailbreak it like this and-" ...
If you mean the dialer app, then yes you can replace it, without rooting. In fact, there is very little you must root to do. Off the top of my head I have only had to root to do the following:
Install custom ROMs/patches.
Run a personal firewall/ad blocker.
Run a wireless tether app that doesn't require that I pay the phone company extra.
Run a VNC server.
Run a program that over/underclocks my phone.
Re: (Score:1)
Well I would argue that the iPhone doesn't "just work". There are plenty of apps that have weird bugs out there, just as in any other environment.
People state the "just works" property because they have no interest in the fancy features a smartphone gives you. As they stand from production Android and iPhones can be categorized as being feature phones. It's not until you start tinkering that the "smart" part comes out.
I love tinkering with my phone, and "jailbreaking" is not so much the word for getting roo
Re: (Score:2)
The biggest misconception with Andriod is that its only better for tinkerers. I have one and have never rooted or done anything fancy to it, but I still prefer it. Why? If I do decide I want to tinker or mess around with something, I have that option even without root. Apple is about the Jobs Way or the Highway. To put it simply, I don't like being told what I can and can't do by an obsessive control freak. That aside, I multitask extensively and Apple's definition of multitasking, after testing, make
Re: (Score:2)
My second question is...
Awesome! Is there an iPhone port of this?
There probably will be an iPhone port for this. But guess what? You're probably going to have to jailbreak your phone to use it!
Hrm, Nokia N900... (Score:2)
Great! Except not :( (Score:2)
>"You can now use the PS3 Sixaxis Controller on Android phones and devices."!
Except not unless you are rooted. Throw away 90% of devices out there.
Or if it is an HTC. So throw out another 50% of devices out there.
Or a newer Samsung. So throw out another 15% of devices out there.
And there is no point if it is not a higher-end device capable of playing good games. So throw out about 70% of devices out there.
Not much left!
Re: (Score:1)
Or if it is an HTC. So throw out another 50% of devices out there.
I'm on a HTC Hero... rooted, and running aospCMod (AOSP 2.3.4 / CM7+ (Gingerbread)). I don't have a Sixaxis to test the actual hardware, but the compatibility checker indicates that my phone is compatible.
So maybe not completely "throw out another 50% of devices out there." Mod'ed HTC's may be good to go, and a mod'ded phone is guaranteed to be rooted.
Headline is slightly misleading. (Score:2)
That's true if you are using a sense based rom, however if you are rooted, there's a good chance you are using an AOSP (android open source project) ROM, such as Cyanogenmod 7 that does have the bluetooth support needed.
Also wanted to note that controller support for android isn't exactly a new concept. The wiimote has been able to be used for quite a while. However support for a pla
nice (Score:1)
Re: (Score:2)
that would require something other than a 20+ year old concept in a new package, though I will consent that having cheap cellular Internet had a major 1 up in the evolution of the newton/palm/and all the other mips and arm pocket pc's
Re: (Score:2)
And would you have the PS3 in your other pocket? Sorry, but that's a dumb idea (plus it would make for a poor controller I'm sure)
Re: (Score:2)
The PS3's controller works then fine in Linux, using BT, like a regular controller work.
Does it? As mine doesn't. The two ways to make it work after the sync seems to be patching hidd [ubuntu.com] or killing hidd/bluetoothd and using QTSixa [sourceforge.net], at least judging from what I have found so far on the Web and most of it seems rather outdated. There also seem to be issues with the controller not using authentification that one thus might need to disable in the bluetooth config.
Long story short: If somebody has an up to date HowTo on how to make the controller just work over Bluetooth without additional hackery in