Archive for the ‘Sleep Issues’ Category
Unfortunately I have nothing but sleep and wake problems with my brand new Unibook MacBook Pro.
Before anyone asks: Yes, I did install the latest 1.6 firmware update.
The latest incident:
I just unplugged my MBP from my external screen and the power. I did not close the lid first. What I do is that I wait for the menu bar to move from the external screen to the MBP screen. Then I close the lid. I moved to another room and opened it. No problem and I worked on it for a bit. Then I closed it and made a coffee. Now I’m back and open the MBP and the screen stays dark. The white power led did turn off. There is no way to get the screen back on.
Only a reboot works. I lose my workspace and some open files. Lame. What is this? Some Wintel piece of crap?
For the record: I run no strange software on this Mac. This is my main development machine and I depend on it daily. So I do my best to keep it as standard as possible. It’s a default 10.5.5 install with the most non-standard thing on it being LaunchBar.
This is getting so annoying that I am now thinking about selling this Unibody MacBook Pro and getting the previous model. This is pretty much an unworkable situation for someone like me who moves around a lot.
Due to very unfortunate circumstances the Lame Leopard had to get a replacement for his good old Early 2007 MacBook Pro. So what did he get? A nice new Late 2008 MacBook Pro. The UniBody. All Hail Jonathan Ive.
To be honest, the UniBodyBookPro is seriously beautiful. It really is a very nice design and the new keyboard is just great.
Unfortunately the new MacBook Pro is also full of fail.
Here are a bunch of mostly annoying things that I have encountered in the first two weeks:
- The Trackpad – It is loud and it misses clicks. Ok the missing clicks issue has been resolved with a recent patch. But really, it shows how less Q&A this whole MacBook has had. I noticed the missing clicks within the first 5 minutes. During the initial OS X install. Why did Apple not notice this before the damn thing was shipped. Maybe they thought it was an acceptable issue. Odd.
- Sleep Problems – Leopard truly was a complete disaster with regard to sleep and wake. It seems with this New MacBook Pro we are back to square one. For example, I just noticed that my new MacBook Pro was still turned on in my Crumpler bag. It was hot as hell. I could barely touch it in the corner where the GPU or CPU lives. Why is this so difficult to get right? Why does it this break every time they introduce new hardware? Do we really have to wait another five Leopard releases again before sleep is going to properly work on the new MacBook Pro? Lame. Lame. Lame.
- External Display Problems – So in the home office I have this nice 24″ Dell screen. It is awesome and when I bought it it was like half the price of a similar Apple screen. It worked great on the old MacBook Pro. On the New MacBook Pro the screen does not wake up properly from power-save mode. I frequently have to either reboot the New MacBook Pro, sleep/wake the New Macbook Pro or disconnect/connect the screen to get it out of the power-save mode. This is sooo annoying
- Audio Input Problems – Many times when I plug in a headphone or external speakers, the New MacBook Pro does not recognize this and will happily continue to play audio on the built-in speakers. The problem goes away when I plug the speakers in again. I’m not sure if this is because of bad quality plugs. But I know for sure that I never had this issue with the Old MacBook Pro.
- Mini Proprietary DisplayPort – The Old MacBook Pro had a completely standard DVI port and it did not require any special cables to hook it up to video equipment. With the new MacBook Pro Apple broke this good habit and fragged it up by introducing their own stupid non-standard and proprietary variant of the video port. This time it is called Mini DisplayPort and there are of course zero cables or non-Apple devices to be found to support this new proprietary Apple standard. I had to put down 30 dollars to get a Mini-DisplayPort to DVI Adapter. My Dell screen does have DisplayPort but of course it is the standard connector and there are no Mini To Standard cables to be found anywhere. They simply do not exist. Lame.
It’s a good reminder to never buy Apple’s v1.0 hardware. Unfortunately I had not choice this time. Otherwise I would have waited till the next revision.
This is just so frustrating …
I’m typing this posting on the iMac because the MacBook Pro with 10.5.2 won’t wake up.
I simply opened the lid as I have done a million times but even though I heard the Mac power on and the white pulsing led on the front turned off, the screen stayed dark.
After a few minutes I gave up and closed the lid again, hoping it would go back to sleep again so that I can give it another try. The white LED on the front is now on, not pulsing and I can hear the Mac do stuff.
The screen is still dark. And now the fans are working at full speed too.
I’m hoping for a little miracle because I have a whole bunch of apps and windows open. But I’m afraid I’ll have to reboot this piece of crap again.
As I said in a previous posting, the MacBook Pro seems to be the number one problematic Apple portable at the moment with regards to sleep and wake. I’ve never had sleep/wake problems of this scale on any other Apple portable.
For the record: this is a plain MacBook Pro with a standard install of 10.5.2. No kernel extensions, no crazy software. I basically just use Terminal.app, Safari and some other very standard apps.
This is a rant about a 2000 EURO laptop that does not work correctly.
I’ve been using Apple computers since 1980 and Apple laptops since ’97 or so when I had a PowerBook 150. I’ve had many iBook models, PowerBooks in all shapes and sizes and now I have the last model of the MacBook Pro 15″. The Late 2007 ‘Santa Rosa’ model.
In all these years I have never owned an Apple laptop that was so incredibly badly supported by Apple’s own operating system. The MacBook Pro in combination with Leopard is a true compatibility disappointment. It feels like a flakey Windows XP install on crappy hardware. Which is crazy since they are both made by the company that we love so much.
Let me explain the issues that I have.
I have constant sleep and wake problems with this MacBook Pro. I know that the MBP now uses full hibernate where it can take a LONG time before it goes to sleep. My problems are different though.
- Sometimes it does not wake up when I open the lid.
- Sometimes it wakes up but the screen stays dark.
- Sometimes I close the lid and I can see that the backlight stays turned on. Forever.
- Sometimes the backlight goes off when I close the lid and the I see the Apple logo flashing every couple of minutes.
- Sometimes I hear the CD drive making it’s purr sound when the lid is closed.
- Many times the ony way to get control back is to reboot. Sucks bigtime.
I’ve seen sleep/wake problems with all other models since the iBook but never so structural as with the MacBook Pro running Leopard. This is simply embarrassingly bad. It used to be one of those great features. Now I am afraid to open my MacBook because there is a good change I will have to reboot.
I have described my keyboard problems in detail on this blog. Summarized the problems are: first keystroke has no effect after some period of idle time. Keyboard functionality disappears completely.
Apple put out a fix for this in the form of a software update. I think this proves that they simply fragged up support for their own hardware. Unfortunately the fix does not work for many people. Many folks on Apple’s discussion forum are reporting that they still have the above issues, even after installing the update.
It’s INSANE that so many people are still having issues and that there is no proper fix.
‘Jumpy’ Mouse Issues
What I mean with Jumpy here is that you move the cursor for a little bit but instead it jumps all over the screen.
The problem is probably related to the wireless connection since I have heard from a lot of people that the mouse is jumpy when the MacBook Pro is looking for a wireless network to connect to. When it is connected to a wireless network of decided that no network can be found then the jumpy mouse problem goes away.
That by itself is already a big problem since your MacBook Pro is basically unusable during that time. And it can sometimes take a really long time before it find a usable network, so all that time you are basically waiting behind a non-working computer. But even more annoying, for many people the mouse stays jumpy even after succesfully connecting to the wireless network.
It actually just happened to me: I was at the Copenhagen airport to fly home and when I opened my MacBook Pro the mouse got all jumpy and stayed that way. Now back at home in Amsterdam I have to reboot and close 8 terminal windows with work and editors with documents open to get rid of this problem. Extremely Lame
This is clearly a Leopard software problem since I never had this issue with 10.4 on this same MacBook Pro.
I’m not alone. Just check Apple’s own MBP forum or the forums on any Apple fan site. Leopard has been out for months, this hardware for much longer. I can only think of one reason why the MBP has so many issues with Leopard: they never did proper testing and quality assurance since everybody in Cupertino was too busy building new products.
Prices go up, quality goes down. These are really bad signs.
I’m so tired of this sh*t. *Again* I have to reboot my MacBook Pro because it woke up after four tries of closing and opening the lid with a bouncy mouse pointer as a result. This is only the .. fourth time this week that it happened.
Someone at Apple ought to lose his or her job for completely messing up Leopard compatibility on the MacBook Pro.
Again my MacBook did not go to sleep and again it was almost melting in my nice Crumpler bag.
Leopard certainly has more sleep problems than Tiger. With Tiger I could just close the MacBook put it in my bag and run off. I never had any problems with that. Leopard is a different story. I simply don’t trust it anymore, so I wait until the white LED on the front starts pulsing before I put the Mac in my bag. Which really sucks.
This might be a little oldskool for some people.
Do you remember that when the old original Mac (128K/512K/Plus) read a floppy disk that there was not enough time to deal with all the interrupts for the mouse movement? And that the mouse would jump around the screen?
The same thing just happened on my MacBook Pro after a couple of failed tries to wake the Mac up from sleep.
The hardware must have been confused or so because ‘top’ did not show any process sucking up all CPU time. I tried to sleep/wake the MacBook, turn the Airport off and on but nothing helped. After a reboot it is fine again.
I just experienced my first Leopard kernel panic. I’m traveling with the Leopard and when I was checking in at the hotel (WOW THE VIEW OF THIS ROOM!) in I noticed that my bag was super hot. I took my Mac out .. it was still turned on, showing the oh so friendly multi-lingual kernel panic screen and COOKING .. it was STEAMING HOT and I actually burned my finger while holding the power button down to shut it off.
I guess some things never change. Sizzling Lame.