HiDPI is basically like the MBP internal “Retina” screen, using higher 4x resolution to render, then projecting and showing with lower resolution on physical display, which will display much sharper text and image. So for 1080p HiDPI, it actually renders at 4320p, requiring a 4K screen to work.
Theoretically, there is no benefit to enable HiDPI on 1080p monitor, because physical screen pixels remains 1080p and the 4K rendered resolution should be projected to the same pixels as original 1080p rendering. However, there’s still a visible improvement, especially in rendering text. Here’s my screenshot comparison.
Without HiDPI, more fuzzy bold rendering of text:
With HiDPI, much sharper and slim rendering:
Since it’s a 1080p monitor, the default device profile won’t list HiDPI resolution options in the display settings. There’s a Mac shareware SwitchResX and disabling SPI to install custom resolution profile. But this can also be done by the free RDM app and this online profile generation tool. After following the steps to install custom made 1080p HiDPI display profile, you could then select the lightning HiDPI for a 1080p external display with the RDM app.
There is a good article for WinToGo setup on MBP2018, along with this article and my old post for MBP2012, but they are all just good for USB drives only. If you want to do a Win2Go with a thunderbolt3 drive, several days of rebooting is ahead.
Firstly, WinToUsb won’t list thunderbolt drives, making it impossible to create bootable disk. This means the old way of imagex/dism and bcdboot to make a bootable installable thunderbolt drive is your friend. Then Win10 boot setup fails with mysterious error “Windows setup could not configure to run on this computer’s hardware” during the preparation spinning circle interface. Nothing googled directly helps, including the popular “msoobe” command hack. After hours of trials, this post gives the correct steps of bootable disk partitions creation. Actually, the top article above mentioned the hack to format with “EFI System Partition”, which will do the same trick to create MSR partition automatically, but latest windows 10 seems unable to create these correct partitions with the hack, causing the preparation setup failure.
Secondly, the Windows 1803 version won’t install on thunderbolt3 drive with MBP 2018. It always fails with DMA Access Violation crash blue screen of death. DMA is related to the storage driver. Since MBP 2018 came out in the later half of the year, Windows 1809 version will have the correct thunderbolt3 drivers included and will install.
Thirdly, Windows 10 boots, installs, and freezes if boot camp drivers are added into the install media. After several rebooting and studying, the problem might be related to the AMD Radeon drivers and ReLive settings. The solution is to begin setup without the add-driver step. It means that the external mouse and keyboard have to be used during the install process. The built-in keyboard with touch bar and trackpad won’t work without boot camp drivers. So prepare an external usb keyboard/mouse for the setup.
Finally, Win2Go of Windows 10 can install and run successfully now. Though, standalone boot camp drivers install might take quite a long time and hang for some USB XHCI controller. Anyway, it doesn’t matter to have an unrecognized mass storage device after a forced restart. Everything works with super fast speed, including the AMD display card, the thunderbolt drive and all USB devices!
The unrecognized devices listed in Win10 Device Manager could be T2 chip related, which are reserved only for OS X and unaccessible in Windows. Since ACPI power management is also controlled by T2, Win10 will have to use standard Microsoft driver for power management. This will sometime lead to some strange battery behaviors, like discharging even if ac power is plugged-in. The only hope is some future released BootCamp drivers.
Latest Raedon 18.40 bootcamp drivers are here, which seems to fix the power discharging issue when GPU is on.
Just migrated my old rMBP 2012 to new MBP 2018 with Migration Assistant. Everything seems as good as the old one, but Office365 is not activated. When activating Office apps, it always fails, reporting unknown error 0xD0000FFFE.
Apparently, it is related to some existing license which was migrated. After Googling, some solutions like deleting folders under ~/Library/Group Container is surely unacceptable, as it will also remove your Outlook inbox folders!
This post has the official software to correctly remove existing license. Then re-activate Office365 will succeed happily.
Just upgraded to WordPress 5.0 and found a strange problem of theme customize live preview showing some domain Ad website instead of my own site.
Googling around shows nothing useful but quite a few sites have similar domain advertising site description listed in the Google search results, which means they got hijacked too.
By disabling the plugins one-by-one, it turns out that Akismet3 is the culprit which shows version 3.9.9 from wordpress.com without “view details” link. Don’t know how it got installed. The official one should be Akismet Anti-Spam, version 4.1, from Automattic, and with “view details” prompting the plugin introduction.
Atom as a code editor just becomes slower and slower with the burden of massive plugins, requiring near 15s on my MBP to initially display file contents. In comparison, VSCode with similar extensions just takes 5s to show file text upon launch. There must be some architectural issues in the Atom startup process, as both are based on Electron. The memory/cpu footprint also has huge differences as this old post shows. Atom sometime even stops responding and asks to wait for editor window to run.
While speed performance is an important factor, all kinds of mysterious long pending bugs are really killing it. In my scenario, the vertical scrollbar sometime just turns into a white bar. Some issues are reported, analyzed, but just doesn’t reach a fix. And the git interface cannot stage lines for files with unicode filename, but is only able to stage the whole file. The nuclide file tree is unusable as constantly steals text editor focus! All of such problems are long existed nuisances to bear with.
Fortunately, VSCode now also enjoys the affluence of extensions. Almost all of my Atom plugins find their counterparts in VSC. The only advantage of Atom is the beautifulness in contrast to the VSCode default theme’s coarseness (the blue status bar is horrible), but hopefully the Atom One Dark theme and keymap extensions are the cure.
Just after Microsoft successfully bought Github, it seems the right time to switch from Atom to VSCode finally.
Just updated BetterTouchTool to V2.645 and found that the accessibility permission warning popup cannot be dismissed as the close icon of the popup panel is now missing. Actually BTT can work well for touch/click functions without accessibility permissions.
After some searching around, one github issue has some useful hint:
Apparently High Sierra has well complained issues with bluetooth. My Logitech MX Master mouse also suffers from random disconnection. Today when I tried to disable bluetooth and reconnect, the mouse just won’t connect.
So I deleted it from MBP’s bluetooth devices, and found out that MX Master cannot pair any more again. Just like some other guys’ video shows, it keeps connecting and disconnecting when pairing.
My MacBookPro was forced to upgrade to High Sierra, because XCode 9.3 is only available on 10.13 to support development for iOS 11.3. The new operating system looks quite the same, except the ridiculous wordings of the Chinese translation of system UI.
As usual, I made a Time Machine backup before the upgrade. Since my NAS disk was quite full, some old backups should be deleted after the system ran smooth. Well then, the Finder just turned frozen during the Time Machine deleting process, locking in the Time Machine tunnel interface.
After a hard rebooting and some googling, I found that the following steps might fix. It uses the command line to delete the dated backups and shrinks the size of the target Time Machine bundle :
Connect to the target Time Machine Sparse Bundle file in the Finder
Ensure that /Volumes/Time Machine Backup/Backups.backupdb shows in ls
Delete old backups: sudo tmutil delete /Volumes/Time Machine Backup/Backups.backupdb/YOUR-MAC/SOME-DATES
Eject the Sparse Bundle file in the Finder
Shrinks the bundle: sudo hdiutil compact TARGET-SPARSE-BUNDLE-FILE
Just encounter a strange high cpu problem of kernel_task in Sierra on my rMBP. It means that the kernel_task process is having more than 80% CPU usage in the process monitor. At first, it seems like some software problems, especially when atom editor is opened with a super long starting time. After closing atom, it does lower the cpu for a period, but running another software afterwards will also boost the kernel_task cpu percentage to 80%. It strongly suggests some underlying hardware problems there.
Comments in this post give a reason: temperature and fan control. Since it’s now summer and super hot, the 10.12 OS X on my mbp is quite possibly reducing cpu speed for temperature compensation, causing the kernel task taking more cpu to consume. Resetting SMC in this article brings the fan control back and fixes the kernel_task cpu problem.
And installing some fan speed monitor/control software is also a good idea to keep an eye on it.