Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
purudaya said:
Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
Click to expand...
Click to collapse
A co-worker of mine had an S3 T999 on tmobile that did this same exact thing on the stock unrooted rom. I'd say its unrelated to CM, and glad you got a replacement. It should not do it again, so CM is safe to run on it.
Not a Rom issue. Sounds like just bad luck of the draw. I am on my 3rd or 4th s3 and i haven't had a Rom kill my phone yet.
Sent from my GT-P5113 using xda premium
I have had a CS918 box for around 4 months and it largely works very well, however every now and then (once an hour maybe, sometimes two or three times in the space of a minute though) the screen goes blank for a second or so, the sound also cuts out for this period of time also.
I was using stock firmware, recently updated to a 1080p kernel and custom rom, but this still persists.
I've changed the HDMI cable and the slot it's in also.
I'm leaning towards a dodgy power supply - has anyone else had this issue?
Many thanks
Hammer_drum said:
I have had a CS918 box for around 4 months and it largely works very well, however every now and then (once an hour maybe, sometimes two or three times in the space of a minute though) the screen goes blank for a second or so, the sound also cuts out for this period of time also.
I was using stock firmware, recently updated to a 1080p kernel and custom rom, but this still persists.
I've changed the HDMI cable and the slot it's in also.
I'm leaning towards a dodgy power supply - has anyone else had this issue?
Many thanks
Click to expand...
Click to collapse
I've just bought one of these boxes and am having this issue. I've tried searching everywhere for other people having this problem and this is the only post I've found.
Has a fix ever been discovered?
Johneboy said:
I've just bought one of these boxes and am having this issue. I've tried searching everywhere for other people having this problem and this is the only post I've found.
Has a fix ever been discovered?
Click to expand...
Click to collapse
I also have an issue with mine, and the answer seems interesting and related.
With mine the image flickers sometimes, and needs to be reset, other times the audio will just go quite for 2-3 seconds.
It very well could be a power supply issue, as it seems to be slightly loose, but the interesting thing is that the video keeps playing perfectly when the sound goes out.
It does the sound thing much more often now that it did before too.
got the same audio issue ... could it be the hdmi cable?
I have the cs918+ and have the same blackout issue I update the firmware frequently but still happens...
Sent from my SGH-M919 using XDA Free mobile app
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
I have my phone paired to my Pioneer head unit and if it disconnects it will occasionally cause the Bluetooth to turn on and off continuously without warning or anyway to stop the cycle. The only way I found to resolve the issue was a factory reset. I just reset my phone yesterday and the same thing happened today when I tried to re-pair to it again after I left my car. As you can imagine, this is extremely annoying, I am hoping someone can provide some insight on a possible fix for this.
Blu Pure XL
Stock ROM
Android Lollipop
SWV: BLU_P0010UU_V16_Generic_5.1_15-03-2016
I've experienced the same thing with my BLU Pure XL. It doesn't look like anyone has responded; likely because there isn't a fix and the phone is so substandard. Bluetooth is weak; signal strength is pathetic, cheap glass, lacks friendly ergonomics. I could go on. I've tried to submit issues through BLU website - no response. I won't give them another chance. Likely will buy the new Plus 1. Good luck and if you find a fix please post it here.
WilsonBridge said:
I've experienced the same thing with my BLU Pure XL. It doesn't look like anyone has responded; likely because there isn't a fix and the phone is so substandard. Bluetooth is weak; signal strength is pathetic, cheap glass, lacks friendly ergonomics. I could go on. I've tried to submit issues through BLU website - no response. I won't give them another chance. Likely will buy the new Plus 1. Good luck and if you find a fix please post it here.
Click to expand...
Click to collapse
So I noticed the Bluetooth issue only occurs for me when I am connected to a bluetooth device and a specific sequence of events occurs to cause it to happen. Specifically something like my vehicles aftermarket Pioneer radio where I can wipe the bluetooth memory of it (it has a 3 device limit). If, I wipe the bluetooth memory of my radio while my phone is connected, it will cause it to go into a loop and thus require a factory reset to resolve the issue. Since I discovered this, I have wiped the memory while the phone is disconnected and the issue does not occur. It has been quite sometime since I have originally posted here and I haven't had a problem since I have monitored it. Please let me know if this seems to be the same thing that occurred for you as well. Cheers
Hi guys!
I've got a problem since yesterday, my Nexus 5 loses connection to Wifi every other minute and as of now, I'm completely unable to activate it over the menu.
I had Dirty Unicorns v11 installed, I thought the Bootloader/Radio was outdated and updated it with images from the last 2016 factory image. This didn't change a thing, so I updated to the newest Unicorn (with factory reset) and then to the newest Lineage nightly with the same result.
After opening my Nexus everything in it seems fine, I replugged the antennas just in case..
As of now, I really don't know what to do anymore. Any suggestions?
I experienced somethig similar with my second Nexus 5. From then to now the WIFI coould not be toggled on again. It just died. Seems like a common problem is hardware related as i understood.
If you are in warranty just hand it in.
I don't think there's any warranty left after 3 1/2 years
I also think it's hardware related because I can't even read the MAC of the chip. Maybe some reflow soldering would do the trick, but I think this means new smartphone for me -_-
Diablokiller999 said:
I don't think there's any warranty left after 3 1/2 years
I also think it's hardware related because I can't even read the MAC of the chip. Maybe some reflow soldering would do the trick, but I think this means new smartphone for me -_-
Click to expand...
Click to collapse
Does bluetooth works for you?
BT works just fine