Database Users

[ISSUE] Touchpad stopped working?

I'm terribly sorry if this question has been asked over and over again, but I tried to search but couldn't find a similar case. I called even ASUS's customer service and they were unable to help.
Anyway, after updating to 3.1 firmware, it seems that my touchpad has stopped working when using the dock.
- All buttons on the keyboard work perfectly
- Touchpad doesn't do anything, there is even no cursor on the screen
- I have tried factory reset and the touchpad is turned on (via fourth function button from the left)
- I tried plugging in a USB wireless mouse receiver and that works perfectly
Has anyone had the same issue and have you find a solution?

Does the dock icon appear on the bottom right?

May work if you let the battery drain but for others of us that had the issue we had to return them. Including me there are 3 people at work with one and two of us had to return for this issue. Someone else posted they knew a Fry's that had to replace the floor model 3 times. Its a very common problem and 90% of the time no fix. It appears software so eventually there may be a fix.

OK, thanks for the info. I'll try draining the battery out.
Sucks to hear that it might be unfixable because I bought the device from a different country I live in so returning it is a hassle.
However, given that the keys of the keyboard work and so does a USB mouse, I might settle with the device for a while and wait if it is fixed in the possible 3.2. update.
(Malandro: yes, the dock icon appears in the lower right corner and works otherwise perfectly OK, only the touchpad/mouse thingy is unresponsive)

Just for good measures you didn't hit the disable/enable touchpad hot key on the dock did you? Sometimes things might be simple. K.I.S.S (keep it simple stupid) method has bit me in the butt plenty of times.
Sent from my HTC Glacier using XDA App

danr238 said:
Just for good measures you didn't hit the disable/enable touchpad hot key on the dock did you? Sometimes things might be simple. K.I.S.S (keep it simple stupid) method has bit me in the butt plenty of times.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No, I wish it were that simple. It's enabled, I've tried enabling and disabling tens of times but doesn't change anything.

ttyori said:
I'm terribly sorry if this question has been asked over and over again, but I tried to search but couldn't find a similar case. I called even ASUS's customer service and they were unable to help.
Anyway, after updating to 3.1 firmware, it seems that my touchpad has stopped working when using the dock.
- All buttons on the keyboard work perfectly
- Touchpad doesn't do anything, there is even no cursor on the screen
- I have tried factory reset and the touchpad is turned on (via fourth function button from the left)
- I tried plugging in a USB wireless mouse receiver and that works perfectly
Has anyone had the same issue and have you find a solution?
Click to expand...
Click to collapse
Seems like you gave a lot of thought, and did all the tests. I think your touch pad might be bad. It is weird because the timing coincides with your 3.1 update, but it happens. There is one final thing to test. You can place your dock on another transformer, friend or display model in store.
I suggest you try warranty replacement rather than opening the dock yourself. It is almost impossible to open the dock without leaving some traces, in my opinion. Can you return your touch pad for replacement or warranty?
Good luck.

[Q] Beware - N7 screen crash while updating to 4.1.1

Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google (Call us at 0800 328 6081) and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
I include a picture of the N7 display after the unsuccessful 4.1.1 update.
Image https://docs.google.com/open?id=0B3oSwFvF1cmebXE4S2lvZlNlU0E
Cab

Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/

Looks like a defective unit. Not sure what pirates have to do with it.
Via my HTC Rezound

CrazyPeter said:
Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/
Click to expand...
Click to collapse
Thank you for being a productive member of this community, xda would not survive without you.
Sent from the matrix. (or my phone)

Not a good sign that it's doing it in fastboot mode. You can try leaving it in fastboot mode to drain the battery then plug it in and try again. Or, search for the instructions to reapply the stock 4.1 image. If those don't work then RMA it.

That looks very familiar.
A few minutes after the update (which I installed about 10 minutes in to receiving my new Nexus 7) I immediately had a total screen lockup/crash with lovely multicolours.
After that, any subsequent reboot/factory reset, the lockups continued and became more an more frequent until after just a day the device was completely unuseable.
I don't think the update caused it. I think it's factory defective and probably related to a messed-up Tegra 3.

Thanks for the feedback guys - I'm gonna RTM it as advised. A good unit shouldn't go wrong at all when just out of the box with no 'normal' or 'strange' apps added. It just had pure google stock on it.

cabello123 said:
Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
Cab
Click to expand...
Click to collapse
Ok, I was about to post this very thing. Mine went red. Bright red. Nothing worked. Took it back to the store and it turned on fine and looked good...until the manager took it and flexed it a bit. Then, bam. Everything flickered and turned red.
So now I have new one (N7 16gig) and its working great. But the alert comes on telling me to upgrade to the 4.1.1. No way in Hell!! It's an hour drive back to the store to get another.
So what's the solution. Anyone else have this happening?

That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.

jonnyg1097 said:
That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.
Click to expand...
Click to collapse
I was not telling people to beware of upgrading. I was asking if others had experienced this.

cr2crf said:
I was not telling people to beware of upgrading. I was asking if others had experienced this.
Click to expand...
Click to collapse
So I finally updated the os to 4.1.1 Success. Hoping this little tab keeps going. The more I play with it the more I am glad I got it and not a 10 incher

Were these affected units stock unrooted? As a general rule you always want to revert back to stock unrooted before applying any OTA updates.

PS4 Remote Play now live

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.

Gamepad not turning off

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.

Shield won't start

Hello everyone!
I was using the Shield (pro model, 500gb) and suddenly it won't respond to the remote control. I turned the Shild off and then tried to turn it on, but it won't. When I try to turn it on the shield button turns green but only for 1 second and then turns off. Nothing is displayed on the TV. I have tried many times turning on the Shield and it only turns green the button for one second and then turns off.
I have tried the instructions provided here, but to no avail: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=Reset_SHIELD.htm
Has anyone encontered this issue and resolved it? Don't know how to recover my device now
Thanks a lot for your help!
Best regards,
David.

austmathr said:
Hello everyone!
I was using the Shield and suddenly it won't respond to the remote control. I turned the Shild off and then tried to turn it on, but it won't. When I try to turn it on the shield button turns green but only for 1 second and then turns off. Nothing is displayed on the TV. I have tried many times turning on the Shield and it only turns green the button for one second and then turns off.
I have tried the instructions provided here, but to no avail: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=Reset_SHIELD.htm
Has anyone encontered this issue and resolved it? Don't know how to recover my device now
Thanks a lot for your help!
Best regards,
David.
Click to expand...
Click to collapse
Im not a expert in this sphere, but according your written the power button on Shield not lights and this happened without your interfering, my guessing and opinion sounds like you have hardware problem, this symptoms not sounds like software. Try this one and or not I would go sending back by warranty!
https://youtu.be/2AzHF-uNiY8
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
austmathr said:
Hello everyone!
I was using the Shield and suddenly it won't respond to the remote control. I turned the Shild off and then tried to turn it on, but it won't. When I try to turn it on the shield button turns green but only for 1 second and then turns off. Nothing is displayed on the TV. I have tried many times turning on the Shield and it only turns green the button for one second and then turns off.
I have tried the instructions provided here, but to no avail: http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=Reset_SHIELD.htm
Has anyone encontered this issue and resolved it? Don't know how to recover my device now
Thanks a lot for your help!
Best regards,
David.
Click to expand...
Click to collapse
...and BTW you have 16gb or 500gb console?
Izsūtīts no manas Nokia 3310 используя бесплатную xda app

I have a pro (500gb) model. Thanks, I'm going to try this and report back my findings.
Thanks!

Hello again!
I tried what is mentioned on the video but it does not enter into bootloader. The video mentions to press the nvidia button two times and in the first time the green light keeps on. In my case, when I press the first time, even if I keep pressing, the green light just turns on for 1 second and goes off. The second time it is the same, and actually nothing happens
Anyone has encountered this issue?
thanks!

Did you manage to eventually get this sorted?
I have an almost identical problem; the remote for my SATV Pro stopped responding, mid-session, one day.
I had to pull the plug and it would no longer boot, thereafter.
The light will stay on indefinitely, it seems - I left it on overnight to test.
It won't enter the bootloader menu, either; if I hold the power button for 6 seconds, the light switches off and I can still hear the harddrive.

when trying the push button method do not forget,the USB and HDMI should be plugged to each device before start. me I just press for start then I instantly press again and hold,works well .

Did you figure out what happened and if there is a fix for this? My Nvidia Shield Pro is having the exact issue and unfortunately my unit is a month over the warranty period =(.

Same light flash for a second after power, but nothing after. I'm thinking it must be a hardware issue, but how to troubleshoot it? Wish an nVidia engineer would help out.

My 2015 Shield 16GB went dark today and I have the LED on for 6-10 seconds after replugging, and then it shuts itself off. I only see the green Shield logo for few seconds. Tried going into bootloader, but there it too shuts down after few seconds...

same her mine just gave up.

Was Shield Experience 8.2.1 recently released or am I just seeing it now for some reason? Maybe that's what caused your problems?
edit: seems like there are issues with the TV trying to go from 7 directly to 8.2.1. See the sticky:
https://www.nvidia.com/en-us/geforc...ield-experience-upgrade-821released-11162020/

after one night unplugged i got it booting again and it run for about 10 minutes or so.
efter that i have now tried toapply new cooling paste and even tried with another power adapter, but noting seems to help so far.
and as some one else up there said, i can still hear the hdd spin

A very similar thing has happened to me but maybe my difference can shed light on this issue?
I was cleaning (sweeping specifically) and accidentally turned the shield on. I pressed the touch button on the front of the shield to put it back to sleep and I then heard a *pop* sound. After that the shield will only turn on for a second, the green light will come on for a second and then it will switch off.
I opened it up (pretty easy with just my finger nails even) and I can hear sounds coming from the mainboard when I plug it in, like it's still receiving power even though it wont turn on.
I have little to no experience repairing electronics but my assumtion is I discharged enough static to blow the power button board on the front of shield unit.
Also to add, the shield unit will not respond to the inputs of a controller or a keyboard that has been paired with it.
I identified the infinitesimally thin wires that connect the touch power button to the main board but they dont seem to be damaged themselves - I plugged the power supply in while each side was disconnected and the shield unit turned on when I reconnected the wires.
I'm going to assume that if I can replace the power button board on the front of the unit it will work again but I'm not sure and cant be sure unless I can get a spare part.
Or maybe I should just take it to a repair shop?
Has anyone managed to get their unit working properly after this specific issue.
Side note: it's strange how many others have this exact same issue in this exact month isnt it?

Just following up a little bit.
I got a new power supply from Ebay to see if that would make a difference.
It did not - the power supply is not the issue.
Oh just to add - I tried cloning the original drive but I was still able to read it on my computer and the drive-clone didn't change the outcome so that wasnt the issue either.

overdrivepower said:
Just following up a little bit.
I got a new power supply from Ebay to see if that would make a difference.
It did not - the power supply is not the issue.
Oh just to add - I tried cloning the original drive but I was still able to read it on my computer and the drive-clone didn't change the outcome so that wasnt the issue either.
Click to expand...
Click to collapse
I turned mine off at the device last night and, pop, a huge static discharge from my finger. My Shield now exhibits the same behavior as everyone else in this thread.
Just wondering if you or anyone else every figured out a fix? Possibly blow fuse or capacitor in the power circuitry?

No change in status.
I'd like to still fix mine but I ended up buying a mini PC, which is a million times better than a proprietary-hardware device.
It's not locked down like an android only device (even though it runs on win10) and I can do much more with it than just watch movies and play android games/apps.
Anyway if anyone else can find a solution to this that'd be great.

D
DreadfulDrummer said:
Did you manage to eventually get this sorted?
I have an almost identical problem; the remote for my SATV Pro stopped responding, mid-session, one day.
I had to pull the plug and it would no longer boot, thereafter.
The light will stay on indefinitely, it seems - I left it on overnight to test.
It won't enter the bootloader menu, either; if I hold the power button for 6 seconds, the light switches off and I can still hear the harddrive.
Click to expand...
Click to collapse
Did you remember to connect it to a PC via USB first?
Cause if not... Well theres your first problem.

Same here, stuck at circles........
Nvidia Shield TV Pro 16GB 4K HDR

All right guys, I'm back with the following steps
If you own a SHIELD Controller
• Unplug SHIELD TV.
• Connect SHIELD controller to SHIELD TV with a USB cable (use port closest to HDMI).
• While holding the A and B buttons at the same time, connect power to SHIELD TV.
If you do not own a SHIELD controller
• Unplug SHIELD TV.
• Connect a USB keyboard directly to SHIELD TV (use port closest to HDMI)
• While holding the "A" and "B" keys down at the same time, connect power to SHIELD TV.
• Once you enter Fast Boot mode, on the keyboard use the "X" and "Y" keys to navigate the menu and "A" to select
Use the X and Y buttons on the controller to move to "Boot recovery kernel".
3. Press the A button to select "Boot Recovery Kernel".
4. You may see the dead Android robot on screen. This is expected behavior. If so, press B button on the controller.
5. You will see Android Recovery Menu.
6. Use the X and Y buttons on the controller to move to "wipe data/factory reset".
7. Press the A button to select "wipe data/factory reset".
8. After process select "reboot system now".
8. SHIELD will boot to home screen.
Do the factory reset
It will bring you back to recovery
Select "Continue"
device will process and reboot like new
Hope this works....ENJOY
It did for me
I received the above info while chatting with Nvidias tech support