yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
hmm. I think the only thing i have being installed (via XDA_UC) Swype, HTC Messaging Client by DeathAngel and G-ThGraf, TOG Dial skin, TOG FMRadio and Booster skin, TOG Quick shutdown skin, NETCFv35.messages, NRGZ28 Disable DocumentIndex, and Pocket controller as well as a few reg edits.

What would be the best way of troubleshooting this? Uninstalling what was installed or cleaning out the XDA_UC folder and reinstalling?

I found a regfile for ameba. I know ameba isnt being used anymore (?) Could this be the problem?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GT247:
battery draining...

There's a high possibility that I'm mistaken on this but...I thought the issue or battery drainage/heat of late was due t
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
im guessing the rest of what you meant to say was google mail. And i thought that too, but it wasnt happening to me with earlier roms and stock rom.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] awalt:
The most recent episode of overheating/battery drain was experienced by quite a few users about a month ago give or take; it was due to a Gmail issue that occurred twice. The Gmail forum discussion and resolution (on their end) is here. That was not related to a custom ROM, as you can see from that thread people with all kinds of phones and OSes were suffering from it.

If it was me, and you have not already received this suggestion, I would Task29, reflash without your SD card so XDA_UC does not run, and see if the phone still does it in a release-ROM setup. Then install one at a time and see when the problem appears.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
Thanks i will do that. And yeah i had known about the gmail issue but i wasnt having the gmail issue when it came to earlier nrg roms and stock rom. I also deleted my gmail account from my phone and it would still happene on newer roms. So i figured my issue wasnt related to gmail. I will try your suggestion though. it may take a few days to full diagnose the problem, but i will try and update you guys with what it was just in case anyone else doe shave the same issue.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] monomer888:
I just wanted to say that I've had to put up with Exchange security policies for a while now and the only times I've had the 'forgotten' PIN effect was when I was doing something like messing with system drivers.

I suppose the policy you'd need to be careful about would be SD card encryption - this might require back-ups of the SD card before each new ROM flash. Luckily, my Exchange policy does not require this (yet!).

I do have to have device encryption enabled and I'm happy to say this works without issue with the plain Energy ROM. I remember reading, though, that CHT 1.8.5 had issues with device encryption... but as I don't use CHT, I can't comment further.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Good to know. I didn't even know there was a policy that would force sd card encryption. I have always been religous about backups, so I have everything on my SD backed up in full to multiple locations.

If SD card encryption is turned on, is there an easy way to tell?

All files are readable from my computer when connected as a disk drive, but I suppose the phone could be decryptiong it for that connection.

I'm going to search to see if I can't figure out what policies were pushed to it.

Start->Settings->System->Encryption

This is not checked, so I think it is safe to assume that my storage card is not encrypted.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] fibonaccievo:
is a beautiful rom
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] vo_danh:
Using 5/14 rom, i've been having issues with txt messages. Most times I try to exit txt messaging it stalls for a long time and sometimes doesn't even exit until i push the back button or start menu to get access to ark to close it. Also having camera issues, I can usually only take one or a few pictures before the camera stalls and freezes up the whole phone. I didn't have these issues on the pervious builds, but I updated because i couldn't recieve/send pictures/mms.

Could be winmo overclock but I had the issues even at stock speeds. Maybe I dropped my phone one too many times not seeing anyone else mentioning this. Testing with jackos rom haven't had the txt exit issue as badly, and overlocking slightly reduces it even more.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] monomer888:
Yeah I suppose the easiest way to tell is putting the microSD card into a reader, but I think the device will warn you before it applies any encryption.

With device encryption, I get an extra screen after boot-up where I have to press an unlock button to decrypt the device (takes less than a second) before proceeding to the PIN unlock screen. I have to say, this 'unlock' screen is rather ugly and doesn't have the usual NRG style to it! ;)

I don't know an easy way to list the policies on the device, and I've mainly used my work's policy documents to tell me which they were enforcing. Windows Mobile is apparently able to enforce all policies, but some require the exchange server admin to have an enterprise license to use.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
It sounds like device encryption was not put on my device because I don't get any extra 'unlock' button.

I googled quite a bit and haven't found anything to look for on the device to identify the policies that it applied.

Couple things I have noticed since using the new exchange server with the policy.

The Dual Boot Screen does not always display. I have only seen it once or twice since the policy was pushed down. I can still run haret to run android if I want. I did test this.

The people tab has not messed up at all since. I had backed up my contacts with outlook to a windows csv file. Then on the new computer connected to the new exchange server, I imported this csv file. I lost the pic associations and needed to use my app to add pic associations after facebook had updated and linked my contacts. Not sure if the new exchange is helping, or the fresh import of the contacts. But in the last 5 days, the people tab has kept the contacts in the correct places with every soft reset and has not randomly moved contacts around oon the tab. The new exchange server is on better hardware. The csv export / import may have cleaned up some junk. [EDIT]Got it to messs up after a soft reset right after posting. Before the home page loaded, I went to the people tab. One favorite was missing. Another soft reset and waiting until the home screen loaded and all was again good on the favorite people tab.[/EDIT]

I have seen Sense boot kind of funny, where you can go to the different tabs, but nothing displays correctly. Everythign is pushed up to the top. I had never seen that before. When in this state, there was some text message that is not from any contact of mine, but it showed a name of William something. After another soft reset, this message is not there.

Mostly I am including these things so that if people encounter anything like this, they will know that they are not a result of the ROM, but probably an exchange policy affecting it.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] monomer888:
Sounds a bit like the 'William Archbell' issue that has been mentioned at various times in the past (including this thread, I think). I've never come across it personally, but seems to be in relation to using a modified manila file.

If it continues to be a problem, there are 'William Archbell fix' solutions on xda, including the GTX thread.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Looks like my issue is some variant of that. I only see the problem if Sense fails to load properly. It's weird that it showed

itself after deleting my exchange connection and setting up a new one with a different exchange server. And it's never shown itself on my Tilt 2 for the near year that I have had it. No new mods recently applied either.

Looks like before people experienced the problem after sending a message. For me it shows itself only after a soft reset and it is right when sense loads.

Found William Archbell on LinkedIn.

[EDIT]I removed the link myself, just in case it would be a problem having it here, but if anyone wants to verify it, a simple Google search will find it.[/EDIT]

Developer for M$, then HTC, then back to M$. Guessing he left some debug relics in code he worked on. Or someone he worked with did.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] eac:
Sencity +

I've done some more changes to my Energy Sencity dialer theme.

For those of you already installed it, just download the zip and replace phcanImages.dll in the Windows folder.

Actually is about calling, incoming and in call screens.

I've attached in call screen.

Hope you'll like it. :)

BTW, just portrait for now...
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
@eac

This is very nice work--is this Sencity-specific, or will it run on other flavors of EnergyROM?

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] eac:
Well Jake, I've tested only on Sencity, but there are many chances to work with other Energy ROMs as well and some chances to work with another chefs' ROMs.

Just try it. You can uninstall. And if you replaced dll-s using a file manager, not by cab, you can make backup copies firstly of your original dialer's dll. If problems show up, after uninstall, replace back the dll-s too.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
So that's it ? you gave up on your love, GTX ? :)

Very nice work.. want me to include it in the ROM ?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
Okay so i am back and more confused now.

To go back to my original problem:

With the most recent NRG roms, my phone was overheating and the battery was rapidly draining. Slower at first, then faster and faster. battery would only last for about 2 hours.

At the same time, GMail started having issues on other people's phones. I pretty much ruled this out as my problem because of a few factors:

a. Phone was still overheating with no gmail account attached

b. Earlier nrg roms and stock roms were still running fine with gmail account attached.

It was kindly suggested in here that i flash a new NRG rom without the SD Card (no XDA_UC folder). It was a great idea and i dont know why i didnt try it.

So i did just that. I gave my phone 2 days. The battery was running fine. I then decided upon the following schedule. I would install 1 new .cab or make one major reg change every day at about noon. As long as my phone survived the night without dying, i took this as success and would move on to the next change.

I have been busy so i went a dayw ithout installing or changing anything. My phone survived two nights. Today i got a two phone calls. One after the other pretty much. Both calls were 5 minutes tops.

My phone began overheating and the battery drained in less than 2 hours :(

I have not made any changes that are related to phone calls. the only changes i managed to squeeze in were:

Messaging Client

Pocket Controller

Activated QuickGPS

Some changes to CookiesHomeTab

The MMS fix for Picture Message sizes

No Animation/Quiet Startup

EDIT: Tmobile provisioning

Any ideas would be amazing

I had yet to attach my gmail account to my phone.

I am going to start fresh yet again. This time making phone calls periodically before i make another change.

As far as i can tell, the problem is related to phone calls, but still cannot be certain.

Please, any idea would be awesome. It is only with the last 2 or 3 nrg roms.

thanks.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Actually he's from Romania... That's where I'm from as well. Only good stuff comes out of there obviously.. :p
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
Which radio are you using? Have you tried flashing a different radio? I think 4.49.25.95 is the recommended one for Energy, but it differs for each person. For me, the stock T-Mobile one (4.49.25.57) works the best. I get max battery life, quick GPS locks (about five seconds), very nice wifi signal strength, strong bluetooth connections, and very clear calls. My suggestion is to flash a different radio. It doesn't require setting anything new up. Use the device with the new radio for a couple of days, and then switch to a different one until you find one that works best for you.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
The radio i have been using is 4.49.25.95. It has worked great for me since i first flashed it month and months ago.

I am completely at a loss of ideas. Thank you for the suggestion.

I re-flashed again. this time i will spread out any major changes to a week or so in between. I am determined to know what the problem is. Ive been using nrg rom since i first got my phone and this is the firs time i have had such an issue. I just wish i could remember if it were the last 2 roms or the last 3 roms. It probably would help a little bit.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bogdan_wrc:
Amen to that :P

Are you working on a new ROM soon this week, or shall i update to the one from the 1st of June? :)

thank you.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GT247:
Lol NRG...I should have known, eh? You both do amazing work, sometimes it can be difficult to tell if it's origins are earthly...without you to explain to me I have no way of knowing....sure, I can look at the profile, but anyone can put a location there..it doesn't count 'til I hear it from you....lol
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
It seems that New nrg rom + phone call = overheating/battery drain. Still clueless as to how this is happening. It doesn't seem to be related to anything i install or change via registry.

Would love to know if anyone with TMobile is having this issue. As far as i can tell, there is no fix and im just going to have to revert back to an older nrg rom again and wait another month or 2 and see if it is fixed eventually. :(
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] NRGZ28:
Well it could also be hardware.....
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
What hardware could it be do you think? It is only with the last 2 roms. All earlier NRGRoms and stock rom works fine.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] eac:
:D No way!

I've just promise to somebody here to try to do something for Sencity and just took a little break from GTX. So only a little break...

I'll be back :p

To include it into the ROM?

I don't know. The "Sencity fan club" to vote for this.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
Love to hear this talk of Romania. My wife and I lived in Bucharest for three years in the late 90s and adopted our Romanian-American daughter in Arad.

Jake
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
Well, one way to test that would be to flash one of those older ROMs to confirm this. Perhaps someone here still has one from April that they could share.

Maybe NRG still has them. I noticed that the f1ip mirror site hasn't been updated since January. Either way, if it is only happening during a phone call, I would still suggest trying a different radio first, since that is way easier than flashing a new ROM or redoing any installing. Try flashing the stock T-Mobile one I mentioned before, since you have a T-Mobile device. Let us know how that goes.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
I have flashed an older rom to confirm it. I have been using nrg roms since i first got my phone last year. Then in april/may i updated to a newer rom and it started doing this. So i reverted backwards to most recent archived rom i could find (jan 1). every time i decided to see if the newest rom is working on my phone, it ends up not and i just go back. Stock rom works fine as well. It is just the last 2 or 3 nrg roms. I have also tried Jackos and and core cell evo. All worked fine. I am only having this problem with recent NRG roms.

I will install the default radio now.

Reverted back to default radio.

Flashed new NRG rom.

Called voicemail.

Phone overheated and drained.

I am join to go back to Jan 1 and try again next rom update.

I doubt it will mean anything but i should mention that, on occasion and on top of the battery drain and overheating, my phone will sometimes tell me there is not enough current coming from the AC to charge my phone (this is when i am charging it via USB and computer, not sure i have seen it with wall charger yet. It only happens sometimes.)

thanks again for your help though. I appreciate it.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
If you aren't doing a Task 29 with each flash, now might be a time to do it.

I honestly have only done a Task 29 about 2 or 3 times. Just when something unexplainable has been happening. In the end, the problem was always something else. But, since there are not other reports of this problem, it seems unlikely that the ROM is the issue.

A task 29 is basically going to make sure all the relavant bits are set to 0. So, that there are not any old remnants from the previous flash. Thinking just a little bit about it makes it seem like this should never be a problem. A bit is either 0 or 1. And the ROM image should write a value for every spot of the ROM. But, thinking a little further. If the last ROM or any previously flashed ROM was bigger, then there will be bits at the end that were not set by the flash so they are of an unknown state. This area should not be modifiable outside the flash process, so I'm still unsure on why this can be a problem. Nothing should be referencing areas outside the current ROM space. But if it did, 0 should probably be what value should be read. Without a Task 29, that is not guaranteed. Still, it would be bad practice of M$ or HTC to read areas not specifically written. My only other thought on why this might help is because there aren't really zeros and ones in the phone or memory. There are voltages. Specifically setting them through Task 29 will set the voltage for each bit to the level that represents 0. Just some ideas why a Task 29 might help. Some might be off base.

I am a software guy. I am by no means an expert on that whole are of the flash memory. But, Task 29 has helped some people with strange problems.

Another thing to try is RhodDiag. This will identify and mark any bad sections in your flash memory, so that any bad bits will not be used when ou flash. I don't really know the details on how this works. I'm guessing there is some other area that kees track of good and bad bits and it writes the info threre. You will need to google RhodDiag. I don't think it is on this site. I have found about 6 to 9 months ago.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
Thanks. I have Task 29'd. I do it before every flash. I will try that RhodDiag thing next time. I need to take a break from this :-/ It has been driving me crazy for almost 2 months.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Any possiblity that your phone got bumped or fell while something was plugged into the USB of the phone. Thinking that there is possibly a loose connection. Or some solder connection is causing a short with the battery. Since the problem started, have you given it a full 2 or 3 day test on the Jan 1 ROM. I only ask, since you did go 2 days on the current ROM without issue. Wondering if maybe it just takes some time for the problem to show.

Also, after a flash, power will show at 100%, even if it was 65% before you flashed. It will quickly come down to 65%. And it will almost always get warm when using Wi-Fi, which uses alot more power than normal phone usage.

Do you use alot of state widgets?

Have you checked in landscape mode also? Just because they aren't visible in portrait does not mean that they are not working and consuming power.

It sounds like you have really tried to find the problem. Just thowing some ideas out there for you.

Not sure of anything else to check other thna making sure settings such aas weather / facebook / twitter update frequencies are the same.

Maybe try rnning with the No Data app to see if that is what is sucking the power.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] billybag:
Here is a link to an earlier post. It describes my problem and what i have been doing to troubleshoot it a bit better.

the problem started in april. I tried to remedy the problem but had to take the dafe route and go back to an older rom because of current life situation. Reverting to the oldest archived rom i could find (jan 6) was, and still, works fine on my phone. I was using it for a month when i desided i would try and update my phone again. There has been another update since the last time i tried (jun 1) so i tried that. But i started getting the same problems.

I then took out sd card and installed jun 1. in the post above, i mention what i did after. Slowly made changes to my phone. it wasnt until i actually got a phone call that my phone started acting up again. So i installed jun 1 again and before making any changes, i made a phone call, my phone immediately started overheating and draining.

Older roms, stock roms, and other roms i have tried work fine and i gave them all 4-5+ days. Jan6 has been working for about a month, maybe a tad longer. Jun1 had been working for a few days, but then i got a phone call (i dont talk on the phone very often at all.)

FORGOT LINK:

http://xdaforums.com/showpost.php?p=14904273&postcount=35251
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] eac:
SOLVED, THANKS!

+1 for this...

I need the 23 of April GTX ROM as well and didn't find it anywhere.

Can somebody help with this matter?

Thanks to anyone who does.

All the best!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] JVH3:
Finally had some time to flash

I just finsihed flashing and setting up the June 1st, GTX ROM.

Very nice.

Like being able to use the Music widget. Not that I actually use it that often, but it just felt incomplete not being able to.

Did some serious cleaning of my SD card. Backed everything up first.

Also, wiped all pictures from my DCIM sub directories.

Got rid of everything that XDA_UC does not apply.

Modified my exchange.xml file to use the new Exchange server. Made one mistake on the domain name, but it was easy to correct after the fact.

Going to make a pre flash exe that will kill sense. Backup the HTC Connection settings and the twitter temp data.

Since it's 2:30 in the morning real testing will happen tomorrow.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] gregb882:
Nope, mine has been working fine. Allowing for the age of my battery, it lasts about as long as it ever did and I've been flashing Energy ROMs since January 2010.

Edit: AND... I set WinMoSpeed to 748Mhz. I never got more than 2 days - even brand new. Now, on the standard battery, I get about a day-and-one-half. Just yesterday, though, I got the HTC extended battery. But it's so new that I don't have a clue how much more life it will give.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] The Silent Man:
Regarding the SMS delivery notification issue...

If I enable SMS delivery notification from HTC client (menu->message option->message option) it will only work for messages sent from HTC client and after reboot it will disabled.

On the other hand, enabling SMS delivery notification in Advanced Config app works only for messages sent from winmo SMS client. Reboot sometimes preserves settings but sometimes it doesn't.

Situation in which we have two SMS clients is very weird. When I start a new message thread I can only use winmo client but when I want to reply to recieved message I must use HTC client (the one with baloons).

Is it possible to use single client in all situations?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jakfish:
@billybag:

I have a TMobile TP2, overclocked to 748, without your problems. I get the same results as gregb882.

Jake