Jump to content

TheBeev

Members
  • Content count

    19
  • Joined

  • Last visited

About TheBeev

  • Rank
    InsanelyMac Protégé
  1. Don't know if anyone else is experiencing this, but for some reason the PlayPause function requires me to hold Fn while pressing F5. None of the other media keys or special functions behave this way. I've tried remapping this in Karabiner but to no effect. To the best of my ability, I've tried following the documentation link you provided but I'm still unclear how to customize the keys based on the Dell layout. I'm attaching my Info.plist if anyone knows how to fix this. EDIT: Never mind, I've fixed the F5 button. Apparently Fn Lock was reset in my BIOS (which, for some reason seems to be the one BIOS setting that doesn't seem to permanently stick...) However, the problem below still applies. Also, a four finger swipe up arbitrarily seems to function as a Brightness Decrement. I also have tried remapping this in Keyboard Shortcuts but can't change this gesture to a different functionality. Additionally, there is odd behavior like "" marks appearing in text when I lightly swipe up with three fingers and other things like that. I don't see how to change this... Any ideas? Info.plist
  2. lebish, could you talk a bit further about this? Specifically, how exactly do we create the patch you mention, and what does it accomplish? Are you saying that we can have a fully functional touchscreen with gestures just like in Windows? So does this mean we can have VoodooPS2 (or KNNSpeed's kext) for the touchpad while simultaneously loading this patch for the touchscreen? Thanks for explaining!
  3. Would anyone be willing to do a High Sierra guide? Please and thank you!
  4. Good news about the trackpad. Looking forward to testing it out. I'm doing a bit of detective work in trying to figure out the Bluetooth situation... I'm wondering if it is somehow related to a USB issue I've discovered, since I've heard that the Bluetooth is treated as a USB device (true?). Let me explain: So since the very beginning I've been having issues using my Logitech MX Master with this build. Using it with the unifying wireless receiver has resulted in spotty, unpredictable behavior. The mouse pointer is very choppy sometimes when moving across the screen; sometimes it will skip so horribly I can't even use it. But it works perfectly in Windows. Also, it worked perfectly on my old Macbook Pro running Yosemite. I've heard that the mouse has been quite unruly in Sierra, but I'm pretty sure those issues have long since been ironed out through driver updates. So I don't think it's an issue with Logitech. I had been using the unifying receiver plugged into a USB 3.0 hub. The solution I discovered was to plug the receiver straight into the laptop's USB port. Since doing that the mouse has operated just fine. So, I'm wondering if anyone else has had similar issues with wireless mice and/or using a USB hub with this build. Could there be something that needs adjustment with a kext? Additionally, I read somewhere (maybe even Rehabman said it) that sleep issues similar to what I've been having could be related to a USB problem. There you have it. Thoughts?
  5. Hmm... I put the patch in and still nothing has changed... You said you had the same symptoms and putting the kexts in /L/E fixed it? Did you have them in S/L/E before and it didn't work? I'm confused now as to which folder kexts should be installed to. I generally thought they were supposed to go in to /S/L/E -- but are certain ones actually supposed to go into /L/E?
  6. Thanks for the advice, but I've already done this. I've even swapped BrcmFirmwareData out for BrcmFirmwareRepo following Rehabman's guide - but it doesn't yield any different results. If anyone knows what's going on here I'd really appreciate the help! Bluetooth is pretty important to get working for me. Also, don't know if it's related, but I've checked in Kext Wizard to see what kexts are loaded and none of the FakePCIID kexts (Broadcom, Intel_HD, Intel_HDMI) are showing up except for FakePCIID.kext. I've installed them and they're in the /S/L/E folder - but they don't show up as "loaded". Is this normal? Once again, Wifi is working fine. And Bluetooth works in Windows. I just can't get devices to connect in macOS.
  7. Well, knock on wood, but I think I finally managed to get a stable system up and running again. I'll go over what I had to do to achieve this in a subsequent post - but for now I need help with a Bluetooth problem. The funny thing is that I had Bluetooth working early on; I don't know what I've done to change things but for the life of my I cannot get my devices to connect now. I have the DW1560. I've installed all the necessary kexts -- FakePCIID_Broadcom_Wifi, FakePCIID, BrcmFirmwareData, BrcmPatchRAM2 -- and I've put the two AirPortBrcm4360 patches in my config.plist. Wifi is working fine. In macOS the Broadcom chipset 20702A3 shows up in System Information under Bluetooth. Also, Bluetooth is working in Windows. But nothing will connect to Bluetooth in Sierra. The computer will recognize the device, but when I click "Pair" it just sits there trying to connect until eventually saying "not connected". Thinking it may have been a problem with the DW1560, I bought this USB dongle to try but I get the same results. I'm stumped. Looking around the internet I see several people experience problems with Bluetooth in Sierra (and Windows 10 as well) but I have not found any solutions to what is happening...
  8. Man this sucks. I don't know what I could have done to cause this... It's strange that it wasn't until I booted into Windows that something happened and the Mac partition became corrupted. I'm having trouble now trying to reinstall macOS. I've deleted the Mac partition within Windows and reformatted it as FAT32. Going through the guide's steps I am hung on Step 11. When I boot from the Mac SSD this is the message I get: This was actually the same problem I had on my first install. I don't remember what I did to get past Step 11, but for some reason now it's just not working. I have to go back from the beginning, redo the USB drive, yet still I'm stuck on Step 11. Another issue is that for some reason I can't get rid of the Clover boot screen - even when the Mac partition has been deleted. Got this part working at least. Yeah, as far as I know. I have a LiteOn drive, which according to my research requires Pike's patches along with an extra patch. This is what I have in my config.plist: <dict> <key>Comment</key> <string>IONVMeFamily Preferred Block Size 0x10 -> 0x01 (c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> 9sEQD4UcAQAA </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> 9sEBD4UcAQAA </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#1</string> <key>Disabled</key> <false/> <key>Find</key> <data> ibP4AgAAweAMBQAQAACJgw== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> ibP4AgAAweAJBQAQAACJgw== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#2</string> <key>Disabled</key> <false/> <key>Find</key> <data> D7aMiIIAAACD+QwPhTIBAA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> D7aMiIIAAACD+QkPhTIBAA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#3</string> <key>Disabled</key> <false/> <key>Find</key> <data> AMeDpAAAAAAQAABIi0gISA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> AMeDpAAAAAACAABIi0gISA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#4</string> <key>Disabled</key> <false/> <key>Find</key> <data> SYnGTYX2dGFBwecMSWP/vg== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> SYnGTYX2dGFBwecJSWP/vg== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#5</string> <key>Disabled</key> <false/> <key>Find</key> <data> hv8PAABIwegMD7cPgeH/Dw== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> hv8PAABIwegJD7cPgeH/Dw== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#6_7</string> <key>Disabled</key> <false/> <key>Find</key> <data> icGB4f8PAABIAdFIgfn/DwAAdzs= </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> icGB4f8BAABIAdFIgfn/AQAAdzs= </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#8</string> <key>Disabled</key> <false/> <key>Find</key> <data> SYHF/w8AAEnB7QxJiwQkSA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> SYHF/w8AAEnB7QlJiwQkSA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#9_10</string> <key>Disabled</key> <false/> <key>Find</key> <data> BgIAAEyNuAAQAABMiflIgeEA8P//SYmGGgEAAEmJjiIB AABBvAAQAABJKfQ= </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> BgIAAEyNuAACAABMiflIgeEA8P//SYmGGgEAAEmJjiIB AABBvAACAABJKfQ= </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#11</string> <key>Disabled</key> <false/> <key>Find</key> <data> AABJiY4iAQAAugAQAABIKQ== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> AABJiY4iAQAAugACAABIKQ== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#12</string> <key>Disabled</key> <false/> <key>Find</key> <data> yAAAAEkp17gAEAAATYskJA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> yAAAAEkp17gAAgAATYskJA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#13</string> <key>Disabled</key> <false/> <key>Find</key> <data> 4b+AQBUGTYnWugAQAABFMQ== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> 4b+AQBUGTYnWugACAABFMQ== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#14</string> <key>Disabled</key> <false/> <key>Find</key> <data> iWTY+EmBxAAQAABJgccA8A== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> iWTY+EmBxAACAABJgccA8A== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#15</string> <key>Disabled</key> <false/> <key>Find</key> <data> Bf8PAABIwegMZvfB/w8PlQ== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> Bf8PAABIwegJZvfB/w8PlQ== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#16</string> <key>Disabled</key> <false/> <key>Find</key> <data> weIIQQ+2wcHgDEQJ0EQJwA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> weIIQQ+2wcHgCUQJ0EQJwA== </data> </dict> <dict> <key>Comment</key> <string>IONVMeFamily Pike R. Alpha Patch#17</string> <key>Disabled</key> <false/> <key>Find</key> <data> RYTJD5XAD7bAweAMRAnYRA== </data> <key>Name</key> <string>IONVMeFamily</string> <key>Replace</key> <data> RYTJD5XAD7bAweAJRAnYRA== </data> </dict> The above has been confirmed to work for other people with LiteOn drives. I dunno... maybe I'm doing something wrong? I really appreciate the help guys!
  9. Oh boy... Well now I have a new problem - and it's a big one. I booted into Windows tonight (which I have done several times previously since installing macOS) and I was prompted by a Disk Repair message. Windows told me there were errors on my C: drive (Windows) that needed to be repaired. So I clicked the message and restarted. Upon booting back into Windows everything seemed fine from what I can tell. When I booted into macOS, however, my Windows drive has mysteriously vanished. Only the Mac partition is visible. I restarted my computer, entered the Clover menu, and tried booting into macOS again. But now the Mac boot screen just hangs indefinitely. I can't get into macOS. I go back to Windows to try to back up my Mac partition (I can still access the Mac drive in Windows). But I can't copy the folders due to an "unknown error". I try to archive the folders into a .zip or .7z but I'm told "the disk structure is corrupted and unreadable." So back to Clover to boot from the Mac recovery HD. I go into Disk Utility to try to repair the Mac drive and this is the error I receive: No matter what I do I can't get into macOS. What has happened here?? How do I fix it, and how do I ensure this doesn't happen again?? Ahhh please help!
  10. I hate to speak too soon, but I think I may have found the solution to the wifi/bluetooth disconnection issues after sleep... In Clover-->Boot I changed Darkwake to value 10 from the standard 1. Then in System Preferences-->Energy Saver I checked (enabled) Power Nap for battery and power adapter. So far—as far as I can tell—everything seems to be working perfectly! I'll report back if I encounter any problems.
  11. Hey KNNSpeed, do you think this solution might have anything to do with the sleep problem? Not sure if it applies to your build. What do you think?
  12. I'm experiencing the exact same problem. After putting the computer to sleep either through the menu or by closing the lid, upon waking I am often disconnected from Bluetooth and Wifi. Trying to turn them on again does nothing. The only way to switch them back on is by a restart. And same for me - the reboot often takes a bit longer to return to the Dell boot screen. Sometimes even if I close the lid after my BT/Wifi is dead, when I open the lid back up the computer has restarted itself on its own. I also sometimes get a battery alert saying my computer will be put to sleep soon unless I charge the battery. I'm at full charge, and the battery status even says 100% (and won't go down, actually) but it's red, as if the battery is critical. A reboot brings it back to normal. Additionally I have the combojack issue after sleeping which I've posted about previously. I tried the LiluFriend trick to no result. The above issues lead me to believe the problem may have something to do with how Sleep works, and not related to the Broadcom card. If anyone knows how to fix this I'd greatly appreciate it. I'd be happy to attach my Clover folder for diagnostics--if I could figure out how to attach files!!! (I'm new to this forum- please help! )
  13. I swear I remember reading somewhere that the CUDA cores can still be utilized inside Mac for video rendering. Is this true or did I dream it?
  14. Thanks, got it! If my audio jack is plugged into the laptop while it goes into sleep or when I close the lid, upon waking/opening there is a harsh hum noise. I have to unplug the jack and reinsert it for the window prompt to appear again in order for the audio to work as normal. Is this a limitation of the audio fix - or is something wrong?
×