Previous 1 129 130 131 132 133 Next 2,972 Replies Latest reply: Jun 22, 2015 8:15 PM by Pretzelcuatl Go to original post Branched to a new discussion.
  • AtterKing Level 1 Level 1 (10 points)

    There's far too much speculation going on here now.  Silly, petty arguments arising.  I do understand the frustration, paying a lot of cash for a premium device only to find it has a fault out of the box.  I'm in the same boat here!  So;

     

    1. If you're not happy and within the 14 day rule, send it back and get your cash back (that's your entitlement and your choice)

     

    or

     

    2. Accept that Apple have acknowledged this and given a statement that they're aware of the issue (http://support.apple.com/kb/TS5296?viewlocale=en_US&locale=en_US). Wait for their formal announcement and follow the instructions to fix.  This could be a simple software fix or hardware recall.  Eitherway there's no point in worrying or panicking about it as ultimately the problem will be resolved.

     

    I would stress however that if you're affected by this issue, whether it's on the new 13" rMBP or any other device you must report the problem to Apple immediately.  Then choose either of the options above.

     

    If you choose option 2, there's no point in becoming embroiled in the 'will they have to open it up' or 'will the software fix simply mask the hardware issue'.  Let's just wait and see, then re-group and continue the discussion from there.

  • Oli.S72 Level 1 Level 1 (0 points)

    sTronic wrote:

     

    lol I don't understand why so many people is just trying to fool themselve..

     

    its clearly some hardware problem in 13 inch MBP.

     

    There is not many or nearly NONE iMac, MBP Air, 15inch MBP user is complaining here... and they are selling a lot too!! they all use haswell, same OS X, only 13 inch get massive complain.

     

    Sorry to say, but you have no clue about what you're talking about.
    "same OS X" is wrong, since it is a different build.
    sTroll would be a better name than sTronic for you, I guess

  • Niels P. Level 1 Level 1 (0 points)

    sTronic wrote:

     

    the reason you have to shut the lid for 60 seconds is to completely power off the keyboard/track pad and then power it on again. the keyboard/trackpad module is completely out of control at that moment, its very likely a hardware issue because the OS X software out of control and can not power it on again!

     

    No, it's not. Putting the system to sleep and opening it up again does the same thing as keeping a USB device plugged in: it forces a wake event on the USB bus. The problem has everything to do with the USB system and nothing with the keyboard/trackpad themselves.

     

    I have to wonder why you keep posting such nonsense. Pretending to know what's happening when you clearly don't. Looking at your previous posts you don't even know how to lookup the OS/X build number or properly quote a message. Go troll somewhere else.

  • Obstladen Level 1 Level 1 (0 points)

    As someone who wanted to buy a new rMBP the next weeks i called the apple shop hotline - to ask if the ones they sell  n o w  do still have this error.

     

    The CallCenter-Guy said he heard the first time of this 'freezing bug'... and recommended me to call the support-hotline.

     

    Apple can not even tell me if the product they're selling is working? ...

  • Oli.S72 Level 1 Level 1 (0 points)

    civictyper88 wrote:

     

    Hi all , I need your advise . Currently I just got my macbook pro 13 inch Late 2013 (2.4Ghz , 8GB , 256GB ) and it has experienced the same problem too . However currently i using a usb 2.0mouse to stop the pc from hang . I have read this forum and noticed many people returned their pcs for refund from apple however I am unable to refund as there is no such policy here in Asia , I am thinking to exchange my pc from apple but after reading this thread previous comments , changing it does not solve anything . Help , I am disappointed as this is the first apple pc I obtained and paid so much for this pc . (added apple care as well ) Not sure this can be of any help .

    No need to panic.
    Very likely, your hardware is 100% okay and there will be a software fix for the problem.
    If it would turn out that your MacBook has a hardware problem, you still have nothing to fear as Apple will exchange it, if it can not be solved by firmware or driver.

    Just stick to your MacBook and wait, all will be good.

  • azbe Level 1 Level 1 (0 points)

    No need to panic.
    Very likely, your hardware is 100% okay and there will be a software fix for the problem.
    If it would turn out that your MacBook has a hardware problem, you still have nothing to fear as Apple will exchange it, if it can not be solved by firmware or driver.

    Just stick to your MacBook and wait, all will be good.

    Please tell me what makes you think that? Again, I spoke with Apple Senior Tech advisor who told me it's a hardware issue. Returned it within an hour. Why would you stick with a faulty $1500+ hardware? No offense, but why would you encourage others to get into that situation as well?

    We're just trying to make ourselves believe that it's software related...no it's not!

  • alkamin Level 1 Level 1 (0 points)

    People need to calm down.

     

    THE CONSOLE IS NOT AN ERROR LOG (repeat as many times as you need to).

     

    It is a record of sytem events.  While some errors will show up there, the messages that appear there are not limited to errors.  The wake message that is being talked about is not an error but an indication the computer recieved input from the touchpad or whatever and chose to wake the system based on that.

  • jjalemany Level 1 Level 1 (0 points)

    Hey guys,

    I don't want to claim having a solution before hard testing what I'm going to share because many people thought they had and finally return here saying it doesn't work... but I think It's worth trying.

     

    ¿Have you tried REPAIRING PERMISSIONS? I'm giving intensive use on my machine and seems solved, ¿can you please try it out?

     

    Hope this helps!

  • shadowku Level 1 Level 1 (0 points)

    I'm a little concerned as to why the 13" rMPB has a different build to begin with while every other Mac from this iteration to all of the previous iterations that can run Maverick have another build.

     

    I think this could be a hardware issue where the actual behaviour is different from the expected behaviour and Apple is giving the 13" rMBP software workarounds. I'm not exactly thrilled by the thought but I'm going to hold out on getting my new Macbook.

  • fusionboy Level 1 Level 1 (0 points)

    I disabled the power settings "Put hard disk to sleep" and I haven't had the issue happen since. It's been over 24hrs, fingers crossed.

  • civictyper88 Level 1 Level 1 (0 points)

    Thank you . i am hoping so . other than this issue , macbook is just fabulous .

  • jtice Level 1 Level 1 (0 points)

    I assume all or most of these are the models prior to the recent updated model, announced late October and available as of November 1st. Has anyone determined if this issue persists or went away with these latest models?

  • Supreem Level 1 Level 1 (5 points)

    jtice wrote:

     

    I assume all or most of these are the models prior to the recent updated model, announced late October and available as of November 1st. Has anyone determined if this issue persists or went away with these latest models?

    Can you elaborate on where, when and who announced that the 13" rMBP model was updated on the 1st of November??

  • 甲壳熊 Level 1 Level 1 (0 points)

    I've encountered the problem exactly as what u described three times this week .

    and I dont know how to solve it , for the power key is unable to force the computer to be restarted too...