Related
I recently had a problem with my 1st Touch Pro with image ghosting/ burn in and ive just had it replaced. Now the same problem is happening with the new device. The problem only seams to happen with custom roms being used on the device. If i re-flash my phone back to the default/stock rom i get no screen problems at all.
Any idea why this only happens on custom roms and not the default/stock rom??
edit: ive attached an example of what i mean in image ghosting/burn in. Just in case some people wasn't sure what i meant by it.
More info?
Heya! What was the last ROM you had this problem with? Version info would be extremely helpful as I have heard that specific builds have some graphics bugs.
I've had that same issue as well on 2 different fuze's. Using various builds of EnergyROMs... However, after reflashing to stock and using it awhile, I'd get the ghosting on that too.
Anyone have any ideas?
Ehh my 2nd Fuze is doing this so I'm getting a replacement, and I'll just do the HTC ROM upgrade and keep WM6.1. I'm tired of it, and the landscape view also distorts the start menu icons 90% of the time.
Having flashed back to a stock rom, doing a hard reset... Playing with it for awhile... The ghosting is evident on it as well... I've also had where the bottom section of the screen will flicker quickly...
Anyone else?
I think it's a hardware defect. My first phone did that, and then after a few weeks, I had to get a warranty replacement because the screen eventually went completely black after doing it intermittently).
I've had both ghosting effects & occasional rapid flickering since I first bought the Fuze back in November. It's intermittent but happens most when the device is hot (either from use or simply being in a hot location). So far it always clears up after a while. This happened on the stock rom and every custom rom I've used so far.
I'm fairly certain it's a hardware issue with the Fuze/TP because the ghost will tend to remain there for a while even after a soft reset.
Hopefully my good fortune continues and it doesn't end up breaking permanently some day.
it is definitely a hardware issue.
I just received a "repaired" phone back from HTC today only to turn it on and find the same problem. I had to call again today and complain...and the only thing they could do for me was ask me to send it in again....so pissed.
I literally got 5x FUZE replacements and each had this until this last one I've gotten...!
Vid: http://www.youtube.com/watch?v=fFb4bQomqPw
Thx
JFlitt
JFlitt said:
I literally got 5x FUZE replacements and each had this until this last one I've gotten...!
Vid: http://www.youtube.com/watch?v=fFb4bQomqPw
Thx
JFlitt
Click to expand...
Click to collapse
were they replaced through HTC or ATT?
I am on my third Fuze.
First day when I upgraded to Fuze the screen started doing this. So I took it back to AT&T for replacement. On the drive back home screen on second device started doing exact same thing. Took it back and got yet another replacement. This one works, but I have seen it happen once or twice in the 3 or 4 months I've had it.
AT&T also told me when I got this phone that it was the last exchange I could make for the 90-day exchange. If I had another problem I'd have to send this back to the company. WTF is that all about? You're going to inconvenience me because you keep giving me bad eggs? At least this one works right.
Is anyone with a Touch Pro having the same issues? Or is it all just us AT&T customers?
I have an O2 Xda Touch Pro. The only symptom I have that remotely resembles the ones listed here is the flickering at the bottom. But, in my case at least, the flickering is caused by a particular shade of gray displayed in Opera...and that's the only time it happens. So, again for me, it seems to be a software issue.
Drew
Flickering is another side affect that mine occasionally has... just in the bottom 1/5th or so of the screen... Most easily seen when in landscape mode in messaging.
those are all hardware issues too, its just only being displayed because that certain shade of grey is whats making it visibly noticeable.
Well, we'll see if replacement number 4 has the same issues soon...
They actually offered me a BlackBerry Bold/9000 as a replacement phone like it is even in the same universe.
Hardware differences?
Anyone with a buggy Fuze want to post the part number / sku number etc...? Maybe we are looking at a bad batch or a bad but unannounced hardware version?
I had this too on energyrom, I allways passed it off as a touch flow 3d opengl issue which would draw to the screen.
But thinking about it, it does occour when the device is hot, and the screen flickers also.
But It allways goes away after a soft reset for me.
Vodaphone UK TP
I have this problem too :/
Well, I just got my replacement, and it is doing it as well. I'll post some screen shots of it later on today.
Anyone want to tell me what numbers we want/need?
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Any more mad cap theories??
No issues here. Maybe there is a problem with the batch you have been replacing your devices from. No need to redesign the phone.
Sent from my HTC Sensation 4G using XDA App
Not seen any issues with mine, 100% fine.. must be a bad batch or certain firmware revision. O2 UK firmware and phone fine.
Sent from my HTC Sensation Z710e using XDA App
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
Any issues I've had were down to the ZDBox app. After I've uninstalled that I've no issues really
Sent From My HTC Sensation using Xda premium App
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
Hello guys,new guy here.
There may be a ground issue with the user,not the phone.
Bear with me:
I used to have a good buddy that could never wear a wrist watch for mare than a week.
After that,they died.
It didn't matter how expensive a watch he bought...they all died.
In this case,there could very well be a static buildup coming from the user's body.
Clothes,diet,etc. can affect body chemistry.
If it acts up again,try touching the backside of the phone to a water faucet for a few seconds.
See if grounding out the case helps.
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
No issues with mine whatsoever.....
Keep in mind before these blanket statements are made, that most owners do not have all the issues you might have. It's by no means the norm. As others mentioned, you may simply have a bad device....or bad app, SD card.
The vast MAJORITY of owners have no such problems....it gets WAY blown out of scale on these and other forums. It would be better to title your thread "I have grounding issues"...
Also, as always, anyone with major issues needs to make sure they still have said issues after a factory reset with nothing installed, no 3rd party apps, no SD card etc. If ya still have issues after that....ya got a defective device.
The vast majority of Sensations are fine....let's keep it real.
We get it....you're having problems with your device....You don't need to start a new thread everyday....I'm sure this could have went into one of your MANY OTHER THREADS YOU'VE ALREADY MADE. As for your "grounding issue", the same thing was said about the nexus one and the EVO....and in the end NEITHER OF THEM HAD A GROUNDING PROBLEM. Just as this phone DOES NOT have a grounding issue either. That being said, if you're having so many problems, return your phone, and go back to your G2X. There really is no reason for a grown man to be whining so incessantly. You have already started several threads about your many problems...post in those....No need to keep creating new threads every time you feel like complaining.
PS
As the previous posters have stated, no I don't have a problem either.
Cass67 said:
Not seen any issues with mine, 100% fine.. must be a bad batch or certain firmware revision. O2 UK firmware and phone fine.
Click to expand...
Click to collapse
I've got a TMo US Sensation, and it's great. The only "problems" i've noticed is the rare sense lag, but it always clears up in a matter of seconds. And the battery life is amazing compared to my Evo (i can go 2-2.5 days on a charge, same usage level would drain my evo in 10ish hours). While I eagerly await s-off and persistent root, I think this is a very good phone especially so recent after release.
This is your 2nd or 3rd thread that you have made to complain about something. Thread closed, start another thread complaining and I am going to consider infractions.
I posted this almost verbatim to my G+ stream. It says it all, basically, and I don't have time (at work right now) to give a lot of detail but I wanted to get this out there...
----
I received three text messages this morning at 7:25 EDT.
They appeared to be random characters, like when an OS is trying to display characters from a language that requires a codepage it doesn't have installed. They are as follows:
<sisa:68571244:1:1:199:41970681>ezG7k3jzC7mFo6SSm7KUIg
<sisa:65471246:1:1:199:43800551>HE85MqRY33Xf0qmVbaCjyQ
<sisa:65471245:1:1:199:43799818>SpxSbHILo1mHG/EjkMAF2g
All three received at 7:25. I was able to use my phone up to this point because I was able to view the messages normally. Now, suddenly I have no digitizer response. None whatsoever. To use my phone, I have to pull the battery and boot to safe mode then use my trackpad and menu buttons to access certain features.
Now, it seems to me, the first part is like an address packet, maybe including a sequence number. The second part is like what I see when e.g. viewing the output of 'cat somefile.binary' in Linux. At first I thought it was spam from a foreign country, but now I'm wondering if this was some binary code received and interpreted by my phone. I wonder if this is possibly an android virus/remote hack? Is that possible?
I may wind up wiping the phone when I get home and have ability to back stuff up, but this is annoying, to say the very least.
-----------
Now, I did a little googling and it appears that it may just be that T-Mobile was trying to send an update to the phone (maybe the fact I'm on a custom ROM is why it borked). But has anyone had this or anything like it happen to them?
Thanks much in advance,
CJ
Update
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
cj chitwood said:
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
Click to expand...
Click to collapse
My evo **** needs a good smack every now and then when the kb gets opened because it has a bad flex cable. since I'm not with sprint and only test roms on that phone I don't need the kb anymore but sometimes the little one opens it
Sent from my myTouch_4G_Slide using Tapatalk 2
Yep, I'm not so lucky. I need the touchscreen more than the keyboard
Still, was on the phone for 45 minutes today talking with two different reps, and my replacement phone (another MT4GS in Khaki) is scheduled to arrive in three days.
Time to see if I can return it to stock. It's a hardware problem, so what ROM is on it shouldn't matter, but I don't want to give them any reason to balk.
I've read a few threads on the screen Flickering and there doesn't seem to be any resolution .
I'm on my 3rd tablet now (thanks best buy accident damage warranty!) And this one is flickering worse lately than ever. I updated to the latest firmware, yesterday only to boot up to horrible bouts of flickering during the setup screens.
The odd thing is, there seem to be no consistency to it. Some days it's so had I can't even use the thing, other days it doesn't happen at all. I use the tablet every day for notes or PDF viewing. I've used it with no magnetic cover (totally naked) and with the cover.. doesn't seem to change the occurrences.
I've turned overlays on/off force gpu render on/off.. nothing seems to fix it. Sometimes changing the overlay will reduce the flickering other times it doesn't affect it at all.
I hate to say it, but if I can't resolve it, I'm going to be forced to move to the surface 3.
I'm an electrical engineer and I've done as much trouble shooting as I can think to do.. but I've come up empty handed.
Anyone else have these problems? Has anyone found a definitive fix?
I sent mine back 3 times. The first was a reset. Thanks for wasting my time. The second was a motherboard and that didn’t do it. The third time they did a motherboard, digitizer, and usb port. It's finally stable and back to normal. After 5 trips back, the BB warranty triggers a new unit. Check if it triggers a refund.
I get it occasionally, so far I'm able to resolve it by booting into custom recovery (TWRP) and clearing dalvic to allow all apps to rebuild. Sometimes this resolves it for a few days, sometimes a couple of weeks. Its a repeatable "fix" that makes me question if the issue is related to memory or trim or something like that. Kind of reminds me of how with the first generation nexus 7s one would see slow downs after a while and filing storage with fake data then deleting it would improve performance for a while.
I'm definitely not a tender user of the device. I go back and forth between multiple ROM's and kernels on a daily basis testing what is testable, and unfortunately also what is not. Anyway, even though mine was bought as refurbished on eBay, I have never had any issues like the ones you describe. More specifically, I have never had any issues what-so-ever, that was not created due to my own ignorance. To me the device seems indestructible.
Besides, I would hate to be in the place of my device, or I would definitely have turned schizophrenic. Should I feel bad about pushing it through all this?
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
ShadowLea said:
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
Click to expand...
Click to collapse
P900 wifi. Us version bought at best buy.
Today the tablet has been rock solid, I have literally done nothing between when it was flickering like mad and now.
I wonder if it might be related to some kid of data transfer. either over wifi, or when data is written or read from storage or SD card. I've take then SD card out to eliminate that as the problem.
Mine was P900 from BB
Issue lies with the screen.
This happened with me I sent it back to Samsung, 3 times. They seem to have finally got it right. They replaced the battery and then the display screen. Now it appears to be working I will let you know after a month if it is still good. They also told me that they will not replace the device even though I bought it and the issue was right from the start. Not even 6 months old. When working the device is excellent.
Ah, so now we know for sure the battery is replaceable. That's good news. Maybe someday our batteries will no longer hold a charge and we can replace it. Now for a good video on tear down and what tools to use to do that and where to get a replacement battery. I know it's early for most of us but someday......we will have to replace that battery. I'm one of those that keep my toys (computers/laptops/tablets/phones,) for many years.
Mine is running like new since last service. Getting the BB Geek Squad warranty has paid for itself already. I get 2 years on anything over $500.
Mine is a p900. I purchased from samsung website. Mine has been doing it fresh out of box. So bummed.
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
{Diemex} said:
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
Click to expand...
Click to collapse
My P900 has just begun flickering exactly as you describe. So I should just be patient and hope it goes away by itself?
I'm flickering again. Turning the screen brighter is what triggers it for me. Returning to stock just to get it back and have it flicker again to hit the magic 5 returns may be what I have to do.
https://youtu.be/CvxbVft69Kg
I just followed this guide. Its been a week now, not had any flickering since I did it.
Manya3084 said:
I just followed this guide. Its been a week now, not had any flickering since I did it.
Click to expand...
Click to collapse
Lifting the motherboard only temporary close the gaps of cracked battery connector. The permanent fix need to do: re solder the battery connector.
Look closely under magnified glass or microscope , you'll see the cracked solders. You can test by pushing the connector slightly, a bad one will move easily or lift off from its solder joints.
This video was removed from the poster after I pointed out his guessing solution. Flickering screen has nothing to do with LCD connector on the motherboard.
Lifting mother board actually you're applying pressure on the battery connector from rear cover.
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
bluebirch said:
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
Click to expand...
Click to collapse
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Beut said:
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Click to expand...
Click to collapse
Thanks, missed that other thread. Next time, I'll send them an en explicit request to replace the battery comnector, and refer to those two threads.
Stefan
Tapatalked on some kind of Samsung tablet
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version