Archive for the ‘Display’ Category

Nothing but sleep/wake problems with the new Unibody MacBook Pro

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.

Lame.

Unibody MacBook Pro and Screen Flicker

I discovered something new and annoying recently: my external screen, attached to the new Unibody MBP, flickers sometimes. Not constantly though, its more like the whole screen does a super quick off/on every couple of minutes. Could this be a first sign of the video controller failing? Or maybe these are DisplayPort problems? Has anyone else seen this?

The New MacBook Pro is Full of Fail

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.

External Display on a Leopard MacBook Pro Issues

I move from office to office and I usually connect an external screen and keyboard & mouse to my MacBook Pro. Leopard has several annoying issues with this:

  • Windows don’t move to the new main screen – When I connect a nice 23″ display to my MacBook Pro I usually make sure that that display becomes the main one. Leopard remembers this and it correctly moves the menu bar from the built-in display to the external display. What it does not do is to move all windows to the new main display. They are still waiting on the built-in display. I’m pretty sure Tiger did this correctly.
  • Applications dont recognize the new main display – After I connect the external display and have for example dragged Mail.app from the built-in to the external display (because of the above bug) it starts doing something weird: when I open a message the new message window is opened on the built-in display, not the external display that is now the main screen! I thought Mail.app might be confused so I quit and start it. But it still happens. Same with Terminal.app. New terminal windows appear on the built-in non-main display.

I’m pretty sure these issues are new to Leopard. I’ve never had these frustrating things with Tiger.