$ grep -r Tag: «os x»

I've been trying to come up with something that would make it convenient to do pixel-perfect screen layout while developing iOS apps. Something that would make it easy and visual to compare the mockup and the result. Today I hacked together this tool for OS X - an almost transparent window where you can open a mockup, place it over Xcode or the simulator, and see what you got. You can adjust the transparency with a slider to check how closely it matches.

Maybe it will be useful to someone. Or maybe someone else feels the same pain and will join the development.

The source code is on github.

Download the binary.

P.S. my first app for OS X.

I'll leave another cheat sheet in the form of a link. Network Link Conditioner is a tool from Apple from the Hardware IO Tools for Xcode set. It lets you limit connection speed in macOS. You can test, for example, how an app behaves under EDGE connections or worse. The same thing exists in the Developer section of iOS settings, but that is on the device, while this is in OS X.

By the way, the same set also contains a simulator for HomeKit.

I finally updated my work Hackintosh from OS X 10.9 to 10.10. It took a lot of time. Here is how I did it and what problems I ran into.

I finally updated my work Hackintosh from OS X 10.9 to 10.10. It took a lot of time. Here is how I did it and what problems I ran into.

So, here is what we need for the update:

1. OS X Yosemite installer. Open the Mac App Store and download it from there. In my case, as before, trying to run it directly to upgrade the OS was pointless: the installer says it is ready to install everything but needs a reboot. You reboot, and nothing happens — you just land back in Mavericks.

2. An 8 GB flash drive or larger. A USB hard drive also works.
3. Unibeast to create a bootable flash drive (download it here).
4. Multibeast to install drivers and the bootloader after the OS is installed (download it from the same place, here).

Bootloader

I used to have Mountain Lion, which I updated to Mavericks a year ago, and now I updated Mavericks to Yosemite. Since then I had the Chameleon bootloader installed. It was an old version. Because of that, after installing the OS I could not get the new bootloader from Multibeast to install, and the old one could not boot macOS — it just sent the computer into an endless reboot loop. So I could not even see the boot error that was preventing the OS from loading.

So it is better to download and install in advance the latest version of Chameleon and the latest version of Chimera, because for some reason they do not install from Multibeast after the upgrade.

Foreign guides also say that you need to edit the file /Extra/org.chameleon.Boot.plist and remove these 2 lines:

Kernel
mach_kernel

Preparing the bootable flash drive

So, the Yosemite installer has been downloaded from the App Store and the latest bootloader version is installed. Time to prepare the flash drive. Start Disk Utility in macOS, select the target drive, then open the Partition tab. There is one important detail here. I had an external 160 GB drive. If I formatted it as one large partition, Unibeast, which creates the bootable drive, simply did not recognize it as a flash drive. The workaround was to split the drive into 2 partitions. I made one 32 GB partition and left the rest in the second one.

After that, click Options and choose Master Boot Record. Click OK, then Apply, and wait until Disk Utility prepares the flash drive / hard drive.

Then launch Unibeast and follow the installation steps. Select the flash drive or the partition on the external hard drive:

On the next step, choose Yosemite:

On the next step, if you have a laptop, choose Laptop Support. If not, continue. I do not know about the USB Legacy Support option. Most likely it is for people whose USB ports do not work out of the box. I did not need that option.

Click Continue, then Continue again, enter your user password, and wait until Unibeast creates the bootable installer flash drive.

When it is done, reboot the computer, choose the flash drive at startup, and boot from it.

Updating OS X Mavericks to Yosemite

If everything goes well, you will land in the Chimera bootloader. Select the USB drive there. After that you should end up in the OS X Yosemite installer. Most of the time it does not start that easily. So when selecting the USB drive in Chimera, you can also type boot flags (just start typing on the keyboard and the entered text will appear at the bottom). I booted with the flags -v -f -x (without quotes) and got into the installer. Although I think I first saw a black screen, so besides those 3 flags I also had to add GraphicsEnabler=Yes. Then follow the standard installation steps. When you get to the disk selection step, choose the disk that already has OS X Mavericks installed — the installer will automatically upgrade it to Yosemite and keep your settings and files.

When the installer finishes, it will ask you to reboot. Reboot. Again boot from the USB drive. This time choose the disk where Yosemite was installed. I had to boot again with the -v -f -x flags.

Then comes the part where you clean up the problems. If everything goes well, you will boot into OS X safe mode, where you can install all the drivers you need from the Multibeast package downloaded earlier.

I was less lucky.

Pitfalls

First I realized that my old OS bootloader would not boot, while the USB bootloader would. Installing the bootloader from Multibeast simply did nothing. That is why I had to download and install Chameleon separately and then Chimera. It took me a long time to figure that out through trial and error. It took so long because every reboot of the computer took about 10 minutes.

Then I noticed an error in the console saying that FakeSMC.kext was already loaded, and the OS did not like trying to load a duplicate. It turned out that back when I was randomly poking at drivers, I had some myHack.kext lying in /System/Library/Extension, and it already contained an old FakeSMC version. It did not fit the new OS and blocked the loading of the new one installed by Multibeast. I had to remove it.

Editing the file /Extra/org.chameleon.Boot.plist did not go smoothly either. Because my bootloader was old, it complained when that line was removed. So if something went wrong, you could no longer boot at all. In the end I had to boot into Single User Mode (add the -s flag at startup) and edit that file again in the console. The working solution was to keep those lines but replace mach_kernel with /Systems/Library/Kernels/kernel. Or maybe that was not even the real reason. With the confusion caused by the bootloader, I never fully figured it out. In any case, if you have the latest bootloader installed, either remove those 2 lines or write /Systems/Library/Kernels/kernel instead of mach_kernel. In my currently working system those lines are gone :)

When installing packages from Multibeast, there is a Customize -> System Definitions section where you can make the OS think your PC is a Mac Pro, Mac Mini, iMac, or Macbook Pro. In my case the system booted normally when I defined the machine as iMac 14,2. But after that I decided to update the native NVIDIA drivers for macOS, and the installer said that this computer was incompatible. I started trying Mac Pro variants starting from the latest one (6,1), after which the system would not even boot in normal mode anymore (I had to boot again with -v -x -f). In the end the working option turned out to be Mac Pro 3,1. With it, the system booted normally and the installer for the new NVIDIA drivers agreed to install.

And the last pitfall was the one I described earlier in my cheat sheet: a Kernel Panic with the error Kernel extensions in backtrace org.apple.driver.applertc(1.5). In the new macOS version, the number in parentheses is no longer 1.5 but 2.0. To solve it, you need to install the package “10.8.1 Rollback” from Multibeast, in Drivers -> System -> AppleACPIPlatform Rollback. The catch is that it exists only in the Multibeast 6 branch. Luckily I still had the old 6.4.2 version and installed it from there. In Multibeast 7 it is gone. There is a package called “10.9.5 AppleACPIPlatform Rollback”, but it did not solve my problem. I had to install the old package.

So, after about 6 hours of poking at it, I finally got everything configured and decided to write this post. I hope it saves someone some time so they do not have to poke around blindly like I did. At the very least it may help me too if I have to do this again later. By the way, many common problems and their solutions are listed here. That link is where I found the short upgrade guide and some of the fixes. It is in English, though.

Good luck, damn Hackintosh :)

When I got the chance to play with the new iCloud features in OS X Lion, the only thing that left me puzzled was the feature called «Back to My Mac». Yesterday I finally figured out how it works, and today I gave it a proper try.

The whole thing works very simply, between two Macs. On both Macs you turn on «Back to My Mac» in iCloud preferences, and from then on they behave as if they’re on the same local network.

I tested it today by taking my MacBook to work and leaving the iMac switched on at home. Once the MacBook connected to wi-fi, it reached into iCloud, saw that my iMac was online, and showed it to me in Finder’s left sidebar under Shared.

From there it’s all just like the machines are on a LAN. You can connect to it and browse files. By default you connect as a guest.

If you log in, you get to see all the files. You can authenticate either with the user account on the other machine, or with the iCloud account.

That said, I couldn’t log in via the iCloud account. But I did manage with the local account on the Mac. Got access to my files. You can copy or upload a file, just like over LAN — only the speed limit depends on the providers on each end.

But the most important and valuable thing for me is the «Share Screen» button.

I can finally drop TeamViewer, which is rather flaky on macOS and where to connect you need all sorts of numbers/codes or logins/passwords. Plus the constant pop-ups telling you it’s only free for personal use, and the connections that constantly drop out claiming the free session has ended.

And the client is rather pleasant. You can take a screenshot of the remote screen. If the remote Mac has more than one display, you can either show both, or switch to whichever one you want. It’s probably the standard built-in client; I just last used it back on Lion and didn’t pay attention to the rest of its features. To me it all looks great. There’s no option to change the quality of the streamed picture, but I don’t need that — my connection is fast enough.

So TeamViewer will from now on only be used for emergency Windows cases. Finally there’s a simple, convenient way to connect to my home machine. Beautiful.

P.S. Maybe someone can tell me how to stop the wretched TeamViewer from launching at boot? Even after I quit it, it just starts up again, and I have to quit it the second or third time.