My wife's S6 auto rotation stopped working. We tried various workarounds and suggested solutions. We eventually found it to be a hardware issue, and it sounds like it's something common for the S6 Edge folks.
If you're experiencing issues with auto rotation, quickly do a hardware check by dialing *#0*#, tap sensor, and if the "X" is stuck on -32768, then exchange for a new one. I got on T-Mobile chat, skipped all the BS and mentioned my “X” is stuck on -32768, and customer service said they're overnighting a new device. No questions asked, so guessing they're aware of the hardware issue.
This is probably why https://youtu.be/e2p_p3Dh5PE:cool:
Related
Why doesn't google respond to this http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
A ton of people are complaining and I really can't see why this could be a hardware problem when it goes away after you lock and unlock the phone. This happens a lot to me and is super annoying. Here is a video of it:
http://www.youtube.com/watch?v=4DmVV_B-SE8
What do you think can we pinpoint this?
I really think this issue has to do with accelerometer. When your screen goes crazzy try using it in other position, the behavior changes a little until it dissapear without turning off the screen.
im having similar issues, when i tap, say, in the middle of the screen it registers as a tap on the bottom, this is only occasional, and rebooting seems to temprerarily(sp?) fix this issue, however it is quite annoying, and in op's link there are a bunch of other users having the same problem. now, what happens to us that have unlocked the bootloader if this is NOT a software issue. i have only had my nexus for a week and i would be quite depressed if this is a hardware issue and it cannot be fixed/replaced because of a manufacturer defect.
Hello everyone,
I had a friend of mine purchase a T-Mobile Nexus One on eBay for me today and I am pretty excited coming from HTC Magic.
Today, I also realized that I haven't looked up Nexus One problems on the Internet. Being a fan of the android platform and going up and down through android blogs, I never read anything bad about the Nexus One and I totally forgot.
Just now I did a quick research and found out that the Nexus One has a bunch of problems which gets me worried.
Are there different revisions of the Nexus One hardware which don't have one another's glitches? Or are all the bugs I found fixed with the software updates? The problems I read about were experienced right after the Nexus one launch 1 year ago and people are running 2.1.
I'm pretty worried that I may have bought a faulty device since it's a used device even though it looks to be in excellent condition judging by the photos.
Any calming advice?
Here are the problems I found that people are experiencing
P.S. The phone will be used in Europe so I'm not sure about that 1st 3G issue.
1) 3G connectivity issue
2) Touch Screen unresponsiveness/sensing incorrect input
3) unresponsive trackball
4) WIFI connectivity issue
5) Lock button response issue
6) Proximity sensor sensitivity issue
7) Ambient light sensor issue
8)bluetooth issues: fails to operate; inadequate volume; intermittent failure to accept commands
9) speaker: horrible sound quality
10) ringer: insufficient volume
11) earpiece: insufficient volume
12) headset connector: headphones cord activates pause or other functions
13) manufacturer says phone cannot go in pocket
14) Phone mutes when calling people and can only be unmuted by turning mute on then off!
15) missed call notification trackball does not flash
Click to expand...
Click to collapse
The only worry of you is about 5) Lock button response issue it could fall down.
Besides the 2) Touch Screen unresponsiveness/sensing incorrect input which sometimes is annoying the other things can be resolved by software..
Anyway congratulation for the acquisition!
Thanks
And is the lock button issue fixable in some way? Also, is the touch screen issue observed on every device with every ROM? Is it a hardware issue?
1. Never existed in 1st place.
2. HW fault. Seems that you can't do anything about it.
3. Never existed.
4. WiFi sleep bug - solved in SW update a long time ago.
5. Power button is prone to failure. Use it lightly and avoid using it as much as you can (using trackball wake) - and it'll last.
6. Never existed.
7. Never existed.
8. Never existed.
9. Not horrible, just low volume. Hack exists in SW.
10. Hack exists in SW.
11. Hack exists in SW. And it's not a fault, anyway. Some complain that after the hack it's way too loud.
12. It's a feature, that doesn't work well with non-stock headphones. Can be deactivated easily.
13. All manufacturers do, and phones still go in pockets.
14. Never existed.
15. Most probably caused by incorrect update to Gingerbread. Reflashing solves it.
I don't know if this addresses all the issues related to proximity sensor & in-call display touch triggering issues but I recently had this issue on my MI A2. So I checked if this is a software related issue. I called the Xiaomi Customer support if they had any knowledge about such an issue. I even searched for this issue on xda and none of the solutions worked for me. Then I stumbled upon an article in gsmarena which was a long-term review of MI A2, where they faced a similar issue during calls and that was in November 2018. Then I thought if the issue was with software then it would have already been fixed. So I visited the nearest Xiaomi service center and got my device checked and they told me the issue was with the display(I never had any issue with the display outside of calls so it never occurred to me that the problem I had would be a display issue). So after 2 weeks I got my display replaced and its been 3 days since then and the problem is gone. So suggest to whoever is facing this issue or a similar one please get it checked at your nearest service center and get your display replaced. It still hasn't been a year since the phone got launched so you can still claim your warranty. Sorry if my English was bad.
Hello there!
I'm experiencing a weird issue after the latest update from December 2020. Since then, my back button (or technically the lower part of my screen) is very irresponsive and does not register touch input. I uploaded a video on Youtube to showcase the issue:
What you can hopefully see is that the back button is very responsive when it comes to horizontal movement; touching far left or far right of the button is still registered as input. However if I touch just slightly below (or sometimes even on) the icon, it does not register my input. This includes the fact that the system does not register the touch at all (as you can see by the active developer tool). This is very frustrating as it also happens with the other two buttons. It seems as if Google has incorporated a kind of "palm detection" or "accidental touch prevention" on the far edges of the screen.
I already activated the "High sensitivity mode" of the display since I have a screen protector installed. However, before the update the issue was not apparent, so I'm convinced the screen protector is not the issue.
Does somebody also experience the issue or may even have a solution for this?
Cheers!
WookieCookie said:
Hello there!
I'm experiencing a weird issue after the latest update from December 2020. Since then, my back button (or technically the lower part of my screen) is very irresponsive and does not register touch input. I uploaded a video on Youtube to showcase the issue:
What you can hopefully see is that the back button is very responsive when it comes to horizontal movement; touching far left or far right of the button is still registered as input. However if I touch just slightly below (or sometimes even on) the icon, it does not register my input. This includes the fact that the system does not register the touch at all (as you can see by the active developer tool). This is very frustrating as it also happens with the other two buttons. It seems as if Google has incorporated a kind of "palm detection" or "accidental touch prevention" on the far edges of the screen.
I already activated the "High sensitivity mode" of the display since I have a screen protector installed. However, before the update the issue was not apparent, so I'm convinced the screen protector is not the issue.
Does somebody also experience the issue or may even have a solution for this?
Cheers!
Click to expand...
Click to collapse
Yes, I've noticed the same thing. Seems to be only the back button.
This is a widespread issue that has been reported by many. So far there is still no update from Google. I am running November build without any touch issues. Google support forum with lots of people reporting.
same problem for me, I hope it will be fixed soon
Looks like this is fixed in the January, 2021 release that came out today!
This issue was NOT fixed in the January release. I and many others are confirming this. Google has yet to fix a major touch-screen bug, almost 2 months after the issue was brought up.
Mine was definitely better in the January release, but yeah, still having the issue here and there (especially when an app is heavy on the processor). This press release should help out: https://www.androidpolice.com/2021/...ssue-can-make-navigation-buttons-hard-to-use/
Same here. But on another side, why do we have to wait another month for a known issue?
Hello,
I havent' posted anything here in years, so I'm out of touch with the latest on this forum. Ever since I got my Note 8 (International unlocked dual-SIM model), my GPS stopped working after the first week. I know this is a Samsung thing, so I lived with it.
Now my accelerometer stopped working mysteriously, and I'm already on the latest firmware which should have fixed the GPS issue (but it didn't).
When I do the hardware test (*#0*# from the dial screen) it shows no movement in the roll, pitch or yaw axis and the same for the magnetometer). I've done numerous reboots, and toggles of the auto-rotate feature of the phone, but the issue is still the same. Other than a factory reset, what other troubleshooting steps can I take?
Perhaps there is a toggle in Developer Options or in Quick Settings that you accidentally switched?
I'm saying this because Stock Android 12 has a "Sensors off"-QS Toggle that disables sensors on the phone ^^
But... I don't remember the Galaxy Note 8's software having such a button...but just throwing this out there
Thanks for your reply. I had checked for such an option. I even disabled Developer Options altogether.
I did the Samsung hardware test (*#0*#), and neither the accelerometer nor the compass moved.