So before the gingerbread update i was experiencing the nexus one touch screen issue. This issue would happen mostly when the phone would be charging or warm, and the y coordinate of the touch screen would be off by about an inch. (I would post a link to youtube but i can't yet... new member =/ ) So if you try to answer your phone while the defect was active, you couldnt, because touching the slider would be recognized as trying to touch the 'menu' key on the phone.
Anyway, after gingerbread got pushed to my device, i have yet to experience this issue!! i havent been able to find anyone reporting this resolution. i'm extremely please about this because it was becoming a deal breaker after i missed an important call because i couldnt answer my phone due to the issue!!
anyone else experiencing this resolution!?
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Hollow.Droid said:
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Click to expand...
Click to collapse
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
this is where I was at before the push, i was seriously considering the incredible s, but for now it seems to have completely disappeared from my device...
I've also heard its a hardware issue (I do believe it to be true, not questioning that), so i found it extremely odd that its not happening now on my device.
Guess I'll just keep my mouth shut and enjoy
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
NexusDro said:
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
Click to expand...
Click to collapse
*gasp* not my invisible shield!?
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
I had it terribly after the GB OTA, I wiped cache & dalvik and it all but went away. One occurrence in a week and a half, and I've been using the crap out of the phone.
Slightly off topic question: On stock Android, is wiping cache the same as wiping the dalvik cache? The stock recovery doesn't have the "wipe dalvik" option, only "wipe cache".
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Rusty! said:
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Click to expand...
Click to collapse
Thanks. But every time you flash an official update, the cache gets wiped and rebuilt though, right? That's why after each update it takes a long time to boot.
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
I still have the prob but it's different with 2.3
Before 2.3, the touchscreen problem was unpredictable and could happen at almost anytime, whether charging or not. I replaced the handset but the problem persisted.
Since upgrading to GB, I've noticed a very clear pattern. If I'm charging my device and unplug it before it is fully charged, the touchscreen becomes extremely erratic to the point I must reboot the phone. If it's allowed to charge completely it's okay.
It never happens when it's is not charging.
Still annoying as hell but I've moved to Africa and having the device replaced is a real challenge. So I guess I'm stuck with until I replace it.
Still has issue
Stock, no modification at all. Today when I was rearranging icons in ADW Launcher, it seems that the screen registered click below where my finger actually was, same as the problem I saw previous to updating to 2.3.3. The phone was not hooked to a charger at the time.
Stock GRI40 here on my Nexus One...same issues that i've already had with Froyo. As it was posted before, it's a hardware issue; and the Nexus S is the new kid on Google's block, so i'm not expecting anything to improve our screens.
filippogiad said:
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
Click to expand...
Click to collapse
Theoretically, there is a chance they could fix a software workaround for the hardware problem. If the error happens in only specific circumstances, and ALWAYS happens in those circumstances, then just teach the phone to know when those circumstances are happening, and tell it what to do in those cases. However, I doubt anyone at Google is working too hard on this problem. I agree, it seems to be much less frequent than it ever was. Seems likely that they may have added a little something to help us out.
brettbellaire said:
Seems likely that they may have added a little something to help us out.
Click to expand...
Click to collapse
Or more likely, it could be unintentional.
So even with official OTA it's still here?
Remember me of the ''crazy'' screen problem we had before while charging,perhaps it's a hardware problem after all
This is a main reason why tomorrow i'm getting a new galaxy s.
I tried a lot of custom and stock roms, I sent my phone to HTC and they replaced hardware, but this issue still persist. And it cause me a lot of problems, especially while driving...
I also still get that glitch but not as frequently. I noticed that i didn't need to reboot the phone to fix it. All i need to do is tap the power button to shutoff the screen and then re-tap to turn it back on and it'll show the lock screen. Slide to unlock and the screen is precise once again.
The bug is still there for me also. However, I didn't seem to have it as bad as some did originally, and now I've noticed that it's happening even less frequently.
Related
So, I've been having the screen sensitivity issue, jaggedy drawn lines, randomly typed keys, etc.
Now, has anyone else done the same?
As the problem is intermittent, what're the odds they'll actually fix it?
Also, is it actually going to be gone 2-3 weeks or do they usually turn around quicker?
I miss it already
mine was gone for 24 days, all it needed was a software flash. overall, good service, but could be quicker......
if they just flash the software I'll not be happy, I could do that myself.
Antimus said:
So, I've been having the screen sensitivity issue, jaggedy drawn lines, randomly typed keys, etc.
Now, has anyone else done the same?
As the problem is intermittent, what're the odds they'll actually fix it?
Also, is it actually going to be gone 2-3 weeks or do they usually turn around quicker?
I miss it already
Click to expand...
Click to collapse
I have this issue too, and I read about it on some other threads as well.
I'm not really sure what is causing it, but its more likely to be a hardware issue rather than software.
Although my friend bought his HD2 recently, and his phone doesnt have this problem. I guess this issue is fixed in newer HD2s
You can see this thread for discussion and videos about this issue
their service is worst ive ever know...4 weeks so far....never going to send my phone to them, rather send it to dodgy kev from the pub to fix
Just done a search about this prob and there is a couple of similar threads but they are not really same issue.
This has happened 3 times now with different roms over past month and not sure what is causing it. Phones screen seems to go bright white on wakeup, looks like a negative.
Is there any experts out there who could shed some light on it. Does it sound like a slow hardware failure or is it more likely a software issue. As I say its only happened a few times and a reboot brings it back to normal but it just concerning
Has anybody else had this same issue on wakeup before?
My first reply post here...
I have the same issue...reboot will recover it...but ones it recovered after normal stand-by upon wake up...I assume it is just some incompatibility of Android with HD2 graphic processor, minor issue.
Current ROM
Omega WM6.5.x v14
Current Android Build
NexusHD2 v1.8
I used to have the same problem and put it down to an incompatibility. Since moving to a Nand ROM it seems to have gone away.
TheATHEiST said:
Phones screen seems to go bright white on wakeup, looks like a negative.
Has anybody else had this same issue on wakeup before?
Click to expand...
Click to collapse
I used to have this issue, but only on SD builds, and very, VERY rarely. From about 5-6 months of SD Android, I probably had it about 4 or 5 times.
I agree with madmillsy that I've not seen it on a NAND build, but I don't think I'd seen it on recent SD builds either.
Is it an SD build you're running, and if so, how old is it?
Edit: Forget that last question - just saw your current ROM in your sig.
I saw this effect twice, never in WM, only in Android. First time with SD build, but second time, last week with gauner's HD NAND build.
As it was already described, there is probably some incompatibility regarding graphic, when waking up from idle mode. I do not think it is related to SD builds only, they handle graphic same way, with same kernels.
By the way in gauner's build I noticed also problem with activating sound from idle mode time to time. So maybe it is not directly graphic driver part, could be somewhere else and this is just consequence.
At the end, it is rare and minor issue, the only discomfort is because of restarting the phone.
Had a few times this issue, and didnt need to reboot to make it worn off. Just put it in a colder environment, and it will go away after 10 minutes orso. So I honestly thing is has todo with the temp of he device. Mostly it came up after a long phonecall I had, which maked the phone a little 'hotter'.
Just a speculation though, didnt have this issue since I use NAND. But I guess it can come-up randomly, but I don't worry it to be honest.
Its happened twice on SD builds and once on NAND build.
I was concerned that I was starting to get a hardware fault but im relieved to hear that others have had it so it must be simply a soft bug.
It rare anyway so no big deal.
Thnx for replies guys.
happened to me once with NAND - sorted with a reset. Scared the hell outa me
F-bone said:
happened to me once with NAND - sorted with a reset. Scared the hell outa me
Click to expand...
Click to collapse
same here, including the scared bit.
sodeknetters said:
same here, including the scared bit.
Click to expand...
Click to collapse
the weird thing is that since I posted in this thread it happened to me twice today!...total 3 times so far... Im getting worried...
Never happened to me with an SD build (after 3 months of use) but happened twice to me with DFT's NAND, reboot fixed it as stated and yes...it scared the **** out of me the first time lol
For anyone that might be debugging the issue - it might be connected with calls.
I receive a call. After I'm done with talking, i turn on phone and it's on negative. Alright, i restart it. After restart it works fine, until i call somebody. After call, again negative screen. It happened two times in a row.
Also i don't really need solution to this problem. Only some kind of workaround that will allow us to fix problem manually without restarting phone. Maybe a script that will reset display driver or something?
I was one of the unlucky persons to deal with the dreaded touchscreen problem. When on the 44s build, it sometimes got so bad the phone was almost completely useless. The touch screen problems didn't go away in spite of flashing countless Rome with almost every possible combination of kernels.. But nothing seemed to help. The touchscreen got noticeably worse when the phone got hot..i was almost at the verge of giving up.. But that's when it happened.. The 05Q update solved all of my touchscreen problems. I've checked with touch Explorer and even multi touch works flawlessly.. I understand that this problem was identified as a grounding defect.. And I did buy it.. But since the 05Q update seems to have completely solved this issue, my faith in oneplus has been restored.. Did anyone else notice this? What could be the reason?
Nothing's changed for me :c
Sent via Telnet
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
my problems
onefanboy3556 said:
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
Click to expand...
Click to collapse
I've been facing touch issues after this update. The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Anyone have similar problems or with possible solutions ? Also for heavy battery drain
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
I'm having some issues too with this! Sometimes, even the physical power button doesn't work and I have to press it multiple times!
I m also facing same issue
Any solutions to resolve this issue?
Glad to hear it is better for you. Unfortunately, I still am experiencing ghost touches... Double tap on the other hand is fine.
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
kewlstuffdudez said:
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
Click to expand...
Click to collapse
From my experience I could say that these 'gost touches' are related to a system slowness more than a touch problem. Sometime I feel I could type fast without any problem, sometime I had to type very slow. Also this is rom related. Some are really snappy others not so. Another thing to mention is that keyboard feels better after a reboot, so maybe a memory leak!?
Inviato dal mio A0001 utilizzando Tapatalk
I just hope it's not the hardware touchscreen / sensor. My observations are consistent with everything you mentioned above. Memory leak feels possible or some unoptimized code. I don't see any issue in ex Chrome. It's mostly Hangouts app that's super slow so perhaps Google also pushed some update to Hangouts that slowed things down enough to be noticeable.
anuradha1208 said:
The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Click to expand...
Click to collapse
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Steelpapi said:
Sometimes, even the physical power button doesn't work and I have to press it multiple times!
Click to expand...
Click to collapse
Yes, same here!
kewlstuffdudez said:
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Click to expand...
Click to collapse
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
I went straighten to CM12 nighties. The touchscreen issues still does up but not as much. Makes me think is a hardware issue with the touchscreen independent of firmware perhaps just didn't notice before. When I went to CM12 I did a full wipe, so everything from scratch
Sumanji said:
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Yes, same here!
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
Click to expand...
Click to collapse
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
I have not faced touch screen issue.
Even i have broken my display from top..
Sent from my A0001 using XDA Free mobile app
Steelpapi said:
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
Click to expand...
Click to collapse
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
A thread i created in the oneplus one forum after a bit of research from my side
https://forums.oneplus.net/threads/major-touch-screen-issue.282231/
Sumanji said:
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
Click to expand...
Click to collapse
Crazy stuff.. Looking at the video, I have almost bought that it's a software problem..
Mine works fine if and only if you turn off all those double tap settings (wake/sleep) and turn off ambient display.
I've gone through all the settings menus and turned off everything gesture or touch related... also switched to onscreen buttons.
Still have the same problem
I emailed support to arrange an RMA, but they want me to wait for Lollipop... WTF?
Hello everyone,
I've had my note 4 over two years now and out of nowhere problems started happening after second MM update, model SM-N910F was freezing and restarting and sometimes was not able to boot normally and got mmc read fail.
I'm reading a lot about this problem in other forums and here, so hope someone could help about this issue.
No Success:
I tried anything from removing sd card, removing sim card, changing the battery, resetting the device, cleaning the cache, flashing the room through odin, flashing the rom with pit file and doing a re partition (Didn't tried Nand erase).
Success:
The only way that I was able to fix the freeze issue was by installing app called Wake Lock and enabling PARTIAL_WAKE_LOCK.
But using Wake Lock has its disadvantages. First of all you need to run the app all times which its not practical and second it wipes your battery because it keeps device and processor awake.
Please join this thread anyone who has similar issues with the aim to fix or bring the phone to an usable state again.
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
The Sponge said:
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
Click to expand...
Click to collapse
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
shpeendi said:
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
Click to expand...
Click to collapse
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
I really don't think it's an hardware issue but even if so, why this started to happen immediately after the update and why it only happens when the device goes to sleep or when we power on the device.
I also noticed the change on bootloader fonts and interface after the update. I'm suspecting that the problem is there.
Does any one has any thoughts about this?
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
ciscostud said:
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
Click to expand...
Click to collapse
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
shpeendi said:
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
Click to expand...
Click to collapse
It was a Bad batch of nand chip that started to go bad after a year or two. Note 4s started to drop like flies before April.
I think your in the 1st stage of Loss and Grief. 1st stage is denial.
If thats so than Samsung should repair our phones under warranty and not tell us we have to pay for the repair coz we installed custom roms.
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
golden_m said:
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
Click to expand...
Click to collapse
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
ciscostud said:
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
Click to expand...
Click to collapse
I would be more interested in understanding how come so many Note 4 devices started acting up around same time mark...
This is definitely a hardware problem with the motherboard. Mine started giving the same symptoms 2 weeks after the 6.01 upgrade. Wakelock made it stable but after Samsung replaced the motherboard it is so much faster and no issues at all. I wonder if this is a faulty NAND issue whether the 6.01 upgrade and the way it manages memory could have triggered it. Certainly strange but it need Samsung to fix it.
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
anasrizvi said:
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
Click to expand...
Click to collapse
Sorry to hear that, as for now jut install wake lock and enable partial_wake_lock so you can use your device until it fails completely
Mmm. I was thinking to root my phone (4month old still under warranty ) i think i changed my mind after reading this ?. Thank you guy's for the warning
Sent from my SM-N910G using Tapatalk
Same issues, I downloaded the wake lock and so far so good.
I have the same issue also guys and it started a week after updating to Marshmallow.
Phone worked perfectly fine for 2 years prior to this. So I highly doubt its a hardware issue and more likely a software/firmware problem.
Phone seems to have issues whenever the screen is asleep (hence why the wake lock app seems to help with this problem although not a proper solution)
I'm hoping Samsumg can release a patch fix for this as I truly love my Note 4 and would like to keep it for some time yet.
have anybody tried going back to Lollipop?
golden_m said:
have anybody tried going back to Lollipop?
Click to expand...
Click to collapse
I was thinking about that! but I saw on other threads people downgrading with no success.
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
steveindajeep said:
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
Click to expand...
Click to collapse
I haven't heard of any display issues in this regard since the X's initial release, and that was fixed pretty quickly with an OTA. None sense then... The "display driver" is built into the kernel, and if this was an issue I'm sure we would have heard more about it.
Sorry to hear, but this sure sounds like a hardware problem.
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
_arxn said:
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
Click to expand...
Click to collapse
Later on the same day: So I fell asleep for about 4 hours with brightness on low. (damn I sleep a lot) woke up and the issue returned. But I had the brightness on full for a while and it seems to have resolved again when I put it back to low brightness.
That's all so far. Still monitoring
I'm glad someone else noticed that when you slide the brightness bar it effects the way this display issue behaves. I was starting to think I was alone on this. Now this is just my experience on my phone of course. It seems to be around 2/3 way to full bright that it starts to flash the white lines on and off and then 3/4 + it is pretty much acts as it should, they go away! So I took a screenshot as acejavelin suggested and the screenshot was clear. So this would explain why updates don't seem to change anything since it does seem to be a certain batch with bad hardware. Can this hardware be solder changed? Guess I will keep an eye out for sale of xpure with busted digitizer/good lcd to test and possible mb swap.
Yes 1575 definitely has a display driver issue, i've noticed this too. I don't think there is a way to fix this, unless it would be fixed in Nougat.
But how sure are you that it's a driver issue and not hardware? That's why I'm waiting for nougat. If it doesn't fix the issue then I'm just going to have to retire the phone.
Sorry bro
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Mine has the same issues now and then but a restart fixes it always.
Bill720 said:
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Click to expand...
Click to collapse
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
But the Op!
onupirat said:
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
Click to expand...
Click to collapse
steveindajeep said:
I've already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
Click to expand...
Click to collapse
Oh. I just read this and assumed that we were all talking about the same thing. In your case, I'd perform some experimentation to make absolute certain that your findings aren't just coincidence.
Question re: hardware vs software
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
Hi ~ just read your msg, and tried your "screenshot test." The grayish area on my screen (which over time, comes & goes - haven't detected a pattern as to why/when) DOES show up on the screenshot.
If I understand correctly, that would tend to indicate that I am experiencing a software issue? (Not hardware)
I did do a Factory Data Reset, and am experiencing the same issue. I had not added any apps for an extended period of time, prior to this gray-area occuring. I did, however, drop the phone. I don't recall for certain, but I don't think the problem occurred immediately, rather, it started very shortly thereafter (1 -3 days).
And I am waiting for delivery of a battery, since that's shot (runs down very quickly, & shuts down with anywhere from 30% - 60%+ battery level).
Any suggestions for resolving this? I hope this post makes sense... And thank you for any ideas or assistance you can offer!
Hello everybody. I have the same problem.
And who ever changed the display? Do you want to understand this is the problem of the display, motherboard or drivers?
I think it's a software problem, a hardware will not stop glitches when you flash a different software until and unless you fix it. In my experience, after my phone break because of downgrade to marshmallow stock firmware, and with an unlock bootloader i update my phone using OTA update, suddenly it stop working. blank screen and i tried try to recovery it with xt1575 IMG file to boot it again, mine it was xt1572(India) then I start facing a lot of problem, glitches, can go back to marshmallow stock firmware so and so... Now I'm trying to find a solution !!!! Custom ROM, CM13 work better and no glitches till now... I will Report soon
Moto x style/pure display problem
steveindajeep said:
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
Click to expand...
Click to collapse
I think maybe due to brightness control problem, could be the software or hardware problem