Yanis Varofakis has made a short, but very dispiriting, summary of the Greek government's attempts to negotiate any of the terms being dictated to them by Europe:
http://yanisvaroufakis.eu/2015/07/30/the-defeat-of-europe-my-piece-in-le-monde-diplomatique/
Read it & weep :( . It's quite easy to see why Europe is now probably a doomed project in the long run (by their own hands).
While the Eurozone crash of the last few years has clearly demonstrated that Britain was right to not to drop the Pound in favour of the Euro, the treatment of Greece now makes me think that the whole EU project is doomed (without major reforms that no-one seems willing to consider), and thus Britain should avoid any further integration with Europe at all (even if that means leaving the EU entirely). I suspect thus was the kind of change-of-heart which David Cameron obliquely warned his European compatriots could happen to the British people, if Europe didn't treat Greece fairly (but firmly).
Saturday, 1 August 2015
Friday, 30 January 2015
Why Greece's new finance minster should be welcomed, not just as a potential saviour of Greece, but the whole Eurozone
Greece's new finance minister is Yanis Varoufakis. Until very recently he was basically just an academic, albeit one who has become know for being loudly outspoken on Greece's & Europe's economic problems. He has only grudgingly become involved in politics (and Syriza).
I've been following his blog for some years, as he has had many interesting things to say about Europe's problems, and a point of view which is rarely heard on mainstream news. As such I think I've a half-decent understanding his point of view, despite not being an economist myself... but fear that his huge number of blog posts make it difficult for anyone suddenly interested in him to understand why he should be welcomed rather than feared.
Rather than do a poor job at summarising his views, I thought it would be better to point to a handful of his best blog posts. Those that give a good overview & have little economist jargon. I've tried to put them in order, starting with the most helpful first, but you could certainly skip some articles (in part or whole) if they don't (yet) make sense to you:
A bit of background on him, before he achieved "fame" (or at least notoriety!) for speaking about Europe's & Greece's problems, although the main body of the article is about why he was hired for a couple of years by Valve (creators of Steam - the PC's biggest games digital marketplace):
http://blogs.valvesoftware.com/economics/it-all-began-with-a-strange-email/
Why he accepted an offer to join the Syrizas party:
http://yanisvaroufakis.eu/2015/01/09/why-i-am-running-for-a-parliamentary-seat-on-syrizas-ticket/
Two nice short overviews of why he thinks massive loans in exchange for massive austerity in Greece (and other failing European countries) is only hiding the problem, and has in fact been making it worse not better:
http://yanisvaroufakis.eu/2013/11/08/ponzi-austerity-a-definition-and-an-example/
http://yanisvaroufakis.eu/2012/05/31/from-ponzi-growth-to-ponzi-austerity/
He draws parallels between the financial crash of 1929 & that of 2008, and argues whether Germany/Europe should reconsider it's current method of bailing-out Greece:
http://yanisvaroufakis.eu/2012/02/05/is-greece-still-viable-is-europe-my-piece-in-deutsche-welle-de/
A long-ish interview about his (and someone else's) Modest Proposal (to
solve Europe's economic problems), which they've been pushing since 2010, and gives a quite nice (if now slightly out-of-date)
summary of how we got into this mess & what might be done to get us
out:
http://yanisvaroufakis.eu/2012/12/16/taking-stock-of-the-global-and-euro-crisis/
http://yanisvaroufakis.eu/2012/12/16/taking-stock-of-the-global-and-euro-crisis/
A long-ish, but very easy to follow, article on how Europe ended-up in the current situation. You don't NEED to read it, but it would surely help understand almost everything else he has written about Europe's problems. Personally I found it a fascinating glimpse into how & why the world went down the particular path it did:
http://yanisvaroufakis.eu/2014/08/29/why-is-europe-not-coming-together-in-response-to-the-euro-crisis/
A summary of his Modest Proposal (to solve Europe's economic problems), followed by a more-technical check of it's predictions (which you may wish to skip):
http://yanisvaroufakis.eu/2012/11/10/a-world-without-the-global-minotaur-why-is-the-world-economy-failing-to-recover/
A brief explanation of why they recently had to update their Modest Proposal:
http://yanisvaroufakis.eu/2013/07/11/taking-stock-of-the-euro-crisis-a-prelude-to-the-forthcoming-version-4-0-of-the-modest-proposal/
The latest version of their Modest Proposal (to solve Europe's economic problems), that takes account of more recent issues, which is split into 5 fairly short pages:
http://yanisvaroufakis.eu/euro-crisis/modest-proposal/
One journalist's view of their Modest Proposal, which may help put it in context:
UPDATE:
I dare anyone to suggest more Austerity is the answer after reading this short summary of the terrible state of Greece (from a couple of year ago - the situation is surely far worse now) :
http://yanisvaroufakis.eu/2013/03/04/on-the-social-conditions-in-greece-now/
This article is now 3 years old, but it might perhaps still provide some insight into where the Syriza party may take Greece:
http://yanisvaroufakis.eu/2012/02/18/greek-default-does-not-equal-greek-exit/
UPDATE:
The world should listen to Greece’s big idea about debt:
http://qz.com/340448/the-world-should-listen-to-greeces-big-idea-about-debt/
Tuesday, 19 August 2014
Star Citizen continues trying to be everything to everyone
Star Citizen has shown trailers for three new "modules":
Of all the modules that Star Citizen could add, I would never have guessed racing. That seems so unrelated to anything Star Citizen is supposed to be doing, it feels like they're now doing something because they can, not because it's actually a good way to spend their large (but not unlimited) money pile.
It seems like they have no clear vision for the game, and instead they're just putting in every fun-sounding feature that Chris Robert's unrestrained imagination can think of, in the hope that something fun comes out the other side. Unfortunately that rarely works, and risks players just finding the game a confusing & unbalanced mess.
I worry that all these modules will end-up taking much more time & money than planned (as usually happens with software projects), and then they run out of money. Given how thinly they are now spreading themselves on multiple "modules" aka sub-games (on the budget of less than a single AAA game) this no-longer seems so implausible.
I worry that Star Citizen starts to resemble a pyramid scheme, where later ambitious modules are announced in the hope of keeping enough money flowing that they can actually finish their earlier ambitious modules. This works fine until they run out of Space Whales to milk, or trouble with their over-ambitious earlier modules causes people to start doubting Star Citizen (thus new money dries up). They're not there yet, but if they continue on the same trajectory I worry they might at some later date.
I also suspect it's disingenuous to label each of these separate sub-games as "modules", as that implies each one has no dependency on what happens in any of the other "modules", and therefore adding more modules doesn't affect the chances of success for existing modules... But each sub-game will unavoidably expect certain things of other sub-games (so you can move seamlessly from one to the other), and may even impose certain restrictions on other sub-games. So the more modules they have, the more likely changing requirements of one module will cause problems for other modules, and the more likely other modules will have problems meeting the requirements of another module. That potentially produces a cascade of delays, where one module's problems lead to one or more other modules having to do extra work (i.e.a delay), which could then impact on yet more modules. In short, having lots of modules going in parallel is extremely risky, even though Chris Roberts may claim otherwise.
- Racing in the atmosphere of some planets.
- Exploring the surface of planets.
- Shooting people inside ships & maybe other things.
Of all the modules that Star Citizen could add, I would never have guessed racing. That seems so unrelated to anything Star Citizen is supposed to be doing, it feels like they're now doing something because they can, not because it's actually a good way to spend their large (but not unlimited) money pile.
It seems like they have no clear vision for the game, and instead they're just putting in every fun-sounding feature that Chris Robert's unrestrained imagination can think of, in the hope that something fun comes out the other side. Unfortunately that rarely works, and risks players just finding the game a confusing & unbalanced mess.
I worry that all these modules will end-up taking much more time & money than planned (as usually happens with software projects), and then they run out of money. Given how thinly they are now spreading themselves on multiple "modules" aka sub-games (on the budget of less than a single AAA game) this no-longer seems so implausible.
I worry that Star Citizen starts to resemble a pyramid scheme, where later ambitious modules are announced in the hope of keeping enough money flowing that they can actually finish their earlier ambitious modules. This works fine until they run out of Space Whales to milk, or trouble with their over-ambitious earlier modules causes people to start doubting Star Citizen (thus new money dries up). They're not there yet, but if they continue on the same trajectory I worry they might at some later date.
I also suspect it's disingenuous to label each of these separate sub-games as "modules", as that implies each one has no dependency on what happens in any of the other "modules", and therefore adding more modules doesn't affect the chances of success for existing modules... But each sub-game will unavoidably expect certain things of other sub-games (so you can move seamlessly from one to the other), and may even impose certain restrictions on other sub-games. So the more modules they have, the more likely changing requirements of one module will cause problems for other modules, and the more likely other modules will have problems meeting the requirements of another module. That potentially produces a cascade of delays, where one module's problems lead to one or more other modules having to do extra work (i.e.a delay), which could then impact on yet more modules. In short, having lots of modules going in parallel is extremely risky, even though Chris Roberts may claim otherwise.
Tuesday, 13 May 2014
Star Citizen's feature creep... and other signs of a software project doomed for disaster?
It seems that Star Citizen is suffering from severe "feature creep"
(where features keep getting added long after work has started on a
project), as they are doing things like:
Apart from this sounding to me like a severe case of "Elite Dangerous envy", feature creep is a classic way for a software project to go way over-budget in time & money, with the end result being a horrible mess, or even simply running out of money before it is ever completed. Feature creep (and changing project goals) happens to many government IT projects that have tens or hundreds of millions of pounds to spend, and is why so many government IT projects end-up being a disaster. So having masses of money is not (on it's own) a good predictor of success (or failure).
Also, my impression of Star Citizen is that they're a big brand new team who have mostly never worked together before. This is not a good way to start a massive project, as demonstrated by Daikatana:
http://en.wikipedia.org/wiki/Daikatana#Development
http://en.wikipedia.org/wiki/Daikatana#Development_hell
- Modifying the game engine to be double-precision (64-bit) for much larger game 'maps'.
- Trying to add orbital mechanics (i.e. actually moving planets & moons).
- Trying to add procedural generation of planets.
Apart from this sounding to me like a severe case of "Elite Dangerous envy", feature creep is a classic way for a software project to go way over-budget in time & money, with the end result being a horrible mess, or even simply running out of money before it is ever completed. Feature creep (and changing project goals) happens to many government IT projects that have tens or hundreds of millions of pounds to spend, and is why so many government IT projects end-up being a disaster. So having masses of money is not (on it's own) a good predictor of success (or failure).
And as someone
pointed out, this also sounds suspiciously like what happened to a certain
well-funded game about chewing bubble gum & kicking ass (i.e. Duke Nukem
Forever).
Early signs do not seem good, as someone reports
that they "have [yet] to produce ... properly working core
functionality - even the hangar is a buggy mess".
Also, my impression of Star Citizen is that they're a big brand new team who have mostly never worked together before. This is not a good way to start a massive project, as demonstrated by Daikatana:
http://en.wikipedia.org/wiki/Daikatana#Development
http://en.wikipedia.org/wiki/Daikatana#Development_hell
In
fact Daikatana may have more similarities to Star Citizen than Duke
Nukem Forever:
- Massive hype before the project had even started, mostly coming from one famous name.
- Massive project for a newly formed team (which also kept adding more people).
- Even Daikatana's changing of game engine mid-project isn't so far off, as Star Citizen's engine has been heavily modified to be double-precision (not an easy undertaking).
- Missed deadline(s).
- The release of an (IMHO) underwhelming early 'demo'.
- Daikatana was even funded to Star Citizen levels, to the tune of $44 million.
Having said all that, I do hope Star Citizen is (at least moderately) successful, otherwise the whole space game genre might be tarnished & disappear for another decade or two (why would publishers take the risk when another First Person Military Shooter is bound to sell well?). But if S.C. is successful, then we are bound to see many more space games (even if most of them will be uninspired crap).
(Up front admission: Although I am a space game fan, Star Citizen has never excited me, but I did back Elite Dangerous, and I am crossing my fingers for Infinity Battlescape.)
UPDATE:
At least one Star Citizen backer is (IMHO rightly) getting nervous, as H1itman_Actual says:
(Up front admission: Although I am a space game fan, Star Citizen has never excited me, but I did back Elite Dangerous, and I am crossing my fingers for Infinity Battlescape.)
UPDATE:
At least one Star Citizen backer is (IMHO rightly) getting nervous, as H1itman_Actual says:
The 6 month delay of the dog fighting module along with ambiguous release dates have test a lot of us backers.
If this date doesn't hold I'm really loosing faith.
I'm an original backer. But CR release dates the past 6 months have been broken. He should have never of told backers "2 weeks from now" "1 month from now" " 1 or 2 weeks after PAX"
that kind of leading backer on creates scepticism.
Sunday, 6 April 2014
Android just became crap with official update (SD cards are disabled)
I can't believe this, but the latest update to Android KitKit (v4.4.2) prevents all 3rd-party apps from writing to the SD card! This is not a joke:
community.sprint.com/baw/message/750451
I mean, WTF. Google has removed one of the most heavily used features of an OS (writing data to external media). And they explicitly prevent manufacturers from restoring this feature! There is NO good reason for doing this, not in the name of "security" or any other short-sighted reason. I know Google thinks SD cards are unnecessary (see Google Nexus stuff) but that's no reason to prevent other companies from offering such stuff. The SD card slot has now become TOTALLY USELESS. Android is now less functional than Windows Phone (in one important respect anyway).
Are they trying to drive people to Android phones that don't use the Google ecosystem, and thus don't have to put up with their ridiculous restrictions? Cos I'm sure as hell not going to buy a phone with a limited amount of storage capacity.
It was bad enough when Google removed the ability of third-party apps to toggle Flight mode (it's really handy having an app put my phone into Flight mode overnight, so I don't get rudely awakened & also to save power).
UPDATE:
I am told that apps can still write to their own pre-defined 'sandbox' folders on the SD card. If that's the case then it's not nearly so bad (and in fact is close to what I've been wanting Android to do for ages, albeit a bit more draconian than I'd have liked).
UPDATE:
community.sprint.com/baw/message/750451
I mean, WTF. Google has removed one of the most heavily used features of an OS (writing data to external media). And they explicitly prevent manufacturers from restoring this feature! There is NO good reason for doing this, not in the name of "security" or any other short-sighted reason. I know Google thinks SD cards are unnecessary (see Google Nexus stuff) but that's no reason to prevent other companies from offering such stuff. The SD card slot has now become TOTALLY USELESS. Android is now less functional than Windows Phone (in one important respect anyway).
Are they trying to drive people to Android phones that don't use the Google ecosystem, and thus don't have to put up with their ridiculous restrictions? Cos I'm sure as hell not going to buy a phone with a limited amount of storage capacity.
It was bad enough when Google removed the ability of third-party apps to toggle Flight mode (it's really handy having an app put my phone into Flight mode overnight, so I don't get rudely awakened & also to save power).
UPDATE:
I am told that apps can still write to their own pre-defined 'sandbox' folders on the SD card. If that's the case then it's not nearly so bad (and in fact is close to what I've been wanting Android to do for ages, albeit a bit more draconian than I'd have liked).
UPDATE:
But this will still mean I can't use OI File
Manager - a really really good free file manager, and instead will have
to use whatever crap is built into the phone. That sucks. Why the hell
can't Google just add a (maybe new) Write-To-Whole-SD-Card-DANGEROUS
permission?
Monday, 27 January 2014
Android's permissions system is great... but also terrible
Android's permissions system is pretty good (compared to the competition). But it still suffers from several serious annoyances:
I would like to see developer being able to mark some permissions as optional, so that savy users could choose to disable them if they wanted. For example, say that My Backup's internet permission was marked as optional - then if I didn't want to use the cloud (nor risk the NSA remote-controlling it) I could simply disable internet access.
Or instead marking them as optional, the developer could mark some permissions as ask first, such that they default to disabled but upon first use the user would be automatically asked if they allow the app access to that permission. This has the benefit that the user will understand WHY a permission is needed, and so they can make a more informed decision about whether to allow it.
Or Google could take try to please everyone, by effectively implementing both options... but keep it simple for users, by having "optional" permissions default to behaving like "ask first". That way users would not have this important security option hidden from them, but savy users could change it if they want. You view this "optional" behaviour as "don't ask me about permission choices".
As far as fixing coarse permissions (esp. when grouping unrelated sub-permissions), it might be too much to ask that Google totally revamp Android's permissions, but there are a few obviously bad mistakes that they ought to fix:
- Permissions
are all or nothing - the user either grants access to all the
permissions at installation time, or he can't install the app.
- Permissions are too coarse, such that if an app needs access to one particular function/ability (let's call them "sub-permissions" for simplicity), it will usually need to ask for a load of other sub-permissions that it doesn't actually need. On it's own this wouldn't have been too bad, but...
- Permissions often contain several sub-permissions that aren't related to each other in a useful way, at least from the user's perspective, when he is worried about privacy (or possibly security). e.g. To tell whether the user is making/receiving a call or not (so it can pause itself), an app also gains access to who the user is calling, the caller's own phone number, and other personal information.
I would like to see developer being able to mark some permissions as optional, so that savy users could choose to disable them if they wanted. For example, say that My Backup's internet permission was marked as optional - then if I didn't want to use the cloud (nor risk the NSA remote-controlling it) I could simply disable internet access.
Or instead marking them as optional, the developer could mark some permissions as ask first, such that they default to disabled but upon first use the user would be automatically asked if they allow the app access to that permission. This has the benefit that the user will understand WHY a permission is needed, and so they can make a more informed decision about whether to allow it.
Or Google could take try to please everyone, by effectively implementing both options... but keep it simple for users, by having "optional" permissions default to behaving like "ask first". That way users would not have this important security option hidden from them, but savy users could change it if they want. You view this "optional" behaviour as "don't ask me about permission choices".
As far as fixing coarse permissions (esp. when grouping unrelated sub-permissions), it might be too much to ask that Google totally revamp Android's permissions, but there are a few obviously bad mistakes that they ought to fix:
- Checking whether the user is making/receiving a call should not require access to tons of other personal info. Thus music players & games & other apps could pause for calls, without getting access to lots of unnecessary stuff.
- Being able to store data on the SD card should NOT require giving an app access to the whole SD card. It would be far better if every app has a pre-defined (but maybe user configurable) folder, and could only be given permission to write to that folder.
- But once you've created an app-specific folder for writing, why not limited read-access to that folder too? Then you don't need to give an app read-access to the whole SD card either. Given that private data may be stored on the SD card, this seems like a big security win.
NSA must love My Backup
My Backup (Pro) is by far the best backup app for Android phones (at least if you aren't rooted). But I have a love/hate relationship with it, because of it's Internet permission & the fact that it can be remote-controlled (from Rerware's website). Snowden's recent NSA revelations make this all the more worrying.
Given the NSA has hacked Google's secure cloud, it
seems very likely the NSA can also read everything that My Backup stores
in the Rerware's dinky cloud, and perhaps even remote-control My Backup (since it's designed to be remote-controlled by you).
I'd like to
see a version which doesn't ask for internet permissions (and has no
cloud backup options), so I can be sure it's impossible for it to send
my data to the NSA. So far Rerware has denied my requests for such a version. But if enough people ask them, they will surely see there is demand for it, and so provide one I hope.
This would be much easier for Rerware, if Google allowed developers to mark certain permissions (such as internet) as optional. Then I'd be able to disable it's internet permission (and stop worrying).
Saturday, 23 November 2013
The end of smartphones with physical keyboards?
This is really depressing:
http://www.theverge.com/2013/11/15/5104704/i-come-not-to-praise-qwerty-but-to-bury-it
I know the UK hasn't seen any keyboarded phones since the Sony Xperia Pro, but I thought the USA was still getting them, and so still held out hope the UK would get another one eventually. Apparently not :(
http://www.theverge.com/2013/11/15/5104704/i-come-not-to-praise-qwerty-but-to-bury-it
I know the UK hasn't seen any keyboarded phones since the Sony Xperia Pro, but I thought the USA was still getting them, and so still held out hope the UK would get another one eventually. Apparently not :(
Sunday, 23 December 2012
Blogger editing sucks on Android
Google get a D-- for their effort with Blogger on mobiles:
The web version is totally unusable on mobile web browsers (due to how touch seems to be interpreted), when editing.
The Android app is a lot better, but as soon as you try to edit a post that I editied on the web version, then I find it filled with tons of HTML mark-up tag crap, rending it unusable.
And of course it's not really possible to send any feedback to Google, so they'll likely remain oblivious to these issues. Something to add to a future "Google sucks" post....
Thursday, 15 November 2012
Android sucks... at App management (and will get much worse!)
Android has no way of rolling-back to a previous (known good) version of an App, if an update makes it much worse. Google were probably thinking this would put more pressure on an App developer to fix it quickly, but the sad fact is this often doesn't happen, and sometimes this is because the developer thinks these bad changes are actually improvements!
You are probably thinking that Android has lots of app-backup Apps. Yes it does, but it seems pretty sure that Google will prevent these apps from working in the not-too-distant-future (with a new version of Android) in the name of preventing piracy - something which is a major issue for Android developers (compared to Apple's walled garden). At that point I may actually start to dislike Android, and wish for a (non-Microsoft) alternative...
I haven't been using Android for that long (say 1.5 years), but I've already seen many of my favourite apps made far worse by "improvements", and then never fixed:
* Simple Task Manager. Used to be the best task manager by a mile, as all it did things wonderfully different to all the (really crappy) task managers on Android. Then he updated it for ICS, and at the same time made it behave like all those other (crappy) task managers. Plus he removed some useful features, and made it buggy (it get's stuck trying to refresh the list - how crap is that?). And despite my emails, the author doesn't seem to care. The only thing still going for it is the lack of internet & other dodgy permissions inexplicably present on most other task managers.
* Adobe Reader. This WAS fantastic, as it was much faster at rendering PDF files than any other PDF reader. Then Adobe made a big update, adding loads of new features... but going by comments (I haven't dared to update), they made it take forever to start-up (due to all the new features bloating it), added lots of new bugs (some still not fixed), and made it far slower at rendering web pages. In short, they ruined it, and apart from fixing the few worst bugs they seem to think it is "mission accomplished".
* (ADDED LATER) Astro File Manager. It was really good & popular, then they completely redid the interface (most likely for tabletes & ICS) & added some major new features, seemingly with much testing as the old features are now extremely buggy, and it takes far longer to start. And they don't seem able to fix these issues, at least not anytime soon (weeks so far). Lots of people have been dumping it for other apps that actually work.
* Memento. THE best database app on Android (by a mile), but after being updated for ICS it wastes a lot of screen space (at least on Gingerbread) without any obviously good reason. This app gets updated so infrequently, that I went back to the old version.
And even after you intentionally install an older version of an App, theGoogle Market Google Play app will keep telling me there is a new (but rubbish) version of the App available. And there is no way to stop it. How crap is that?
You are probably thinking that Android has lots of app-backup Apps. Yes it does, but it seems pretty sure that Google will prevent these apps from working in the not-too-distant-future (with a new version of Android) in the name of preventing piracy - something which is a major issue for Android developers (compared to Apple's walled garden). At that point I may actually start to dislike Android, and wish for a (non-Microsoft) alternative...
I haven't been using Android for that long (say 1.5 years), but I've already seen many of my favourite apps made far worse by "improvements", and then never fixed:
* Simple Task Manager. Used to be the best task manager by a mile, as all it did things wonderfully different to all the (really crappy) task managers on Android. Then he updated it for ICS, and at the same time made it behave like all those other (crappy) task managers. Plus he removed some useful features, and made it buggy (it get's stuck trying to refresh the list - how crap is that?). And despite my emails, the author doesn't seem to care. The only thing still going for it is the lack of internet & other dodgy permissions inexplicably present on most other task managers.
* Adobe Reader. This WAS fantastic, as it was much faster at rendering PDF files than any other PDF reader. Then Adobe made a big update, adding loads of new features... but going by comments (I haven't dared to update), they made it take forever to start-up (due to all the new features bloating it), added lots of new bugs (some still not fixed), and made it far slower at rendering web pages. In short, they ruined it, and apart from fixing the few worst bugs they seem to think it is "mission accomplished".
* (ADDED LATER) Astro File Manager. It was really good & popular, then they completely redid the interface (most likely for tabletes & ICS) & added some major new features, seemingly with much testing as the old features are now extremely buggy, and it takes far longer to start. And they don't seem able to fix these issues, at least not anytime soon (weeks so far). Lots of people have been dumping it for other apps that actually work.
* Memento. THE best database app on Android (by a mile), but after being updated for ICS it wastes a lot of screen space (at least on Gingerbread) without any obviously good reason. This app gets updated so infrequently, that I went back to the old version.
And even after you intentionally install an older version of an App, the
Thursday, 2 August 2012
Motorola Milestone 2 review (old)
This is a repost of an old Google+ post I made in August 2011 (to see how well Google+ could be used as a blog). I have NOT updated it in anyway, so it's mainly for historical purposes. Especially BEWARE that I subsequently discovered the Milestone 2's keyboard only lasts about 6 months of non-light usage for many people (including me), so I would recommend the Sony Ericsson Xperia Pro instead.
Intro
This is a review of the Motorola Milestone 2 (aka Droid 2) phone, which had a major firmware update a couple of months ago (which fixed many but not all of my complaints). In fact this review was written on it!
My review is written from the perspective of a former Nokia 9500 user (good keyboard, ran Symbian S80) & a former Psion die-hard (great keyboard, ran EPOC aka Symbian for PDAs). However, I will try to avoid talking about Android issues common to many phones (leaving them to a separate "Android review"), and instead focus on aspects unique to the Milestone 2.
My review is also written from the perspective of a UK/European user. I gather that the USA has a much greater choice of keyboarded Android phones, but our choice is very limited.
The Milestone 2 (from now on referred to as the M2) currently runs Android 2.2, although as Motorola (along with many other phone manufacturers) semi recently signed an agreement with Google about keeping their Android phones up-to-date (and now Motorola has now been bought by Google!), I have some hope it will be updated to Android 2.3...
HARDWARE
The M2 seems pretty well built, and I have confidence that it is about as robust as a complex phone this size can be. But if you are prone to dropping your phone, then you may still want to buy a snap-on cover to protect your expensive phone (I found a good one for only £4 (!!) on Amazon, although it prevents using it with a Car Dock, and is so hard to remove that you will probably break the keyboard slider mechanism if you try).
The touch screen is supposed to use Gorilla Glass, so it should be a little more damage resistant than on some other phones. The screen's brightness automatically adjusts to how bright the surroundings are (unless disabled), and I found this worked very well (and helps save the battery when used indoors). The touch screen's sensitivity seems about right, being neither overly sensitive nor unresponsive, although sometimes I have to clean my sticky fingers before the screen will respond. I do however wish that the screen had the iPhone's oleophobic coating, to reduce greasy finger marks, but that applies to all non-Apple phones.
The small backlit keyboard is revealed by a slider mechanism that feels reassuringly solid. It didn't take me long before I was very comfortable typing on it... but make sure you turn off the VERY stupid Auto-correct options, or you will constantly think you have mis-typed a word (when actually the phone changed it). No doubt this feature is useful for the on-screen keyboard (that I essentially never use), but the real keyboard is accurate enough to never need it. Despite it's small size, I have found the keyboard wonderful to use - it seems almost as good as the (much larger) one on my old Nokia 9500.
The main downside is that there is no dedicated row of number keys, such that you have to press Alt or Alt Lock to get numbers from the top row of letter keys. Surprisingly this works very well, and I now rarely find myself wishing for an extra row of keys. Alt Lock works great for entering large blocks of numbers, with the only bad point being that you have to leave Alt mode to enter a decimal point (how on earth did they miss that?!?). You can set a double-space to automatically be turned into a dot (followed by a space) but that then means pressing delete afterwards to get rid of the space.
Also, the Shift & Alt keys don't seem to reliably be "sticky" (where "sticky" means the Shift/Alt key doesn't need to be held down at the same time as the key press). And the Alt Lock key doesn't work in some (usually third-party) apps, but this may be a limitation of Android itself (rather than bad programming on Motorola's part).
Despite my moans, it is still one of the best Android keyboards available; keys are easy to identify by touch, and have good 'clicky' feedback (both feel & sound). As with other Android phones, the small size means you will always be "thumb typing".
Battery life is probably typical for a powerful Android phone, which means it will struggle to last a whole day if you use it heavily (i.e. a few hours combined use, depending on usage), unlike my old Nokia 9500. This means that in my pocket I now have a separate small MicroUSB battery (made by Kensington), which I can use to charge my phone in emergencies. WiFi does NOT seem to use much battery power, where-as it does on the HTC Desire Z. Something which MAY be unusual for Android phones is that GPS mapping apps (like Google Maps & Copilot Live) seem to kill the battery very quickly, so don't plan on using it away from the car (charger). Maybe using wifi & phone signals would reduce battery usage, but I don't like Google knowing where I am at all times...
Talking of GPS, I am usually stunned by how quickly the Assisted-GPS gets a lock (typically a few seconds) no matter the conditions, and sometimes even inside buildings! Seems much better & more reliable than other Android phones I have seen (inc the HTC Desire Z). But if you don't have a data connection (unlikely but possible) then it will take the usual few minutes to get an unassisted lock.
Sound seems loud enough (both headphones & speaker), and call quality seems fine for both parties (at least since the firmware update). While I am not one to ask about sound quality, it seems pretty good to me. There is supposed to be noise-cancelling for hands-free calls, but I can't say how well it works. I have had problems with 3.5" headphones (NOT headsets!) randomly pausing music & trying to make calls. By the way, the M2 obviously supports high-quality music-only Bluetooth audio.
I am not a camera fan, but I didn't notice any problems with the built-in 5MP camera (although surely anything is better than my old Nokia 9500's fuzzy 0.3MP camera!).
I highly recommend the official Motorola Car Dock (attaches to the windscreen) which works brilliantly, and you can even slide the keyboard open if you want. OTOH, do NOT buy an Expansys Desktop Dock as the phone goes in & out of dock mode at random (causing all sorts of problems). This seems to be a problem with most non-official Desktop Docks, due to incorrect placement of a magnet that the M2 uses to detect when it is in the Dock. So only buy Motorola Docks (for car or desk).
My M2 came bundled with an 8GB MicroUSB card (early reviews said 4GB), a nice pair of wired headphones (with microphone pick-up & call answer button), a USB data/charger cable, and USB socket in a mains plug (in case you don't have a PC handy).
Leaving my Noka 9500 (with it's awesome transflective LCD screen) for the Milestone 2 (with it's standard back-lit LCD screen), I was worried that it's screen would not be readable outside. This worry proved to be entirely unfounded, as the phone will detect I am using it outside & after a short delay (about one second) the screen brightness will be automatically increased. Of course this will eat the battery quicker, so outside usage is still something you want to minimise.
I should also mention that I have very occasionally found the Milestone 2's battery seem to run out very quickly, despite no obvious sign of any apps heavily using the CPU. Rebooting it (power off then on) fixed this. I cannot say whether this was Motorola's fault, or one of the apps I have installed. It's NOT a frequent reoccurring problem, so you don't need to worry - I only mention it in case you ever run into a similar problem.
On the plus side, I continue to be pleasantly surprised at how quickly Android (on my 1GHz Milestone 2 anyway) boots after being completely switched off. It only feels like a few seconds (certainly well under a minute), where-as the Nokia 9500 would literally take 5-10 minutes to finish.
I am also pleasantly surprised at how little the battery gets used overnight (about 10%), if I leave the phone in "Flight mode" (where Mobile & Wifi usage is turned off). This manages to about equal the Nokia 9500, which is quite an achievement considering how frugal Symbian was.
In summary, the M2's hardware is fantastic & seems robust. It probably beats all other keyboarded Android phones currently available. It is as good as (if not better) than anything Nokia ever made! Motorola did a great job here.
SOFTWARE
The software side is more of a mixed bag. Motorola's "MotoBlur" adaption of Android got heavily panned for being too slow in pre-release reviews of the M2, but I think this was before they had finished optimising the software. That isn't to say it is perfectly smooth (even after the firmware update), but in general I think it is acceptable.
MotoBlur's good points include a lot of additional functionality that doesn't come as standard (some not even in the HTC Desire Z). For example:
* The Motorola Task Manager means you can't accidentally stop Android working properly, because unlike Task Managers from the Android Market, it won't allow you to kill Motorola-specific tasks/services (and in fact won't even show them by default).
* The music player has quite a few nice features probably lacking from the standard one, although it still misses some things I'd like, so you may end-up getting one from the Google Market. For example, Playlist generation is virtually missing, so I had to install the free My Playlist Maker 2 app. Note that the manual documents you can search your music, but I have never gotten this to work, and so have reported this as a bug to Motorola (but their reply was not encouraging).
* It comes with Quick Office, which is no-doubt good if you need that kind of thing. My main use of this is the PDF viewer, which seems fast & works well... although for one complex PDF that it struggled with, I found the official Adobe Reader much faster.
* The Car Dock mode is pretty good.
* There is support for Facebook, Twitter, Picasa, etc although I don't use these so can't really comment. Apart from various widgets for the Home screen, the Contacts app is suppose to automatically combine people on your Google Contacts with the same people on Facebook/etc (I read someone say it was fairly good at this). Beware that those internet-enabled Home screen widgets may drain the battery fast, so you may end-up removing them (I certainly did!).
* The web browser has been enhanced with an iTunes-esque scrollable bookmarks facility. Not sure whether this is actually an improvement or not, but it is pretty & fluid. In the end I have disabled bookmark thumbnails, in favour of text-only bookmarks, so that I can see more on screen & more quickly identify them.
* The MotoBlur account you have to create means you can remotely locate your phone using GPS, and even remotely wipe it. Never tried either of these features though.
OK, enough good points. Why might you decide against getting an M2, despite it's many plus points?
* A few MotoBlur things are NOT fluid, despite the 1GHz processor. The obvious one is browsing your pictures using the Gallery app - it's not unusuable, but scrolling through the pictures isn't as smooth as it should be.
The phone does occasionally grind to a halt, when it is does a full synchronisation with Google a few times a day (you see a little symbol in the status bar), which can be frustrating, so I have learnt to wait for this to finish (maybe 30 seconds) before doing anything. Not sure if this is a general Android problem, or only specific to the M2, but it does seem stupid on a such a powerful phone with proper multitasking.
* MotoBlur's "Android skin" is slightly inconsistent. Mainly the GMail app has rather dark grey buttons, while the rest of the phone has light grey buttons. You may also occasionally notice a highlight is (standard Android) bright orange rather than MotoBlur's bright red. This doesn't bother me, and in general I like MotoBlur's skin, but artistic perfectionists may not.
* While I have 16GB Class 4 MicroSD card working fine, before the firmware update I (like many others) found the phone would randomly freeze when using a high-speed card (I ran into problems with a Class 10). I HAVE NOT YET TESTED whether this is fixed by the firmware update.
* Despite the firmware update, it is still not completely stable (I have occasionally gotten a spontaneous reboot, or otherwise had to reboot it because of some problem). Although I hear that other Android phones (e.g. the HTC Desire Z) can be afflicted by similar issues. I'm also used to this from my Nokia 9500, so it seems to be an almost unavoidable result of the complexity of modern smartphones (and how they are rushed to market)... but one day I really hope things will improve (like Windows has from crashy 95 to rock-solid 7). I guess the iPhone might be more stable here, because it lacks real (user) multi-tasking.
My own experience of Motorola's "MotoBlur" adaption of Android suggests that you should wait until 6 months after a Motorola phone is released (in the UK anyway), because it seems it takes them that long to work out most of the bugs & performance issues. This isn't doing their reputation any good, and explains the "vanilla Android not MotoBlur" campaign by some people.
* Netgear DG834G v5 owners BEWARE that the M2 has serious wifi problems with that particular router: After about 1 day the M2 refuses to connect wirelessly to the Netgear. Rebooting the M2 makes no difference, the only solution is to reboot the router! I have had no such problems with any other device (inc my aging Nokia 9500), so I believe this is Motorola's fault. The M2 certainly did have many wifi issues before the firmware update, and it seems this particular one was missed.
Now, let me be clear, this does not happen with any other routers (not even earlier versions of the DG834G), as far as I know, and as far as Motorola's tech support is aware. EDIT: I discovered that this affects many Android devices, so it is actually Netgear's fault.
SUMMARY
None of the M2's software issues is particularly problematic for me, the M2 does provide some nice software on top of the standard Android stuff, and it has absolutely fantastic hardware.
If you are looking for a keyboarded Android phone, then the M2 is probably the best one currently available.
Intro
This is a review of the Motorola Milestone 2 (aka Droid 2) phone, which had a major firmware update a couple of months ago (which fixed many but not all of my complaints). In fact this review was written on it!
My review is written from the perspective of a former Nokia 9500 user (good keyboard, ran Symbian S80) & a former Psion die-hard (great keyboard, ran EPOC aka Symbian for PDAs). However, I will try to avoid talking about Android issues common to many phones (leaving them to a separate "Android review"), and instead focus on aspects unique to the Milestone 2.
My review is also written from the perspective of a UK/European user. I gather that the USA has a much greater choice of keyboarded Android phones, but our choice is very limited.
The Milestone 2 (from now on referred to as the M2) currently runs Android 2.2, although as Motorola (along with many other phone manufacturers) semi recently signed an agreement with Google about keeping their Android phones up-to-date (and now Motorola has now been bought by Google!), I have some hope it will be updated to Android 2.3...
HARDWARE
The M2 seems pretty well built, and I have confidence that it is about as robust as a complex phone this size can be. But if you are prone to dropping your phone, then you may still want to buy a snap-on cover to protect your expensive phone (I found a good one for only £4 (!!) on Amazon, although it prevents using it with a Car Dock, and is so hard to remove that you will probably break the keyboard slider mechanism if you try).
The touch screen is supposed to use Gorilla Glass, so it should be a little more damage resistant than on some other phones. The screen's brightness automatically adjusts to how bright the surroundings are (unless disabled), and I found this worked very well (and helps save the battery when used indoors). The touch screen's sensitivity seems about right, being neither overly sensitive nor unresponsive, although sometimes I have to clean my sticky fingers before the screen will respond. I do however wish that the screen had the iPhone's oleophobic coating, to reduce greasy finger marks, but that applies to all non-Apple phones.
The small backlit keyboard is revealed by a slider mechanism that feels reassuringly solid. It didn't take me long before I was very comfortable typing on it... but make sure you turn off the VERY stupid Auto-correct options, or you will constantly think you have mis-typed a word (when actually the phone changed it). No doubt this feature is useful for the on-screen keyboard (that I essentially never use), but the real keyboard is accurate enough to never need it. Despite it's small size, I have found the keyboard wonderful to use - it seems almost as good as the (much larger) one on my old Nokia 9500.
The main downside is that there is no dedicated row of number keys, such that you have to press Alt or Alt Lock to get numbers from the top row of letter keys. Surprisingly this works very well, and I now rarely find myself wishing for an extra row of keys. Alt Lock works great for entering large blocks of numbers, with the only bad point being that you have to leave Alt mode to enter a decimal point (how on earth did they miss that?!?). You can set a double-space to automatically be turned into a dot (followed by a space) but that then means pressing delete afterwards to get rid of the space.
Also, the Shift & Alt keys don't seem to reliably be "sticky" (where "sticky" means the Shift/Alt key doesn't need to be held down at the same time as the key press). And the Alt Lock key doesn't work in some (usually third-party) apps, but this may be a limitation of Android itself (rather than bad programming on Motorola's part).
Despite my moans, it is still one of the best Android keyboards available; keys are easy to identify by touch, and have good 'clicky' feedback (both feel & sound). As with other Android phones, the small size means you will always be "thumb typing".
Battery life is probably typical for a powerful Android phone, which means it will struggle to last a whole day if you use it heavily (i.e. a few hours combined use, depending on usage), unlike my old Nokia 9500. This means that in my pocket I now have a separate small MicroUSB battery (made by Kensington), which I can use to charge my phone in emergencies. WiFi does NOT seem to use much battery power, where-as it does on the HTC Desire Z. Something which MAY be unusual for Android phones is that GPS mapping apps (like Google Maps & Copilot Live) seem to kill the battery very quickly, so don't plan on using it away from the car (charger). Maybe using wifi & phone signals would reduce battery usage, but I don't like Google knowing where I am at all times...
Talking of GPS, I am usually stunned by how quickly the Assisted-GPS gets a lock (typically a few seconds) no matter the conditions, and sometimes even inside buildings! Seems much better & more reliable than other Android phones I have seen (inc the HTC Desire Z). But if you don't have a data connection (unlikely but possible) then it will take the usual few minutes to get an unassisted lock.
Sound seems loud enough (both headphones & speaker), and call quality seems fine for both parties (at least since the firmware update). While I am not one to ask about sound quality, it seems pretty good to me. There is supposed to be noise-cancelling for hands-free calls, but I can't say how well it works. I have had problems with 3.5" headphones (NOT headsets!) randomly pausing music & trying to make calls. By the way, the M2 obviously supports high-quality music-only Bluetooth audio.
I am not a camera fan, but I didn't notice any problems with the built-in 5MP camera (although surely anything is better than my old Nokia 9500's fuzzy 0.3MP camera!).
I highly recommend the official Motorola Car Dock (attaches to the windscreen) which works brilliantly, and you can even slide the keyboard open if you want. OTOH, do NOT buy an Expansys Desktop Dock as the phone goes in & out of dock mode at random (causing all sorts of problems). This seems to be a problem with most non-official Desktop Docks, due to incorrect placement of a magnet that the M2 uses to detect when it is in the Dock. So only buy Motorola Docks (for car or desk).
My M2 came bundled with an 8GB MicroUSB card (early reviews said 4GB), a nice pair of wired headphones (with microphone pick-up & call answer button), a USB data/charger cable, and USB socket in a mains plug (in case you don't have a PC handy).
Leaving my Noka 9500 (with it's awesome transflective LCD screen) for the Milestone 2 (with it's standard back-lit LCD screen), I was worried that it's screen would not be readable outside. This worry proved to be entirely unfounded, as the phone will detect I am using it outside & after a short delay (about one second) the screen brightness will be automatically increased. Of course this will eat the battery quicker, so outside usage is still something you want to minimise.
I should also mention that I have very occasionally found the Milestone 2's battery seem to run out very quickly, despite no obvious sign of any apps heavily using the CPU. Rebooting it (power off then on) fixed this. I cannot say whether this was Motorola's fault, or one of the apps I have installed. It's NOT a frequent reoccurring problem, so you don't need to worry - I only mention it in case you ever run into a similar problem.
On the plus side, I continue to be pleasantly surprised at how quickly Android (on my 1GHz Milestone 2 anyway) boots after being completely switched off. It only feels like a few seconds (certainly well under a minute), where-as the Nokia 9500 would literally take 5-10 minutes to finish.
I am also pleasantly surprised at how little the battery gets used overnight (about 10%), if I leave the phone in "Flight mode" (where Mobile & Wifi usage is turned off). This manages to about equal the Nokia 9500, which is quite an achievement considering how frugal Symbian was.
In summary, the M2's hardware is fantastic & seems robust. It probably beats all other keyboarded Android phones currently available. It is as good as (if not better) than anything Nokia ever made! Motorola did a great job here.
SOFTWARE
The software side is more of a mixed bag. Motorola's "MotoBlur" adaption of Android got heavily panned for being too slow in pre-release reviews of the M2, but I think this was before they had finished optimising the software. That isn't to say it is perfectly smooth (even after the firmware update), but in general I think it is acceptable.
MotoBlur's good points include a lot of additional functionality that doesn't come as standard (some not even in the HTC Desire Z). For example:
* The Motorola Task Manager means you can't accidentally stop Android working properly, because unlike Task Managers from the Android Market, it won't allow you to kill Motorola-specific tasks/services (and in fact won't even show them by default).
* The music player has quite a few nice features probably lacking from the standard one, although it still misses some things I'd like, so you may end-up getting one from the Google Market. For example, Playlist generation is virtually missing, so I had to install the free My Playlist Maker 2 app. Note that the manual documents you can search your music, but I have never gotten this to work, and so have reported this as a bug to Motorola (but their reply was not encouraging).
* It comes with Quick Office, which is no-doubt good if you need that kind of thing. My main use of this is the PDF viewer, which seems fast & works well... although for one complex PDF that it struggled with, I found the official Adobe Reader much faster.
* The Car Dock mode is pretty good.
* There is support for Facebook, Twitter, Picasa, etc although I don't use these so can't really comment. Apart from various widgets for the Home screen, the Contacts app is suppose to automatically combine people on your Google Contacts with the same people on Facebook/etc (I read someone say it was fairly good at this). Beware that those internet-enabled Home screen widgets may drain the battery fast, so you may end-up removing them (I certainly did!).
* The web browser has been enhanced with an iTunes-esque scrollable bookmarks facility. Not sure whether this is actually an improvement or not, but it is pretty & fluid. In the end I have disabled bookmark thumbnails, in favour of text-only bookmarks, so that I can see more on screen & more quickly identify them.
* The MotoBlur account you have to create means you can remotely locate your phone using GPS, and even remotely wipe it. Never tried either of these features though.
OK, enough good points. Why might you decide against getting an M2, despite it's many plus points?
* A few MotoBlur things are NOT fluid, despite the 1GHz processor. The obvious one is browsing your pictures using the Gallery app - it's not unusuable, but scrolling through the pictures isn't as smooth as it should be.
The phone does occasionally grind to a halt, when it is does a full synchronisation with Google a few times a day (you see a little symbol in the status bar), which can be frustrating, so I have learnt to wait for this to finish (maybe 30 seconds) before doing anything. Not sure if this is a general Android problem, or only specific to the M2, but it does seem stupid on a such a powerful phone with proper multitasking.
* MotoBlur's "Android skin" is slightly inconsistent. Mainly the GMail app has rather dark grey buttons, while the rest of the phone has light grey buttons. You may also occasionally notice a highlight is (standard Android) bright orange rather than MotoBlur's bright red. This doesn't bother me, and in general I like MotoBlur's skin, but artistic perfectionists may not.
* While I have 16GB Class 4 MicroSD card working fine, before the firmware update I (like many others) found the phone would randomly freeze when using a high-speed card (I ran into problems with a Class 10). I HAVE NOT YET TESTED whether this is fixed by the firmware update.
* Despite the firmware update, it is still not completely stable (I have occasionally gotten a spontaneous reboot, or otherwise had to reboot it because of some problem). Although I hear that other Android phones (e.g. the HTC Desire Z) can be afflicted by similar issues. I'm also used to this from my Nokia 9500, so it seems to be an almost unavoidable result of the complexity of modern smartphones (and how they are rushed to market)... but one day I really hope things will improve (like Windows has from crashy 95 to rock-solid 7). I guess the iPhone might be more stable here, because it lacks real (user) multi-tasking.
My own experience of Motorola's "MotoBlur" adaption of Android suggests that you should wait until 6 months after a Motorola phone is released (in the UK anyway), because it seems it takes them that long to work out most of the bugs & performance issues. This isn't doing their reputation any good, and explains the "vanilla Android not MotoBlur" campaign by some people.
* Netgear DG834G v5 owners BEWARE that the M2 has serious wifi problems with that particular router: After about 1 day the M2 refuses to connect wirelessly to the Netgear. Rebooting the M2 makes no difference, the only solution is to reboot the router! I have had no such problems with any other device (inc my aging Nokia 9500), so I believe this is Motorola's fault. The M2 certainly did have many wifi issues before the firmware update, and it seems this particular one was missed.
Now, let me be clear, this does not happen with any other routers (not even earlier versions of the DG834G), as far as I know, and as far as Motorola's tech support is aware. EDIT: I discovered that this affects many Android devices, so it is actually Netgear's fault.
SUMMARY
None of the M2's software issues is particularly problematic for me, the M2 does provide some nice software on top of the standard Android stuff, and it has absolutely fantastic hardware.
If you are looking for a keyboarded Android phone, then the M2 is probably the best one currently available.
First blog, First post
This is my first blog, so I have no idea how it will turn out. But I suspect that I'll mainly be moaning about techy stuff, like how Android's multitasking sucks. Plus I want to keep people's expectations as low as possible! Hence the blog name.
The name is also (of course) a big tip of the hat to the infamous Stevey's Drunken Blog Rants (and also the newer Stevey's Blog Rants). You can be sure he has posted much more interesting things than I ever will, so why not loose yourself in all his old classics?
I have previously experimented using Google+ as a kind of Blog, but I don't think it worked very well. My 'blog-like' posts have tended to get lost in all the other news I repost, plus it seems very hard to search past Google+ posts.
The name is also (of course) a big tip of the hat to the infamous Stevey's Drunken Blog Rants (and also the newer Stevey's Blog Rants). You can be sure he has posted much more interesting things than I ever will, so why not loose yourself in all his old classics?
I have previously experimented using Google+ as a kind of Blog, but I don't think it worked very well. My 'blog-like' posts have tended to get lost in all the other news I repost, plus it seems very hard to search past Google+ posts.
Subscribe to:
Posts (Atom)