being able to toggle resolutions with RDM has been such a delight.
still 1536x960 90% of the time, but periodically 1680x1050 is fun
still 1536x960 90% of the time, but periodically 1680x1050 is fun
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Scale 1680x1050 on rMB without an app
- Thread starter thadoggfather
- Start date
- Sort by reaction score
Did you do "Check System Preferences->Displays->Profiles->Color LCD->Open profile->Line 17"
(First post of this thread, first sentence)
In my case, i had to change the "DisplayProductID-a028"-file instead of the "DisplayProductID-a027"-file to get the effort.
I came from here: https://forums.macrumors.com/thread...tion-performance.1893032/page-2#post-22317146
Apologies if this is not the right thread to ask (then, which is it?), the question:
Which is the absolute lowest resolution El Capitan (the OS) supports? The reason I'm asking is, I might want to administer a headless Mac Mini via a jumbo phone or a smallish tablet. Thanks!
Apologies if this is not the right thread to ask (then, which is it?), the question:
Which is the absolute lowest resolution El Capitan (the OS) supports? The reason I'm asking is, I might want to administer a headless Mac Mini via a jumbo phone or a smallish tablet. Thanks!
This is not the right thread. You could have posted a new thread on the Mac mini forums, however, on my Mac mini, the lowest I can set is 1024x640. I doubt very much that the OS would be usable at this resolution.
Sorry for the big bump but I remember doing this on my original RMB but can't get it done on my new RMB. When I try to copy and paste the altered A027 file back into the folder it doesn't let me. Any suggestions?
Look at the bolded part at the very end of the original post , disable rootless.
Should take care of it
I tried this just now and still won't let me overwrite the file. I also tried what another member suggested and boot into recovery and enter a string into terminal but I can't seem to figure out how to enter the command. My harddrive is simply named Macintosh HD (haven't changed it) but the command is written all weird in the post macintosh\ hd so I'm not exactly sure what I'm doing incorrectly.
Had to do the procedure again today, because the recent OSX update did throw away my beloved screen-resolution:
Just boot in recovery mode, open the terminal and type (without quotes) "csrutil disable", then type "reboot". Then do the stuff described by thadoggfather in this first post of this thread (ignore the bold written stuff). After you tested the new resolution and all works fine, boot again in recovery mode, open the terminal and type (without quotes) "csrutil enable", then type "reboot". - Done -.
Just boot in recovery mode, open the terminal and type (without quotes) "csrutil disable", then type "reboot". Then do the stuff described by thadoggfather in this first post of this thread (ignore the bold written stuff). After you tested the new resolution and all works fine, boot again in recovery mode, open the terminal and type (without quotes) "csrutil enable", then type "reboot". - Done -.
Thanks! Worked perfectly and much easier than the other line of code that I was trying to do.
I'm still on 10.11.2 
[doublepost=1458786166][/doublepost]
Sorry I couldn't be of help, if I do update I'm glad to have that solution in place glad it worked out in the end
[doublepost=1458786166][/doublepost]
Sorry I couldn't be of help, if I do update I'm glad to have that solution in place glad it worked out in the end
Finally made leap to 10.11.4, and 1536x640 and 1680x1050 and RDM functionality remained in place,
Figured why not, one of the nice things of OS X is I can get updates unlike iOS where I have to wait for jailbreak and then some before taking the plunge. Still not update trigger happy / hasty due to always questioning software QC, but I think after letting the dust settle its not the worst idea.
woo, glad to not need to do any more thinking
Figured why not, one of the nice things of OS X is I can get updates unlike iOS where I have to wait for jailbreak and then some before taking the plunge. Still not update trigger happy / hasty due to always questioning software QC, but I think after letting the dust settle its not the worst idea.
woo, glad to not need to do any more thinking
I realize this is a thread for how to do it yourselves and I respect that--I used to do all this file editing myself. But then I discovered Quickres and never looked back. Definitely easy and doesn't use a ton of resources nor does it have a memory leak as someone warned about earlier in this thread. Also, it doesn't get jacked up when you do OSX updates. (And I'm in developer program and update a lot.) 1400x900 is my personal favorite res on the rMB. 1680 makes things pretty small. 1920 is really tiny text.
I'm curious if it still works with the 2016 rMB. I surely hope so since I'm buying one. If someone can test that, I'll be happy to know.
Thanks!
Awesome thanks !Yes it does. I just set this up using this thread over the weekend
I have always used QuickRes with my 15" MacBook Pro. I have it also installed on my rMacbook. Here's the thing, QuickRes will give you 1680x1050, but it will not be HiDPI. In order to get that higher res, you will need to follow the guideline referred to in the first post of this thread. Once doing that, you will get a much cleaner and sharper display at 1680x1050. Like so many here, I'm actually using 1536x960.
[doublepost=1465288866][/doublepost]
Yes, it does work as others have verified. One thing of note though, you need to be sure that the display file you are modding matches your display. I found out the hard way... I figured my display was a027, like most everyone else, except no matter what I tried, the mod would not take. So... I went to System Preferences|Displays and went to Color, and then selecting Color LCD as the profile, then selected Open Profile, and then scrolled all the way to the bottom to select "Apple Display Make and Model Information". This reveals the Manufacturer, in my case 00000610, and the Model, in my case 0000A028. So... as it turned it out, I was modding the wrong file all along. So, I modded the a028 file, and I was in business.
I hope this clarification may save someone a little time.
In Terminal run this command:
ioreg -lw0 | grep IODisplayPrefsKey
It will output something like this:
"IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-610-a028"
At the end of the string you will see some hex values, in this case 0x610 and 0xa028.
Your DisplayVendorID is 0x610 and your DisplayProductID is 0xa028.
I was looking for a terminal command to make this easier. Thank you for providing it!