That doesn't sound right.

I'm not using ultrasn0w as I had my hacking fun with mk1 and have used factory unlocked phones since then.

But the dev team write tight code. I'd definitely look at OS processes to see whether it's the OS eating the CPU (if the CPU is idling but the phone is getting hot and the battery is running down, then it's the baseband) or the radios.

I'd probably restore from scratch though to baseline for a day (is it usable with a PAYG SIM from the 'official' provider?) to see whether it's faulty hardware, and then if not I'd use purplera1n and then ultrasn0w (if you need unlock) in the cleanest environment possible. Running these hacking apps on a machine that's also got a load of other stuff running can be a bit undefined.

One specific thing that's caught me out numerous times is that the Dev Team's older apps (PwnageTool and QuickPwn) don't expect more than one device on the USB tree... trying to jailbreak a 3G iPhone when there's an old mk1 iPhone connected to a USB hub that's hanging off the same machine causes confusion. I'd expect that any iPod connected may do the same thing.

So try a *clean* reinstall and see if you still have the problems.

For that speed of battery drain, you'd have to be running the hardware 100% - which indicates a bug somewhere, an infinite loop of some sort. Even heavy radio and CPU use (a good example is restoring an entire phone setup over Wifi with Cydia and iTunes - Cydia downloads packages over Wifi, the debian packaging tools use the CPU to install stuff, and with a full reinstall it's a fairly intensive workout for the phone) won't take half my battery in a couple of hours.