Related
Hello all and thanks in advance for the help.
I just got a refurb Hero from Sprint a couple weeks ago. I Rooted with Z4Root and started trying out Roms. I had just went from CM 6.2 to 6.1. Had everything working fine until my screen would stop coming out of hibernate mode. I would have to reset the phone to get the screen back on. It has gradually gotten worse (over the course of one day). Now when I reset the phone I might get the screen to turn on 1 out of 40 times, but the screen is now all messed up even when it does turn on now. I cant figure anything out other than to answer a call because I know where the slider is supposed to be on the screen for answering calls, so if someone calls I cant see anything I just swipe the screen and it answers fine.
Any ideas what might be causing this issue? Would it be a harware issue?
Thanks again
Yea I would try a different download you might have gotton a bad one. Also you should try a different rom after a full wipe. If that didn't work then I would say its a hardware issue.
Something.About.Me.U.Don’t
Like.Its.Cool.I.Understand.
.AWAH.
Thanks for the reply. I did nandroid back to every previous backup I had. Now I cant get the screen to turn on at all so, Im guessing its hardware. taking it to Sprint Today, we'll see what they say.
Thanks again
Yup, They replaced the screen and I'm back in business!
Swwet, glad to hear it man now enjoy more xda
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.
I was just wondering if there was something to do with installing different roms that could have cause the screen to go out? I am thinking not, but I am new to the whole rooting and rom-ing thing. Is it possible that something I did caused the screen to go out?
Na I doubt it. Hardware usually is the manufacturers fault or user error. Unless you droped it, banged it up real bad or flashed a gsm radio your good. And a screen issue such as yours is most def not a rom issue.The rom dev's on here are solid. And XDA is a well known and respected site. If you need any help with anything just let me know.
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.
cool thanks for the response. I was just worried that maybe I messed it up somehow. Glad that was likely not the case
Hi everyone! Unfortunately, my run with my T-Mobile G2 appears to be nearing it's end.. I've had this phone since November of last year, so fortunately for me, I'm still within the 1-yr warranty. I couldn't find a legit answer on the forum so far so hopefully someone will have the information I need to know now.
Lately, my phone has been getting crazy. Sometimes it would start pressing random things by itself. Apps would start by itself, things would type by itself, etc, etc. Then, at times certain areas of my screen wouldn't work at all, most noticeably the "y," "b," and "h" on my keyboards. And this doesn't matter whether I'm using the stock Gingerbread keyboard or Swype.
To answer any questions, yes I am rooted and I have been running CM 7.0.2. I tried to flash 7.0.3 to see if that would correct my issue but it didn't. I also tried to reset the phone via Privacy within the Android UI and via Recovery, both with no avail.
My question to y'all is how can I fix this if at all? If this problem is not fixable, can someone provide me with the MOST SIMPLE guide as to how to unroot and restore my original T-Mobile stock ROM if necessary for me to send it to claim warranty.. Finally, if I resorted to claiming warranty, does anyone know if T-Mobile will be sending me a refurb G2 or a new one or a completely different one?? Thanks ... This is EXTREMELY UNFORTUNATE.
it happens to me plenty. keep the scroll pad on the side from changing angles in direct light or it goes nuts. if theres any water on the screen at all touch commands work funny. its errors in the optical touchpad and cpacitive screen technology, not the;phone itself.
edit: im stock if youre wondering
It happens even in the dark though. I think its problem with the screen.
Any word on this? the same thing is happening to my phone.
Hui,
I was also having this problem for some time and was reallythinking of replacing the phone until I finally got rid of this last week. To start with I think this is a software issue but I'm still not sure what sw is causing this. n order to fix it I had to install the rom again from scratch and did not restore anything from google. Because independent from whatever ROM I installed the issue appeared soon after I set up the phone. So if you wnt to give it try, do a clean ROM install or factory reset to your phone and then while setting up your device uncheck the option to backup and restore settings to your google account. I know that setting up everything manually does not sound great but it's better than the crazy touch screen.
Digitizer issues
Sent from my HTC Vision using XDA App
Digitizer issues, T-Mobile just replaced my original release date G2 because of it.
They will send you a refurbished model and you have to send yours back in within 7 days or they bill you $400 I believe.
Sent from my HTC Vision using XDA App
I had serious digitizer issues last month and thought for sure that my G2 was finished. Come to find out I had gotten some oil on my phone, probably from answering a text or phone call while eating at work. I took it out of its case and completely cleaned it with a cloth dampened with peroxide...not soaked just damp, and now my phone is back to normal. Give that a try and rule that out first before you replace the digitizer or phone. Make sure you clean the inside and outside of the case/skin if you have one too.
I finally figured mine out. I guess the digitizer is really really sensitive to moisture. I usually take my phone into the bathroom with me when I shower in the morning, once I stopped doing that and gave the phone some time to dry out (in a dessicant container, but rice would work just as well) my screen is back to normal. I guess the steam from the shower was enough to bring up some bugs.
Having some random and annoying screen fluctuations. Its like the screen depolarizes and the images become distorted and somewhat inverted. Happens off and on and reboots do not help. Im gonna go back to stock just incase it needs to be sent in and to see if the ROM I am using is completely to blame, I have tried reflashing too.
Just thought I put this out there to see if anyone else is having similar issues.
I may have had something similar the other day - basically the color blue would go away, and the remaining R&G pixels would smear. Best way to describe it would be to pretend that there is a specific frame buffer for blue, and it has a pointer, and that pointer was getting whacked. Meanwhile the pointers for the red and green buffers were having less-significant bits screwed with. Yeah, like I said, "pretend". My initial gut said it was a simple case of some bad silicon on a line driver. Done.
While getting ready to exchange the Tab (aka removing stuff), I discovered the behavior was strongly impacted by memory pressure. If you've played with ESXi, you know what I'm referring to. If not, go read about Ballooning.
With lots of crap floating around, screen gets more wonky more often to the point of being unusable. Including during the boot splash screen. Remove the junk (not programs - just... stuff, music, browser cache, whatever)... less wonky, less often. Still wonky, mind you, but less wonky, and less often.
Decided the culprit was likely Task Manager by Rhythm Software. Removed exactly it, cold started, and never had an issue since. Note that I'm not really keen on saying Rhythm's work was at fault, especially since saying "it's fixed!" is trying to prove a negative and this is not a reported problem. OTOH, the behavior did start within a few days of installing it, and the behavior's ending exactly coincides with RTM's removal.
In that sense, take a close look at what you're installing - something otherwise fine might be suffering an... unexpected feature.
HTH,
- sbb
Thanks for the tip, mines still looking like hardware failure. Sometimes when i put it into the samsung keyboard dock it randomly clears up, as if the jiggle in the pin connector port affects it but it will reappear eventually.
Been trying to use the return to stock stuff from the main sticky in the development section but it keeps erroring and failing in CWM when I attempt to flash. Oh well.
Thanks for the reply yo!
I think its because the stock rom they have is p700 and I am p7510 or whatever. Am I in the wrong place? lol Time to scavenge the forums.
Unroot for Return
So, I made my backup copy of my ROM after it was rooted. How do I get this thing rooted again so I can take her in? I tried using the info on the stickie in the Dev section but I get an error when flashing the supplied stock ROM, repeated, no mistakes I am pretty sure.
Any tips?
also, hasnt been 30days, should I just go back to best buy or call samsung?
I have the exact same issue with my tablet and going to return it for warranty. I had to unroot and get it back to default blind, since the screen is almost never readable here (too much distortions).
I got it back to factory default (unrooted) through ODIN + Download Mode. Use the files and step-by-step guide on this webpage: http://droidangel.blogspot.com/2011/06/samsung-galaxy-tab-101v-p7100-stock-rom.html
I got the same problem. the screen just distorted, which happens on several custom ROM. It happens after heavy use. I have to put it aside for a couple of hours to get it back to normal.
Is that hardware issue? If it is, how could you convince the shop to get it replaced?
you may not be able to reproduce it at the shop.
I lost my interest to samsung product. It took quite some time to create an account and file a case. Now the webpage just keeps telling that it is processing the data.
I remember that I have never succeed to create an account through the TAB.
very bad service.
Well, mine's finally going in for repair.
As mentioned in the post above... after removing a few apps and most of the data from the tab... not a single issue with the screen, since.
Then... the behavior came back last week, gradually becoming worse until the colors are just plain hosed. Blew out the browser caches, wiped any remaining data... pulse, etc... and it cleared back up again... for about an hour, but rapidly reverted back to horrid. Did a hard reset... no avail.
It is quite the interesting behavior, to say the very least.
It's not mechanical. It's not thermal.
Is samsung service center the only solution for this?
Does yours look like this?
www youtube com/watch?v=WauTDdzxGq0
(Sorry, you;ll need to fill in the obvious missing doys. It was either that or posting 8 random posts)
My Tab also has similar issue and it still appears after hard reset, trying to convince the shop to exchange or help me to send back to Samsung.
Did Samsung cost you any charge for repairing? The shop say it need charges and they don't want give any help.
not really. Mine has distorted display but more likes adding white noise.
Seems that sumsung really sucks. products have so many different issues.
pholklore said:
Does yours look like this?
www youtube com/watch?v=WauTDdzxGq0
(Sorry, you;ll need to fill in the obvious missing doys. It was either that or posting 8 random posts)
Click to expand...
Click to collapse
simgamer50 said:
My Tab also has similar issue and it still appears after hard reset, trying to convince the shop to exchange or help me to send back to Samsung.
Did Samsung cost you any charge for repairing? The shop say it need charges and they don't want give any help.
Click to expand...
Click to collapse
I was covered by seller warranty. I sent it back, and the seller sent me a new device. I don't know where you're at, but usually sellers are required to handle this for you, if under warranty, _by law_. This is obviously a manufacturing fault, not bad usage.
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Maybe change the title of your thread... Your phone was bricked because you installed the Rom...
How r people getting the FFC to work with stock camera
wanabdev said:
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Click to expand...
Click to collapse
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
2. pulling the battery isnt as dangerous as everyone says it is. its only dangerous if you pull it while trying to flash the stock PD15IMG to return to stock, or during the phones booting process where its loading everything up. Ive pulled my battery plenty of times, but never in those situations.
Maybe hope
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
macblaxter said:
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
Click to expand...
Click to collapse
DING DING DING we have ourselves a winner.
[OP] are you able to get into the bootloader or recovery?
I remember when I first started rooting my phone it would be titles like this that would scare me away form certain roms. Which is a good and bad thing. Although I would generalize the title a little. Like " dam i messed up installing a sense rom" this way it's a little more inviting to open minded people that want to help and less offending to people that put in time for tutorials and development
Sent using XDA App
aznprodgy said:
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
Click to expand...
Click to collapse
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Jack_R1 said:
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Click to expand...
Click to collapse
well damn bro, didnt think it was that serious...
Hey Jack_R1 thanks for the input. I always enjoy getting a snapshot of information to clarify how things work.
wanabdev do you know if you're able to get into the boot loader to get access to fastboot? You really may be able to save your phone if you're still able to do this.
Wi-Fi Calling using Darkside Runny 2.2
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Chicago T said:
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Click to expand...
Click to collapse
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Wi-Fi Calling using Darkside Runny 2.2
glacier1122 said:
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Click to expand...
Click to collapse
Right, soooooo annoying. There's gotta be a fix out there? I like this ROM the best, it has all the little tweaks that make me happy!
Anyone have any ideas?
Flash the newest version.
http://forum.xda-developers.com/showthread.php?t=1283682
UPDATE:
It seems the problem I have is ghost typing. Based on FourPointedFreak suggestion, I activated the Show Touches option in the Developer Options menu, and now I see ghost presses on the touchscreen, always in the same place, about 1.5 inches from the bottom and 0.5 inches from the left. If I try pressing with my finger in the same spot when the mark shows up, it slides down before I can even get to the screen. If googled it, and it's been reported on some Android phones and ipads, but not on the S4, and there is no agreement if it is hardware or software.
If you've dealt with something like this before, even with a different device, your input would be most welcome. I'm planning to change ROM tomorrow or early next week, and see if the problem continues. And clean my screen with a soapy moist towel, so far I've only used a cloth for glasses to clean it.
I'm really hoping it's a software issue as I don't want to do a warranty replacement, I'd be most probably get a device on MF3. But if it is hardware I'd rather have that than a faulty device. I got it refurbished as a replacement for an Xperia Ion, and I only have one more month left of warranty.
Again, any input especially from past experiences would be greatly appreciated.
-----------------------------------------------------------------------------------------------
LAST UPDATE:
It seems the problem is hardware, as the false inputs in the screen happen also in TWRP while trying to flash the new ROM. I guess any mod can close this thread now.
josemald said:
Hi everybody, in the last week I've had issues with the display. First it started like going up and down in scroll menus, like if I was scrolling up and down around a certain position very fast. In the last two days, after that happens, the touchscreen gets unresponsive (it didn't use to happen before), including the menu and back buttons, only the hardware buttons work. Home screen button works fine, but I can't do anything in the screen. The only solution is to turn the screen off, enter PIN, and then it starts working. A couple of times the screen keyboard started acting weird when I was typing, for example if I wanted to move the cursor in an email the keyboard interpreted as if I was pressing a key, which was way below. Again turning the screen off and on solved it.
I'm using Mint Jelly ROM, which has been stable for almost two months. I recently updated the modem to MF3, but only the modem and not the firmware. The screen issues were happening before that, it just got worse today. I also tried freezing Samsung WatchOn, which started acting out by showing itself on the notification panel even though I had selected the option for it to not appear, and I uninstalled the Software Update app (used for OTA updates) using Titanium Pro, since I saw it in the list of running processes. The problem still continues.
Is it possible that this is a hardware issue? I have 1 more month of the warranty (I got it as a warranty replacement for a Sony Xperia, so it wasn't new). If I don't need to send it back I would prefer not to, since the one I'd get would probably come locked with MF3 firmware. If you have any ideas on how to debug this, I would appreciate the input. I haven't installed any new app recently.
Click to expand...
Click to collapse
Well, you're definitely smart for doing your research before just pulling the warranty card.
I would do some testing and research with the phone to figure out what the cause is. It doesn't sound like something that can be just 'debugged'.
Go into your developer options on the phone and enable a few things.
To get developer options, go to System Settings > More > About Device and tap on "Build Number" until it says you've enabled it.
Then go into Developer Options (Above About Device) and under input, select both options "Show Touches" and "Show Pointer Location". Then under Monitoring, enable "Enable Traces" for anything applicable to what you're having problems with.
Some of these settings may be annoying, but continue to use the phone as you would. See if it's adding and doing things you're not, this would show clear signs of a malfunction with the firmware. Check for dead pixels too. Sometimes a dead pixel can cause things like you're dealing with. Where something is selected on the screen much lower than where you pressed and variations of that.
Also, have you tried reflashing your ROM to see if that makes a difference?
FourPointedFreak said:
Well, you're definitely smart for doing your research before just pulling the warranty card.
I would do some testing and research with the phone to figure out what the cause is. It doesn't sound like something that can be just 'debugged'.
Go into your developer options on the phone and enable a few things.
To get developer options, go to System Settings > More > About Device and tap on "Build Number" until it says you've enabled it.
Then go into Developer Options (Above About Device) and under input, select both options "Show Touches" and "Show Pointer Location". Then under Monitoring, enable "Enable Traces" for anything applicable to what you're having problems with.
Some of these settings may be annoying, but continue to use the phone as you would. See if it's adding and doing things you're not, this would show clear signs of a malfunction with the firmware. Check for dead pixels too. Sometimes a dead pixel can cause things like you're dealing with. Where something is selected on the screen much lower than where you pressed and variations of that.
Also, have you tried reflashing your ROM to see if that makes a difference?
Click to expand...
Click to collapse
Thanks for the suggestions!
Do you think it´s possible that the problem was caused by a dirty screen? I know it sounds a bit insane, but yesterday I wiped off my screen to clear dust and smudges, and since that I haven´t had any issues with the phone. This is the third touch screen device I had, I've never seen something like this, but also the S4 screen is a lot more sensitive than my previous devices. Could it be that too much dust and grease made the phone interpret that there was some input?
josemald said:
Thanks for the suggestions!
Do you think it´s possible that the problem was caused by a dirty screen? I know it sounds a bit insane, but yesterday I wiped off my screen to clear dust and smudges, and since that I haven´t had any issues with the phone. This is the third touch screen device I had, I've never seen something like this, but also the S4 screen is a lot more sensitive than my previous devices. Could it be that too much dust and grease made the phone interpret that there was some input?
Click to expand...
Click to collapse
I would think it's 'possible' but it would have to be thick and really caked on there to make a difference. That may have just been a coincidence of timing with your issue. But perhaps it is.
Maybe go buy a cheap screen protector to help with finger prints and dirt and see if it gets better?
If it persists, I would factory wipe and install the stock ROM through Odin. Use it a bit completely stock and see if the screen works. If the issue continues then its an hardware problem and i would take a video and e-mail Samsung about it with the video. I've actually had this problem before and that's because my phone was cold as hell. Doing a lot of benchmarks so i put it in the freezer (I would NOT recommend that) and my screen started acting up and it pressed random things like yours.
crzykiller said:
If it persists, I would factory wipe and install the stock ROM through Odin. Use it a bit completely stock and see if the screen works. If the issue continues then its an hardware problem and i would take a video and e-mail Samsung about it with the video. I've actually had this problem before and that's because my phone was cold as hell. Doing a lot of benchmarks so i put it in the freezer (I would NOT recommend that) and my screen started acting up and it pressed random things like yours.
Click to expand...
Click to collapse
That's a good idea. Just make sure you flash the custom ROM appropriately as not to brick your device.
Sent from my AT&T SAMSUNG-SGH-I337 via XDA Premium Mobile App
FourPointedFreak said:
That's a good idea. Just make sure you flash the custom ROM appropriately as not to brick your device.
Sent from my AT&T SAMSUNG-SGH-I337 via XDA Premium Mobile App
Click to expand...
Click to collapse
It seems the problem I have is ghost typing. Based on FourPointedFreak suggestion, I activated the Show Touches option in the Developer Options menu, and now I see ghost presses on the touchscreen, always in the same place, about 1.5 inches from the bottom and 0.5 inches from the left. If I try pressing with my finger in the same spot when the mark shows up, it slides down before I can even get to the screen. If googled it, and it's been reported on some Android phones and ipads, but not on the S4, and there is no agreement if it is hardware or software.
If you've dealt with something like this before, even with a different device, your input would be most welcome. I'm planning to change ROM tomorrow or early next week, and see if the problem continues. And clean my screen with a soapy moist towel, so far I've only used a cloth for glasses to clean it.
I'm really hoping it's a software issue as I don't want to do a warranty replacement, I'd be most probably get a device on MF3. But if it is hardware I'd rather have that than a faulty device. I got it refurbished as a replacement for an Xperia Ion, and I only have one more month left of warranty.
Again, any input especially from past experiences would be greatly appreciated.
josemald said:
It seems the problem I have is ghost typing. Based on FourPointedFreak suggestion, I activated the Show Touches option in the Developer Options menu, and now I see ghost presses on the touchscreen, always in the same place, about 1.5 inches from the bottom and 0.5 inches from the left. If I try pressing with my finger in the same spot when the mark shows up, it slides down before I can even get to the screen. If googled it, and it's been reported on some Android phones and ipads, but not on the S4, and there is no agreement if it is hardware or software.
If you've dealt with something like this before, even with a different device, your input would be most welcome. I'm planning to change ROM tomorrow or early next week, and see if the problem continues. And clean my screen with a soapy moist towel, so far I've only used a cloth for glasses to clean it.
I'm really hoping it's a software issue as I don't want to do a warranty replacement, I'd be most probably get a device on MF3. But if it is hardware I'd rather have that than a faulty device. I got it refurbished as a replacement for an Xperia Ion, and I only have one more month left of warranty.
Again, any input especially from past experiences would be greatly appreciated.
Click to expand...
Click to collapse
Yeah, I have heard the term "ghost typing" before. I couldn't seem to find much information or help on the subject as I'm sure you noticed as well. To me, and many others on the internet - this doesn't seem software related to me. This would seemingly be an issue with the hardware. Maybe the screen itself, the data connectors for the screen's signals - could be all kinds of things.
If I were in your shoes and you really like the S4, i'd just take advantage of the month you have left on your warranty and get a new device. If, and they probably will, they supply you with a new(er) device with MF3 on it, it's not the end of the world. Mine got stuck with it - there are methods to root it even still.
To me, cleaning it just doesn't sound like it's a solution. I've worked for T-Mobile, AT&T and Verizon. Only twice had I seen an issue like this where you can attempt to press "E" and another key was hit in place of "E". We never found a fix - this occurred on demo phones so we related the issue to it having demo software.
The only other 'solution' or fix would be to replace to screen to see if it fixes. But since you have a warranty, for the trouble - i'd just get a new device.
FourPointedFreak said:
Yeah, I have heard the term "ghost typing" before. I couldn't seem to find much information or help on the subject as I'm sure you noticed as well. To me, and many others on the internet - this doesn't seem software related to me. This would seemingly be an issue with the hardware. Maybe the screen itself, the data connectors for the screen's signals - could be all kinds of things.
If I were in your shoes and you really like the S4, i'd just take advantage of the month you have left on your warranty and get a new device. If, and they probably will, they supply you with a new(er) device with MF3 on it, it's not the end of the world. Mine got stuck with it - there are methods to root it even still.
To me, cleaning it just doesn't sound like it's a solution. I've worked for T-Mobile, AT&T and Verizon. Only twice had I seen an issue like this where you can attempt to press "E" and another key was hit in place of "E". We never found a fix - this occurred on demo phones so we related the issue to it having demo software.
The only other 'solution' or fix would be to replace to screen to see if it fixes. But since you have a warranty, for the trouble - i'd just get a new device.
Click to expand...
Click to collapse
Thanks, that's what I'm going to do. It must be hardware related, since the problem also came while I was in TWRP after formatting the phone. I like the S4 but a locked down Android, not so much. If rooting is enough to be able to tether, I might ask for another S4, if not, might as well try to migrate to Windows Phone. It's ridiculous that we have to pay extra just to be able to use our limited data plans to navigate through a different device.
Again, thanks for your help!
josemald said:
Thanks, that's what I'm going to do. It must be hardware related, since the problem also came while I was in TWRP after formatting the phone. I like the S4 but a locked down Android, not so much. If rooting is enough to be able to tether, I might ask for another S4, if not, might as well try to migrate to Windows Phone. It's ridiculous that we have to pay extra just to be able to use our limited data plans to navigate through a different device.
Again, thanks for your help!
Click to expand...
Click to collapse
No problem - yeah there is definitely a way to root the MF3 build of the S4.
Since you mentioned it, my only note ***If apps are important to you, Windows Phone is a dangerous field. Many apps available for Android and iOS are not available on Windows Phone. I'd make sure the content you want is available before switching.
I can see why the carriers would charge additionally for tethering. If you can make an extra buck, do it. But it does suck. Especially when you have unlimited data and want to tether.
-Do some research on Windows Phone in case you're seriously considering switching. I wouldn't though