Related
Hi there!
The problem i'm having, for which i have found no solution yet and no help or similar cases around several forums or google is the following:
I've had my Asus Transformer for several months (since august) and it has worked perfectly until this Monday. after playing a while with it, i left it in normal sleep pressing the power button and when i woke it up to keep on playing the screen would not turn on. The problem was the screen illumination. If i used a lantern tu illuminate i could barely see the unlock button. after i rebooted, and reinstalled several times revolver rom I managed to get it fixed.
I then found out then that this screen issue only happens whenever I try to modify the brightness of my tablet, specially if an application is running in that specific moment.
I've tried restoring nandroid, flashing from cwm, flashing on apx mode from pc, restoring stock rom, prime rom, and revolver rom with absolutely no success. I'm am unable to modify the screen's brightness with out getting the problem of the illumination, and i dont carry a lantern with me to use my tablet whenever this happens.
Did anyone have this same problem? maybe something similar? Does anyone know which can be the cause of this problem? Any idea how to solve it?
P.D.: I installed revolver rom a week or two before this started happening.
If you've tried countless software things and that has not resolved the issue, then it leads me to think the backlight may be dead or finicky. It seems like an issue to RMA for. Try giving it a few firm taps to see if it may be a loose connection (not hard enough to actually damage).
codyrt said:
If you've tried countless software things and that has not resolved the issue, then it leads me to think the backlight may be dead or finicky. It seems like an issue to RMA for. Try giving it a few firm taps to see if it may be a loose connection (not hard enough to actually damage).
Click to expand...
Click to collapse
I've also thought that the hardware might go wrong, but in that case:
-how can just playing a game have caused that?
-how can it be that the trigger that leads to the screen failure is modifying the screen's brightness?
Also, I forgot mentioning, i found out that messing about a bit with the brightness config. while the screen is off or crashed or whatever, and then pressing the power button twice, one for sleep and one to turn it on will fix the screen again.
referring to the RMA: I live in spain, but the tablet was bought in US. Is Asus waranty world wide? or should i have to send it myself to US?
fmiguellopez said:
-how can it be that the trigger that leads to the screen failure is modifying the screen's brightness?
Click to expand...
Click to collapse
Since the brightness control is interacting with the hardware backlight, at a certain level of brightness, it may be defective. I've had LED lights burn out but still work at a lower level, and sometimes a temperature change brings them back for a short period of time.
fmiguellopez said:
referring to the RMA: I live in spain, but the tablet was bought in US. Is Asus guarantee world wide? or should i have to send it myself to US?
Click to expand...
Click to collapse
This ones out my scope of knowledge, I'm sure another member on here knows the answer to this one.
In the end after testing, my asus tf looses the screen brightness over a point, may be 50 or 60 percent. can someone tell me for sure this is a hardware issue? in case it is, should it be difficult to mend? im struggling to find the waranty ticket
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
rock1324 said:
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
Click to expand...
Click to collapse
Update:
I can now rarely get it to vibrate for even a second holding the power for a long long time. Screen does not come on at all. Looks completely dead.
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Thats OK said:
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Click to expand...
Click to collapse
I was hoping it wouldn't lead to something like this. I got my tablet from Amazon around the first week of september. I have treated it very well.
I'm not quite sure how it could have burned out, my brightness is usualy <50% and I have used the super IPS+ more less time than I can count
on one hand. If this is the case, Is it possible that a technical problem like this would still be repaired on warranty seeing as it has nothing to do
with the bootloader?
Also I'm not sure how this explain the constant vibrating that does not turn off untill the battery runs out. The way I see it is you could be right, the tablet is trying to tell me it's not going to work, or there is really some kind of software glitch.
Have you ever had LCD problems with a tablet? any idea how much this could cost?
rock1324 said:
Have you ever had LCD problems with a tablet? any idea how much this could cost?
Click to expand...
Click to collapse
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Thats OK said:
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Click to expand...
Click to collapse
Thanks for the advice, I have heard some terrifying stories of Asus customer support (never had a problem with them myself) and of devices just being completely lost in their care.
To answer your question, no the back lights are not visible at all. The only way I know the Infinity is somewhat alive is by the led coming on while charging and the somewhat random vibrating patterns that happen when trying to boot up.
Hi, I have a sensation XE that i S Off-ed and rooted using FloWolf's EXCELLENT guide before installing CM 10.1-20130322-Albinoman887-pyramid. However, i started facing the issue of the hardware keys giving feedback when touched, but not working- instead, it happens as if the lowest part of the display, right above the key i pressed, has been touched. I updated to the 20130510 nightly but it did not fix the issue. I now want to try going back to the stock ROM but can't find an easy guide. I never took a backup of the stock ROM with CWM . I have the HBOOT 1.29 model
Now another issue has sprung up. Even when using a single finger, the phone sometimes behaves as if i'm multi-touching it. It only gets fixed if i lock and then unlock the screen.
Will going back to the stock rom fix these issues or will i have to get it repaired? If the stock rom will fix it, can i please get a link for it that's as easy as Flo's guide to rooting was. Thanks!
Omer Humayun said:
Hi, I have a sensation XE that i S Off-ed and rooted using FloWolf's EXCELLENT guide before installing CM 10.1-20130322-Albinoman887-pyramid. However, i started facing the issue of the hardware keys giving feedback when touched, but not working- instead, it happens as if the lowest part of the display, right above the key i pressed, has been touched. I updated to the 20130510 nightly but it did not fix the issue. I now want to try going back to the stock ROM but can't find an easy guide. I never took a backup of the stock ROM with CWM . I have the HBOOT 1.29 model
Now another issue has sprung up. Even when using a single finger, the phone sometimes behaves as if i'm multi-touching it. It only gets fixed if i lock and then unlock the screen.
Will going back to the stock rom fix these issues or will i have to get it repaired? If the stock rom will fix it, can i please get a link for it that's as easy as Flo's guide to rooting was. Thanks!
Click to expand...
Click to collapse
I am on ICS 4.0.3 and Stock ROM.
Since last few days, I am having somewhat similar touch screen issues after the warranty of my Sensation XE expired last month.
At any given random time of the day, my touch screen goes berserk....!!! I am using Apex Launcher and have folders containing various apps in the Dock. These folders start moving around/rearranging automatically, apps start opening randomly on their own, screen and navigation keys (red ones on bottom panel) become unresponsive, keyboard comes up on its own and characters appear as if being typed... etc. If I lock and unlock the screen (all hardware keys - volume & power - work fine during all this), touch screen becomes responsive again but only for a short period. Again the whole cycle repeats. The only way to stop this for longer period of time is restarting the phone. This state last upto anywhere between 6-10 hours be fore my phone acts up again. I have tried the Factory Reset too, but with no results.
I have installed Avast Mobile Security soon after I got my XE. I have also installed around 80-90 paid as well as free apps.
Currently my XE has free resources as follows:
RAM 640MB out of 1.1GB
SD Storage 25GB out of 29.71GB
Though the behavior looks like some kind of virus activity, Avast doesn't show any malware or virus on the system.
Which issue does this behavior pertain to, a hardware or a software issue?
Any kind of help to pinpoint the cause of this issue is greatly appreciated.
Thanks & Regards.
Hello,
I am having the exact same problem as the two mentioned above. Sometimes the thouch screen doesn't response at all, start doing things by itself or the capacitive buttons on the bottom doesn't respond. To fix the problem I have to press the on/off button to lock and unlock the phone but after a minute it's going all over again. I thought this maybe could be a memory problem, as if the phone simply hangs because it is acting very slow when the problem shows up.
Last weeks I've tried many ROMS as I thought it would be a mem problem. Cyanogenmod 10.1 and 10.2, ViperS 1.6.3 and 3.1.2, Android Revolution and with all these ROMS the same problem showed up. So I'm thinking it's almost for sure that this is a hardware problem. I got my Sensation XE in January 2012 so there's still a waranty of a half year. In case this is a hardware problem I'm thinking about sending the phone back to HTC, but I'm not sure about what is causing this problem.
So, if anyone knows the cause of this problem, please share It's really annoying and makes the phone pretty much unusuable. In October I will be able to get a new phone but it would be nice to have a very good one for spare
Thanks in advance!
Sibbevangeyn said:
Hello,
I am having the exact same problem as the two mentioned above. Sometimes the thouch screen doesn't response at all, start doing things by itself or the capacitive buttons on the bottom doesn't respond. To fix the problem I have to press the on/off button to lock and unlock the phone but after a minute it's going all over again. I thought this maybe could be a memory problem, as if the phone simply hangs because it is acting very slow when the problem shows up.
Last weeks I've tried many ROMS as I thought it would be a mem problem. Cyanogenmod 10.1 and 10.2, ViperS 1.6.3 and 3.1.2, Android Revolution and with all these ROMS the same problem showed up. So I'm thinking it's almost for sure that this is a hardware problem. I got my Sensation XE in January 2012 so there's still a waranty of a half year. In case this is a hardware problem I'm thinking about sending the phone back to HTC, but I'm not sure about what is causing this problem.
So, if anyone knows the cause of this problem, please share It's really annoying and makes the phone pretty much unusuable. In October I will be able to get a new phone but it would be nice to have a very good one for spare
Thanks in advance!
Click to expand...
Click to collapse
Put a thin foil between the metal pin on mid right and the back case.
Also search for touch screen issues in sensation forum. A lot of people have this issue.
Happy to help.
Far_SighT said:
Put a thin foil between the metal pin on mid right and the back case.
Also search for touch screen issues in sensation forum. A lot of people have this issue.
Happy to help.
Click to expand...
Click to collapse
Thanks a lot Far_SighT for pointing me in right direction.
As per the "Touchscreen Issues" topic in "General" category, my phone will be undergoing second cycle of "Pull Pin - Add Tin Foil - Drain Battery - Take out Battery - Press Power - Keep Battery outside overnight - Recharge fully without touching screen" procedure.
First cycle didn't help much, but as per the post I have to go through this cycle at least 2-3 times.
I will get back with the results.
Thanks & Regards.
Update:
Followed the steps in the "Touchscreen Issues" thread under "General" category, and it worked!!
All my touchscreen issues have been solved by that simple solution. A great post!!
Highly recommended for solving similar touchscreen issues, specially when you have dropped your phone.
Thanks & Regards.
radhx said:
Update:
Followed the steps in the "Touchscreen Issues" thread under "General" category, and it worked!!
All my touchscreen issues have been solved by that simple solution. A great post!!
Highly recommended for solving similar touchscreen issues, specially when you have dropped your phone.
Thanks & Regards.
Click to expand...
Click to collapse
Can you elaborate which step you think fixed the issue of having to press the power button to make the screen responsive? I went throught a full battery discharge-leave overnight-full charge without touching the phone, but i did this procedure only once and didnt have the patience to try again as it didnt improve the situation at all.:cyclops:
usju said:
Can you elaborate which step you think fixed the issue of having to press the power button to make the screen responsive? I went throught a full battery discharge-leave overnight-full charge without touching the phone, but i did this procedure only once and didnt have the patience to try again as it didnt improve the situation at all.:cyclops:
Click to expand...
Click to collapse
Please follow my last post in "Touchscreen Issues" thread: http://forum.xda-developers.com/showthread.php?t=1239238&page=50
Mostly one cycle does not help as per my experience. I had to go through 3 complete cycles to get my XE fixed. It made huge difference only after second cycle.
Also, other than aluminum foil over the silver square on the side of back panel, place a piece of thin paper in the depression on the back panel (check the second snapshot in above thread) which should cover the metal casings of both SIM card and SD Card so that they do not touch the back panel.
The steps taken in the cycle after placing the foil and paper:
1] Drain the battery fully.
2] Remove the battery.
3] Press Power button as if trying to power on your mobile.
4] Leave the battery out for overnight.
5] Replace the battery and back panel taking care to see that both foil and paper are in correct positions.
6] Recharge your phone fully without touching the screen and without powering on (this to prevent you from using the phone. ).
7] Disconnect the charger and use your phone till battery drains out and phone is ready for next cycle.
Hope this is helpful to sort out your issue.:fingers-crossed:
Thanks & Regards.
Far_SighT said:
Put a thin foil between the metal pin on mid right and the back case.
Also search for touch screen issues in sensation forum. A lot of people have this issue.
Happy to help.
Click to expand...
Click to collapse
Thanks for the tip but did that already. I read the OP well and a lot of pages in this topic but no luck so far. Stopped even trying because half October I will have a new phone, the One to be exact. So it's no use.
What I did try was the recalibration of the touch screen by flashing the image file. That worked for a few days maybe and now it's drama all over again. Sometimes I pull out the battery for a night, push the on/off button blabla but no luck too. I think it's actually half broken because on some spots on the screen it's registering no touch. I do have to admit my phone fell a couple of times past 2 years, without a case or something. So I guess for me the only option is a new digitizer.
Like i said, I really would like to have a good spare one. Went looking on E-Bay and for 16 dollars I found a digitizer for the Sensation 4G. I have a XE, will that work with that digitizer? A digitizer for the XE was 23 bucks, but if only the color of the capacitive buttons are different I don't care and I save 7 bucks
Thanks!
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??
semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.
Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?
Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it
I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.
Rma
Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.