Jump to content


  • Content Count

  • Joined

  • Last visited

About Lockzi

  • Rank
    InsanelyMac Protégé
  1. I have upgraded one of my location to Google WiFi. I now notice that the WiFi compatibility seem to not be as expected... It's a two story location with concreet walls with 3 Access Points. It simply refuses to connect to the closes network, and insists on 5Ghz AC connection rather then 2.4Ghz even though it gives poor connection. I remember reading before about someone else having problems with the WiFi on this configuration. Has there been any updates on that specific issue and maybe someone is interested in troubleshooting?
  2. I was able to fix the teleporting by the assistant of Alexandred at: https://github.com/alexandred/VoodooI2C/issues/113 Really awesome trackpad now!
  3. What Mac OS version are you running? I'm still on 10.13.3 due to DisplayLink driver issues.
  4. Hello Alex, I can confirm that I was using APCIBatteryManager. After disabling it I still have the same issue, so it's not even after sleep. Should I go through with the troubleshoot procedure you've listed on Github?
  5. So then I am guessing it is something with our implementation. I have not realized nor confirmed that it occurs after sleep. Interesting, will check it out. It seems like it has something to do with the GPIO pins for trackpad interrupts? Maybe I should try rolling back the GPIO patches and use VoodooI2Cs polling method instead...
  6. Hey Guys, just wanted to quickly check here before I report a bug and troubleshoot with the developer. I've switched to VoodooI2C v 2.1.4 today, and if I draw a circle with the mousepointer using the trackpad continuously I can see how it teleports in the last known direction of the circle - exactly every second, which makes it impossible to do a circle. Same thing can be observed if you slowly scroll on this page. The scroll will be jumpy at every second. I have added the DSDT files as per hvolkoff's initial discussion Is anyone else seeing this on our machines? Are everyone else still using the SSDT-I2CX.aml and SSDT-XOSI.aml from the linked post or has the development of the kext changed so it's no longer needed?
  7. I updated, but I am still on 10.13.3 No other changes for me.
  8. Same for me. Even though removing the I2C kexts it does not work. It may be due to the SSDT-XOSI or voodooPS2daemon? I have only tried the SSDT-XOSI as @goodwin_c suggested, not using the previous one with enabling later windows as @hvolkoff stated. I have tried both I2C 2.0.1 and the "10.13 beta" as included in zip file of original post by @hvolkoff . The ControllerInterrupt first two hex are "10" looking at IOReg. I've noticed that in some cases the mouse works just fine during the login screen, but shortly after logging in it stops moving, hard to do mouse clicks, essentially unusable except for scrolling. The touchscreen, however, works perfectly.
  9. Has anyone else started to experience problems with Bluetooth after sleep since High Sierra? The problem is that after wake up: It's on - but can't connect to any devices and can't be turned off (no error message or anything, just nothing happens when pushing the button). The only fix is to restart the computer. I remember that while installing I had some bcrmpatch2 errors while trying to install.
  10. Exact wording: macOS could not be installed on your computer An error occured while verifying firmware. Quit the installer to restart your computer and try again. If I recall right I opned the console and there it was a message about securityd killed all processes through sigterm due to "Firmware unsuported", but the wording above is what the installer wizard says.
  11. I had to disable (rename/remove) the EmuVariableUefi-64.efi, it apparently has to do with our NVIDIA GPUs (source: http://hackintosher.com/guides/high-sierra-fix-macos-not-installed-computer/) /dev/disk0 (internal): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme 1.0 TB disk0 1: EFI EFI 314.6 MB disk0s1 2: Apple_APFS Container disk1 980.1 GB disk0s2 3: Apple_HFS Win10 43.6 GB disk0s3 I'll go along with installing win10 now through bootable USB - hoping for the best! UPDATE: There's no problem dual booting High Sierra APFS with Win10!
  12. I can not confirm by facts, exactly that is my experience based on the two re-installations I've done. Another thing I would like to add was that once the first installation failed (firmware unsupported error), I had to reformat the whole disk to HFS (from APFS) in order to get it working again. I created another partition as place holder for Windows 10 at the end of the drive. Has anyone installed Windows 10 (dual boot, not bootcamp) after High Sierra with APFS? Worried about it overwriting the partition scheme and screwing something up...
  13. Yes, i7 Got it working by removing the emuvariable driver as well as downloading the latest cover instead of the one Pandora uses. Apparently it seems like it's because of our integrated GPU.
  14. I have the exact same problem as well. Changing from Cloverx64.efi to bootx64.efi does unfortunately not work either. Doing a clean install. 4k sector, extended journal, GUID, with prepared empty partition for bootcamp. Any more ideas?