[05.14.09] dB_ROM WM 6.5 21501,21502,21222,21231 ROMs/Kitchen TouchPro [Multi-ROMs]

[cmajewsk]

Originally Posted by tn_friend

Hey Decibel...i am enjoying your rom, but I had one issue.. it seems like everytime I turn my phone on, it will open up in email (messaging), it also seems to pop up messaging when doing other tasks....any suggestions?

I've seen this as well - and it's not necessarily happening when new mail arrives - it's fairly random. But I'd say it's better than messaging randomly shutting down...

[dodge_longhorn]

Hey when i modify the config.txt file to add a few things, it does not load the config.txt but some other default kind..does anyone know where the config.txt is located at.

[coolsac32]

Originally Posted by dodge_longhorn

Hey when i modify the config.txt file to add a few things, it does not load the config.txt but some other default kind..does anyone know where the config.txt is located at.

it is the operator config .txt file. because thats how it has been for other builds. but i could be wrong lol

[decibel]

It is the Operator_config.txt file.. But, be careful because this is in two folders. It is in <OEM\Herman\COMMON\PACKAGE_Raphael_CARRIER> and in <EXT\Herman\COMMON\Apps\Mortscript-4.3b2>.

If you include Mortscript in your build, you have to change it in the Mortscript dir. If you do not, change it in PACKAGE_Raphael_CARRIER. I have two because Mortscript has to be executed on first boot to register. The one in Mortscript overwrites the one in oem IF its included.

[decibel]

Sorry I haven't released the newest yet. I had to spend time with the fam this weekend. You know, it was Mother's Day and all. I do have a release ready, but need to get some sleep. I will upload it later today. At approximately 1200-1300 central during my lunch.

Just to let you know whats going on with it:

(*)HTC Notification Enhancement (Tachi/Rhodium Mix)
(+)Google Maps 3.0.1.6 (BRAND new)
(*)New taskbar Icons
(*)New Notification Enhancement Icons (to match taskbar)
(*)PowerOffWarning to match Notification Enhancement
(+)Zip Updated
(*)G-Alarm 1.5.1
(-)Dropped SprintTV & Sprint NAV to cab form for ROMs (Still in Kitchen)

Night! You have my word they will be uploaded today!

[Weapondrift]

saw this rom i think it was a week ago at XDA havent tried it yet but dont fret. Its the start of a new week.

[selders59]

Originally Posted by Weapondrift

saw this rom i think it was a week ago at XDA havent tried it yet but dont fret. Its the start of a new week.

I run db's rom. They are really stable and fairly fast. I have alot of my own app's and games added and still only use like 40% of program memory. Battery life is pretty fair. Could be better but I have used rom's that were alot worse.

[garyflynn]

Originally Posted by selders59

I run db's rom. They are really stable and fairly fast. I have alot of my own app's and games added and still only use like 40% of program memory. Battery life is pretty fair. Could be better but I have used rom's that were alot worse.

Who has the best battery life? And what is the best way to measure power consumption in a CDMA custom rom?

[decibel]

Originally Posted by garyflynn

Who has the best battery life? And what is the best way to measure power consumption in a CDMA custom rom?

I would say there isn't a set standard for testing battery life. I would recommend getting a baseline battery life number by using your "favorite rom" or "stock rom" for a couple days (a week would be preferable) and measure how much battery is consumed during a normal 24 hr period. Then get the average usage for those X amount of days. Then you can go to another rom and just use it a couple days and compare it to your original findings.

There are FAR too many factors in what causes batteries to discharge faster or slower. So a true "do this to test it" isn't there. There are even things that are out of your control that can affect battery life (weather, network maintenance, etc). During your comparisons, I would make sure you are doing the same amount of consumption (# of calls, time on data, # of times XX applications updates, etc) and staying in the same area (with good signal). Make sure the ROMs are basically the same. Programs installed, etc.

Good Luck!

[psyki]

Originally Posted by decibel

It is the Operator_config.txt file.. But, be careful because this is in two folders. It is in <OEM\Herman\COMMON\PACKAGE_Raphael_CARRIER> and in <EXT\Herman\COMMON\Apps\Mortscript-4.3b2>.

If you include Mortscript in your build, you have to change it in the Mortscript dir. If you do not, change it in PACKAGE_Raphael_CARRIER. I have two because Mortscript has to be executed on first boot to register. The one in Mortscript overwrites the one in oem IF its included.

Heh I assumed the one in the Mortscript directory was simply a mistake and deleted it. The proper way to have multiple configs would be to have something like mortscript_config.txt in the mortscript directory, and put an entry in the correct operator_config.txt file that says CFG: \windows\mortscript_config.txt. Although I believe in that scenario the mortscript_config.txt file MUST exist somewhere otherwise the script will fail, I can't remember exactly. Or maybe just put the mortscript_config.txt at the end of the operator_config file (but before sdautorun) and it will work whether the mortsscript_config is there or not, you'll have to test to be sure. There must be a proper or at least more reliable way to install mortscript...

I guess if I knew I was going to include mortscript I'd just add it to the operator_config script. Because either way having two copies of the config file with the same name is just asking for trouble, especially since Ervius kitchen by default will overwrite files without notification. Just my $.02