Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Hello,
I have been using OCLP on my mid 2014 rMBP since the first Ventura release. Nearly everything has been perfect so far.

However lately I have noted that there is no way for the apps to ask for permission, when they for instance have to access videocamera, disk, and so on.

Is there a way to solve this annoying issue? Please help, thanks,
Daniele
You can use the Tccplus utility to apply a fix for each app affected. Search "Github Tccplus" for a download link.
The link DeeVeeDee mentioned, is a version of OCLP, now in beta, but working fine on many computers quite fine, that was developed recently specifically to enable the AMFI function necessary to run VM apps like VWWare, etc. It also fixes that function where apps used to ask for permission to use the camera or microphone, which was disabled for 13.3 etc. (not sure which OS versions were affected). Using that version of OCLP, apps now ask for and are granted permission as they should, so your issue may (most likely will) be fixed if you install that version.
Read the instructions carefully and you should be good.
 
  • Like
Reactions: dcaccount
You can use the Tccplus utility to apply a fix for each app affected. Search "Github Tccplus" for a download link.
The link DeeVeeDee mentioned, is a version of OCLP, now in beta, but working fine on many computers quite fine, that was developed recently specifically to enable the AMFI function necessary to run VM apps like VWWare, etc. It also fixes that function where apps used to ask for permission to use the camera or microphone, which was disabled for 13.3 etc. (not sure which OS versions were affected). Using that version of OCLP, apps now ask for and are granted permission as they should, so your issue may (most likely will) be fixed if you install that version.
Read the instructions carefully and you should be good.
Thanks.

I have already used tccplus to grant access to Teams. Now I need to grant access to Apple Notes to an app called Exporter.

I my iMac natively running Ventura the permission is under the automation tab.

I cannot understand how I can proceed in this case.

Please help, thanks
 
Thanks.

I have already used tccplus to grant access to Teams. Now I need to grant access to Apple Notes to an app called Exporter.

I my iMac natively running Ventura the permission is under the automation tab.

I cannot understand how I can proceed in this case.

Please help, thanks
In your first post you said you were using a mid 2014 rMBP, now it's an iMac. If you put your hardware in your signature (Click on your name in the top pane) it would be easier to understand what your situation is. What iMac is that?
Unfortunately, I don't know whaat you should do to get Notes working with that "exporter" app.
Maybe someone else can pitch in.
 
In your first post you said you were using a mid 2014 rMBP, now it's an iMac. If you put your hardware in your signature (Click on your name in the top pane) it would be easier to understand what your situation is. What iMac is that?
Unfortunately, I don't know whaat you should do to get Notes working with that "exporter" app.
Maybe someone else can pitch in.
Actually I have a new iMac running Ventura natively and this is not the issue.

The issue I have is with the mid 2014 rMBP I was mentioning.

Thanks!
 
FYI: I mentioned this in an earlier post. This was fixed in 0.6.6, but with 0.6.7 (AMFIPass Public Beta Test) the problem is back again:
Shortcuts: Here I noticed that on the wired USB Apple Keyboard, which is not directly connected to the MacPro 3.1 but to the Mac via the USB 3 hub of my monitor, certain shortcuts (e.g. crtl-eject for the Restart, Sleep, Cancel and Shut Down dialog) or ctrl-alt-cmd-eject for direct shutdown do not work reliably. Sometimes it works, but sometimes only the drawer of the optical SATA drive opens. This was also never a problem in Monterey.
 
Hello,
I have been using OCLP on my mid 2014 rMBP since the first Ventura release. Nearly everything has been perfect so far.

However lately I have noted that there is no way for the apps to ask for permission, when they for instance have to access videocamera, disk, and so on.

Is there a way to solve this annoying issue? Please help, thanks,
Daniele
please see this video by Jessie that takes care of this problem
 
I don't use Safari or Firefox, only Brave <https://github.com/brave/brave-browser/releases/tag/v1.51.118> (scroll down for various versions) and sometimes ungoogled chromium <https://github.com/ungoogled-software/ungoogled-chromium-macos/releases/>
Try one of these?
I've tried Brave as well and same problem, it only happens with youtube, even when playing in window mode (so not full screen) and 720p (so not 1080p nor 1440p). I don't know why this happens, I think the graphics card and processor should be more than enough to handle it. It did not happen with my previous 2013 iMac which had a lesser processor and graphics card...
 
EFI generated by OCLP amfipass beta2 can be used with latest OCLP nighly builds. I have disabled the AMFIPass kext in Kernel -> Add and added amfi=0x80 in NVRAM -> boot-args before installing latest OCLP build. After, revert the changes and all good: latest build + AMFI enabled.
 
  • Like
Reactions: perez987
How?

This would overwrite the existing EFI, meaning removing the AMFIPass.kext

Manually add AMFIPass.kext back in the kext folder and config.plist?
You need to mount EFI, use a plist editor and follow my steps to modify the config.plist. But, with all do respect, if you don't understood for the first time what I meant, it is safer to wait for the release.
 
I installed clean 13.4 with OCLP 0.6.6, after setup the user I did not apply a root patch.
Then installed Xcode and tested problems with GPUCompoler - works ok.
Installed OCLP 0.6.7 - Xcode works.
Applied the root patch - Xcode stopped working.

But without root patch mbp11, 3 has another issue with screen resolution, performance, etc.

I tried to build a custom OCLP without PrivateFramework patches, but have problems on Python build step.
Uhm, yesterday I did test it with all the 13.3.x versions and when I remove or not install the root patches XCode debugger works. Screen resolution is as set but it is slow and sometimes images are not shown. To choose from both evils, I did instal the patches.

My question; whats inside the root patches what causes the debugger crashes? Is that avoidable? Is it a little part that can be separately turn off or on.
 
I could, but I'd be doing you a disservice and would be repeating what has already been discussed in this thread (and then reposted again and again). Best to read this thread starting here.

All sounds clear, my only concern is that AMFIPass is in beta and I use the laptop for business and I would like to avoid any risk.

I have then checked the linked video and it is super clear.
The problem is that the app I need to use (Exporter to back up notes) needs to access to Notes and I have not found a way to grant access to notes using tccplus
 
@dcaccount I've never used tccplus for Notes, but if you do need to use tccplus for Notes, you can find the Bundle Identifier of Notes (or any app) by showing package contents of the app in the Applications folder and inspecting the app's Info.plist:

Screenshot 2023-05-31 at 6.29.22 AM.png
 
"my only concern is that AMFIPass is in beta"
As you said, "I have been using OCLP on my mid 2014 rMBP since the first Ventura release" and in a very real sense, every version of OCLP is a beta, because it is in constant development, in order to cover all of the various hardware variations and Apple's constant revisions. If you read the special thread on Discord (link on that page DeeVeeDee posted) related to the AMFIPass version of OCLP, many people have reported success. You could try it, in order to see if the Notes related backup app works. If it doesn't, simply reinstall OCLP 0.6.6 or 0.6.7n.
Very little risk involved - as long as you have a good backup plan implemented.
 
The Apple Compressor refuses to work with the message.

Apple Compressor does not support macOS virtual installation.

Does anyone have an idea to fix this?

MacOS 13.4
OCLP 0.66
 

Attachments

  • Screenshot at May 31 16-40-11.png
    Screenshot at May 31 16-40-11.png
    311.3 KB · Views: 56
Last edited:
  • Like
Reactions: macinfo
Uhm, yesterday I did test it with all the 13.3.x versions and when I remove or not install the root patches XCode debugger works. Screen resolution is as set but it is slow and sometimes images are not shown. To choose from both evils, I did instal the patches.

My question; whats inside the root patches what causes the debugger crashes? Is that avoidable? Is it a little part that can be separately turn off or on.
The binaries necessary to fix graphics acceleration on 13.3+ needs to be extracted from the dyld cache, there is a big problem with the extractor that breaks lldb, that's why it works without root patches. There is a workaround but it's not recommended since you'd need to extract those binaries by yourself and each of them is around 2gb.
 
The Apple Compressor refuses to work with the message.

Apple Compressor does not support macOS virtual installation.

Does anyone have an idea to fix this?

MacOS 13.4
OCLP 0.66
Probably (?) this happens because Compressor explicitly checks if the environment is a VM: and with the new spoofless OCLP’d Mac approach, it indeed in some way is. So, ideally there should be a way to let Compressor see a real, native Mac environment also with OCLP: don’t know if and how this can be done, however; or disable the check in the app (?)…

Edit: It could perhaps also have something to do with the recent changes in Ventura 13.3+ and OCLP, who knows: anyway, as said below, a fix is in the works… :cool::)
 
Last edited:
  • Like
Reactions: hvds and macinfo
The binaries necessary to fix graphics acceleration on 13.3+ needs to be extracted from the dyld cache, there is a big problem with the extractor that breaks lldb, that's why it works without root patches. There is a workaround but it's not recommended since you'd need to extract those binaries by yourself and each of them is around 2gb.
Thank you for the explanation.
 
Thanks! Reset PRAM worked, much better than entering recovery mode to enable SIP.

Was already using the first boot menu procedure for Catalina and Windows (non EFI install).

Would be nice tough to have OCLP just re-enable SIP for oficial install. My point is, if it can disabled it automatically when I boot Ventura it should be easy to re-enable SIP selectively.

Thank you for the quick reply!
It is not possible to reenable SIP selectively. SIP on Intel Macs is controlled by a single NVRAM variable and used for all macOS installations (unlike Apple Silicon, where it is per installation). We have OpenCore overwrite the SIP configuration when you boot it in order to ensure that you can actually boot Ventura.
FYI: I mentioned this in an earlier post. This was fixed in 0.6.6, but with 0.6.7 (AMFIPass Public Beta Test) the problem is back again:
The AMFIPass beta and 0.6.6 use the exact same patches, so...

Does this occur on the AMFIPass beta if you disable AMFI?
EFI generated by OCLP amfipass beta2 can be used with latest OCLP nighly builds. I have disabled the AMFIPass kext in Kernel -> Add and added amfi=0x80 in NVRAM -> boot-args before installing latest OCLP build. After, revert the changes and all good: latest build + AMFI enabled.
If you do this, you will not get support. I don't want to deal with people using unknown configurations, nor do I want to deal with people messing something up and breaking their installation.
The Apple Compressor refuses to work with the message.

Apple Compressor does not support macOS virtual installation.

Does anyone have an idea to fix this?

MacOS 13.4
OCLP 0.66
Known issue, fix coming soon™️
 
Last edited:
It’s really impressive to see what we can do with OCLP, but it remains two annoying failures for my situations:
- HEVC decode not working on my late 2015 iMac with a amd R9 => problems with Photos, videos, chrome startup, Apple TV crashes …
- Xcode debugger doesn’t seem fully reliable
Do you think you are able to improve that ?
 
  • Like
Reactions: Sanmiguel71
It’s really impressive to see what we can do with OCLP, but it remains two annoying failures for my situations:
- HEVC decode not working on my late 2015 iMac with a amd R9 => problems with Photos, videos, chrome startup, Apple TV crashes …
- Xcode debugger doesn’t seem fully reliable
Do you think you are able to improve that ?
I thought I'd be able to fix the VA problem with my new MacBook with GCN GPU but it's not affected by this so unlike for this problem to be fixed any time soon since we don't have an affected machine to work on.

The LLDB crash is a DSCE limitation, the only one who can fix that is @ASentientBot but apparently that's not easy.
 
I thought I'd be able to fix the VA problem with my new MacBook with GCN GPU but it's not affected by this so unlike for this problem to be fixed any time soon since we don't have an affected machine to work on.

The LLDB crash is a DSCE limitation, the only one who can fix that is @ASentientBot but apparently that's not easy.
Maybe the difference is the Amd GPU is not always used on laptops (only when plugged in and heavy workload) ?
On iMacs, the intel iGPU is never used, we only rely on the amd
On your MBP, you haven’t noticed that 4K iPhone videos are read in low res in Photo ?
Chrome (or edge or other chromium browsers) are not slow to start ?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.