Can anyone give me some advice on how to make this work. I plug it in and all I get is all 4 red light blinking. CORDY, emulators keymapping all get nothing. I'm on 3.1 of course and the controller works on the ps3
Tap the PS button after you plug it in
cowballz69 said:
Can anyone give me some advice on how to make this work. I plug it in and all I get is all 4 red light blinking. CORDY, emulators keymapping all get nothing. I'm on 3.1 of course and the controller works on the ps3
Click to expand...
Click to collapse
is that an official ps3 controller? Mine works very well in most emulators..
magicpork said:
is that an official ps3 controller? Mine works very well in most emulators..
Click to expand...
Click to collapse
Yes its official. And tapping the ps3 button didn't help atall. I tried 2 controllers and still no go. Seams like im the only one with this issue
If you're using it with an emulator, it seems sometimes that the controller has to be plugged in and responding before you start the app. (I may be wrong, hard to confirm) My basic usage goes like this:
- Plug in PS3 controller, check for blinking lights
- Wait 5 seconds
- Firmly press the center PS button
- Wait a moment
- Start FPSe/your-app-here and start keymapping.
I'm sure parts of this are excessive, but it seems to be reliable for me.
PhonicUK said:
If you're using it with an emulator, it seems sometimes that the controller has to be plugged in and responding before you start the app. (I may be wrong, hard to confirm) My basic usage goes like this:
- Plug in PS3 controller, check for blinking lights
- Wait 5 seconds
- Firmly press the center PS button
- Wait a moment
- Start FPSe/your-app-here and start keymapping.
I'm sure parts of this are excessive, but it seems to be reliable for me.
Click to expand...
Click to collapse
still no go here, are u using stock kernel or the modded 3.1 kernel? im using modded and im starting to think thats why
edit downgraded to stock kernel instead ov the overclock, and the controller is now working!!!! suck i have to lose the overclock but im sure it will be fixed in a future update
I'm having this same issue. I'm using the stock kernal but I'm on prime 1.4 maybe thats the problem?
I'm trying to use it with snes9x someof the diretion buttons wrk but none of the others do
I'm currently using the official Sony PS3 wireless controller - connected via USB with great success, including spinning piledrivers and shoryukens.
Prime 1.4 rom
Stock Kernel
SNesoid, Gameboid, Nesoid, FPSe (tried Breath of Fire 4 which works)
Tried it with Prime and Clemsyn/Blades OC kernel and the controller was not detected.
4 red lights blink all the time. annoying. might duct tape it.
Make sure that you manually map the button keys in the app. If the d pad works then something is working.
Sent from my ADR6300 using XDA Premium App
Is there a way to connect the controller wirelessly? Or it's only via USB?
Related
Hey there! Having a bit of trouble getting my wired Razer Onza Xbox 360 controller (Tournament Edition) working with the Nexus 7.
I was browsing through the forums for a bit and the user 'sleeplessninja' posted some information saying that each controller you plug in gives out a unique Product and Vendor ID. So your third party controllers give out a different ID compared to the official MS branded ones and whatnot.
I downloaded the file inside the thread and renamed it to the Onza's VID/PID, which ended up being Vendor_1689_Product_fd00.kl I put that in the directory /system/usr/keylayout/ and rebooted the tablet but it's still not doing anything! The four lights around the Xbox button in the middle just keep flashing over and over. I do have the official Xbox branded steering wheel controller, I plugged that in and it works flawlessly, but I really want to get my Razer Onza working!
Any help would be greatly appreciated, thanks!
Bump! Still no luck here so far.
Just a little update, I've plugged in an official Xbox branded steering wheel controller and it works flawlessly, I've also tried a little $10 crabby USB keyboard, it works just fine too.
For some reason I just can't get this Razer Onza controller working! It's a bit frustrating.
Just another quick bump for the day, I've made no progress at all. Controller just has the 4 green rings around the Xbox button in the middle flashing on and off, doesn't do anything other than that.
The official steering wheel controller has all 4 lights blinking as well, but after 2-3 seconds it only shows the top left light turned on indicating player 1's controller is ready and it works fine.
Again, from the first post I've tried to add the file with the Razer Onza's Product and Vendor ID but it hasn't seemed to do anything.
u ever get it working
?
https://lkml.org/lkml/2012/7/17/644
Its everything I found. Looks like this controller works on Cyanogenmod 12 perfectly, but one drawback is that its Home button (5.0.2)
I have the same issue. I am able to use the controller with happy chick emulator playing family computer games. but when it comes to playstation games, it doesnt do anything.
Is there another way to calibrate this thing or do I just have a $50 paper weight ?
The left stick on my C.T.R.L. recently went out of whack, it is always moving the pointer down unless I hold a bit of "up" on it.
I tried the calibration steps from the Mad Catz site and it will not work. ie: no flashing purple light. I tried it on my M.O.J.O. and my PC, same problem.
Thank You for any help.
Soooo, paperweight then. Great!
vwtazzman said:
Soooo, paperweight then. Great!
Click to expand...
Click to collapse
Did you put in a support ticket with MadCatz? May be a defunct unit.
christoph80 said:
Did you put in a support ticket with MadCatz? May be a defunct unit.
Click to expand...
Click to collapse
Yup and it looks like the unit went bad. They will warranty it but why bother.
The sad thing is that this whole console has failed in one way or another.
I tried to pair my NYKO to it which pairs with every other android device I own and....will not pair, WTF?
And I am SO tired of seeing "not compatible with M.O.J.O." in the google store!
I have a MK908 and MK802 that will work with everything.
What't the hell MadCatz?
I should have bought a Shield.
By by MOJO
vwtazzman said:
Yup and it looks like the unit went bad. They will warranty it but why bother.
The sad thing is that this whole console has failed in one way or another.
I tried to pair my NYKO to it which pairs with every other android device I own and....will not pair, WTF?
And I am SO tired of seeing "not compatible with M.O.J.O." in the google store!
I have a MK908 and MK802 that will work with everything.
What't the hell MadCatz?
I should have bought a Shield.
By by MOJO
Click to expand...
Click to collapse
Did you update to the latest firmware? Check the MOJO icon on your homescreen, go to the fifth step and get the 205-TS firmware as that will make a huge difference to the "not compatible" incidence rate.
We've had no issues pairing the Nyko or OUYA controller with MOJO though - are you correctly placing the Nyko pad into pairing mode?
Dunno if this is resolved but for future users having an issue
The re-calibrate process for the C.T.R.L.R is as follows
Make sure the C.T.R.L.R is paired and connected to a host
Press and hold A, B, X, Y, L1 and R1 for 3 seconds – the status LED will turn purple
Press the Back button once – the status LED will begin to flash
Move each stick and trigger through their full range of movement 4 times
Press the Start button once – the status LED will return to blue to show the pad is in normal operation
According to madcatz
Edit: Dunno if I even read the first post Jesus,
also stated this before in the correct thread but the update dramatically increased the incompatible message for me, hardly saw it before now its every other app and loads that used to be compatible ain't. Controller is much much better. Just now I've got the choise of laggy controller and loads of apps or brilliant controller and no apps. Lose lose
Ash180287 said:
Dunno if this is resolved but for future users having an issue
The re-calibrate process for the C.T.R.L.R is as follows
Make sure the C.T.R.L.R is paired and connected to a host
Press and hold A, B, X, Y, L1 and R1 for 3 seconds – the status LED will turn purple
Press the Back button once – the status LED will begin to flash
Move each stick and trigger through their full range of movement 4 times
Press the Start button once – the status LED will return to blue to show the pad is in normal operation
According to madcatz
Edit: Dunno if I even read the first post Jesus,
also stated this before in the correct thread but the update dramatically increased the incompatible message for me, hardly saw it before now its every other app and loads that used to be compatible ain't. Controller is much much better. Just now I've got the choise of laggy controller and loads of apps or brilliant controller and no apps. Lose lose
Click to expand...
Click to collapse
interesting instructions.. read more like a finishing move lol
Yeah, sucks google play is stuffed.. I tried going back to the previous firmware update but the rooting doesn't fix it :/
I am having the same issue with my Mac. Tried to recalibrate but its stuck at the bottom left of the screen.
Just seen the news on Xperia Blog.
first thing i noticed after the update to the ps4 and playstation app now the device is listed as "Sony/5803"
edit:
work like a charm hope it will not require the drm so it will have a chance to not be locked on non sony devices.
Any plans for PS3 remote by Sony?
Someone try it on their Z3 Compact and post an initial impression! I'm at work...just started my day!...damn...
Can I use a dualshock 3 on my z3 compact with remote play?
war1 said:
Any plans for PS3 remote by Sony?
Click to expand...
Click to collapse
No, this feature is only for PS4
squadz said:
Can I use a dualshock 3 on my z3 compact with remote play?
Click to expand...
Click to collapse
No, this feature is only for PS4s dualshock
I'm also interested in initial impressions of remote play for Z3C. Especially regarding screen size and lag.
Played with it a bit last night. It definitely works if you have a fast connection. I was able to play Shadow of Mordor even.
But with the size of the screen it's pretty hard to really see any details or text. I think it would be much much cooler on the Z3 or the tablet. The screen size makes it kinda pointless, but some arcade games may work really well.
On the other hand, I couldn't get the ps4 controller to repair with my ps4 after! Anyone have any ideas?
Alex2x3 said:
Played with it a bit last night. It definitely works if you have a fast connection. I was able to play Shadow of Mordor even.
But with the size of the screen it's pretty hard to really see any details or text. I think it would be much much cooler on the Z3 or the tablet. The screen size makes it kinda pointless, but some arcade games may work really well.
On the other hand, I couldn't get the ps4 controller to repair with my ps4 after! Anyone have any ideas?
Click to expand...
Click to collapse
You tried re-pairing it using the charging cable, right? That should do it instantly.
schnidex said:
You tried re-pairing it using the charging cable, right? That should do it instantly.
Click to expand...
Click to collapse
Yea, tried it in a bunch of different ways. With the controller on and off, holding the PS button, and tried it while booting the ps4 up. Also was sure to disconnect from the app itself, and have my phones bluetooth off. The controller light just continuously blinks.
Idk what was going on, hoping it'll start working today.
Alex2x3 said:
Yea, tried it in a bunch of different ways. With the controller on and off, holding the PS button, and tried it while booting the ps4 up. Also was sure to disconnect from the app itself, and have my phones bluetooth off. The controller light just continuously blinks.
Idk what was going on, hoping it'll start working today.
Click to expand...
Click to collapse
did you try resetting the controller first? there's a reset button on the back of the controller. i think it's near the left trigger buttons (under the light bar). then after that you redo the pairing process.
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I am experiencing something similar, it started with restarts, then it would not boot without the button on the bottom and now it says no signal. Tried connecting it to the pc, pc installed drivers, and if you unplug a cable it says cable unplugged.
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Bumping as I still haven't found a solution.
yep, mine does the same thing, every day i have to reboot it as the screen is black and the device is unresponsive
MIne I have to unplug the HDMI and plug it back in then magically there is a signal. I tried setting never go to sleep and that did not hep. Did anyone upgrade to 5.1.1? does that fix anything?
Bump. Got mine a few days ago and the same thing happens.
It's still on and running. It's still a little warm under the button. But no matter what I do with the remote or button or TV, nothing happens. The only way to get it back up is to unplug/plug the hdmi or power cable.
I've got the same problem, but I've unplugged everything and still nothing, tried different TVs, Different HDMi leads still nothing. Going to contact Ausu or go back to where I purchased it tomorrow. was loving catching up with Game of Throne haha
malctron said:
I've got the same problem, but I've unplugged everything and still nothing, tried different TVs, Different HDMi leads still nothing. Going to contact Ausu or go back to where I purchased it tomorrow. was loving catching up with Game of Throne haha
Click to expand...
Click to collapse
You think it's just a defective device?
Maybe I should return mine as well.
I'm taking mine back tomorrow hopefully. If I can find the receipt
malctron said:
I'm taking mine back tomorrow hopefully. If I can find the receipt
Click to expand...
Click to collapse
Did you get a replacement? Did it work?
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Quoting you so you get a notification
Did you find a solution? Was it your TV, HDMI cable, or the unit itself?
DonDizzurp said:
Quoting you so you get a notification
Did you find a solution? Was it your TV, HDMI cable, or the unit itself?
Click to expand...
Click to collapse
Still no solution. Tried 3 different ROMs and it's the same thing with each one. Could it be a firmware problem? I mean I shouldn't have to reboot it every time it goes to sleep. The hardware button on the bottom has no effect. I'm slowly giving up.
DonDizzurp said:
Did you get a replacement? Did it work?
Click to expand...
Click to collapse
Hey, sorry for the delay, been busy.
But yeah I got my new nexus. Rang Asus with some struggle as the serial on the product wasn't matching up on the system. Useful haha
Then they said it would take 29 days to get a fix or replacement.... I then said I'll take it back to where I got it which in my case was Argos.
Took it back told them the problem, girl looked at me completely confused. Think I lost her at bootloader haha. But I might as well tell them how to explain to do a factory reset which I couldn't do anyway. Then got my replacement. Which I'm leaving in the box as I want to be a geeky guy and do a unboxing video this time haha.
I found if you turn the TV on and off again it will work.. no need to get up and pull the HDMI cable
I noticed this issue didn't happen with 5.0 but happened with 5.1.1 so I'm hoping a new update will fix it.
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
malctron said:
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
Click to expand...
Click to collapse
A sideloader? If you are asking how to sideload, you boot into the recovery and then choose install from sideload, then use the "adb sideload" command.
malctron said:
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
Click to expand...
Click to collapse
That has absolutely nothing to do with this thread
LOL
Also, you sideload using ADB
Turn on USB debugging, install the ADB driver on your PC, then use the adb command "adb install apkname.apk"
No need for root or recovery.
DonDizzurp said:
I found if you turn the TV on and off again it will work.. no need to get up and pull the HDMI cable
I noticed this issue didn't happen with 5.0 but happened with 5.1.1 so I'm hoping a new update will fix it.
Click to expand...
Click to collapse
This doesn't work on my setup. But pulling the HDMI cable works.
This problem appeared on my Nexus player about a month ago, it was working perfectly until that time.
It looks like a problem with the HDMI CEC. Even if I put my NP in "Never sleep mode" as soon as I turn off the TV it will not then wake when I turn the TV back on.
Well, in my case at least, that is not accurate. When I turn the TV on, nothing appears on the screen nor is there any audio, but the NP is still responding to commands and working. I can blindly start a YouTube video from the highlights section while the TV is still "blanked" and when I toggle the HDMI cable connection the I can see that the NP was functioning "correctly" other than it wasn't outputting anything to the HDMI port.
I would say that the "fault" is just likely to be on the TV not implementing HDMI CEC correctly, but everything WAS working correctly until recently and the only changes are on the Nexus Player side of the equation.
DonDizzurp said:
That has absolutely nothing to do with this thread
LOL
Also, you sideload using ADB
Turn on USB debugging, install the ADB driver on your PC, then use the adb command "adb install apkname.apk"
No need for root or recovery.
Click to expand...
Click to collapse
Haha I know told you it was random yeah I did that after I sent it. Couldn't delete the message sorry haha
Problem solved?
Before you take the device back to the store, I believe the problem is the TV; even those of you who tried multiple ones. I did the same thing; tried a different TV. However, in my case, it works. When I hooked mine to a newer TV, the device wakes up fine. I read in other forums (searched "HDMI won't wake up device") and to my surprise, there are other forum where people complained about the same with other devices. Apparently, something related to the HDMI port (maybe the version of HDMI?).
I thought I read that the gamepad was suppose to turn off after 10 minutes after you stop using it, mine does not. Is there any place in settings where I can turn it off?
lartomar2002 said:
I thought I read that the gamepad was suppose to turn off after 10 minutes after you stop using it, mine does not. Is there any place in settings where I can turn it off?
Click to expand...
Click to collapse
Unfortunately no there isn't a place to turn it off. The one solution that is fool proof is if you unplug be console it will power the controller off. You can't put it to sleep or hut the button it needs to physically be unplugged from power. Its not a great solution but it works.
Pilz said:
Unfortunately no there isn't a place to turn it off. The one solution that is fool proof is if you unplug be console it will power the controller off. You can't put it to sleep or hut the button it needs to physically be unplugged from power. Its not a great solution but it works.
Click to expand...
Click to collapse
The more I play with the shield the less polished it seems. Hopefully this will be fixed in future updates. It just seems like such a Ouya mistake.
lartomar2002 said:
The more I play with the shield the less polished it seems. Hopefully this will be fixed in future updates. It just seems like such a Ouya mistake.
Click to expand...
Click to collapse
Me too, I still like my Shield Tablet and TV. There used to be a way to turn off the controller but they got rid of it in an update for some reason
Press and hold for 10s on the power capacitive button of the shield console will power down the unit. It's a hack done by nvidia that is unavailable on stock Android TV.
Oops not applicable thought you meant the console.
Restarting the tablet works also, but that's not really an elegant solution. I just keep mine plugged into a wall wart as it still will give me remote volume and wireless from tho console. It's good enough for me, but it would be nice to have an option. Battery life is so good that I can kinda see why they wouldn't offen an off option though. They should' but it almost doesn't need one.
I spoke with someone at NVidia about it. I'm assured they know and that a fix is coming.
On their forms they have also assured that a fix was coming in a small patch "in the near future" and a very large update, probably android 6.0, is coming not too long after.
OTA 1.4 has a fix to allow you to turn the controller back off again. Manually though.