I recieved my Shield Tablet + Controller a few days ago and have used it for about 3 hours all told. I haven't modified it at all other than installing some apps.
For some reason both shoulder buttons stopped working today, at the same time I think. I did update using OTA MM last night, not sure if this coincided with the buttons ceasing to work though. I *think* they were working afterwards but I'm not sure.
I thought "AHA!" when I noticed an controller update but the problem persisted after applying the update and restarting the device still.
Is anyone able to shed any light on a fix for this? It seems to me it's most likely a software issue since both stopped together at the same time I'm pretty sure, I wouldn't expect this if it was a problem with the physical device.
After opening the Gamepad Mapper I cannot select the < or > buttons because they're greyed out.
Which I think confirms this is a software issue.
Downgraded to Lollipop 5.11, buttons still not working.
Hi! I have also buttons problem after last 1.5 OTA update (Shield K1 version). Did you solve your problem?
I can't stress it too often: updates are bad.
Why fixing something that works?
Related
Hello there, Quick question.
I recently upgraded TomTom Navigator 7 on my SE XPERIA X1 from version 7.450.9028 to version 7.910.9185 mainly for the fixes for a WVGA screen e.g. larger buttons and text.
However, I have found that the phone always seems to freeze when using TTN7. I never found this with the previous version however, the improvements are too improved to revert back to the old version.
Is this problem caused by the application or the phone as the screen becomes unresponsive when freezing (e.g. it doesn't vibrate on tap) giving the idea that the phone's memory is full when running the application and causing the phone to slow down.
Cheers,
Hyped
I have been experiencing the same issue on my Xperia X1 that you've had Hyped. I am actually running version 7.915.9196. Basically, TomTom will be fine UNTIL it gets a GPS fix. Once that has happened, it is only a matter of 1-2 mins before the whole phone locks up, requiring a battery cover removal + reset button fix.
I also don't want to revert to the previous version, but I'm thinking it may have to come to this I have the ATI D3D driver installed from the Diamond, and I'm planning on removing it to test, but I don't think TomTom calls D3D at all (in fact, im 99% sure), so I doubt this will fix the issue.
Looking for more insight from anyone else, or if there's a newer version of TT7 that we're missing out on.
Mine is touch and go, When it hasn't got a GPS fix, it'll freeze at random moments e.g. when the keyboard is up.
I tried it yesterday in the car and experienced the same problem as you, as soon as it got a GPS fix it froze up and required a soft reset.
Hello, I have an issue with the touchscreen of my nvidia shield tablet.
I bought the tablet only one week ago and I'm on the Stock lollipop version 5.0.1 (2.2), but I had the same issue with the KitKat version.
When I hold my finger on the screen and I change direction, the shield take a long time (about 1 second) before validate this change of direction.
This issue make all my games unplayable in touch mode. (If I use a controller, this problem doesn't exist)
I wanted to post a video to show the problem but I can't because I'm a new user. (I can pm the link if necesserary)
On this video I activated, in the developer mode, the trace of the movement to see that the lines moves very late after my finger. (I'm doing the same test with LG G Pad to compare and see that it respond perfectly)
In the Real Racing Game: I move my finger with very little fast movements and the wheels doesn't move at all.
I tried the calibration tool in lollipop but the problem persists.
I tried also a Custom Rom ([ROM][4.4.2][wx_na_do] AOSP for Nvidia Shield Tablet LTE US)
My questions:
- Does every Nvidia Tablet Shield have this problem or is it only mine?
- Is there a way to configure the pressure and move sensitivity (from the config file /system/usr/idc/touch.idc)
I would like to know if someone has the same issue to know if I have to send back my tablet in warranty.
Thanks in advance for your time.
I've had this issue, but only while charging. More noticeably while charging using 3rd party chargers, though the nvidia charger does have some "lag" as well.
phuzznut said:
I've had this issue, but only while charging. More noticeably while charging using 3rd party chargers, though the nvidia charger does have some "lag" as well.
Click to expand...
Click to collapse
Thanks you for your answer.
I have always this problem, I never tried when the tablet is charging.
In fact the touchscreen is relatively responsive when I touch and release quickly.
The problem is when I let the finger on the touchscreen and I change the direction slowly with small moves.
Hello,
I re-up this post because I really need your help.
I sent back my tablet to the seller for my touchscreen issue.
But they don't undertsand and tell that there is no problem with the touchscreen.
They compared to another Nvidia shield and told me that the response is the same than mine.
I can't believe that all the Nvidia shield has the same response because for me all the games are unplayable.
So I would like to know if someone has the same feeling (delay) about the touchscreen when you slide and change laterally the direction with your finger to play games like racing or platform games.
Thanks in advance
Sorry if I open this again.
I've been going crazy with this issue too and have been looking around for a fix, too.
I tried applying different configurations to my /system/usr/idc/touch.idc file, without any noticeable differences.
The only setting that works for sure is 'touch.size.calibration': the possible values are "none | geometric | diameter | area | default". Whatever I set besides 'none' will make the touchscreen work like a touch pad (you scroll around and there's a little cursor moving, you tap and it taps on the cursor's location).
I'm not sure which setting (if any) can calibrate the touchscreen for small movements. The documentation is a little unclear (I only found this: https://source.android.com/devices/input/touch-devices.html ).
Does anyone know more about this configuration file? I believe it's a common issue for all the shield tablets, it would be great if we were able to fix this.
Please note that root is required to edit that file, of course. Plus, the /system partition needs to be writable (mount -o rw,remount /system).
Same issue on new k1
Same issue on K1
I purchased an new K1 today and am experiencing the same issue. After enabling "show touches" in developer options it is very clear that the display periodically becomes unresponsive. I have also tried to re-calibrate the display with the Sensor Calibration Utility with no change. This happens while NOT connected to a power supply. So, I'm not sure what else to try.
What have others done about this issue? Do you return the device to the reseller? Because as it is, I can't play most games and find a typical browsing experience annoying.
Thanks in advance for any advice.
After trying everything, including full wipe, different Rom etc, I have returned it to the reseller. I got another one and and am very happy with it. Turning screen off and back on gets the responsiveness back for a while. Good luck with swapping it for new one, reseller I dealt with made no issue of it.As I have restored tablet to factory settings,I have just shown a video of a tablet going all crazy to a guy at the counter, and he gave me a new one.
Acidicus said:
After trying everything, including full wipe, different Rom etc, I have returned it to the reseller. I got another one and and am very happy with it. Turning screen off and back on gets the responsiveness back for a while. Good luck with swapping it for new one, reseller I dealt with made no issue of it.As I have restored tablet to factory settings,I have just shown a video of a tablet going all crazy to a guy at the counter, and he gave me a new one.
Click to expand...
Click to collapse
Thanks. I appreciate you sharing your experience on this. I got it from Amazon, so I hope they are cool with it.
My GF's M2 Aqua has a bug with the accelerometer. If she makes a longish phone call the accelerometer stops working (i.e. no auto-rotate) without a reboot. Looks like I'm not the only one:
https://talk.sonymobile.com/t5/Xperia-M2-M2-dual-M2-Aqua/accelerometer-bug/td-p/918650/page/16
Anyone else facing this?
Apparently Sony are finally looking into it and hopefully will issue a fix in another firmware release.
Usually I'd just flash a custom ROM but there doesn't seem to be any reliable builds with a fully working camera...
I confirm that this happens to me too, I just hate it because it worked if I had NFC activated in the update before 18.3.1.c.1.13.
temporary solution
it seems that the proximity sensor has something to do with it.
somehow after a long call it stucks and blocks even the accelerometer and the compass sensors.
it happens even to me and you have to restart your device to work again, but if you talk using the headset or if you press the power button while you are talking at the phone you can avoid the bug.
for me is working all the time and i can wait patiently until the official fix
Looking at the other thread I posted, one of the users said a new firmware update has been pushed with the same version number. Let's hope it fixes it...
Accelelometer bug tread
maxray said:
it seems that the proximity sensor has something to do with it.
somehow after a long call it stucks and blocks even the accelerometer and the compass sensors.
it happens even to me and you have to restart your device to work again, but if you talk using the headset or if you press the power button while you are talking at the phone you can avoid the bug.
for me is working all the time and i can wait patiently until the official fix
Click to expand...
Click to collapse
Thanks for the tip, but :confused for how long should i press the power button...just one click or during the conversation?
Just enough to wake up the screen, can't say as my M2 has it as never had a problem of on my own one
D2303 stock 4.4.4 KK rooted philz touch recovery xposed Bravia engine 2 x-reality
I think it only affects the Aqua (2403) model. Anyway, I installed a kernel for the standard M2 model following the instructuions here: http://forum.xda-developers.com/xpe...a-2403-root-philz-touch-t3072833/post60152564 and it seems to have fixed the issue.
Apparently Sony are about to issue another software update, but I'll hold off on that until I know the status of this bug...
I have the latest update 1.15 and it seems that it doesn't have the bug anymore. I am quite happy now with phone. Hope it works for everybody
Anyone having the same issue and have found a solution?
Phone suddenly stuck at some instances even with non-extensive usage.
Yesterday I was only using Facebook app. When messenger bubble pop up, my phone suddenly spiked. Moved once and then it got stuck already. You'll notice that it's not Facebook app only that's not functioning since nav. buttons are also stuck. You can't go press home and clear recent apps/hibernate apps. Power and volume buttons are also not functional.
So I assume the main system crashed. I only did a long press on power button to restart.
I installed Franco kernel r73, and thought that issue would only occur with stock kernel.
However, it occurred again today, I was viewing photos in Stock Photos app. I haven't started viewing the first 10 images yet, so memory should not be consuming that much. I turned on the auto rotate to view the image larger. When I turned the phone landscape, it reacted like it's about to rotate. And suddenly it got stuck. This time, power button is functional. It turns the screen on and off but it still turns to the same stuck screen, not the lock screen.
I've been experiencing this since 5.0.1. and almost everyday since I updated to 5.1.
I'm not sure if this is a hardware issue on my unit since mine is already about 1 year and a half old. I don't want to buy another phone yet!
Or is this a common issue nowadays due to Lollipop upgrade. If so, then could you provide temporary fix before they update this on 5.1.1.
Thanks a lot!
I had something similar . When I put forward the curtain hangs notice and then everything worked fine
Meh
I've seen this behavior on my Nexus 5 only on 5.1, and I'm pretty sure, it was introduced with that specific lollibug version. It's really annoying, that you have to reboot the phone every two or three days to avoid the freezes.
There's already in issue for that, it has got the ID 161032.
Hi i bought yesterday nvidia shield k1 and all is well but when i play fps (critical ops) i found one problem with touchscreen i don't know but it's embarassing i use 4 finger and sometimes i have touchscreen delay when i use 2 finger at the same time
i think multi touching is bugged
Can u help me please
Thank's :crying:
thats strange mate that game is fine on my tablet, try a screen touch test app and see if it happens there too
i find the problem it not about multi touch it about slide delay
can i fix slide delay ?
https: //www .youtube. com/watch?v=08uPtusOJHQ
There was an old bug similar it only occured when low quality power bricks were used. If you play while plugged in try playing not plugged in.
It changes nothing at all I already play plug and without plugging anything changes
What version of software are you running and I'd factory reset the tablet it might clear up a bad update or something
SHIELD TABLET K1 6.0.1
And i don't know but in the video he has got the same problem of me