19 January 2016

I'm an Android Owner... finally! First Impressions.

I've intentionally avoided getting involved in the smart-phone/tablet mania of the last few years.  In truth, I didn't see the need for one.  My trusty old Dell laptop, over 10 years old now, can still handle anything I can throw at it - and no, I'm not a games-player, apart from the odd game of Mahjongg, so no state-of-the-art hardware needed here!  Phone-wise, I still have an old Samsung SGH-D500 (original battery too) that is more than adequate of my humble needs.

But a Dragon x10 tablet owner I've become, for better or for worse.  Being a hater of all things Microsoft, and a Linux-buff with 8 years experience using that OS, an Android-based tablet was always going to be my first and only choice - Android of course having derived from Linux.

First, a word about the hardware.  The x10 sounds on paper a fairly impressive beast.  ARM7-based, it features a 8-core CPU, clocked up to 2Ghz, a snappy GPU, 1Gig RAM and 16Gig internal memory, 5M-pixel/2M-pixel cameras, coupled with a wide-viewing-angle 10.6" screen - all for €130, available from Amazon Germany.  Incidently, it is available marginally cheaper from Amazon UK - or would be, if they shipped to Ireland, which they don't - hence the German sourcing.  Fuller details on the x10 are available here.

So yeah, for the price, it's a well-spec'ed piece of kit, and very snappy in use.  It comes with a 7600mAh battery and claims some impressive run-times between charges - so I decided to do a quick test with a looped video.  With a fully-charged battery and using MX-player with hardware-decoding enabled, I managed to get just short of 13.5 hours of continuous video playback from it - which I found kinda amazing!  I should also add that that was with the minimum screen brightness, namely because that's the way I use it normally, but it also had both wireless & bluetooth enabled at the time, as I had forgotten to turn them off.

Firmware-wise, my x10 came with Android Kitkat 4.4.4.  Amazon UK had claimed that Tablet Express (the x10 manufacturer) was selling them with the new & improved Lollipop 5.1 before I had ordered, so I was disappointed to discover mine was Kitkat-based when it arrived.  Lollipop was available as a download from T.E though, so it was an opportunity to compare & contrast both systems.  I played with Kitkat for about a month before upgrading to Lollipop.

Upgrading proved a real ordeal too!  Although T.E don't make clear what Microsoft OS's are compatible with their upgrade software, as it looks like something that was produced for Windows 3.1 (so really bad) I presumed XP could easily handle it.  No such luck!  Try as I might, over the course of two days, XP resolutely refused to work with the upgrade-software.  I eventually had to borrow a copy of Win7 and to temporarily install that, all just to upgrade the x10's firmware!  It was also the first time that I had ever installed Windows 7 on a 'real' machine (I used it once with VirtualBox, but it had proven too slow) and must admit given my past recollections with Windows installations, this was a much improved experience.

Anyway, onto Android itself, and (imo) the whole setup's Achilles-heel.  First, its good points.  On the x10, most user-actions are super-slick.  Obviously a lot of thought has gone into the user-interface.  You also have more software available for it than you will ever get a chance to try - if you can ignore all of the ads!  But given that I'm old-school (my first computer was a Sinclair Spectrum) and more interested in the implemention, and know from experience just how good Linux's multitasking capabilities are, I was surprised at the obviously poor job that Android does on this front!  Given that there are 'proper' Linux distros that come on installations as small as 10Meg (Core Linux) I know that it doesn't take gobs & gobs of memory to create a 'proper' multitasking environment.  This Android does not do!  I was even more surprised to discover that earlier versions of Android had no multitasking capability at all!  Rather than a System Monitor (or Task Manager in M$ parlance) where the user can monitor & interact with running processes, all Android has is the Back-button - and it is not at all clear what this does!  Sometimes this will terminate an app, sometimes it will just send it to the background.  A perfect example of this sloppy implementation involves the use of Browsers for surfing the net.  Boot Firefox, open your favourite page, do some reading, hit the 'Recently used apps' button to start say Gmail, then head back to Firefox - what you find is that FF has been terminated, and is forced to reload its entire setup!  This sloppy handling cannot be down to lack of memory - I have 1Gig after all!!!

It is hard to come to terms with this shoddy performance, especially given that Android is derived from Linux, which has being doing 'proper-multitasking' since forever!  I can only surmise that Google has been putting all of its development effort into the GUI - but that still doesn't explain their not using already-existing technology!  I have even read that Google/Android, rather cynically, terminate/reopen apps intentionally in order to generate more revenue from the ads having to be reloaded!  If Google is following this route, then they will eventually end up getting their just desserts.

Long before Google even existed, Microsoft & Yahoo ruled.  Yahoo in particular I remember as dominating cyber-space.  And they really took the piss!  I recall how Yahoo would lace their search-engine results with irrelevant links (mostly porn-related) and to hell with what the user was searching for.  Along came Google, offering a really good search-engine with the minimum of unobstrusive ads - and they cleaned up!  If they are now going to go and undo all of that good work by producing a half-arsed OS that intentionally starts/stops apps, just so they may generate a little more revenue, then they are idiots and deserve to be kicked off of their pedestal.

After the initial novelty of the tablet, I find myself going back to the laptop more & more.  Sure, the tablet is handy, indespensible in some ways - I forgot to mention its bluetooth-headset music capability, which is superb, and its main-use here nowadays.  But being somewhat of an OS-purist, imo, Android is a huge step-backwards as far as proper multitasking is concerned.

Edit:
A quick addendum.  3 - 4 months down the line, here are a few more thoughts on this purchase of mine.  First off, one thing I didn't mention above, and something that has existed from the get-go, is that this x10 tablet suffers from a charging problem.  The charger itself is your typical cheap-and-cheerful Chinese type, complementing the tablet perfectly.  The problem is that when you plug it into the tablet's charge-socket, the tinest movement of the charger's lead will cause intermittent charging - I have often set it to charge overnight, only to find next day that no charging has taken place!  Given that the charger-plug itself looks fine, I initially thought that it was a soldering dry-joint that was causing the problem.  After carefully opening the tablet - no unscrewing necessary, it's of the 'clam-shell' variety - I am now (thankfully) again of the opinion that it is probably the charger-plug after all.  Although a dab-hand with a soldering iron, given the component dimensions involved (sub-millimeter resistor/capacitor sizes, which is kinda scary!) I really didn't want to go messing in there.  The circuit board is also tiny, especially considering the tablet's size - probably 100mm square all told.  Thing about the charger is, it's a 'custom-type', with a teeny 2mm charging plug - so no place to buy another to see if that would fix things!  Another charging-related problem is that occasionally when you plug in the charger, the tablet completely freezes.  This is really disconcerting, as the only thing you can then do is hold down the power-off button and hope!

Regarding Android, one thing I've discovered is that despite all the 'anti-rooting' articles I've come across, after you use Android for a while, rooting is the only way to go!  Two places where a rooted-device is essential, ad-removal and Bluetooth-GPS.  Before I rooted my tablet, no matter what software I installed, I could not get my Bluetooth GPS-dongle to work with the tablet.  Once rooted, things 'just work'!  Same goes for ads-removal - internet browsing with an unrooted Android is generally a pain, often unusable.  Once I installed 'Adaway' on my rooted device, browsing became a pleasure again.  My opinion of Android itself has not improved one iota either.  If only Unix/Linux could sue Google for bringing its superb multitasking capabilities into disrepute - seriously, it sucks!!! 

28 August 2015

The "Asiandate.com" dating-website scam.

I admit it, I find Asian ladies (Chinese especially) very attractive.  So about 4-5 years ago, I decided to give the asiandate.com website a go.  Before spending a penny, I had done a fair bit of research on the company behind this, and it had 'shady' written all over it - so I knew from the get-go that this setup was probably a scam.  They are also behind anastasiadate.com which uses the very same system, and is the source of many scare-stories of guys who got more than they bargained for when they went to meet their "model-quality" Russian bride.  But those lovely Asian ladies looked oh so cute - so I decided to give it a shot anyway!

The first thing you cannot possibly fail to notice is that this 'service' is outrageously expensive.  Their text 'Chat' is $1 per minute.  Including a 'premium smiley' in your text will cost another $1 per-inclusion.  Viewing a photo, or sending the lady one of yours costs an absurd $15.  Even worse, sending her a "Virtual gift", which consists solely of a tiny little picture/jpg, of a teddy-bear for instance, will cost you a whopping $15.  'Letters' seem better value at $10 per letter - until you realise that you are charged for both sides of the conversation, so in reality it's $20 per letter-exchange.  Video-chat will cost you $2 per minute where only the lady's cam is on, whereas 2-way video costs a gob-smacking $6 per minute!  All with audio disabled - naturally, they do everything in their power to prevent the exchange of any sort of off-site contact information.

These are their main-stays when it comes to fleecing customers, but they have a few other 'tricks'  up their sleeves.  One infuriating one is that if you click on a "Start Camshare" popup button, either by accident or design, you are immediately charged $2, even if you cancel before the lady's cam comes online.  Back then, there were relatively few "Start Camshare" popups, whereas now, that figure is up to at least 50% - so it's obviously a nice little earner for this outfit.  Unsurprisingly, the vast majority of these pop-ups from ladies begging to chat are fake, just randomly generated by the site from women (supposedly) online.  Another one I fell foul of more than a few times was clicking a part of the site I shouldn't have - the reason? well, their site is positively littered with ways of extracting yet-more cash from your account.  My Nemesis was in the Letter's section.  It contains multiple buttons/links to letters & photos, that the unwary can unintentionally click upon.  It's like a mine-field of sorts that needs to be tip-toed through, and given the number of times that I ended up paying for letters that I accidently opened, I guess it's designed that way on purpose.

And the majority of these letters are not even genuine - something that these gangsters readily admit to, though in the small print!  Many of the letters sent seem to be from ladies who haven't been 'live' on the site for years, yet you are still charged the same amount for reading these randomly-selected letters from long-dormant accounts.  Of course, no doubt there may be genuine women included as well, but how do you tell the real from the fakes?  Another issue I occasionally came across on asiandate.com was where apparently genuine ladies were unable to get their profiles removed from the site.  These were invariably pretty/beautiful.  Here is one example that I took a screen-grab of at the time - read the ladies 'Character' text.  This seems to have been a last-resort ploy to get her profile removed, which worked - less than a week later, her profile had been deleted!

And when it comes to charging you, there is absolutely no confirmation asked for with this crowd - your credits are instantly debited, you are not even told after the fact, that your account has just been charged!  Up until recently, it was in fact necessary to 'trick' the site into revealing how many credits you had remaining in your account.  Now, there is literally no way of seeing what your account balance is - these scammers apparently want you to remain blissfully unaware of what you are spending, right up to your last 10 credits, whereupon you will then be prompted to buy some more!  There is also no invoicing of any sort in place, you just have to take their word for it that they are charging you what they say they are!!!  How can this be legal???

Speaking of legality, during my research 4-5 years ago, this company rated an abysmal E-rating with the Better Business Bureau (BBB).  Were you to check now, you would find that the BBB has no record of them!!!  Apparently they have declared bankruptcy since then - even though they have never been off-line in the interim - and reputation-wise, now have a clean slate!  Also back then, there was a Youtube video from a guy well-known in the website-dating industry that had done consultancy work for asiandate.com, as well as its main rival.  One of the things he said both companies were guilty of was the buying of 'Catalogues' of models - yep, that pretty lady you think you are talking to could very well be some fat bloke that is working as many as a dozen of these profiles from the 'Catalogues' and charging you for the privilege!  I also remember him saying how he had tried to convince the management of both companies to offer a more value-oriented service, rather than their then 'in-for-a-quick-buck' business model, but they did not want to know.

My time with them as a paid-up member was relatively brief.  I opted for one of the ladies that was not a 'real-stunner', figuring that she would probably not be 'Catalogue material'.  No such luck!  After over 10 letters (20 paid-for, when her replies are included) I suggested to her I was considering paying for her email address (about $60 if memory serves) and would she be interested in contacting me off-site.  A response, but no answer to the question.  The next letter, I was more direct - another reply, but still no answer!  Finally I told her not to expect another letter from me if she didn't answer my one simple question - result!  She indicated that she was happy with the current arrangement and that if saving money was the issue, I should just email her less!  Haha, funny in retrospect, though I didn't think so at the time.  I exchanged letters with a couple of others, though no real 'correspondence' as such.  None seemed interested in communicating off-site.  I tried the 'Chat' for a bit as well, no joy there either - they all seemed to long to communicate, but ONLY via the site!  I wonder why???  Anyway, long story short, I didn't spend too much and it was an 'experience' of sorts.

Back to the present-day, this scam seems to be taking on a new twist.  'asiandate.com' is now unbelievably charging a subscription - $10/month or 120/year, which includes absolutely nothing that wasn't available for free before!   You are merely subscribing to be allowed to communicate with ladies - you then have to buy the credits to actually do so!  One other thing I've just noticed that will highlight how petty this lot are - having recently updated their 'Smiley' icons, they also took the opportunity to thin down the 'free-smileys' even more, customers now having a mere handful that may be used without incurring a charge.  Rather than working to improve things for potential customers, these actions show that they are (still) more interested in fleecing them for every penny they can - so as short-sighted as ever.  Shame.

I am not a betting man, but I would wager that this just-introduced 'Subscription' is doomed to failure.  In fact it seems more like a last-ditch effort to stave off (real) bankruptcy, than a credible means of generating a fresh revenue stream.  Who in their right mind will pay $120/year just for the privilege of paying for credits!?!?!


10 August 2015

Linux - the infamous 'Unlock keyring' dilemma.

If you are in any way Linux-inclined, you are certain to have come across this problem multiple times already.  Namely, when you browse your network for your online computers and double-click a share that you want to access, you are first prompted for a password to access the remote computer, followed by another password-prompt to unlock the infamous keyring.  The former is usually a one-off affair, bypassed by simply clicking the option to "remember forever" the entered password.  The latter however, has been the cause of much gnashing of teeth for at least the past 7 years, the period of time since I abandoned Windows for Linux - just Google "unlock keyring" if you are in any doubt!

This has driven me nuts over the years.  As you move from Linux distro to distro, just when you would start to believe that the Linux developers had finally 'fixed' it, you would be met once again by that infernal prompt to unlock the keyring at every boot-up.  And up to about an hour ago, I had resorted to my now-usual custom of cursing all developers responsible for this travesty, as well as all of their offspring, past and present, for good measure!  I then had my 'Road to Damascus' moment when I (finally) succeeded in understanding the underlying issue and fixing it permanently!  It's embarrassingly simple as well!

One of the biggest problems is that there must be dozens of tutorials out there on how to fix this, but knowing what I now know, it is equally clear that most of these are either incomplete, or the originator has only a vague idea of what the underlying problem is - his setup works for him, he therefore tries to describe how to configure your system so that you see what he sees.  Sure, you will find a lot of "Great, it worked for me!" responses, but invariably there are many "Nope, it didn't work for me" posts as well.

So, onto the solution.  First-off, despite what I had thought for years, there is nothing wrong with the keyring-management software itself - it's just that all those bloody misleading "fix-it" tutorials leave you (me) with the impression that there is!  To get this working properly 100% of the time, all one needs to do is follow what is outlined below.  But first, a word about 'security'.

Back 5-7 years ago when this was really driving people to distraction, there were equally distracted individuals doing the rounds of all the major forums, telling us to stop whinging and just enter the bloody password - after all, we need to keep Linux secure!  I, and probably most others thought "bollocks to that!", why can't this stupid setup just use your login password, which had already just been entered.  And this stance is perfectly reasonable & valid!  Where these pontificators might have been on much firmer ground involved those that wanted to auto-login as well - in this instance, there is absolutely no security in effect.  I mention this because I will now outline how to successfully achieve both, but naturally recommend that only the secure method be used.

1) To begin, open the Keyring Management app. On my Ubuntu-based distro (Deepin 2014), it's called 'Passwords and Keys' in the System's menu.  The underlying software is called 'seahorse'.  From the menu, select 'View' and check 'By Keyring', then select 'View' again and select 'Show Personal'.  You should now see at least one key-ring listed under 'Passwords' on the key-ring's pane on the left.

2) To make this as fool-proof as possible, delete all of these personal key-rings.  It should be obvious as to what you are deleting.  If unsure, select its properties.  Normally there are 2 key-rings that need deleting, one containing your login password, the other containing your network password.  It is this 'division-of-labour' (2 or more key-rings) that causes all of the problems.  We want to use a single key-ring for all operations, to hold our login-password, and our network-password.  Do NOT delete any of the 'Certificates', PGP keys etc.  - just the key-rings that are listed under 'Passwords'.

3) Even though you may want to start Linux without entering a password (auto-login), complete the following step anyway, as it will allow you the option to switch to the more secure password-login at a later date and your Network-keys setup will continue to work unaltered.  From  the 'Passwords and Keys' app. select 'File' -> 'New...' -> 'Password Keyring' and name the newly created key-ring "login".  This is the key-ring in which our Network key will now be stored.

4)  Open the desktop manager app. (Nautilus, Caja, Nemo etc.) select 'Browse Network' and navigate to the remote share you wish to access.  When you double-click it, you will be prompted for 2 passwords. Enter the first password, making sure that you select the 'remember forever' option for this, your network password.

 Now select either the 'Secure Method' or the 'Insecure Method' below.

Secure Method.
This assumes that you enter a login password each time you start Linux, and will use this entered-password to automatically unlock the network keys.

1) Enter your Keyring password & confirm it, at the prompt.  That's it, nothing further needs to be done!  The Password manager will have detected the "login" key-ring and copied the just-entered network-password key into it.  All should be well.

Insecure Method.
This assumes that you want to start Linux without entering a login-password, and also to not be prompted repeatedly for Key-ring passwords every time you start Linux.

1)  At the 'Enter Keyring-password' prompt, simply leave both the 'password' and 'confirm password' lines blank.  You will then be prompted to confirm that you do indeed want to store your passwords in an unencrypted format (hence the "no security" bit!)  Hit yes, and you're done.

With only one keyring, it will already be set to 'Default', so no need to worry about that.  You should never again be prompted for a password for that particular network.  If for any reason the keyring manager instead of copying the network-key to the 'login' keyring, creates another one named 'default...' and copies it to there, something is wrong - delete this and try again!  it must end up in the "login" folder for this to work properly.

Overall, eazy-peezy,what was all the fuss about? ;)

Edit 1.
Jesus wept.  Mere days after penning the above, I'm aghast to discover that the piece of shit that is Linux key-ring management is buggy after all!!!  I was shocked to find that on logging in (the 'secure method') I am occasionally still prompted for a key-ring password.

The bug is that the "login" key-ring is sometimes not unlocked at login, when it should ALWAYS be unlocked.  It is also very easy to reproduce, though it may take a few reboots/re-logins for it to show itself - just do the following;

reboot/login, and immediately open the 'Keys & Passwords' application.  You will find that sometimes the "login" keyring is still locked, sometimes it is unlocked!

This is with an Ubuntu Trusty-based 64-bit setup (Linux Deepin).  It is moronic crap like this that has ensured that Linux has managed to retain barely a toe-hold in the Desktop/Workstation OS environment.  Bill Gates might as well be paying Linux developers to sabotage Linux, for all the effect these cretins are having.  Remember, this bug has been around for at least 7 years, yet these arse-holes still haven't managed/bothered to fix it!!!  I don't have any Android-based devices, (which is Linux-based) - I don't like mobiles, and haven't got around to getting a tablet - but I bet that Google sees to it that bugs like this are quashed immediately.  I know one thing, Micro$oft wouldn't feel threatened enough to be giving away Windows 10 for free (which from what I've read, is actually pretty decent) if the competition was as bug-ridden as these Ubuntu-based releases.

Case in point, take Linux Mint.  I had tried a few Mint releases over the years but never saw the point - after all, it was essentially Ubuntu/Gnome2 with a candy-floss coating.  That all changed with the debacle that was/is Gnome3, so I have been acclimatising myself to Mint/Mate since 17.1.  Now Mint 17.2, I am continually shocked at the number of serious bugs this setup continues to harbour.  I have personally submitted 3 bug reports but don't expect that they will ever be looked at, never mind fixed.  On the other hand, Ubuntu 10.04, long EOL'ed but still my OS of choice, is a joy to use, almost bug-free, and I'm pretty sure doesn't suffer from the key-ring management bug discussed here.  The thing is, Mint is almost universally recommended as the Linux of choice for Linux-newbies.  As someone who currently uses it for several hours daily, my question is, WHY???  I'm using it purely because of Mate's emulation of Gnome2, but jeez, that also has so many bugs that it would merit its own article.  On the other hand, picture a typical Windows user who is thinking of switching to a free OS, has grown accustomed to using a decent OS - let's face it, Windows is not bad - and is then faced with headaches the likes of this key-ring management thing - common-sense would suggest that the majority will end up running for the hills, and back to fattening Bill's coffers.  And would you blame them, I certainly wouldn't.

Edit 2:
Try as I might, I cannot reproduce this 'failure to unlock keyring at login' on Mint 17.2, only with Linux Deepin, where it seems to occur 'naturally' about 50% of the time.  Given that they are both based on the 'Ubuntu-trusty' distro, I find this odd.  It is especially ironic in that Mint/Samba has a bug of sorts where remote-computers are not detected & listed automatically when you choose to 'Browse Network' (with Deepin, they are) - because of this, and in conjunction with another major Samba bug, where if you double-click 'Windows networks', then the 'workgroup' icons, your Browser window will instantly close (it crashes, issuing a 'segmentation fault' when Caja is launched from a terminal), but only if a remote Linux computer exists on the network!  It works fine if a Windows computer exists - it's as if Windows themselves are behind the development of Samba!!!  Note that this bug does not exist on my Ubuntu 10.04/Samba installation, only with the 'new-and-improved' Samba that is in the Trusty repository.  This means that from the Mint computer, I cannot Browse the network for available shares, but have instead to 'Connect to server...' via a specified IP address.

So, with Deepin, I can Browse & connect to network shares because Samba automatically detects & lists computers on the network, but am prompted 50% of the time to also enter the keyring password, whereas with Mint, since the remote computers are not automatically listed by Samba, I would normally need to go the 'Windows networks'->'workgroup' route to find them - only to have the Browse window crash when it detects that the remote computer is a Linux box.  So in a sense, I'm damned either way...

Edit3:
Weeeeeee,  I've just noticed that this Deepin bug has finally been removed!  Thanks should probably go to the Debian crowd, rather than the Deepin developers though - Deepin is after switching from the Ubuntu, to the Debian base-system for Deepin 15.  This move incidently is after introducing a whole other range of serious problems, not least of which is that Deepin 15 will not even install on a lot of computers - my Dell laptop being just one example.  After multiple graphics-related problems running on my Zotac pc, I finally have a stable setup there.   These 'introduced' problems have the Deepin devs thinking of starting a 'base-system' of their own, which sounds like a big move.

Stick with Debian I'd say.  The fact that this Debian setup is minus this stupid bug, one that seems to have plagued Ubuntu distributions for years, is a good omen.

21 May 2015

Raw deal from Three to O2 customers.

I haven't done one of these in a while so may as well blow off some steam over my latest pet-peeve.

I had been a customer of the telecoms-provider O2 for over 15 years, though for 'normal-calls' usage only, as my broadband/data usage is catered for by the Three telecom group.

That all changed about 2 months ago when O2 started texting its customers to inform them that they were about to be taken over by Three - but Hey! not to worry, it would be business as usual for O2 customers (paraphrasing) after the change.  Decidedly not the case as I have just discovered!

I had over €70 worth of credit with O2 prior to the take-over. I was therefore flabbergasted to discover about a week ago that this had plunged to a mere €7.  Contacting Three, I have been informed that I am on a €1 per-day/50MByte plan, which relentlessly counts down your account balance to zero, whether or not you use the phone.  In the past 6 days, my remaining €7 has been reduced to €1 even though I have not placed a call...

My immediate reaction to this is, how can it be legal?  Ok, Three can offer any account-types they like, but how can they not inform former O2 customers that their no-expire-with-non-use accounts have suddenly become Three credit-expiration accounts?!?!?

One thing is for certain, I will NEVER be topping up this phone again!

Notes:

A few years back, I foolishly signed up for a Three phone when cold-called out of the blue by a Three rep.  It turned out that the phone I was told would be a Nokia was some unknown piece of crap with software that almost made it compulsory to create a Facebook account before it could be used.  I contacted Three, telling them I wanted to return the unit and get a refund - and was almost told point-blank that I could not do so!  After almost an hour of being passed around to Three people, no doubt in an effort to break my resolve, I finally was given an address to return the phone to, albeit at my own expense - BUT ONLY AFTER SCREAMING AT THEM THAT UNDER EUROPEAN CONSUMER-RIGHTS LAW, THEY WERE LEGALLY OBLIGED TO ISSUE A REFUND!

I suffered similarly at their hands with regard to my Broadband account with Three.  I had had a BB-account with them for a couple of years previously, even though I had since moved address and technically, Three didn't have network coverage in this part of the country.  In actuality, their signal was weak and usable, so they had no problem with my continuing to pay for their BB service!

Fast forward, a few years.  Their network coverage had finally expanded to cover my area and to advertise the fact, they were stuffing leaflets through every letterbox in the locality.  As the EU-sponsored BB-rollout was a much better deal both financially and data-cap wise, I naturally opted to sign up.  Only to be told that I couldn't - but they had this alternative that cost almost twice as much and would I be interested...    After over 30min of this bullshit - I was after all, no longer in contract, so could have just closed my Three account, then immediately open the much better deal BB-account - followed by some more actual screaming at the rep, I eventually got my way.

The above experiences highlighted one thing to me - Three's primary focus is money, and despite all their rhetoric to the contrary,  if providing quality customer-care deflects from this goal in any way, to hell with its customers!

Edit:
After reading this post in its entirety,  it has dawned on me that I should also have re-read it before this 'Edit:' - it's just confusing!  So, this 'Edit:' also needs a major re-editing!

What I had written above about the reason my account had been blitzed from €70 to €7 was what I had been told by Three Customer Care (CC) - IDIOT, WHOEVER THEY WERE, THIS WAS NOT CORRECT!!!  The real cause turned out to be a 'service' that I was signed up for without my knowledge, and which had been debiting my O2 credit by €5 a week for almost 5 months!  Even though the Three CC rep. would have had this information in front of her when I called, there was not one mention of it.   I only discovered it when I looked through my call-history for myself online, something I didn't know I could do till then.  Next I contacted Three CC, explained my discovery, and was flabbergasted to be told that they were aware of this 'scam' (though she didn't use that word) but unfortunately could do nothing about it as it was a third-party operation.  It was then I went searching for info online (Three CC having yet again proven completely useless!)  and discovered that this scam was both well-known and has been ongoing for YEARS!!!  You would think that Network operators would ban these scam operators (PrizeVault in my case) from using their network - not a bit of it!  It was then I contacted Comreg Ireland.

Well, I emailed ComReg Ireland and was informed that they were well aware of this scam but had agreed to allow the company in question to reimburse any aggrieved parties that would contact them directly - which I was advised to do, so I did!  Within about a week I was sent a cheque for €95 - no note of explanation, no apology, nothing but the cheque!!!  So, they had been debiting my account for nearly 5 months, without so much as an email/text-message to me that they even existed. 'They' being a company named "PrizeVault".  My demand to know how they had gotten my details in the first place, to sign me up for this 'service', was met with silence naturally.

I've had further dealings with Three's Customer support since then as well.  Their email service is both a joke and an insult to customers.  The second-to-last time I emailed them I was waiting for 10 days for a response.  The last time, I lost patience after a week, so tried their 'Live-chat' help instead.  Much much better, and I had received clarification of my problem in less than 10 minutes.  I never did hear back from the email help.  If Three can't be bothered to provide a decent email help service, they should just withdraw what's currently on offer entirely. 

8 August 2014

The BRICs Superpower Challenge - book review.

Having just read this book, I'm left both frustrated and bemused.  I have seen quite a bit written about B.R.I.C.S on the web, and while the book doesn't offer an appraisal of 'S' (South Africa) it does offer a comprehensive analysis of the strengths & weaknesses of the other four, namely Brazil, Russia, India and China.  I figured this book would provide a decent foundation on these up-and-coming 'upstarts' who (using the book's terminology) in the not too distant future could provide both 'soft and hard' competition to the current bully-of-the-block on the global stage, the USA.

You do not have to read this book for long to realise that this is little more than a rehash of 'facts' that are currently viewed as being 'politically expedient', with actual realities never getting a look-in.  The entire book is devoted to analysing the attributes of the four, both good & bad, then using America as a yard-stick when scoring them.  The author then summarises, citing the country's strengths & weaknesses, and offers them advice on rectifying these problems.  Maybe this methodology is fine where 'hard-power' is concerned, but it's tough to stomach when the author recommends say, more "democratic" policies, as if the 'West', and the US in particular, were the only political systems that one should aspire to.  Particularly ironic given that democracy in America has long since had its hey-day, the US becoming more and more a National Socialist State as each day passes.

Equally irritating throughout this book is the constant conjuring up of the "terrorist" bogey-man.  Reference is made repeatedly to 911, the author even commending some of the countries (China and India in particular) on their immediate responses after this "outrage".  While it is possible that many/most countries initially believed the 'terrorists-with-bolt-cutters' story, there is now overwhelming evidence to the contrary - yet 12 years on, Mr Kwang Ho Chun was still promulgating this poppycock as if it was fact!  Given that the US is directly responsible for the deaths of more than 2,000,000 Iraqi's since the war that it started on a pretext that has since been proven to have been a blatant lie, it must be obvious to most who the real terrorists are!

This book may as well have been produced by the Rand corporation for all the 'unbiased' opinion it exhibits.  In fact, to my recollection, there is not a single critical comment regarding America to be found anywhere in this book.  Maybe that's hardly surprising given that the author is from South Korea - although the "South" part has been deftly omitted - making him far from unbiased towards American foreign policy.

All of this might make me seem anti-American, when in fact I'm not.  Just a romantic who dreams of the world that the American Ideal originally espoused, not the tyrannical hegemony that it is fast becoming.  Even the American public is (finally) becoming jaded at the direction that the "Land Of The Free" seems to be heading in.  Which is why the rats in charge are now looking to take away their guns! But I digress.

Long story short, not a very satisfying read. 

14 July 2014

Huawei E5220 rant...

Jesus wept.  There's a line from the John Cleese film 'Clockwork' that often comes to mind at times like this - paraphrasing, "it's not the 'despair' I mind, despair I can handle, it's the 'hope' that's the killer."  I had six days of hope that my wireless problems were at an end.  I had been connected continuously for that long, still with the same public-IP address.  Not a true test admittedly, as in that time I had also rebooted the laptop several times, flipping between old faithful Ubuntu 10.04 and the new Mint 17 install.  But for all intents and purposes, the E5220 seemed to have been performing admirably.

Until yesterday that is.  Last night, while web-browsing, and with a Intel 5100 <- > E5220 connection, without warning, the wireless disconnected, followed almost immediately with it reconnecting again.  That in itself was unusual, particularly the speed at which it reconnected.  Unfortunately, although reconnected to the E5220, there was no internet connection.  Checking the E5220's connection information via the Firefox browser revealed that there was no incoming signal from the ISP, a rare occurrence, but something that had happened a few times before, so was plausable.  But just disconnecting the 5100 NIC and enabling the Atheros 5008 gave me a live web-feed again - yet the E5220's connection stats. still showed there to be no ISP signal present.  To restore the 5100 connection, its driver just needed to be removed & restarted via 'modprobe'.

But my suspicions had turned from the laptop's on-board NIC's to the Huawei E5220 itself.  I then decided to reboot the modem via its 'Settings' options using the browser.  This seemed to have no effect - I still had the same public-IP and the connection stats still showing that there was no ISP signal, despite now having a live-internet connection.  I then tried resetting the E5220 to its factory defaults, again via the browser.  Again, no effect.  Seeing as I had a torrent on download, I left things as they were overnight, to find this morning that my download had completed, all 3gigs worth - so a perfectly healthy connection, despite what the E5220 itself thought!  I had to physically switch off/on the modem, before it realised that the ISP's signal was indeed present.

So I've gone from being suspicious of NIC drivers on my laptop - rightfully so, and through much suffering! -  to having my woes compounded with the knowledge that the new Huawei modems firmware is almost certainly buggy as well!  One of the E5220's improvements helps confirm this, namely its battery back-up feature.  Since I've got it, I have experienced at least one 'brown-out', a momentary interruption of the electricity supply, which would normally have reset my old TP-Link router, making it necessary for it to reconnect with the ISP again.   Since this can't happen with the E5220, it reduces considerably the possible causes for network disconnections.

What this means is that until Huawei fixes this firmware problem, I have probably just exchanged one set of firmware bugs for another.  Boo-hoo, not fair.  The only plus so far that I've experienced is that I've witnessed the fastest download speeds yet with it - over 850kB/s, but only for short bursts.  Most of the time it averages just 150-200kB/s.

Edit: The above little hissy-fit seems to have been premature.  A few weeks on, the E5220 has been performing exemplarily.  A rock-solid connection with no re-occurrence of the bug seen above.  What has surprised me even more has been the speed.  I now regularly see speeds of 700-950kB/s which is great!  This has been using a E5220 <-> Intel 5100 connection.  If ever I needed proof that the Linux ath9k Atheros wireless drivers are buggy as hell then this must be it.  I'll continue with this problem-free setup for another while before looking for confirmation and trying the E5220 <-> Atheros AR5008 setup.

8 July 2014

Linux Wireless (still) Sucks!!!

I've been using the long-ago EOL'ed (end-of-line) Ubuntu 10.04LTS as my main OS for several years now.  So, apart from the developers still issuing security-updates for it, development-wise it is dead, with most of its application repositories not having been updated for years (but thankfully, are still on-line).  Critical packages I had taken to building myself from source, but increasingly, 10.04's frozen-libraries (Python for instance) are no longer being supported either, so attempted builds often fail with unmet-dependencies.

Searching for a replacement, I settled on Mint 17 using the Mate Desktop.  Frankly, I expected more from Mate - a 'fork' of the no-longer-supported Gnome2 desktop - which I thought should at least have been on-par with Gnome2 by now.  No major faults, just lots of annoying little things that don't seem to work 'quite right'.  After initially believing that the snazzy Compiz desktop compositor would no longer work with Mate, I was elated when I got it going, but not perfectly - currently after logging on, I need to immediately change the desktop 'Appearance', which 'fixes' Compiz's initially-broken multiple workspace feature - changing the desktop-appearance in this way somehow gets multiple-workspaces working properly again!  Annoying but bearable, at least for now.

Anyway, after installing a brand-spanking new OS on a brand-spanking new SSD (Transcend 256GB) I hoped against hope that Wireless might at last also be working properly.  I didn't have to wait long - within 5 minutes, Linux wireless had lost its internet connection!  That was the final straw, I resolved there and then get to the bottom of this issue (somehow!).

My first act was to order a new wireless network-interface-card (NIC).  Seeing as most of my suffering for the past several years had revolved around Atheros cards (specifically the ath9k driver-class), those were obviously ruled out.  My experience with my Intel card (IWL3945) had been none too favourable either, but given that Intel is still heavily engaged in both developing and financing development of Linux systems, I decided to give them another go.  Ended up getting a Intel 5100 NIC for a very reasonable $10 all-in.

From the get-go, this seemed much more reliable than the (2) Atheros cards.  Nevertheless, there still seemed to be breaks in communication.  I had always known that my router's (TP-Link MR-3420) software seemed 'suspect'.  Often while cursing the Atheros cards as I restarted Linux (often the only recourse), to my dismay I'd find that I still had no signal!  But rebooting the router would fix the problem!  It was while Googling for others that were suffering similarly with this router that I came across the OpenWrt project.

OpenWrt it turns out is a Linux-based (yipee!!!) OS for embedded-systems.  Frankly I had never thought of my router like that, so was excited by the possibility of being able to swap out firmware that I knew was buggy for one that hopefully contained less bugs.  Actually it was an Aussie-based 'fork' of OpenWrt that I first came across located here, affectionately known as ROOter.  These guys apparently focus on working out the configuration details of the newer modems available, then combining these configuration-scripts with the current OpenWrt releases.

The slight downside to upgrading your router's firmware is that you run a real risk of 'bricking' it should anything go wrong during programming!  I've just recently found out that as long as you're prepared to get your hands dirty (and can solder) it's possible to un-brick them through a combination of software and a serial-cable.  That said, I've not had to go down that road (yet) despite flipping back and forth between different firmware-flavours over the past few weeks.  One interesting (and suspicious) thing about the MR-3420 router is that it employs an Atheros chip (AR6722) which also uses the very-suspect (to me anyway!) ath9k Linux driver.  I'd love to know where TP-Link sourced the AR6722 driver-code that's in their firmware.  Wouldn't surprise me in the least if it was the buggy ath9k driver-code that they used - it would at least explain a lot!

Anyway, although I've been playing with ROOter for about 2 weeks, I would need to leave things 'undisturbed' for at least a month or two before I could do an apples-to-oranges comparison between OpenWrt and the original TP-Link firmware - something I haven't thought of doing yet, as I've been, well, 'playing' with it.  What was quite disappointing to find was that neither of my Huawei modems (E169G, E122) were recognised by ROOter, although both connected to the internet OK - all the statistics-fields of the live-connection are left blank though.  This wasn't helped when 3 days a go, my 'fast' (7.5Mb/s) E122 modem suddenly died.  I chose the easiest option and simply upgraded my modem via my ISP - €30 for a E5220 modem and another 12 month contract.  Much more than just a modem as it turns out - faster 21Mb/s speed, battery-backed with in-built routing for up to 5 external connections.  Downsides - no external antenna support, and no microSD-card slot.  Unfortunately, this modem is not recognised by either the TP-Link firmware or the latest ROOter firmware.  Nor can it be controlled via the router (the other two modems can), so they cannot be used in combination. The downside of connecting using just the E5220 is that the signal between the E5220 and the computer(s) is noticeably weaker - understandable, since the router comes equipped with  2 large 3dBi antennas!  But as I'm composing this on that very setup, it obviously works well enough.  Surprisingly, the incoming signal from the ISP's nearest cell-tower is displayed as 'strong', even though the speed-tests done so far average only about 200-300MB/s at best - so not much better than what I was receiving with the other two modems, and certainly nowhere near what I was regularly receiving at my old address (600-700MB/s).

So a mixed bag really, result-wise.  I now have 2 NIC's installed in my laptop, although only one of them is ever being used.  Several times already, the Atheros NIC has lost the signal completely.  Switching to the Intel 5100 has resulted in an immediate resumption of the feed.  As far as I'm aware, the 5100 has yet to slip up.  Then again, the MR-3420 is now out of the loop completely, so it's really a different combination of software/hardware that's being tested...