Saturday, April 25, 2015

Google Calendar not syncing to Nana's Nexus 7

For some reason, Google Calendar on Mum's Nexus 7 has a long-standing bug where it spontaneously forgets how to sync her calendar data.  Since I'm on the other side of the country, and I don't use Android at all these days, here are the notes on how to fix the issue.
  • Open Settings
  • Select Storage
  • Select Apps Data and Media
  • Sort Apps By Name (using the right-hand menu)
  • Scroll down to Calendar
  • Remove Data
  • Scroll down to Calendar Storage (this should be the next one on from Calendar)
  • Remove Data
Make sure you do both Calendar and Calendar Storage!
  • Go back to top of Settings
  • Under Accounts, go to Google Accounts
  • Select Sync (using right-hand menu)

Friday, November 21, 2014

The human brain is really good at seeing patterns...

Dear Penthouse, I would never have thought something like this might happen to me.

I got into work this morning, and I had forgotten to rinse out my coffee cup the night before so I needed to clean it.  Imagine my surprise, however, when I looked down into it and saw someone looking sternly back at me.

Don't take my word for it, though.  Here is iPhoto agreeing that there is a face in there, you can't argue with computer software...

I'm pretty sure its Alan Moore, famed comic artist and well known magician. Go take a look at him on Wikipedia.  But what is the author of V for Vendetta doing in my C for Coffee Cup? Sadly, we'll never know. His unnerving visage made me feel so guilty that I washed the cup immediately, well immediately after taking a few photos.  Here's one more close-up.

Thursday, October 17, 2013

I owe Optus an apology

We just switched our Optus Cable service across to their "speed pack" which supposedly gives us 10x the bandwidth.  To do so, we needed to upgrade the modem from the old Motorola Surfboard 3100 to a Netgear CG3000 which has a built-in router and does Wifi.

Our home network is more complicated than normal but I copied across all the appropriate config, rebooted all the computers and it all just worked.  Well, almost all.

For some reason, Pauline's email would not connect.  Nor would Catriona's.  It didn't matter how I tried, it just wouldn't work.  When I tried configuring new accounts, they wouldn't work either.

I probably spent half an hour (over a few nights) ranting to the guy on support that "I do networking for a living, I can see that its your mail server not responding to POP/SMTP when I use TELNET to the appropriate servers and do the protocol by hand".

Today, sheepishly, I realise that "hmmm, the IP address we are using is a class-B, but the subnet mask we have configured is a class-C".  Surely that couldn't cause this symptom, it didn't upset the old modem.  Hmmm, this is a modem *and* a router.  Oh dear...

So, I fixed our network config to use legitimate class C IP addresses, Pauline pushed the Get Mail button and down came her mail.  Problem solved.

My only excuse is that my old router allowed me to configure a proper class-B subnet mask - the Netgear has the subnet mask locked at class C, but I didn't pay attention when I was entering the numbers. Tomorrow, when Optus Support rings me back, I have to take hat in hand and admit my error.

The moral: if you want to use anything other than the default 192.168.1.* network that your modem manufacturer, or your ISP expects you to use, make triply sure that you have configured it right.  Because getting it wrong is hellishly difficult to debug, especially for the poor bastard at the other end of the phone that doesn't know how clever you think you've been.

Friday, July 19, 2013

unexpected precompiled header, simply rerunning the compiler might fix this problem

This post is about Microsoft's answer to the IT Crowd and their "did you try turning it off and on" running gag.

For years, we (at work) have been plagued with this particular error that seemed to happen spontaneously, hang around for a while then disappear, and today (with the help of Google) I've been able to track down an actual answer.

Microsoft explains the embarrassing truth here.

In a nutshell, precompiled headers are implemented cheaply as a straight memory dump complete with physical memory addresses.  When the compiler subsequently tries to read them back, ASLR has potentially scrambled it's little brain.

There are lots of fixes mentioned around the net, of varying levels of quality and security.  Microsoft has a hotfix but it only solves the problem for Visual Studio installs - we build using the Platform SDK.

For me, the sanest approach was:
  • download and install EMET from here
  • use EMET to disable "MandatoryASLR" and "BottomUpASLR" on the C compiler (cl.exe)
This leaves you with ASLR enabled for everything but the C compiler which doesn't cope.

Note, this has no impact on the output of the compiler - your programs will still be ASLR-enabled or not, depending on what switches you pass on the command line.  All we are doing here is fixing the actual compiler itself...

I hoped I'd never have to revisit this post, but today I had to. Looks like EMET can cause quite a bit of damage when you run it.

I tried using EMET 5.2 and it did resolve my problems with the C compiler.  As collateral damage, however, it took out Microsoft Office, AutoCAD 2011-2016, and even Internet Explorer.  Every one of them reported a vanilla error message "Attempt to access invalid address".

This looked to me to be related to either Data Execution Protection or perhaps to ASLR.  However, even though I completely disabled both of those features (through EMET), it didnt' help.  I've restarted so many times today you would not believe it.  Uninstalling EMET changed nothing.  I sat and manually uninstalled every Windows Update that had been applied in the last 48 hours and still no joy.

Eventually this post on the Microsoft Forums pointed me at an obscure registry entry and lo, it fixed the problem.  It would appear that EMET automatically puts in registry entries when it is installed, and does not remove them when it is uninstalled (no surprise there).

So, the fix was to go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options

and locate the application I was trying to use.  I removed the troublesome keys and voila, my apps work again.  (Actually, for many, I just removed the value for MitigationOptions which was 0x0000100)

Note: this is not something that you should attempt lightly.  No warranty implied or assumed.

Wednesday, May 1, 2013

Nexus 7 vs iPad Mini

Yet another comparison between the Nexus 7 and the iPad Mini. This is going to be my collection of notes to myself of stuff I notice as time goes by.

Physical Size

A number of people have commented that "its much bigger" (the iPad) seeing two devices side by side with their screens on, and it feels like the aspect ratio (width/height) of the iPad is more pleasing than the Nexus.


The screen on the iPad seems larger, which is no surprise because it is about 3cm wider and 2cm taller. However, I think the secret is that the iPad only shows 4 rows of 5 icons whereas the Nexus crams in 6 rows of 6 icons.

In terms of resolution, my old eyes aren't really picking a difference.

What is odd is that the iPad feels more natural to hold in landscape where the Nexus feels better in portrait.  Perhaps that's because it was only recently that Android coped properly with a portrait orientation launcher.  Or it could be the slight different in screen proportions.  The iPad Mini really feels like the bottom half of a "real" iPad, and for the most part, that feels like enough.


Both devices have context-specific keyboards that they flip in as required.  Only the Nexus is stupid enough to leave the '@' key off the URL keyboard, making it impossible to search for, say, in the Google Chrome browser.  This is still true at Android 4.2


Big win for the Nexus - because it has a GPS chip on-board, and Google Maps can make large chunks of the mapbase available offline, you can prepare for a days walk around Paris by pre-caching the map, then relying on the on-board GPS to let you know where you are.

Stop press:  I took it out for a walk today and it looks like the offline'd maps had un-offlined themselves.  I stood in the Camberwell Market waiting for the Maps app to wake up, and it never did.

And it looks like Apple have done something spooky where they seem to be able to get location *without* a GPS chip onboard, if you are in sight of civilisation.  This probably depends on how well they have mapped the area you are in, but for wandering Paris, I'm wondering if the iPod Touch won't be sufficient.


Comparing the iPad Mini against both my iPad1 and the Nexus, the Mini does not seem to have the same range as the others.  There are rooms in the house where the Mini sees no signal while the other two get enough to work.

Stop press: buying an Airport Extreme made it possible for the Mini to see the farther rooms in the house. However, the Nexus does not see the 5GHz bands, only the 2GHz ones, whereas the Mini is fine with both.

Calendar Application

To be fair, by the time I wrote this section, I don't own the Nexus any more, it moved on to my mother who is 80% happy with it, except when it goes stupid for no apparent reason.

iCloud synchronises all my contacts & calendars without causing any grief whatsoever across multiple devices. (iPod/iPad/iPad Mini)

Android has dropped all knowledge of Mums Google Calendar multiple times now, and Internet Wisdom suggests that the fix is to "delete the local calendar data, disconnect syncing, reconnect syncing and wait".  Not something that the novice user wants to do.  In fact, there are a disturbing number of posts that suggest that when these things go wrong, "reset the device and reinstall everything from scratch".

Saturday, January 26, 2013

mDNSResponder running rampant

So, this morning I took at look at my Mac and noticed that Little Snitch shows that someone is doing almost constant network traffic out.  Looking in the Network Monitor, it appears that mDNSResponder is sending almost constantly to our DNS server.

Useful tip 1:  To debug what mDNSResponder is doing, use the following:

sudo killall -SIGUSR1 mDNSResponder

and then take a look in the Console log.  This is a toggle so do the same command to disable the extended logging.  (Thanks to - I could have just read the man page (man mDNSResponder) but who has time to read local documents when you have Google?)

Some internet pages suggest you can get this symptom if you have a misconfigured DNS server that does not report errors correctly. This does not appear to be the problem for my ISP (Optus).

In my case, the log showed messages like this:

26/01/13 9:55:50.819 AM mDNSResponder[40]:  24: DNSServiceQueryRecord(35000, 0,, PTR) START PID[264](LogMeInGUI)
26/01/13 9:55:50.820 AM mDNSResponder[40]:  24: Error socket 72 closed  00000000 00001005 (0)
26/01/13 9:55:50.820 AM mDNSResponder[40]:  24: Error socket 72 created 00000000 00001006
26/01/13 9:55:50.820 AM mDNSResponder[40]:  24: DNSServiceQueryRecord(35000, 0,, PTR) START PID[264](LogMeInGUI)
26/01/13 9:55:50.820 AM mDNSResponder[40]:  24: Error socket 72 closed  00000000 00001006 (0)

Hmmm, LogMeIn?  Don't I have that switched off?

I checked the LogMeIn control application and yes, it definitely shows as "Off" - that's the normal state for me.  On a hunch, I turned it "On" and immediately the mDNSResponder traffic ceased.  Turn if "Off" and mDNSResponder again starts sending.

So, LogMeIn, when turned off, generates more network traffic than when it is turned on and idle.

I've reported it to - we'll see what happens.  For now, I'll probably uninstall.

Wednesday, July 18, 2012

Never fly Philippine Airlines

It took some doing, but Philippine Airlines have supplanted United in the "I will never fly them again unless there is no other choice" stakes.

On our most recent trip, three out of four legs of the journey were just too unpleasant, and while the last helped to smooth over the annoyance, the sum total was best summed up by Catriona who said "Dad, next time we fly, can we *not* go with the cheap airline?"

Picture this: You get onto a plane, about to take a 10 hour flight, expecting to see those in-seat monitors.  What you get is a poorly focussed overhead screen.  And a bunch of children looking really disappointed already.

The announcement comes over to "please close your windows - if you want to read, turn on your overhead lights".  You push the button.  Nothing happens.  You sit in the dark with your Kindle wondering how you're going to kill the next 10 hours.

You open the window and let the light in. A flight attendant comes and asks you to close it.  You explain that the light doesn't work.  She goes away.

The purser comes and asks you to close it.  You explain that the light doesn't work.  He shrugs.  You show him that in fact the light control actually comes out of the seat showing exposed wiring.  He laughs and goes away.  You hope that the wiring in the cockpit is in better condition.

Repeat for two more flight attendants.

For an hour you try to watch the blotchy screen showing some movie.  The movie stops.  And restarts from the beginning.  This happens several times during the flight.  They do show snippets of an insane American game show where people get hurt trying to climb over/under/through a watery obstacle course.

After 10 hours, you get off in Manila.  You are escorted up to the departures lounge, and go through security having your bags and shoes X-rayed, and being patted down.  Loo break, have a tiny ice-cream, then go to the gate (approximately 20m away from where you were last scanned) where you have to go through security again, having your bags X-rayed and being patted down.  Presumably this is because you might have visited the gun dealer in the departure lounge.  At least, you can keep your shoes on this time.

So, now you are in the "secure area" - that is, a part of the same floor that's cordoned off with those ribbons you see in bank queues. Once inside the "secure area", you realise that there are no seats left so you sit on the marble floor, only to realise that the airport roof is leaking and the floor is wet.  But it's ok, that's to make sure you don't dehydrate -- it must be, after all, it's the only source of water you have access to until your flight.  Unless you want to go through security again.  Remember, you can't bring more than 100ml into the "secure area" so don't think about going out and buying drinks for the kids.

Still, at least this next Manila to Los Angeles flight will have personal screens, won't it?  No, you probably only wanted to just sleep anyway.  This time we're split across three rows, with me behind the three kids and Pauline somewhere up frontish.  I get to share the row with a couple who were, well, large.  For the entire trip, the voice in my head was that of the male hippo in Madagascar 2 saying "Girl, you're large. You're chunky!"

(realise that I've been switching from second person to first person - give up dreams of being a novelist)

But you're in LA now - have a holiday, and try not to think about the flight home.  If you have to think about Manila, think about how cheap the ice-creams were.

Fireworks in a carpark on July 4th.
Universal Studios.
Legoland again.
Fly to Washington.
Smithsonian x 2
Too many burgers, too many cokes, this is holiday living.
Drive to Pennsylvania
Climbed on by niece and nephew

Too soon it's over and you are winging back from Washington to LAX arriving at about 2:30pm and having to wait till 10:30pm, thinking "I'll check the suitcases and then grab a bus somewhere outside the airport".  Bzzzt, sorry, Philippine Airlines don't begin checking in until 6:45pm.  Ok, this one isn't completely their fault but if the whole trip had been with them, I'd have been able to check the bags in in Washington.

Ok, we're back - side trip was acceptable though it was a little tricky dragging 3 suitcases and 5 people each with backpacks onto a peak-hour city bus.  Again, can't blame the airline for that.

At about 10:45, learn that "because the plane is lighter than we thought, we don't want to stop in Guam to refuel".  "Hooray" shouts the crowd.  "... so, we'll be delaying the flight until 1:30am so that when we get to Manila Airport it will actually be open."   "Boo!" shouts the crowd.  "... so, here is a $12 voucher that you can use at any of two eateries here in no-mans-land behind security -- no, they won't work anywhere else".

(Hmmm, and yet the airports Facebook page says "always open" - sigh)

Get on the plane and discover that the little man at checkin who told us that the last side-row of seats reclines, was lying.  They don't.  They would block the exit door. He had deliberately moved us there to keep us altogether and we explicitly said that we would only go there if they reclined.  So he said "sure they do".  First rule of airlines - get the passenger to be someone else's problem, preferably at another airport.

We complain to the purser and get the girls moved forward about 40 rows, leaving us boys at the back.  Next to a walrus.  I don't know what else to say, just try to imagine someone who can snore loud enough to be heard over an airplane engine.  Thomas can't take it and moves forward with the girls, leaving Jonathan and I with more room.  And a noisy walrus who, to be fair, eventually shut the hell up.  But that just made it easier to hear the scary rattling noises from above.

Try to lift the arm rest to use that extra space?  Aha, no, they have that covered too, they only raise about 2/3 of the way making it impossible to spread out.

Well, at least this time the plane has those little screens.  Look, Movies and TV. Hmmm, movies aren't anything special, what do they have on the TV - *one* program.  One! And for irony, it's "a documentary on aviation technology".  After the flight, you learn that in fact the people over on the right hand side of the plane had dozens of TV shows to watch.  Or perhaps it was "front" vs "back".

Watch a couple of movies. This part was ok.  But it's what we were expecting on every leg.

When the flight is just about over, we discover that in fact when they moved the girls, there were three empty seats behind them - they could have moved us all, they just didn't think we'd want to.

Back at Manila.  Back to double-goes on the security ride.  At least, this time it wasn't raining.

Notice that the security area has been set up so that the guy looking at the X-ray screen has to shade it with his hand the entire day, because they placed the screen such that the sun shines directly on it through wall-to-ceiling windows - what a shame they couldn't have anticipated, while designing the airport, that the sun actually shines.  This just reinforces the notion that all of this security crap is based on the notion that the guy before you was incompetent.  Not to mention the tautological sign that justifies it by saying "Philippine law requires that all bags be inspected when passing through inspection points".  So, if they hadn't put an inspection point in, there would have been no need for an inspection point. "It's a bypass, ya gotta build bypasses".

One last plane.  One last chance for reasonable entertainment.  Why does the screen say TV but doesn't mention Movies?  And why is there so much "Glee" in the TV section?  After four reboots (did you know those things run Linux? We do now), the Movies actually show up.  So, the final leg of the trip is tolerable.  Not surprisingly, it was the shortest of the bunch at less than eight hours (Manila to Sydney is faster because it's downhill all the way).

Oh, by the way, you know how nice a warm pork bun can be?  Not surprisingly, the "warm" isn't optional - a cold pork bun snack really doesn't do anything for me, but they served it anyway.

All told, there weren't any catastrophes, no lost bags, no falling out of the sky. Just a series of unpleasant experiences which left you with the feeling that "this is an airline that is just a bit manky".

Your mileage may vary.  But I've flown Singapore Airlines, I've flown Air New Zealand, I know it can be done a lot better than Philippine Airlines did on four flights out of four.