Since the first week I had my MacBook Pro, it had a peculiar, intermittent problem: it would spontaneously turn off, and getting it back on was hit or miss. Pressing and holding the power button didn’t do anything. Tapping the keyboard did nothing. Once, I reset the SMC and it came back to life – but that trick never worked again. Other times, simply leaving it alone for 5-10 minutes would bring it back to life. What was odd was that it would only happen when I was away from home – it never exhibited this behaviour while it was used in my home office. I didn’t think heat was a factor as it didn’t happen after extended uses of heavy load – in fact, it often happened before I even started doing any real work.
This issue, when combined with the lackluster battery life, combined to leave me with a feeling of frustration and regret and having spent so much money on this product. No longer being a professional tech blogger, I am much more judicious about my technology purchases – this was my only laptop for the next 3-5 years, so it had to be a great purchase…and it sure didn’t seem like it.
The sixth time this happened (while I at my kid’s Taekwondo class), I finally got fed up enough to bring it into the local Apple Store Genius Bar. That time, it blinked off just after I logged in, which was a new behaviour. Normally it simply wouldn’t turn on.
In truth, I am still a neophyte with the UNIX underpinnings of macOS, so the “deep in the guts” troubleshooting methods aren’t part of my skillset yet (and might never be if I’m honest). The particular symptoms my MacBook was having were difficult to search for – I couldn’t find any online resources that were applicable. I thought since I paid the Apple premium – which includes the benefit of taking it into an Apple store – I’d see how the premium tech support experience worked. I already had decades of experience calling tech support lines in India for Dell and HP laptops, arguing with them about the problem, so I’d try the Apple way.
I’ve had my MacBook Pro 13 for about two months now, and based on all the initial furor around battery life I wanted to wait until I had sufficient hands-on time with it to make my own determination. After two months of use, the truth is really simple: Apple put in a tiny battery because they felt people wanted a thinner/lighter MacBook more than people wanted long battery life. This is simply a laptop that was not designed for all-day battery life. There’s nothing more to this story than that.
People can talk about software optimizations, Chrome vs. Safari, etc. all day long – but the reality is that there’s no software tweak in the world that will make a tiny battery into a bigger one. The battery in the 2016 MacBook (49.2 Wh) holds about 38% less power than the 2015 MacBook (79.2 Wh) .
I’m a little upset that this machine I spent $2600 on has worse battery life than the last laptop I owned (which was 60% less expensive I should add). I am trying to come to terms with that reality; the only thing that helps is that the battery is so pathetically small it charges fast, and that the USB-C ports give me charging options I didn’t have before – I now carry a 10,000 mAH battery pack with me to top up the MacBook when needed. It’s worth pointing out though that I need to put the MacBook to sleep to get any real charging – most battery banks don’t put out enough power to charge the device while in use.
A week ago Monday, I unpacked my new 2016 MacBook Pro 13. It took 57 days from day I ordered it until the day it showed up at my door. Why so long? I’m glad you asked friend. 🤓 I didn’t order it right away – I wanted to see a few reviews because I was so shocked and dismayed at some of the decisions Apple had made regarding the ports and the small battery size. As I waited, the build time went from 1-2 weeks to 4-6 weeks. Since I wanted to avoid Washington State sales tax (which would have added $260 to the final bill), I ordered it from ABT. It was considered a custom order since I got the Core i5 2.9 Ghz / 16 GB RAM / 1 TB SSD version. I didn’t want to make the mistake I made with my 5K iMac having only a 512 GB SSD, especially since I was planning on using Final Cut Pro on the MacBook and it needs tremendous storage to make it’s powerful mojo work.
The final price was an eye-watering $2600. I remember paying $2500 for several of my first laptops – I’m looking at you, little Fujitsu P5010D – but my 2015 Dell XPS 13 purchase was only $1151, so this was a big step back up to the pricing stratosphere. I am agog at the people who max out the 15″ version and pay over $4300! Cost is a relative thing though of course – back when I was a single guy with no real bills, a $5000 computer every two years was a regular occurrence. My how things change!
Presented to you stream-of-consciousness style, here are my first impressions of my 2016 MacBook Pro 13.
I have a new Mac-related post coming up, but I wanted to finish off this series first (yes, it’s long overdue!). After month four, I started getting into a groove, and had fewer questions and issues – thus fewer things to write about. There were a few things though that came up, and so I give you the final entry in this series. In some cases I’ve added updates if things have changed since I first wrote these 6-10 months ago. It’s fair to say that things have smoothed out since the first six months.
- Although I didn’t buy the iMac for gaming, I saw the promo for Wasteland 2 and the comments about it being similar to Baldur’s Gate, a game I used to spend hours playing. I bought it, let it install, fired it up…and squinted in dismay at the incredibly blurry text. There’s just no way around it: when you have a display showing 5120 x 2280 pixels over 27 inches of screen, and a game that caps out at only half that (2560px) you’re getting a lot of stretched pixels. The cut scenes in particular were extremely blurry; it got better once I was in the game, but even then the in-game text was pixelated. I spent about 5 minutes playing it, but the controls were awkward with the Magic Trackpad. I’m grateful for Apple’s refund policy, though it’s entirely unintuitive because the process looks like you’re asking for tech support until the final step where a refund option is presented. That’s very likely the last time I pretend an iMac with a laptop GPU and a 5K display can do any gaming. 🙂
“A husband and wife must operate like two wings on the same bird; if they don’t work together in full partnership, the marriage will never get off the ground.”
– Dave Willis, “The Seven Laws of Love”
It’s been quite a while since I’ve posted anything on this blog about the debacle that was Concrete Equities, but the wheels of justice move slowly – when they move at all – in the realm of white-collar crime. Finally though, some good news:
“While one of his victims sobbed in the back of a Calgary courtroom, a city man pleaded guilty Friday for his role in bilking $23 million from hundreds of investors. Varun (Vinny) Aurora pleaded guilty in provincial court to fraud over $5,000 in a scheme centring on Mexican real estate investments. His own father lost the largest amount — $901,000 — in the fraud run by Concrete Equities Inc. that roped in 1,200 investors, about 20 of whom showed up in court. The play, which began in 2007, sold investor units in a Mexican development known as the El Golfo project, whose purchase price Concrete Equities greatly inflated for investors.”
– Calgary Herald Article
What kind of a person would defraud his own father out of $901,000? I’ll leave that for you to decide. While I’m glad to see him charged and his guilty plea, I am stunned at the “justice” being served here: according to this CBC article, he will spend no time in jail. Incredible – just incredible. 😡 $23 million dollars was stolen from 1200 people – much of it retirement savings – and he doesn’t go to jail. His punishment?
- Setup was fast and painless. Once I installed the Google Home app it was a smooth setup. I was especially impressed with how the app pulled the WiFi network + password from my Android phone and automatically created a peer to peer WiFi network connection with the Google Home. This is much less awkward than the Echo setup where you have to manually create a WiFi connection with the Echo, switch back to the app, and finish the setup. Google did a solid job with the setup process. The app also looks great – the Amazon Echo app is a bit rough looking on Android.
- The Google Home only has two microphones, but it’s very sensitive. My son was sitting about 20 feet away and talking in a normal voice and said “OK Google” and it heard him easily. With our Amazon Echo Dot, he would have to raise his voice. I was watching election coverage at a normal TV volume, and a Google Home commercial came on and the person saying “OK Google” triggered the Google Home in my home about 20 feet away from the TV sound bar.
- There’s just no escaping the fact that “Alexa” is less awkward to say than “OK Google”. I’d like to see Google let users change the command word to whatever we want. I’d use “Jarvis” for mine. 😉
- I was expecting to see my other Chromecast devices show up in the Google Home app. None of them are, including my new Samsung TV. They show up in the YouTube app, so it looks like Google Home is only going to see official Google Chromecast devices. 🙁 This is puzzling to me because Google is essentially creating a two-tier Chromecast ecosystem. It could be their attempt to ensure predictable quality, but it’s a let-down for me not to be able to speak to my Google Home and request it play a video on my TV. I’ve ordered a Chromecast Ultra which I’ll connect to my Samsung TV, but I wasn’t expecting to have to use it on this cast-enabled TV?
- The Google Home’s overall sound quality is excellent – significantly better than the full-sized Echo. It sounds fuller with deeper bass. Previously I had an Echo Dot connected via Bluetooth to an amazing-sounding Vizio sound bar, so even though the Google Home sounds good, this is a big downgrade in sound. The Google Home can’t connect to a Bluetooth speaker, which is an unfortunate omission in my view. It should just be table-stakes at this point for a home assistant to work through whatever speaker the user wants. Once I have the ability to cast to the Chromecast Ultra, which will be connected to my Samsung TV (which outputs audio to the Vizio sound bar) I’ll get some of that back…but it may mean the TV will have to be turned on, which is no good. This is clearly an area where Amazon has an advantage with the Echo Dot. Google needs a “Home Mini” ASAP.
Any questions about the Google Home? Post ’em and I’ll answer.