hello there...
i need some help n want to know,why my phone when i turn the power button to turn on from off blacklight not working?i was flash many rom based 6.5 still same...when i reset n flash new rom it ok but after install same application the problem
Uhm,don't install that application?
i want just to know it because my softwares or hardware
sori i newbie and cannot speak english perfect
I think what is happening to you is the overall problem people have had with windows mobile 6.5, that sometimes while charging it simply will not turn on, the screen is black and you have to take out the battery to fix it. If this is the problem you can change it so that the screen does not turn off while charging in the power settings.
Then theres also the times when the mobile hangs after have been locked and turned off (atleast for me). But I figure this is due to applications I have installed. For example manila roms are sometimes pretty unstable, manila might collide with another software you have running and so the phone wont start.
My recommendation if this is a problem is actually to flash a 6.1 rom, the touch x rom is great: http://forum.xda-developers.com/showthread.php?t=561555
or perhaps a non-manila 6.5 like the energy titanium rom or the xperia unoff rom.
And to answer your question, it absolutely should be the software, as I suggested, test a 6.1 version and it should work great.
Good luck!
em maybe i try to change 6.1
i so tired to flash every day..huhu
thank u
Related
Hi Guys,
I'm using touch x ultimate on my xperia and its been amazing, but last night I had to use the soft-reset button because the HTC interface had jammed up, usually takes a few minutes but after the s-e logo showed up, it just went black. Tried for ages to make it work, nothing. I had to load up the boot-loader and update the rom, well 'update' as in re-install the same rom.
Its quite a worrying thing to happen, I lost all my data, loads of important stuff.
Just wondered if anyone else has had this problem, and If not why would it have occured!
Many thanks
Go for a change!
Hey u better go for touch it rom by itje or gtrab's 6.5 roms. Touch x ultimate is no longer updated and supported by the cook. It still has some bugs. I had to soft reset my device atleast twice a day when using touch x rom. It hangs so often. Right now im using gtrabs 6.5 rom. Until now its great. cheers!
Not sure why this occured on your device but.....It is still supported by the creator, he is just not cooking until a stable 6.5 platform comes out....ummm and if you look all (hense the hundreds of posts saying "Great rom...butttt"...lol)of the cooked roms have bugs, so if he is looking for a solution...then ask the creator of the rom...if you are worried about using a cooked rom....then the option to go back to a stock rom is always available.
Regards,
WC
Darkrider114 said:
Hey u better go for touch it rom by itje or gtrab's 6.5 roms. Touch x ultimate is no longer updated and supported by the cook. It still has some bugs. I had to soft reset my device atleast twice a day when using touch x rom. It hangs so often. Right now im using gtrabs 6.5 rom. Until now its great. cheers!
Click to expand...
Click to collapse
Hi,
same problem here, using Valkyrie Firestorm 2.1 ROM . Basically a good ROM, but since i can't trust it this will be the reason why i change the ROM again.
I use touch x 10.1 Blue and so far no problems at all. Could it be something you've installed after flashing that's caused it?
kinnyfaifai said:
I use touch x 10.1 Blue and so far no problems at all. Could it be something you've installed after flashing that's caused it?
Click to expand...
Click to collapse
I Use Firestorm since Wednesday. First Crash happened without any hint. After a normal Softreset it stuck and after a long time waiting suddenly the setup screen of windows mobile appeared.
The Second Crash was today after installing Fingerkeyboard 2.1 (wvga version) . After the konfig screen appeared the phone freezes and i had to reboot using the stylus, then Hardreset followed (and no, i did not press the two silverbuttons in the middle of the phone in addition)
btw: now, fingerkeyboard runs perfectly. I will wait and see, syncing my data all the time not to loose something.
When the Phone hardresets itself one more time, i must react. Fortunately i have vacation at the moment..
and sorry for my bad english, im from germany
Alex_de_Large said:
I Use Firestorm since Wednesday. First Crash happened without any hint. After a normal Softreset it stuck and after a long time waiting suddenly the setup screen of windows mobile appeared.
The Second Crash was today after installing Fingerkeyboard 2.1 (wvga version) . After the konfig screen appeared the phone freezes and i had to reboot using the stylus, then Hardreset followed (and no, i did not press the two silverbuttons in the middle of the phone in addition)
btw: now, fingerkeyboard runs perfectly. I will wait and see, syncing my data all the time not to loose something.
When the Phone hardresets itself one more time, i must react. Fortunately i have vacation at the moment..
and sorry for my bad english, im from germany
Click to expand...
Click to collapse
That´s exactly my problems with the Valkyrie 2.1 as well.
All I can say from my experience is this....sometimes when "beta" programs are used with other "beta" software...because in essence all of 6.5 is beta and ported from another device to work with the xperia....you will have random weirdness...things work one day...the next they don't....Yes they may look pretty and may have the latest and greatest so to speak in them, but with too many customizations,tweaks,mods....things are bound to break sooner or later....So this may be something to consider before flashing a cooked rom as opposed to sticking with a stock rom....
Regards,
WC
Hiya,
I've been using this phone for 2 months now, I've flashed a number of roms, ranging from windows mobile 6.0 to 6.5, I am currently using energy rom, however, with every rom I've used so far, the phone turns itself off at random intervals (i.e. goes into standby and won't come out).
Does anyone have any idea how to fix this? it's really irritating, it basically renders the alarm next to useless and having to pull off the cover/soft reset several times daily which is very inconvenient!
Any help is appreciated
try a clean rom, I've never had any problems with the Unoff series wm6.5 roms
key lock
when its in stanby mode slide out the qwerty keyboard. if it come back on i know what the probelm is
If it's the same behavior across different ROMs, it may well be a hardware problem. Try flashing a stock ROM and see if it still turns off by itself.
Or it could be that one of your installed programs is turning your phone off.
I was having the same problem with my X1, it happens with all manilla roms i tryed.
At certain point i was thinking it was a hardware problem till i use Christian's Clean Rom and the Xperio from Valkyrie both without Manilla.
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.
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
Hi i have a Touch Diamond 2 and am having some serious difficulties!
I've had the Energy ROM installed for about 3 months and all has been good until Sat.
My phone was hanging with the turn on screen(htc across middle) when i tried to turn it on and would just stay like that until i removed battery.
To solve the issue i have tried installing new ROM's with varying success. I have tried un grading to the new Energy ROM and it seems to work for a bit then turns itself off and wont turn back on until i remove battery again. I've also tried going back to the official ROM's. The WM 6.1 version does the same as the Energy ROM and the WM 6.5 one is even worse as it continues to give me the start up screen as before!
Is my phone dead or do i need to do something to get it back working again?
Any help would be much appreciated.
Cheers Sean
Sounds to me like the NAND is dying.. or just corrupted. Try HardSPL instead of ROMs. Possibly the bootloader is bad.
Cheers for the quick reply, I have just re-done the HardSPL to 2.51 now running with it and Energy ROM. Will see long long it works for but not overly optimistic the now! Will keep you updtaed.
Sean
Nope thats it turned itself off already! Bloody annoying!!!!!!
Is your SD card ok,sometimes these things happen when windows is not able to communicate with the sd card properly.