Every time I connect my Shield tablet to a TV and switch to console mode, my controller disconnects. I'm on Lolipop. Any ideas how to fix? Or... is this normal behaviour? Should I just go return it to shop?
Only way how can I reconnect the controller in console mode is by pulling down the notifications and try to hit the game controller button (after which I connect it again). But trying to find that button on a black screen is a pain... And yes, of course I tried forgetting the controller and re-adding.
On lollipop this is normal. Every time you switch to console mode it gets disconnected. Just press the nVidia logo again and it should work.
I'm facing now i'm strange behavior. for me the cursor start going from the bottom to the top of the screen without even touch the stick, i have to turn it off and turn it on again for make it go for some time.
Yup this happens every time. When you switch to console it sleeps the tablet and you have to relogin and turn you controller back on. But all you have to do is press the NVIDIA button on the gamepad and it will reconnect you don't have to actually goto the menu to press the gamepad button. The gamepad button in the notifications window should only have to be hit the first time you ever sync the controller. After that you should always be able to connect the gamepad by just pressing the NVIDIA button on the gamepad and it should just turn on and instantly be connected mine usually connect before the green light even comes on.
factory reset solved it
So just to let you guys know - factory reset solved the problem - now Im able to connect my controller just by pressing the nvidia logo. Before I had to resync it everytime when I changed to/from console mode.
Related
My transformer has been my right hand since June and all of the sudden I'm without it. Was listening to a podcast via beyondpod this morning and paused the audio via my BT headset. Went to a meeting, then lunch. Came back two hours later and my tablet wouldn't turn on. I figured it was a sleep of death that randomly occurs so I held the power button in for 30 seconds or so to reboot, but that didn't work. It was still on because I could hear audio notifications for calendar appointments.
Tried the power button for 60-90 seconds, still nothing on screen. In the past I've been able to plug in the charger when this occurred and it would pop the screen on, tried that, but got no results.
I tried plugging it into my laptop to see if I could get ADB active and do a reboot. Windows saw the device and loaded the ADB driver, but if I tried adb devices it showed no devices. I long pressed the power button again and the windows device manager reset, adb devices now showed the transformer, but in offline mode. I couldn't run any commands.
Next I tried the "soft reset" utilizing the volume up and power button. This didn't do anything, except that the next time I attached it to my laptop it prompted me for an APX driver. I didn't know at the time this was for NVFlash (I rooted my device before the SBK was out with the initial blob tools from androidroot.mobi).
Now when I hook up my transformer I get no response from my computer and no response from the buttons on my tablet.
I'm at a loss and would love any suggestions or ideas to get my tablet back up and running.
This is resolved, I was finally able to get it rebooted via the volume down button and power while hooked to my laptop. I have no clue what was going on with it, but its still acting hinky.
Do we have any hardware diagnostics?
my tablet just started doing the same thing. O_O asus is trying to get us to buy their new slates, so they broke our current ones. /s
Something is seriously wonky here. My wifi keeps turning shutting down but being stuck at turning off. My power button is very inconsistent.
I think I'm going to fully wipe the system and start from scratch...
Been a couple months, but I'm back in the frozen state again. I charged my TF101 over night, pulled it off the charger and validated it was in a SOD. I put it in my sleeve and headed to the office. I turned on my BT headset to listen to a Podcast, but it didn't connect. I grabbed the tablet and it was screen on, frozen at 7:29am.
I can't for the life of me get this thing to reboot. I've held the power button in for 60 seconds, tried power button with volume down to boot recovery. I tried on AC power and off. I tried to hook to my PC, but the USB is not recognized at all.
I don't know if I just need to let this thing die (which will take forever) or what to do to get this rebooted.
Power button feels like it is catching when I press it in...
If you take off the outer bezel (be mindful of your micro sd card if you have one) you can push the actual power button itself. It should be a simple hold the button down for about 3-5 seconds and it'll reboot.
I have tried a Moga Hero and Pro Power. They both work for a moment, but then will stop controlling anything. The icon is still in the notification bar (sometimes) and the Bluetooth settings say Moga Pro 2 HID is connected (sometimes), but pressing the controller buttons stops responding. The lights on the controller are solid orange and one blue light. If I turn the controller on and off a few times, it will sometimes reconnect briefly, but it usually stops working soon after. I am using B mode. I couldn't get A mode to work at all. Many people online have said it needs to be in B mode, especially for Gear VR.
Any idea why this issue is occurring?
Hey all, need a hand. My Shield TV seems to be bricked. When I turned it on last night there was a red and green ball animation playing and the console wouldn't respond to any input from the controller or my Harmony remote. I should clarify a bit, the animation was actually frozen. Anyway, I unplugged the console for a while and now it won't do anything. There's no video output from the console. I've tried 3 different TV's and 3 different HDMI cables. I was going to try and reflash it back to factory, but I can't get the laptop to recognize the console. It finds my android phone just fine and ADB works great on it. The green light comes on when I plug it in and the power button seems to at least turn the light on and off. It does show up in the device manager on the laptop when its on, but as an unknown device type called APX. I downloaded the drivers from NVidia which then shows it as Android ADB Interface, but ADB still won't see it. I've also tried plugging it, waiting 2 seconds then holding down the power button for 5 to get it into Fastboot mode, but all it does it turn the console off. Any suggestions would be greatly appreciated. Thanks!
connect the console to your pc. unplug the dc. > plug the dc > touch power for ~3 sec.
after that download factory image from nvidia website. and flash it on shield console.
https://developer.nvidia.com/shield-open-source
flashed wrong rom on Nvidia Shield 2015 16GB -- stuck in APX mode -- unable to access fastboot.
Please help?
Ok, So my Shield Tablet has been great, never any issues until today. I was just browsing the web, gaming a few games, not installing anything or messing with system files are anything like that, and out of no where my power and volume buttons just stopped working! Heres the strange part though, they only stop working once the tablet is booted up. They work fine to power the tablet on from a cold boot, and they work fine in recovery mode (volume and power buttons), but one the tablet it booted the stop working. The only way to get the screen to wakeup once booted it by removing the stylus. To power down or reboot I have to use the terminal emulator, or hold the power button down for 10+ seconds to force a shutdown. Just pushing the power button once the tablet is booted up does nothing (it should either turn off the screen or bring up the power/reboot menu), same goes for the volume buttons, once booted they stop working. It has to be a software because the buttons work in the recovery. Has anyone else seen anything like this, and/or know how to fix it? I REALLY don't want to have to do a factory reset....
Never mind! I figured out what was wrong. I caused the problem and just didn't realize it. About a week ago, I was trying to use a ProEX brand Xbox 360 wired controller with my tablet using a USB OTG cable and for some reason the right thumb stick was being mapped to the trigger buttons. So, long story short, I copied all the info from the Xbox 360 controller map file in android and pasted/overwritten all the map settings in the Generic.kl file (which is what the ProEX controller was using for its mapping). By doing that, I basically accidentally removed the Power, volume up, and volume down key mapping because those keys are mapped from the Generic.kl file. I just didn't realize that's what caused the issue because it didn't take effect immediately. It only took effect after I rebooted the tablet several days later.
Also, this is kind of a double post, so if any mods would like to, please delete this thread. Thanks
OK, my Shield Tablet has been great, never any issues until today.
I was just browsing the web, playing a few games; I was not installing anything or messing with system files or anything like that (I am rooted on the stock 5.1.1 ROM though), and out of no where my power and volume buttons just stopped working!
Heres the strange part though, they only stop working once the tablet is booted up. They work fine to power the tablet on from a cold boot, and they work fine in recovery mode (volume and power buttons), but once the tablet is booted up they stop working. The only way to get the screen to wakeup once booted it by removing the stylus. To power down or reboot I have to use the terminal emulator, or hold the power button down for 10+ seconds to force a shutdown. Just pushing the power button once the tablet is booted up does nothing (it should either turn off the screen or bring up the power/reboot menu), same goes for the volume buttons, once booted they stop working.
It has to be a software issue because the buttons work in the recovery. Has anyone else seen anything like this, and/or know how to fix it? I REALLY don't want to have to do a factory reset....
Never mind! I figured out what was wrong. I caused the problem and just didn't realize it. About a week ago, I was trying to use a ProEX brand Xbox 360 wired controller with my tablet using a USB OTG cable and for some reason the right thumb stick was being mapped to the trigger buttons. So, long story short, I copied all the info from the Xbox 360 controller map file in android and pasted/overwritten all the map settings in the Generic.kl file (which is what the ProEX controller was using for its mapping). By doing that, I basically accidentally removed the Power, volume up, and volume down key mapping because that's keys are mapped from the Generic.kl file. I just didn't realize that's what caused the issue because it didn't take effect immediately. It only took effect after I rebooted the tablet several days later.