Colonel's Custom 3.3 Rom

[colonel]

Yuck. What all were you doing during these 3 hours? That is a definite increase in usage and consumption.

[Alwaysbelieve1]

i let the phone be. never touched it once.

[colonel]

Very strange. There is definitely something happening. Right now I have only the battery meter running and the data connection open and I am humming alone at around 50-70mA. How often do you check mail and to you just use poutlook or push? Any other scheduled things happening?

[Alwaysbelieve1]

i am on an exchange server and my phone is set up for push. the only app i ever have open is the palm messenging.

i received 2 texts during that time with which i never replied- just let the phone handle them.

i have deleted the O2 ink and msn ink from day one.

[tbhausen]

I saw similar high power consumption with the original 3.3 rom (using acbPowerMeter) and Direct Push enabled. That's the primary reason (plus miniSD not being recognized) that I've gone back to the official Sprint rom for now. There's definitely an issue with Direct Push and utilization of the data connection.

Thanks everybody for all your efforts to bring the latest AKU's to our Apaches!

Todd/Indy

[haus]

I just read another thread and got an idea about people's battery drain issues (maybe...).

There is a setting in the "buttons" applet under Settings called "Lock" that allows you to lock the hardware buttons so that when the phone is suspended, pressing the hardware buttons do not wake up the phone (only the power button or an incoming phone call wakes up the phone). Please note this is different from the today screen device lock, the "Lock" settings applet itself, or Jonathan King's onlock program. In the 2nd Verizon ROM (the updated one from UTStarcom), the hardware button lock was enabled by default - that was a change from the first Verizon ROM. So after Verizon users hard reset on the stock ROM, they don't have to worry about making that change to prevent the phone from turning on every time they press a button by mistake in their pocket.

Turns out that in Colonel's custom ROM, the default is unlocked - that is, the hardware buttons CAN turn on the phone when it is suspended.

I just noticed this, and I'm wondering if this is why my battery dropped 70% in 3 hours yesterday when the phone was in my pocket. I've reset the hardware button lock and I will try again tomorrow and see if there is any difference.

Colonel, you might want to consider making that change in the ROM - it makes a lot more sense to have the button lock default to ON, I think. I don't know where the setting is in the registry, but if people want to try it in the interim, you go to Settings...Buttons...then choose the "Lock" tab at the very bottom, and tell it to "Lock all buttons except Power button".


Hopefully that helps someone...

[Alwaysbelieve1]

nope not it. i always check to make sure the button lock it on. i did notice his was off by default.

this is one of the first things i did when i installed any rom.

i always have my buttons locked when suspended.

[haus]

I should note that I've had random issues with severe battery drain at times with all the ROMs (UTStarcom's, original 3.3 and Colonel's). It happened to me yesterday hence my post above after discovering the hardware button issue. But if that's not it, I'm still not willing to assume this is something about Colonel's ROM automatically, I think it may have something to do with the phone, push email, or the software I have installed.

Sorry, though, thought it might be an epiphany for someone.

I'm going to leave the post up though, because I think it's an important setting that people may overlook since it's a change from the last official ROM.

[sd_matto]

Hello-

Great work by Mike (for the tools), and by Helmi, Mike and especially Colonel (for the new 3.3 based ROMs, and for showing proof of concept on an actual customization).

Helmi's ROM (and the Colonel's, which has two extra copies of a 680K file, one in \windows and the other \windows\pem\) can be easily fixed via the custom tools following instructions on here. In addition, the smartdialer hack can be similarly fixed. All via the custom ROM tools.

As I was working my way through this custom ROM exercise, I thought about UPX and system files. At first, I tried a blanket UPX of EVERYTHING; did not go over well, and had to reflash. So, I was wondering about people's experience with UPXing ROM files, and, specifically, what ROM files can be safely UPXd. Your thoughts?

Thanks in advance.

[colonel]

Thanks haus, I am changing that now. However, I think that it is the Direct Push that is draining batteries. Since I dont use it, my battery seems to last a bit longer. Here are my stats after 90 min. Now: 101, Avg: 129, Total: 153. This is with some internet usage and outlook checking pop account every 15 min.

Alwaysbelieve, use the included Task Manager and go to Net Stats. Under IP stats, how many packets have been received? Output Requests?