All posts by Tim Anderson

Review: Seagate Wireless Plus combines hard drive and wi-fi for storage on the go

Need more storage for your tablet or smartphone? If so, the Seagate Wireless Plus could be just the thing. In a nutshell, this is a 1TB USB 3.0 external drive with battery power and a wi-fi access point built in. Attach it to your PC or Mac and fill it with stuff: a zillion MP3s, or a pile of videos, or pictures, or boring business presentations, or whatever you need. On the road, you power up the drive, connect your mobile device to the built-in wi-fi, and play what you want – though note there are a few complications, of which more below.

image

In the box you get the drive, a USB mains adaptor, a USB port that attaches to the drive, a USB 3.0 cable, and a brief getting started manual.

To be clear, there is a protective cover on the end of the drive which pops off to reveal what looks like Seagate’s GoFlex port. Another piece plugs into this, converting it to a USB port. Slightly awkward, because you may well lose the protective cover and end up having the USB adaptor permanently attached.

image

Setup is a matter of charging the battery and then connecting your mobile device to the drive’s integrated wi-fi access point. By default this is an unencrypted open connection, and if you intend to travel with the unit I recommend setting a password, which converts it into a secure encrypted connection.

Next, you download the free Seagate media app for iOS or Android, at which point you can view the contents and playback media such as music and video. What if you have a mobile device other than iOS or Android? Hang on, all is not lost.

The inherent problem here is that connecting storage to a mobile device is not as simple as on a computer, where it just appears as another drive, especially on Apple’s iOS which does not directly expose a file system to the user. This is the reason for the Seagate Media app.

Second, the obvious problem with connecting to a dedicated wi-fi access point on the Seagate drive is that you will no longer be connected to any other wi-fi network and therefore may be disconnected from the internet, or forced to use your data connection.

Fortunately Seagate has a solution, called “concurrent mode”. You use Seagate’s app to connect your drive to a second wi-fi network, such as your home wi-fi, and then your internet connectivity is restored.

While this mostly works, it is an inconvenience, since if you are out and about you will need to do this for any new wi-fi connection point you want to use. Further, as soon as you turn the drive off (or the battery runs out) you will have to connect your mobile device separately. If you then later want to reconnect to the Seagate, you have to change the wi-fi settings on the mobile again, so it is a little bit of hassle.

I used the drive on both an iPad and an Android phone, and found the setup fairly straightforward, though the Android mysteriously needed restarting before it worked properly. Playing media from the drive via the app works fine for video, images and music.

If you have a device that is neither Apple nor Android, you can still use it by connecting the wifi on the device to the Seagate, and then browsing to a mini web server on the drive. The question is: where to point the browser? Help was not helpful on this point, suggesting a wirelessplus URL that did not work at all for me, but I noticed that the network was in the 172.25.0 range, took a stab at 172.25.0.1 and found that it worked. Using a Nokia Windows Phone, for which there is no Seagate app, I could connect to the device, stay on the internet, and still easily play the media. Here is the browser view on Windows Phone:

image

You can also access settings from the browser and check status:

image

That said, as I connected various devices to the Seagate I found its behaviour increasingly unpredictable. On the iPad I got a mysterious message saying I was connecting through another device and should connect directly, even when I was connected directly as far as I could tell. Sometimes you lose internet connectivity and the second network connection needed to be kicked back into life through settings. You are meant to be able to have up to eight devices connected, with up to three streaming media simultaneously, but maybe this is optimistic.

The wi-fi complications are not Seagate’s fault, but inherent to providing additional storage for mobile devices, though I wonder if the firmware could be improved a bit.
Connecting the drive to a computer over USB disables the network connectivity but is otherwise straightforward. The drive is formatted with the Windows NTFS format, and a read-write NTFS driver is supplied for Mac users. Apparently you can also convert the drive to Mac HFS+ format though I did not try it. It uses a fast USB 3.0 connection when available, which is a big plus since it is much faster than USB 2.0.

There is some sync software for Windows supplied but I do not really see the point of it; personally I prefer simply to copy stuff across as needed.

According to the manual, the drive takes 3 hours to charge fully, and then has about 10 hours battery life streaming, or 25 hours standby, which is enough for most journeys. If you fancy using this on a flight, note that some airlines may not allow wi-fi to be enabled which would prevent use of the drive, other than via a laptop and USB.

Despite the fact that it is not hassle-free, I rate this drive highly based on its generous 1TB capacity and the fact that it also works fine as a standard USB 3.0 external drive, making all the mobile and battery-powered capability a nice bonus. If you need serious extra local storage for a tablet or smartphone, I cannot think of any better option.

That is the question though: do you need extra local storage for a mobile device? Internet-based storage like Dropbox, Skydrive or Google Music is more convenient, provided of course that you can connect. Most mobile devices come with built-in storage that is enough for a few videos or a fair amount of MP3 music.

There are certain scenarios where Wireless Plus will be useful, but I am not sure how common they are for most people.

Update: The Wireless Plus can also be used as a DLNA server and I have successfully used this feature both on the iPad (you can download a DNLA client from the app store; I used 8player Lite) and on Windows:

image

Can you use this then as a standalone music server? Yes, though it is a shame there is no option to join the Wireless Plus to your existing network directly. I am guessing there is a way of hacking this though, if you can figure it out. It is not too bad, since once it is connected to your network using concurrent mode, other devices on your network can see it.

You can also play media from the Wireless Plus to Airplay devices such as Apple TV.

Review: Bayan Audio StreamPort Universal Bluetooth streamer

Problem: you want to play audio from your mobile device on powered speakers or through your home hi-fi. Usual solution: connect a cable from the earphone socket on your device to the powered speakers or to an input on your hi-fi. That is a little fiddly and untidy, so how about a wireless solution instead?

image

This is where Bayan Audio’s StreamPort Universal comes in. This little USB-powered box in effect enables any audio system for Bluetooth. Simply connect the output from the StreamPort to your hi-fi or powered speakers, using either a 3.5mm jack socket or right and left phono sockets, and then pair it with your mobile device. Audio output is then redirected to the StreamPort and you can enjoy the music at full quality.

imageimage

In my tests the StreamPort worked exactly as advertised – well, nearly. You put the StreamPort into pairing mode by holding down power for 8 seconds. A Sony Experia T Android phone connected easily, I fired up Google Music, and was able to play one of thousands of tracks at what sounds to me very decent quality.

Next I tried an Apple iPad 2. Again, it paired first time. I started BBC iPlayer and was able to watch a recent broadcast with excellent sound over hi-fi speakers. A Windows 8 tablet also worked well.

You can pair up to four devices, but only one at a time will be active. If the “wrong” device grabs the connection, turn Bluetooth off on that device. If you pair a fifth device, it will simply forget one of the other pairings.

So what didn’t work? Well, the StreamPort supports NFC Secure Simple Pairing, which means you can connect a device simply by tapping it. I tried with the NFC-enabled Xperia T and got the amusingly polite message, “Unfortunately content sharing has stopped.” I am not sure whether this should have worked, but I put the failure down to this being a relatively new protocol; perhaps it would work with the newer Xperia Z. Note that Apple devices do not currently support NFC at all.

I also experienced very occasional audible stuttering, which is unfortunate, though most of the time everything was fine. Still, this could be annoying. I heard it on music on the iPad and on the Windows tablet, but BBC iPlayer was fine. I guess it may depend on the underlying bitrate and how much data is being transferred. I am reluctant to pin the blame on the StreamPort; rather, it is a common problem with Bluetooth audio, it may or may not be something you experience, and shows that the implementation of the standard (or the drivers) on devices has a little way to go before it is rock-solid everywhere.

Is the quality as good as it is through a cable? Generally not, though how noticeable the loss of quality is in the realm of “it depends”. It is a digital connection, so in some circumstances (if the analogue output is poor) it could be better.

Bear in mind that if you are using a mobile device as the source, you are probably not looking for the best possible sound quality; but you will probably be pleasantly surprised by how good it can sound.

The actual quality will depend first, on the quality of the source, and second, on what audio protocol the source negotiates with the StreamPort. Bayan states that best quality will be from Bluetooth devices that support aptX compressed audio. The protocol used is generally invisible to the user, so all you will notice is how good it sounds. Generally a more recent device will sound better. At a minimum, your Bluetooth source has to support version 2.1 and the A2DP profile, otherwise it will not work at all.

image

In the box is the StreamPort, two audio connection cables, a USB cable for power, a USB mains adaptor, and a brief manual.

Two final thoughts. One is that Apple has its own AirPlay system for wireless audio; but thanks to the rise of Android we are seeing more Bluetooth audio devices coming on the market. Since Apple devices work with Bluetooth audio, but Android and other devices do not work with AirPlay, this is an obvious response to demand.

Second, it is reasonable to expect Bluetooth audio to be built into an increasing proportion of new playback equipment. Of course, in this case you will not need the StreamPort. It is not that common yet though, which makes the StreamPort a handy accessory. Recommended.

Review: Olympus LS-14 24/96 audio recorder with Tresmic mic

The Olympus LS-14 is a portable digital recorder with integrated microphones. It supports recording at up to 96 kHz/24 bit. Although you might not hear much difference between this and CD quality (44.1 kHz/16-bit), the higher resolution is still worth it if you want to do any post-processing, as it gives you some headroom for processing without audible loss of quality.

image

In the box is the recorder, a combined stand/clip which screws into the device (the screw hole is also the right size for direct tripod mounting), a zipped bag of reasonable quality, the usual USB cable, getting started manual, and batteries.

image

The unit feels well made, though after a couple of days some plastic broke off the head of the bolt that attaches the clip. Glued back and seems OK, but annoying.

In the Olympus range, the LS-14 falls between the pro LS-100 with multi-track recording and XLR connectors, and the budget LS-12 which is similar to the LS-14 but with only 2GB internal storage and lacking some features like the third microphone.

There is a brief getting started manual, but I recommend you connect to a computer and copy the detailed manual from the internal storage as otherwise some features are a little perplexing (I thought the metronome feature was broken at first).

image

The device seems well made but is not particularly small by today’s standards: 52.5 x 138.7 x 23.5mm. Not really bulky, but seems large compared to my Philips voice recorder, for example.

The most notable feature is the third microphone, which sits in the centre on the end of the unit. Olympus calls this the Tresmic mic, and it is the recording equivalent of a subwoofer, capturing low frequencies that would otherwise be missed.

The quoted frequency response of the internal mics is 20Hz – 20kHz with the Tresmic mic, or 60Hz – 20kHz without.

Unfortunately the level of the third mic is not separately controllable, though you can switch it off, and I found the bass tended to be excessive with it engaged. On the other hand, if you want to capture those low sounds you will be grateful for it, and I guess you can tweak the EQ later.

Recording formats range from 64kbps mono MP3, if you want to record for many hours and don’t care about the quality, to 96/24 PCM which will fill up your 4GB internal storage rather fast (about 1.5 hrs). Still, you will want this for pro recording.

There are three recording modes. In Smart mode, you press record, it spends 30 seconds adjusting the level automatically, and then starts recording. In Manual mode, you press record, adjust the level using the on-screen meters, then press record again to start. In Quick mode, you press record and it start, using the current levels.

There are a couple of extra features. In tuner mode, you can use the device to tune an instrument. It shows the note you are playing and whether it is sharp or flat. In Metronome mode, which only works during a recording, two lights flash and a tick sounds through the earphone output; you can adjust the timing of the beat.

On the right-hand side of the unit are microphone (with plug-in power) and line-in inputs, as well as an SD card slot (up to 32 GB). On the left-hand side is the USB connector, headphone out, and input for a receiver for the optional wireless remote.

Using the settings, you can set mic sensitivity, limiter (automatic level control) and a low-cut filter at 100Hz or 300Hz.

There is also a pre-recording feature. In this mode, the unit is constantly recording, and when you press Record it will capture the previous two seconds.

Various editing features are supported, such as trimming and dividing files, though since you are more likely to edit on a computer these are of limited value in my opinion. You can also overdub a file, provided it is in 14.1/16-bit format, though again, why not record the new track separately and combine on a computer later?

So how is the sound? In my tests, excellent, thanks to the high quality of the integrated microphones and electronics. It compared well to a decent external Sony mic, though that sounded good too with not too much noise from the mic preamp. That said, as noted above, personally I preferred the sound without the Tresmic mic which is rather a waste of the most distinctive feature of the LS-14.

I made some samples so you can hear the impact of the Tresmic mic for yourself:

Internal with 2 mics

Internal with 3 mics

External mic

Olympus states a maximum external sound pressure of 130 db making this suitable for recording live concerts; set the sensitivity to low and adjust the levels carefully.

The LS-14 microphones are rather sensitive to wind, so beware using it as a hand-held microphone or outside. No windjammer accessory is currently listed, though maybe the one for the LS-100 would work; test before you buy!

It is worth noting that the built-in microphones form a significant part of what you are paying for in the LS-14, so if you intend to use an external mic most of the time it is not good value. I am conflicted on this. I prefer external mics, partly because you can choose the right mic for the purpose, and partly because built-in mics inevitably pick up noises if you operate or handle the unit while recording. On the other hand, having a single device is convenient and that sometimes counts for more.

The supplied batteries are not rechargeable, though Olympus quote recording time of 43-46 hours which is not too bad. You can use the USB port for external power. I would have preferred rechargeable batteries and USB charging.

A somewhat hidden feature: you can change the USB connection type to “composite” in which case you can use it with your PC as a USB microphone. Probably not that useful.

For certain types of usage, I think this device is great. For example, you could use it to record school concerts, your live band or music rehearsals. The high quality microphones and high-res PCM format mean you will get great results, though I am wary of the Tresmic mic as mentioned above; try it with or without.

It is also handy as a high-quality recorder for things like capturing vinyl records to digital and works well with external microphones.

Negatives? A little bulky, sensitive to wind noise, batteries not rechargeable, and Tresmic mic prone to make boomy recordings. None of these are showstoppers, but worth noting.

 

First sight of Firefox OS at Mobile World Congress

Alcatel OneTouch has a preview of its Firefox OS smartphone on display at its stand here in Barcelona.

3.5” HVGA, 1Ghz CPU, 3.2Mp camera, 256Mb RAM, 180Mb internal storage, MicroSD, 1400mAh battery.

image

and to give you the scale

image

The phone looks ordinary, but bear in mind the Mozilla philosophy which is more geared to universal, open access than to high-end smartphones for the few.

Several well-known names have signed up, but that in itself does not mean much. What counts is the extent of that commitment. A device like this one looks more about “let’s put it out and see who bites” rather than serious investment.

The app story (HTML 5 based, naturally) is key and I will be investigating later.

Fixing Windows blue screen using Internet Connection Sharing in Windows Phone 8

I have been reviewing a Nokia 620 – an excellent budget smartphone.

Yesterday I was travelling and used the Internet Connection Sharing feature. This is one of the best features of Windows Phone 8, allowing you to use your mobile data connection as a wireless hotspot.

Unfortunately it did not work properly. It could connect for a bit, then the PC (a Samsung Slate running Windows 8) would crash. The error is Driver_IRQL_Not_Less_Or_Equal and the driver mentioned is netwsw00.sys.

The fix is easy (once you know). Reboot, and before you connect to the hotspot (or before it crashes), view the properties of the wireless connection. Click Advanced, and enable Federal Information Processing Standards (FIPS) for the connection.

image

Presto! everything works.

If you want to know what FIPS is, see here. The question of what difference the setting makes though is not known to me, though there are some clues here.

Fortunately you do not need to know, just make the change.

I am glad Windows Phone 8 is FIPS compliant (why not?) but disappointed that some issues with Windows 7 and 8 (I repeated the problem in Windows 7) and this hotspot feature, possibly also involving third-party wireless drivers, causes such a catastrophic and repeatable crash.

Review: Nokia Lumia 620, a winner when the price is right

Nokia’s Lumia 620 is now widely available in the UK, and was offered recently at just £120 (including VAT) by O2 on a pay as you go deal (which means that the amount of operator subsidy is small). That struck me as an excellent deal, especially as I already have an O2 sim, so I got one to take a look.

image

The Windows Phone with which I am most familiar is the first one Nokia produced, the Lumia 800, which is still widely available at a similar price to the 620. The 800 is a beautiful phone with a high quality feel, though my early model has a dreadful battery life and suffered from charging problems (going into a state where it could not be charged without much coaxing) until at last a firmware update seemed to fix it.

The 620 is lighter and very slightly smaller than the 800, and feels more ordinary in design and manufacture. On the other hand, it is up-to-date and runs Windows Phone 8, whereas the 800 is stuck with Windows Phone 7.5 or 7.8. The 620 also benefits from a Qualcomm Snapdragon S4 Plus system chip, 1Ghz dual core, versus the 1.4Ghz single core Scorpion and MSM8255 Snapdragon in the 800.

In the picture below, the Lumia 620 is on the left and the 800 on the right.

image

Do not be misled by the apparently faster clock in the 800 (1.4 Ghz vs 1.0 Ghz). In practice, I found the 620 performs much better than the older single-core CPU. Here are my Sunspider Javascript results:

  • Lumia 800: 6987ms
  • Lumia 620: 1448ms

I also have a Lumia 820 on loan. This is the true successor to the 800 and has a gorgeous 4/3″ AMOLED display plus a Snapdragon dual-core 1.5 Ghz chip. It completed Sunspider in just 910ms.

Still, the 820 is around £350 on pay as you go deals, more than double what I paid for 620. It is in a different high-end market, whereas the 620 is in an affordable category alongside dozens of budget Android phones like the HTC Desire C, Samsung Galaxy Ace 2 or Sony Xperia U. If Microsoft is to make real progress with Windows Phone 8, it has to be competitive here as well as at the higher end of the market.

You can see how Nokia has reduced the cost of the 620. The screen is TFT Capacitive, not AMOLED, and looks dim and small next to an 820. The battery is a small 1300 mAh affair, slightly smaller than the one in an 800. The side buttons feel like cheap plastic.

That said, I would rather focus on what the 620 does have, including A-GPS, Bluetooth 3.0, microSD card slot, 5MP camera with flash, front VGA camera, NFC (Near Field Communication) support, accelerometer and compass.

Two significant advantages over the old Lumia 800 are the removable battery (so you can carry a spare) and the microSD card slot, supporting up to 64GB of additional storage.

One thing I noticed with the 620 is that charging the battery is super quick. I have not timed it yet, but it charges considerably faster than the 800.

Battery life when on standby is substantially better than the Lumia 800. With light usage and wi-fi off, I am getting more than 2 and half days.

image

There is 512Mb RAM and 8GB storage; reasonable at this price. The Lumia 610, predecessor to the 620, had only 256Mb RAM which caused app compatibility issues.

Getting started

The out of box experience for me was pretty good. I put in my O2 sim, which worked without any issues. The setup asked for my Microsoft account and password which also worked, though as is typical with Microsoft, I found myself having to enter this several times more when setting up the SkyDrive app.

I have my own Exchange server which uses self-signed certificates. I installed the certificates and rather to my surprise auto-discover then worked and I was able to add my Exchange account to Outlook on the device without my having to enter the server details.

So far so good; but I was expecting some sort of automatic or semi-automatic process of installing the apps I was using on the Lumia 800, but this is more difficult than it should be. Nothing appeared automatically. You have to go to the store and re-install. You can reduce the work slightly by going to your purchase history online and selecting Reinstall; but in many cases that does not work and there is a message saying “App not available on the Web. Try downloading it on your phone.”

That is a shame, since this works well for Windows 8 store apps. The experience of upgrading to a new Windows Phone should be like this:

  1. Buy new phone.
  2. Enter Microsoft account details.
  3. Wait a bit, then carry on where you left off with all apps in place.

Unfortunately we are not there yet.

The new Windows Phone 8 Start screen is a considerable improvement. The big deal is that you can get four times as many icons on the screen, so no need to waste all that space. The Live Tile concept works better on the phone than it does in Windows 8, since you see the Start screen more often. I might work for hours on a PC and never see the Start screen.

The supplied earbuds/microphone are functional but not very good. The sound is mediocre and the earbuds do not feel secure. Incidentally, a much better set comes with the 820; but in practice most of us have our own favourite headset already and I would not mind if Nokia did not bother to include this in the box. Audio with a better quality set is fine, and after copying some MP3s to the device I was happy with the sound.

Once during the course of this review the phone rebooted itself for no apparent reason. Once it froze and I had to remove and replace the battery. Hmm.

Fitting a memory card

The 620 accepts a microSD card up to 64GB. Fitting is not too difficult, though slightly fiddly. First remove the back. Then slide back the silver card holder until it pops up.

image

Insert the card and close the holder.

image

Camera

The camera captures images at 2592 x 1936 pixels. It is fine for the use I am likely to make of it, bearing in mind that I am not yet ready to abandon carrying a separate camera. The camera software supports extensions called “lenses” which let you process the image. An example is Translator which lets you point the camera at some text and have it translated, an intriguing idea from which I got mixed results.

image

I was disappointed to find that Blink, from Microsoft Research, will not install as apparently the 620 does not meet minimum requirements, though I cannot quickly see in what way it falls short.

One small feature that I like on Windows Phone is that you can press the camera button even the phone is locked and use the camera.

Nokia Apps

Nokia has some exclusive apps, of which my favourite is Nokia Drive. I have found it works pretty well for turn-by-turn directions and no longer use my Tom Tom. The 620 lets you install Nokia Drive + Beta, giving you free downloadable maps and offline directions.

City Lens is a fun app that uses augmented reality to superimpose nearby attractions on the image from the phone’s camera. It has some promise, though it asks me to “Calibrate your compass” every time it starts up, which means waving your arms in the air and probably hailing a taxi by mistake.

More seriously, City Lens is only as good as its data, and in my part of England it is not good enough yet, with only a few local businesses showing.

Nokia Transit gives you public transport directions, and worked OK when I asked for directions to my nearest airport, giving a sensible bus route. The app integrates with Nokia Maps for directions and I found the user interface a bit perplexing. The app also freaked out when I asked how to get to London. Sensible options would include my local railway station, which has an hourly service, or a National Express coach from the nearest city centre. Instead, Nokia Transit proposed a seven hour bus journey with numerous changes, starting yesterday (I am not joking). Then the app crashed. Still, looks like it could be useful for local bus journeys.

Nokia Music gives you “Mix radio” for free, and a download service for a per-track fee. Fair enough, though the quality of the Mix radio is indifferent.

Nokia Smart Shoot takes five pictures at a time, and lets you select the best, superimpose faces from one on those of another, or remove people or objects. Face transposition is not my thing, but taking five images at a time makes sense. You can then flip through to find the best, and save it. Useful.

Creative Studio (I am surprised Nokia can use that name) is a simple photo editing app that lets you crop and rotate, remove red eye, adjust colour balance and brightness and so on. It is simple but rather good.

SkyDrive

Microsoft’s cloud storage service SkyDrive is integral to Windows Phone 8. If you follow the setup defaults, photos and videos end up there, though in slightly reduced quality, and it also forms storage for the Office Hub. It is free for up to 7GB of storage and generally works well. Windows Phone would be crippled without it.

Local Scout

Local Scout is an official Windows Phone app that is meant to give information and ratings for local businesses such as shops, restaurants and attractions.

Excuse me while I have a rant. Local Scout was introduced in Windows 7.5 “Mango”, made available in September 2011. It has potential, but I noticed at the time that the data was not that good. In my local area, it included a restaurant that has closed, for example. I hit the link that said “Tell us this place is closed.”

As you can guess, the restaurant is still listed, more than a year later.

There is also a bit of a mystery about Local Scout. It has ratings and reviews, but there is no obvious way to add your own rating or review. The data must come from somewhere, but there are relatively few contributions for the places near me and the app would be more useful with community content.

Local Scout on the Lumia 620 (and on the 820) seems to have got worse. There is no longer a “suggest changes” link so you can no longer easily report that a place has closed. You still cannot add ratings or reviews for places you visit.

All a bit of a disaster. My hunch is that some team created Local Scout for Mango and made a reasonable but incomplete job. Since then, someone decided that it is not important and the thing is essentially frozen. It is still there though; it seems to me that Microsoft should either improve it or abandon it.

This is important because it influences the experience when you pick up a Windows Phone and try to use it. Of course you can use Yelp or TripAdvisor or something else instead; but why does Local Scout occupy a precious spot on the default Start Screen, on most Windows Phones I have seen, when it is so broken?

Office

The Office hub on Windows Phone lets you create, view and edit Word and Excel documents, and view and edit PowerPoint documents. At least, you might be able to. I tried some recent documents on SkyDrive. A PowerPoint opens beautifully, and I can easily edit or hide individual slides. On the other hand, another document I have been working on will not open; it downloads, then the screen flashes slightly, but it never opens. An Excel document downloads and views OK but comes up with a message “can’t edit workbook”.

In both cases, there are in the old binary Office document formats. I tried converting them to the new XML based formats (docx and xlsx) and they worked fine, both for viewing and editing. My recommendation then is to use the new Office formats if you want full access on your Windows Phone.

You can add comments to documents, which is a great feature for collaboration.

If you want to know in detail what will work on the phone, see here, and especially the entry “Why can’t I edit some Microsoft Office documents on my phone?”. This lists “common reasons” why a document cannot be edited. It does not say anything about documents which simply will not open so I guess that is unexpected behaviour.

Given the complexity of Office documents, it is not surprising that there are limitations. On the other hand, it does seem to me problematic that the question of whether you will be able to edit any particular document is, from the user’s perspective, rather hit and miss; and if there are many instances where documents do not open at all I will soon lose confidence in the app.

In an emergency, you could try going through the browser instead, since SkyDrive supports the Office Web Apps.

It may be imperfect, but the Office hub is miles better than nothing.

Other apps

Windows Phone remains a minority taste, and if you want the best and widest selection of apps, you should stick to Apple iOS or Google Android.

That said, the Windows Phone Store does have over 125,000 apps, increasing at around 500 apps per week according to windowsphoneapplist.  Some big names are present, including Twitter, Spotify, Amazon and Google; others are missing or only supported by third party apps, including BBC iPlayer, Dropbox and Instagram. Whether any of these (or others) are deal-breakers is up to the individual.

On the other hand, the strong web browser (see below) means good performance from web apps, which mitigates issues with missing native apps.

YouTube works well full-screen in the browser. Unfortunately BBC iPlayer does not.

A bonus for Xbox users is Xbox SmartGlass, which gives remote control of your console plus a few extras.

image

Internet

Windows Phone 8 includes the Internet Explorer 10 browser, and it is excellent, fast and with decent standards support. It gets a score of 320 at html5test.com, which by no coincidence is the same as IE10 in Windows 8.

image

The 620 also includes the simple, effective internet sharing hotspot feature which was introduced in Windows Phone 7.5, but worth mentioning since it is so useful.

Conclusion

Any budget smartphone is a compromise. The Nokia Lumia 620 is not beautiful to hold, the screen is not the best, the processor is 1.0Ghz rather than the 1.5Ghz on the high-end Lumias, and the battery a bit small.

Nevertheless this is a full Windows Phone 8 smartphone, performance feels snappy, and it supports a generous range of features. It fixes annoyances seen in some earlier Lumias, with a replaceable battery and no fiddly flap over the micro USB port.

The Lumia 620 is a better choice than the old Lumia 800, still on sale at a similar price. It performs basic functions admirably, and has valuable extras like Nokia Drive +. Outlook and the Office hub make it a good choice for Microsoft platform users on a budget.

The Windows Phone 8 OS itself is nice to use but in some areas not as good as it should be. Some of the supplied apps, like Local Scout, are not good enough, and a few crashes suggest bugs.

Web browsing is great though, and strong features like add-on “lenses” for the camera app make up for a few flaws.

In summary, a Lumia 620 is a great way to see what Windows Phone can offer at a budget price. If you can find one for under £150 it is a great deal.

Lumia 620 Key specifications

3.8” display

Dual-core Snapdragon S4 1.0 Ghz, Adreno 305 GPU

Wi-fi 802.11 a/b/g/n, Bluetooth 3.0, NFC

5MP camera with flash, front-facing VGA camera

8GB storage, 512MB RAM, MicroSD up to 64GB

1300 mAh battery

A-GPS

Magnetometer

Ambient light sensor

Orientation sensor

Proximity sensor

Hi-res audio and the hi-fi press: the problem with honesty

I have posted several articles on the subject of high resolution audio – here, for example. It is a subject that fascinates me. I enjoy music more if it is accurately reproduced, and regard sound quality as something worth paying for, but is it worth investing in high resolution formats such as SACD, DVD Audio, 24/96 and higher FLAC or ALAC (Apple’s lossless audio format); or is it better to concentrate on other parts of the audio chain, on the grounds that even lowly CD and 16/44 capture music with an accuracy close to the limits of what human hearing can perceive?

Many audio enthusiasts swear that high-res formats sound much better; but solid evidence for their superiority as a delivery format is hard to come by, and when you perform simple tests like converting a high-res format into one at CD resolution and comparing the two, it is often (perhaps always) hard to hear any difference. 

High resolution formats are of course a necessity in music production, where the sound will be processed, possibly many times over, before the final master is complete.

Alan Sircom is the editor of the UK audio magazine hi-fi plus. In a frank forum discussion concerning the challenges of editing such a magazine today he makes the following remark:

For all the enmity you and yours have toward the magazine, our biggest potential loss of readers right now is coming from my stance on hi-res. I still maintain that you are paying a premium for microphone thermal noise and – at best – a more careful mastering process. I know a lot of manufacturers of DACs who (privately) agree with me… but have to continue to develop their products from 24/96 to 24/192 to 32/384 to DSD-over-USB because the audiophiles (who, let’s face it, buy our stuff) will not accept anything less. This is a sham, especially as there is a better campaign to be had (something like “brick-wall mastering is worse than brick-wall filtering”, but more pithy). However, the upshot of the excellent exposé of the hi-res game by Hi-Fi News did not cause an army of hi-res-loving audiophiles demanding more from their hi-res, it caused some of them to consider Hi-Fi News ‘hostile’ to hi-res.

If true, this is a depressing situation. The goal of home audio is to achieve the best possible sound at home within your budget, which means investing in the technology that makes the most audible difference. It is not easy to discern what that is though, which is where an independent press has a valuable role to play. According Sircom, that is difficult to do in practice, because of the constraints imposed by the economics of advertising at one end, and a readership which does not always want to hear the truth at the other.

Two ways to make a spoon: 3D printing in action

Last week I attended the Monki Gras, a distinctive event exploring how to scale craft, mainly in the context of technology but also in the context of beer.

On the second day there was a light-hearted competition. Who can make a spoon faster, a wood carver, or a geek with a 3D printer?

image

A skilled craftsperson can make a spoon in around half an hour, we learned.

In the other corner was a techie, a laptop computer and a 3D printer.

image

image

Said techie (I did not get the name unfortunately) had downloaded a spoon design from the internet and was printing it on a Prusa Mendal RepRap machine. Cost: from a few hundred pounds if you self-assemble, or £1000 or more if you purchase complete.

The software is open source: slic3r to convert a 3D model into printing instructions, and pronterface to talk to the 3D printer.

Looking in more detail at the printer, what you have is a system of cogs, rails and stepper motors that lets a print head move in three dimensions. The raw material is a spool of green plastic from faberdashery. This could be fed from the rotating white spooler at the top of the machine, though in this case only a little was needed and it was floating loose.

image

The plastic is melted by the print head and squirted out to form the object being printed. Apparently once formed it is reasonably rigid and strong.

image

Attendees observed that the competition was pretty silly, since speed is not a goal of 3D printing (and the wood carver was indeed the victor). In that sense, 3D printing is a poor way of scaling craft, though it has some potential in that a brilliant design can be reproduced as an object many times over. If you want a lot though, it is worth investing in traditional plastic moulding: setup is expensive, but once you have done one, you can do thousands more cheaply.

Still, imagine what 3D printing enables. I have a nice set of headphones, for example, which are useless because a small plastic component has broken. If I can get hold of (or make) a 3D computer model of the part, I can now make that part for little cost. You do not even need your own 3D printer; services like Shapeways let you upload the design and get the part in the post a few days later.

In niche areas like model trains and landscapes, 3D printing makes models viable even if only a few are needed. You can also have exactly the size you want, rather than being restricted to the standard sizes that are volume manufactured.

For inventors, 3D printing makes prototyping easier. You can iterate through hundreds of slightly different designs and try them out physically, rather than relying on computer models.

The opportunities are fantastic, and you can get started for little cost; though the guy at Monki Gras did note that his RepRap was temperamental and therefore a high maintenance gadget. Maybe by making a few modified parts he can improve it.

When Google Maps is wrong

When I arrived in Bologna yesterday I was well prepared. I had found my hotel on Google Maps and printed out the map. I had plenty of time, so rather than take a taxi from the airport I decided to take the bus and then a short walk to the hotel.

All went well, I thought; I got off at the right stop, crossed the river, and walked to where the hotel was on my map. It a sizeable hotel and is even marked on the map.

image

Oh dear. No hotel. I was on the right road, but instead of a welcoming hostelry there was a high fence behind which was a residential area.

I sought directions. Unfortunately I don’t speak Italian, but I pointed at the hotel on my Google Map. My helpers did not speak English but helpfully pointed me back the way that I came.

I turned on my smartphone. Bing Maps could not find the hotel at all, a fact confirmed by the full browser version.

image

I tried Nokia Drive. That could find the hotel, but placed it in the same wrong place as Google Maps. I walked there anyway. I was standing right next to the finish flag, no hotel.

Again I sought directions. This time my helper spoke good English. “It is the other side of the river”, he said. Only about 10-15 minutes walk, but still.

He was right. Here is the hotel’s map on its site, again a Google map but note with its own pushpin.

image

Google maps thinks it is east of the river, but in fact it is west of the river, approximately 1.5km away from Google’s location.

The hotel is not particularly small.

image

No surprise I guess that Google Maps has errors, but I am surprised that a prominent hotel in a well-known city is so significantly misplaced. And that Nokia Drive has the same wrong information, suggesting a common source.

The lesson: local knowledge is best.

It gives me pause for thought though. On the web, if Google cannot find you, traffic drops alarmingly. Could the same be true in the physical world? Could there be future lawsuits over lost business from missing or incorrect information on IT systems on which we rely?

Fortunately I was still in good time for a nice plate of pasta before bed.

Postscript: The hotel told us that it is aware of the issue and has told Google “many times” but has been unable to get it corrected.

Another point worth mentioning: in order to find the right bus I had consulted with Tourist Information at the airport. They had worked out my route using … Google Maps. It shows the extent Google’s service is embedded into our way of life, increasing the significance of errors.

Office 2013 annoyances: Avoiding the Backstage, slow typing in SkyDrive

I have been using Microsoft Office 2013 since the first public previews. It is a high quality release, though washed-out in appearance, but there is one thing I find annoying.

In previous versions of Office, if you start a new document and hit Save you get a Save As dialog pointing at your default save location. Type a document name, press Enter and you are done.

In Office 2013, the same steps open the Backstage, a full window view where you have first to select a location. You cannot type a document name immediately, even if you are saving to your default folder.

image

It is only one or two extra clicks, but it is annoying.

The fix is to go to File – Options and check Don’t show the Backstage when opening or saving files.

image

Now Save works in the same way as before.

If you also check Save to Computer by default, it will no longer try to save in SkyDrive every time.

This reminds me of another problem, which I doubt is unique to me. I like using SkyDrive, but there is something broken about the way Office communicates with SkyDrive. It seems to be chatty, checking perhaps whether another person is editing the online version of the document. The consequence is that sometimes (but not always) editing in Word slows to a crawl. You have to wait after each keystroke for the letter to appear. Usually this problem appears only after I have been working in a document for a while. The workaround I have found is to Save As to a local folder, and to remember to put your updated version back on SkyDrive afterwards.

Maybe there is a fix for this behaviour as well. If you know of one, please comment below.