Was It Worth It?

Here I am speaking of Gingerbread upgrade for HTC Desire. And in short - it was worth it.

First thing that I noticed after upgrade was different vibration feedback on key press. I cannot say whether it is better, worse or just a product of my imagination but it is noticeable. :) Screen looks the same as in Android 2.2 but there as subtle differences (e.g. icons in status bar).

There is improvement in speed. It might be just effect of finally clearing phone of all nonsense that got installed over these months but I think that there are some optimizations behind it also.

Although HTC did cut some applications, only one that I found missing from original ROM was Flashlight. Since this application’s install file is included in same zip file that brings update, I didn’t miss it for long.

Calendar application got small change - addition of time zones. This feature is worth the whole upgrade mess to me. As with all killer features most users will neither need nor notice it. However, if you travel a lot this is life saver.

Additional nice touch comes in form of “Pocket mode”. It basically makes ring tone extra loud if it detects that you have phone in pocket or case. I still have to see how this will work in practice but it at least shows some actual thinking.

And that was all that I consider worth mentioning. This is not a major upgrade as far as user interface goes nor it is as different as HTC would make you think. It is just a simple evolutionary step.

Gingerbread Desire

HTC Desire got it’s Gingerbread update!

In order to keep shitty attitude they have made it as difficult and frightening to install as they could possibly do. First of all, there is no version for Germany (Telekom Deutschland), North America, South Korea and Japan. Most of my readers will probably notice this “North America” part.

Another thing to notice is zip file with another zip file and then an installation inside. It reminds me of Babushka doll. All that is rounded with layer of warnings that would make Charles Manson seek his mommy. And for a good reason - all your data will be gone once upgrade starts.

In order to even think about phone upgrade, you need to get HTC Sync from HTC support. This is probably most bloated piece of shit software from HTC but unavoidable. Just to be sure this won’t mess with my development setup on this machine I made fresh install on my wife’s laptop.

Whole update takes approximately 5 minutes and it goes without any problem (if you discount wiping data as a problem). It leaves you with software version 3.14.405.1 (Android 2.3.3) and no hope of getting next update. :)

P.S. If you are wondering, my internal storage has 124 MB free.

Getting String Value for All Object's Properties

In last post I wen’t through task of restoring properties from their textual representation. But how did we end up with text?

It is as simple as loop through all public properties and then using TypeConverter in order to properly convert a value to it’s string representation. Do notice that ConvertToInvariantString is preferred over ConvertToString in order for code to properly work on non-USA Windows.

public static IDictionary<string, string> GetPairs(object objectInstance) {
    var result = new Dictionary<string, string>();
    foreach (var propertyInfo in objectInstance.GetType().GetProperties()) {  //loops through all public properties
        var propertyConverter = TypeDescriptor.GetConverter(propertyInfo.PropertyType);  //gets converter for property
        var stringValue = propertyConverter.ConvertToInvariantString(propertyInfo.GetValue(objectInstance, null));  //converts value to string
        result.Add(propertyInfo.Name, stringValue);
    }
    return result;
}

P.S. Saving key/value pairs to file is not shown here… guess how it is done… :)

Setting a Value From String

It all started with list of key value pairs from file. Each key was some property on object that needed to be set and value was obviously value for that property. Since there was no type information in file, I had to use reflection in order to set value. And then problem hit me. Reflection would not sort out my problem with converting string value to proper type.

To solve it, I just loop through all key/value pairs and find property with that name in my object’s instance. Once property is found, I get a magic thing called TypeConverter. TypeConverter enables conversion from string to proper type that can be used in standard reflection SetValue call. And thus problem is solved. Code follows:

foreach (var item in pairs) {                                                                         //go through all key/value pairs
    var propertyInfo = instance.GetType().GetProperty(item.Key);                                      //find property with same name
    Trace.Assert(propertyInfo != null);                                                               //we must have this property
    var propertyConverter = TypeDescriptor.GetConverter(propertyInfo.PropertyType);                   //lets find proper converter.
    Trace.Assert(propertyConverter != null);                                                          //we must have converter
    propertyInfo.SetValue(instance, propertyConverter.ConvertFromInvariantString(item.Value), null);  //set value
}

Microsoft’s All In One Code Framework

Browsing through one Belgian guy’s blog I found news about Microsoft’s All In One Code Framework.

In short, it is a site where you should be able to find best practice code samples. You can even make a request for some sample that you need. Of course, not all requests will be granted but interesting and much sought code should appear there eventually.

Of course, anybody can upload their code sample for any request and thus take some load off poor Microsoft guy who got writing samples as a task. :)

It is interesting idea, but let’s wait whether usefulness/noise will be better than rest of Internet.