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
Related
I've tried various different ROM images (including the excellent Dr.Gonzo), and I have this problem with all of them.
When I'm using the phone either with the keyboard in or out, the screen just switches off randomly. If I wait a few seconds (possibly the backlight timer length), then it comes back. Mostly... Othertimes I have to wait a lot longer, but it does always come back.
A reboot sometimes fixes it, but not always - does anything survive a reboot or battery removal?
Anybody else seen anything like this? I have seen a lot of threads about the screen staying on, but not off.
Of course, it could be a hardware fault, but because it's intermittent, it's hard to prove.
Mike
same problem
If you shake the phone can you re-produce this problem? I've never not heard of this being affected by software - you might also want to ensure you're not overclocking it.
Nothing is removed when you do a battery removal or reboot, ensure your connections are all tight and make sure the SIM pins are all making contact and the SIM door closes, apart from that it sounds like a possible bad LCD ribbon.
Shaking it doesn't reproduce the problem.
Once the phone has started doing this, it happens everytime you press a key.
Seems more like a memory leak to me since it always seems to happen after a while of web browsing/email use.
So actually, it looks like it might be a hardware fault.
I think it happens when the device gets warm. After a few minutes with the screen on, keyboard lit up, wifi on, the phone gets pretty warm and that's when the screen seems to go black. Leave to cool and all returns to normal.
Mike
Same issue here, but the screen does not acually go black/blank it just seems that the screen backlight does not turn back on from a standby like state, the phone itself functions but just not able to see whats going on on the screen.
(keyboard lights work fine and come on when expected)
Not sure about the heat theory as it happens (to me) most often right after a call, anything over 30-50 seconds and the backlight problem occurs, when it decides to work again is a matter of luck.
As said before because it's intermittent, it's very hard to prove.
Has anyone who has had this issue, fixed it with a hard reset ?
Very strange ... but also getting very annoying now!
i got the same thing. took it back to warranty and they said nothing's wrong with the phone but i still get this.
I experience the same problems.. it happens pretty random, but every time when you hit a key. I have set all timers to never but the problem is still there.
Running Gonzo 1.1 at the moment, upgraded from guava.. but that didn't solve the problem.
It is getting so annoying now that I am about to throw the s710 in the dustbin
I have had the same problem!
I have turn it back to my provider and no problem now.
i have the same problem with my VOX
apparently, i can still receive phone calls, and do whatever i want with the phone,
but the screen just stays black, its like if you have unplugged your monitor
since i dont have a htc center in my town or anywhere else nearby.
does anyone know a way on how to open the phone, change what need to be changed and correct the problem? im all up for testing if that would resolve this annoying problem :s
cheers everyone
there is a dismantling manual somewhere in this forum. search.
i don't think taking it apart would help you because this is not a physical fault that you can locate.
and i learned that mcel is the retail seller of vox in mozambique. they should be able to help you with service. else just send a mail to htc support and they will guide you.
yes, mcel are the retail sellers, but i tried to go there, and there are no specialists on htc's there,
the thing is, i didnt bought my htc from them, so i can't go there and change for another one
but tks anyway
no problem
but do try to contact htc support by email. they might suggest a way.
I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?
are you trying to say that by desabling the light sensor, the problem might go away?
i would also like to know if it possible to have the baklight on the lowest possible brightness forever, because it seems, on a low brightness the problem might go away
petlof32 said:
I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?
Click to expand...
Click to collapse
I also have this problem with the lightsensor turned off. And also at (as it seems) random moments.
well, even with the light sensor turned off, the problem persisted.
i got my phone to a repair shop of htc's, and they figured out the problem
my phone is now 100% thankfully, the repair man told that the problem was because of bad or malfunctioned circuits, he exchanged them with new ones, and the problem went away,
dont know wich circuits exactly, and he didnt want to tell me, but i suggest anyone having the same problem to try and do the same
probably its a hardware malfunction with these VOX,
its possible since so many times before i've heard about malfunctioned pieces coming out in large quantities for sale.
anyways, cheers everyone, and good luck Portugal in EURO!
I have the same problem. I just noticed that it usually happens when the phone is warm, so if you need to do something on my phone just... take some ice from fridge and put it on back of your mobile. I cant see any more solutions.
Please someone help us!
Update. Problem Solved
Just thought I'd update this thread I started.
I sent the phone back to my dealer (Grapevine in Poole,UK).
A week later, I got a brand new one back from the HTC repair centre.
So far, so good. Looks like the problem's solved.
Mike
Sam problem here,
i called with HTC and they sent them to there repair centre.
[Q] This auto-dim "bug" is completely unacceptable...and is driving me beserk
Basically, if I turn autodim off and turn the brightness up over 50%, the screen shuts off and when I press power to wake, flashes for 1/10 of a second and then turns off. The only way I can use my tablet with brightness over 50% is when it is plugged in.
How has this not been fixed yet? It's got to be a software issue right? This is completely and totally ridiculous.
Chief85 said:
Basically, if I turn autodim off and turn the brightness up over 50%, the screen shuts off and when I press power to wake, flashes for 1/10 of a second and then turns off. The only way I can use my tablet with brightness over 50% is when it is plugged in.
How has this not been fixed yet? It's got to be a software issue right? This is completely and totally ridiculous.
Click to expand...
Click to collapse
I don't have this problem. I use it at 75-100% most of the time on battery.
I have zero idea what it could possibly be. I'm on the verge of returning and just washing my hands of this thing. It's a shame because the Galaxy Tab will definitely be at a higher price point.
exchange it. Something is wrong. No one else is reporting this issue. I've had my ft stock, running Paul's rom and prime, and all the different kernels. No such problem. Sounds like a hardware fault.
crater said:
exchange it. Something is wrong. No one else is reporting this issue. I've had my ft stock, running Paul's rom and prime, and all the different kernels. No such problem. Sounds like a hardware fault.
Click to expand...
Click to collapse
This.
I get that people can get frustrated when something's wrong but the store should always be the first point of call if you've got a problem. If you get it exchanged and it still has an issue, THEN you get to post about it and complain. Even so, at least post in the right forum...
I have this problem and I've seen 2-3 other people with it, so its not that common by the looks of it. I tried to find a solution but I am RMAing mine as there isnt a fix at the moment.
cpalmer98 said:
I have this problem and I've seen 2-3 other people with it, so its not that common by the looks of it. I tried to find a solution but I am RMAing mine as there isnt a fix at the moment.
Click to expand...
Click to collapse
tryed to mimic the issue here and it does not have that issue, its gotta be a bad unit. these things happen , it just sucks when it happens to u
sooo, yeah. my wife has the t959v. the screen cracked months ago, replaced it with one from ebay, works fine. a few weeks ago, it was involved in an accident and needed yet another screen replacement; ergo, back to ebay i go. installed the new screen yesterday, turn it on, all is well. for a bit.
now, the phone isn't currently, nor has it ever been rooted; pure stock tmo us 2.3.6. during boot, the splash screens and boot animation are gorgeous and perfect in appearance. the recovery menu is exactly as expected. android boots as you'd want it to, and then the display will do one of the following:
-work properly (rare)
-automatically turn off, capacitive buttons still lit, touchscreen unresponsive - turning it "off" darkens the cap buttons, turning it back on flashes the screen on for a half-second, then off, with cap buttons still lit (common)
-graphical corruption ("solarized" colors, completely wrong colors, pixel vomit in essence) (fairly common)
-screen tinting, blue most often, followed by pale yellow, then greenish, then red (almost constant)
-screen inversion - the display will show as rotated 180 degrees; grabbing a framecap in ddms shows it right way up. touches are also inverse; you have to touch where the onscreen element would be if it were displayed properly instead of where the element is; e.g. a button on lower-left will display in the upper right, upsidedown, but the screen registers the button when you touch the lower-left portion of the screen. (quasi common, equally infuriating and hilarious)
none of these problems will show up in a screenshot at all.
i can reliably reproduce any of the above by simply adjusting the screen brightness. this will, quite literally, cycle through every possible defective display mode randomly for a split-second before moving on to a different one as long as you move the brightness slider.
MOST of these issues are transient and are either fixed (temporarily) or replaced with a different listed issue if you lock/unlock the display. it feels like a hardware issue what with the solarizing and color horrors, but is acting like a software issue, considering that recovery and boot are perfect and have never displayed any of these issues. i tried gently flexing and stressing the case in areas that might be a weak connection point, but can't get it to bug out that way.
in no way am i suggesting that i didn't screw something royally in the reconstruction stage, but i tore down and rebuilt that phone 4 times with identical results, so i can guarantee it's not some loose ribbon connector or zif socket.
i beg of you, great minds of xda, what the balls did i muck up this time? any hope for a fix? are there different panels, drivers, something?
thanks in advance
OK, if your screenshots appear normal, then your phone appears to be working correctly!
or at least it thinks it is we can conclude that it isn't the rom, kernel, or anything that you can blame the phone for going screwy.
Try buying another screen??
The ribbon connector might be broken?
yeah, these were what i figured what my options were. it just seems odd that the boot process and recovery menus have error-free displays while only the full android os doesnt. oh well, i'll probably just have to make a stink about it on ebay or something.
thanks for reading
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
lumin30 said:
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
Click to expand...
Click to collapse
hell, warranty's void at this point anyway, right? may as well thanks much!
welp, all went well, screen was perfect through the whole heimdall/recovery process, but the problems still exist in the os c'est la vie. at least my wife's phone is finally rooted, i suppose. thanks anyway!
Have you tried opening it back up and reconnecting?
yup, 4 times, but i guess one more wont hurt
[edit]
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
zero01101 said:
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
Click to expand...
Click to collapse
That's interesting and could very well be a hardware problem with the screen. You wouldn't see that in recovery as the OS isn't loaded to mess with the brightness in that mode.
Does it do it on-demand if you mess with the brightness slider?
stephen_w said:
Does it do it on-demand if you mess with the brightness slider?
Click to expand...
Click to collapse
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
zero01101 said:
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
Click to expand...
Click to collapse
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
stephen_w said:
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
Click to expand...
Click to collapse
as fun as that sounds, unfortunately i bet i'll end up just getting my wife a used phone on ebay or somewhere similar and using this one as a development monkey. i was assuming that it wasn't something i could fix but hoping otherwise... yeah, that worked out
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
kristoper said:
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
Click to expand...
Click to collapse
nawp, nothing even close to a solution here i did end up buying my wife a whole new replacement phone and turned the broken one into my api10 development device. for what it's worth, yeah, autobrightness off does help a bit for when the phone is actively displaying content, but after you put it to sleep/screen off and try to turn it back on, it's a crapshoot. for a few horrifying hours, the screen was upsidedown even in recovery/boot animation and would NOT flip back to right-side-up until i ran the battery completely flat.
is no fun, 'tis truth. sorry for your troubles.
Hello all,
I have been using my TF700 for like 3 weeks now. Yesterday suddenly it started to flicker. First I tried cold boot and it turned normal but today it got even worse. It stops randomly and then starts again.
so should i return that or is it just software issue? (dammit i cant out the youtube link)
EDIT: It fades away after like 10-12 seconds, do you think it is software related? Using latest firmware btw.
archonur said:
Hello all,
I have been using my TF700 for like 3 weeks now. Yesterday suddenly it started to flicker. First I tried cold boot and it turned normal but today it got even worse. It stops randomly and then starts again.
so should i return that or is it just software issue? (dammit i cant out the youtube link)
EDIT: It fades away after like 10-12 seconds, do you think it is software related? Using latest firmware btw.
Click to expand...
Click to collapse
"5. Disable "smart dimmer", which is the reason you can see some screen flickering when changing between light and dark backgrounds that many find annoying (described by some as "dynamic contrast", which it resembles):
To disable:
echo 0 > /sys/devices/tegradc.0/smartdimmer/enable
To re-enable echo 1 to the this file or simply reboot.
Be sure to include this in a script so that rebooting won't change it (just make an .sh script with the above line in it, you can use either SManager or system .sh scripts (you can use my simple solution posted here if you don't like editing files yourself). See also jtrosky's hints on changing the brightness settings.
Please note that it may negatively affect your battery life, although with brightness set low it shouldn't be much worse.
All credit goes to those who have found out about it - see this post for details."
http://forum.xda-developers.com/showthread.php?t=1758160
thank you for your reply. it just occured that for example when there's a flicker on the screen, if i turn on auto brightness, it goes away.
the thing is actually i do not know if it is software related or just bad hardware. returning it to amazon would push me in a lot of trouble (like shipping it back, waiting for repair or sth) and the biggest problem that i don't have that much time.
archonur said:
thank you for your reply. it just occured that for example when there's a flicker on the screen, if i turn on auto brightness, it goes away.
the thing is actually i do not know if it is software related or just bad hardware. returning it to amazon would push me in a lot of trouble (like shipping it back, waiting for repair or sth) and the biggest problem that i don't have that much time.
Click to expand...
Click to collapse
I'm under the impression that the autobrightness and the smart dimmer are two different things. The smartdimmer cannot be turned off without doing the edit i pasted above. Try it out and see if it works for you
omg this is totally not normal right? it got even worse(see attached pics)
archonur said:
omg this is totally not normal right? it got even worse(see attached pics)
Click to expand...
Click to collapse
Um yea, I'd get that replaced ASAP
Yep - that's the same kind of graphical glitches that I had before I rebooted and my TF700 was dead (although my glitches weren't quite as bad). After rebooting, my device would just lock up at random places during the startup - sometimes at the first screen (where it says your device is unocked), sometimes at the Asus screen with the circles and sometimes I could even get to the Android lock screen (or even further), but in the end the device just keeps locking up hard. Tried all of the normal "reset" stuff including going back to complete stock, unrooted, etc...
In my case it's definitely a hardware problem, but since I was unlocked, I can't even get warranty service.
Just curious as to your locked state, rooted state or if you were running a custom ROM...
Thanks.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Yep - that's the same kind of graphical glitches that I had before I rebooted and my TF700 was dead (although my glitches weren't quite as bad). After rebooting, my device would just lock up at random places during the startup - sometimes at the first screen (where it says your device is unocked), sometimes at the Asus screen with the circles and sometimes I could even get to the Android lock screen (or even further), but in the end the device just keeps locking up hard. Tried all of the normal "reset" stuff including going back to complete stock, unrooted, etc...
In my case it's definitely a hardware problem, but since I was unlocked, I can't even get warranty service.
Just curious as to your locked state, rooted state or if you were running a custom ROM...
Thanks.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
luckily i haven't unlocked it yet and i am sending it back to amazon for replacement. hope i will get one without problems, but i have some doubts about it after reading hundreds of complainings in forums.
My screen sometimes flickers when playing a game. The game also crashes at this point. I wonder what this issue could be. After a cold boot it usually works fine for a couple of days.
I've only had this tablet for 2 weeks now, but some issues like poor io performance, screen flickering, and the screen flex on certain points on the screen are really annoying me. Maybe I should go to the retailer and ask for a replacement.
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.