Related
Okay so I've had the HTC Fuze for 3-4 days now and 1 thing that i noticed is in the screen, by the bottom (where the touchflo is) the screen is like "blinking".
It's hard to explain, but if you get closer to the screen you see like its moving and shaking but when you look at any other spot its not.
Is this normal or my device could have a problem?
Oh and sometimes when i use the keyboard and the screen rotates, the "right side" which is the bottom (keeps blinking) sometimes has the letters of the menu before i rotated the phone, so it has like letters with opacity there as if OVER the screen.
Any of you have this problem? Or is it just me?
What can I do? My device is still in warranty but its a really small problem, it just bothers me the screen like that.
Thank you.
PS. Ill post a video if you want to see more clearly.
not normal
I agree this is not normal. Reflash your ROM.
xlinkx said:
I agree this is not normal. Reflash your ROM.
Click to expand...
Click to collapse
I've never done this before. But i wanted to take all the A&T stuff of my phone and make it faster. What ROM would you recommend me?
There's other threads about this on these boards. It's a hardware issue with the Fuze, and yes, it is normal. I've gone through 4 Fuze's, all of them were sent back on warranty, because of this exact problem. I just seen a thread not too long ago about it and someone mentioned that it was a hardware problem but I really don't remember his/her explanation of it.
PryorDaniel said:
There's other threads about this on these boards. It's a hardware issue with the Fuze, and yes, it is normal. I've gone through 4 Fuze's, all of them were sent back on warranty, because of this exact problem. I just seen a thread not too long ago about it and someone mentioned that it was a hardware problem but I really don't remember his/her explanation of it.
Click to expand...
Click to collapse
Oh so should I send mines back or just keep it?
It doesn't bother me at all, i mean, i could live with it, but sometimes i think it would be better if it didnt do that.
It just happens when my device is hot. I mean, when you use WIFI the phone gets warmer and thats when the screen starts doing that, when i turn it off and let it rest it works fine again, and sometimes when i put it in standby mode and then back to normal it comes with the blinking thing and sometimes not.
Like I said, I've gone through 4 and still have the problem. My advice, either switch the TF3D look so it's not as noticable in portrait or just switch a totally new ROM with a new TF3D look. It's still going to happen but you'll notice it less. Even on this new Fuze it's still happening. I'm using EnergyROM Mercury right now, and while I still have the problem, it's nowhere near as obvious as before.
Another thing I've noticed that seems to help a bit from time to time is to turn off the screen and plug the charger in. Weird, but it fixes it sometimes. As you also noticed, it only happens when the device is hot. A prime time for it to happen is when you hang up a call.
PryorDaniel said:
Like I said, I've gone through 4 and still have the problem. My advice, either switch the TF3D look so it's not as noticable in portrait or just switch a totally new ROM with a new TF3D look. It's still going to happen but you'll notice it less. Even on this new Fuze it's still happening. I'm using EnergyROM Mercury right now, and while I still have the problem, it's nowhere near as obvious as before.
Another thing I've noticed that seems to help a bit from time to time is to turn off the screen and plug the charger in. Weird, but it fixes it sometimes. As you also noticed, it only happens when the device is hot. A prime time for it to happen is when you hang up a call.
Click to expand...
Click to collapse
Thanks a lot for this information!!
Ill just keep my device and live with it.
I'm flashing to a new room soon, ill see which one i'd like.
Thanks again.
My Gtab has intermittent wake from sleep failures, where it then resets on the next button push. You can tell it's going to fail because you see a flash of the "desktop" the instant you push the button, then it goes dark. Next push gets you the birds!
Is this unique to my tablet?
running Vegan B5.1, but it has happened on other Roms.
Jim
Not unique. I get a similar thing and I'm running VeganTAB b5.1. Usually it doesn't shut right down, but occasionally it does. I also get lag when putting it to sleep. The screen seems to have two stages. First it blacks out for about a second, then it turns off. The only problem is that the digitizer seems to still be active for that one second so if I brush the screen or buttons it wakes up. Not a big issue, but a little annoying.
Prof-KOS said:
Not unique. I get a similar thing and I'm running VeganTAB b5.1. Usually it doesn't shut right down, but occasionally it does. I also get lag when putting it to sleep. The screen seems to have two stages. First it blacks out for about a second, then it turns off. The only problem is that the digitizer seems to still be active for that one second so if I brush the screen or buttons it wakes up. Not a big issue, but a little annoying.
Click to expand...
Click to collapse
Well, the cold resets are annoying, everything I had open is gone. You do not get the resets?
jmdearras said:
My Gtab has intermittent wake from sleep failures, where it then resets on the next button push. You can tell it's going to fail because you see a flash of the "desktop" the instant you push the button, then it goes dark. Next push gets you the birds!
Is this unique to my tablet?
running Vegan B5.1, but it has happened on other Roms.
Jim
Click to expand...
Click to collapse
EXACTLY the same symptoms and problems here too, I've seen this on both the ZPad and TNTL 3.0 ROMs, do I'm pretty sure it's not limited to just the Vegan.
Justin
Turbo4V said:
EXACTLY the same symptoms and problems here too, I've seen this on both the ZPad and TNTL 3.0 ROMs, do I'm pretty sure it's not limited to just the Vegan.
Justin
Click to expand...
Click to collapse
Thanks. I was more concerned it was limited to my hardware! Software can be fixed.
Hi, i had the same issue and changed the endbutton behaviour in spare parts to "home, then sleep". Haven't had the problem since then. Maybe worth a try.
jmdearras said:
Well, the cold resets are annoying, everything I had open is gone. You do not get the resets?
Click to expand...
Click to collapse
I don't get the resets often. They happen, but almost every time it wakes properly it seems to register a second button press and brings up the power menu. Not a big deal because I can just cancel out of it, but it's definitely strange.
DaMan said:
Hi, i had the same issue and changed the endbutton behaviour in spare parts to "home, then sleep". Haven't had the problem since then. Maybe worth a try.
Click to expand...
Click to collapse
Ah, great suggestion DaMan. I think the kernel issues sometimes causing this problem were fixed with our lagfix. But there's still some slightly flaky behavior with the Power button. Changing the Endbutton behavior as you suggested in Spare Parts seems to reduce the tendency for the power button to bring up the shutdown menu when waking up, which I believe is the root cause of this problem.
Everybody should change that setting.
DaMan said:
Hi, i had the same issue and changed the endbutton behaviour in spare parts to "home, then sleep". Haven't had the problem since then. Maybe worth a try.
Click to expand...
Click to collapse
I tried that, but it did not seem to help.
anyone else have any ideas how to fix this annoying problem?
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
Hi,
Yesterday (08/02/2013) I updated my tf700t, everything seemed to be fine after it rebooted, I was playing a game, the battery was low, and it turned off abruptly. I assumed it automatically shutdown because of the battery, so I put it in the dock and plugged in the charger. Several hours later I tried turning it on and nothing. I held down the power button for 8 seconds felt the double vibration, but no display. I tried various combinations of docked/undocked, power cord plugged in, holding the power button for 30-60 sec. etc. but nothing.
Out of curiosity I connected the HDMI to my computer monitor and sure enough, it was there, I could unlock it and everything seems to be functioning fine, just no display. The digitizer seems to work fine, although guessing where things are at is pretty tough.
I think I tried the cold boot, volume up/down (I tried both) plus power, and it didn't make a difference.
In order to do the update I had to flush the DMC Client and CMClient data and cache, I had been getting errors from DMC Client crashing.
Also I'm not certain this is update related, as the tablet had been acting wierd, which is why I did the update. I would press the power button to turn the screen on and nothing would happen, so I'd hold it down longer and the tablet would reboot and finally the screen would come on, or it would come on a few seconds after I pressed the button. I was getting a lot of reboots etc... I thought the update might resolve this.
I'm not sure if the problem is hardware, firmware, or software related.
I'm wondering if when I flushed the DMC and CM Client cache, maybe I deleted the drivers for the display or something?
My options seem to be:
1.) Factory reset by feeling around the digitizer while connected to HDMI
2.) Factory reset via the pinhole
3.) Install new (old) firmware via usb/computer. (the device is recognized by Windows 7 so I think this is doable.)
4.) Send it off to Asus. (would this be free?)
So my questions are:
1.) is there something else I should try?
2.) what order should I do the above in?
*Note: I'd like to save my data somehow.
*Edit: I forgot to mention I was on 4.2.1, no root or anything. Also I bought this in July of '12 so I'm pretty sure it is out of warranty. Any idea how much it might cost to send it off? Perhaps I could replace the LCD myself? I replaced the digitizer/screen on an ipod touch, although I'm sure this LCD is much more expensive and much harder to replace. This is turning into a nightmare. So much for trying to keep my data, now I hoping to keep this from becomming a paperweight.
Thanks.
A bloke at work had this issue. He let it rundown and left it for 3 days. It worked fine again after that.
zpyatt said:
I'm not sure if the problem is hardware, firmware, or software related.
Click to expand...
Click to collapse
If you don't even see the boot logo, it cannot be software related.
Thanks for the replies.
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
zpyatt said:
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
_that said:
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
Click to expand...
Click to collapse
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
zpyatt said:
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
Click to expand...
Click to collapse
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
sbdags said:
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
Click to expand...
Click to collapse
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
zpyatt said:
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
Click to expand...
Click to collapse
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Having the same problem
I am having almost the same problem, except that the tablet screen works when the wall charger is plugged in. THe HDMI display and the digitizer work fine. It is just the tablet's screen dispaly when the charger is unplugged.
sbdags said:
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Click to expand...
Click to collapse
So I didn't have any luck letting it run all the way down.
I contacted customer support, the warranty is only 1 year, but fortunately for this there is an extra 3 months, so I just managed to squeak by, although I'm keeping my fingers crossed.
same problem as you both
i have d same problem well until last week the screen displays when conne ted to wall charger now its all blank but iy works via hdmi, digitizer works fine but all blank, this tf201, does anyone know if i change d whole display it will work?
i already bought the tf701
any suggestions is welcomed and did you get youra to work?
zpyatt said:
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL.
Click to expand...
Click to collapse
I have not seen people mentioning VHDL and verilog for a while, hahaha... It sounds like you are a low level or physical layer programmer. Any way, a firmware is in general a low level program that communicating with the hardware and the software or high level program ( level 7).. If you will, a firmware is a management levels (level 2 and 3). A VHDL is a level 1 which generates a 0's and 1's or mapping the transistors in the FPGA chip for example.... Oh well, it is just my definition...
zpyatt said:
I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
If you can get the output from the HDMI port, it is more likely you have a hardware problems. I think that the problems are your display related hardware. If you really want to troubleshoot your issues, you can look on the mother board to locate all the electrolytic caps and check to see any abnormal signs of those capacitors. Those caps are the one that will blew up first before any others parts go....Good luck...:fingers-crossed:
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.