Database Users

[Q] Nexus 7 gyroscope issue

I've had my 1st gen Nexus 7 for almost a year, got it in December as a Christmas present to myself and I've had a few problems ranging from the screen not rotating, to aiming issues in fps games and some random reboots, all of these problems usually fixed themselves or I fixed them through tips and guides online.
However this time I'm a little confused; My Nexus 7 last week had a minor issue regarding screen rotation for a day or two in which it seemed to have stuck either in portrait or landscape and it fixed it's self, although since then I still check by rotating my screen on it's 4 ends to check if it does this correctly because I'm paranoid like that.
Now my current issue is with the gyroscope I believe, in games that have the option to use it, I do like in Modern Combat 4, it makes it easier to aim than using the touch screen to manually aim and fire, before I was able to move the camera in every possible direction to aim my weapon and had no issue, although this time my problem is just that.
I try to aim and it lets me for a moment and then it wants to center it's self and then it's really difficult to move my tablet around to aim at all, although moving it really quickly in another direction fixes it, then I try to aim again and it gives me trouble moving the camera.
Not really sure what to do now as I've tried to do my usual things to fix it, and there are two ways I check to see if it's a major problem, I check Modern Combat 4 and see how the aiming is with the gyroscope enabled, and The Sims Freeplay, the reason I mention the Sims is because earlier this year when I was having gyroscope issues my sims would react as if I was flipping the screen from one landscape to the other and would constantly do this.
Also during this time my screen wouldn't rotate but after a week or two the issue somehow fixed it's self and it was fine until now, although the issue is just aiming in FPS games and my sims react just fine now as I can freely rotate my screen without a problem.

Nobody?

JohnathanKatz said:
Nobody?
Click to expand...
Click to collapse
I direct you to the Google forum on the Nexus 7 Sensor (aka Gyroscope) problem.
Since I am brandy new on this forum, I can't actually post the URL here:
productforums.google.com/forum/#!topic/nexus/GgnRFsw3o-Q%5B176-200-false%5D
There look to be about four or five different problems with sensors including the orientation/gyroscope sensor.

redgatormds said:
I direct you to the Google forum on the Nexus 7 Sensor (aka Gyroscope) problem.
Since I am brandy new on this forum, I can't actually post the URL here:
productforums.google.com/forum/#!topic/nexus/GgnRFsw3o-Q%5B176-200-false%5D
There look to be about four or five different problems with sensors including the orientation/gyroscope sensor.
Click to expand...
Click to collapse
I've checked it out and it doesn't seem like many solutions helped, I'm under warranty so I may just send it in for repairs.

[SM-G730A] ATT Galaxy SIII Mini (KitKat/Touchscreen Issue)

I am not sure how many owners of the SM-G730A are mobile gamers at all, but maybe some of you have noticed this...
Since the update to Android KitKat 4.4.2 the touchscreen behaves erratically in certain games, primarily FPS shooters. I know it is not an issue with my particular device, goto Google Play and look up Dead Trigger 2. View the reviews for this device model only, you will see numerous complaints beginning after the date the OTA was released (8/27/14) complaining about the touchscreen controls.
I have downloaded the kernel source code from Samsung for both 4.2.2 and 4.4.2. Upon examining the kernel source, the Atmel touchscreen driver has been updated in 4.4.2. I believe this to be what is causing the problem. I am not sure if it is configured incorrectly or if it is just a poor driver. The Jelly Bean driver gave NO issues what so ever. I would revert back to 4.2.2 Jelly Bean if I could. I also compiled a kernel for KitKat which includes the Jelly Bean Atmel driver, however due to the locked bootloader, it does me no good.
What happens is this, you will have two fingers on the screen. Suddenly it is as though you lifted one, even if you are still touching the screen. Touches are erratic for a few seconds after this happens, then touch returns to normal temporarily until it happens again (usually only a few seconds later). This makes using the device for gaming extremely annoying, and difficult. This issue does not occur in normal use, only gaming, where there is rapidly changing multitouch inputs.
If any of you have noticed this, maybe you can contact Samsung/ATT complaining of the issue, if we're lucky maybe a patch will be released. Or it will be fixed in a future firmware update. I already wrote to both, ATT says they will forward the complaint to their management, Samsung has yet to reply.
http://www.samsung.com/us/support/contact / [email protected]
Also, this is a video I created demonstrating the problem. The video includes annotations describing the issue that can only be viewed from PC YouTube.
https://www.youtube.com/watch?v=3FMEPB51Y-4
Thanks for reading.

Has anybody with this device tried a multi-touch test? I'm starting to wonder if it's related to my screen protector. The issue only started after the KitKat update though, immediately after. I do a good amount of mobile gaming or I'd never have noticed it still to this day. Never presents itself outside of fps games.
Best way to check (within multi-touch test app):
Touch screen with two fingers.
Keep one stationary and rapidly slide the other around for a few seconds then stop and lift that finger only.
The stationary touch will act as though you lifted even though you didn't.
Sometimes touches will be erratic for a while if the test is repeated several times.
If anyone tries this please let me know if you have a screen protector or not and how it behaved. Thanks.

Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt

quakeaz said:
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
Click to expand...
Click to collapse
Its the phone mine does these same. Might just be a cheap screen make

Deonta23 said:
Its the phone mine does these same. Might just be a cheap screen make
Click to expand...
Click to collapse
Thanks for verifying. It's not the screen itself from what I can tell. I tried this on Jelly Bean with no issues. I did go through the kernel source for KitKat and believe it is the KitKat kernel touch driver. I am hoping for ATT/Samsung to release a kernel patch. The multitouch was perfect in JB.

compass not working?

I tried a few random compass apps and none of them seem to work (the needle does not point to a fixed direction as I walked around). I tried this with and without wifi/data/location. Can anyone confirm this?
I really like everything else about the phone and I would hate to RMA this just because of the compass.

case-sensitive said:
I tried a few random compass apps and none of them seem to work (the needle does not point to a fixed direction as I walked around). I tried this with and without wifi/data/location. Can anyone confirm this?
I really like everything else about the phone and I would hate to RMA this just because of the compass.
Click to expand...
Click to collapse
I also have troubles with the compass. Tried calibrating it a few times, as per the guidelines Google give out. However it just doesn't seem to want to stick!
Anyone else confirm the issue?
Sent from my Nexus 6P using Tapatalk

I'm also having issues with the compass. Doesn't work as a compass should. Turning around 180dg the phone makes north 180dg from where it was before.

copong said:
I'm also having issues with the compass. Doesn't work as a compass should. Turning around 180dg the phone makes north 180dg from where it was before.
Click to expand...
Click to collapse
I still haven't been able to solve this, not sure if it's a software or hardware issue?

I've just managed to fix it, it was a calibration issue but I fixed it with a different calibration routine as the one in google maps did nothing.
Installed https://play.google.com/store/apps/details?id=com.brothers.compass
Then press the menu button at the bottom right. That goes straight into calibration mode with instructions.

copong said:
I've just managed to fix it, it was a calibration issue but I fixed it with a different calibration routine as the one in google maps did nothing.
Installed https://play.google.com/store/apps/details?id=com.brothers.compass
Then press the menu button at the bottom right. That goes straight into calibration mode with instructions.
Click to expand...
Click to collapse
I've managed to get it to work for a while, but the calibration won't stick after reboot.
Sent from my Nexus 6P using Tapatalk

Damn, same here. Anyone else?

No issues here.

There is a discussion on Google's forum at https://productforums.google.com/forum/m/#!msg/nexus/SK7gbrV5MhU/X4OdqoheBQAJ. Seems the 5X is also having the same issue. Post your problem there to hopefully help get it sorted out quicker.
Sent from my Nexus 6P using Tapatalk

After I finally got the November security update tonight, some of my Play store apps needed updating too. (I'll get to the point in a minute, I promise) One of those apps was Google Maps. I opened it & tapped on the location icon (so the image will turn as I do) & a pop-up came up stating that my compass was not correct & to turn it in several directions in succession to fix it. It may pop up for you too.
If you do not see that, do this: It asks you to hold your phone upright screen facing you (while in Maps) & fan it towards you then away, towards you then away. Then turn it in the air like the 4H queen wave, just twisting your wrist. Then while still facing you, rotate it to the left & right, like you're going to bang the sides of the phone on a table. Do each motion 4 times.
After doing that, the compass is dead on! Unfortunately, it doesn't hold the calibration after shutting the screen off though & backing out of Maps but it's a start without installing an app to do the same thing.

copong said:
Damn, same here. Anyone else?
Click to expand...
Click to collapse
Yep me too. Thank god for XDA. I was thinking I was the only one with no compass (although a 5 minute drive showed navigation works fine). It isn't a deal breaker for me because...
Nearly everything else is just good on the money, great display but not natural white (bit like the old AMOLEDs from the Note 2 that I have) with no pink or yellow hues, great sound (except in calls, loudspeaker only uses bottom to play out the audio), superb fast and crisp camera especially the FFC (but bad stabilisation in videos), beautiful design esp in the frost finish, phenomenal imprint scanner, very good battery life seeing as I'm coming from the venerable Z3 (but it can vary wildly, rogue apps perhaps), excellent build quality as mine doesn't have any QC nicks or rattling noises (apart from the camera lens, which is par for the course), bluetooth works without cutting off via 'cupping', Maps is locked at 60fps for the first time in Android history (and uniquely on this Nexus only), charging is quick and I'm glad it is type C (very convenient).

OP2 Screen rotation periodically stops working

Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!

OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.

utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.

k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13

Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.

Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.

Touchscreen Issues

I've just purchased a Tab S5e but appear to be having some issues with the touchscreen. I first noticed it when scrolling, occasionally the scrolling would stop and the device would click on anything that was under my finger. I also noticed this when playing a game where a finger needed to be held on the screen, it was sometimes appear to the game that my finger was removed.
I recorded a video of what i'm experiencing here: https://drive.google.com/file/d/1-33ixSpHRijjhb8g-MNLvbjMvuPRuGrQ. I did not remove my finger at all whilst drawing in white, but gaps appear.
I guess my question is has anyone else experienced this, or could this be a hardware fault? I thinking of returning this and waiting for the S6e or similar rumoured to be out soon.
Thanks all!

I'm experiencing touch screen problems where I sometimes need to tap the display 3 or 4 times before the screen will register the touch. I've only had mine for a few days but Im thinking about returning as well.
I was going through the threads for the first time to see if there were similar issues reported or tips to minimize the issue.
After switching from the Huawei Mate 20 Pro to the Samsung S10+ and from a Huawei tablet to this I have to say I'm seriously underwhelmed with Samsung.

jhs39 said:
I'm experiencing touch screen problems where I sometimes need to tap the display 3 or 4 times before the screen will register the touch. I've only had mine for a few days but Im thinking about returning as well.
I was going through the threads for the first time to see if there were similar issues reported or tips to minimize the issue.
After switching from the Huawei Mate 20 Pro to the Samsung S10+ and from a Huawei tablet to this I have to say I'm seriously underwhelmed with Samsung.
Click to expand...
Click to collapse
Did you somehow solve the probelm?

k.bergmann2 said:
Did you somehow solve the probelm?
Click to expand...
Click to collapse
Nope. The problem doesn't occur when playing games or using apps that test the display--but does with pretty much everything else. Some apps also have very pronounced jelly effect while scrolling including the Samsung Members App--scrolling through posts has so much jelly effect it makes me feel like I'm going blind.
Earlier Galaxy Tab devices had a calibration setting to adjust touch sensitivity but the type of panel used in the S5e apparently can't be user calibrated. Some people have claimed that the pointer speed setting is the same thing but touch sensitivity and response speed aren't the same thing and increasing that setting to the max didn't improve anything for me. If you want a faster response that's one thing but if the touch doesn't even register in the first place then there isn't anything to speed up.
The game optomizer service running in the background clearly ramps up the kernel when playing games to eliminate or minimize the touch issues and display test apps are treated like games and also get the extra performance boost--but with a locked bootloader I don't think there are any user options besides not purchasing Samsung in the first place.

Would a custom rom solve this?

k.bergmann2 said:
Would a custom rom solve this?
Click to expand...
Click to collapse
I always check before buying a tablet to make sure there is developement of custom ROMs in XDA. And the first thing I do when I get one is to root and install one. Are there still "touch problems" with my ROM? Yes and no. I've noticed with this and other tablets that when the tablet first boots, there can be a lag in touch response. But I don't think it has anything to do with "touch sensitivity". I think the problem is that the OS is still "setting up" and just isn't ready to accept touches. (Try it on a Win 10 box. There is a terrific delay between the time the desktop screen first appears and the time it is ready.) This can also be true of apps. The screen can display before the app is ready for input. IMNSHO, I think some people just love to find reasons to knock "the vendor they love to hate".:crying:

Since I bought this tablet, I noticed that issue, the screen detects the touch, but it does not perform the action I want, open an app, select something,etc. I learned to live with it, but that is annoying !!, I installed a Custom ROM specifically [ROM] [UNOFFICIAL] [gts4lvwifi] [10] LineageOS 17.1 and I can confirm that the issue disappears, the problem for which I returned to STOCK, is the cut down quality of Amazon Prime Video, Netflix, because Widevine Level certification . and now in STOCK, I lost Samsung PASS, because it detects that I have the rooted device. fyi, my model is SM-t720.