Database Develop

Screen get's messed up with Helmi BA WM2k5 AKU2.6 during charging

Hi,
I have a Qtek9090 which I upgraded yesterday to Helmi BA WM2k5 AKU2.6 Beta (v.1.1.2 Beta).
Everything went fine and I do like it (apart from the usual problems with WiFi, BT,...).
However I got into a shock-state when I turned it on this morning after leaving it in the craddle during the night for charging:
It would turn on, but the screen was completly f..ked up!!!
I did a Softreset -> screen still messed up
I did a Hardreset -> screen still messed up
I did reflash the upgrade -> screen still messed up
I took out the battery for half an hour and put it back -> still the same
After many resets and so on, suddenly I got the color stripes again and the phone booted normaly. I did not even loose any data.
Next I put it to charge again and after a while (the screen went off meanwhile), I turned it on and guess: scrambled screen again.
This time, I did the Reset this way: battery-notch off, kept the Softreset pressed and simultaneously put the battery-notch on again.
Is this a known problem (shouldn't be - I searched the forum!)?
Why does this happen?
Any ideas???
Also, I have these questions:
- What is this selection one has to do after the upgrade for (2. and 3. item YES)? What should the first item be: YES or NO? Can this be the cause for my problem?
- Would it be wise to downgrade again? (In case this is a defect -> so I can try to claim warranty, if things get worse...)
- What is the patch for energy management for? Where can I download it, as the link in the Wiki does not work? (Has this to do with my problem?)
Thanks,
vma

The problem remains.
It does not seem to depend on the charging, but happens when the device is turned off for some time.
When I turn it on it will either work fine, or funtion with a wild flickering screen.
Arrggghhhh!!!
Am I the only one with this problem?
Cheers,
vma

Hi,
Some month have passed on this issue. The reason I did not post about it, was because I had to send my BA for repair and one never knows if the "enemy" is listening... Now the warranty has expired anyway and mey BA is fully working.
It may have been a coincidence, but one day after the upgrade the screen went mad and totally messed up. Only 1 Hardreset in about 100 tries would bring it back to normal for some period of time and even reflashing it with WM5 or 2003SE would not make it work normal again.
The screen would get messed up suddenly for no particular reason, normally during a standby.
At the end I had to send it in for repair, which was actually a good thing, as I complained about the loose stylo and bad working hardkeys, all within warranty.
I got a new key-pcb, backside and they reflashed the device with 2003SE.
I am almost sure that I must have done something wrong with the upgrade to WM5.
Strangely I was able to flash 2003SE onto it, though it did still not work properly: hours with messed screen and sometimes out of the blue I would turn it on and the screen was OK again for a few hours.
Could it be a bad cable connection, which got repaired as well? Was it just a software problem?
One of the things I was in doubt with: when you enter this menu to format the device, the instructions say to switch two options, but the menu on my device had three options. Sorry - I do not exactly recall the details.
Anyone with an idea, why my device went mad?
As a side-note: while WM5 was great, while it worked during the one day it worked. I specially liked to be able to turn the device completly off or being able to remove the battery without loosing data.
However: not having my beloved BA fo two weeks made me reconsider doing experiments on it. Since I have it back I did not reconsider flashing it again.
But I would like to understand what had happend...
Cheers,
vma

May I assume from the lack of replies, that this was a pure coincidence on my device?
Nobody else experimented this weird problems after upgrading to WM5?
I am considering upgrading my phone again, essentially because I am tired of being afraid of discharging the battery and thus losing all data...
Cheers,
vma

Small Kaiser Problem

Hello,
I have been a member for about 3 months or so but not been a heavy poster. (sorry about that)
anyway I have a small problem which normally gets solved by a few searchs but I don't seem to be having any luck.
I Have an Orange build kaiser (installed the today screen) and have hard reset the device a few times after encounting the same problem again and again (about to hard reset for the 4th time i belive)
back to the point, the problem seems to be a simple one in that new SMS don't appear on my today screen... weired?! and last night was the worst my phone was on charge but in standbye mode but my girlfriend couldn't connect any phone calls and when i checked my phone i had a mountain of missed calls and a bundle of txts which all came through at the same time on wake up..
(I've mentioned the fact my phone was on charge because search results suggest it was due to a 30% or less battery)
when i had the problem before I thought at 1st it was one of the many many cabs that have installed so this time i made sure i+I only had on the minumal
(forgive me but with the phone not being with me I am not sure on the names but here is the list)
HTC Home (maybe an old verison but i have tried many verisons)
HTC Home customiser (with IPHONE apps theme)
TOM TOM 6
HTC touch Keypad
A program to stop the phone connecting to the internet
A program that on start up my phone switches directly to the Keypad
Like I said used to install loads and loads of cabs but now limiting my self to a few to try and rectify the problem.
any one else had this problem? should i send it back to Orange? (I have insurance), will there be problems reinstalling TOM TOM? is one of the apps i have currently installed a problem?
any help would be much appricated and thank you in advance.

Does it exhibit this behaviour if you leave the phone in shipped condition, with NO software installed by yourself? If so, then it's faulty; if not, then install your apps one by one and test until you find what's causing it by process of elimination.

thanks for the reply...
I was going to leave it this time around with the dreaded orange home screen, was hoping someone else had a simular problem with one of the apps i have already mentioned
I'll give it a go tonight and see how it goes
thanks again for the reply

Grey screen of death?

Does anyone experience "Grey Screen of Death"??
Every couple of days my Diamond crashes, the screen is stuck displaying a noisy grey screen.
Most likely I will have to reinstall the ROM (I'm using SwiftBL 5.5) ... but if there is a simpler solution out there I'd love to know it,
Thanks,
Mike

I've seen that kind of screen but only when I'm playing a particular game and if I switch the Diamond off before closing the game down; when I next switch it on I get the noisy (mostly) grey screen. When this happens to me though I just need to toggle the power on and off a couple of times and it sorts itself out. Or just not switch the thing off when playing that game of course.
None of which helps you of course as yours sounds like a much more serious and randomly occurring issue.

never heard of it before. try changing to a different Hard SPL, these can have funny effects sometimes.

Thanks for reply. Well, at least I'm not alone.
Mine is more worrying alright. I left the Diamond in standby last night, it wasn't running any apps before that, and the phone didn't wake me up with my normal alarm as it had crashed sometime during the night, not doing anything in particular.

do you notice it get unusually hot at any time?
with some diamonds, when it is processing a lot and on charge it can get very hot, and this may have caused ur problem.

Maybe the Hard SPL will help.
One possibly odd thing I notice is that my ROM is listed as 1.93.00.00 on the bootup screen, I expected this to be 1.93.405.1. Is that usual?

It's not the hot or charging possibilities.
I can't find a pattern really, it definitely crashes just sitting there doing nothing.

Does this also happen with a stock rom?

I didn't see it on the stock rom, but that didn't last too long in my diamond and I've been running the Swift one for a couple of months now.

To rule out SPL and radio, you could try different versions there. If that doesn't help, try flashing another rom (maybe also the stock rom).
If this still doesn't get rid of the GSOD, I would send the phone back for repairs.
Sorry, I couldn't be of more help...

Good suggestions, thanks. At least there's something to try without flashing whole rom.

mine is the same, seems to only do it when phone is charging but idle overnight, and certainly not hot when it does it. I am running the stock 1.93 ROM. Maybe it just gets bored lol!

Then mine was very bored.
Always restarted itself during the night - and lost half the battery charge while doing so.
Had it repaired twice and now it works great. They told me it was a software problem, but I wonder what they fixed, because I have flashed the same SPL, radio and rom on my phone as before.

Glad you fixed it. Mine was ordered on the cheap from HK (to Ireland) so I'm reluctant to send it back except in dire need.
I often see it get very hot around the crash time, as if some app is running crazy, would explain the low battery.

BTW, what rom, spl, radio do you use?

I had the same exact problem up till a week ago.
Now I'm happily a satisfied Diamond user. To solve this issue, do either of the following:
1. Find a rom with a newer Manila version, e.g. Dutty > v2.6.
2. Install the latest Manila cab.
Changing hard spl doesnt work, as I had tried them all. Stock rom was more acceptable but the problem still occurs once in a while.
I had changed to Dutty's rom more than a week ago I haven't had the problem ever since. Try it and share with us if it works.
Reason I say its due to Manila is becos Dutty is using a newer version of Manila as compared to the rest.

Oooh, tasty. A confirmed software method of fixing the problem! I'll give that a go and observe the phone for a week. I'll post then if all is well.
Many thanks,
Mike

I'm running Olinex HardSPL 1.93, Radio BS14 and O2 Germany stock rom 1.93.207.2.
I hope knave's solution will do the trick for you.

Hi...
This just append to my phone sometime tonight..!
A left it charging over night ... like I always do..
and when I wake up... there's just a gray screen of death!
I've just flashed my first cooked rom... had stock HTC ROM before...
and my TF3D version is 1.2.35091.2_1813.6..
maybe this was just a freak accident... one time happening??
lets wait and see...

i'm backing up my phone at the moment to hard reset it later. i've got the problem, that in opera when the page (spiegel.de especially) is fully loaded and it idles for 5 secs, the screen turns grey with stripes and blocks slowly. after hitting power on/off 2 times it's normal again, but as soon as it's idling for 5 secs it fades to grey again.
must have messed up something while updating opera

Strange problem

So I have my new diamond for a couple days now and updated to the last 2.03 Win Mob 6.1 rom from HTC. The phone is all stock and the only thing I installed was background in all tabs of manilla TF. Now I notice that between some hours my diamond lights up for a second and turns off again. I don't know what might be causing this. This is my second diamond as the first one was always freezing and the warranty gave me a new phone!

mine does this in some areas of my home where i don't get good reception and the phone is switching modes. this happens so much that it may drain my battery overnight if i don't put it into airplane mode. not saying that's what's happening with you but it's a possibility.

This is very strange, because I only noticed this while the phone was without the SIM card!

Zero|Cool said:
The phone is all stock
Click to expand...
Click to collapse
Found your problem.
You should look into a cooked ROM. They're so much better...my diamond wouldn't even be close to what it is today with a stock ROM.

Solutions to charging and standby freeze?

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.