Archive for January 2016

Other than for the landline, Iāve never bought a phone before. Each cellphone has come as a result of a company plan or a loyalty gift from the telco, but when my Huawei Ascend Y200 began needing resets several times a dayāIāve had computer experts tell me this is the phone, or the SD card (like any endeavour, itās hard to find agreement; this is like saying that the problem with an axe lies with the handle or the blade)āI decided to replace it. Plus, having built websites for clients it seemed only fair to have a device on which I could test them on an OS newer than Android 2.3, and after a few days I have to say the Meizu M2 Note has been worth every penny. (The Xiaomi Redmi Note 2 was on the shortlist but the Meizu performed better in online tests, e.g. this one.)
You can find the specs on this device elsewhere, in reviews written by people far more au fait with cellular technology than me, but a few things about arriving in the mid-2010s with such a gadget struck me as worth mentioning.
First, I opted for a blue one. Theyāre usually cheaper. Since I have a case for it, I donāt have to put up with the colour on the back anyway, so why not save a few bucks if the guts are the same?
Secondly, itās astonishing to think in five inches I have the same number of pixels as I do in 23 inches on my monitor.
Thirdly, cellular battery technology has come a heck of a long way. (Down side: you canāt replace it in this device.)
But hereās an absolutely wonderful bonus I never expected: itās Google-free. Yes, the Flyme OS is built on Googleās Android 5.1.1, but the beauty of buying a phone from a country where Google is persona non grata is that Iām not stuck with all the crap I had on the Telstra Clear-supplied Huawei. No Google Plus, Google Play Store, Gmail, Google Maps and all the other stuff I had to switch off constantly. I could have had the phone rooted but it never was a big enough priority, even with my dislike of the big G.
I donāt know how much ultimately gets back to Google through simply using its OS, but Iāve managed to keep away from signing in to any of their services. In this post-Snowden era, I regard that as a good thing.
The phone booted up for the first time and gave me English as an option (as the seller indicated), so the deviceās OS is all in the language Iām most fluent in. However, itās not that weird for me to have Chinese lettering around, so the apps that stayed in the Chinese language are comprehensible enough to me. There is an app store that isnāt run by Google, at which all the apps are availableāInstagram, Dolphin Browser, Opera Mini, plus some of the other admin tools I use. Nothing has shown up in my Google Dashboard. The store is in Chinese, but if you recognize the icon you should be all right, and the apps work in the language youāve set your OS to.
The China-only apps arenāt hard to dispose of, and the first ones to go were Netease, Dianping (I donāt even use an Anglo dining review app, so why would I need a China-only one?), Amap (again, it only works in China, and it can be easily reinstalled through Autonavi and its folded paper icon), and 116114, an app from a Chinese telco. Weibo I donāt mind keeping, since I already have an account, and I can see some utility to retaining Alipay, the painting app, and a few others.
And having a Google-free existence means I now have Here Maps, the email is set up with my Zoho āboxes, and 1Weather replaces the default which only gives Chinese cities.
What is remarkable is that the Chinese-designed default apps are better looking than the western counterparts, which is not something you hear very often. The opposite was regularly the case. A UI tipping-point could have happened.
I also checked the 2G, 3G and 4G frequencies against Vodafone New Zealand’s to ensure compatibilityāthere are at least two different M2 Notes on the market, so caveat emptor. Vodafone also recommends installing only one SIM, which suits me fine, as the other slot is occupied by a 64 Gbyte micro-SD card.
The new Flyme-based-on-Android keyboard isnāt particularly good though, and I lose having a full set of smart quotes, a proper apostrophe, and en and em dashes, but far more obscure Latin-2 glyphs are accessible. Iām not sure what the logic is behind this.
I had an issue getting the Swift keyboard to install, but Iāve opted for Swype, which, curiously, like the stock keyboard, is missing common characters. Want to type a g with a breve for ErdoÄan? Or a d with a caron? Easy. An en dash? Impossible.
This retrograde step doesnāt serve me and there are a few options in Swype. First, I had to add the Russian keyboard, which does give an em dash, alongside the English one, though I havenāt located a source of en dashes yet. Secondly, after copying and pasting in a proper apostrophe from a document, I proceeded to type in words to commit them to my personal Swype dictionary: itās, heād, sheāll, wonāt, etc. This technique has worked, and while itās not 100 per cent perfect as thereāll be words I missed, itās better than nowt.
I see users have been complaining about the omissions online for three years, and if nothing has been done by now, I doubt Swypeās developers are in a rush to sort it.
Swypeās multilingual keyboards are easy to switch between, work well, but I havenāt tried my Kiwi accent on the Dragon-powered speech recognition software within.
Going from a 3Ā·2 Mpixel camera to a 13 Mpixel one has been what I expected, and finally I get a phone with a forward-facing camera for the first time since the mid-2000s (before selfies became de rigueur). Itās worth reminding oneself that a 13 Mpixel camera means files over 5 Mbyte are commonplace, and thatās too big for Twitter. Iām also going to have to expect to need more storage space offline, as I always back up my files.
I havenāt found a way to get SMSs off yet (suggestions are welcome), unlike the Huawei, but transferring other files (e.g. photos and music) is easier. Whereas the Huawei needed to have USB sharing switched on, the Meizu doesnāt care, and you can treat it as a hard drive when connected to your PC without doing anything. That, too, has made life far easier.
Iāve been able to upgrade the OS without issue, and Microsoft (and sometimes Apple) would do well to learn from this.
It leaves the name, Meizu (é­ ę), which in Cantonese at least isnāt the most pleasant when translatedāletās say itās all a bit Goblin King. Which may be appropriate this week.
Iām not one who ever gets a device for imageās sake, and I demand that they are practical. So far, the Meizu hasnāt let me down with its eight cores, 16 Gbyte ROM and 4G capability, all for considerably less than a similarly equipped cellphone that wears an Apple logo. And itās nice to know that this side of Apple, one can have a Google-free device.

General Motors’ fine in 1995 for 470,000 cars using defeat devices against EPA testing: US$11 million. Volkswagen’s fine in 2016 for 580,000 cars using defeat devices against EPA testing: potentially US$40,000 million (or $40 billion, as the Americans say). The local companies get off far easier in the US. In fact, GM can even get a US$49,500 million bail-out from Uncle Sam. I realize there’s a difference between a settlement and a claim, but I wonder if Volkswagen’s going get away with paying less than a figure in the milliards.

An interesting weekend on Facebook. Despite regaining access, Iām not allowed to post links (with the accusation that my computer is infectedāsee above), and after considerable research, I know this to be completely untrue. The Facebook malware accusations are targeted at certain users and, from the tiny sample of four that have responded to me, we are all heavy users. Just as I theorized back in June 2014 when Facebook shut down for me for 69 hours, some of us have reached a limit on their servers.
Boffins, and Facebook, say that thatās impossible, but there have been countless signs of that over the years. Most were recorded on Get Satisfaction before Facebook shut down that community (how convenient). Among them were things such as Facebook being unable to show me every video I had uploadedāthe list began at 2011 and earlier ones were omittedāand the many occasions where I could no longer post, comment, like or share. Thereās a direct parallel to my experiences on the former Vox.com, which Six Apart confirmed in 2009 and which they had no official answer for.
Whatās the best course of action if Facebook accuses you of malware and forces you to download one of their programs from Trend Micro, F-Secure or Kaspersky? Delete your cookies. Once you do that, you can regain access, though, like me, youāll have a limited account where link-sharing is impossible. Initially, I was able to share a few links after my accessing Facebook, but it eventually became a blanket block, with the odd one getting through (two a day in my case).
If you want to be extra-safe, run the free version of Malware Bytes. The free one wonāt conflict with your existing antivirus set-up (Iām not trying to do Malware Bytes out of money), but, like the rest of us, youāll likely discover that your system is clean.
One woman got around this by downloading a new browser, although she was also limited on the link-posting.
Whatever you do, do not listen to these big firms. Facebook, Google et al are, as Iāve been documenting over the years, particularly deceptive. Iāve still had to deal with the remnants of Facebookās scan switching off McAfee, nearly two days later.
Facebookās apparently had many complaints about this since 2014, so Iām hardly the first to encounter it. Blaming malware for their own databasing issues is cheap, but enough people will believe itāeven with my mistrust of these big Silicon Valley firms I still did their malware scan, not thinking I had a choice if I wanted to access the site again. What it really did during the scan is anyoneās guess.
Iād rather they come clean and tell people: you are allowed x posts a day, x links a day, and x photos and videos a day. I can work around that. But if they came clean about this and the number of click-farm workers and bots plaguing the site, what will that do to their share price?
And isn’t it ironic I can presently share more, and have more freedom of speech, on Weibo, monitored by the Chinese Communist Party?

PS.: As of the last week of April, I have had two reports that deleting cookies does not work, but switching browsers does. Facebook appears to find a way to identify you, your regular browser and your IP address together, without cookies.

P.PS.: Mid-May, and from my other thread on this topic, in the post-postscripts: āAndrew McPherson was hit with this more recently, with Facebook blocking the cookie-deleting method in some cases, and advises, “If you get this, you will need to change your Facebook password to something very long (a phrase will do), delete and clear your browsers cache and history, then delete your browser, then renew your IP address to a different number and then reinstall your browsers.” If you cannot change your IP address but are using a router, then he suggests refreshing the address on that. Basically, Facebook is making it harder and harder for us to work around their bug. Once again, if you sign on using a different account using the same āinfectedā computer, there are no problemsāwhich means the finger of blame should remain squarely pointed at Facebook.’

P.P.P.PS.: November 30: it appears waiting it out is the best option for those who don’t want to mess around under the bonnet. Shawn Picker, in the comments, says to expect a five-day wait.

P.P.P.P.PS.: May 9, 2017: On the other post on this subject on my blog, a user called David suggested modifying your headers and to fool Facebook into thinking you are using another type of device. In comment no. 66 below, Stephan confirms that it works and gives more details about it. Check it out!

P.P.P.P.P.PS.: October 24: Again in the other thread on this topic, Don Dalton found that he was able to replace his Chrome profile with an older one to bypass Facebook’s block. Have a read of his comment here.

P.P.P.P.P.P.PS.: February 18, 2018: over the last few weeks, Mac users have been getting hit hard with this fake warning, and are being offered Windows software to download (which, of course will not work). Some have reported that changing browsers gets them around this. Downloading the equivalent anti-malware program from the same provider (e.g. Eset) does nothing, since the one user I know of who has done this came up with a clean Macābecause, as we already know, the warnings are fake.

P.P.P.P.P.P.P.PS.: February 23, 2018: finally, a journalist has taken this seriously! Louise Matsakis, a writer for Wired covering the security and social media beats, has looked into the latest round of Facebook malware warnings being forced on Mac users. Facebook is still lying, in my opinion, claiming there could really have been malware (lie number one), but the company’s probably so used to saying one thing and doing another by now. Louise is right to seize upon the fact that no one knows what data are sent to Facebook during the scan. It’s a fine article, and I highly recommend it.

Above: While the Kaspersky scan proceeded, McAfee was knocked out and could not be switched on. Coincidence?

Unlike most people, I have options open to me, so I began to go on to Facebook using several different methods. A VirtualBox containing XP on the same computer was fine, if incredibly slow while Kaspersky was doing its thing. (Think about Windows XP on a 386.) Lubuntu was fine as well, as was Mac OS X. I Tweeted the McAfee community link, and thought it odd that it did not appear in Facebook (I have my Twitter set up to post there). I then tried to paste the link into Facebook manually, whereupon, in Lubuntu and Mac OS, I was told that my computer was now infected with either a virus or malware. Unlike Windows, I had the option of telling them they were in error, and I was able to continue using the machines.
This really sounds like Facebook and Kaspersky have it in for McAfee and, possibly, rival products, if the scan knocks out your choice of antivirus and anti-malware program, and if the mere mention of mcafee.com inside Facebook results in a warning box saying your computer is infected.

Above: On a Mac, I couldn’t even tell people about the post on mcafee.com. The second I did, Facebook said my computer was infected. The same thing happened on Lubuntu. Facebook accuses you of infection on the mere mention of mcafee.com.

Eventually, the entire system froze, and while I could still move the mouse about, I couldnāt access the task bar or go to other programs.
I was forced to do a hard reboot.
But youāre asking now: was I ever infected? No. Itās Google all over again.Peter, the very knowledgeable McAfee support tech who came to my aid many years ago, was present again and put me on to two other programs after this restart. Getsusp analysed my system for malware, and, you guessed it, found nothing. Malware Bytes did the same, and found some PUPs (potentially unwanted programs), all of which I knew about, and I had intentionally installed. Theyāve been present for years. In other words, two other malware scanners told me my system was clean. Malware Bytes did, however, restore McAfee as the correct antivirus program, exactly as Peter had predicted.
He also suggested a system restore, which sadly failed, with Windows giving the reason that an antivirus program was running. Having restored this system once before (after some bad advice from Microsoft), I knew it couldnāt be McAfee. The only difference on this computer: I had had Kaspersky doing its Facebook scan. It appears that Facebook and Kaspersky donāt want you restoring your system.
I had fixed the newer issues, but the original one remained: I couldnāt get on to Facebook. The Kaspersky scan never finishes, incidentallyāyouāre stuck on 62, 73 or 98 per centāand while not having a personal Facebook is no great loss, I have businesses that have presences there.
I stumbled across a Reddit thread where others had been forced to download antivirus programs by Facebook, and, fortunately, a woman there had found where hers resided. In my case, it was at C:\Users\USERNAME\AppData\Local\Temp\FBScanner_331840299. Deleting this, and all cookies mentioning Facebook and Kaspersky, restored my access.
What to do if you ever come across this? My advice is to, first, run Malware Bytes, but ensure you run the free version, and do not opt for the trials. Once youāre satisfied your computer is clean, head into your cookies and delete all the Facebook ones, and any from the antivirus provider it recommends.This second Reddit thread may be helpful, too. I donāt know if this will work completely, but anything is preferable to following Facebookās instructions and wasting your time. I really need to stop following instructions from these big firmsāyouād think after all these years, Iād know better.

PS.: I found this video from last July which suggests the malware accusations have nothing to do with your computer set-up:

In addition, I cannot paste any links in Facebook. The situation began deteriorating after I regained access. Initially, I could paste and like a few things, but that facility eventually disappeared. Regardless of platform, I get the same error I did on the Mac yesterday (see screen shot above). Liking things results in the below error, and the wisdom there is to wait it out till Facebook staff get back to work on Monday.

P.PS.: Holly Jahangiri confronted the same issue as I did a few days later. She was smarter than me: she didn’t download the anti-malware malware. Have a read of her post here: other than that one difference, it’s almost play for play what happened to me for four days. She’s also rightly frustrated, as I am, by Facebook’s inaction when it’s legitimately needed.

P.P.P.PS.: I’m beginning to hear that deleting cookies will not work (April 26). Facebook seems intent on having you download their suspicious junk. In those cases, people have switched to another browser.

P.P.P.P.PS.:Andrew McPherson was hit with this more recently, with Facebook blocking the cookie-deleting method in some cases, and advises, ‘If you get this, you will need to change your Facebook password to something very long (a phrase will do), delete and clear your browsers cache and history, then delete your browser, then renew your IP address to a different number and then reinstall your browsers.’ If you cannot change your IP address but are using a router, then he suggests refreshing the address on that. Basically, Facebook is making it harder and harder for us to work around their bug. Once again, if you sign on using a different account using the same “infected” computer, there are no problemsāwhich means the finger of blame should remain squarely pointed at Facebook.

P.P.P.P.P.P.PS.: January 28, 2017: David has come up with a great solution in the comments (no. 103). You can fool Facebook into thinking you are using a Mac by changing the user-agent. He suggests a Chrome Extension. I have Modify Headers for Firefox, which might work, too.

P.P.P.P.P.P.P.P.PS.: October 24: Don Dalton found that he was able to replace his Chrome profile with an older one to bypass Facebook’s block. Have a read of his comment here.

P.P.P.P.P.P.P.P.P.PS.: February 18, 2018: over the last few weeks, Mac users have been getting hit hard with this fake warning, and are being offered Windows software to download (which, of course will not work). Some have reported that changing browsers gets them around this. Downloading the equivalent anti-malware program from the same provider (e.g. Eset) does nothing, since the one user I know of who has done this came up with a clean Macābecause, as we already know, the warnings are fake.

P.P.P.P.P.P.P.P.P.P.PS.: February 18, 2018: let’s see if Wesley Shields, security engineer at Facebook, will tell us what’s going on. He’s been asking for more staff to join his malware detection team.

Hi Wesley, Iāve seen a lot of people being told their machines have malware, but they run scans and they are clean. Happened to me in 2016. Is this something that your department has created? Iād like to learn more, but of course tagging Facebook doesnāt net a reply.

P.P.P.P.P.P.P.P.P.P.PS.: February 23, 2018: finally, a journalist has taken this seriously! Louise Matsakis, a writer for Wired covering the security and social media beats, has looked into the latest round of Facebook malware warnings being forced on Mac users. Facebook is still lying, in my opinion, claiming there could really have been malware (lie number one), but the company’s probably so used to saying one thing and doing another by now. Louise is right to seize upon the fact that no one knows what data are sent to Facebook during the scan. It’s a fine article, and I highly recommend it.