Related
One of my problems is :
sometimes when the power is off in my B.A. i cant turn it on by pressing power button I had to reset
and when it is off i cant receive any call because it is not ringing and I don’t know if there is a call so I missed a lot of call lately that I don’t know about
please can any one help me with that
Yes,mine is the same as yours.
Any help please?
It seems that your machine hanged. Did U apply all the cab files on the first page?
wodonwong said:
It seems that your machine hanged. Did U apply all the cab files on the first page?
Click to expand...
Click to collapse
yes i did
and this power problem is not happening every time when the power is off
maybe ones or twice a day
One of my problems is :
sometimes when the power is off in my B.A. i cant turn it on by pressing power button I had to reset
and when it is off i cant receive any call because it is not ringing and I don’t know if there is a call so I missed a lot of call lately that I don’t know about
please can any one help me with that
Click to expand...
Click to collapse
Strange, I am using the helemi_C rom but I havn't experience any problem like this. May be you need to reflash the rom again with all fixes available. [/list]
I flash this ROM this morning and face this problem in the afternoon one time.
I have had this thing in my Himalaya with WM5 ROM a long time ago.
Don't know why.
Did U hard reset and clear all the previous registries?
Yes , surely.
with options No,Yes,Yes.
don't know if it can help but I had the very same problem with different roms. after some tests I discovered that this was due to the joypad at the bottom, the 'down' key made contact and was, in a way I don't know, kind of overriding the pression of any key, power included.
cleaning the contacts worked perfectly for me.
straniero said:
don't know if it can help but I had the very same problem with different roms. after some tests I discovered that this was due to the joypad at the bottom, the 'down' key made contact and was, in a way I don't know, kind of overriding the pression of any key, power included.
cleaning the contacts worked perfectly for me.
Click to expand...
Click to collapse
I am sorry but I don't understand what should I do exactly
i also have this problem, anybody can help??????
Same problem with Qtek9090 flashed with IvanV4R3_RAMDisk32_1
Hi guys,
In fact, I'm having the same problem after having flashed my Qtek9090 with IvanV4R3_RAMDisk32_1.11. (When the device is turned off (standby mode) for more than 5 minutes, it's impossible to turn it back on - only reset helps. While that state, when somebody rings my phone, they get "engaged" signal as though I'm talking on the phone. When you put the device into cradle - the computer indicates that there is a new device with some installing errors...)
Now, I've noticed one thing: there is a localization software from Paragon (LEng - Russian language pack for Pocket PC) - after having disabled that software, the device works well and comes back from the standby mode easily. Perhaps, that deals with some bugs in the localization software.
I guess you all have some localization soft on your BA (Arabic, Chinese, etc.) - try and disable it - let's see if that helps...
No i dont have any language pack on my PPC.
Using helmi 1.3 and this is what i have currently installed
E-TEN m600 Blue Dualer Skin
IdosPPC - (train schedule )
Resco Explorer
Resco Today Plugin
Resco Keyboard Pro
Helmi 1.3 NET missing FIle
SpbAirlands
Microsoft .NET CF 2.0 ENU-String
Socket Wi-Fi Companion
SpaceTime Mobile 2.0
Gray is right. I have tried 2 Chinese Localisation softwares, namely Monster Chinese V5.3 and CE-Star V2.8R2 and they both hanged the machine, especially before dawn, usually with the red LED flashing but BA hanged. Well yes, I am using the stupid MS Auto-Push on my BA! (Pocket Outlook is the least stupid email client available at the moment, FlexMail still needs much works to integrate with the WM5 interface) I have tried to disable MS Auto-Push while running Monster Chinese V5.3 and tested for 3 full days without hanging.
When I resumed the MS Auto-Push, the machine hanged again.
Interim findings:-
1. My BA hangs when running both Chinese localisation software and MS Push.
2. My BA seems to work OK when running Chinese localisation but not MS Push.
3. My BA seems to work OK when running MS Push but not Chinese localisation.
I guessed Notification of Email feature may have caused the hanging problem, I'll try to reduce the red LED flash duration from UNLIMITED to say 15 minutes. Will report my findings in due course.
In fact, I've installed an update for the language pack (LEng build 7928) and the problem disappeared.
So, I guess, you need to check if there is any buggy software on your PPC. ...Although the issue may be much deeper...
Good luck!
Hi there,
I wonder if anyone has had that problem before, and knows of a fix.
Ocassionally, after a few hrs/days of use, my SPV M1500 gets the screen shortcuts "confused" - for example, on the today screen I will tap on "Start" and TomTom will start, in the "Settings" screen I tap "Device info" and "backlight" comes up, and so on.
A soft reset solves the problem, but it will come back a few hours/days later.
It is annoying, to say the least.
Has anyone ever had this before? The M1500 is stock, except for an upgrade to Radio 1.04.00
Details:
ExtROM 1.11.167
OP Vers 3.11.1.167
ROM 1.11.00
Radio1.04.00
Protocol 1337.42
Thanks in advance,
seg
you should try recaliberating your screen. If the problem persists, do a backup followed by hard-reset(this ll also bring the caliberation screen)
Thanks for the reply, kdskamal.
I will try your suggestion, but the fact that after a soft reset everyrthing works fine, for a while, seems to imply that the calibration is OK?
It seems that something gets corrupted over time - more like a memory leak, or a stack overflow, or some other software problem.
Anyway, I will recalibrate to see if it makes any difference.
Thanks,
seg
Hi all,
As an update to this, I recallibrated the screen but the problem is still there. To make it even more interesting, a few nights ago I put the Alpine on the cradle, Activesync started, and then, the bluetooth manager fired up!
I have narrowed it down to two options:
--demonic possesion,
--badly corrupted registry.
Perhaps it's time for a hard resety and re-install...
seg
You could try memory cleaning progs like Memmaid...
Or you could try cleaning the registry (Memaid also has that feature)...
Have you done any tweaks to your Alpine?
Hi,
I have just upgraded my Blue Angel's (BA) ROM to the WM5 AKU3.5.2 R5 Rom Kitchen v2 last night, but start having issues already!
There are a couple of scenarios that I found the BA will hang at the startup screen when the Windows Mobile logo appears.
1. The first scenario was when I changed my battery. I turned off the screen, pull the battery out and replaced it. The BA hung!
2. I installed SPB Pocket Plus 3 and uses the embedded RESET function (icon) to restart the BA. Every single time I did it, the BA hung. (And I have tried more than 5 times. It really started to piss me off!)
The only solution that I can get back to the WM5 system was to give my BA a hard reset! The paid was to LOSE ALL the programs I have installed!
Has anyone experienced this before? What was wrong with it?! Did I do something ridiculously wrong or just another bug (a big one!) of the ROM? If it's a bug, anyone has a smarter way to get around it rather than hard resetting the BA before the fix comes out?
Many Thanks!
Spent hours on it!!!! Resolved by upgrading the ROM to the latest AKU3.5.2 R5 Rom Kitchen v2 and use the default setting with "BuildOS.exe".
Cheers
I've been lurking on these forums since I got my diamond, about 5 months ago, and i would like to say, I would have sold my diamond about 2 weeks after buying it if it wasn't for all the knowledge and tools available here. Thank you.
Now, I've been flashing my phone every so often, with ROMs such as Swtos, Panosha, Duttys, AZTOR, Wildberry, Dia Diut, and most recently (wherein the problem lies), NATALY 2.1, Cloudy 1.0 and udK Syrius R3.
Now with these latest three roms (2.03?), i started to encounter a similar problem over and over again, without exception. If I try to launch a program while another is using the CPU, the phone will begin to crash. First it will become unresponsive, then programs will no longer open, and eventually, the only thing that can be done is a soft reset.
For example, the alarm will activate (klaxon), i'll flip the phone, and hit off. Now I know the problem has begun because though the phone has returned to the home screen, the title bar may still show the image from the alarm. Now the phone will work like its cpu is being heavily engaged and I can never reach task manager to see what it is. The hard volume keys frequently cause the phone to begin behaving in this manner. Soft reset only solution again. TF3D still animates, but programs will never appear on the screen if you try to launch them.
Same sort of effect on Cloudy's and udK's, except after the soft reset, the phone would begin to reinstall the rom again, as if some sort critical error occurred.
I have a DIAM130, and i've heard that to install 2.03 base ROMS (such as NATALY2.1 and Cloudy, is that correct?) you should first install a 2.03 SPL and a 2.03 stock ROM, then upgrade the SPL, then the ROM.
The latest SPL i've seen here is 1.93, and installing this increased the stability of these ROMs from 30 minutes to about 1-2 days, but the same problem occurs.
(also, haven't been able to find a stock 2.03 ROM on here... am I blind/illiterate?)
Latest addition to this problem (first occurred a few minutes ago after the phone began reflashing itself again after the aforementioned problem): Windows began the usual first-time boot customization procedure, and is now giving me an error: Run FILEOP \Windows\Menu_FILEOP_Operator.txt failed.
Is there some sort of corruption or hardware failure going on?
Well, thanks in advance
EDIT: Problem solved by reflashing stock SPL and 2.03 ROM, then flashing what I wanted. The impression i get from the pros here is that I flashed a ROM which wrote to some memory location that shouldn't have been written to.
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.