[Hero, G2 Touch Android Development] Hacre:
RIGHT then folks.

It would appear, thanks to Google and their stellar changes to Google Apps </sarcasm> my roadmap is completely bollocksed up now and FroydVillain 1.3 will be arriving sooner than expected.

There has had to be a -lot- of changes to the framework code (not just by myself but by the great folks at Cyanogenmod and other contributors) to get a lot of the stability issues resolved as well as various other bugs.

This one isn't going to be fixed by a hotfix I'm afraid.

I'm looking at a release either tonight depending upon how busy I am, or tomorrow. I'll keep you all posted with the ETA. I'll also make sure we have backup download methods in place due to the issues we're having with the server accepting requests from various providers at the moment (I don't deal with the server hosting).

Just a quick note about CPUSpeed. It's the only CPU management app with crash detection and it's there in case someone tries too low (or too high!) a frequency and gets system issues. Unfortunately, due to -NO- fault of CPUSpeed or Alankila, when you shut down Android it doesn't do a clean shutdown, apps are simply killed so CPUSpeed has no way of knowing whether the system was shut down, or if it crashed.

We thought about it and figured when phones are stable, the amount of reboots or shutdowns they actually endure are rare so we kept the crash detection in. I'd rather a few of you weird rebooters had to quickly re-enable a management app rather than take away something that makes it a bit easier to recover from CPU experimentation.

A note about battery life. I put the kybosh on my Hero last night and over a period of 14 hours it's lost 14%. This is after a full calibration and stats wipe. During those 14 hours it was trying (and often failing) every 10 minutes to get a GPS fix for the weather update, Touiteur updating every 15 minutes, Facebook syncing and Gmail pushing.

So I repeat. If you're having battery issues, it is not the ROM, it is not the kernel, it is not CPU speed, there are other causes that we need to get to the root of.

At the FroydVillain project we've taken a hard line stance that we're not going to simply work around issues and introduce bad practices to "fool" our users that everything is hunky dory. We would much rather do things right and identify apps or configurations that cause issues than just leave the issues as they are and work around them. It's the only way we're going to improve quality at the point of delivery.

So I guess with that I can ask you to either be patient and keep reporting bugs (and also reporting apps that are unnecessarily greedy on resources to the app developers) or feel free to use another ROM while we work on this overall improvement project. I assure you though, in the long term, ours is the better approach.

So yeah. I'm now working on 1.3. I'm figuring out some issues with a build process for the Nexus (my main phone is actually a Nexus One, I've been intending a Villain rom for it for ages now and the Hero has taken all of my time) and then I'll start looking at test builds.

Thank you all for your patience.

You don't. Just put your key in. The apk is the same.

Hehe. When you initiate connections over adb, you're putting activity in the run queue. Activity in the run queue switches up the CPU.