Data Usage Monitor in Android ICS

Found this while playing around with my HTC One S running Ice Cream Sandwich (aka ICS, aka Android 4.0) while on vacation and roaming (!).

If you pull down the Settings menu or open it via the apps screen under *** more you will find a Usage menu.

Opening this will reveal some very useful and detailed statistics about the data usage of your phone.

You can see the wireless data as it accumulates over the data usage cycle as you define it. Since I am on a corporate plan where the billing cycle starts with the first of the months, I set the usage cycle to the month. If your billing cycle starts on the - say - 21st, you should change this to 21st to 21st of the following month. Set the Reset data count value for this.

You can also set two different thresholds.

1. A simple warning when a certain data volume is reached within the usage cycle - see the 1.0GB bar in the graphic
2. A real limit, where - once reached - the phone will no longer allow a data connection. As you can see I have not activated the hard limit.

If you scroll down further, you can see in detail how the data is been use per application. This lets you easily identify data hogs, giving you some good data points when you want to tweak your data consumption.

In my cases here (just for demo) a good idea would be turn of one of the podcast players (I have both, BeyondPod and Google Listen active right now... more on this later), and also restrict them to Wifi only... Or maybe do less Facebook while commuting :)

Very useful indeed. If you are running ICS already, take a look at it.

BTW: You can turn this on for Wifi, too. This will give a separate tab on this page.

HTC One S

For almost exactly one and a half years my son was the owner of a Sony Ericsson Xperia X10 mini pro. To be precise, he had two of them, probably three - since we had the first replaced immediately. With all three of them, the Sony showed huge problems with charging the battery after a while. We already went through an external charger, which worked fine. So it was never a problem of the battery, or the USB cable.

So about a week ago, I decided to get myself a new phone and pass the HTC Desire Z on to my son.

At first I could not really make up my mind between

• HTC One S
• HTC One X
• Samsung Galaxy S III

So I want to a A1 store, where they had all three of them on display.  The S3 and the One X are of almost exactly the same size (in all three dimensions; or four if you include weight :) ). Although the display of the One S is significantly smaller, the whole body of it is only marginally smaller than those two.

Since I still don't like the Samsung skin, and I - quite frankly - love HTC Sense, the choice was only between the two HTCs.

Or in other words:

• Do I need 1280 HD on my phone? - No
• Do I need NFC? - No... not yet, not sure if ever.
• Do I need a 4.7 display instead of 4.3? - No
• Is the One S display sufficient ?  - Yes
• Do the One X features justify 100 EUR more? - No

There. I ended up with a HTC One S and I'm totally happy with it.

Android 4.0.x (Ice Cream Sandwich)  and dual core are just ... wow.

I'll continue to report on my love for this gadget in the weeks to come.

Back to the basics for my phone

As much as I love my HTC Desire Z (or Vision for the US guys), it had one major flaw from day 10 or so.

For about 90% of the incoming calls, when I answered them (drag, or click on the <Answer> button), the phone would not really answer the call, it would keep ringing... and the other party would continue to get the ringback tone. After 7 or 8 or so rings, it would finally put the call through. Sometimes it would take too long, and I'd lose the call.

Annoying.

Very annoying.

Well, my dear friend V. noticed this behaviour the other day on my phone (granted, after a couple of beers) and told me there was one of those creepy #*codes that would switch of some networking stuff and make it work normal.

So while he was searching his archives to find this code, I also did some googling myself and found this behaviour described like this:

If you sync your Facebook contacts (on an HTC Desire)  this could happen; and the solution -   delete the Facebook contacts - seemingly did help a couple of users.

Well, it was a convincingly high number of users that reported both the problem and the success through removing the Facebook contacts.
So I gave it a try, removed all my Facebook contacts, had a co-worked call me (a couple of times) and it seemed to work.

3 hours later, V. sent me the code.

Enter the following code in the dialer screen. *#*#2347#*#*

So I did.
(and got a "CFU query when camp-on is off" message... talk about non-cryptic :))

It still works fine.

Only problem now is, ... Against everything I learned and preached when I was working in software support decades ago, doing heavy problem determination work... never ever change two parameters at the same time, when you want to get to the problem source... never ever ... you understand?!

Well I here did... So I still don't know what made the phone work, removing Facebook contacts or V.'s cryptic CFU-query-when-camp-on... code.

So if anyone else runs into this problem, please try only one of them, and report back here.
Thanks

Anyway... my phone is now back to its basic functionality, taking calls.

How to build up a 1000+ € phone bill..,

... without you knowing.
And no roaming.
Or doing anything different ... compared to the previous month.

This is what just happened to a friend of mine:
She learned from their operator that she ran up a 900€ data bill, and the month (i.e. billing cycle) was not even over.
Did she have an app running, that kept data open? No.
Did she have a video running in the background? No. [1]
But she did have a 15MB email in her outbox that could not be sent for days.

The email app (on the iPhone) was trying every 3 minutes.
Could be tracked down with the operator's help.

My guess: it failed, because the mail server (or mta) did not let it send a 15MB+ email...
So it kept retrying, without any chance to succeed.

Simple math:
3 minutes a day = 20 times an hour = 480 times a day

Lets just say it successfully transmits only 1MB before the error[2], that's still 480MB ~~ 1/2GB a day.
Continue for a week or so, and you have 3.5GB... and through the 3GB ceiling and you hit the area where it gets really expensive.

And she really did not do anything wrong. Claimed that there was no error message, from the mail-app... And why should there, it kept retrying anway...

Well, the operator in an act of humanity - or to avoid the negative publicity of a court case - found a way to help here. But only because it totally breaks her data pattern until then.

--
[1] The operator really asked this... no pun.
[2] unlikely, it probably occurs after a lot higher transfer volumn, so those are best case numbers.

Dinosaurs mating

So... Nokia and Microsoft seem to mutually feel that they need each other to survive in the mobile / smartphone world.

I guess there is some truth to that, and it will play out to some extent:

• Microsoft needs every hardware manufacturer they can get for their Windows Phone 7.
  In that regard, Nokia is very important and helpful to them: they still do have a huge base of followers, and they do have the operator connections.
• Microsoft will gain a lot by the uni-lateral exclusivity: every Nokia smartphone will come with Windows Phone 7. So if you want Nokia (and a smartphone) you have to go Windows.
• Nokia needs a good OS... Symbian was OK  - years ago, but would never stand up to iOS, Android or Windows Phone.
• On the other hand: there's a good chance that Nokia smart phones will become just another HTC/LG/... phone.

There are still good reasons to choose Nokia:

• They have robust hardware design - even Windows can't take that away.
• They do know a lot more about radio and the phone functionality than Apple and the Android folks combined - but lets see if this can make it into a Windows phone
• If you only want a feature phone, Nokia (with Symbian) is still an excellent choice.

What I'm not really sure about is: Do people explicitely want an iPhone or an Android phone ... or do they "just" want a nifty smart phone, and don't really care about the OS (and app ecosystem). The lackluster 2010 sales of Windows Phone 7 (despite all the push from Microsoft and others) and the decline of Nokia Symbian smartphones indicate that it really is about the OS (iOS, Android).

Let's see.

And one more thought:
Remember that Palm with the Treo once thought the found their salvation by giving up PalmOS and being embraced by Microsoft?

Sad.

My Android Family

So, now my whole family (sauf moi) now has Android phones:

Relation	Model
wife	Samsung Galaxy S (i9000)
son	Sony Ericsson Xperia X10 mini pro
daughter	HTC Desire

And myself still with the old Nokia E71... (not for long, I guess).

So after a couple of days of use here's the quick breakdown:

Galaxy S	(Android 2.2) The largest of them...excellent display. Worst PC companion software (Kies). Updates only through the PC software.
Xperia X10 mini pro	(Android 2.1) Not really my kind of phone, mainly because it is too small. OK-ish PC-Software (Sony Ericsson PC Companion 2.0) installable from the phone.
HTC Desire	(Android 2.2) Best body/housing and general haptics. Also quite fast (to me it seems faster than the Galaxy). Also I prefer the mechanical 4 buttons over the soft buttons of the Galaxy. OK-ish PC-Software (HTC Sync)installable from the phone, but this does not really matter, because it updates over the air (!).

My favourite: The HTC Desire .. can't see why, but it seems to beat the Galaxy S.

Also the Xperia X10 did only last one and a half battery cycles. Simply does not charge ever since. Seems to be a bad contact in the USB/charging plug. I hope to be able to register this as a DoA. I'll be posting the results here.

The activation experience was the same and excellent for all of them [1] - as long as you are not paranoid of Google. Just exporting the contacts with the good old Nokia PC Suite from their old Nokia phones, import the .csv file into their Google contacts, and have the phone sync. Done.Gmail is there, market place is there.  No fussing around with iTunes etc etc...

I guess I should try the HTC Desire Z because of the physical QUERTY keyboard. But I have to test this first; I do have my doubts about Android with a physical keyboard... does not seem to fit (from my brief X10 mini pro experience). See how this measures against the near-perfect keyboard on the E71 (probably the best feature of the E71... along with the phone stability and battery lifetime).

--
[1] Well I can only guess for the Galaxy, because my wife activated and personalized it herself while she was on vacation during summer. I guess this is quite a good benchmark.

Facebook Phone ?

So the last 10 days or so saw a lot of rumors, denials, half-hearted confirmations and semantics about a Facebook phone.

Current state: they are obviously not manufacturing the hardware (what a surprise) but teaming up with INQ mobile to integrate facebook into (or rather:onto) the software stack.

Does it make sense to have a Facebook feature phone?
Not to me.
The Facebook apps for the various smart phones are powerful enough. Just to have your (phone) contacts synced with facebook[1], does not require or justify a Facebook feature phone. Much less the crappy Facebook chat.

Does it make sense for Facebook ?
Sure  - Three words:

mobile.
ad.
revenue.

As I'm saying, the are a (only) marketing platform...

I rest my case, your honor.

--
[1] if you want that at all - I don't.

Microsoft's Kin is dead

The Kin will be discontinued and never make it to Europe.

So what?
Is anyone really surprised by this?

First of all, Microsoft never had a good track record with or mobile phones (and their operating systems) nor generally with hardware...

Secondly, a pure social network phone that's cluttered with status updates, tweets and stuff does not make any sense. A phone is still a phone, and not a social network beeper or pager.

If I consider my social graph - any of them, be it Facebook or on Flickr or on Xing or on Twitter - I'd panic if I'd get all their updates directly on my phone.

So lets grieve for the Kin...
Then again.... No, let's continue to ignore it.

Function Follows Platform

With a bit of hands on experience with the most recent generation of mobile phones (or smartphones, I guess I should say; iPhone/iPod touch, E71/S60, X1/Windows mobile), I noticed that it is more and more the platform that dictates what and how the phone does things.

E.g. my rant about the X1/Windows not being able to handle an alarm like every other phone on this planet.
Or that with some functions I feel that the E71/S60 is - as a phone - way behind my previous Nokia 6233/S40: Can't schedule a call on the S60, I could on the S40 (which is supposed to be inferior).

I haven't had any experience with the G1/Android so far, but from what I saw with those other phones, it will most probably be the same:

Function Follows Platform.

The (downward) stack now dictates the (upward) user experience.

As much as I like open platforms with easy and open developer access and app distribution, I hate what it sometimes does to user experience.

Sad, somehow.

Why Microsoft should not do phones

1. See today's news about the dying Zunes (they are not phones - I know - but the same category of devices)

2. A coworker and friend just got an Sony Xperia X1 ... cool phone, if it were not for the Windows Mobile inside. What he (a long time Nokia user) discovered was, that you should not switch off the phone when you rely on the alarm to go off in the morning, because it then wont.

Yes. True.
With Winodws Mobile, the d*** phone is stays switched off and the alarm just wont sound.

What I dislike about the E71 / S60

As much as I like my Nokia E71, there are some regressions vis-a-vis the previous Nokia pure-phones I had:

The 6233 could schedule a call - you had a calendar entry that represented a call to another person.
When the notification would pop up, you just had to press the green button to actually call this person.
Quite handy.

Not on the E71. Does only know of "Meeting, Memo, Anniversary, To do", but not of "Call".

Quite disappointing.

My new Nokia E71

The Noka E71 is probably the best Nokia (smart) phone I ever laid my hands on.

And I have to admit that I hated Symbian based phones in the past... the communicator series, etc.

They were slow, hard to use, had a bad form factor (ok, that's not really related to Symbian), and so forth.

And when the iPhone was first released I really thought, I'd never move from my POMP (plain old mobile phone) to a Nokia SmartPhone...

Enter the E71.

• It is fast.

• It is lean (SW wise I mean)

• It has an excellent form factor.

• The display is brilliant.

• It comes with Wifi, Bluetooth, 3G, GPS (my order of importance, should be more space between 3G and GPS … ;-) )

• Email actually works:

  • not just „ POP over IMAP“, but the phone client and the server actually stay in sync.

  • I can actually read an email (ok, more display size related, then phone OS)

  • I can see and open attachments … and read or work with them too

• The camera is OK (not really important to me, but still; see this for a test)

• Gmail, Gmaps, Skype (via fring), flickr-upload work amazingly well for a phone.

• The tiny QWERTZ (the german layout for QWERTY) keyboard does work well. Better than the virtual keyboards on iPhone and friends.

Still, there are some classical Nokia goofs (you did not expect me the ever stop ranting about nokia, did you?)

• its predecessor, the E61i had the concept of access point groups , where you could group e.g. your home Wifi, your office Wifi and your 3G connections (i.e. access points) into one group, and then assign this access point group e.g. to your email connection settings. So email retrieval would work on any of those networks, but go over the faster and cheaper Wifi first.
  No longer possible with the E71.

• Automatic email retrieval is a cool thing, but can you spot the missing item here ?
  
  Why - oh why - just not every (1) hour ?
  

• I can no longer schedule a call in the calender. That's really a loss to me... I used that feature a lot for “scheduled call backs”. I still can set a reminder of course, but there is a lot more typing involved – both when entering the reminder as well as later when doing the call. It used to be just one click (on the green button).

And I get a full new set of typos when SMS/texting now that I moved from T9 to QWERTZ ;-)

Most missing feature on my Nokia

The last parade of Nokia mobiles I had [1](and still have) lacked one important feature:

If I go to the calendar „application“ I can schedule a call with a person from my contacts list or any phone number I choose to enter. At the given time I will get a reminder and - by simply pressing the green „call“ button - I call this person.

Nice.

Comfortable.

Good.

Why, then, can't I create this entry from a person/contact context. E.g. I am in the address book / contact list, or I am in the missed/received calls list... most of the time I want to schedule a call (or call back) from there. I saw that someone called e.g. whilst I was in a meeting, and I want to call him back after the meeting, say in 30 min. Or I just called someone, got on their voicebox and want to try again in an hour.

Why didn't anyone think of this use case?

Why doesn't any mobile support his ?

I just checked: not even the iPhone...

[1] 6310i, 6230i, 6233

Sun and Samsung developing 'Java phone'

A late edition of an April Joke ???

"McNealy said Tuesday in Seoul that the companies were working on a 'Java phone' that would surpass Apple's iPhone in functionality and cost less, the mass-circulation JoongAng Ilbo reported."

Report: Sun Microsystems, Samsung developing 'Java phone' - International Herald Tribune

Update for Nokia 6233

Finally there is a new software version for the Nokia 6233 out: V 05.10 (check it at http://www.nokia.com/A4305060).

This fixes my problem with the previous release (4.91) which would not allow Google Maps Mobile to connect to the network. Now it works again...

Wifi vs VoIP

Before Christmas I had a conversation with some former colleagues of mine. We had all worked for the same wireless operator, and most of them still do.

During that conversation one of them said, that he thinks that VoIP over Wifi will replace GSM because its cheaper.
I begged to differ:

His line of thought was, that Wifi is cheap and now that PDAs and phones do support voice over Wifi (e.g. Skype).
Everybody, he said, will switch to PDAs with Skype getting access from cheap local hot spots. GSM (or rather managed/operated voice and networks) will cease to exist.

To me there are several obvious flaws in this reasoning:

Wifi is not cheap.
Granted there are free (as beer and as in speech) hot-spots (like fon, but only a very limited number of them.
Commercial hot-spots charge horrendous amounts per hour/day...
T-mobile in Austria charges 1€/min or 8€/hour; A1/mobilkom is even more expensive

Wifi is not easy to configure
Well, maybe it is on the mac, but not on Phones and PDAs. To be clear, it's still easy to configure the pure Wifi/radio stuff, to get access to the
small network at the hot-spot, but that usually does not give you internet access beyond the hot-spot. In order to get that, most sites force you through some web authentication to be able to charge you.
Repeat for each location where you want to place a call.
Don't even consider a handover (like you are used to on the mobile)

Wifi is not easy to find
Forget all the finder services and icons and logos and what not. You still have to look for it.
GSM/3G you don't have to look for.
It's just there.

I wouldn't want my proverbial mother to have to configure a Wifi phone (not even my real one).
Nor do I want to have to educate her on the usage of the phone...

The transition from the good old fixed line phone to the mobile was difficult for many people, but essentially the only real change was, that you have to press the green button after you keyed in the numbers.
That's it. Ah, end yes, you no longer needed a cable.

Consider all the changes between the classical telephone sytem (including the mobile) and VoIP/Skype over Wifi.
It's more then just the green button. You have to register with several operators, you have various accounts...
So most people just wont follow you there.

Granted, it is possible, and to (us) techies it is a viable option, but only as long as we can cope with the service and usage limitations.

There is really no technical limit: Wifi can transport voice with top quality (provided the hotspot provider knows his stuff)
It's really just the people.

Wifi phone services do work already.
They can also work for my mother, but only stationary, i.e. replace the phone at home by a Wifi service.
My point is only about mobile networks, not about fixed line or home installations.