After upgrading to the latest update, my DPI is affected on both screen. They are almost identical when folded and unfolded. I can't reset it. I've tried turning it off and on, reset all settings, factory reset, as well as Odin. I cannot seem to figure this out. I've Google this and no luck. Has anyone experienced this??
Related
I recently (yesterday) updated my one X to jellybean (official OTA ROM update) and since then it's suffering from phantom touches.
I tried everything I could think off, even a hard reset (btw, that also deletes your storage data, very nice to discover this afterwards) but even that didn't help.
It doesn't happen all the time but when it does it's seriously annoying.. it start apps, calls people, just anything that's on the touched place.
I turned on the development option for visual touch feedback and it actually shows the phantom touches.
I've been googling for similar cases but nothing useful except some broken digitizers.
If it were the digitizer it would have happened before the upgrade too, right? but it didn't, it started right after I upgraded.
It's not an app, I booted my phone in safe mode and it happened, it even happened during the first boot setup.
Any suggestions? Is there anything else to clear that's not cleared after a hard reset?
My screen will not rotate. I have reset my phone and have made sure that the box is checked for auto rotation. Also when I try to calibrate the sensors it will not allow me. I have searched but haven't seen anything yet unless I missed something. Please help.
rebal1oo said:
My screen will not rotate. I have reset my phone and have made sure that the box is checked for auto rotation. Also when I try to calibrate the sensors it will not allow me. I have searched but haven't seen anything yet unless I missed something. Please help.
Click to expand...
Click to collapse
I did a hard reset and it is fixed now. I was resetting my phone from the menu before. I also set up as a new phone this time and then reset from a backup.
rebal1oo said:
I did a hard reset and it is fixed now. I was resetting my phone from the menu before. I also set up as a new phone this time and then reset from a backup.
Click to expand...
Click to collapse
This happens a lot? Or just once? Does it still rotate?
It only happened once. The night before I wached YouTube and it worked fine. The next dayit quit working. After a hard reset it works fine now.
I also have some issued related with screen rotation...
Sometimes, not in all apps, when I rotate the phone from portrait to landscape, I get for a while only half of the display. Sometimes take almost a minute to go to the normal resolution (or complete display).
The image get kind of shrinked only on the left side of the display, if I turn back to portrait I have (of course) only the superior half.
Anyone with the same issue? Any solution?
Thank you
Hey so my speaker phone is always on whenever I make or receive a call. I've gone through every single setting, made sure no apps are installed making it default to be on (voice recorders, GPS apps, ect) yet it is always on?
Anyone know how to fix this? Is there some app that I can install that can force it stay off unless I turn it on?
Some people say its the phone thinking its in dock mode. Is there any way to disable that?
This is driving me nuts. I've tried pulling the battery, rebooting and nothing is working.
Thanks for the help!
Is there some app that I can install that can force it stay off unless I turn it on?
Click to expand...
Click to collapse
You shouldn't need an app to do what the phone already natively "normally" does. More than likely, some app you installed is causing your problem. Even if you disable apps to not have speaker on by default, perhaps the app cache settings are still affecting your phone.
If you're still agonizing over this problem by the time you read this... I would clear all the app cache, clear data on each installed app, disable all installed apps (force stop), and if that doesn't work, back up your data and factory reset. More than likely a factory reset will get your phone working correctly again. A pain, I know, but... better than going nuts! Good luck!
Yeah I've gone through every conceivable app that would have anything to do with my speakerphone and it hasn't helped. I'm afraid to do a factory reset because I honestly don't think it is going to fix it. I'm starting to think more and more that it is a hardware issue with the USB port and not a software issue. I may have to go to a Verizon store and see what they say. I'm sure once the guy can't figure it out he will tell me that I have to factory reset it at which point I want to make say if it doesn't fix it, I'll need a new phone.
So annoyed it's not even funny.....
UPDATE:
Ok so I still can't figure out what it is, I've cleared all data and cache on all apps (including the phone app) but nothing seems to help.
For ****s and grins I wanted to see if I plugged in my headphones what it would do. When I plugged them in and tried to make a call, this time the speakerphone button is NOT illuminated BUT.........IT STILL PLAYS THROUGH THE SPEAKER PHONE AND NOT THE HEADPHONES????
I know, mind...blown.
Now if I push the speakerphone button, it turns green (on) and the sound still comes through the speaker phone but if I push it again, it turns off and now the sound plays through the headsets.
What on earth is possibly going on??? Can the phone dialer app be corrupted? What else can I try other than a hard reset? Is there a way I can reinstall the phone dialer app?
I know you stated you looked at all the apps you could, but did you look into the S Voice settings to see if Auto start Speakerphone is enabled? Supposedly it'll be used only when S Voice is used, but who knows when something might be corrupted.
Already tried that, didn't fix it. Even tried disabling Svoice.
I also booted up in safe mode and it still was doing it so I know it isn't any installed app that I have that is doing it.
At this point I think have no choice but to do a hard reset unfortunately. SO incredibly annoying.
Well, I hope you solve the problem. At least with the hard reset you'll get a clean start. Nah... nothing good about a hard reset! Damn annoying! Let us know how you solved it once you get it going.
My fiance and I both updated, my phone seems no different. The screen on hers is constantly turning on and off with no messages or notifications and no outside user input. Any thoughts? No factory reset performed.
Bumping. The issue seems to present when the phone is moved.
Performing a factory reset is my suggestion. It should fix the issue.
My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.
Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.