Hello, everyone!
Yesterday I discovered that my device doesn't detect its own orientation. It was after I tried to record a video and it came out vertical. I thought it was a ROM bug (since I was using the CyanogenMod nightlies), but I flashed with RSD Lite (cleanly) both 5.0.1 and the latest 6.0 ROMs and it still doesn't work. Sensor apps detect changes in the numbers when I move the device, though. I haven't dropped my Moto MAXX, and I always use it with a case...
Is there any way to recalibrate the sensors or something? I can provide any information or log if you tell me how to grab them.
Thanks!
Okay, this is REALLY weird. After a whole afternoon believing it was something software-related, I gently hit my device against the table three or four times and now it rotates correctly...
Shooting Star Max said:
Okay, this is REALLY weird. After a whole afternoon believing it was something software-related, I gently hit my device against the table three or four times and now it rotates correctly...
Click to expand...
Click to collapse
A hammer would have fixed with just one tap.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChazzMatt said:
A hammer would have fixed with just one tap.
Click to expand...
Click to collapse
I was kind of desperate about the matter, probably I would have gone with the hammer option if the table hits hadn't worked.
By the way, and following my original post, is the gyroscope a mechanical thing? Or is it electrical?
Shooting Star Max said:
I was kind of desperate about the matter, probably I would have gone with the hammer option if the table hits hadn't worked.
By the way, and following my original post, is the gyroscope a mechanical thing? Or is it electrical?
Click to expand...
Click to collapse
It's the accelerometer.
Here's an issue Samung had with the Galaxy S6 at launch a year ago:
Samsung confirms screen-rotation problem with some Galaxy S6 Edge phones
http://www.computerworld.com/articl...-problem-with-some-galaxy-s6-edge-phones.html
Some Edge users have raised various theories about what causes the problem. One theory is that Samsung's fast-charging cord fried the chip that controls the accelerometer sensor, which affects rotation of images on the display. Another theory is that certain apps on the Edge — either third-party or pre-installed apps — have not been updated sufficiently to be compatible with recent minor Android OS updates. That lack of compatibility could somehow restrict the software controlling auto-rotation.
A Samsung technician on the 800-support line told Computerworld that users affected by the auto-rotate problem are being asked to test the faulty device by first going to "safe mode" to allow the phone to operate without third-party apps loaded by the user. If the problem persists after that test, the users are then asked to try a "hard key re-set" of the phone, which basically wipes all personal data and contacts and initiates a factory reset upon a reboot of the phone. The technician said personal data can first be stored to a remote backup location through the Samsung Kies or Samsung Smart Switch applications.
The technician didn't indicate what Samsung might do if the hard key re-set fails to fix the auto-rotate problem. A Samsung tech will walk users through the various steps required to perform the tests or Samsung can do the tests remotely.
The Samsung technician's course of action seems to indicate the problem is related to incompatible software, not hardware, but Samsung is not saying officially what the cause or the solution may be.
An Edge user named "IDOG" reported early Wednesday at Android Forums that he may have found the culprit. He said the rotation problem occurred when using the third-party Nova Launcher, but not when using TouchWiz, which is Samsung's own front-end touch interface. Nova Launcher, a third-party Android app by TeslaCoil Software, replaces a user's home screen with one that is customizable.
IDOG said Nova Launcher has so far worked fine after he uninstalled it and then re-installed it without borrowing any of the settings from his prior install of the launcher.
As a result of IDOG's field work, in theory, something as seemingly insignificant as user settings inside a third-party app could be part of Samsung's problem with some Edge screens not rotating properly
Click to expand...
Click to collapse
None of those seems to fit with what happened. Well, let's hope it stays functional. Thanks.
Related
My 2 1/2 year old son was playing with my Galaxy Note 10.1 tablet and seems that he change some settings on the tablet because everything (wallpaper to widgets to apps) all look like film negatives. Even Youtube videos have that effect. How do I get it back to the regular look? Do I just do a factory reset or is there other steps that I can go through without having to do the factory reset?
Thanks in advance for the help!
Go to Settings > Accessability and uncheck Negative colours.
clee290 said:
Go to Settings > Accessability and uncheck Negative colours.
Click to expand...
Click to collapse
Thank you so much. I am still trying to learn all the functions of the note 10.1. Now I can go to bed :laugh:.
No problem, glad to have helped
If you like to use it often, for any reason, there is a widget "negative colors", it's one click instead of going through settings.
Possible issues causing color inversion.
I see that this thread is almost 3 years old, but I wanted to offer some possible explanations and solutions to this issue.
There are 4 problems that can cause the colors on the Galaxy note 10.1 to become inverted or distorted. Settings, LCD flex cable, Display drivers, and the LCD itself.
First check settings (Settings>Accessibility>Negative Colors) and ensure that this is disabled (box unchecked).
If this hasn't solved the issue, then carefully open the back panel of the device, and ensure the the LCD flex cable is connected properly. YouTube has several instructional videos available.
If the issue persists, then perform a back-up and restore to factory settings. This will reinstall the display drivers.
Lastly, if all the above has not solved the issue, then replace the LCD or contact your local repair facility.
Anything beyond these would indicate a problem on the mother board.
I hopes this helps someone out there save time and money.
ICDT Technologies said:
I see that this thread is almost 3 years old, but I wanted to offer some possible explanations and solutions to this issue.
There are 4 problems that can cause the colors on the Galaxy note 10.1 to become inverted or distorted. Settings, LCD flex cable, Display drivers, and the LCD itself.
First check settings (Settings>Accessibility>Negative Colors) and ensure that this is disabled (box unchecked).
If this hasn't solved the issue, then carefully open the back panel of the device, and ensure the the LCD flex cable is connected properly. YouTube has several instructional videos available.
If the issue persists, then perform a back-up and restore to factory settings. This will reinstall the display drivers.
Lastly, if all the above has not solved the issue, then replace the LCD or contact your local repair facility.
Anything beyond these would indicate a problem on the mother board.
I hopes this helps someone out there save time and money.
Click to expand...
Click to collapse
I'd like to thank you for this post. I was having issues with the color calibration and artifacting on my note that started one day for no reason. I followed the troubleshoot order you have posted here and found out the LCD connector had worked its way loose. So I split the case and re-sat the connector and now everything works great. Thanks for saving the $100 screen replacement cost.
Most Sincerely,
A poor college student
color issue after screen off
My Note 10.1 2014 (P605) is ruining smoothly for 3.5+ years without much trouble. Now, it's screen is giving some color issue. Tab boots fine and colours shown correctly. Once screen is off, it start to invert (not sure whether the correct word) colours. Later I observed screen not switching on but accepting touch commands.
I tried color invert setting, it seems not effective. Flex cable was not loose but sometimes reconnecting resolved temporally. Re-flashed the OS but issue came up after few days. This may seems like screen fault, but screen working fine at boot till screen off.
Does anyone have similar experience or advice to help me out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
udeshjr
This is Not the forum for your Note 2014 P605 model .
I have the same problem but I don’t have the solution. The color is ok when I turn it on after the tablet power off but the second on the colors turn To light red
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above is an image of what the digitizer is registering in my Nexus 5 vs the S6. The red circles represent one specific tap on the screens. As you can see, each tap on the N5 is registered once whereas on the S6 there are several click points registered in one tap.
Is this normal?
I recently discovered when playing a game that a lot of my taps are registered as veeeery small scroll motions instead of a tap. In the game is a long list with several buttons in it. More often than not when trying to push a button nothing happens but a yanking motion (like a short scroll/swype/whatever you call the motion) in the list. It's really annoying! I haven't noticed anything similar in other apps (have not tried other games yet).
Is this normal on a new phone? For reference; a friend of mine is playing on a Note 3 and HTC One M9 and he hasn't these issues. I also found an S6 owner on the game forum with the same issue.
The app that tested the digitizer is: https://play.google.com/store/apps/details?id=com.cp.stest
dadilydoo said:
Above is an image of what the digitizer is registering in my Nexus 5 vs the S6. The red circles represent one specific tap on the screens. As you can see, each tap on the N5 is registered once whereas on the S6 there are several click points registered in one tap.
Is this normal?
I recently discovered when playing a game that a lot of my taps are registered as veeeery small scroll motions instead of a tap. In the game is a long list with several buttons in it. More often than not when trying to push a button nothing happens but a yanking motion (like a short scroll/swype/whatever you call the motion) in the list. It's really annoying! I haven't noticed anything similar in other apps (have not tried other games yet).
Is this normal on a new phone? For reference; a friend of mine is playing on a Note 3 and HTC One M9 and he hasn't these issues. I also found an S6 owner on the game forum with the same issue.
The app that tested the digitizer is: https://play.google.com/store/apps/details?id=com.cp.stest
Click to expand...
Click to collapse
Funny enough I have noticed this as well. I downloaded the app you mentioned and I am seeing similar results. I play Trails Frontier a lot and right off the bat I noticed that many times the game would not register taps as nicely as it would on my Oneplus One.
I am having this issue also. I am surprised that not so many people are talking about it. I have made a post earlier about the touchscreen being supersensitive that touches registers as swipe (http://forum.xda-developers.com/galaxy-s6/help/touchscreen-s6-sensitive-t3073953)
It is annoying not only in web browsing but also in playing games. Play Adventure Capitalist and you can notice how the touches does not register.
Does anyone know of this could be fixed in a firmware update or if it's solely hardware related?
I noticed that too
just download an app called 9gagtv from playstore and try to hit that card to start the video...
have fun trying it ...
Hmm I wouldn't have noticed this until you pointed this out. It isn't a big issue to me since it doesn't seem to affect anything I do, but I do hope it can be fixed through a software update. I would assume this is a widespread issue.
vbauer86 said:
I noticed that too
just download an app called 9gagtv from playstore and try to hit that card to start the video...
have fun trying it ...
Click to expand...
Click to collapse
I tried this app and it exactly explain this issue. I believe it is a software issue, the touchscreen sensitivity needs to be reduced.
Bumping this for visibility. Has anyone seen any improvement on this issue?
I see this too. If I tap the screen quickly and lightly I can see one pixel, but if I tap is like I was pushing a button, it creates more pixels. I can see in the 9gagtv app, trying to press a card to start a video, it slightly moves it instead of starting the video, and you really need to tap quickly to get to open.
I think it's the screen is just really sensitive more than anything. I'm sure it can be corrected with software updates.
I was wondering if you use any kind of screen protection? I noticed that mine does this as well and I thought it may be related to the screen protector, but without peeling it off and wasting my money, I can't really test this.
Mine is doing the same. Samsung Note 5 though (Verizon). No screen protector.
Hello there! I recently acquired a 3rd generation Moto G. However I've run into a few issues. My tab switcher appears to be stuck in "accessibility" mode; a weird tab switcher that uses the old holo UI. Here is a picture of the problem:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I checked chrome://flags and the accessibility tab switcher setting is not even on. Toggling on/off doesn't seem to change anything.
I also have no animations for opening the drop down menu, or opening the tab switcher. Pressing any of the UI buttons simply instantly opens the menu, as if I had battery saver on (which I don't). I've tried the dev and beta versions of chrome, and they also exhibit the same problems. Clearing cache, reverting to the factory version of chrome, etc... all don't seem to fix the issue.
I am running Android 5.1.1, with chrome 44.0.2403.133.The phone is the 1gb RAM/8gb storage version. I did some other research and found someone who had the same problem a few years ago, but on a Samsung phone:
http://forum.xda-developers.com/showthread.php?t=2490353
Please help!
I'm really surprised there are no replies to this thread. We can't be the only two people with "Merge tabs and apps" turned off.
I'd like to know if this issue is present just on the 1GB models or all 2015 models?
Running an XT1540 here with the latest 5.1.1 firmware from Bell.
skyblaster said:
I'm really surprised there are no replies to this thread. We can't be the only two people with "Merge tabs and apps" turned off.
I'd like to know if this issue is present just on the 1GB models or all 2015 models?
Running an XT1540 here with the latest 5.1.1 firmware from Bell.
Click to expand...
Click to collapse
Thank you so much for posting - I was beginning to think that I was the only one in the world with a bugged phone!
I actually purchased the phone at Best Buy in the states, but I am using it in Canada. Do you think that has anything to do with the issue?
Tijauna said:
I actually purchased the phone at Best Buy in the states, but I am using it in Canada. Do you think that has anything to do with the issue?
Click to expand...
Click to collapse
I highly doubt it has anything to do with *where* you operate the phone.
It's likely a firmware or Chrome specific setting for 1GB devices running Lollipop.
It's good to know you purchased yours in the US and have this issue. I can rule out it being specific to Bell issued firmware.
skyblaster said:
I highly doubt it has anything to do with *where* you operate the phone.
It's likely a firmware or Chrome specific setting for 1GB devices running Lollipop.
It's good to know you purchased yours in the US and have this issue. I can rule out it being specific to Bell issued firmware.
Click to expand...
Click to collapse
Yes, that's what I thought as well. The accessibility tab switcher was originally meant for low memory devices, so I'm assuming something got triggered in chrome and flagged our Moto Gs as low ram offenders.
Kinda funny, given how chrome runs just fine on more budget orientated devices like the Moto E, but gives up on the newest Moto G!
i have noticed the same problem the 1st day i have used chrome.. i just installed firefox .. as i dont use chrome which lacks in addons
I went ahead and opened a ticket with Chromium: https://code.google.com/p/chromium/issues/detail?id=525745
It would be nice to verify if 2GB users are also affected.
The issue should likely be raised with Motorola/Lenovo as there's another bug ticket that may be related:
https://code.google.com/p/chromium/issues/detail?id=519996
skyblaster said:
I went ahead and opened a ticket with Chromium: https://code.google.com/p/chromium/issues/detail?id=525745
It would be nice to verify if 2GB users are also affected.
The issue should likely be raised with Motorola/Lenovo as there's another bug ticket that may be related:
https://code.google.com/p/chromium/issues/detail?id=519996
Click to expand...
Click to collapse
I can confirm that my 2GB Moto G3 16GB is NOT affected.
hope your issue gets solved.:good:
I remember someone said something about Moto G 1GB model having a low ram parameter enabled in build.prop. Chrome may be using this to conserve memory. I have 2gb and don't have this issue.
v8s10 said:
In the build.prop, ro.config.low_ram=true If set to false chrome tab layout is normal, tried it on my 8gb/1gb ram model. Do so at you're own risk, i have no idea if editing this will cause any other problems, working fine for me so far...ymmv.
Click to expand...
Click to collapse
Alright, thanks for the heads up. Will be sure to check this when I finally get around to rooting.
Hi all, new member here, so apologies for any mistakes I make.
A friend of mine has passed on to me his Nexus 5 (2013), stating that there were a number of issues he was having with it. After using the device myself for a couple days I can confirm that the following issues are present:
- The screen will sporadically freeze and become unresponsive to any touch input, and the only way to solve this is to lock the device and unlock it again. The time between instances of this is random.
- The screen will occasionally cut to black, but the display is still active (i.e. you can only see the backlight). This happens for a number of seconds before returning to normal on it's own.
- The camera is completely unresponsive/broken (See picture 1 below). Possible loose connection?
- The WiFi is stuck on 'turning WiFi on' in the settings, and stuck at searching for networks in the notification bar(See pictures 2 & 3 below).
The device was dropped at some point in the past, but the damage is typical (See picture 4 below) and I see no immediate reason why this damage should cause these issues in particular, but I'm by no means an expert, hence why I'm here. =) The device has only been dropped one time, and has not suffered any other damage, including water damage.
My first instinct was to boot into recovery mode (where it should be noted that the freezing and display issues I mentioned above didn't occur, leading me to believe it is more of a software issue?) and clear the cache partition, which did not solve the issue, and neither did a full factory reset.
So, with all that being said, what would you guys suggest? Should I try flashing the factory image to see if that works? Rooting? Flashing a custom ROM? Any suggestions would be most appreciated!
If you require any additional information let me know and I'll happily oblige.
Thanks in advance guys!
Picture 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Picture 2
Picture 3
Picture 4
It could be the motherboard or screen. You won't know for sure until you replace one or the other.
The wifi chips do fail on the Nexus 5. I a motherboard that also tries to turn on wifi but turns itself off after a few minutes.
audit13 said:
It could be the motherboard or screen. You won't know for sure until you replace one or the other.
The wifi chips do fail on the Nexus 5. I a motherboard that also tries to turn on wifi but turns itself off after a few minutes.
Click to expand...
Click to collapse
My first thought was that it was a hardware issue to begin with, but due to the sporadic nature of the issues (excluding the camera obviously), and the fact that it didn't happen whilst in the recovery menu, I'm more inclined to believe it to be a software issue? I could be wrong of course, I'm just wondering if it's worth flashing the factory image on to see if that solves the issue?
You may as well flash the stock image and see what happens.
The lines showing on the screen does not look like a software issue to me.
audit13 said:
You may as well flash the stock image and see what happens.
The lines showing on the screen does not look like a software issue to me.
Click to expand...
Click to collapse
Those lines are what appear when I open the camera, they're not there otherwise. THAT is almost definitely a hardware issue, granted.
I have a Nexus 5 that has the wifi issue. I flashed a bunch of different Android versions (like Android 7 and 6.0) which none have worked. At one point I opened my Nexus 5 and left it like that for about a month, then afterwards I assembled it back together and the wifi worked for a little bit and then went back to its broken state. I've concluded that it is a hardware issue since data was working fine and was the only way I could get internet on my phone.
xsacter said:
I have a Nexus 5 that has the wifi issue. I flashed a bunch of different Android versions (like Android 7 and 6.0) which none have worked. At one point I opened my Nexus 5 and left it like that for about a month, then afterwards I assembled it back together and the wifi worked for a little bit and then went back to its broken state. I've concluded that it is a hardware issue since data was working fine and was the only way I could get internet on my phone.
Click to expand...
Click to collapse
Hmm. I have to be be honest after looking online it appears that wifi failure is a somewhat common issue on the Nexus 5 devices. It has to be a hardware based problem it would seem.
Thanks for letting me know, I appreciate your input. =)
I use an accessibility app from here that allows long press volume up + down to activate and deactivate flashlight. Worked fine even screen off no aod on OneUI 4.0 Feb but after updating to 4.1 it barely works and only with screen on.
So, I decided to test other stuff and yeah it completely broke accessibility.
The touch and hold delay setting does nothing, it always takes like 2-3 seconds for anything to activate even when set to very short 0.3s, no longer works screen off at all.. GG Samsung..
Lol, my one N10+ is still happily running on Pie.
Upgrades and updates can and do break things.
It's a Samsung tradition... Samsung will eventually patch it.
Try clearing the system cache as that may correct it.
blackhawk said:
Lol, my one N10+ is still happily running on Pie.
Upgrades and updates can and do break things.
It's a Samsung tradition... Samsung will eventually patch it.
Try clearing the system cache as that may correct it.
Click to expand...
Click to collapse
Clearing cache didn't help but thanks for the tip. And thanks Samsung for not allowing us to access recovery without the usb-c plugged in.
It doesn't work on aod either. Only when fully waking the device. I wonder if this is intended behavior or just a huge bug.
Can anyone else on a S21/+/Ultra with march 4.1 test accessibility shortcuts on screen off state?
Imprezzion said:
Clearing cache didn't help but thanks for the tip. And thanks Samsung for not allowing us to access recovery without the usb-c plugged in.
It doesn't work on aod either. Only when fully waking the device. I wonder if this is intended behavior or just a huge bug.
Can anyone else on a S21/+/Ultra with march 4.1 test accessibility shortcuts on screen off state?
Click to expand...
Click to collapse
Your welcome.
Try in safe mode to rule out a 3rd party app interference.
Try clearing the data in the accessibility apk.
Turn off Developer options temporarily.
Play with it, there's probably a fix or work around.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blackhawk said:
Your welcome.
Try in safe mode to rule out a 3rd party app interference.
Try clearing the data in the accessibility apk.
Turn off Developer options temporarily.
Play with it, there's probably a fix or work around.
View attachment 5569505
Click to expand...
Click to collapse
Did that, no difference. I did figure out what Samsung did actually.
They changed it so that long press volume up + down is 3 seconds and ignores the long press delay setting completely. And it also no longer works screen off while it used to work fine.
They also changed auto rotate sensitivity which makes it rotate with the slightest motion which is annoying as hell when reading something I'm bed for example as it constantly rotates..
Rolling back to Feb 4.0...
Do you have com.samsung.SMT disabled or removed?
Imprezzion said:
Did that, no difference. I did figure out what Samsung did actually.
View attachment 5569635
They changed it so that long press volume up + down is 3 seconds and ignores the long press delay setting completely. And it also no longer works screen off while it used to work fine.
They also changed auto rotate sensitivity which makes it rotate with the slightest motion which is annoying as hell when reading something I'm bed for example as it constantly rotates..
Rolling back to Feb 4.0...
Click to expand...
Click to collapse
This is one reason why I almost never upgrade or update. I don't like rude surprises.
Still running on Android 9 and 10; if it runs well I leave it be.
Funny what you say about the display flipping too easy; I get tired of waiting for it to transition.
They should have user settings for that by now.
Wonder if there's a 3rd party app to dial that in?