Gavin Duley's Weblog
Still nothing of interest
Photo Gallery
Weblog (RSS)
Interests
UK Farming Crisis
What's new?
Links
Contact me
External (open in new window)
Librarything profile
Snooth profile
Twitter (RSS)
Old posts:
May 2013 (1)
Apr 2013 (1)
Oct 2011 (6)
Sept 2011 (1)
Aug 2011 (1)
Jul 2011 (27)
Categories:
/books
/botany
/cars
/cars/oldcars
/computing
/computing/android
/computing/mac
/computing/unix
/music
/photography
/photography/cameras
/photography/experiments
/soporific
/stuffisaw
/stuffisaw/error_messages
/this_site
/travel
/travel/australia
/travel/australia/south_australia
/travel/france
/travel/france/burgundy
/travel/uk
/wildlife
/wine
/wine/oenology_diploma
/wine/vintage2011
Sun, 17 Jul 2011
Out of memory!
I guess this is a continuation of my Android phone review.
One thing has been somewhat annoying me about my Android phone recently.
No, it's not constantly receiving calls from my Aunt Agatha.
That's Bertie Wooster you're thinking about there.
It's this friendly little icon:
That's the one that tells me my phone thinks it's running low on space
on its inbuilt memory. Normally there is a few megabytes spare when it
starts to complain, but maybe that's not enough. It's normally
just one partition that's starting to run low, the others tend to be okay.
Of course, there is over a gigabyte free on the memory card, but that
can't be used for anything other than storing files (photos, music, etc).
Sometimes the problem goes away if I just wait for a bit. Sometime rebooting works.
I guess this suggests that temp files are at least part of the problem.
This is annoying for two reasons. One is that it means I have to keep the
number of apps I have installed strictly limited. There's an exciting
new app out and you'd like to try it out
(e.g. ... Google+)?
Forget it. I'm down to ones
that I use all the time, plus a few extra (Google Sky Map! I don't use it
often enough, but it's too good to remove).
The other is that, when the phone is low on space, I can't receive emails
or text messages. Potentially very annoying.
Can I blame Zoidberg for this?
posted at: 04:32 | path: /computing/android |
permanent link to this entry
Fri, 01 Jul 2011
Odd hostname problems
Just for the past few months, my MacBook had been assigning itself a
hostname from the network. Only odd thing is, the network is is on is my
home network, and wasn't set up to hand it a hostname from DHCP.
A quick search on google found that Mac OS X goes through a number of steps
to automatically determine its network hostname:
- The name provided by the DHCP or BootP server for the primary IP address
- The first name returned by a reverse DNS (address-to-name) query for the primary IP address
- The local hostname (set in the Sharing pane of System Preferences)
- The name localhost
Only thing is, it must have been asking my ISP's DNS servers, and ended up getting an odd amalgam of the local internal IP address and my ISP's domain, eg: 192-168-1-5.tpgi.com.au
This was a similar format to the external hostname given to my router by the ISP, which is in the form of 123-456-78-90.tpgi.com.au (where 123-456-78-90 represents an imaginary IP address 123.456.78.90).
Here's what /var/log/system/log showed:
Feb 24 05:03:42 192-168-1-5 kernel[0]: sleep
Feb 24 05:03:42 pippin kernel[0]: Wake reason = USB1
Feb 24 05:03:42 pippin kernel[0]: System Wake
Feb 24 05:03:43 pippin kernel[0]: USB (UHCI):Port 2 on bus 0x1d has remote wakeup from some device
Feb 24 05:03:42 pippin configd[34]: setting hostname to "pippin.local"
Feb 24 05:03:45 pippin kernel[0]: AirPort: Link Up on en1
Feb 24 05:03:47 192-168-1-5 configd[34]: setting hostname to "192-168-1-5.tpgi.com.au"
Feb 24 05:03:47 192-168-1-5 mDNSResponder[22]: NOTE: Wide-Area Service Discovery \
disabled to avoid crashing defective DNS relay 192.168.1.1:53
Feb 24 05:03:49 192-168-1-5 mDNSResponder[22]: Note: Frequent transitions for \
interface en1 (192.168.1.5); network traffic reduction measures in effect
Feb 24 05:03:51 192-168-1-5 Mail[215]: Type selection took over 1.000 seconds. Stopping early....
(some line-wrapping added by me)Obviously, as far as problems go, this was a very minor one. But odd, too -- it really shouldn't have been trying to get a hostname off my ISP, given that the network is behind a NAT firewalled router/"modem". Also, this address was a figment of the computer's imagination: attempting to ping it from within the network failed.
There were a number of suggestions as to how you could force Mac OS X to use a static hostname, but most of these seem to come with a warning as to why you shouldn't do that. In the end, since I am, err, "network administrator" of my home network I just gave myself a static IP address on the router, and told it to give that IP address the hostname I wanted.
This seemed to work:
Feb 25 00:04:04 192-168-1-5 kernel[0]: AirPort: Link Down on en1
Feb 25 00:04:07 pippin configd[34]: setting hostname to "pippin.local"
Feb 25 00:04:21 pippin airportd[3594]: Error: Power unexpectedly off, bailing - Apple80211GetPower() = off (0)
Feb 25 00:04:21 pippin airportd[3594]: Could not find any preferred networks; trying broadcast requests..
Feb 25 00:04:21 pippin airportd[3594]: Error: Apple80211Scan() error 82
Feb 25 00:04:21 pippin airportd[3594]: Error: __performScan() failed (82)
Feb 25 00:04:22 pippin airportd[3594]: Error: Power unexpectedly off, bailing - Apple80211GetPower() = off (0)
Feb 25 00:04:27 pippin login[3573]: DEAD_PROCESS: 3573 ttys001
Feb 25 00:04:41 pippin PubSubAgent[3593]: AgentTask: Daily Tasks took 6756 msec
Feb 25 00:05:07 pippin ntpd[14]: sendto(17.72.255.11) (fd=23): No route to host
Feb 25 00:05:18 pippin login[3603]: USER_PROCESS: 3603 ttys001
Feb 25 00:06:00 pippin kernel[0]: AirPort: Link Up on en1
Feb 25 00:06:07 pippin configd[34]: setting hostname to "pippin.home"
Feb 25 00:06:08 pippin mDNSResponder[22]: NOTE: Wide-Area Service Discovery disabled to avoid crashing \
defective DNS relay 192.168.1.1:53
Feb 25 00:06:12 pippin ntpd[14]: sendto(17.72.255.11) (fd=23): Network is unreachable
Feb 25 00:06:42 pippin login[3623]: USER_PROCESS: 3623 ttys002
I just wonder what exactly it is that it is complaining about with "Wide-Area Service Discovery disabled to avoid crashing defective DNS relay 192.168.1.1:53"...
posted at: 01:50 | path: /computing/mac | permanent link to this entry
Dead MacBook - deja vu all over again?
Well, the problems I had had previously with my MacBook had come back again. I think, even
though I did manage to revive it last time, that the hard disc still has problems. The
computer boots using the same ELive live CD, just not off the hard disc.
At the moment, it's still dead. I don't have a backup that's as up-to-date as I would like,
so I'll try copying stuff across the network before I reinstall. Interestingly, I can
still read the hard disc when I boot using the Live cd, it just won't boot off it.
Booting from the Mac OS X installer disc, I can run test on the hard disc. The test that
checks the file system reports no problems, but it keeps crashing on the test that tests
file permissions. I wonder if this is the problem, or just a symptom...
Ironically, I was trying to do a backup when it died. I hadn't plugged in my TimeMachine
disc in about 10 days, so plugged it in so it would do a backup. When, after several hours,
it had only backed up a few megabytes I decided something was wrong and so restarted it. I
then tried again. Then my web browser crashed and couldn't be persuaded to restart. I
decided to try restarting the computer, as the backup still wasn't going well.
Unfortunately, this time it decided not to restart...
posted at: 01:50 | path: /computing/mac |
permanent link to this entry
The best way to set up a new VPN...
This looks like the best way to set up a new VPN to me... :-)
(Comic from xkcd.com, with thanks).
posted at: 01:50 | path: /computing |
permanent link to this entry
Twitter!
I finally gave in and made an account on Twitter.
Its http://twitter.com/penguinoid. So far,
I'm just using it to follow other twittererererers that I find interesting for one reason or another.
I'll probably end up posting inanities myself too, though. A horrifying thought...
posted at: 01:50 | path: /computing |
permanent link to this entry
Phone review: Samsung Galaxy i5700 (aka Samsung Spica)
Originally posted: 5 July 2010
Updated: 4 Jan 2011
I've been meaning to write up a brief review of my new phone for a little
while, here is my first attempt ;-). I'll probably update this as I think of new points to add.
Introduction
I recently bought a new phone, to replace my Sony Ericsson K750i. Initially
I bought a HTC Tattoo, but for some reason I ended up with a 2G version of this
phone. I was able to replace it with a 3G Samsung i5700. Since I'm fairly familiar
with these three phones, most of my comparisons will be with these phones.
Reasons for upgrading from the K750i
I wanted:
- A larger screen and touch-screen based interface;
- The Google Android operating system, which has a wide range of useful apps;
- GPS, with the ability to run navigation software such as NavIt;
- Mobile email and web access.
- 3G (now that 4G is on it's way, I thought I should finally upgrade to a 3G phone...)
One thing I did not get from the upgrade is a better camera. The camera on the Sony Ericsson K750i is very good, and even though the Samsung has a 3.2 megapixel camera, it isn't quite as good as the 2 megapixel camera on the Sony. Both are better than the HTC Tatto, which lacks autofocus.
The phone
As a phone, it works pretty well. Once or twice, I've had it bring up the keypad whilst I'm talking on the phone and start dialling numbers, but it locks the screen after I've been talking for a minute or so which normally stops this. The way that my address book and calender are synced with my Google account automatically and wirelessly is great, and very useful.
The web browser is pretty good too, though sometimes it misinterprets my attempts to scroll down a page as zooming. I'll probably get used to this with practice, though. Both email clients (GMail and non-GMail) are good, and the push email facility with the GMail client is very handy. Both share the handicap that both force you to use top posting, which I am not a fan of. I prefer interleaved replies.
Oddly, sometimes it looses data connectivity. Sometimes the HSDPA/3G/GPRS logo disappears completely and the phone seems to be unable to access the mobile data network. Sometimes the logo remains, but the phone just fails to fetch email or load web pages. Rebooting the phone solves this problem. Recently it's simply lost all mobile connectivity once or twice, showing no network coverage in an area I know has good 3G coverage. It even claimed not to have a SIM card installed at one point. I am starting to worry about this... Again, rebooting helped.
I bought my phone off MobiCity, which means I got the phone unlocked, cheap and with a warranty. It's an overseas model, but that doesn't bother me
The Samsung i5700 next to the Sony Ericsson K750i, and the back of the Samsung i5700.
The camera
Is okay. It has autofocus, and manual control over ISO, white balance and a number of other things. Auto ISO seems to stay on ISO 100 most of the time, even when it's quite dark.
Both the HTC Tattoo and the Samsung i5700 have the ability to geotag photos (i.e., to tag photos with the GPS co-ordinates of where they were taken), though it never seemed to work for me with the HTC. It works and works well with the Samsung, though it does need to be given a few minutes to get a decent signal, or it ends up being as much as a few kilometres out.
The autofocus works well, and sometimes you can con it into taking close-up photos, though it is a bit unpredictable as to where it will decide to focus. Often, it will decide the background of a close-up photo is more interesting, and will focus on that. Again, the K750i was better here, this phone even had a dedicated close-up photography mode on the camera.
It has something claimed to be exposure compensation, but this does not seem to work as I would have expected. It appears to take the photograph, and then digitally make it darker or lighter afterwards rather than altering the exposure. Certainly, it does not work as well as the K750i. Here is a photograph where I attempted to use exposure compensation to stop the background burning out, instead, the whole photo has become somewhat grey. I guess there is a limit to what you can expect from a cameraphone.
Here is another sample photograph:
Click here for a full-sized file of the above image (note: it's 1.6 megabytes).
More photos:
Google Android
A really nice phone operating system, that seems to start to blur the line between phone and computer. Sometimes it does feel more like using a computer than a phone. Which is no coincidence, it is a computer -- but then, so was my Sony Ericsson. This is just a more flexible computer ;-).
Having access to the web and email all the time is surprisingly handy. Google Maps has been a lifesaver many, many times when I've had to try and find my way somewhere. Google's Voice Search can't understand my accent (which is somewhere between a British accent and and Australian accent).
Annoyingly, it is not easily possible for the user to upgrade the operating system unless the manufacturer releases an update. This phone was first designed for Cupcake (Android 1.5), but Samsung supplied an update to Eclair (Anroid 2.1) which came pre-installed on my phone. Now that FroYo (Android 2.2) has been released and seems to be a big improvement again on Eclair, I'd like to try it out. I can't, until Samsung releases an update, if they ever do.
There are unoffical firmwares floating around for most phones, but these normally seem to involve downloading a .zip file off some forum somewhere. Though mostly these are probably 100% safe, I tend to worry a little about malware, especially since there's no way of knowing anything about the person who put the firmware together. Chances are they're just another Anroid enthusiast, but... well, I'm always paranoid. Additionally, as these are unofficial and probably not very widely tested, there is always the possibility of voiding the warranty and killing the phone...
Also annoying is, like a computer, the software can sometimes crash. Quite a few times I've taken the phone out of my pocket only to find that it's frozen completely, and I have to take the battery out and put it back in again to reset it. Sometimes apps crash, or run really slowly, but I guess that's unavoidable.
Grumbles aside, it's a very nice system, and I've come to really like the touchscreen interface. Most things just work as you'd expect, and it's all very nicely thought out. Not quite as elegant as the iPhone system, but it does have the advantage of being a more open system. I'm not sure I'd be willing to move back to another sipler proprietary mobile phone system such as that found on the K750i again, this just seems years ahead.
GPS navigation
The phone's GPS system seems to work, and work well. Using a program called 'GPS Status', I can easily get my co-ordinates, and use the phone's built-in compass.
As noted above, I've also installed an Android port of NavIt. This mostly works well, though sometimes it gives somewhat... eccentric directions. This seems normal for GPSes, though.
My only real annoyance with NavIt is that it does not seem to like quitting cleanly. Mostly, when you ask it to quit it simply hangs. Initially, with the HTC Tattoo, I resorted to removing the battery and putting it back in again to force the phone to reboot. At one point this annoyed NavIt to the point that it stopped working, midway through a daytrip (luckily, I had a printed map with me). I've since installed SystemPanel Lite, which enables me to kill NavIt when it won't play nice. I just hope that it doesn't decide to go on strike again.
It may not be such a problem now since Google Navigation is available in Europe and Australia. I tried this whilst I was back in the UK for a bit recently. It worked okay, though the software and I had a philosophical disagreement about what 'go straight ahead at the roundabout' means. I interpreted this as taking the road at 180° to the road I was currently on. It interpreted it as continuing on the same numbered road as I was currently on, even if this was at 90° to the road I was currently on (i.e., not straight ahead). I still maintain that I am right. This does not help when you're lost due to the large number of wrong turns you have taken... Seriously, it was a big help and helped me find my way around.
I found Google Maps and the GPS to be very useful when finding my way whilst walking. I found this to be invaluable when I visited France recently, and would have got lost a lot without it (my French is too poor to easily ask for directions...). It also helped that I could look up restaurant and winery reviews. I could not look up winery websites as T-Mobile UK blocks these as unsuitable for under-18s. I still haven't gotten around to going to a T-Mobile shop and proving to them that I am, in fact, over 18.
Conclusions
So far, this has been a very nice phone to use, and has done everything I want and more. I'd appreciate a better camera, and to be able to easily get OS upgrades directly from Google, but other than that it's been very good. Battery life is not as good as the K750i (no surprise, given the screen size) but is enough for one and a bit to two and a bit days. It's better to just recharge it every evening though (if you remember!).
It can be very annoying, too. When it works, it works beautifully. Sometimes it seems to slow... right.. down -- normally when I need to look something up in a hurry, or want to show it off to someone. The way it has simply lost mobile connectivity quite a few times is also a worry. I hope it is not a faulty phone...
All in all, a very nice phone (if not 100% reliable), and good value for money.
posted at: 01:50 | path: /computing/android | permanent link to this entry
Dead MacBook
For a couple of weeks, I had a dead MacBook on my hands (flippers?). I thought I'd write up a quick weblog post, as I've not found much information on the particular problem I had. I'm not certain how common it is, but anyway...
The only symptom was this: the MacBook (1st generation, for what it's worth) would not boot. I got past the Apple start up screen, on to the blue startyp screen. This alternated between a blank blue screen, and one with a circular progress bar. And got no further. I was able to boot from both the Mac OS X DVD and from a Linux live CD -- ELive CD. This showed at least that it was not a hardware problem such as dead RAM.
Initially, I had thought that it was just a dead hard disc, but I was able to mount it okay with the Linux live cd. In addition, I was able to use Disk First Aid on the Mac OS X install DVD, which found no problems with it.
The problem seemed to have just been a software issue -- my guess is it was just a few corrupt startup files. I'm not really certain what caused this -- it could be an early warning of looming hardware problems, or it could just be bad luck. In any case, the only way I found to get it to boot was to reformat and reinstall OS X. Luckily, I had a Time Machine backup of my user files and settings (unfortunately not of the whole system), so this was easy enough. There was an option to transfer files from a Time Machine backup at the point in the OS set up where you can transfer your information from another Mac, and this worked smoothly enough.
Now I just have to hope it keeps behaving itself...
posted at: 01:50 | path: /computing/mac |
permanent link to this entry
Sun Ultra 5
Recently, I put an old 80GB hard disc drive in my Sun Ultra 5, to replace its existing
10GB one. The 10GB one was getting a bit old, and was starting to seem a bit small anyway :-(
The Sun complained loudly when I first booted with the new drive, as it did not have the
appropriate label for a Sun disk. A quick Stop+A then boot cdrom allowed me to boot off the CD-ROM fine,
so I could run the Debian lenny installer.
The installer seems much the same as last time I used it. The main problem I had this time
was in configuring X. For some reason, the installer only asked me questions about my keyboard
and not about my monitor or graphics card. X11 completely failed to work after install.
I soon found out what the problem was by asking a question on the
Humbug general mailing list.
The issue here, though, was changes made in the Linux kernel version 2.6.25 and 2.6.26
apparently broke some things which Xorg depends upon. Going back to version 2.6.22 got rid of the issue,
and Xorg now works fine. The only problem now is still a futex bug that causes firefox to quit
spontaneously after running for a few minutes.
In any case, it's good to have my Sun system back up and working again. It may be "only" 333MHz, but it still
works pretty well...
posted at: 01:50 | path: /computing/unix |
permanent link to this entry
