Differences between various HTC Vision (Desire Z/G2) builds

There are a number of different builds for HTC Vision (aka HTC Desire Z, T-Mobile G2) which are distributed by various carriers and HTC itself, they are as follows:

  • WWE (World Wide Edition)
  • TMOUS (T-Mobile USA)
  • Asia (HK, India, TW)
  • Hutch AUS (Australia Vodafone)
  • BellMobility WWE

Each build has different features, and different /system/build.prop which varies from setting the GPRS Class of the device to power saving features and ability to use no SIM card on the device.

I've been working on discovering the differences between various builds to find out why one build or another uses less power. One of the key factors in controlling a build of HTC Sense/ASOP is /system/build.prop on Android.

Currently I have written a script to compare the different versions and spit out a CSV which I can then export to a Google Spreadsheet. It's certainly interesting to see the differences between the various carriers and regions, especially in terms of wireless restrictions (like Bell Mobility disabling Fast Dormancy in their build.)

Fight against HST ramps up

Fight against HST ramps up, via CKNW.

A citizen's initiative application to kill the incoming H-S-T has been approved by Elections BC.

The initiative petition is a legally binding petition that, if successful, will require the BC government to hold a referendum on the H-S-T, or repeal it in the legislature.

I, really hope that this initiative passes. I will most likely be part of the petitioners. I do not believe that we need a "harmonized" tax that will raise the prices of a large majority of my day to day activities.

If we had exemptions like the maritime provinces do, it would be okay. But as the HST is, it's a big giant lie in British Columbia.

Linux RAID mdraid "stripe_cache_size" vs. transfer rate

Part of the Linux RAID mdraid RAID6 & RAID5 benchmarks, and Linux RAID mdraid RAID10, RAID0 benchmarks (continued) series.

"stripe_cache_size" vs. transfer rate

Generated with the following shell script:

for cache_size in 256 512 768 1024 2048 4096 8192 16834 32768; do
 for i in {1..3}; do
 echo ${cache_size} > /sys/block/md0/md/stripe_cache_size
 echo 3 > /proc/sys/vm/drop_caches
 echo "stripe_cache_size: ${cache_size} (${i}/3)"
 # for write
 dd if=/dev/zero of=/dev/md0 bs=3145728 count=5460
 # for read
 dd if=/dev/md0 of=/dev/null bs=3145728 count=5460