Me and Nokia, we go a long way back; my first mobile phone was a trusty Nokia 3210 and it’s unique gaming proposition Snake.
I switched it for a Nokia 7710 because I was thrilled to be able to go on the Internet. The CSD data transport protocol, WAP and WML were very limited however and the phone crashed regularly (apparently it was the first Nokia with the Series 40 OS and it showed) so that didn’t last too long really.
A couple of years of infidelity later, while half the world went crazy about those iPhone’s and the other half was busy looking very business-like on their Blackberrys, I returned to Nokia for the Symbian-powered Nokia e61i, which I absolutely loved not in the least because of the hardware keyboard (a feature I missed on smartphones years after I bailed on my e61i).
And now I, the prodigal son, after a long string of good, bad and broken smartphones, have finally returned home, buying a 2018 Nokia 6.1 with 64GB internal memory (and 4GB or RAM) for under €300. Great build-quality with a aluminum unibody shell, 5.5 inch screen, fast charging, fingerprint, Zeiss lens … And it is running bloat-less stock Android 8.1 and given the Android One stamp it will receive continuous security updates and 2 years of OS upgrades. After 2 weeks of usage I can say this is the best smartphone I have owned to date! It sure feels good to have come back home 😉
android
Wordfeud, server maintenance & monetization
#Wordfeud servers are going down for maintenance around 06:00 CET. We expect 2-3 hours of downtime.
This message is 9h old but still no Wordfeud, so they must be facing major problems. Which begs the question; is Bertheussen IT into server-technology? And wouldn’t they invest more if paying customers could simply stop paying if service-level became too bad instead of paying a one-time fee?
The broken smartphone sequel
- 2014: Google Galaxy Nexus; 2nd hand replacement (a steal for only €95) with Cyanogenmod 11. Missed 4G, but loved the phone really. It just died on me within a week.
- 2014: ZTE Vec Blade 4G: no 2nd hand, 4G and not ridiculously expensive was what I was aiming for, so I bought the ZTE for just €170 and it was a very decent handset really. I sent it in for repairs under warranty mid 2015 after the power-button broke.
- 2015: Samsung Galaxy Ace2: much like the Galaxy Gio I used before a useable but underpowered small smartphone with an aging 2.x Android. But once one is used to it, there’s not a lot one cannot do with it (I typically want Firefox Mobile, WordFeud and a music player).
- 2015: back to the ZTE which was repaired perfectly, until after approx. a month it fell out of my pocket onto the ground, shattering the glass. I tried finding a shop to replace the glass, but ZTE being not that common I didn’t find one. So …
- 2015: Samsung Galaxy Core Prime VE: So I wanted a not-too-expensive big-brand phone (i.e. LG, Sony, Samsung or HTC) to have a better chance of getting it repaired outside of warranty, with 4G and a very recent Android-version (i.e. Lollipop) and that’s what the Galaxy Core Prime is about. I added a 16Gb class 10 SD-card and I bought a flip wallet case. Just to be safe I’ll go and buy a screen protector as well, because I am, as this list proves, not only spoiled but also clumsy.
The Broken Smartphone Breakdown
- 2009: HTC Hero: my first smartphone (although I wasn’t complaining about that 2nd hand Nokia e61i). I lost it on the train a year and a half after buying it
- 2011: Acer beTouch e110: cheap replacement for the HTC Hero, only used it for a couple of weeks before selling it because it was a horrible excuse of a smartphone.
- 2011: HTC Magic: 2nd hand replacement, it was a great little handset once it was flashed with Cyanogenmod. I sold it for my next new phone, the …
- 2011: Samsung Galaxy SII: Had a great time with that Sammy, lots of upgrades & tweaks. but I did need to have it repaired within a year of buying it, after it fell out of my pocket when getting off the train.
- 2012: Samsung Omnia 7: My first encounter with the Windows Phone Metro interface as a temporary device, while the SII was getting fixed.
- 2012: Samsung Galaxy SII: back from repairs and was very happy with it, but a year after that it broke down again.
- 2013: HTC Radar: temporary replacement for the SII, Windows Phone again.
- 2013: Samsung Galaxy S4: A brand new handset which I dropped approx. a year after buying it. Not really a huge leap forward compared to the SII, but I did love the speed improvements 4G offered.
- 2014: Samsung Galaxy Gio: temporary replacement for the broken S4. but despite the fact I got my main apps up and running (incl. Firefox Mobile), the old version of Android (2.3.6), the small screen and a serious lack of memory decided this was not a permanent replacement.
- 2014: Google Galaxy Nexus; 2nd hand replacement (bought yesterday, a steal for only €95) with Cyanogenmod 11. Early days, but I just might try not to drop it, I’m loving it already. The only thing I really miss is 4G support, because, after all, I am a spoiled brat.
Android Chrome bug when styling unicode character?
While experimenting with the use of Unicode characters in a small proof of concept, I stumbled upon what I think is a bug in Chrome for Android. Apparently character ☰, which renders as ☰ and which most people consider the “options”-icon, cannot be given a color in Chrome for Android whereas other Unicode characters can.
As you can see when visiting this test-page, the 3 symbols styled correctly (font color white) in most browsers (tested on IE8, FF on W7, Ubuntu and Android, Chrome on W7 and Ubuntu), but the options-symbol is not white on Chrome for Android (at least on my Samsung Galaxy S4).
So, does this qualify as a bug, or did I just mess up? Anyone happens to know a workaround?
Facebook force-feeding Messenger, going mobile web instead
So Facebook wants me to install yet another permissions-greedy app just to read messages? That is so frustrating! So no, don’t think so guys. I’m putting Facebook back into the (slightly) safer sandbox that is the mobile web;
So thanks for reminding me why I love my mobile browser that much Facebook!
Sammy’s dead, long live Sammy!
I was pretty happy with my Samsung Galaxy S II, especially after the non-trivial Jelly Bean upgrade some time ago. Because of that and as I wanted to wait until I had 3 vouchers from my employer (which covers the bulk of the cost of a high-end device), I decided to hang on to my S II for one more year.
But then (about a week after the guarantee period ended) it died on me. Black screen, no sound what so ever. I tried charging it (the battery was running low a couple of hours before), but the thing remained dark. I tried replacing the battery with a known good one, but still nothing but silence. I banged it against the counter of the shop where I bought it and threw it up in the air while yelling slightly frantically;
‘ELLO SAMMY!!!!!
Testing! Testing! Testing! Testing! This is your nine o’clock alarm call!
…
THIS IS AN EX-SMARTPHONE!
But the shop-guy just said my Sammy was stunned and that it was out of guarantee anyway.
So I needed an alternative. I started out using my wife’s ancient Sony Ericsson w810 (which I used before her) but that didn’t work for me. I then convinced a colleague (thanks Gregory) to lend me the HTC Radar from his collection of test-devices, but the Windows Phone experience was pretty similar to the one I had over a year ago. In the mean time I tried to find me a smuggler who could buy me a ZTE Open with Firefox OS in Spain (thanks Tamara, thanks Pieter & Tine) but Telefonica (Movistar) support couldn’t confirm it wasn’t sim-locked so I cancelled the order.
And then i saw colleague after colleague (Benoit & evil twin Jean-Paul) surrender to the sweetness of what is considered the current hotshot smartphone, the Samsung Galaxy S 4. And after someone (Gregory, great chap!) gave me his voucher (on condition he would get mine next year), I caved and ran down to buy me that beautiful telephone. So (again) no Firefox OS phone for me just yet, I have me a new PRISM-device to tame.
Thanks for reminding me about AdBlock Plus Google!
So Google removed AdBlock Plus from the Google Play Android store. That is their prerogative, off course, but it does confirm they’re not the cool technology-centric search engine everyone once thought they were. It’s kind of ironic that in December 2011 AdBlock Plus by default enabled the display of “acceptable” ads, a move that seemed to be an attempt to appease (or please) Google.
But whatever way you look at this, Google’s core business (as is Facebook’s) is displaying ads. Sure they try to do that in an intelligent manner. And sure, they have some cool technologies (App Engine, Android, Chrome, …). But at the end of the day they want us to see and click on ads. That makes Google a media company. But whereas traditional media have -at least the notion- of a wall between their editorial and advertising departments, editorial independence does not seem to exist over at Google.
I don’t like particularly like ads, I don’t like widgets snooping on my web-whereabouts and I definitively don’t like Google’s advertising department dictating what applications the editorial team in charge of Google Play should remove. So today I installed AdBlock Plus on all my devices. Maybe you should too?
Samsung Galaxy SII now with over 50 hours of battery life
After updating my Samsung Galaxy SII to Jelly Bean a couple of weeks ago, Samsung pushed even newer firmware (I9100XWLSD) to my phone which is the best of all official Samsung ROM’s to date: with the update JuiceDefender was able to squeeze over 50 hours out of my Samsung Galaxy S II battery:
As Samsung also released Jelly Bean kernel sources, maybe the great Cyanogenmod-team can finally also push out a stable version of Cyanogenmod 10 for the SGSII?
Emotional rollercoaster: installing Jelly Bean on a Galaxy SII
I’m happy! Here’s why; when I bought my Samsung Galaxy S II a year and a half ago, it came with Android 2.3 aka Gingerbread. Last year Samsung released an official update for Android 4.0 (Ice Cream Sandwich). And while most manufacturers stop after one major upgrade, Samsung promised Android 4.1 Jelly Bean for the aging SII a couple of months ago. And so early this week I took a ride on this Jelly Bean rollercoaster:
- Yay, Sammobile reports Samsung started pushing out Jelly Bean for the Galaxy S II
- Damn, apparently the ROMS are only available for Spain & China, not for my region yet.
- Yay, the Spain version has support for my region after all, downloading.
- Damn, can’t shut down my phone to switch to “download mode”, it just reboots.
- Yay, re-inserting battery while holding Volume down, Home & Power switches the phone to download mode after all, flashing with Odin!
- Damn, flashed and rebooted, but installation wizard hangs, rebooting.
- Yay, installation wizard completes after all.
- Damn, ADW settings screwed (widgets & some shortcuts MIA)
- Yay, almost done configuring ADW (except for the tethering shortcut on my desktop, can’t seem to reinstate that).
- Damn, no keyboard selection in notification bar, so no Swype!
- Yay, Swype available after all, hidden in “Language & Input” configuration.
So does Jelly Bean put the old S2 on the same level as the S3? Not really, some advanced S3-features aren’t included, think the ones in the Premium Suite for S3 that Samsung released a couple of months ago, especially “multi-window” (which might make less sense the smaller S2 display anyway). Both the Calender application and the mail-client (for my Exchange-mail) changed. Samsung replaced Calender with their own S Planner, which has a more skeuomorphic UI which doesn’t fit with the rest of the OS. Good thing you can install the default Android Calendar from Google Play. Mail got slightly better, with a nice little refresh-button and a timestamp showing when the last connection occurred (I don’t do push mail). But most importantly: Jelly Bean does feel more smooth (thanks to Project Butter) and at first sight battery life seems better as well. So, yeah, I’m happy!