macOS 10.14 Mojave on Unsupported Macs Thread

[ASentientBot]

This may be way off, but I just noticed something kind of interesting related to the transparency glitches.

When you login to an account in light mode, the menu bar appears as follows:
- No menu bar, just the SystemUIServer (clock, etc) on the right side, directly on the desktop
- Menu bar appears in dark mode, with proper transparency
- Menu bar appears in light mode, with grey appearance

Now, this might be a kind of radical conclusion to draw from that. But imagine for a second, the dark mode effect appears (mostly black, with slight transparency). Then, the light mode draws correctly, but over that. So it's a translucent white menu bar, on top of a translucent black menu bar, on top of the desktop. Would that not produce the grey color we see?

This seems crazy. But now, look at the brightness HUD overlay. In dark mode, it's quite transparent -- you can clearly see the colors of the desktop underneath. In light mode, it's supposed to be the same (only white, of course). But instead, it's a grey color. But you can still see the colors underneath if you have a very colorful wallpaper (ex. "Chroma 2"). Just extremely faintly. Would that not be exactly what you'd expect of wallpaper + dark overlay + light overlay? Less transparency, and grey.

I don't have any hard facts to back this up. But it's just an idea that fits the observations strangely well.

I guess what would follow from this, is the glitch may not be caused by NSVisualEffectView at all. It may be some result of drawing both the dark and light effects on top of each other?

Again, all guessing. But it might be worth investigating (or proving it wrong).

A good way to test this would be to completely disable the dark mode code and then try light mode. Not sure how to do this, however.

Edit: There is a serious hole in this theory. The light mode brightness HUD can be darker than the dark mode one. Nevermind. I'm wrong!

 

[thegurgz]

I’m stumped. I cannot install anything on an APFS volume on my MBP 5,5. Here’s all my history:

1: Downloaded and ran APFS Rom Patcher, everything went successfully.
2: Formatted my Mojave disk to APFS, booted in with no issues.
3: Attempted to install DP7 from DP6 through software update, ran post install (force rebuild), afterwards failed to boot. Installation removed the option to boot into recovery partition from the Mojave disk, but in diskutil list it was listed in the container of the APFS along with “VM” and “Preboot”, all unmounted.
4: Erased, moved all my files, reformatted to APFS, tried to update again, same result, no recovery disk.
5: Erased, installed DP7 on HFS+. Created a partition for testing APFS.
6: Converted empty disk to APFS, installed DP7, ran post install. Would not boot in, nor had a recovery disk. New booting option, “EFI Boot”, which when booted into would stop when the bar reached the end.
7: Erased APFS testing partition, reformatted to HFS+. No more “EFI Boot” option. Converted back to APFS, still no “EFI Boot” option.

And this is where I stand. I have come to the conclusion that it is not the native installed causing the install issues, since I tried to also clean install from a patched USB installer and the same result occurred. I don’t know if running the APFS boot rom patcher again would fix anything, but I am open to any suggestions. Thank you!

 

[TimothyR734]

Also, Dark Mode isn't just dark-as-in-desaturated. In order to prevent clashes, the system samples what's behind a window, including the system wallpaper. Then, it subtly tints the window — and controls because of their slight translucency — based on the average colors, and mixes that with a base gray, so that the color temperature of the window matches the rest of the environment and your wallpaper. It's a dynamic process that updates as you move windows around, so all the elements on your screen always feel part of a cohesive whole.

(If you hate the idea of tinting, you can pick the graphite accent "color", which forces no tinting at all.)

Vibrancy, which is what Apple calls the bright, saturation boosted, translucent effect applied to things like app sidebars, is also optimized in Dark Mode to maintain legibility. Basically, gray background elements take the place of white so that the contrast stays high, even in lower opacity levels.

Glyphs, or the monochrome icons used throughout interfaces, have also been adjusted so that they maintain weight legibility on dark backgrounds. Often, they've been redrawn to replace outlines with solid forms and details with knockouts.

From more.com MacOS Mojave:The secrets behindDark Mode

 

[Aletancredo]

Also, Dark Mode isn't just dark-as-in-desaturated. In order to prevent clashes, the system samples what's behind a window, including the system wallpaper. Then, it subtly tints the window — and controls because of their slight translucency — based on the average colors, and mixes that with a base gray, so that the color temperature of the window matches the rest of the environment and your wallpaper. It's a dynamic process that updates as you move windows around, so all the elements on your screen always feel part of a cohesive whole.

(If you hate the idea of tinting, you can pick the graphite accent "color", which forces no tinting at all.)

Vibrancy, which is what Apple calls the bright, saturation boosted, translucent effect applied to things like app sidebars, is also optimized in Dark Mode to maintain legibility. Basically, gray background elements take the place of white so that the contrast stays high, even in lower opacity levels.

Glyphs, or the monochrome icons used throughout interfaces, have also been adjusted so that they maintain weight legibility on dark backgrounds. Often, they've been redrawn to replace outlines with solid forms and details with knockouts.

From more.com MacOS Mojave:The secrets behindDark Mode

Hello, Is there avaiable new macOS mojave for beta public or just for developers? Thanks...

 

[TimothyR734]

Hello, Is there avaiable new macOS mojave for beta public or just for developers? Thanks...

If you have the Apple Public beta access utility installed check your software update

 

[arqueox]

This may be way off, but I just noticed something kind of interesting related to the transparency glitches.

When you login to an account in light mode, the menu bar appears as follows:
- No menu bar, just the SystemUIServer (clock, etc) on the right side, directly on the desktop
- Menu bar appears in dark mode, with proper transparency
- Menu bar appears in light mode, with grey appearance

Now, this might be a kind of radical conclusion to draw from that. But imagine for a second, the dark mode effect appears (mostly black, with slight transparency). Then, the light mode draws correctly, but over that. So it's a translucent white menu bar, on top of a translucent black menu bar, on top of the desktop. Would that not produce the grey color we see?

This seems crazy. But now, look at the brightness HUD overlay. In dark mode, it's quite transparent -- you can clearly see the colors of the desktop underneath. In light mode, it's supposed to be the same (only white, of course). But instead, it's a grey color. But you can still see the colors underneath if you have a very colorful wallpaper (ex. "Chroma 2"). Just extremely faintly. Would that not be exactly what you'd expect of wallpaper + dark overlay + light overlay? Less transparency, and grey.

I don't have any hard facts to back this up. But it's just an idea that fits the observations strangely well.

I guess what would follow from this, is the glitch may not be caused by NSVisualEffectView at all. It may be some result of drawing both the dark and light effects on top of each other?

Again, all guessing. But it might be worth investigating (or proving it wrong).

A good way to test this would be to completely disable the dark mode code and then try light mode. Not sure how to do this, however.

Edit: There is a serious hole in this theory. The light mode brightness HUD can be darker than the dark mode one. Nevermind. I'm wrong!

Are you trying to say that light mode and dark mode are the same mode, but the light is overlayed by a dark tone Everytime we change do dark mode? Like a filter?

 

[flygbuss]

@jackluke I downloaded the CoreBrightness from your link its missing the .framework at the end but it didn't add nightshift and I think dosdude1 one is still working on night shift as it was removed from the Patch Updater. I even replaced the CoreBrightness framework from my iMac 9,1 which Night does appear in the displaypref.pane with the one on my MacBook 5,2 no luck. So maybe Night shift will only work on APFS formatted drives

You have to open the CoreBrightness.framework and go to the specified folder and replace the CoreBrightness inside.
Check out jacklukes link again please.


[doublepost=1534806072][/doublepost]https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-162#post-26298190

 

[TimothyR734]

You have to open the CoreBrightness.framework and go to the specified folder and replace the CoreBrightness inside.
Check out jacklukes link again please.

View attachment 776979
[doublepost=1534806072][/doublepost]https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-162#post-26298190

Thank you that worked !!!!

 

[David403]

Thanks for the advice. However, in the EFI disk, it only shows this:
View attachment 776967

... well it was worth checking but at least you know you don't have the APFS script from High Sierra. So it's not that.

I hope someone else can help you get APFS Mojave beta drive to be recognized and be bootable - I'm out of ideas, sorry.

 

[TimothyR734]

The new icon for the DVD player

 

[nekton1]

First, a usable recovery disk is NOT created by this method so forget it.
Second, your step 3 implies that you can install DP6 on the APFS formatted disk, since you are trying to install DP7 over DP6. Is this correct?
Instead of bashing head against wall with repeated DP7 UPDATE attempts, why not build a DP7 or DP8 USB FULL installer and run the full installer on a freshly partitioned and erased disk?
IIWY, I'd try this.
1. Build DP8 USB installer using Mojave 1.1.2 patcher from Dosdude1 and using the Tools menu to download fresh full Mojave DP8 installer.
2. Start Mac from USB installer and use Disk Utility to partition/erase SSD (I assume it is an SSD and not HDD) to APFS.
3. Return to Terminal in USB installer and run diskutil list to check structure of SSD with correct APFS container and Preboot volumes. etc., (see screenshot).
4. Run Mojave DP8 USB installer.
5. If install completes, restart and run post-install for correct model and remember to select clear cache option and reboot.
6. Let us know what happens.

I’m stumped. I cannot install anything on an APFS volume on my MBP 5,5. Here’s all my history:

1: Downloaded and ran APFS Rom Patcher, everything went successfully.
2: Formatted my Mojave disk to APFS, booted in with no issues.
3: Attempted to install DP7 from DP6 through software update, ran post install (force rebuild), afterwards failed to boot. Installation removed the option to boot into recovery partition from the Mojave disk, but in diskutil list it was listed in the container of the APFS along with “VM” and “Preboot”, all unmounted.
4: Erased, moved all my files, reformatted to APFS, tried to update again, same result, no recovery disk.
5: Erased, installed DP7 on HFS+. Created a partition for testing APFS.
6: Converted empty disk to APFS, installed DP7, ran post install. Would not boot in, nor had a recovery disk. New booting option, “EFI Boot”, which when booted into would stop when the bar reached the end.
7: Erased APFS testing partition, reformatted to HFS+. No more “EFI Boot” option. Converted back to APFS, still no “EFI Boot” option.

And this is where I stand. I have come to the conclusion that it is not the native installed causing the install issues, since I tried to also clean install from a patched USB installer and the same result occurred. I don’t know if running the APFS boot rom patcher again would fix anything, but I am open to any suggestions. Thank you!

 

[thegurgz]

First, a usable recovery disk is NOT created by this method so forget it.
Second, your step 3 implies that you can install DP6 on the APFS formatted disk, since you are trying to install DP7 over DP6. Is this correct?
Instead of bashing head against wall with repeated DP7 UPDATE attempts, why not build a DP7 or DP8 USB FULL installer and run the full installer on a freshly partitioned and erased disk?
IIWY, I'd try this.
1. Build DP8 USB installer using Mojave 1.1.2 patcher from Dosdude1 and using the Tools menu to download fresh full Mojave DP8 installer.
2. Start Mac from USB installer and use Disk Utility to partition/erase SSD (I assume it is an SSD and not HDD) to APFS.
3. Return to Terminal in USB installer and run diskutil list to check structure of SSD with correct APFS container and Preboot volumes. etc., (see screenshot).
4. Run Mojave DP8 USB installer.
5. If install completes, restart and run post-install for correct model and remember to select clear cache option and reboot.
6. Let us know what happens.

View attachment 776990

I did try a DP7 clean install on an APFS in step three, still a no go. I just wrote DP8 to a usb, so I will install it on my main Mojave partition, then start messing with APFS again tonight. I’m not sure what you mean by “clear cashe option”, are you talking about in the post install? I think the button you’re thinking of is “force cashe rebuild” but I could be wrong.

 

[Luckygreek]

That was relatively painless, ran Software Update, reboot, finish installation, reboot into USB Patch, ran patch, reboot and system updated. I don't think it went this smooth since 3rd or 4th beta. UI glitches still prevail, although it doesn't appear to be as pronounced as was with DP7. DP6 still being the best in terms of no UI glitches, ie: trails. At least somewhat usable on 2010 iMac. Also just running over an hour, overheating not as bad as with DP7.

 

[pkouame]

I did try a DP7 clean install on an APFS in step three, still a no go. I just wrote DP8 to a usb, so I will install it on my main Mojave partition, then start messing with APFS again tonight. I’m not sure what you mean by “clear cashe option”, are you talking about in the post install? I think the button you’re thinking of is “force cashe rebuild” but I could be wrong.

Well, if you tried all our recommendations and DP7 (cause DP8 won't probably change this experience) doesn't boot - and your APFS diskutil list looks like mine and @nekton1 's ....

"Once you have eliminated the impossible, whatever remains, however improbable, must be the truth." — Spock, Star Trek

There must be something wrong with your flashed APFS rom. I would suggest begging @dosdude1 for help.

• Did you save the original rom binary? Sorry, if don't remember every step in this saga. I think dude can recommend a way to regen the original rom. Starting back at square 1, may be a possibility.
• Are you booting to a recovery partition at least?

 

[Macschrauber]

I investigated a bit more about those "unsupported" Low End GPUs on Mac Pro 3.1:

another Mac Pro 3.1, another Apple HD5870 1GB - same dragging window glitches with dp7 and dp8
same Mac Pro 3.1, a HD6870 1GB - same dragging window glitches with dp7 and dp8
another Mac Pro 3.1 and a HD4870 2GB - blazing fast window dragging without any glitches with dp7 and dp8

the interesting part is that this HD4870 had same false 30 bit colours - BUT not had those dragging glitches.

It IS fast, I can move a full screen window around without any delay.

That's my first test to see if a GPU has its driver loaded or not.

Maybe there's a half way accelerating, frame buffer wise, I dunno, but dont tell me those AMD GPUs dont have any drivers activated. I installed DP1 manually and there was no acceleration, all GUI was like in slow motion - so there is some driving now.

Is it the 2GB VRAM in my 4870 in this particular GPU ? I do some more testing when I get hands on a "standard" 4870.

And as told, running in safe boot cures the glitches on those GPUs I tested on 3.1 (5870,6870) with DP7 and DP8.

DP6 was fine.

update: running Cinebench R15 on Mojave / HD4870 with 44fps...

 

[pkouame]

That was relatively painless, ran Software Update, reboot, finish installation, reboot into USB Patch, ran patch, reboot and system updated. I don't think it went this smooth since 3rd or 4th beta. UI glitches still prevail, although it doesn't appear to be as pronounced as was with DP7. DP6 still being the best in terms of no UI glitches, ie: trails. At least somewhat usable on 2010 iMac. Also just running over an hour, overheating not as bad as with DP7.

Really. DP6 glitched less or not at all for you? In terms of window trails...

 

[TimothyR734]

Well, if you tried all our recommendations and DP7 (cause DP8 won't probably change this experience) doesn't boot - and your APFS diskutil list looks like mine and @nekton1 's ....

"Once you have eliminated the impossible, whatever remains, however improbable, must be the truth." — Spock, Star Trek

There must be something wrong with your flashed APFS rom. I would suggest begging @dosdude1 for help.

• Did you save the original rom binary? Sorry, if don't remember every step in this saga. I think dude can recommend a way to regen the original rom. Starting back at square 1, may be a possibility.
• Are you booting to a recovery partition at least?

I Love that quote from Star Trek a big fan

 

[Luckygreek]

Really. DP6 glitched less or not at all for you? In terms of window trails...

Pretty much non-existent in DP6 and some of the prior updates, DP7 everything went haywire.

Edit:
At least with this version, I can move around windows, get the "trails" however click Desktop and window redraws. DP7 that was not possible. Command W to close the window as there were too many trails could not determine which window was which.

 

[pkouame]

I investigated a bit more about those "unsupported" Low End GPUs on Mac Pro 3.1:

another Mac Pro 3.1, another Apple HD5870 1GB - same dragging window glitches with dp7 and dp8
same Mac Pro 3.1, a HD6870 1GB - same dragging window glitches with dp7 and dp8
another Mac Pro 3.1 and a HD4870 2GB - blazing fast window dragging without any glitches with dp7 and dp8

the interesting part is that this HD4870 had same false 30 bit colours - BUT not had those dragging glitches.

It IS fast, I can move a full screen window around without any delay.

That's my first test to see if a GPU has its driver loaded or not.

Maybe there's a half way accelerating, frame buffer wise, I dunno, but dont tell me those AMD GPUs dont have any drivers activated. I installed DP1 manually and there was no acceleration, all GUI was like in slow motion - so there is some driving now.

Is it the 2GB VRAM in my 4870 in this particular GPU ? I do some more testing when I get hands on a "standard" 4870.

And as told, running in safe boot cures the glitches on those GPUs I tested on 3.1 (5870,6870) with DP7 and DP8.

DP6 was fine.

If "...running in safe mode cures the glitches" it means : running without kernel extensions cures the glitches. That is a significant finding. Are you sure about that? (not being facetious ... just curious and intrigued)

 

[Macschrauber]

If "...running in safe mode cures the glitches" it means : running without kernel extensions cures the glitches. That is a significant finding. Are you sure about that? (not being facetious ... just curious and intrigued)

Yes, tried that a few times, but just about the dragging window glitches on the 5870 in dp7. I will tell tomorrow with dp8, it's 3 am here, need a nap now

 

[pkouame]

I’m stumped. I cannot install anything on an APFS volume on my MBP 5,5. Here’s all my history:

1: Downloaded and ran APFS Rom Patcher, everything went successfully.
2: Formatted my Mojave disk to APFS, booted in with no issues.
3: Attempted to install DP7 from DP6 through software update, ran post install (force rebuild), afterwards failed to boot. Installation removed the option to boot into recovery partition from the Mojave disk, but in diskutil list it was listed in the container of the APFS along with “VM” and “Preboot”, all unmounted.
4: Erased, moved all my files, reformatted to APFS, tried to update again, same result, no recovery disk.
5: Erased, installed DP7 on HFS+. Created a partition for testing APFS.
6: Converted empty disk to APFS, installed DP7, ran post install. Would not boot in, nor had a recovery disk. New booting option, “EFI Boot”, which when booted into would stop when the bar reached the end.
7: Erased APFS testing partition, reformatted to HFS+. No more “EFI Boot” option. Converted back to APFS, still no “EFI Boot” option.

And this is where I stand. I have come to the conclusion that it is not the native installed causing the install issues, since I tried to also clean install from a patched USB installer and the same result occurred. I don’t know if running the APFS boot rom patcher again would fix anything, but I am open to any suggestions. Thank you!

Hey - in addition to my previous post - I just thought of something: what kind of SSD are you running (make, model and interface)?

 

[Luckygreek]

If "...running in safe mode cures the glitches" it means : running without kernel extensions cures the glitches. That is a significant finding. Are you sure about that? (not being facetious ... just curious and intrigued)

That's odd, I can't boot into Safe mode, I get ø, I wanted to test your theory. This requires some poking under the hood.

I can boot in Recovery or Verbose but not Safe Mode???

 

[TimothyR734]

Dark and Light mode in safe mode

 

[nekton1]

Reading what you posted, in step 3 you wrote:

3: Attempted to install DP7 from DP6 through software update,...

As fas I can guess, that is not a clean full install. Build a USB full installer as described for DP8, partition/erase SSD as APFS, check volumes and install DP8 as described.

Yes, Force Cache Rebuild or something like that.

I did try a DP7 clean install on an APFS in step three, still a no go. I just wrote DP8 to a usb, so I will install it on my main Mojave partition, then start messing with APFS again tonight. I’m not sure what you mean by “clear cashe option”, are you talking about in the post install? I think the button you’re thinking of is “force cashe rebuild” but I could be wrong.

 

[thegurgz]

Reading what you posted, in step 3 you wrote:

3: Attempted to install DP7 from DP6 through software update,...

As fas I can guess, that is not a clean full install. Build a USB full installer as described for DP8, partition/erase SSD as APFS, check volumes and install DP8 as described.

Yes, Force Cache Rebuild or something like that.

Huh, must have made a typo. I meant step 6. “Converted empty disk to APFS, installed DP7”. Clean install and still a no-go, but will try DP8.
[doublepost=1534816319][/doublepost]

Hey - in addition to my previous post - I just thought of something: what kind of SSD are you running (make, model and interface)?

Not an SSD at all. I have a newer (though not technically mine) mid 2014 MBP accessible to me, so I never decided to invest in an SSD for my old MBP, even though they are around 40 dollars. Running a hitachi HDD, could be the issue.