The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    W3J - screen doesn't recover after "Turn off monitor: xx min"

    Discussion in 'Asus' started by mike105, Nov 13, 2006.

  1. mike105

    mike105 Notebook Guru

    Reputations:
    0
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    15
    My LCD turns off after 15 min (that's how i have it set up) if I'm not using my W3j however it doesn't turn back on when i click with mouse or do anything. Computer is working fine since I can turn on/off wireless (BT), I can hear a music etc. The only way to get it back on, is to reboot.
    I use Omega drivers and NHC...

    Help is highly appreciated cause this is really annoying me! I'm quite positive that it is a software issue but have no idea how to fix it :confused:
     
  2. WuHT

    WuHT Notebook Consultant

    Reputations:
    0
    Messages:
    197
    Likes Received:
    0
    Trophy Points:
    30
    close the lid and open it up.
     
  3. mike105

    mike105 Notebook Guru

    Reputations:
    0
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    15
    tried it before... didn't help
     
  4. mike105

    mike105 Notebook Guru

    Reputations:
    0
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    15
    my problem is evolving lol, i was actually using computer and suddenly LCD turned off and when i closed the lid and opened it again, the screen turned on... but why is that happening!? :(
     
  5. CalebSchmerge

    CalebSchmerge Woof NBR Reviewer

    Reputations:
    1,126
    Messages:
    2,395
    Likes Received:
    2
    Trophy Points:
    55
    Go into the options for the screen saver and for the power options, set it so you don't go to the welcome screen when you resume. I think this is what has fixed it before. I have had similar problems with the V6j, but its fixed now.
     
  6. mike105

    mike105 Notebook Guru

    Reputations:
    0
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    15
    you mean "prompt for password when computer resumes" ??
    if so then it is unchecked
     
  7. robohgedhang

    robohgedhang Notebook Evangelist

    Reputations:
    78
    Messages:
    657
    Likes Received:
    13
    Trophy Points:
    31
    Hmmmmm..... what version of Omega driver are you using? I bet it's the Omega that's based on the catalyst ver 6.9?
     
  8. mike105

    mike105 Notebook Guru

    Reputations:
    0
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    15
    i'm using Omega 6.7
     
  9. CalebSchmerge

    CalebSchmerge Woof NBR Reviewer

    Reputations:
    1,126
    Messages:
    2,395
    Likes Received:
    2
    Trophy Points:
    55
    Did you check BOTH of the options I suggested? Also, are these official Asus drivers?
     
  10. mike105

    mike105 Notebook Guru

    Reputations:
    0
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    15
    Yes
    I got them for www.omegadrivers.net so I don't think that they are "official" but they work for other without any problems
     
  11. qnz

    qnz Notebook Enthusiast

    Reputations:
    0
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    15
    i have the same problem too. i also use omega 6.7. my solution is to hit fn+f8 so that it projects to an external monitor. hit it 2 more times and it should project onto LCD only, and you should get ur screen back. annoying ya, but the only solution i have found.
     
  12. mikez

    mikez Notebook Evangelist

    Reputations:
    18
    Messages:
    372
    Likes Received:
    0
    Trophy Points:
    30
    Other Asus series have this problem too. I'm regretting getting an Asus... Too expensive while new tech comes out every three months or so...
     
  13. mike105

    mike105 Notebook Guru

    Reputations:
    0
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    15
    is this a hardware or software problem??

    Despite this screen issue I still love my W3j :)
     
  14. battlemage

    battlemage Notebook Consultant

    Reputations:
    7
    Messages:
    123
    Likes Received:
    0
    Trophy Points:
    30
    its a software problem and ASUS has not been able to address it properly yet. this issue comes up every few weeks and people always have one "hack" or another way to get around the problem. A actual "solution" is going to have to come from ASUS. I propose we start some sort of lobbying to try and get ASUS to fix this issue once and for all! Any resellers (justin, danny, eddie, ken?) interested in helping us out? It worked for the x1600 graininess fix so it could work for this issue as well.
     
  15. CalebSchmerge

    CalebSchmerge Woof NBR Reviewer

    Reputations:
    1,126
    Messages:
    2,395
    Likes Received:
    2
    Trophy Points:
    55
    It is a software problem, as mikez said, it affects a lot of Asus notebooks, and there is a fix, it might be the video drivers, or another setting I can't remember at this point. I would do some searching, someone did some extensive work to fix this problem, so check what they found.
     
  16. battlemage

    battlemage Notebook Consultant

    Reputations:
    7
    Messages:
    123
    Likes Received:
    0
    Trophy Points:
    30
    Ive been following this issue for a while and I havent seen a real fix yet, only workarounds. If there is indeed a fix, I would be really curious to know what it is.
     
  17. CalebSchmerge

    CalebSchmerge Woof NBR Reviewer

    Reputations:
    1,126
    Messages:
    2,395
    Likes Received:
    2
    Trophy Points:
    55
    I suppose I should amend what I said to workaround, but I consider it a fix, since it is taken care of easily and once you do that, no more problems.
     
  18. Genaro

    Genaro Notebook Guru

    Reputations:
    0
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    15
    I was also having this problem on a regular basis. After I uninstalled the Power4Gear, it stopped. I think the monitor itself is just getting turned off, so when you put it into standby, when it comes back on it turns the monitor on again. You can also fit Fn+F8 twice to turn it back on.

    Never had the issue again for weeks, then suddenly started having a real similar problem, BUT ONLY if I leave the laptop on for a long period, as in over night and a full day, once I restart, the problem stops again. This problem never lets me turn it back on no matter what I try, so I have to turn it off.
     
  19. mujtaba

    mujtaba ZzzZzz Super Moderator

    Reputations:
    4,242
    Messages:
    3,088
    Likes Received:
    501
    Trophy Points:
    151
    I had posted an answer for this problem before.
    FN+F8 Does not turn the LCD on/off it dims(reduce the brighteness) to the least level.
    So FN+F8 Does not help with this problem.
    The best is to prevent the windows from turning off the monitor.
    Best Regards,
    Mujtaba ;)
     
  20. Genaro

    Genaro Notebook Guru

    Reputations:
    0
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    15
    Fn+F8 doesn't dim mine down at all, just says "LCD only" when I press it. I always assumed it had some control between an external monitor and the lappies LCD?
    Fn+F7 appears to completely turn off the back light, is that what you are referring to?

    Curious, Is there anyone who has uninstalled Power4Gear that still has this problem?
     
  21. mikez

    mikez Notebook Evangelist

    Reputations:
    18
    Messages:
    372
    Likes Received:
    0
    Trophy Points:
    30
    Me, I still have this issue but my monitor rarely off so I'm not to concern about it.

    This is not a fix whatsoever.
     
  22. reicaden

    reicaden Notebook Consultant

    Reputations:
    0
    Messages:
    102
    Likes Received:
    0
    Trophy Points:
    30
    I have the W7J, and i am still having this problem :(

    If i close the lid, and then later in the day open the lid and try to resum, the computer resumes, but the screen remains black. I can hear functions, and i can tell it is on, but no screen.

    If i close the lid, again. (to stand-by) and then open it once more, boom, problem solved.

    its irritating, any fixes yet? a search on google and this site has shown me nothing in the way of a fix :(

    I just turned off the password on resume feature, lets see how that goes. :p any help appreciated...

    sincerely,

    ReiCaden
     
  23. e36'n

    e36'n Notebook Enthusiast

    Reputations:
    0
    Messages:
    32
    Likes Received:
    0
    Trophy Points:
    15
    I had this problem, it went away, then came back somehow. I have an Asus W7J

    To fix it the second time I set screen saver ON in the Power4gear settings. Fixed it for me. The first time I had to adjust the power properties in the control panel to match the Power4Gear settings.

    I can live with the screensaver for now.
     
  24. e7fendy

    e7fendy Notebook Enthusiast

    Reputations:
    0
    Messages:
    40
    Likes Received:
    0
    Trophy Points:
    15
    can anyone tell me how to fix this problem?
    i have this problem too...
    really annoying..
     
  25. jabba1900

    jabba1900 Notebook Geek

    Reputations:
    0
    Messages:
    96
    Likes Received:
    0
    Trophy Points:
    15
    I had this problem on my A8Js, but I managed to fix it. I honestly can't remember what I did. I did some Google searches and ended up on a forum for Toshiba, where Toshiba owners had the same problem. They had links for a fix that took care of the problem.

    Sorry I couldn't be of more help, but at least I can confirm that this can be fixed. I can also confirm that it is not exclusively an Asus problem. Keep searching, and I'm sure you'll find that fix somewhere. I'll post a link here if I happen to come across it somewhere.