Database Develop

Low memory error after new ROM flashes

For about the last 2 weeks I keep getting a "Voice Command has quit due to low memory" with any ROM. Yes, I always do a hard reset after I flash the ROM. It shows up before I even try to install anything. I'm not using any auto install programs during this so they are just the plain ROMs. Free program memory is also at least 50 MB, depending on ROM with 30-35 MB in use. I've just been removing VC from the StartUp.
I went back and tried the April 1 Dutty ROM that I think ran fine when I first tried it but now gives me an error. I reflashed the stock AT&T ROM and everything was fine.
I'm also having issues with HTC Home Customizer v1 in that it runs fine for a while then stops and gives a string of directory errors. I've gotten this when installed on both SD and device memory. It happens after I install some additional software but doesn't seem to be related to anything specific and has occurred with 2 version of HTC Home.
Wondering if there is a diagnostic program to check for bad chips or anyone else has seen this. I've had the Tilt for a few months and it just started acting up.
Thanks

Cant think of anything but hardware issues that would cause that.....
If i were you, i would flash back to the stock rom and spl, and take it back to att for a new/refurb one

mwp_742 said:
For about the last 2 weeks I keep getting a "Voice Command has quit due to low memory" with any ROM. Yes, I always do a hard reset after I flash the ROM. It shows up before I even try to install anything. I'm not using any auto install programs during this so they are just the plain ROMs. Free program memory is also at least 50 MB, depending on ROM with 30-35 MB in use. I've just been removing VC from the StartUp.
I went back and tried the April 1 Dutty ROM that I think ran fine when I first tried it but now gives me an error. I reflashed the stock AT&T ROM and everything was fine.
I'm also having issues with HTC Home Customizer v1 in that it runs fine for a while then stops and gives a string of directory errors. I've gotten this when installed on both SD and device memory. It happens after I install some additional software but doesn't seem to be related to anything specific and has occurred with 2 version of HTC Home.
Wondering if there is a diagnostic program to check for bad chips or anyone else has seen this. I've had the Tilt for a few months and it just started acting up.
Thanks
Click to expand...
Click to collapse
Use KaiserTweak or Advanced Configuration to Disable the File System Cache, in most of the new ROM's they are enabled that is why it is using so much memory even on startup.

impalass said:
Cant think of anything but hardware issues that would cause that.....
If i were you, i would flash back to the stock rom and spl, and take it back to att for a new/refurb one
Click to expand...
Click to collapse
Yeah, that was kind of my feeling. Was hoping someone would say, "Oh, happens all the time, just hit CTRL three times, say the magic word and it will be fixed."
My USB connector is getting loose anyway. I got mine through work and we have a dedicated AT&T rep so hopefully it won't be a big deal. I just need to remember not to say the words Flash or ROM.

KDKobes said:
Use KaiserTweak or Advanced Configuration to Disable the File System Cache, in most of the new ROM's they are enabled that is why it is using so much memory even on startup.
Click to expand...
Click to collapse
I seems no one else has reported this problem (and you know the forum would be full of posts it was common) so that's why I'm leaning toward a hardware issue.

mwp_742 said:
I seems no one else has reported this problem (and you know the forum would be full of posts it was common) so that's why I'm leaning toward a hardware issue.
Click to expand...
Click to collapse
Have you tried what I had suggested? People do talk about it just in the ROM Development Forum where it should be. And just so you know the AT&T Tilt is an 8925 not an 8950.

mwp_742 said:
I seems no one else has reported this problem (and you know the forum would be full of posts it was common) so that's why I'm leaning toward a hardware issue.
Click to expand...
Click to collapse
Don't worry I have the problem too.. now I am searching for the tweak and will post result after I try it

maybe clear the temps files from pIE

I've seen this same problem three times since flashing dutty's April 1 rom about two weeks ago. Haven't spent any time to investigate it yet.

Sounds like a possible .net issue.
I know there were a few missing files from the Apr. 1 ROM.
First, try re-installing .net cf.
Then if you are using Opera delete the Cache files, Take a look for files in \Temp, \Application Data\Volatile, & the cache/history/temp files for PIE.

Thanks for all the input guys (and gals? - yeah right!)
Guess I won't send it in to the shop yet (especially if they replace with a refurb).

Major rom issues i ned help sorting out

I seem to be having some biig issues with my tilt and was hoping for someone to shed some light on the situation for me, I have a tilt, now running on hyperdragon IIIr , hard spl 3.56 and a emonster radio, ever seince I've unlocked it and flashed the a rom I've ran into oone of two issues 1. rom works fine with exception to heavyish lag on typing that forces me to type slow (E.G. duttys 19716 hybrid) and I do a lot of typin so the lags is a big issue 2. running currrrently beforemention hyperdragon IIIr and emonster radio, (although I've had the issue on other radios) and it runs fine at first, I tap the power button don't use it for 20 mins or so then when it turns back on it either steps in from dark to bright and will be VERY unnresponsive like having to tap the windows button 20x times before I get one tap I've been flashing like a madman tyig tofind a rom that generaly works... PLEASE HELP

Learn to use search. I, as well as many other people, have the lag issue. It's been mentioned before.
The other issue could be either your device, ROM, or radio. Change to an official radio. If you still have the same problem, try going back to the stock ROM. If the problem continues to exist, it could be your device.
If it turns out to be the radio, simply change radios.
If it's the ROM, address it in the ROM's thread, not in a new one in a different forum.
If it's your device, you had better learn how to get it back to it's OEM state, provided you have a warranty.
Also, spacing, punctuation, and spelling tend to be helpful when seeking help. I'm not saying it has to be perfect, but it's nice for it to be understandable without having to analyze it twice.
Now, run along and play.

mr4r4n said:
I seem to be having some biig issues with my tilt and was hoping for someone to shed some light on the situation for me, I have a tilt, now running on hyperdragon IIIr , hard spl 3.56 and a emonster radio, ever seince I've unlocked it and flashed the a rom I've ran into oone of two issues 1. rom works fine with exception to heavyish lag on typing that forces me to type slow (E.G. duttys 19716 hybrid) and I do a lot of typin so the lags is a big issue 2. running currrrently beforemention hyperdragon IIIr and emonster radio, (although I've had the issue on other radios) and it runs fine at first, I tap the power button don't use it for 20 mins or so then when it turns back on it either steps in from dark to bright and will be VERY unnresponsive like having to tap the windows button 20x times before I get one tap I've been flashing like a madman tyig tofind a rom that generaly works... PLEASE HELP
Click to expand...
Click to collapse
It almost sounds like you installed an application that is causing your device to freeze up. Also, remember to hard reset after flashing. If you can please list the applications and sips you have installed and maybe someone can point out the culprit.

trust me spelling is never normally an issue but im typng from the device, unfortunatly I don't have a home computer at the moment. I've used search, I just haven't come across anything that matched my situation, the best working rom so far was duttys apr 29 hybrid. I've done some different radios and if anyone would be able to id love to read whatever setups you guys have on your devices thatwork and whatever issues you guys may be having btw my hard spl is 3.56 as well. I mean alll I wanted was 6.1 style messaging a good strong antenna (emonster is working well) if the roms fome with extras cool, if not its all good, I just need the device to work, thanks for all you help people
and btw the issue with the major slowdown is after flash (and hard reset) when I first tap the power button to put it on my belt for later no apps installed

This will be tedious, but try going back to AT&T Stock and see if you're still having an issue with the slowdown. Also, you might want to try looking for the Tilt Keyboard fix and trying that first. I still have lag with it, but it's worth a shot before you go back to stock.
If you still have issues with the stock ROM (try the stock SPL too if you can, there's instructions for going back to OEM you can click here to see those)
If you have the issue with everything set to stock, it's your device itself. If the problem goes away after reverting to stock, then try re-doing the whole SPL and flashing process for the ROM of your choice. At that point, you may wish to consider addressing your issue in that ROM's thread.

you are a genius, i ran it from the beginning and started it from scratch, i started with a light rom the new Hyperdraggon IIIr emonster rom and then hard spl'd at 3.29 (after i did the whole re stock and unlock process) im guessing i might not have done it right from the start and or the 3.56 spl might have been the problem also but its acting sufficiently well now i will keep you guys posted thanks for the support

I have 3.56 and have no problems. I almost always use a light rom and throw EVERYTHING onto my storage card. You also might trying running Pocket Mechanic

[REF] "LOCKUP" issue on HD

** Please check post #2 first. It looks like we have found a solution. **​
We don't reprimand anyone for asking questions, so feel free to ask (preferably after reading or searching the thread) if you have doubts.​
I'm starting this thread in the hope that we can determine and find a cure for the lockup issue some of us have been dealing with in the later Manila 2.5 version ROMs.
This is something I've been trying to deal with for some time now and it seems more widespread than people realize from the number of posts by users who have had this issue.
Let me explain my definition of "lockup":
1- It always happens when the device is in sleep mode, never while it's used.
2- Never happens with stock ROM or Manila 2.1, only on Manila 2.5.
3- It's random, could happen any time of the day, in any frequency.
4- It's more likely to happen with some ROMs than others, leading me to believe it is related to the ingredients used in the kitchen (that is: operating system/software ) The "lockups" will start within the first 24 hours and possibly become more frequent over time.
5- It's highly unlikely that any sw installation is responsible for this (NeoS2007_Driverpack_3 excluded, I haven't done sufficient testing with it)
6- When the "lockup" occurs, the screen lights up (you can see it does in the dark) but the device is unresponsive. If you wait for a while, the home screen appears but the device is unresponsive. The only way out is taking the battery out or doing a soft reset.
7- Using MTTY or flashing a stock ROM may help fix other problems but does not help for this specific case, the "lockup" will still occur.
8- It's entirely possible (but hard to determine) that hardware may be an issue here. The fact that some people always have this problem and others don't, may be due to different hardware revisions, if there are any.
9- This problem is very specific and never leads to a hard reset.
10- When the lockup has occurred, people calling may hear the phone ringing but the HD remains unresponsive and there is no call logged, so at least the radio section is working.
Please post you experience with this issue, including the ROM involved, and any action you have taken that leads to a solution.
Please also mention whether you flash using SD card or from the PC. Since none of my SD cards work, I always have to flash using my PC, so that is something I need more info on.

Please read this post to be uptodate on the latest situation with this issue
Quite a number of new sys versions seem to be causing lockups on most HDs. This is a sys problem and is not related to the lockup with the video drivers but is related to the OS version. If you are using a ROM with a new sys version and are having lockups, just switch to another ROM with a different sys version.​
As the number of pages in the thread started to increase, I want to post a summary of our findings here.
As stated numerous times, not everyone suffers from this problem but the number of people who do suffer seems to be much more than I originally thought.
Please remember that we are talking about a very specific kind of lockup here as explained in post #1.
So far, our findings indicate that it is a combination of conditions that cause this issue. If Manila 2.5 and the Neo's Driver pack are used together, this lockup will occur on those HDs that are prone to this issue.
mnet has prepared a cab that effectively deletes the driver pack and restores stock drivers. If you are having this problem on a Manila 2.5 ROM, you should try this. Needless to say, before trying this, you should have already tried the recommended cures, like flashing a stock ROM or using MTTY.
You can't actually delete the files cooked in the ROM, only replace them...Some dlls from Neos drivers remain in the windows folder, however they are no longer used due to registry modifications.
Several users who have been suffering from this lockup have confirmed that after applying mnet's cab to uninstall the Neo's Driver Pack, the lockups have stopped. So, it's a definite cure.
Cab to remove Neo's Driver Pack.
Also, please check this post. It may be worth giving it a try if you have unexplained lockups.
The Topaz D3DM drivers also seem to be causing lockups, confirmed by other users.
Mikenificent BlackStone TestDrivers seem to be safe. I tested for a few days and no lockups occurred.

sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.

homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?

Fallen Spartan said:
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.

I only had this with Dutty and Miri's 21xxx series with Manila 2.5.
Once I went to 28xxx series, from PDAViet, Energy etc, this hasn't happend again.
So I'm guessing its WM6.5 21xxx and 23xxx related rather then manila.
Also, it happens far less when you use a lightweight (short and low bitrate) sound for notification.
It seemed to happen for me whenever the "new mail" or "new sms" notification was supposed to sound.
When putting a very short sound, it stopped freezing. When putting back a long sound, it would freeze up more often.

bobsbbq said:
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.
Click to expand...
Click to collapse
A number of people have stated that they get issues with cooked roms (while others don't) if they are constant flashers, and the common solution would be to flash a shipped rom and then back to cooked. As I stated above I've been fortunate enough not to experience this so haven't had the need to flash a shipped rom. But from reading users issues this isn't a clear cut problem as it doesn't affect everyone

homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
I've ruled that out. I always install the same set of applications, same email etc.
Never have this issue on stock ROM or Manila 2.1 ROM, only on later M2.5 ROMs, so it has to be related to M2.5 somehow.
Xannytech has been very helpful, comparing ROMs where I had this issue with a few ROMs where I don't have it, it seems that the problematic ROMs are larger in size. So perhaps there is a problem with the NAND memory and the bigger size ROMs use it whereas the smaller size ROMs do not use it. This is the reason why I mentioned hw revision as a possible cause.

Fallen Spartan said:
Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
It does happen on a bare ROM, no data sync, no SD card, no applications installed. Just flash a new ROM and wait, it will happen.
I guess it would be OK to mention here that currently the only ROMs where I don't have this issue is with Miri's ROMs (which are smaller in size than others).

wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
currently using;
GridLeo 1.7 (1.2.5.30),
OS (5.2.21869)
Manila 2.5.19201130.0,
Radio (1.14.25.24)

termignoni said:
wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..
u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..
Click to expand...
Click to collapse
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.

makbil said:
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.
For your case, I suggest you flash a stock ROM and test with it for a while.
Click to expand...
Click to collapse
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
this is what is going on with my HD.. until one day, even after soft reset, i could not enter my pin or even access the calibration screen as i could only "tap" the top half of the screen..
after many soft resets, i could only "tap" the top half.. hard reset resolved my problem until a couple of days back, where the problem seems to start again.. this has been going on since last month, and out of the blue..

termignoni said:
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..
Click to expand...
Click to collapse
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.

makbil said:
I never got as far as having to do a hard reset but I guess it is possible after extended use.
I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.
Click to expand...
Click to collapse
i suspect it's a ROM issue as well, as i never had this issue with any other ROMs with the old Manila.. i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..

termignoni said:
i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..
Click to expand...
Click to collapse
If you do have this problem on a stock ROM, then definitely it's a different problem. Just remember to flash the stock ROM by running the executable and not through running the BlackstoneRUUWrapper + nbh file manually.

I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
http://forum.xda-developers.com/showthread.php?t=540290

bodgeman said:
I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
any reference to this "MTTY thing" u did? i might give a try 1st..

bodgeman said:
I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.
Click to expand...
Click to collapse
I also did the MTTY thing but had the lockup within 24 hours on Xanny's Evo 1.6. Keep a close eye on this, if you don't have it within a few days your problem may have been cured
Didi you flash from SD card or from the PC?

termignoni said:
any reference to this "MTTY thing" u did? i might give a try 1st..
Click to expand...
Click to collapse
Here . My results are on page 50.

makbil said:
Here . My results are on page 50.
Click to expand...
Click to collapse
thank you..
btw, this time i flashed using PC instead of the SD card..
one more thing to add, the first time i did my hard reset, i restored my device using PIMBackup (restored everything).. within 24hrs, it happened again..
the 2nd hard reset, i restored only my Contacts and till now (after 3weeks), only it's starting to happen again..
i don't know bout u, but this is how it's happening to me..
- at first, u'll notice a slight mis-calibration while typing an sms or selecting something (after screen calibration, everything went fine)
- then, after a few days, same thing happens (can't tap the bottom part, soft reset and screen calibration solved this)
- and today, after my device woke up on sms, i could not unlock (using the default WM6.5 lock screen - had to soft reset twice, then calibrate screen)

Icons are all jumbled up and hard to see

Can anyone explain to me how something like this may have happened and what I can do to correct it? I experienced it before when I was trying some registry tweaks, however this time it seems to have happened on its own.

flash another rom

No success - at least with all of the sense 2.5 wm6.5 ROMs. Problem keeps reoccurring.

jmreyesiii said:
No success - at least with all of the sense 2.5 wm6.5 ROMs. Problem keeps reoccurring.
Click to expand...
Click to collapse
i had the same problem but it was because of a missing file and the menu was getting all laggy....i just flashed omj's rom over at ppcgeeks and it worked again...

Yeah, tried OMJ's ROM too, and at first things looked fine, but then it happens again. I've even tried installing software one at a time and in different orders to see if it's a software conflict, but nothing confirmed yet. Oh well, I have the quicklinks with Cookie's Home Tab, so I'll at least have access my most common apps. The "techie-wanna be" inside me, and being a man, I still feel the need to solve this. If I ever do I'll advise the cause and solution.
Update: Well I used XTask to close what I believe was a mail app running in the background (I only use my Diamond as a PDA), and then I removed XTask from Windows/Start, so it doesn't automatically start. Now there is no lag, even after said apps were restarted. Can't say for sure now why I had the problem in the first place.

Sleep of Death" on (almost) every recent custom & stock ROM

Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!

Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?

MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.

Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.

Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there

It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.

I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6

Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.

Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now

Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster

Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.

I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?

Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?

I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.

I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.

aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster

aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks

kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.

Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks

kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.