[Desire HD Android Development] krzych:
Not that fast guys (I'm saying it to the testers). I don't know how you test roms, but I'm trying to be really careful. Add to the global reports mine:

- Cannot confirm GPS is slow - its fast AS HELL (1 second fix), so no, GPS is very fine

- It's not touch sensitivity like some users say - it's Rosie's sensitivity which is really HARD to use (every not stable touch is considered as a movement). Other launchers work as intended and as on any rom I had before. It's Rosie.

- confirming Aroma installer touchscreen issues (I know it's fixed already)

- Sound is better, but still something is wrong - when you run any other player than HTC Music, SRS is gone, moreover - when you install SndUI which is supposed to browse the processors and choose one, it browses something strange - not the processors (DSPs) like SRS, but some settings according to dual/single mic recording, playing by headphones or speaker and so on - by the way, DHD has only ONE mic, so it's completely OFF topic. You probably mixed DSPs from Inspire with DHD ones, or even supplied only Ispire's... OR HTC changed something a bad way (I hope not). SRS with external apps is a must too if someone wants to use for example PlayerPro, PowerAMP and so on (and many ppl uses those). By the way, Beats Audio is gone. I wont miss it, but it may suggest what's wrong to you.

- Importing backed up SMS stucks at some point and does nothing (you can wait hours), but if you press back and then choose to cancel import, it seems that ALL the sms are in place like backup was never cancelled. I know it may be HTC messing with app, but maybe it's fixable.

- no HTC Notes installed. The only usable notepad around is missing. It saves notes in XML so It's convertible/parseable/editable/etc. A must... I did restore it from 3.1.0 and it works perfectly

- Power saving seems to be gone

- Thai and zing keys aren't very popular I think ;)

Network location has very serious problems to determine my position while on 3.1 was immediate. Never waited more than 3 minutes, but I think in my location it never succeeds for now. GPS is one-second thing, but network is gone, which is very bad as it's only hope inside steel buildings. This was doublechecked.

And additions:

- We could use supersu (yes, I know already added), but a file manager could be nice too for _offline_ installations.

- I miss Quick Setting toggles on/off feature :) (can I restore Blackout app just like this? Won't I break something this way?)

- I miss battery bar, very very much

- I miss back-button kill too

---------- Post added at 06:30 PM ---------- Previous post was at 06:23 PM ----------

This is only theory never confirmed by life-examples. To be honest, much of ppl here confirmed the opposite. I can confirm that with _my_ usage, killer is not exactly a must, but I'm using phone rarely. As I did use it much, killer _would_ be good, but earlier I got background limit apps setting, so I could use it instead.

There is even simple explanation of this - memory expenses - companies try to save money giving us as little memory as needed and while upgrades, it shrinks (system eats more and more with each upgrade), so the mem left is very small. And to ANY memory management politics most important is to have a space at least for two, three aps in parallel. With DHD it's not as bad, but still I have issues of third app in the background being killed by _standard_android_mechanisms_ every time I use "bigger" apps (as I have many "daemons" - background apps doing useful stuff too, so overall app count is bigger). And no, standard killing is not fast enough - every time it happens, I have a lag - few seconds and then slowly phone gets back to its normal speed, but it lasts another couple of secs. It can be easily prevented, but I don't care for myself. For others if anyone is such a perfectionist, killer can resolve this. Or even kill buttons, but then you have to restore apps which you really need, whatever anyone prefers...

Just saying there's no universal advice... which you just served us. It's false statement, depends on real usage.