Skip to main content

How to improve HTC HD2? Use energy ROM!

I'm really satisfied with my cell phone HTC HD2. I've bought the device in February and I truly like the change, the innovation.

Logically, I've started to consider flash HD2 by one of many ROM's developed by guys around xda-developers.

There were three main reasons why I did it.
  • the device suffers by child ailment like wrong delivering of SMS. I've no time to watch and search forums and apply released patches
  • there are a lot of handful applications around HD2
  • there are a lot kinds of settings, it's hard to fine tune the device
The most widely known rom is the Energy rom.

What do you need to do to flash your device? There are two simple steps described in details within the article. Note that you should make the all flash stuff on the notebook to prevent against the blackout.

What the energy ROM brings me?

  • I have got the updated device all the time as I'm flashing it couple times per month. The rom contains almost 40 applications, see the complete list
  • HD2 keeps alive almost three days per one charge! This is the best improvement at all
  • the fine tuned and fresh graphic of sense environment, see screenshots, note that there are seven different graphics designs!
  • the fine tuned environment, all applications works together in the complete bundle
  • the whole device is faster, this is the main reason why "energy" :-)
 NRGZ28 made and is making the great work, I like it and I appreciate that! I also have to admit that sometimes the HD2 went down without any reason but it happen a few times.

Comments

Popular posts from this blog

Performance Battle of NoSQL blob storages #1: Cassandra

Preface We spend last five years on HP Service Virtualization using MsSQL database . Non-clustered server. Our app utilizes this system for all kinds of persistence. No polyglot so far. As we tuned the performance of the response time - we started at 700ms/call and we achieved couple milliseconds per call at the end when DB involved - we had to learn a lot of stuff. Transactions, lock escalation , isolation levels , clustered and non clustered indexes, buffered reading, index structure and it's persistence, GUID ids in clustered indexes , bulk importing , omit slow joins, sparse indexes, and so on. We also rewrite part of NHibernate to support multiple tables for one entity type which allows use scaling up without lock escalation. It was good time. The end also showed us that famous Oracle has half of our favorite features once we decided to support this database. Well, as I'm thinking about all issues which we encountered during the development, unpredictive behavio

ETCD: POST vs. PUT understanding

ETCD is distributed key value store used as a core component in CoreOS . I've already send a post earlier this week. Here is a page describing how to use ETCD basic commands = ETCD API. Code snippets placed in a page mostly use put , but ETCD allows to use post as well.  Most of us understand differences between those two commands in a notion of a REST(ful) service, but how does it work in key value store? POST Example over many words. curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" curl -v http://127.0.0.1:2379/v2/keys/test -XPOST -D value="some value" Two same command result into following content: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 { "action" : "get" , "node" : { "key" : "/test" , "dir" : true , "nodes" : [ { "key" : "/test/194" , "value" : &