When I went to update my TomTom XL to the latest version of the operating system, I ran into a problem where the update failed and the device was stuck at a blinking screen with a red X across it. I Googled the problem a bit, but didn’t really find any good solutions. This Apple forum was trying to solve the problem, so I applied the first two suggestions, but to no avail. Following the instructions on repairing a bricked device on TomTom’s site was similarly unsuccessful.
Then I started watching the TomTom every time I ran the update, and I noticed that the little hard drive icon would stop flashing before each disconnect, not the other way around. This led me to believe the problem started on the device. When I went into the Manage my device option in TomTom HOME, I noticed the device’s memory was nearly full.
I think the problem is that the TomTom update/map is larger (or at least requires more room during unpack) than the previous version of the OS or map. In my case, the problem was solved in the following way:
In TomTom HOME, choose More->Manage my device
Make sure you’re looking at Item on my device (not on the computer)
Navigate through and delete any unncessary files (in my case deleting extra downloaded voices was enough)
Go back to the HOME menu and choose Update my device
The update should finish. If it fails, check to see if it’s failed on a different file (that means it used more space, but still failed because it ran out), and delete more files. If your device is already bricked (like mine was), deleting the application itself (see screenshot below) couldn’t hurt (in fact, this might’ve been necessary for my OS update to successfully install).
After running a Nessus scan on my VPS last night, I ran a yum update to fix a few security holes patched in newer software packages. It was pretty late, so I went to sleep after the upgrade, because everything seemed to be working fine. This morning, when I went to log in to this site’s admin dashboard, I discovered that none of my sites were working. Pings were working fine, but a quick check of the nginx error log revealed this:
2011/03/28 15:18:30 [emerg] 2661#0: eventfd() failed (38: Function not implemented)
A quick Google search turned up this forum, which indicated that the problem was related to the fact that the YUM version of nginx 0.8.53 is compiled with the –with-file-aio option, which uses libraries that were apparently not installed on my system. The solution was to re-install nginx by downloading the latest source and compiling it.
Once I did this, I changed the value of the nginx variable in /etc/init.d/nginx from /usr/sbin/nginx to /usr/local/nginx/sbin/nginx (the location of the new executable). Running service nginx restart did the trick, and my sites were back up and running.
If there’s one thing Apple understands, it’s marketing. Why would I lead a post about Windows Mobile 6.5 with this statement? Because if there’s one thing that’s holding back Windows Mobile as a viable operating system for smartphones, it’s the inability to announce important things and make updates and applications available to users. Take, for example, Microsoft’s late entry into app stores with the Mobile Marketplace–too little, and maybe too late.
Or, take the update for my HTC Ozone. I just found a link the recently-released update. Where did I find this? On HTC’s Twitter page, where it was available as a link. Not on HTC’s main page, as a news item, or even on the Microsoft 6.5 update site, which says that there is no planned date for its release. I haven’t checked Verizon yet, but it’s telling that this update isn’t hosted on a Verizon site. As long as Microsoft fails to properly inform its users about important updates, the iPhone and the Droid will all but eliminate Windows Mobile before the long awaited version 7 can arrive.