My touch screen just started acting up. When scrolling thru lists it stutters and when I select something I end up selecting something I didn't select (make sense?) When typing I'll hit a key on the left side of the screen and a key on the right side will be selected. I did a factory/data reset, wiped cache and cleared dalvik cache to no avail. It appears that the calibration is now off. I'm rooted and running Infused153. I hope my phone ain't broke Your help is greatly appreciated.
I just did a battery pull and everything appears to be working as it should. Probably shoulda tried that before I posted.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Related
I recently bought a used stock G2x and when I turn the unit on, it takes forever to boot up. When it does boot into the stock OS 2.3.3, some of the apps work fine and some of them i.e. Camera, Phone I will get FC's. I also have no sound for some reason, the only sound is the vibrate feedback when you are using the soft keys.
I have tried a factory an hard reset and nothing, tried flashing CW recovery using NV Flash and installed CM7 7.1.0 stable and it's still acting weird with no sound. It looks like new and shows no sign of any abuse. It's almost like the factory firmware is corrupt or something along those lines.
It's almost 10 minutes to boot sometimes and is in a slow motion mode for some reason, I have had several of these and have never seen this happen so I am stumped.
Any help would be appreciated, I want to root this puppy and use it as my daily driver.
Have u wiped ur data, format ur system before flashing new rom?
Sent from my LG-P999 using xda premium
Waldano said:
Have u wiped ur data, format ur system before flashing new rom?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yes, I have wiped, formatted system, flashed the ROM and still NO SOUND and the thing is acting weird.
When i push the power button to shut off the screen, when I try to turn it back on, it is a black screen, i can see the backlight react when I push the power button and sometimes the screen recovers after a long period of time.
When I try and make a call, the screen is black with no call buttons but the status bar is at the top of the screen, same thing when I try and use the camera.
When I flash it back to the stock ROM, there is still no sound and some of the apps do not work, same thing as I described above.
When I try and receive a call, there is NO SOUND and the screen is black, it never turns on like normal on an incoming call.
This is the weirdest thing I have ever seen, it's almost like the hardware is not reacting to the software commands. Help!!!!!
You checked settings/sound just to make sure it wasn't on silent right lol
Sent from my LG-P999 using xda premium
Currently on Liquid rom with Bubba kernel:
My middle button is mapped as short press home, long press menu. However, I noticed that sometimes after not using my phone for a while, it changes to short press menu. The home function just disappears, regardless of long press or short press. A reboot gets it back to normal, but I'm just curious as to why this happens.
Thanks ahead of time for any feedback!
just wipe cache reflash rom and clear settings data it should fix the problem!
Been a while now and I'm currently on Rootbox (after full wiping etc). The problem still comes back from time to time. It seems that no matter how short/long you press back, home, or recent apps button, it will always be interpreted as a long press. This happens with volume rocker as well sometimes: even if I just tap it quickly, the sound will change by a lot of steps. Anyone else have this problem?
It popped up a couple of times, im on Liquid Smooth. Normally a restart solves the problem. You cleared the cache as well?
Sent from my One S using xda app-developers app
Yeah rebooting helped. Was wondering if there's someway to prevent it permanently though...
Sent from my HTC One S using xda app-developers app
Hi All,
I've recently updated my Desire S to CM10.1 using a ROM off here --> [ROM][XXYYYZZ][UNOFFICIAL] CyanogenMod 10.1.
Everything has been running fine until I found the "Simulate Secondary Displays" button under Developer Options and decided it would be cool to see what it does...
The kicker:
a) Screen is now stuck exactly where it was on the Developer Options prior to selecting a screen resolution
b) Holding down power button for any period of time does nothing
c) Holding down Volume up + Volume down + Power for any period of time does nothing
d) The computer recognizes the phone as it makes it's lovely "new device found" sound, but stupidly, at some point I've disabled USB debugging so can't use adb to reboot as it returns authorisation error (The authorisation option doesn't pop-up on device screen as it's frozen).
I've read about this exact problem happening on other phones after selecting this option but they all seem to be able to use either b) or c) to get back to bootloader to reflash the ROM.
So, my question: if I let the battery die, what are my chances? I've read myself out of pulling the battery due to eMMC issues. Unfortunately the damn battery was mostly full so could take a long while to drain :S
Thanks!
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Pulling the battery out doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
SimonTS said:
Pulling the battery ut doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
Click to expand...
Click to collapse
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Click to expand...
Click to collapse
Apologies, it wasn't a particularly open question. It was more out of frustration that there is an option available that will always freeze the phone when it isn't supported on the device.
I let it die then used recovery to clear cache and davlik cache and booted fine until freezing on the "Optimising apps" screen. Let it die again, clear all data, clear cache, clear davlik cache, restore nand successfully.... Boots to HTC then black screen, no response to anything, same as when it first froze.
EDIT:
Repeat same process but clear cache and davlik cache after nand restore... black screen, no response. Cant even tell if it is actually doing anything. Charge light doesnt come on when plugged into pc whilst on black screen.
All I can think of now is flash the CM10.1 ROM again or maybe restoring the original nand from before CM10 but will have to be after work. Is this behavior indicative of a larger (potentially physical) problem?!
PoZER937 said:
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
Click to expand...
Click to collapse
From what I remember - there was some in-depth discussion on one of our threads about 18 months ago - the actual cause is that re-inserting the battery while the circuitry is discharging causes a spike which can be high enough to blow the eMMC.
Just to let you know, reflashed CM10.1 ROM and all is well in the world again Thanks guys for replying!
However, NAND restore did not work. As the NAND backup is supposed to be the be-all and end-all for phone recovery, should I be concerned this failed?
Seemingly out of the blue earlier today, both my home button and recent apps button stopped working properly. The home button works when the phone is locked to wake, and fingerprint sensor unlocks, but when the screen is on it is useless. The recent apps button lights up and vibrates when touched, but does nothing. Anyone else experience this problem?
Sent from my SM-G920V using XDA Free mobile app
Try going to recovery mode and wipe cache.
roydok said:
Try going to recovery mode and wipe cache.
Click to expand...
Click to collapse
Yes,or Do a factory restore.
stush0104 said:
Seemingly out of the blue earlier today, both my home button and recent apps button stopped working properly. The home button works when the phone is locked to wake, and fingerprint sensor unlocks, but when the screen is on it is useless. The recent apps button lights up and vibrates when touched, but does nothing. Anyone else experience this problem?
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
A recently installed App must be causing this. Wipe the cache and if it doesn't help try in Safe mode.
Going to safe mode:
1. Power off the phone.
2. Hold the volume down button and then press the power button till the homescreen boots up.
If the issue doesn't happen in safe mode, try uninstalling the recent apps you have installed to save yourself from doing a factory reset.
Cheers:good:
ultraquantum said:
A recently installed App must be causing this. Wipe the cache and if it doesn't help try in Safe mode.
Going to safe mode:
1. Power off the phone.
2. Hold the volume down button and then press the power button till the homescreen boots up.
If the issue doesn't happen in safe mode, try uninstalling the recent apps you have installed to save yourself from doing a factory reset.
Cheers:good:
Click to expand...
Click to collapse
Wiping the cache and safe mode didn't do it. I also went through the play store recently added/updated apps and removed them. That did not do anything either. So I ended up going through with a factory reset and that did the trick. The problem occurred around the time I installed a pair of apps from the Galaxy Apps store. I installed the Car Mode and the Soundboard apps. I went in an uninstalled them, but there may have been something extra installed with the Car Mode app that was still causing issues. In any event, thanks for the suggestions and to anyone in the future, just stay away from the Galaxy App store. We all know there really isn't anything worthwhile in there anyway.
Thanks for the help and suggestions.
I have the exact same problem right now! The home and revents button are useless. I installed car mode and deleted it because it didn't want to start on my galaxy sy edge+...
Just encountered the same problem with my S7, factory reset fixed it. For anyone else that encounters this problem and finds their way here: it was Car Mode that caused this problem, DO NOT INSTALL IT. Thank you for creating this thread.
Hi,
I also posted this in the Moto G forum, possible by mistake. If the Mods. could decide which location is better, and delete the unnecessary post, it would be great....
Wondering if anyone can help.
I have a Moto G3 8Gb model. Everything is stock. Not rooted, unlocked. The phone is 4 Months old.
The problem I am having is the battery symbol always displays the "Lightening Flash" for charging, even when the phone is not plugged into the charger. I have tried clearing the cache, but that didn't work. I am not sure if this "bug" is only an indication issue, or if the phone will actually think it is in charging mode and that will have knock-on effects to the phone itself. I am tempted to do a Factory Reset to see if that cures the problem, but maybe someone has a fix......
Thanks for your help.
Does it also show 'charging' in the settings>battery page? Or only statusbar?
Edit:- Sorry no idea.
Broadcasted from Zeta Reticuli
No, on Settings>Battery it shows XX% - approx. YY hrs left.
First, do a hard reboot... With the phone operating, press and hold power for 10+ seconds until it reboots. Test
Second, boot in safe mode and see if it persists. Hold the power button a different when prompted to Shutdown, long press the button and select Reboot to Safe Mode. If the trouble is gone after reboot, it's an app you have installed that causing the issue
Third, clear cache... https://motorola-global-portal.cust...ail/a_id/105527/p/30,6720,9390/kw/clear cache
Lastly, do a full factory reset to wipe all information (delete Google account first).
If it still persists it's a hardware issue and there is nothing you can do but send it in for repair.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
First, do a hard reboot... With the phone operating, press and hold power for 10+ seconds until it reboots. Test
Second, boot in safe mode and see if it persists. Hold the power button a different when prompted to Shutdown, long press the button and select Reboot to Safe Mode. If the trouble is gone after reboot, it's an app you have installed that causing the issue
Third, clear cache... https://motorola-global-portal.cust...ail/a_id/105527/p/30,6720,9390/kw/clear cache
Lastly, do a full factory reset to wipe all information (delete Google account first).
If it still persists it's a hardware issue and there is nothing you can do but send it in for repair.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Did hard reboot, and factory restore. Problem still there. Contacted my mobile operator. They are sending phone for repair (phone still under warranty). Hopefully that's the end of the saga. Mind you, it seems very easy to replace the charging port. There is an access panel at the bottom of the phone - 3 screws, and out pops the charging port. Anyone any experience replacing the port?