My touch screen seems to have issues, it just registers taps even though I never touched it, this just started randomly, it makes that tab almost completely unusable. When I do get in, it registers second or third taps even though I only tapped it in one place. I've already tried restoring to an old nandroid backup, flashing latest Rom and kernel, flashing another rom and kernel,slamming the tab on my table, etc. Is this a hardware or software problem? If software, how do I fix it?
If you say you tried different rom versions than it's most likely a hardware issue. If your tab is still under warranty RMA it.
Just to be sure you weren't doing something wrong, restock your tab following the overcome guide.
Related
I've been in this rooting game since it began, and I never had a major issue.
Unfortunately now I have come across one, and I believe it may be a Hardware problem, but I'm not entirely sure.
At any rate, the other day I'm on the computer the phone is charging through the usb cable, and while im using it, the back light goes out. I think this is weird.
I lock, and unlock it and everything is back to normal, but when I slid the screen back the back light went out again.
And the home button didn't work either, I doubt this was a problem with Cyan's ROM, or a theme. I do have the new lockscreen but I never had an issue.
So from Cyan's 4.0.4 I upgrade to the experimental version and the problem persists, the back light won't turn on unless the screen is slid up/open (Also, I have no lock screen!? wtf?).
Afterwards I decide to go back to 4.0.4 and even when my phone boots up the back light wont turn on unless the phone is open/screen is slid up. So obviously it seems like a hardware issue.
Anyone else have this problem? or any thoughts about it?
I'm on Cyan's 4.0.4 - no theme
26I Radio and H's SPL.
reset your phone. hit call,menu and power at the same time. then let us know how everything works.
Funny things happen when you don't wipe, make a nandroid backup of your current setup and than wipe and flash again and see if it persits
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
igloo77055 said:
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
Click to expand...
Click to collapse
This is a hardware problem. Happened to me too. Been trying to find a solution, but the fact that it still has the same backlight problems when the phone is booting (On the T-mobile G1 screen) shows that's it's way beyond the ROM.
Mine even has the same problems on the recovery screen. Time to find a new G1. If you find a solution, lemmie know. I've been looking for one.
Good evening everyone!
Little did I know, my father had his OG Droid just sitting in a drawer when he upgraded to the Inc2. I had him ship it out to me this past day so I can use it as my play thing!
Upon first boot up, before root or anything at all, I noticed the left side of the screen wasn't responding. Say, the back button and all the way up. Everything beyond the back button seemed ok.
I felt that maybe it was just a quirk with how old and how much he had used his phone, and was hoping for a software fix (read - flashing) and not a broken screen or any hardware problem.
As I began wiping data and resetting everything that could / should be, it started to get worse. Random "touches" on the screen, menu keys moving, total unresponsiveness. Just general whacked out problems that make you want to throw any device across the room.
I did manage to get Clockwork on, flash into recovery and install (successfully!) a plain 2.3.5 ROM I like. It was annoying with all the menus and key presses going all over the place, but they weren't happening while in recovery, so I was hopeful.
Upon the successful bootup of 2.3.5 though, the screen was even worse - more bouncing around, less responsive, etc etc.
So, my long winded question: anyone have any idea if this could be any problem but some sort of screen mishap or other hardware problem? I kind of hope it's not, just so I can have a device to constantly play with.
Thanks in advance!
broken digitizer, a common issues with droids/milestones.
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues
At a certain point on my screen, the phone thinks I am touching it.
I dont know how else to explain it but a 'phantom touch'.
Its repetitive and very annoying.
It seemed to start after I flashed some custom ROMS.
I flashed back to stock (2.3.5) in the hopes of it being fixed but it seemed to follow me.
Has anyone had this issue/knows how to fix it?
Thanks
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
dr. xp55 said:
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
Click to expand...
Click to collapse
It seems to have just gone away on its own. Cheers for the help anyway, would have done this if I still had the problem.
It seems to come back when I flash a ROM.
I flashed the German ICS official ROM (which is great btw), and it seems to have come back.
Hopefully, someone can provide me with a solution, perhaps its a corrupt system file?
Still, it goes away when the phone is charging.
Any ideas at all?
I'm not sure if this is helpful, but I faced the same issue when I flashed ParanoidAndroid yesterday. In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive). It was then that these phantom touches started. I set it to 100(max, least sensitive) and I couldn't get the touchscreen to register any touches at all. The Spen worked in both cases, so I just used that to reset it.
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Hi, I think this seems to be the trick.
I was unable to find the code to access the settings menu you described.
However, I installed TouchScreenTune, and that seems to be working for the moment.
Will post my results in a few hours or so.
Thanks
bloodyhippo said:
In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive)....
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Click to expand...
Click to collapse
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
novastorm17 said:
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
Click to expand...
Click to collapse
You're right, I couldn't find one that'd help either. Hmm.
Do you still have the problem?
It hasn't gone away, but I think the frequency at which it occurs has reduced
Any other ideas/any other way to do your previous method?
Cheers
Okay so here is all the information I have.
No matter which ROM I flash, the issue of the random touching continues.
Ive tried without root, and tried a complete reinstall (by formatting all data and storage)
I found a CWM restore I made 6 months ago (long before the issue started). That didnt work either.
Things that DO work:
TouchScreenTune seems to greatly reduce the frequency at which at occurs by decreasing the sensitivity of the screen, however, it makes it harder to use the phone.
Plugging in USB stops it completely, but when its removed, the issue comes back.
I thought since it is following me through different ROMs it is a hardware issue.
Does ANYONE know a fix/heard of this before?
At the moment Ive resorted to using my old IDEOS (oh god) and have begun working towards a warranty rectification.
Thanks anyone who can help
Update from Samsung:
Issue due to motherboard/touchscreen
Cheers for your help
I recently hard bricked my LG G4 and I was given this phone by someone I know. The phone had a cracked lcd which has since been fixed.
I reformatted to phone back to stock firmware, DOK2. And. I followed the instructions in how to root and install twrp to then ultimately install a custom ROM. Got all that and I have a custom ROM and I am rooted. But the phone lags like crazy. I am trying to type now and I am tapping faster than the keyboard actually acknowledges. Also, if I try to watch Netflix or even an embedded video from the browser, the video "hiccups" every 8 seconds or so.
What I have done.
I wiped the entire phone, including internal SD and external. I did this twice and I Odin stock twice. After I tried the custom rom and experienced the lag. I started from square one again. BTW, the lag happens on stock ROM, too. I have tried Ovrdrv and tek hybrid on both I have SU 2.52 installed and I tried beast and emotion kernels. The lag is real. Maybe this phone is designed to work in this manner when compared to my G4,rip.
On a side note, this phone was given to me in not the best shape. I mentioned I changed the LCD, but the phone's back button and fingerprint scanner don't work. It is also missing the stylus, but that's not a big deal for me. The charging port works fine and so does the recent button and both the back and recent light up. At this point I am thinking it's a hardware issue and it's conflicting with the software somehow. I downloaded different keyboards but they all do the same. I can type maybe 5 short words before it freezes for about a second.
Videos playing directly from device also lag like streaming services, but mp3 and music do not lag.
I can't help with the Note, but did you brick the G4, or did it die because of the known hardware issue? Those phones are dropping like flies. I had one that recently fell into a boot loop out of nowhere. AT&T replaced it, no questions asked. LG has acknowledged a hardware issue. Bad connections on the mobo, I think. I sold the new one to buy the Note. Didn't really like the G4 anyway!
How long did you allow to settle before you wrote this post? The phone needs a couple days to settle before it runs optimally. Did you install any apps or mods such as xposed?