Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CAT tool with macOS Sierra #312

Open
robstoll87 opened this issue Jun 28, 2016 · 19 comments
Open

CAT tool with macOS Sierra #312

robstoll87 opened this issue Jun 28, 2016 · 19 comments

Comments

@robstoll87
Copy link

I installed the macOS Sierra beta and the CAT tool BETA for Sierra yet it doesn't seem to work. In "general" it had handoff checked.

Please include the following information.

  • OS Version: 10.12 Beta (16A201w)
  • Mac model: MacBook Pro (15-inch, Mid 2010)
  • Dongle: IOGEAR Bluetooth 4.0 USB Micro Adapter (GBU521)

Any ideas on how I can get this to work? It worked for me in the past.

Thanks,
Rob

@mwoolweaver
Copy link

Did you run it from the /Applications directory?

@robstoll87
Copy link
Author

I dont believe so. Should I drag it to applications and try reinstalling it? Thanks for the quick response!

@robstoll87
Copy link
Author

screen shot 2016-06-27 at 11 48 30 pm

@mwoolweaver
Copy link

Yes

@robstoll87
Copy link
Author

screen shot 2016-06-28 at 12 15 38 am
Still doesn't work.

@mwoolweaver
Copy link

Do you have the options to enable Continuity/HandOff though in Preferences.app?

@robstoll87
Copy link
Author

Yes

@mwoolweaver
Copy link

Ok so I had a weird issue were I didn't see any continuity features for at least 4 days (see issue #308) and then they just magically started working for no given reason...

@iPhonda
Copy link

iPhonda commented Jun 28, 2016

Hello, I've a Mac mini (mid) 2011 and buy the Asus bt400, when installing everything goes fine then I restart the Mac but the HandOff does not appear on Preferences.app...
Whats wrong???

Ps : MacOs Sierra

@ghost
Copy link

ghost commented Jun 28, 2016

I installed on my macbook pro sierra 2009 with a patch and after I installed CAT! after the reboot no kernel panic but the mac still hang on the progress bar and restarts after 10 minutes. 😞

@hrubymar10
Copy link

Same for me…

MacBook Pro 13' Mid 2011 (MacBookPro7,1)
macOS Sierra 10.12 Beta (16A201w)
Asus BT-400 Dongle (worked in Yosemite, but in El Capitan not)

ma

On 28 Jun 2016, at 21:10, mactofou notifications@github.com wrote:

I installed on my macbook pro sierra 2009 with a patch and after I installed CAT! after the reboot no kernel panic but the mac still hang on the progress bar and restarts after 10 minutes. 😞


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #312 (comment), or mute the thread https://github.com/notifications/unsubscribe/ACHbQeXUtTand7cvBKI9wYm-LX5I2iP3ks5qQXGMgaJpZM4I_tWi.

@tim0feev
Copy link

On macOS Sierra in Preference.app it does not appear click "Allow your Apple Watch to unlock your Mac", although it works via Bluetooth.

@iPhonda
Copy link

iPhonda commented Jul 12, 2016

On mine appear that option but on the lock screen he try's to unlock with the watch but after a 3 seconds ask the password again...

@robstoll87
Copy link
Author

robstoll87 commented Jul 18, 2016

This is running beta 3. This is the report I get. Any idea why its still not working?
screen shot 2016-07-17 at 8 52 05 pm

@maciboy
Copy link

maciboy commented Sep 8, 2016

Just installed the macOS Sierra GM on my MacBook Pro 15’’ 2010.
I’m using a Gmyle Dongle (https://www.amazon.de/gp/product/B007MKMJGO/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1)

CAT is working fine so fare, no panics, no unavailable Wifi or BT :)

Just one thing was a bit strange during installation: backups of kext files weren’t possible due to „read only filesystem“.
So no backups of IO kexts :(

@frizby66
Copy link

frizby66 commented Sep 8, 2016

I Have had the same message ever since I installed Sierra and ran CAT.

On 8 Sep 2016, at 15:43, maciboy notifications@github.com wrote:

Just installed the macOS Sierra GM on my MacBook Pro 15’’ 2010.
I’m using a Gmyle Dongle (https://www.amazon.de/gp/product/B007MKMJGO/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 https://www.amazon.de/gp/product/B007MKMJGO/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1)

CAT is working fine so fare, no panics, no unavailable Wifi or BT :)

Just one thing was a bit strange during installation: backups of kext files weren’t possible due to „read only filesystem“.
So no backups of IO kexts :(


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #312 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ALU-Ro3Il_e0hnseehNjN-R1Tz9C0LWBks5qoB79gaJpZM4I_tWi.

@electricburgers
Copy link

@robstoll87 I did something and now Handoff is working!!
https://imgur.com/a/CdzjU

Clipboard sharing, Safari/iMessage handoff!

What I did is:

Settings > iCloud > iCloud Drive > Toggle Off > Toggle On > Stuff works

NB: Before trying this I did do a Restore > Restore from Backup to 10.0.1. I don't know if this helped with anything. I did not touch anything on the macOS side.

  • OS Versions: macOS Sierra 10.12 (16A320), iOS 10.0.1 (14A403)
  • Mac model: MBA mid-2011, 11-inch, MacBookAir4,1
  • iPhone model: iPhone 6S
  • No dongle, no replaced card, using built-in WiFi, built-in Bluetooth

@mobile4
Copy link

mobile4 commented Sep 27, 2016

Macbook 13' 2010 mid. Gmyle dongle. HDD has been replaced to SSD. Worked well with the latest Yosemite.
El Capitan - CAT installed without errors but kernel panic on reboot. Tried both version of CAT from Master and Beta branches.
Sierra - Some errors during installation of CAT. Something related to permissions and kext back up. Hangs on reboot.

  1. Probably problem related to SSD? Everybody who has the same problem. Do you use SSD instead of HDD?
  2. As I wrote above MBP hangs on reboot. Please make detailed instruction on how to replace wifi and bluetooth kext back to original. It is very boring to reinstall OS for the next experiment.

@fischersd
Copy link

What else is CAT doing for the ContinuitySupport patch? I check my SystemParameters.plist (in frameworks) and there is an entry there for my board-ID (Mac Mini, late 2012) - Mac-031AEE4D24BFF0B1.
But when I run the CAT diags (after doing a force using the contitool.sh script), what you're checking still isn't patched:

--- Hardware/OS checks ---
Verifying Continuity status... OK. OS X reports Continuity as active
Verifying Mac model reference... OK. Known compatible Mac Model detected: Macmini6,1
Verifying Mac board-id... OK. Long board id detected: Mac-031AEE4D24BFF0B1
Verifying OS X version... Warning: This tool wasn't tested with OS X versions higher than 10.10. Detected OS version: 10.12
Verifying Wi-Fi hardware... OK. A Broadcom AirPort card is active, and is using the Continuity compatible Brcm4360 kext
Verifying AWDL status... OK. Wi-Fi hardware is compatible with AWDL, but no such interface is up. This tool can try to fix this.
Verifying Bluetooth hardware... OK. The internal Bluetooth card is active
Verifying Bluetooth version... OK. Bluetooth 4.0 detected
Verifying Bluetooth features... OK. Bluetooth features are Continuity compliant
Verifying Bluetooth firmware... OK. Bluetooth firmware version: v126 c9195
Verifying Login Item... OK. Login item for Auto Continuity Check is not set.

--- Modifications check ---
Verifying OS kext protection... OK. Kext developer mode is already active
Verifying SIP... Ok. System Integrity Protection is already disabled
Verifying ContinuitySupport... Print: Entry, ":Mac-031AEE4D24BFF0B1:ContinuitySupport", Does Not Exist
NOT OK. Unknown state. Your Mac might not be compatible.
Verifying kexts readability... OK. Wi-Fi and Bluetooth kexts were found and could be read
Verifying Wi-Fi whitelist status... OK. The whitelist is correctly patched with your board-id
Verifying BT4 dongles compatibility... OK. Compatibility with BT4 USB dongles is not enabled, this tool can fix this if a dongle is plugged in
Verifying old Wi-Fi kext presence... OK. Legacy Wi-Fi driver Brcm4331 was already removed
Verifying legacy Wi-Fi card patch... OK. The patch is already done. Old Broadcom Wi-Fi cards may work.
--- Modifications check ---

(yes, it says the model is ok...did a little tinkering with the script - but not able to find what you're doing for this check).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants