Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Snow Leopard: Expose choppy?

what a LOAD of garbage!!!
get this:
SAME computer, two system, one on RAID 0 one on second half of 2y old drive.
One updated Leopard to 10.6.2, cluttered and ****ed up.
one Fresh installed Snow Leopard, 10.6.2.

THE FRESH ONE HAS CHOPPY Quick Look!!
and the Updated one works as smooth as a whistle. :( what the hell could be the problem? Block size of Raid partition? i think i made it 16kb. i dont believe that should affect SL QuickLook animation.

this is so damn annoying how could this happen? the system is 2 weeks old!
 
well, i reinstalled the system and now its A-OK. no choppiness. looks like system got corrupted somehow.

anyway, all is good, im happy now.
i cant blame apple, its obviously a usermistake if reinstall cured it. so, so far, Snow Leopard: works like a charm. :)
 
Problem still remains with choppy expose.

With 3 or more minimized windows there’s absolutely no transition, just jerkiness, usability is affected cuzz you don’t know where have all the windows came from…

The problem especially persists when there’s a Skype video open and you try to invoke Expose which makes it come down to a CRAWL!
 
I did, Ploki, but it didn't help much. In Leopard it was silky smooth. I tested it on both version of the new MacMini with SL and the same Expose behavior was apparent - especially with minimized windows the transitions are non-existent.
 
Makker's solution worked perfectly for me.
Mac Book Pro 6,1 April 2010 with nvidia GT 330M. There are reports from the youtube comments that it worked with other macbook models and mac minis.

Here's a summary of the solution (the video has some parts hard to see):

1. Open System Profiler (top left Apple Icon > About This Mac > More Info)
2. check Software > Extensions. AppleGraphicsPowerManagement.kext will probably be there.
3. in Terminal:

cd /System/Library/Extensions
sudo mv AppleGraphicsPowerManagement.kext/ AppleGraphicsPowerManagement.disable

4. Download and run Kext Utility:
http://cvad-mac.narod2.ru/Kext_Utility/

wait a minute while Kext Utility fixes something about kext permissions, then quit.

5. reboot

6. check System Profiler again. AppleGraphicsPowerManagement.kext should not be there anymore.

7. In System Preferences > Energy Saver, change Display Sleep to 1 minute.

8 Wait 1 minute for screen to sleep.

9. Tap a button to wake up from display sleep. Return your Energy Saver> Sleep Display time to whatever value you want.

Tada you're done. I believe this fix forces the nVidia to work all the time and at some higher setting. (My MBP has switchable graphics which are now apparently disabled. I also turned off Cody Krieger's excellent gfxCardStatus app before doing any of this.)
 
Just an update on battery performance. With the Nvidia card now fully enabled, I was getting about 4.5-5 hours max battery life (with wifi on and screen about half brightness.) That was a lot lower than before.

BUT Cody Krieger's excellent gfxcardstatus app solves that problem:

http://codykrieger.com/gfxCardStatus

because it allows you to select the integrated intel graphics or the nvidia card. Integrated intel graphics are NOT affected by makker's fix. With the intel graphics selected in gfxcardstatus, battery life is once again 8-10 hours when I want it.
 
Easy fix to choppy expose and other graphics 10.6.7

THERE IS A MUCH EASIER FIX: This may work for some and i suggest you attempt it first before the other complex solutions posted out there. RESET YOUR PRAM on your mac and the slow expose problems will go away. (worked for me and some others after attempting other much harder and complex solutions)

1. locate your apple, option, "P" and "R" keys
2. Reset your system and hold all four keys down and the same time (prior to the apple welcome or spinning wheel)
3. Continue to hold down the keys and the system will reset four (4) times.
4. On the fourth reset release the keys and your system will restart normally with the PRAM reset.

I hope this will help your expose choppiness; it fixed mine and others I know! If this works for you share with others as i have found this was the most logical and simple fix with out deleting files that will affect your system!

QVZ:apple:
 
waterhead said:
Just an update on battery performance. With the Nvidia card now fully enabled, I was getting about 4.5-5 hours max battery life (with wifi on and screen about half brightness.) That was a lot lower than before.

BUT Cody Krieger's excellent gfxcardstatus app solves that problem:

http://codykrieger.com/gfxCardStatus

because it allows you to select the integrated intel graphics or the nvidia card. Integrated intel graphics are NOT affected by makker's fix. With the intel graphics selected in gfxcardstatus, battery life is once again 8-10 hours when I want it.
Click to expand...

Are you sure the Intel isn't affected by this fix? Because I get lowered projected battery times with the Intel.
 
karohan said:
Are you sure the Intel isn't affected by this fix? Because I get lowered projected battery times with the Intel.
Click to expand...

Hi Karohan sorry for the late reply.

Using gfxcardstatus app to force the mbp to use the intel integrated graphics, I'm able to get 9-10 hour battery life. This is about the same as before using Makkker's fix. So I don't think the fix affects how the mbp uses the integrated graphics. Since the whole idea of the fix is to pump up the nvidia graphics performance, this seems to makes sense. But ymmv of course.

Cheers
 
waterhead said:
Hi Karohan sorry for the late reply.

Using gfxcardstatus app to force the mbp to use the intel integrated graphics, I'm able to get 9-10 hour battery life. This is about the same as before using Makkker's fix. So I don't think the fix affects how the mbp uses the integrated graphics. Since the whole idea of the fix is to pump up the nvidia graphics performance, this seems to makes sense. But ymmv of course.

Cheers
Click to expand...

Thanks for the reply. I'm not sure how you are able to get the same battery life on Intel (let alone 9-10 hours). I usually got around 5-6. But after deleting the .kext I got 3-4. This was consistent to settings I found in the kext itself. There are power settings in there for the integrated card. However, I was able to manually modify the kext to only remove power saving for the Nvidia, so I was able to achieve my desired results eventually haha. To do that you would have to go into the Info.plist, find the setting section corresponding to the dedicated GPU, and change the power setting for all load levels to be the highest (power setting 0).
 
karohan said:
Thanks for the reply. I'm not sure how you are able to get the same battery life on Intel (let alone 9-10 hours). I usually got around 5-6. But after deleting the .kext I got 3-4. This was consistent to settings I found in the kext itself. There are power settings in there for the integrated card. However, I was able to manually modify the kext to only remove power saving for the Nvidia, so I was able to achieve my desired results eventually haha. To do that you would have to go into the Info.plist, find the setting section corresponding to the dedicated GPU, and change the power setting for all load levels to be the highest (power setting 0).
Click to expand...

Hi, bringing back this topic.
I was wondering how exactly you managed to do this.
Once I deleted the kext graphics got much smoother - like they used to be, although battery life dropped as well using both integrated graphics and GeForce 330m, 3 hours max.
What I have in the kext regarding the 330m is this:
Code: 
<key>MacBookPro6,1</key>
			<dict>
				<key>LogControl</key>
				<integer>0</integer>
				<key>Vendor10deDevice0a29</key>
				<dict>
					<key>BoostPState</key>
					<array>
						<integer>0</integer>
						<integer>1</integer>
						<integer>2</integer>
						<integer>3</integer>
					</array>
					<key>BoostTime</key>
					<array>
						<integer>0</integer>
						<integer>0</integer>
						<integer>0</integer>
						<integer>0</integer>
					</array>
					<key>Heuristic</key>
					<dict>
						<key>ID</key>
						<integer>0</integer>
						<key>IdleInterval</key>
						<integer>250</integer>
						<key>SensorOption</key>
						<integer>1</integer>
						<key>SensorSampleRate</key>
						<integer>4</integer>
						<key>TargetCount</key>
						<integer>1</integer>
						<key>Threshold_High</key>
						<array>
							<integer>57</integer>
							<integer>70</integer>
							<integer>83</integer>
							<integer>100</integer>
						</array>
						<key>Threshold_High_v</key>
						<array>
							<integer>1</integer>
							<integer>3</integer>
							<integer>98</integer>
							<integer>100</integer>
						</array>
						<key>Threshold_Low</key>
						<array>
							<integer>0</integer>
							<integer>68</integer>
							<integer>75</integer>
							<integer>94</integer>
						</array>
						<key>Threshold_Low_v</key>
						<array>
							<integer>0</integer>
							<integer>2</integer>
							<integer>4</integer>
							<integer>99</integer>
						</array>
					</dict>
					<key>control-id</key>
					<integer>17</integer>
				</dict>
Could you point me in the right direction here?
Thanks
 
Sure, you will first need to get Property List Editor, which I think is included in the OS X Developer Tools suite. That will allow you to edit .plist files more easily. After that, you will have to edit the values for throttling corresponding to the 330m in the plist. The threshold low and high values should be above 100, except for level 0, which is the highest level. That should be within the 0-100 range, and that will make only level 0 (no throttling) be active at all times.
 
karohan said:
Sure, you will first need to get Property List Editor, which I think is included in the OS X Developer Tools suite. That will allow you to edit .plist files more easily. After that, you will have to edit the values for throttling corresponding to the 330m in the plist. The threshold low and high values should be above 100, except for level 0, which is the highest level. That should be within the 0-100 range, and that will make only level 0 (no throttling) be active at all times.
Click to expand...
Thanks, karohan!
Works perfectly now
Battery life 7+ hours on Intel graphics
To anyone who might be interested my kext values for the 330m look like this:
Code: 
<key>MacBookPro6,1</key>
			<dict>
				<key>LogControl</key>
				<integer>0</integer>
				<key>Vendor10deDevice0a29</key>
				<dict>
					<key>BoostPState</key>
					<array>
						<integer>0</integer>
						<integer>1</integer>
						<integer>2</integer>
						<integer>3</integer>
					</array>
					<key>BoostTime</key>
					<array>
						<integer>0</integer>
						<integer>0</integer>
						<integer>0</integer>
						<integer>0</integer>
					</array>
					<key>Heuristic</key>
					<dict>
						<key>ID</key>
						<integer>0</integer>
						<key>IdleInterval</key>
						<integer>250</integer>
						<key>SensorOption</key>
						<integer>1</integer>
						<key>SensorSampleRate</key>
						<integer>4</integer>
						<key>TargetCount</key>
						<integer>1</integer>
						<key>Threshold_High</key>
						<array>
							<integer>57</integer>
							<integer>170</integer>
							<integer>183</integer>
							<integer>200</integer>
						</array>
						<key>Threshold_High_v</key>
						<array>
							<integer>1</integer>
							<integer>103</integer>
							<integer>198</integer>
							<integer>200</integer>
						</array>
						<key>Threshold_Low</key>
						<array>
							<integer>0</integer>
							<integer>168</integer>
							<integer>175</integer>
							<integer>194</integer>
						</array>
						<key>Threshold_Low_v</key>
						<array>
							<integer>0</integer>
							<integer>102</integer>
							<integer>104</integer>
							<integer>199</integer>
						</array>
					</dict>
					<key>control-id</key>
					<integer>17</integer>
				</dict>
 
Fix for Nvidia 320M

Does anyone know if this fix will work for Macbook Pro 2010 13 inch model with Nvidia 320M integrated graphics?
and is it safe to use this?
About how much will it reduce the battery life by (since there is only one graphic card)?

Even the 320M is choppy in 10.6.8, things such as expose and scrolling, animations. I tried reinstalling the OS but no luck :( . The only time when the expose goes super smooth is when playing a youtube video in Chrome. This maybe because the GPU is forced to increase its clock speed. Thanks for your answers!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back