I recently falshed the new WM6.1 ROM from the HTC website. The only problem I can't seem to get around is when the phone is locked and put in sleep mode, a few seconds later the screen will flash white for a second. And then periodically blink white. Mainly I don't want to waist precious battery life. Its now driving me insane. I've looked and searched for hours on hours and can't find anything like this.
I've hard reset, soft rest. Got rid of the bloatware. But still got this blink.
Any help would be greatly appreciated!
Thanks in advance!
I've came across this several times with many 6.1 roms. I am not sure if a fix exists. However, this has never bothered me. I simply click the power button twice and the blinking stops. Hope this does the same for you.
All The Best.
Same thing happens to me. I will be watching to see what the response is. Bugs me too. No idea how many times that's happening while it's in my pocket or something - not good for battery life and can't be good for the screen either...
Empire101 said:
I've looked and searched for hours on hours and can't find anything like this.
I've hard reset, soft rest. Got rid of the bloatware. But still got this blink
Click to expand...
Click to collapse
As already mentioned several WM 6.1 ROMs suffers from screen flashes relating to power management issues. Using the latest HTC WWE WM 6.1 ROM the TyTN II will occasionally require two button presses to come out of power saving mode.
If you were happy/happier with the WM 6.0 ROM complain to your ROM provider and if necessary request it be reverted (or read up here and once you know whats required, do it yourself). I don't see any 'new' official ROMs coming for this device now it's comparitively elderly, so I think it'll be up to you to come up with a solution.
HTC has provided an HotFix for that issue at :
AT&T Tilt WM 6.1 Backlight HotFix
But Truely speaking, I installed and it didn't worked for me.
It might work for you, so just give a try.
Regards,
Thanks guys. I'll try the double push of the power button and see if it works, if not I live with it a little longer, till I go mad.
If I can't take it anymore I'll just re-flash to a different ROM.
Once again, thanks for the replies.
By the way the BACKLIGHT HotFix didn't work for me either. I think thats mainly to fix issues with the backlight timer always reverting back to 10 seconds, no matter what the user setting is.
Been lurking around for quite a bit now, been flashing my diamond since i discovered xda-dev, and with that goes out awesome thanks to the chefs out there for pushing what our phones can do, and how quickly they do them!
Though I've run into a problem that search cant seem to find an answer to!
My Diamond requires a Hard Reset about every 12 hours, and if it doesn't, then all programs disappear, and eventually it'll hard reset itself!
I was running CT's 6.4 for 2 months without a single lockup, decided to flash topaz r6, then back to CT's 6.4 and then bam, problem started. I've tried numerous roms, seems to have developed into a chronic problem with all of them.
I've managed to uncover this problem, or very similar to this with other devices, especially when moving to a wm6.5 rom, and it seems the fix is to flash back to a stock rom, then to the rom of choosing!
But this is where I'm on the confused side. My phone is a branded (rogers) diamond, htc doesn't seem to have released a stock rom for this phone, so I'm not sure how to go about fixing the problem!
If someone has some insight, you'd be a huge help! Thanks!
Just flash ANY stock ROM. Doesn't need to be branded. Just one that is not cooked. Any one that is released by HTC or a Telco should do the trick.
if flashing a stock rom doesnt fix your problem have a look here http://forum.xda-developers.com/showpost.php?p=3433851&postcount=22
cobbs,
After 3 weeks, that quick fix solved the problem right away!
I appreciate you digging out that answer for me!
Hi! For a while I've been searching for a reason why my phone seems to freeze almost daily while charging or before / after I snooze a morning alarm. And sometimes during the night, maybe it's random. By freeze I mean the phone is sleeping and when I push the power button nothing happens. The only way to restart it is to take off the cover and either remove the battery or press the little reset button.
I use itje's ROM with standard WM6.5 and Manila 2.1. I tried diferent builds and newer Leo ROMs, but I always get the same problem. It didn't happen some time ago when I was using WM6.1 + Manila 2.0.
While searching in the forums for solutions, I noticed there are some users with the same random freezes using various ROMs from different chefs. But most of the users don't seem to have this problem, which is weird. I guess the hardware should be the same, so does anyone have any idea why this freezing happens only to some of us?
I tried different methods and ROMs, countless hard resets and re-flashes, even additonal Stock-SPL and Hard-SPL, but nothing seems to work. It even happens if I install no other programs and don't have the SD inserted into the phone, only my SIM card. So it's not from external programs (like G-Alarm) either.
Well, any helpful information or advice? Thanks!
I am experiencing the same problem. If anyone got a solution for this, please share.
Regards, Eduardo.
i have the same problem to but only with the cooked wm 6.5 roms and higher not with the rom that came with my x1
i get the same problem. i'm using itje's Touch I-T Xperience 15 6.5
Now I flashed a WM6.1 ROM with Manila 2.1 to see if I still get the problem. Do you think our phones have a problem with the Windows 6.5 builds or maybe the problem is with Manila?
Did anyone try to live with one of these ROMS for a few days with Manila disabled to see if you still get the freeze? Maybe I'll try this also after I finish my 6.1 test. It's very annoying that we don't even know the cause for this freeze yet...
have the same problem when using 6.5 but when on 6.1 nothing of the kind...
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Well, I can confirm that on various itje 6.5 ROMs I get the standby of death without installing any alarm program. I didn't install ANY programs, for what it's worth. And others can use G-Alarm 2.3 and don't get this freeze.
Didn't use Valkyrie ROMs yet. I'm testing now Touch X 10.8.2 and I have G-Alarm 2.3 installed. Let's see if it dies in the next 48 hours while on a 6.1 build...
Here is my experience...
I never got standby freeze issue(never used G-alarm/Klaxon), but i do get black screen or garbled screen issue randomly while receiving call irrespective of the ROMS(wm 6.5/6.5.1).
Only one time almost a week i didnt face this issue, then later problem repeated. So i realized that week i've used COM4 build. So for testing it i tried again same one for a week and problem didnt exists. Since the ROM which i used has default X1 dialer which i didnt like at all.. so got updated to other ROM and started face the same issue
Maybe some of us have a slightly different harware in our X1 that triggers this freeze, but only in WM 6.5?
So far the WM6.1 + Manila 2.1 is working fine, lots of customizations made by me after flashing too. G-Alarm managed to wake me up OK.
Darkchaser said:
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Click to expand...
Click to collapse
Well you can count Valkyrie 4.5.502 out because i installed it yesterday and this morning after my alarm went off about 20mins later the phone frooze. I have been experiencing this for the past months and i REALLY hate this phone now. I have tried all sorts of tricks from reseting the phone around 9pm to just not running ANY program and it still freezes. I have tried all sorts of roms with the exception of Touch X 10.8.2. I guess i might as well give that one a try. I will keep an eye on this thread for a solution.
On an older Valkyrie TR build I was getting the problem and I fixed it by doing a soft reset with the SD card out, waiting for everything to load up and run nicely, then inserting the card again. Went to the music tab and waited for it to load all my tunes and the same with photos. Didn't have the problem after that, but I was only on that ROM for about a week.
I thought it may be related to usb port driver issues in WM6.5, but it could also be the audiomanager in manila or some conflict between a WM6.5 process and a manila process.
Anyway, will be trying 4.4.81TR Valkyrie and see...
But the biggest question is why some (most) people never have this problem...
Never seen this problem on WCX 22001 Pure wm6.5 rom and I'm using it for about one month. I've installed many apps and my X1 works great with battery about 2-3 days using WIFI, BT, and all other stuff. No Manila - no problem in this case. It's an older build of WM6.5 but with newer builds WCX Rom users didn't complain about freezing problem or alarm issues.
So maybe it's Manila?
Today I wanted to flash Itjes newest ROM but I'll wait for solution couse my phone should wake me up today
Can program your phone Lockscreen has frozen the rechargeable device. Best before charging you restart your phone and not run any programs.
yes i get this problem too.. every morning my phone is off.... so it really needs to be looked into.. it seems to occur from more recent builds of 6.5..
i was previously using a wild child pure rom from about 3-4 months ago (6.5 early build)... this issue never happened...
then recently i upgraded to the V11 Unoff series and now it occurs.. and is obviously occuring for a lot of people with other recent builds of 6.5...
if the solution is ever found please let us know....
I might be completely off here... but I used to have this problem often, in addition to having slide to unlock malfunction on me, even with the newer rom builds.
When I unchecked the boxes that said display owner information/notes when device is turned on, both problems were gone - it might just be a coincidence though and I've only been testing it for 2 days.
Hey guys,
I've been having the same problem, only that this are the situations in which I faced the issue with my X1i (and managed to replicate the freeze):
-Receiving SMS while charging (no pc conection)
-Charging while alarm goes off (again no pc)
-When task or appointment announcement sets itself to sleep (i.e: you ignore it) while charging. (go figure, no PC)
-When after ignoring (not hitting dismissed button) task or appointment screen shuts off (Running on battery)
I've also gotten the problem in other situations, but i couldn't replicate them. The only Thing I did notice was that there is a growth in the rate this happens over a span of 3 days after flashing/hard reseting. In my case, it was one increment per day (ie: 1st day, happened once; 2nd day, twice; 3times the 3rd day.. then, i reseted or replicated, so my statistics went down the pipe )
Other thoughs: what radio are you guys using? maybe we can narrow it down to a radio as well. Thus far I've seen it narrowed it down to Manila 2.5, but then others do not have this (and then there me, with Manila 2.1, that has it ). I changed my radio y-day and hasn't happened yet (xing fingers though...) wil try to replicate tomorrow after my alarm wakes me up
My info:
X1i Black (came with R3 generic UK ROM, Radio. 1.14...)
Issues happened with: Radio 1.10.25.18 (Installed with NRG's ROM vOCT 28)
ROM info: (see signature..)
Manila: v2.1.191...
Current radio: 1.14...
Carrier: AT&T US
I tried to contribute as much info I could get about this issue... hope we can get it solved.
I'll try to flash again a WM6.5 version to see what radio will be installed. This week I needed my phone WORKING , so I used a 6.1 ROM.
I didn't find a pattern for my freezes, but I think it mostly happened while charging from the outlet, or in the morning before the alarm went off (very bad thing to happen), or after I snoozed the alarm (again, very bad).
I read somewhere that it's useful to format your SD card before flashing. I don't see how this could help, but I'll try to flash via USB or from another newly-formated SD card. I always flashed with kovsimg.nbh on the SD root and I only formatted it when I got the phone, 9 months ago...
Also, some say it's good to flash first an original ROM, hard reset, then install the custom ROM again. I tried that, even stock-SPL and hard-SPL again, but didn't seem to work. Maybe I had 48 hours without freeze, but then it started again.
@8SE8 - I never had those options checked, so we can rule that out I guess.
I have been reading about this issue here and in another forum - mainly
because I had seen it only one single time. It actually occured when I was
loading the device during the night. I do not remember which ROM it was
exactly, except that it was an itje ROM with Manila 2.5.
Then, I went back to Manila 2.1 and WinMo 6.1, Touch_X 10.X.X. Must say,
that is still my fallback ROM, it feels extremely fast, it is stable, memory
usage is low - what else to wish?
Next, I went to the multilanguage Rhodium based Manila 2.1 and WinMo 6.5
from itje in my own language. After installing FM Tuner, a correct dialer and
some tweaks, it is also very fast and stable, memory usage at 50%. No more
soft resets since almost a week now, no "stand-by of death".
The difference to others is maybe: I do not flash using the SD card, always
with the USB connection. Is this provoking the difference? I cannot imagine,
but this is what I can contribute here.
Hello. i am no cook lol, but I've flashed plenty of trouble free (not bug free) Roms between my old TP and my new TP2. The worst I ever saw was that POS htc messaging client.
Lately almost every ROM I flash has serious issues. My phone will stop responding so I soft reset and it takes foreeeever to boot up. If it all, usually stuck at ROM boot screen.
Then I loaded Viigo, rom says its untrusted and hard resets! Then doesnt work right! Then I tried restoring my PIMBackup and it wouldn't connect to Outlook. Before that, my data connection kept being very erratic, more off then on.
Very frustrating here. I thought maybe my phone was failing, but I saw another person complaining of the same thing.
can someone explain what causes this? I am on Tmobile, Tmobile TP2, and my usual ROMS are the Fusion and Shadowline ROMS, which have worked best for me. Never ever had these probs before. Is it the builds used? Possible virus (doubtful) or hardware failure?
With the shipped 6.1 rom i never had to reset. Honestly i never removed the battery cover until i installed my first cooked rom. I did some soft resets via hd restart just to free memory.
Most of the cooked roms are extremely buggy, also the official 6.5 doesnt power up from standby some times.
Energyrom photon is very stable though, better than official 6.5.
I highly suggest Pro Cell v5.5 (V6 being released soon!) never had any problems with it, is fast and responsive, looks the best in my opinion with colour icons etc 10/10 for me
Hi Guys,
I suppose one good thing to come out of me constantly finding my HD dead after it being on standby for a few hours (it seems intermittent) is that it seems many others are having similar issues.
Can people post their findings to the following question so we can help the community at large narrow down the issue:
When your device hangs/freezes, is it in standby or in use?
If the unit is in Standby, are you using Manila 2.5 or an earlier version?
Which WM version are you using? (6.1 of 6.5)
Have you unticked the "Today timeout" on the Today Settings screen?
My experiences are as follows:
I have only seen this since I have been using a 6.5 ROM
I have only seen this since I have been using Manila 2.5 (i think)
I install only a small number of applications
I have used both MyPhone and PIM Backup to restore info
oh and finally, it's bloody annoying!!!
If anyone has any information as to what could be causing this please post. I'm sure we'd all give our left nut to get this fixed?
This does seem to be an issue that effects some and not others, I had it happen a few times but after flashing back to an official ROM then back to custom (including SPL) I have using custom ROMs for a while now without this occuring again.
Flashmore, thanks for your input. Can you state what steps you followed for others?
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
xboxhalo said:
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
Click to expand...
Click to collapse
I'm attempting to systematically find out what the problem is by installing the same programs each flash with the exception of one. The first attempt was to move back to Manila 2.1 - so far so good but I'm expecting the same to happen at some point.
I want a good ROM, but I'm more bothered about not missing an emergency phone call because my phone is dead!
Hi all.
I'm not sure if this is actually related since when I experienced these so called "lock ups" my phone hard reset and corrupted the SD card as well. This happened two times with HD and once with Diamond2. Both phones with WM6.5.
I'm using corporate exchange and get enforced a device lock policy. I noticed that each time the device froze it was displaying the "classic" device lock number keyboard although the "default" (the new wm6.5) lock was selected.
Anyway, both phones have been working perfectly with WM6.5 and manilla 2.5 after I have started to use the ugly "classic" lock screen.
E
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
gallegus said:
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
Click to expand...
Click to collapse
That's interesting. I might try that.
I have been on Manila 2.1 for a few days and so far so good though.
I'm on WM 6.5 w/ Manila 2.1 for a couple of days and it has happened to me too.
I just tried disabling the options for turning off backlight and turning off phone. Hopefully this "fixes" the problem.
Check this thread, same subject, more details !
K
As said by Kostas66 above me. I guess this thread will soon get a lock...
As per post#10 & 11, please use this thread for future posts
Thread closed